[SOLVED] All personal files lost after reboot
by underscoreus from LinuxQuestions.org on (#4SG6D)
So, eh, yeah... Rough restart I guess you could say. I am running a Linux Mint 19.2 Cinnamon VM and just now after restarting the VM I notice that all my personal files are gone. All the programs I have installed seem to still be here but files are completely gone as far as I can tell. Everything works, no errors or seeming glitches, just the lack of all of the files and documents I had.
I haven't rebooted the VM in a while since its running on an Unraid box in my closet, but the last thing I did and the reason for the reboot was a small change to the /etc/fstab file. I edited the last line I have added myself to change where an Unraid share would mount. Incase there are questions here is the fstab file. As far as I know I have not done anything wrong in editing it, I've tried to be very careful in what I change and save to the file since I have heard that editing the wrong thing can cause bad shit (like this I guess) to happen.
Code:# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/mapper/mint--vg-root / ext4 errors=remount-ro 0 1
# /boot was on /dev/vda2 during installation
UUID=c9475bee-90df-4c3e-bd86-c0b71deaf15f /boot ext4 defaults 0 2
# /boot/efi was on /dev/vda1 during installation
UUID=EDFA-E436 /boot/efi vfat umask=0077 0 1
/dev/mapper/mint--vg-swap_1 none swap sw 0 0
//192.168.1.9/libraries /home/underscore cifs file_mode=0777,dir_mode=0777,username=temp,password=temp123 0 0What I can see though is that in the /etc/ folder there is both an fstab file and an fstab.save file. The fstab.save file has some changes I thought I had discarded. Before I do anything I wanted to ask people who probably know abit more than me about this, just so I don't break stuff more than I already have, if thats even possible, I haven't tried to restart the VM yet either.
Hopefully, I did not just nuke everything...
Thanks for the read, any comment is really appreciated.
I haven't rebooted the VM in a while since its running on an Unraid box in my closet, but the last thing I did and the reason for the reboot was a small change to the /etc/fstab file. I edited the last line I have added myself to change where an Unraid share would mount. Incase there are questions here is the fstab file. As far as I know I have not done anything wrong in editing it, I've tried to be very careful in what I change and save to the file since I have heard that editing the wrong thing can cause bad shit (like this I guess) to happen.
Code:# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/mapper/mint--vg-root / ext4 errors=remount-ro 0 1
# /boot was on /dev/vda2 during installation
UUID=c9475bee-90df-4c3e-bd86-c0b71deaf15f /boot ext4 defaults 0 2
# /boot/efi was on /dev/vda1 during installation
UUID=EDFA-E436 /boot/efi vfat umask=0077 0 1
/dev/mapper/mint--vg-swap_1 none swap sw 0 0
//192.168.1.9/libraries /home/underscore cifs file_mode=0777,dir_mode=0777,username=temp,password=temp123 0 0What I can see though is that in the /etc/ folder there is both an fstab file and an fstab.save file. The fstab.save file has some changes I thought I had discarded. Before I do anything I wanted to ask people who probably know abit more than me about this, just so I don't break stuff more than I already have, if thats even possible, I haven't tried to restart the VM yet either.
Hopefully, I did not just nuke everything...
Thanks for the read, any comment is really appreciated.