Mounting External Backup Drive with Script

Use a Bash script to automatically mount an external backup drive by resolving its UUID to a device node and executing the mount command with appropriate options. This approach ensures reliable access regardless of device name changes, providing a robust solution for automated backup tasks in Linux environments.

Why Use UUIDs for Mounting?

In Linux, device names such as /dev/sdb1 or /dev/nvme0n1p2 are not persistent. They can change between reboots or when multiple drives are connected. The Universal Unique Identifier (UUID) is a stable label assigned to each filesystem. By using the UUID, your script remains functional even if the kernel assigns a different device path at boot time. This stability is critical for backup scripts that must run reliably without manual intervention.

Preparing the Environment

Before writing the script, you need two pieces of information: the UUID of your external drive and a local directory where it will be mounted. First, identify the UUID by running blkid or ls -l /dev/disk/by-uuid/. Look for the entry corresponding to your external drive's filesystem type, such as ext4 or ntfs-3g. Second, create a mount point directory using sudo mkdir -p /mnt/backup. Ensure the directory exists before attempting to mount, as the mount command will fail if the target path is missing.

Writing the Mount Script

The core logic involves finding the device associated with the UUID and then mounting it. Below is a robust script structure. It uses findmnt which is part of util-linux and is generally more reliable than parsing lsblk output for simple lookups.

#!/bin/bash

# Configuration
DRIVE_UUID="your-uuid-here"
MOUNT_POINT="/mnt/backup"

# Check if already mounted
if mountpoint -q "$MOUNT_POINT"; then
    echo "Drive is already mounted."
    exit 0
fi

# Find device from UUID
DEVICE=$(findmnt -n -o SOURCE -S "UUID=$DRIVE_UUID")

if [ -z "$DEVICE" ]; then
    echo "Error: Device with UUID $DRIVE_UUID not found."
    exit 1
fi

# Mount the drive
sudo mount -t auto "$DEVICE" "$MOUNT_POINT"

if [ $? -eq 0 ]; then
    echo "Successfully mounted $DEVICE on $MOUNT_POINT"
else
    echo "Failed to mount drive."
    exit 1
fi

This script first checks if the drive is already mounted to prevent errors. It then queries the system for the device source linked to the specific UUID. If the device is found, it proceeds to mount it. Using sudo within the script requires that the user has passwordless sudo privileges for this specific command, or you should run the script with elevated permissions directly.

Handling Permissions and Security

Running mount commands requires root privileges. Hardcoding passwords in scripts is insecure. Instead, configure /etc/sudoers to allow the specific user to run only the mount command without a password. Alternatively, use PolicyKit rules for desktop environments. For server environments, ensure the script runs under a service account with appropriate capabilities. Always validate the UUID input to prevent injection attacks if the UUID is derived from user input, though in most backup scenarios, it is hardcoded.

Automating with Cron

To make this process seamless, integrate the script into cron. Edit the crontab with crontab -e and add a line to execute the script at desired intervals. For example, to check and mount every hour:

0 * * * * /path/to/mount_backup.sh >> /var/log/backup_mount.log 2>&1

Logging output to a file helps diagnose issues if the mount fails unexpectedly. You can also use systemd timers for more complex scheduling requirements. This automation ensures your backup drive is ready whenever needed, reducing administrative overhead.

Troubleshooting Common Issues

If the script fails, check the following. First, verify the UUID is correct using blkid. Second, ensure the filesystem driver is installed; for NTFS drives, install ntfs-3g. Third, check kernel logs with dmesg | tail for hardware errors. If the drive is detected but not mounting, try manually running the mount command with verbose output to see specific error messages. Also, ensure no other process is holding the device open, which can cause "device busy" errors.

For related scripting techniques, you might find Understanding Background Script Execution using nohup on Ubuntu Server useful for managing long-running backup processes. Additionally, Understanding Window Specific URL Curl Output with Bash offers insights into handling external data streams, which can be complementary when fetching metadata for backups.

Frequently Asked Questions

How do I unmount the drive safely via script?

Use the umount command followed by the mount point or device name. Before unmounting, ensure all write operations are complete by syncing disks with sync. If the device is busy, use lsof +D /mnt/backup to find and close any open files.

Can I mount the drive read-only for safety?

Yes, add the -o ro option to the mount command. This prevents accidental writes to the backup drive, which is useful for verifying backup integrity or protecting against ransomware. Syntax: sudo mount -o ro "$DEVICE" "$MOUNT_POINT".

What if the UUID changes after formatting?

Formatting a drive generates a new UUID. Your script will fail because the old UUID no longer exists. Update the DRIVE_UUID variable in your script after reformatting. Always verify the new UUID with blkid before updating the configuration.

How do I handle multiple drives with similar names?

Always rely on UUIDs rather than device names like sdb1. UUIDs are unique across all storage devices. Even if you plug in multiple identical drives, their UUIDs will differ, ensuring the script targets the correct physical disk.

Is it safe to leave the drive mounted permanently?

Leaving a drive mounted continuously increases wear on spinning disks and consumes power. For portable drives, consider automating unmounting after a period of inactivity. Use autofs for on-demand mounting, which mounts the drive only when accessed and unmounts it after a timeout.