On 3/28/07, Ian Jackson <[EMAIL PROTECTED]> wrote: > > Every hard drive has a very similar partitionning scheme: > > * boot partition (two installs, each has a backup of its main > > "/boot", not exactly up to date as I have been too lazy to write a > > small script) > > * swap partition or small temporary data partition > > sd?1 and sd?2 respectively, I take it ?
yes sd?1 are boot partitions and sd?2 swap/other > Do you recall in what state the md0 raid came up ? The symptom as I > understand it is that it came up degraded ? Looking at the log, the > disks were found in the order sda3 sdd3 sdb3 sdc3 so if it came up > degraded was sdc3 missing ? With older versions (of mdadm I think) the RAID was assembled, but degraded or kind of assembled but not startable (when only 1 or 2 disk were present at first). a "--no-degraded" option was added in the mdadm script to avoid this. Now the RAID does not try to start when drive(s) are missing (i.e. is never assembled in degraded mode) but weird things are still hapening. I do not recall which devices were in the "assembled" array when I launched this one, but the RAID was _not_ degraded. But I guess you have it right: I had sometime enough time to see in /proc/partition only a few of my drives, and the array was assembled with these. Once all the devices are there, runing /scripts/local-top/mdadm again fixes it all. > > And the LVM works properly now ? after running udevd and udevtrigger, I checked that things were well broken (it works too fine in my two first attempts) and then all I had to do is running "/scripts/local-top/mdadm" once more and the array was correctly assembled. I have not started LVM by hand, I copied the udevd.out to one of my normal partition, then exited the shell and it finished to boot fine. One more comment: I have tested some other suggested workarround: - removing the mdrun script did not help (the first thing done by this script is to check the presence of the mdadm one and then to exit) - adding a timeout in "/usr/share/initramfs-tools/init" works fine for me: 5 seconds are not enough but 8 are OK ;) -- aurelien naldi -- boot-time race condition initializing md https://launchpad.net/bugs/75681 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
