On Sat, 16 May 2009 16:01:10 +0200 Maximilian Bräutigam <max-br...@gmx.de> wrote:
> all of your mentioned options are enabled (since genkernel and me did > it). > > i copied all data to another partition /dev/sdb9 and disabled initrd. by > the way, i think that initrd was running, because all the scans after > executing the initrd ran without problems. despite, i disabled it and > got a kernel panic, like: > > """ > [md] scanned 0 and added 0 > ... > VFS: cannot open root device "sdb9" or unknown block(0,0) > please append correct "root=" > ... > Kernel panic - not syncing: VFS: unable to mount root fs on > unknown-block(0,0) > """ I think there should also be a list of detected partitions (if any). > i don't know how to handel this error, since my grub entry is correct > (or not?): > > """ > title Gentoo Linux x86_64-2.6.28-5 (no initrd) (on /dev/sdb9) > root (hd1,8) > kernel /boot/kernel-genkernel-x86_64-2.6.28-gentoo-r5 > root=/dev/sdb9 > """ Looks correct to me. "kernel /vmlinuz root=/dev/md0" works fine in my case with RAID1 and posted above settings, nearly all the other device drivers are modular. Prehaps it's just some weird version-hardware compatibility issue or build problem, although I believe it's quite rare with disk / fs drivers, so you must be doing something wrong. Try stopping the system boot as soon as possible using "I" key, exiting to shell, and look at the output of "lsmod". It should list the stuff you have loaded as modules, which were probably loaded from initrd (since the system won't boot w/o it), so you can try either compiling the relevant ones in or dropping them from initrd to see if the system can boot (yeah, sounds crazy, but it might be just simplier ;) With some luck, there might be something critical you've just managed to miss, easily detectable at the first glance. -- Mike Kazantsev // fraggod.net
signature.asc
Description: PGP signature