Cirdan Posted July 24, 2019 Share Posted July 24, 2019 I'm trying to mount one of my shares in an Ubuntu 18.04 server VM. Unfortunately, adding it via fstab causes my system to go into emergency mode on each boot. My share (/mnt/user/hemlock) has been added to the VM with tag 'hemlock'. Running 'sudo mount -a' works correctly and shows no errors, and 'sudo mount -t 9p hemlock /home/<user>/hemlock' also works. However on boot up I consistently see this: Pressing Control-D and continuing seems to work anyway, but having that prompt is still an issue on a server. I cannot find anything related to mounting in 'journalctl -xb', but perhaps I am looking for the wrong thing. Here is my fstab entry: hemlock /home/<user>/hemlock 9p trans=virtio,version=9p2000.L,nobootwait,rw,_netdev 0 0 Thank you for any help, and please let me know if you need any other information. 1 Quote Link to comment
nowhere99 Posted October 6, 2019 Share Posted October 6, 2019 I see this is an older thread but I have the same exact issue and can't find any help on it yet. Anyone have any ideas? THX! Quote Link to comment
Woodpusherghd Posted October 8, 2019 Share Posted October 8, 2019 (edited) I had a similar problem. Here is a line from my fstab file. I'm running a ubuntu server 18.04 vm: Backup /mnt/Backup 9p noauto,x-systemd.automount,x-systemd.device-timeout=10,timeo=14,x-systemd.idle-timeout=0,trans=virtio,version=9p2000.L,_netdev,rw 0 0 Edited October 8, 2019 by Woodpusherghd 1 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.