I recently replaced a secondary internal hard drive that died. The new one worked for several days and then suddenly I got an 'unable to mount hard drive' message when booting up. I wasn't able to mount it manually, so I reformatted it.
It seems to be working now, but I'm getting a confusing unable to mount/access hard drive message again when booting up. Only now if I press s to skip, the hard drive will actually be mounted correctly when it boots up. I set the options in the disks utility to mount it to /media/username/4TB_Storage
. Could a start-up script (like /etc/rc.local
or /etc/profile
) be trying to run before the drive is mounted? Is there a way to find out what is running when I get that start-up error?
sudo blkid
match those in the file/etc/fstab
.