My Suse 10.2 used to come up with two boot options. No problem.
Now it offers me several:-
openSUSE 10.2
openSUSE 10.2 – 2.6.18.8-0.5
Failsafe – openSUSE 10.2 – 2.6.18.8-0.5
Floppy
Failsafe – openSUSE 10.2
XEN
The second one is highlighted, and if I just let it run I get the message:-
Error 15: File not found, Press any key to continue…
If I select the topmost option Suse runs up apparently normally.
Where have all these options come from, what do they mean, and how can I correct or delete those that are not needed please?
It looks as though a new kernel has been installed, hence the two options with a kernel number. To find out the number of your kernel, you can use the command ‘uname -r’. The distros I’ve used enter the kernel number for the new kernel.
You can edit the boot file directly. Are you using Grub or lilo? Or, probably, you can use the control centre (Yast?) to edit your boot menu.
Please help build a new site for KOffice users
Reading for fan children
each time your system updates (connecting to the internet, it modifies the file in /boot/grub/menu.lst
that file tells the system what to start and from where on the disk: read your menu.lst:
ls -l /boot/grub/
total 196
-rw-r–r– 1 root root 197 2007-11-18 20:43 default
-rw-r–r– 1 root root 15 2007-11-18 20:43 device.map
-rw-r–r– 1 root root 7584 2007-11-18 20:43 e2fs_stage1_5
-rw-r–r– 1 root root 7424 2007-11-18 20:43 fat_stage1_5
-rw-r–r– 1 root root 8192 2007-11-18 20:43 jfs_stage1_5
-rw-r–r– 1 root root 4448 2007-11-18 20:49 menu.lst
-rw-r–r– 1 root root 6848 2007-11-18 20:43 minix_stage1_5
-rw-r–r– 1 root root 9280 2007-11-18 20:43 reiserfs_stage1_5
-rw-r–r– 1 root root 512 2007-11-18 20:43 stage1
-rw-r–r– 1 root root 108360 2007-11-18 20:43 stage2
-rw-r–r– 1 root root 8904 2007-11-18 20:43 xfs_stage1_5
cat /boot/grub/menu.lst (you could copy it to your homedir and have a look at it)
and if you list your /boot/
ls -l /boot/ you’ll see all the kernels still in store (the initial you installed and the upgrades downloaded with yast)
ls -l /boot
total 18072
-rw-r–r– 1 root root 70781 2007-05-09 23:14 config-2.6.18-4-686
-rw-r–r– 1 root root 70658 2007-10-03 00:31 config-2.6.18-5-686
drwxr-xr-x 2 root root 4096 2007-11-18 20:49 grub
-rw-r–r– 1 root root 4901099 2007-11-18 20:49 initrd.img-2.6.18-4-686
-rw-r–r– 1 root root 4495651 2007-11-18 20:06 initrd.img-2.6.18-4-686.bak
-rw-r–r– 1 root root 4901677 2007-11-18 20:49 initrd.img-2.6.18-5-686
drwx—— 2 root root 16384 2007-11-18 19:41 lost+found
-rw-r–r– 1 root root 722037 2007-05-10 05:14 System.map-2.6.18-4-686
-rw-r–r– 1 root root 722899 2007-10-03 05:49 System.map-2.6.18-5-686
-rw-r–r– 1 root root 1261213 2007-05-10 05:14 vmlinuz-2.6.18-4-686
-rw-r–r– 1 root root 1260158 2007-10-03 05:49 vmlinuz-2.6.18-5-686
you see here (debian kernels and starting img 2.6.18-4-686 was the 1st installed and the next version upgraded: 2.6.18-5-686)
so all you have to do is to
ls -l /boot and check which version you’re running and it must match your menu.lst
but if you’re unsure, don’t touch menu.lst or it would fail to start your system.
since menu.lst is edited by the system it should be ok, obviously your second line is pointing to a missing file. check if you’ve got 2.6.18.8-0.5 for each file in /boot
You can compare with the kernel number you’re running by checking as you’ve been advised in the previous reply.
Thanks. I have looked at the lists described, but am not sure how to interpret them or what actions I should take. I have pasted the outputr here:
linux-oiu2:~ # uname -r
2.6.18.2-34-default
linux-oiu2:~ # ls -l /boot
total 7764
-rw-r–r– 1 root root 744294 Nov 27 2006 System.map-2.6.18.2-34-default
-rw——- 1 root root 512 Sep 28 13:24 backup_mbr
lrwxrwxrwx 1 root root 1 Sep 28 12:32 boot -> .
-rw-r–r– 1 root root 72710 Nov 27 2006 config-2.6.18.2-34-default
drwxr-xr-x 2 root root 4096 Nov 2 16:04 grub
lrwxrwxrwx 1 root root 26 Oct 22 16:06 initrd -> initrd-2.6.18.2-34-default
-rw-r–r– 1 root root 2916874 Oct 22 16:06 initrd-2.6.18.2-34-default
-rw-r–r– 1 root root 379904 Nov 2 16:04 message
-rw-r–r– 1 root root 86990 Nov 27 2006 symsets-2.6.18.2-34-default.tar.gz
-rw-r–r– 1 root root 344102 Nov 27 2006 symtypes-2.6.18.2-34-default.gz
-rw-r–r– 1 root root 100600 Nov 27 2006 symvers-2.6.18.2-34-default.gz
-rwxr-xr-x 1 root root 1761938 Nov 27 2006 vmlinux-2.6.18.2-34-default.gz
lrwxrwxrwx 1 root root 27 Oct 22 15:51 vmlinuz -> vmlinuz-2.6.18.2-34-defau lt
-rw-r–r– 1 root root 1474998 Nov 27 2006 vmlinuz-2.6.18.2-34-default
linux-oiu2:~ # ls -l /boot/grub/
total 216
-rw——- 1 root root 45 Nov 2 16:04 device.map
-rw——- 1 root root 45 Oct 22 16:06 device.map.old
-rw-r–r– 1 root root 7552 Nov 25 2006 e2fs_stage1_5
-rw-r–r– 1 root root 7424 Nov 25 2006 fat_stage1_5
-rw-r–r– 1 root root 6688 Nov 25 2006 ffs_stage1_5
-rw-r–r– 1 root root 6688 Nov 25 2006 iso9660_stage1_5
-rw-r–r– 1 root root 8160 Nov 25 2006 jfs_stage1_5
-rw——- 1 root root 1493 Nov 2 16:04 menu.lst
-rw——- 1 root root 1496 Oct 22 16:06 menu.lst.old
-rw-r–r– 1 root root 6848 Nov 25 2006 minix_stage1_5
-rw-r–r– 1 root root 9216 Nov 25 2006 reiserfs_stage1_5
-rw-r–r– 1 root root 512 Nov 25 2006 stage1
-rw-r–r– 1 root root 104042 Oct 22 16:06 stage2
-rw-r–r– 1 root root 7040 Nov 25 2006 ufs2_stage1_5
-rw-r–r– 1 root root 6240 Nov 25 2006 vstafs_stage1_5
-rw-r–r– 1 root root 8904 Nov 25 2006 xfs_stage1_5
linux-oiu2:~ #
Lokking forward to hearing!
In /boot/grub/ directory search for a file name menu.lst. Take a backup of this file. Open this file in a text editor like vi or nano or ed. Delete unwanted entries. Save this file and enjoy.
check out the following link on how to edit this file safely:
http://boff.wordpress.com/2007/01/17…rub-boot-menu/
|
|
If your leery about editing anything in your /boot/grub you can do this through yast, open yast select system then boot loader.
Once there you should be able to see what to do
if you choose to edit i would strongly suggest making a copy first
On a side note you can call it whatt ever you like mine is Windows Blaster
just select highlight and then select edit and edit the name
Tux
Posting Permissions
Reply With Quote
Bookmarks