Search guides

Fix a mount that will not work

We'll check the device exists, fstab syntax, mount point, and fsck when needed—or tell you when to escalate.

Troubleshooting · Servers & Linux
10–25 min
What you'll need
  • Root or sudo on the server
  • Console access if the system does not boot due to fstab
Step 1 of 6

Quick triage — pick your path

Get started

Choose the option that matches what you see. You can jump straight to that section.

Show full guide

Steps

Goal: Confirm the device exists, check fstab syntax, create the mount point, and run fsck if the filesystem is corrupted.

  • Run lsblk and blkid to confirm the device exists and get its UUID. Check /etc/fstab for correct device (use UUID), mount point, and type.
  • Create the mount point with mkdir -p /path if missing. Run mount -a to test. If mount fails with filesystem errors, unmount and run fsck -y (or xfs_repair for XFS).
  • Good: mount -a succeeds and the filesystem is accessible.
  • Bad: Device is on SAN/iSCSI and unreachable—escalate.

Check device and fstab

Goal: Confirm the device exists and fstab has correct syntax.

  • Run lsblk and blkid. Use UUID in fstab for stability. Check type (ext4, xfs) matches blkid. Run mount -a to test.
  • Confirm you should see no error from mount -a.

Fix filesystem

Goal: Run fsck when the filesystem is corrupted.

  • Unmount with sudo umount /path. Run sudo fsck -y /dev/sdXN (ext4) or sudo xfs_repair /dev/sdXN (XFS). Remount with mount -a.
  • Confirm you should see fsck complete and the mount succeed.

When to escalate

Gather lsblk, fstab, blkid, and dmesg output before escalating. Escalate if:

  • The device is on SAN or iSCSI and you cannot access it.
  • fsck fails repeatedly or reports unrecoverable errors.

Verification

  • mount shows the filesystem mounted at the correct path.
  • df -h shows the filesystem with available space.
  • Files can be read and written on the mount.

Escalation ladder

Work from the device outward. Stop when the problem is fixed.

  1. Confirm device exists lsblk; blkid.
  2. fstab syntax Check UUID, type, mount point; mount -a.
  3. Mount point mkdir -p; confirm empty.
  4. fsck umount; fsck -y or xfs_repair.
  5. Escalate Provide lsblk, fstab, blkid, dmesg.

What to capture if you need help

Before calling support or posting for help, have these ready. It speeds everything up.

  • lsblk output
  • fstab contents
  • blkid output
  • dmesg or journalctl -k excerpt
  • Steps already tried

Does the device exist?

Run lsblk and blkid.

Run `lsblk` and `blkid`. Missing device: check if it is on SAN/iSCSI; escalate if unreachable. Wrong device name: use UUID in fstab.

Yes No

You can change your answer later.

Device missing

Check cabling, SAN, iSCSI. If local disk, check if it appears after reboot. Escalate if SAN/iSCSI unreachable.

Done

Is fstab syntax correct?

device, mount point, type, options.

Check UUID, mount point exists, type matches blkid. Run `mount -a` to test. Fix any syntax error.

Yes No

You can change your answer later.

Fix fstab

Use UUID= from blkid. Confirm type (ext4, xfs). Create mount point with mkdir -p. Run mount -a.

Done

Does mount point exist and is it empty?

Mount point must be a directory.

mkdir -p /path. Confirm directory is empty. If mount fails with "not a directory", fix the path.
Question

Mount point OK?

Continue

You can change your answer later.

Does mount fail with filesystem errors?

dmesg may show I/O or filesystem errors.

If mount reports corruption: umount, run fsck -y (or xfs_repair for XFS). Remount. If fsck fails repeatedly, escalate.

Done

Reviewed by Blackbox Atlas

Frequently asked questions

Why would a mount fail?
Device does not exist, wrong fstab syntax, mount point missing or not empty, filesystem corruption, or wrong filesystem type. Check lsblk, fstab, and dmesg.
Can I fix mount failures myself?
Yes. Fix fstab (UUID, type, options), create mount point, run fsck if corrupted. Use mount -a to test after editing fstab.
When should I escalate mount issues?
If the device is on a SAN or iSCSI and you cannot access it, or the filesystem is severely corrupted and fsck fails.

Rate this guide

Was this helpful?

Continue to