Running fsck in CentOS 5 [StartupCTO]

Last Updated: 27 Jun 2023

|

Author: dordal

Page locked

This page is currently locked for editing by another user. You have to wait until this user finishes editing or the lock expires.

Currently locked by: 178.20.44.140
Lock expires at: Jun 12, 2026 03:02 AM (83 min)

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

= Running fsck in CentOS 5=

It is apparently a very bad idea to run fsck on a mounted filesystem, even via single user mode. There are two good options for running it:
=== Boot from a CD ===
Boot from a CD with CentOS on it, and run it from the CD. Then none of your filesystems are mounted.

To do this, boot into Linux Rescue Mode:
<code>
boot: linux rescue
</code>

**DO NOT mount your filesystems when it asks you if you want to.** As noted above, you can't run ''fsck'' on a mounted filesystem.

Once you're in rescue mode, run ''fsck'' on the correct partition:
<code>
fsck -f /dev/sda1
</code>

If you've used the Linux LVM to create your partitions, you'll need to make those accessible before you run ''fsck'':
<code>
lvm pvscan
lvm vgscan
lvm lvchange -ay VolGroup00
lvm lvscan
</code>

Then you can run ''fsck'':
<code>
fsck -f /dev/VolGroup00/LogVol00 
</code>

=== Run on restart ===
If you type<code bash>bash# shutdown -Fr now</code>then CentOS will reboot and do a forced fsck, which will be done before the filesystems are mounted.

Page locked

About Me

Recent Changes

Get In Touch

Follow