[opensuse] Opensuse doesn't wait long enough for the disks to spin up before trrying to configure raid
Hi. I have a Opensuse 11.0 system running as a server with about 18 data disks hooked to the local motherboard SATA ports, and 3 SATA port multipliers hooked to a Adaptec 1430SA controller. Because of how the PMP code works and how long it takes to spin up each disk, it can take awhile before the disks are all spun up and online. About half the time I boot the system, OpenSUSE thinks the disks are already up and proceeds to run the /etc/init.d/boot.md and boot.lvm files, which of course fail to assemble the disks because they haven't fully come online yet, and dumps me into a single-user mode shell to fix the disks. 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? Thanks, Mike -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Mike Myers pecked at the keyboard and wrote:
Hi. I have a Opensuse 11.0 system running as a server with about 18 data disks hooked to the local motherboard SATA ports, and 3 SATA port multipliers hooked to a Adaptec 1430SA controller. Because of how the PMP code works and how long it takes to spin up each disk, it can take awhile before the disks are all spun up and online. About half the time I boot the system, OpenSUSE thinks the disks are already up and proceeds to run the /etc/init.d/boot.md and boot.lvm files, which of course fail to assemble the disks because they haven't fully come online yet, and dumps me into a single-user mode shell to fix the disks.
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?
Thanks, Mike
There is a time delay at the boot screen that can be used to delay the boot process. timeout 8 Gives an 8 second delay, no reason you can't make it 30 to allow all of the disks to spin up. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
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
participants (3)
-
Anders Johansson
-
Ken Schneider
-
Mike Myers