≡ Menu

Repairing Linux ext2 or ext3 or ext4 File System [ fsck ]

Linux comes with the system utility fsck (“file system check”) for checking the consistency of a file system. This quick post explains how to use fsck to fix error.

The syntax is as follows to check and optionally repair one or more Linux file systems:

fsck Fs-Name-Here
fsck /dev/xyz
fsck /home
fsck.ext3 /dev/hdc1
fsck.ext2 /dev/flash/device/name

Fs-Name-Here can be one of the following

  1. A device name (e.g. /dev/hda1, /dev/sda2, /dev/md0, /dev/vg1/volume_1)
  2. A mount point (e.g. /var, /home)
  3. An ext2 label (e.g. LABEL=home )
  4. UUID specifier (e.g. UUID=8868abf6-88c5-4a83-98b8-bfc24057f7bd)


First, a file system must be unmounted. You cannot repair it while it is running. Take system down to runlevel one (make sure you run all command as root user):
# init 1

Next, unmount file system, for example if it is /home (/dev/sda3) file system then type command:
# umount /home
# umount /dev/sda3

Finally, run fsck on the partition, enter:
# fsck /dev/sda3
However be sure to specify the file system type using -t option. Recently, one of our sys admin run the command on ext3 file system w/o specifying file system. Result was more corruption as fsck by default assumes ext2 file system:
# fsck -t ext3 /dev/sda3
# fsck.ext3 /dev/sda3
# fsck.ext4 /dev/sda5
If you do not know your file system type then typing mount command will display file system type.
$ mount
Sample outputs:

/dev/root on / type ext4 (rw,relatime,barrier=0,journal_checksum,data=ordered)
/tmp on /tmp type tmpfs (0)
none on /dev/pts type devpts (gid=4,mode=620)
/sys on /sys type sysfs (0)
/proc/bus/usb on /proc/bus/usb type usbfs (0)
/dev/vg1/volume_1 on /volume1 type ext4 (usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,synoacl)
/volume1/@optware on /opt type bind (bind)
none on /proc/fs/nfsd type nfsd (0)

fsck will check the file system and ask which problems should be fixed or corrected. If you don’t want to type ‘y’ every time then you can pass -y option to fsck:
# fsck -y /dev/sda3
Please not if any files are recovered then they are placed in /home/lost+found directory by fsck command.

Don’t execute, just show what would be done:
# fsck -N /dev/sda3

Once fsck finished, remount the file system:
# mount /home

Go to multiuser mode, enter:
# init 3
Read man page of fsck for more information. Make sure you replace /dev/sda3 with your actual device name:
$ man fsck

Page last updated at 9:58 PM, April 10, 2012.

Share this on:

Your support makes a big difference:
I have a small favor to ask. More people are reading the nixCraft. Many of you block advertising which is your right, and advertising revenues are not sufficient to cover my operating costs. So you can see why I need to ask for your help. The nixCraft, takes a lot of my time and hard work to produce. If you use nixCraft, who likes it, helps me with donations:
Become a Supporter →    Make a contribution via Paypal/Bitcoin →   

Don't Miss Any Linux and Unix Tips

Get nixCraft in your inbox. It's free:

{ 22 comments… add one }
  • Anonymous October 17, 2005, 2:20 am

    simple and effective :) good pice of work

  • Anonymous October 17, 2005, 7:50 pm

    can I try same commands on HP/UX?

  • LinuxTitli October 18, 2005, 12:32 am

    Commands are same but syntax changes.

    To repair HFS file system (/home)

    umount /home
    fsck –F hfs /dev/vg00/lvo1
    mount /home

    To repair JFS file system (/home)
    umount /home
    fsck –F vxfs /dev/vg00/lvo14
    mount /home

    Replace /dev/XXX/YYY with actual device file.

    • Michael November 8, 2011, 4:14 pm

      To repair a file system in HPUX

      # fsck -F vxfs -y -o full /dev/vg##/lvol#
      # fsck -F vxfs -o full -y /mount_pt

      Note: The HFS file system has been obsoleted in HP-UX since version 10, except for the /stand file system which contains the kernel, and you’re not going to unmount the kernel and run a file system check. Instead, get to single user. Here is one way:

      # reboot
      # interact with IPL . yes
      ISL>hpux -is

      And as the kernel is loaded vg00 will be enabled and automatically checked for corruption.

      # init 2, same thing, automatically check run level 2
      # init 3, same thing, automatically check run level 3, multiprocessor mode. The system is up.

      NEVER! fsck /stand – The only hfs file system for over a decade is /stand, and you never fsck /stand!

  • Anonymous October 18, 2005, 11:25 pm

    thanks for HP/UX JFS repair commands :)

  • General Zod October 27, 2006, 5:16 pm

    Concise, very effecive and to the point. Just what was required.

  • General Zod October 27, 2006, 5:17 pm

    excllent work

  • Jm December 4, 2006, 3:05 am

    What about to recover data that are deleted?
    Thanks anyway… :)


  • Lusidvicel December 18, 2006, 5:50 pm

    Hello, i love http://www.cyberciti.biz! Let me in, please :)

  • Owain March 3, 2007, 10:03 pm

    Thankyou – this page saved my life! (well, not literally). After checking loads of links that just told me what it said in the man page, here was a quick, easy and practical way to use the command.

  • jack June 10, 2007, 4:50 pm

    How do you check the / partition – which cannot be unmounted since it still shows as “in use” after going to run level 1? Is there a way without rebooting?

  • Paolo July 14, 2008, 12:38 pm

    Thanks, very good guide!

  • herson December 11, 2008, 4:32 am

    @Jack, I think that’s when you need to use a rescue disk. Most of the distros have this on their installation media.

  • Chris December 24, 2008, 9:10 am

    How do you find out what the actual device name is?

  • markthecarp January 28, 2009, 2:00 pm

    This post is over two years old but still relevant today.

    I just used most of the steps described here to repair an ext3 partition on my Ubuntu desktop system. Only difference being I did not do “init 1”. I logged out to the gdm screen then did Ctl-Alt-F2 to get to a virtual console. I logged into the system and ran the commands with the exception of “init 1”.

    Thanks for a very helpful and concise article.

  • tuxsun1 August 3, 2009, 10:13 pm

    Excellent article!!
    Is there a way to do this via SSH?
    What methods do you recommend for listing the mounted file systems?

  • bsuresh November 3, 2009, 7:07 am

    system not booting.because new root user created last time,not come guimode .so restart that p.c .not booting asked password or alt ctrl d.so i gave that password .system restarted.what will i do?lasttime i worked that pc du /dev/hdc6 .but i don’t know about this cmd.may be reason is there

  • MRPOST February 12, 2011, 12:17 am

    Hi I am getting following mesage:
    Repair File system 1#
    I don’t know what to do now.
    Beofore this it is saying file system corrupted. Anybody please help help….

  • Jan Girke May 19, 2011, 1:12 pm

    Don’t try that on Ubuntu 10.04.
    It will just shut down the system.

  • Sk. Shahin Rahman December 4, 2011, 7:28 am

    Thanks a lot for this helpful article

  • Isaiah September 25, 2012, 6:52 am

    Thanks for telling me to check for the filesystem of giving me the command. I should of read ahead but I was executing commands in order.

  • Miguel Angel Diaz September 30, 2015, 2:58 am

    checking filesystems fsck.ext3: Unable to resolve LABEL=/ lo solucione cambiando de posición el disco en el cable de datos de la PC.

Leave a Comment

   Tagged with: , , , , , , , , , , , , , , , ,