Search guides

Fix a disk that will not mount

We'll check the disk is visible, run fsck or xfs_repair, and fix fstab—or tell you when to escalate.

Troubleshooting · Servers & Linux
10–30 min
What you'll need
  • Root or sudo on the server
  • Console access if the system does not boot
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 disk is visible, run fsck or xfs_repair if corrupted, and fix fstab so the disk mounts.

  • Run lsblk and blkid to confirm the disk is present. Check dmesg for I/O or hardware errors. If the filesystem is corrupted, unmount and run fsck -y (ext4) or xfs_repair (XFS).
  • Check /etc/fstab: use UUID, correct type, mount point exists. Run mount -a to test.
  • Good: The disk mounts and is accessible.
  • Bad: dmesg shows hardware errors or fsck fails repeatedly—escalate.

Check disk and fsck

Goal: Confirm the disk is visible and repair the filesystem if corrupted.

  • Run lsblk and blkid. Check dmesg | tail -100 for errors. Unmount, then run fsck -y (ext4) or xfs_repair (XFS). Remount.
  • Confirm you should see fsck complete and the mount succeed.

Fix fstab and mount

Goal: Correct fstab and mount the disk.

  • Use UUID from blkid in fstab. Confirm type (ext4, xfs) and mount point. Run mkdir -p /path if needed. Run mount -a.
  • Confirm you should see no error from mount -a.

When to escalate

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

  • dmesg shows I/O or hardware errors and the disk may be failing.
  • fsck fails repeatedly or reports unrecoverable errors.
  • The disk is on SAN or iSCSI and unreachable.

Verification

  • mount shows the disk 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 disk visible lsblk; blkid.
  2. dmesg Check for I/O or hardware errors.
  3. fsck / xfs_repair umount; fsck -y or xfs_repair.
  4. fstab and mount UUID, type, mount point; mount -a.
  5. Escalate Provide lsblk, blkid, dmesg, fsck output.

What to capture if you need help

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

  • lsblk output
  • blkid output
  • dmesg excerpt
  • fsck or xfs_repair output
  • fstab entry
  • Steps already tried

Is the disk visible in lsblk?

Run lsblk and blkid.

Run `lsblk` and `blkid`. Not visible: check cabling, USB, SAN. Visible: proceed to fsck and fstab.

Yes No

You can change your answer later.

Disk not detected

Check cabling, USB, SAN/iSCSI. If hardware, escalate or replace disk.

Done

Does dmesg show I/O or hardware errors?

dmesg | tail or journalctl -k.

Run `dmesg | tail -100`. I/O error, medium error: disk may be failing—backup and replace. No errors: proceed to fsck.

Yes No

You can change your answer later.

Escalate

Hardware errors or disk not detected. Provide lsblk, blkid, dmesg. Consider disk replacement.

Done

Is the filesystem corrupted?

mount fails with filesystem error.

Unmount. Run fsck -y (ext4) or xfs_repair (XFS). Remount. If fsck fails repeatedly, escalate.
Question

fsck succeeded?

Continue

You can change your answer later.

Fix fstab and mount

Use UUID in fstab. Confirm type and mount point. mount -a.

Done

Reviewed by Blackbox Atlas

Frequently asked questions

Why would a disk not mount?
Filesystem corruption, wrong fstab entry, device not detected, I/O errors, or disk in use. Check lsblk, fsck, and dmesg.
Can I fix disk mount failures myself?
Yes. Run fsck or xfs_repair, fix fstab (UUID, type), create mount point. For hardware errors, replace the disk.
When should I escalate disk mount issues?
If fsck fails repeatedly, dmesg shows hardware errors, or the disk is on SAN/iSCSI and unreachable.

Rate this guide

Was this helpful?

Continue to