Hi Moshe, On Mon, May 23, 2005 at 07:51:29AM -0500, Moshe Yudkowsky wrote: > Package: mdadm > Version: 1.9.0-2.3 > Severity: critical > Justification: breaks the whole system > > After moving to the latest version of mdadm, and kernel 2.6.11-1-k7 > (2.6.11-5), I was unable to reboot my system. I was able to fix this > problem by changing the symbols I use to represent my RAID arrays.
> There's been a problem with mdadm for some time. Although I used the > symbols "/dev/md[1-3]" in my /etc/fstab and in /etc/lilo.conf and in > /etc/mdadm/mdadm.conf to configure my RAID arrays, the command in > /boot/initrd.img-<version>/script uses the format "mdadm -A /dev/md/[1-3]" > instead. > After the move to the latest mdadm, kernel , and initrd-tools (0.80.0) I > attempted to reboot and could not do so. The md/3 device would not start, > reiserfs couldn't pass the check, and the system hangs until I intervene. > Once I figured out that the /dev/md3 was not starting at all (and that > reiserfs was reporting, incorrectly, a superblock problem) I was able to > start this device manually. Howver, and this seems to be the crux of the > problem, I can't use "mdadm --assemble /dev/md/3" to start the array if I > use the notation "/dev/md3" in the mdadm.conf file. > After some further fiddling around, I decided to change lilo.conf, > mdadm.conf, and fstab to all use the form "/dev/md/[1-3]". When I made this > change, I was able to reboot without any problems. > So... this seems to be an error in how mdadm configuration works, a > mismatch between the command that generates the "mdadm -A" command that > goes into the system startup and the contents of the conf file. What > changed in the most recent version of mdadm isn't clear to me, but I have > my work-around. > What's suprising is that even after I've changed the mdadm.conf file to > read /dev/md/[1-3], the command "mdadm --examine" still produces output in > the form /dev/md[1-3]. I'm finding your report quite puzzling, to be honest. A few questions: Are you running udev on /dev? What was the last version of mdadm you had installed that worked? You mention initrd-tools -- is your root fs on RAID? If so, which device is it? Did you also upgrade initrd-tools and mdadm at the same time? Thanks, -- Steve Langasek postmodern programmer
signature.asc
Description: Digital signature
