Hi again, thanks to Anders Johansson we figured out that /dev/900 is my /dev/md0. old-Kernel: 2.6.4-52-default (SuSe 9.1) /dev/hda1 = boot /dev/hda3 + /dev/hdb3 = /dev/md0 = / #(root) After upgrading the Kernel with YOU to 2.6.5-7.--somthing the box no longer boots. the boot stops with the message: Waiting for device /dev/900.... not found ! I already did: Rescue-System: mount /dev/md0 /mnt mount /dev/hd1a /mnt/boot chroot /mnt mkinitrd lilo Same result. I restored /boot/ with the files from version 2.6.4 did the same procedure again and was able to boot int the system. sure it complains with missing modules.... i restored boot to the version of 2.6.5 mkinitrd lilo same fault again. I stuck
raidautorun ?
could it be my problem ?
but how can i disable it at boot-time ?
----- Original Message -----
From: "Werner Penz"
Hi again, thanks to Anders Johansson we figured out that /dev/900 is my /dev/md0.
old-Kernel: 2.6.4-52-default (SuSe 9.1) /dev/hda1 = boot /dev/hda3 + /dev/hdb3 = /dev/md0 = / #(root)
After upgrading the Kernel with YOU to 2.6.5-7.--somthing the box no longer boots. the boot stops with the message: Waiting for device /dev/900.... not found !
I already did:
Rescue-System:
mount /dev/md0 /mnt mount /dev/hd1a /mnt/boot chroot /mnt mkinitrd lilo
Same result.
I restored /boot/ with the files from version 2.6.4 did the same procedure again and was able to boot int the system. sure it complains with missing modules.... i restored boot to the version of 2.6.5
mkinitrd lilo
same fault again. I stuck
-- Check the headers for your unsubscription address For additional commands, e-mail: suse-security-help@suse.com Security-related bug reports go to security@suse.de, not here
participants (1)
-
Werner Penz