Fixed, see below. 2014-07-29 0:22 GMT+02:00 Redalert Commander <[email protected]>: > Yet another thing I now stumbled upon with systemd (I really don't > mean to bash it, but now I'm getting tempted). I have a raid 10 BTRFS > array, and 1 drive failed, so I want to replace it. > I physically replaced the disk, but now I can't get past this next hurdle. > > Because of an entry about that array in /etc/fstab, systemd does not > proceed to boot properly. I get the 'recovery mode' dialog about > password and Ctr-D, but neither seems to work, so I can't edit fstab > to boot up further. It won't accept my password (worked fine 2 days > ago). > > Also, I don't get dropped into recovery mode when using the default > grub entry, but only with the 'recovery mode' entry. I do get the > 'Welcome to emergency mode' message, but nothing about Ctrl-D or the > root password. > > Any ideas besides booting from external boot media?
When specifying init=/bin/sh on the kernel command line in grub, I can boot into a shell, remount the root filesystem as rw (it's mounted ro when doing this), and edit /etc/fstab. After commenting out the array from fstab, systemd let me boot up normally so I can fix the array. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/CAMDu+mOTB_aZPXOffAw=k7gnddfunv3jef0tirkmshnqqmh...@mail.gmail.com
