I had to edit menu.lst to get it pointing to a drive that was actually there for starters (The drive referenced in resume on menu.lst produced by the update has not existed in this machine for over a year at least.)
here is the menu.lst made during the update.
# Modified by YaST2. Last modification on Tue Nov 8 16:11:13 PST 2011
# THIS FILE WILL BE PARTIALLY OVERWRITTEN by perl-Bootloader
# Configure custom boot parameters for updated kernels in /etc/sysconfig/bootloader
default 0
timeout 8
##YaST - generic_mbr
gfxmenu (hd0,0)/boot/message
##YaST - activate
###Don't change this comment - YaST2 identifier: Original name: linux###
title Desktop -- openSUSE 11.4 - 2.6.37.6-0.9
root (hd1,0)
kernel /boot/vmlinuz-2.6.37.6-0.9-desktop root=/dev/disk/by-id/ata-WDC_WD5000AADS-00M2B0_WD-WCAV5R429030-part1 resume=/dev/disk/by-id/ata-ST3500630AS_9QG141S6-part5 splash=silent quiet showopts vga=0x31a
initrd /boot/initrd-2.6.37.6-0.9-desktop
###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- openSUSE 11.4 - 2.6.37.6-0.9
root (hd1,0)
kernel /boot/vmlinuz-2.6.37.6-0.9-desktop root=/dev/disk/by-id/ata-WDC_WD5000AADS-00M2B0_WD-WCAV5R429030-part1 showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe vga=0x31a
initrd /boot/initrd-2.6.37.6-0.9-desktop
###Don't change this comment - YaST2 identifier: Original name: linux###
title Desktop -- openSUSE 11.4 - 2.6.37.6-0.7
root (hd0,0)
kernel /boot/vmlinuz-2.6.37.6-0.7-desktop root=/dev/disk/by-id/ata-WDC_WD5000AADS-00M2B0_WD-WCAV5R429030-part1 resume=/dev/disk/by-id/ata-WDC_WD5000AADS-00M2B0_WD-WCAV5R429030-part1 splash=verbose showopts nomodeset vga=0x31a
initrd /boot/initrd-2.6.37.6-0.7-desktop
###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- openSUSE 11.4 - 2.6.37.6-0.7
root (hd0,0)
kernel /boot/vmlinuz-2.6.37.6-0.7-desktop root=/dev/disk/by-id/ata-WDC_WD5000AADS-00M2B0_WD-WCAV5R429030-part1 showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe vga=0x31a
initrd /boot/initrd-2.6.37.6-0.7-desktop
This is the edited menu.lst
# Modified by YaST2. Last modification on Tue Nov 8 16:11:13 PST 2011
# THIS FILE WILL BE PARTIALLY OVERWRITTEN by perl-Bootloader
# Configure custom boot parameters for updated kernels in /etc/sysconfig/bootloader
default 0
timeout 8
##YaST - generic_mbr
gfxmenu (hd0,0)/boot/message
##YaST - activate
###Don't change this comment - YaST2 identifier: Original name: linux###
title Desktop -- openSUSE 11.4 - 2.6.37.6-0.9
root (hd1,0)
kernel /boot/vmlinuz-2.6.37.6-0.9-desktop root=/dev/disk/by-id/ata-WDC_WD5000AADS-00M2B0_WD-WCAV5R429030-part1 resume=/dev/disk/by-id/ata-WDC_WD5000AADS-00M2B0_WD-WCAV5R429030-part1 splash=verbose showopts nomodeset vga=0x31a
initrd /boot/initrd-2.6.37.6-0.9-desktop
###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- openSUSE 11.4 - 2.6.37.6-0.9
root (hd1,0)
kernel /boot/vmlinuz-2.6.37.6-0.9-desktop root=/dev/disk/by-id/ata-WDC_WD5000AADS-00M2B0_WD-WCAV5R429030-part1 showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe vga=0x31a
initrd /boot/initrd-2.6.37.6-0.9-desktop
###Don't change this comment - YaST2 identifier: Original name: linux###
title Desktop -- openSUSE 11.4 - 2.6.37.6-0.7
root (hd0,0)
kernel /boot/vmlinuz-2.6.37.6-0.7-desktop root=/dev/disk/by-id/ata-WDC_WD5000AADS-00M2B0_WD-WCAV5R429030-part1 resume=/dev/disk/by-id/ata-WDC_WD5000AADS-00M2B0_WD-WCAV5R429030-part1 splash=verbose showopts nomodeset vga=0x31a
initrd /boot/initrd-2.6.37.6-0.7-desktop
###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- openSUSE 11.4 - 2.6.37.6-0.7
root (hd0,0)
kernel /boot/vmlinuz-2.6.37.6-0.7-desktop root=/dev/disk/by-id/ata-WDC_WD5000AADS-00M2B0_WD-WCAV5R429030-part1 showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe vga=0x31a
initrd /boot/initrd-2.6.37.6-0.7-desktop
I think this should boot but it doesn’t. What am I doing wrong?
So seeing that it points to hd1,0 since you could see that and I didn’t i’ll try and fix that. It will probably fix it
What can I do to prevent this from pointing at the wrong drive in the future when YAST configures it during a kernel update?
The original .7 kernel is booting on this machine. I keep my old kernels so I don’t get hosed if a kernel update goes bad. I am posting this message from that machine. I simply copied the “resume” portion that needed to be fixed into the line that added the new kernel. The boot is done from “/” There is nothing in the mbr. The drive exists and I am using it and booted from it so I knew something I didn’t notice was wrong
While the smoothness in kernel updates have improved over the years, I am still of the ‘old school’, and before every kernel update I still make a copy of the /boot/grub/menu.lst file, and then AFTER the kernel update and BEFORE restarting, I always compare the old menu.lst to the new menu.lst (updated by script in the kernel rpm) to see what the changes might be, and to see if they make sense. I concede its a bit of a pain to do so, but the pain it can prevent (in cases where the script is not advanced enough to figure out one’s complicated partitioning) makes it worth putting up with the effort to do the file content inspection (of the new menu.lst). The key is this needs to be done before the reboot.
Color me confused by my own drive layout. As you can see the drive referenced as where the boot is, is gone. It’s hashed out because the drive is in a drawer not in the system.
I need some guidance as to how to proceed in the bootloader part of YAST.
Whatever you have in the devices.map file is there since install day, the
system will not modify it unless you do. So if your removed a drive it will
not be noticed in that file, nor in fstab.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
Hello this is my first post on the forum. After some years away from linux I’ve started using it again a few months ago so my problem resolution abilities are close to none. I’ve done the kernel update earlier so when asked for a reboot I did, when it went to grub all I had was “linux other” and “floppy” (no kernel update boot option appeared as usual) options so I can’t boot into the system and I don’t know what to do. A little help would be much appreciated.
Fortunately, the new kernels had been installed. Here’s what I did:
I booted the install disk to rescue mode, and logged in as root.
I “cd” to “/boot/grub”.
I copied “menu.lst.old” to “menu.lst”. That was after checking that “menu.lst.old” had all of the entries.
I then edited this “menu.lst” to update the kernel names to match what was actually there in “/boot”. The “menu.lst.old” had the old kernel versions, while only the new kernel versions existed. So editing those to the correct names was needed.
This worked, and on reboot the system came up as it should.
If, for some reason, you don’t have any kernels installed, then it will be a bit more tricky (but should still be doable). Here is where I describe how I solved a similar problem: Rescuing Susie
Revisiting this as after my most recent kernel update I had to go back to menu list and edit it again. I know now due to this thread that the drive getting added to menu menu.lst is the wrong drive.
After reading this, I recall that when I updated my 3 HDD box from 11.4 to 12.1, the first time I tried to boot without the install DVD installed I got a similar (or the same) error message as in #1.
I just popped the DVD back in, started from it, started DVD chose boot from Hard Drive and had 12.1 up and running.
I then ran updategrub and reinstalled the boot loader to the MBR on the boot drive.
At the time I thought it was due to my environment ( I boot from the /sdb drive. it is first in the bios order) but perhaps there is a more general problem with the automatic grub configuration on multidrive systems?
At any rate, find grub and update grub were helpful creating a workable menu, I used yast-boot to make sure the correct MBR was written.
It’s a simple matter once you know whats’s up to edit menu.lst. D
ealing with device.map is different for me since I don’t know what it actually does.
The drives in the list may not be in the order they appear in the list and may not ( in at least one case is not ) be installed anymore. I am trying to update proof the machine looking forward to a future kernel update and eventually an update to 11.2 without encountering problems.
