On Sat, 27 Feb 2016 10:01:21 +0100 "Mader, Alexander" <auma...@gmx.net> wrote: > On Fri, 26 Feb 2016 23:45:01 +0100 "Mader, Alexander" <auma...@gmx.net> > wrote: > > On Mon, 22 Feb 2016 18:19:58 +0000 Chris Boot <bo...@debian.org> 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? > 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.
Hello, I tried to trick the mount sequence by adding "_netdev" to the home volume. As a result the boot completed but the home directory was not available, anyway. The 1:30min pause in the boot sequence was there as well. The change in /etc/fstab: 8< ----------------------------------------------------------------- >8 # /home was on /dev/md0 during installation UUID=8e677927-d719-48eb-815d-d16170bdd003 /home xfs defaults,_netdev 0 2 8< ----------------------------------------------------------------- >8 Best regards, Alexander.