During the CU179 Testing the problem I found was related to LVM volumes. For those, as there is a workaround of adding the info into fstab, it was decided to leave fixing LVM on ExtraHD until after CU179 was released.
@jon then flagged up that some usb sticks were not showing up and it was identified that slow USB sticks were not getting correctly mounted at boot. A commit was done to fix that, at the start of last week, and there has been no feedback since then of further issues so the CU179 Testing has been released today.
I would think you can also add a line for it into fstab. However, I would suggest not using sda nomenclature but the UUID in case adding or removing drives causes the drives to be renamed differently. The UUID is unique for each drive and I have been using those for all my fstab definitions for the last 4 years or so rather than /dev/sda1 etc
For example, if the UUID is 1234-ABCD and you want to mount it at /mnt/mydisk with ext4 filesystem:
UUID=1234-ABCD /mnt/mydisk ext4 defaults 0 0
Save the file and exit the text editor.
Create the mount point directory if it doesn’t exist:
mkdir -p /mnt/mydisk
Mount the filesystem to verify:
The fstab entry ensures that the disk is mounted at boot or when you run mount -a. The defaults option refers to the default mount options, and 0 0 at the end are for dump and filesystem check options, which are generally safe to leave as zero.
The dump and pass (also called “check”) are the fifth and sixth fields in the /etc/fstab entry, respectively.
Dump: The dump field is used by the dump utility to decide if a filesystem should be backed up. If the value is 0, the dump utility will ignore the filesystem. If the value is set to 1, it will be included in the backup. dump is not commonly used these days, so this field is usually set to 0.
Pass (Check): The pass field specifies the order in which the fsck utility will check the filesystems at boot time. The root filesystem should have this set to 1, and other filesystems you want to be checked should be set to 2. If this is set to 0, fsck will not check the filesystem. It’s advisable to set the root filesystem to 1 and any additional filesystems to 2 to ensure they’re checked at boot, though not simultaneously, which could slow down the boot process.
In most cases, for additional disks and partitions, setting both dump and pass to 0 is acceptable, which means no backup and no check at boot.
A small note, usually noatime is interpreted as both “no last access time” for files and directories as nodiratime is supposed to be used only if noatime is missing, but I usually add both just in case, as I never found a problem with this redundancy.