April 25, 20197 yr I've been running a Ubuntu server 18.04 VM on Unraid 6.70 RC7. I've been backing up the VM weekly but have recently run into a problem with my latest backup. I was trying to change the cpu pining of my VM (with the my VM shut down) when I restarted, everything was borked. I tried booting my latest backup and it stopped after "Dependency failded for local file system." I successfully booted a previous backup but noticed my network interface changed (after running ip link) from enp9s0 to enp11s0. I edited network .conf and all was well. I also noted my couchpotato DB was corrupt (in root) and I deleted it as well. After updating the server using apt-get dist-upgrade i shut down and when I tried to reboot I received the same error. I've attached a screen shot of the boot screen. I booted several times with this backup but when I correct network.conf I have the same issue when I try to reboot. I am currently running the VM using the second to last backup but if I shut down, I'm sure I'll run into the same problem. Any suggestions on trouble shooting steps? Thanks. Edited April 28, 20197 yr by Woodpusherghd Solved
April 28, 20197 yr Author Turns out the culprit was my fstab file. Apparently some update to systemd caused a problem which was solved by adding the following code to my unRaid shares in fstab: noauto,x-systemd.automount,x-systemd.device-timeout=10,timeo=14,x-systemd.idle-timeout=0, Hope this helps others who my encounter this problem.
Archived
This topic is now archived and is closed to further replies.