You are not logged in.
Virtualbox shares require modules in [community]/virtualbox-guest-modules-lts which are not always built against the most recent kernel in the repos.[1,2] Systemd treats the error of the mount's inaccessibility as critical and stops the normal boot up entering emergency mode. Is there a more intelligent way I can define a share-mount in my vbox such that it will fail silently or at least boot the system for ssh access?
I have tried both of these /etc/fstab configurations, but each ends in the emergency mode drop if the modules are bad:
Config 1:
data-vbox /mnt/data vboxsf uid=1000,gid=100 0 0
Config 2:
data-vbox /mnt/data vboxsf,noauto,x-systemd.automount uid=1000,gid=100 0 0
1. https://bugs.archlinux.org/task/38097
2. https://bugs.archlinux.org/task/38247
EDIT: A typo in config 2 kept me from finding my own answer. The line works when composed correctly:
data-vbox /mnt/data vboxsf noauto,x-systemd.automount,uid=1000,gid=100 0 0
Last edited by graysky (2013-12-23 15:05:22)
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
Have you tried it with this :
data-vbox /mnt/data vboxsf noauto uid=1000,gid=100 0 0
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
@Lone - Yes, but that drops to an emergency shell at boot as well (added a comma between vboxsf and noauto).
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
I'm assuming these are fstab entries (Edit: I should've looked harder, you said as much in the first post), in which case the comma should go on the other side of noauto, it's a mount option, not an filesystem type. This mistake is present in your first config example too, which is possibly why that's not working either.
Last edited by WorMzy (2013-12-23 14:48:39)
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
<HEADSMACK> You're right. I will edit my first post. Thanks.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
Adding the nofail option is the general solution to this problem, but maybe I'm missing something...
But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner
Offline