Make devices and network shares mount automatically and reliably at boot. 16.11.2025 | reading time: 2 min Want a disk or network share to appear automatically after every reboot? This short guide shows how to add robust entries to "/etc/fstab" so devices mount reliably at boot and how to test changes safely from the shell. Hands-on example: mount a data disk Follow these commands to find a device, add it to fstab, and verify the mount; do not run them blindly on production systems: ```bash $ lsblk -f NAME FSTYPE LABEL UUID MOUNTPOINT sdb1 ext4 b6a3f2c3-8d2b-4a1e-9e6c-123456789abc $ sudo blkid /dev/sdb1 /dev/sdb1: UUID="b6a3f2c3-8d2b-4a1e-9e6c-123456789abc" TYPE="ext4" # Edit /etc/fstab and add the line below: UUID=b6a3f2c3-8d2b-4a1e-9e6c-123456789abc /data ext4 defaults,noatime 0 2 $ sudo mkdir -p /data $ sudo mount -a $ mount | grep /data /dev/sdb1 on /data type ext4 (rw,noatime) ``` Options that prevent boot problems Use UUIDs instead of "/dev/sdX" to avoid device renumbering, and add options like "nofail" to skip missing devices, "_netdev" for network filesystems, or "x-systemd.automount" to defer mounts until first access; choose the dump and fsck fields (the last two numbers) according to whether the filesystem should be checked at boot. When fstab is not enough For dynamic or per-user mounts consider systemd mount units, autofs, or per-session tools; always test fstab edits with "sudo mount -a" and inspect with "findmnt" or "mount" before rebooting to avoid getting dropped to an emergency shell. Next steps and certification Start by practicing on a VM, experiment with NFS and vfat options (uid/gid for ownership), and then explore automounting and systemd mount units for advanced scenarios; deepen system knowledge and consider pursuing CompTIA Linux+ or LPIC-1 with intensive exam preparation at bitsandbytes.academy to turn hands-on skill into certified expertise. Join Bits & Bytes Academy First class LINUX exam preparation. setup filesystem storage boot-process backup utilities
