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: Thu, 05 Jul 2007 11:16:12 +0200 From: Ingo Freund <linux-kernel-news@...ict.net> To: linux-kernel@...r.kernel.org Subject: Re: md device files missing at boot time Hi folks, I could temporarily only read your answers in archives. Thank you for your reaction. Hopefully this answer doesn't break the thread. If it does: sorry for it, there were some mail mail problems which stopped our server receiving mails from this list and the list auto-unsubscribed me and stopped sending mails :-( But it is all fixed now. @Kay How did you build the initramfs image? /sbin/mkinitrd? Did you add md support to the image? Both "Yes". included modules are (in opensuses /etc/sysconfig/kernel: INITRD_MODULES="raid1 md reiserfs sym53c8xx pata_serverworks edd" @J.A. Magallon yes the partitions in question are all typed "fd" neither all-drivers-compiled-into-the-kernel nor the module using version work. The only difference I find is the exit to an emergency shell when using modules via initrd while the "only kernel version" stops commentless when it is time to use /dev/md0 for the first time. "dmesg" is not found after exiting to the shell. I can only post the content of a log file which was written into the initramfs (which seems to be also a trace of the in and output of the emergency console). Content of the log file (/var/log/boot.msg): Boot logging started on /dev/tty1(/dev/console) at Thu Jul 5 06:36:35 2007 Creating device nodes with udev Loading md-mod Loading raid1 Loading sym53c8xx Loading libata Loading pata_serverworks Loading edd Loading reiserfs Waiting for device /dev/md0 to appear: ..............................not found -- exiting to /bin/sh sh: no job control in this shell $ dmesg sh: dmesg: command not found $ fdisk sh: fdisk: command not found $ ls /bin bash cat chmod date ipconfig.sh ln ls mkdir mknod mount pidof rm run-init sed sh sleep true umount ... Question: is the order "creating dev nodes with udev" and after that "loading the modules" correct? Thanks - Ingo. - 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