| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Wed, 4 Jul 2007 22:54:25 +0200 From: "Kay Sievers" <kay.sievers@...y.org> To: "Ingo Freund" <linux-kernel-news@...ict.net> Cc: linux-kernel@...r.kernel.org Subject: Re: md device files missing at boot time On 7/4/07, Ingo Freund <linux-kernel-news@...ict.net> wrote: > one of the systems I'm working with was changed (copied) from single (scsi - sda1) > to multiple disk (raid1) (sdb1,sdc1 --> md0). > When I try to boot from the new created md-device it stops with: > ... > loading reiserfs > "Waiting for device /dev/md0 to appear: ........ not found -- Exiting to /bin/sh > > # ls -la /dev/md* > shows nothing, so I understand why the "/" cannot be mounted, but > where are the /dev/md* files (I found them in "/lib/udev/devices")? > > The kernel is vanilla 2.6.21.5, the (I think) needed hardware and filesystem > drivers are built in modules and put into an initrd file for loading at boot time. > > Does anyone have an idea what I might do wrong? How did you build the initramfs image? /sbin/mkinitrd? Did you add md support to the image? Kay - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists