The issue that I am having is that after adding my other internal drives to the fstab, sudo mount -a works until a reboot. After a reboot the drives simply fail to mount with the following error:
mount: /mnt/sdb: wrong fs type, bad option, bad superblock on /dev/sdc1, missing codepage or helper program, or other error.
mount: /mnt/sdc: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error.
After that, i run fsck on each drive which runs just fine, telling me the drives are clean.
Running sudo mount -a after this throws the same error.
If I mount them manually with the mount command, there are no errors or problems (running sudo mount -a after that works without throwing an error).
My fstab is setup thus:
GNU nano 4.8 /etc/fstab
# /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>
# / was on /dev/nvme0n1p2 during installation
UUID=11c43336-056e-4f34-9d50-360791b7d390 / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/nvme0n1p1 during installation
UUID=9F66-227D /boot/efi vfat umask=0077 0 1
/swapfile none swap sw 0 0
UUID=01D6EE21AA9E4980 /mnt/Jdrive ntfs rw,user,exec,umask=000 0 0
UUID=4e792db8-d367-48cc-9123-d4a4adf17f53 /mnt/sdb ext4 rw,user,exec,umask=000 0 0
UUID=f7ffba02-ab34-4aa3-8c6b-40be7aa23b19 /mnt/sdc ext4 rw,user,exec,umask=000 0 0
UUID=B460B09F60B06A2E /mnt/Seagate ntfs rw,user,exec,umask=000 0 0
Not sure if those options are the best ones, I was just going off of an article explaining how to setup fstab. Also, the two ntfs drives mount without issue or complaint every time, it's only the ext4 formatted drives that have a problem.
Why is this happening, am I making a simple newbie mistake?
