RE: [suse-security] Waiting for device /dev/900 to appear
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 experienced the same problem just recently. Part of my setup: /dev/md0 / reiserfs acl,user_xattr 1 1 /dev/md1 /boot reiserfs acl,user_xattr 1 2 /dev/md2 /home reiserfs acl,user_xattr 1 2 /dev/md3 /srv reiserfs acl,user_xattr 1 2 /dev/md4 /var reiserfs acl,user_xattr 1 2 I booted with the 9.1 boot cd and went to the update system option and accepted all of the default sections. Unfortunately I didn't pay attention to what packages it had to install. After I did this I still had the 2.6.5-7.95 kernel (at least that's what YAST says) but it works with no problems. I have no idea why this works... I'm just hoping that the info can help someone get past this problem. Andy Coleman
Just to be masochistic I decided to make a backup of the working 2.6.5-7.95 kernel and installed the kernel patch through YOU. For some reason now it's working perfectly. I'm guessing that the update system function I mentioned in my last post somehow fixed the problem. Added some notes below also. On Monday 12 July 2004 10:39 am, Andy Coleman wrote:
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 !
As a clarification I was running 9.1 w/the default kernel (2.6.4-2?) and experienced these problems when updating to the 2.6.5-7.95 kernel patch through YAST.
I experienced the same problem just recently. Part of my setup:
/dev/md0 / reiserfs acl,user_xattr 1 1 /dev/md1 /boot reiserfs acl,user_xattr 1 2 /dev/md2 /home reiserfs acl,user_xattr 1 2 /dev/md3 /srv reiserfs acl,user_xattr 1 2 /dev/md4 /var reiserfs acl,user_xattr 1 2
I booted with the 9.1 boot cd and went to the update system option and accepted all of the default sections. Unfortunately I didn't pay attention to what packages it had to install. After I did this I still had the 2.6.5-7.95 kernel (at least that's what YAST says) but it works with no problems.
I have no idea why this works... I'm just hoping that the info can help someone get past this problem.
Andy Coleman
Andy Coleman wrote:
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 experienced the same problem just recently. Part of my setup:
/dev/md0 / reiserfs acl,user_xattr 1 1 /dev/md1 /boot reiserfs acl,user_xattr 1 2 /dev/md2 /home reiserfs acl,user_xattr 1 2 /dev/md3 /srv reiserfs acl,user_xattr 1 2 /dev/md4 /var reiserfs acl,user_xattr 1 2
I booted with the 9.1 boot cd and went to the update system option and accepted all of the default sections. Unfortunately I didn't pay attention to what packages it had to install. After I did this I still had the 2.6.5-7.95 kernel (at least that's what YAST says) but it works with no problems.
I have no idea why this works... I'm just hoping that the info can help someone get past this problem.
Andy Coleman
I think the problem depends on a) new mdtools or b) on not supported drivers in 2.6.x kernels. For this purpose I use 2.4.x instead, even if this is the older kernel, but I don't have enough experience in 2.6.x kernels with software raid. Philippe
On Monday 12 July 2004 17:44, Philippe Vogel wrote:
I think the problem depends on a) new mdtools or b) on not supported drivers in 2.6.x kernels.
Nope, if you carefully follow this thread, you could discover, that the problem is due to some initrd updates, which is also fixed by the latest one: mkinitrd-1.0-199.50. Be careful with just guessing such things: there are way too many possibilities to fail!
For this purpose I use 2.4.x instead, even if this is the older kernel, but I don't have enough experience in 2.6.x kernels with software raid.
This also doesn't sound wise: if you don't like 2.6, stick with 9.0..
Philippe
Pete
participants (3)
-
Andy Coleman
-
Hans-Peter Jansen
-
Philippe Vogel