Boot fails after Kernel update (SuSE10.3)

English Install/Boot/Login
1

Hi,

today I performed a kernel update using the automatic updated from 2.6.22.17-0.1 to 2.6.22.18-0.2.
After rebooting the machine, it won’t come up anymore. It hangs up with the following error:

Waiting for device /dev/disk/by-id/scsi-SATA_ST3120023AS_3KA1AKAV-part2 to appear: ....................Could not find /dev/disk/by-id/scsi-SATA_ST3120023AS_3KA1AKAV-part2

I’ve tried to start with a knoppix CD, but there the drive is reachable and exits under this namings …

Does somebody has a solution for this?

cya

hachtl

2

Try just using the device name and not the device ID name in fstab. Like /dev/sda2 which should be close, :stuck_out_tongue: . Also, did you install any other hard drives lately? Perhaps left in a USB drive? Somtimes GRUB is finicky with these things. Simply do:

sudo vim /where/hard/drive/is/mounted/etc/fstab

And edito the line have to do with
/dev/disk/by-id/scsi-SATA_ST3120023AS_3KA1AKAV-part2
to
/dev/sda2
Assuming you have only one harddrive.

CaptSilverFox
OpenSuse 11

3

No, there was no change in the configuration recently.

The error is still the same with “Waiting for device /dev/sda2” instead …

After the Message comes:

Want me to fall back to /dev/disk/by-id/scsi-SATA_ST3120023AS_3KA1AKAV-part2 (Y/n)

But you hardly can enter a key now …

hachtl

4

You must recreate your initrd…I think I have had this problem before. Start a live cd.

mkinitrd -d /dev/sda2

That should get you up and running, :stuck_out_tongue:

5

Hi,

not that easy. I tried the following:


mount /dev/sda2 mnt/
mount --bind /dev /mnt/dev
chroot /mnt
mount /proc
mount /sys
mkinitrd
Kernel image:   /boot/vmlinuz-2.6.22.18-0.2-default
Initrd image:   /boot/initrd-2.6.22.18-0.2-default
Root device:    /dev/sda2 (mounted on / as ext3)
Kernel Modules: processor thermal scsi_mod libata pata_amd sata_sil fan jbd mbcache ext3 edd sd_mod usbcore ohci-hcd uhci-hcd ehci-hcd ff-memless hid usbhid
Features:       block usb resume.userspace resume.kernel
Bootsplash:     SuSE (1280x1024)
17537 blocks
/proc/misc: No entry for device-mapper found
Is device-mapper driver missing from kernel?
/dev/mapper/control: open failed: No such device
Failure to communicate with kernel device-mapper driver.
Command failed
/proc/misc: No entry for device-mapper found
Is device-mapper driver missing from kernel?
/dev/mapper/control: open failed: No such device
Failure to communicate with kernel device-mapper driver.
Command failed
/proc/misc: No entry for device-mapper found
Is device-mapper driver missing from kernel?
/dev/mapper/control: open failed: No such device
Failure to communicate with kernel device-mapper driver.
Command failed

The result after booting is still the same … I think the error messages are the problem … any hints? :confused:

cya

Hachtl

6

It does sound like you are for some reason missing a kernel module which must be loaded to access the drive’s controller.

Use the installation DVD to boot into repair mode. Go to the boot loader section and re-install it. That will re-create the initrd. Beforehand, use the live CD to take a look at /etc/sysconfig/kernel which lists the modules that SuSE’s mkinitrd script will build into the initrd. Make sure what you need is in that list.

7

Hi all,

this won’t work either. I gave up, and have reinstalled the system.

cya

Hachtl