From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.43) id 1DsmBR-0004LW-6H for garchives@archives.gentoo.org; Wed, 13 Jul 2005 18:42:13 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.4/8.13.4) with SMTP id j6DIeIZa016032; Wed, 13 Jul 2005 18:40:18 GMT Received: from smtp108.mail.sc5.yahoo.com (smtp108.mail.sc5.yahoo.com [66.163.170.6]) by robin.gentoo.org (8.13.4/8.13.4) with SMTP id j6DIafxg000218 for ; Wed, 13 Jul 2005 18:36:42 GMT Received: (qmail 56410 invoked from network); 13 Jul 2005 18:37:44 -0000 Received: from unknown (HELO ?192.168.50.105?) (richard?j?fish@212.180.33.26 with plain) by smtp108.mail.sc5.yahoo.com with SMTP; 13 Jul 2005 18:37:44 -0000 Message-ID: <42D56021.1030408@asmallpond.org> Date: Wed, 13 Jul 2005 20:40:33 +0200 From: Richard Fish User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050623) X-Accept-Language: en-us, en Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] problem with raid1: error while booting References: <42D3710F.7020305@gmx.net> <42D3DA38.206@serent.com> <42D3DDDE.7020805@gmx.net> <42D49631.8070406@gmx.net> <42D4A57F.4030304@asmallpond.org> <42D52089.8000901@gmx.net> In-Reply-To: <42D52089.8000901@gmx.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Archives-Salt: ad29a927-77c5-4af5-87b7-c8e40890f79a X-Archives-Hash: 405fce586f50dedd212ee72e877254d8 Jarry wrote: >> In the maintenance mode, does /sys/block/md0/* exist? What does "cat >> /proc/mdstat" report? > > Actually, if the kernel autodetection runs at boot time, /proc/mdstat should show the devices regardless of whether the device nodes exist or not....so something is a bit strange with your kernel configuration. Either you are missing a RAID driver in the kernel, or a necessary disk driver. Take a careful look at what "grep =m /usr/src/linux/.config" reports...something in there is almost certainly the problem! You can also follow my notes about creating an mdadm.conf file in another message (sorry for the multiple replies!). > It seems (or at least it is discussed there) that this (udev does not > create /dev/md* at startup) is some kernel-bug! If some of our kernel > developers is watching this list, could he confirm or refuse it? I don't know if I would call it a kernel bug. It is mostly just functionality that isn't clear where it belongs, and there is no obvious right thing to do. The autodetection feature of the MD driver came from a different era of kernel development, and would almost certainly not be accepted today. > Can I somehow get rid of udev, when it is causing problems to me? Well, you can always revert back to static device nodes. See the RC_DEVICES entry in /etc/conf.d/rc. If you set this, you will need to run a bunch of /sbin/MAKEDEV commands to get the static nodes created. If you do decide to go this route, I encourage you to consider it a temporary solution until you get the system up and running. -Richard -- gentoo-user@gentoo.org mailing list