Am 27.02.2016 um 10:01 schrieb Mader, Alexander: > On Fri, 26 Feb 2016 23:45:01 +0100 "Mader, Alexander" wrote: >> On Mon, 22 Feb 2016 18:19:58 +0000 Chris Boot wrote: >>> Adding "rootdelay=15" to the kernel command-line probably fixes this >>> (can't test as we can't just reboot this production server at will) but >>> this isn't a nice fix. >> I just tried "rootdelay=15" as well as "rootdelay=30" to no avail. For >> this I entered the extended boot options in GRUB2, used "e" to edit the >> parameter section, and inserted as second line the rootdelay. Should I >> rather edit the /etc/default/grub? > > Hello, > > I just tried booting with /etc/default/grub edited, but it does not > help; presumably because root is not my problem but home. Is there > something similar for other partitions but root? As you might have > noticed, I am quiet flexible with reboot experiments for testing something. > > The entries in /etc/default/grub: > > 8< ----------------------------------------------------------------- >8 > GRUB_DEFAULT=0 > GRUB_TIMEOUT=5 > GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` > GRUB_CMDLINE_LINUX_DEFAULT="quiet" > GRUB_CMDLINE_LINUX="rootdelay=15" > 8< ----------------------------------------------------------------- >8 > > After update-grub ...
Am 10.03.2016 um 15:57 schrieb Samuel Thibault: > Samuel Thibault, on Thu 10 Mar 2016 14:45:20 +0100, wrote: >> Dmitry Smirnov, on Mon 29 Feb 2016 18:46:10 +1100, wrote: >>> I tried adding "rootdelay=4" to kernel boot parameters but it did not help. >> >> I had tried rootdelay=15, it didn't help me either. > > Ok, I had to increase that to 45 seconds to get it working automatically. Hello, I tried that 45s delay as well using the GRUB edit and it just added a long delay before starting anything, but the manual assembly of md0 was still necessary. Best regards, Alexander.
