They devices are being created. But what happens is the driver find the PMP, probes it, goes to the first port, tries to talk to the disk, finds it not ready, resets it (causing it to spin up), tries again, fails, tries again 5 secs later, finds it, tries the next port, same thing happens, resets the PMP, then probes the first port again, finds it ready, finds the 2nd port ready, then goes to the next port, resets it, etc... This can take quite awhile. It appears that the last PMP doesn't get probed and udev events triggered until some time after udevs from the 2nd and a1st PMP's are already created. So boot.md is already going, and after it more devices are being created. Sounds like if I change the mdadm device timeout to 2 mins or so, that may fix it... I'll try it and report back. If you want, I can post a dump of the tsratup log showing this behavior. As for starting the disks all at once, I don't think the liata architecture is set up to do that, and I think you really don't want it to. Starting up 20 disks at the same time will put quite a load on the +12V line of the PSU. Doing them one at a time means you need a much smaller PSU, so staggered spinup is the right thing to do I think. thx mike ----- Original Message ---- From: Anders Johansson To: opensuse@opensuse.org Sent: Saturday, August 30, 2008 12:33:54 PM Subject: Re: [opensuse] Opensuse doesn't wait long enough for the disks to spin up before trrying to configure raid On Saturday 30 August 2008 21:03:34 Mike Myers wrote:

The bottom line is about half the time I try to boot the system, it fails and needs some console work before I can bring it up. Does anyone know if there is a fixed time delay somewhere that waits for the disks to spin up or does it use a different way of telling if it's done?

I'm not sure what exactly is failing here. Once the disk identifies itself on the bus, a udev event causes the device node to get created. Does it get created? What exactly is the error message when boot.lvm fails to assemble the logical volumes? boot.md will wait 60 seconds for all udev events to get processed. Would it help to increase that (in /etc/sysconfig/mdadm, the value is MDADM_DEVICE_TIMEOUT)? Otherwise, you have to let us know exactly where in the chain things fail Anders -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org