I'm having some trouble with my home server's hard drive. I set up an enclosure connected to my mini PC via USB, but it keeps disconnecting randomly, which causes it to change its mount point. To fix this, I tried mounting the HDD using its UUID in the fstab file. I edited my /etc/fstab to include a line for the HDD so it could mount properly. After making changes, running `sudo mount -a` seemed to have messed things up. Now, when I check the new mount point, it's empty, and the old mount point is giving me an input/output error. I rebooted my server, and while some data shows up in the old spot, the new mount is still empty. What can I do to fix this?
3 Answers
It sounds like the `mount -a` command is trying to mount everything in your fstab, but it's possible that the filesystem on your HDD isn’t recognized properly or mounted at multiple points. Check your /etc/fstab again to ensure there aren’t conflicting mount points. You may want to unmount the old point first and then remount it using the new one after confirming the settings are correct!
Rebooting usually helps but might not be enough if there are outdated references in fstab. Make sure your fstab entry for the server HDD is correct. Also, did you create the directory /media/devmon/serverhdd? Sometimes, if that directory doesn't exist, the mount won’t work, leading to it showing up as empty. You should also verify that the filesystem type is indeed ext4 as specified.
When you run into issues like this, a good approach is to validate with `lsblk` and `blkid` after your changes. It indicates which devices are active and their mount points. If the HDD is still showing as read-only after rebooting, there could be a deeper issue. You might need to check dmesg for any kernel messages regarding the HDD that might indicate problems.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures