On Wed, 2004-12-22 at 01:23 -0800, Marc Singer wrote: > On Wed, Dec 22, 2004 at 03:39:32PM +0900, Horms wrote: > > I took a breif look at initrd and for reference have included > > how it handles mdadm below. I think that the important bit > > is that it passes not only the md device but its component > > devices to mdadm -A (--assemble). It seems to me that as your > > invocation does not do that, it is going into a code path > > in mdadm that has a bug in it and thus segfaults. In a nutshell, > > I don't think it is a kernel problem. > > Adding the UUID to the mdadm command line allows MD to assemble the > raid. So, that answers the question "why doesn't mdadm assembled once > the machine is booted." > > Now, the question is this: with the md and raid modules added to the > initrd, why doesn't initrd find and start the raid array? I have an outstanding bug with this same issue. Except, I used udevd, it wasn't creating the /dev nodes soon enough. I had to revert to non-udevd /dev. This solved the mounting problems after the initrd mounted the root fs, which all md (mirrored). with udev, mdadm could not find anything except /. The following is what I have working beautifully. greg@asbestos:~$ df Filesystem Size Used Avail Use% Mounted on /dev/md1 1.9G 60M 1.9G 4% / tmpfs 475M 0 475M 0% /dev/shm /dev/md0 139M 4.6M 134M 4% /boot /dev/md4 9.6G 18M 9.6G 1% /home /dev/md3 972M 656K 972M 1% /tmp /dev/md5 15G 179M 15G 2% /usr /dev/md2 9.6G 239M 9.3G 3% /var Dunno if it is related. -- greg, greg@gregfolkert.net The technology that is Stronger, better, faster: Linux
Attachment:
signature.asc
Description: This is a digitally signed message part