Advanced fsck?

hadimotamedi · 01-27-2010, 11:54 PM

Dear All
My Red Hat 7.2 server got file system inconsistency , asking for "type Ctrl-D for normal boot or give root password for maintenance to run fsck manually". I tried for manually run fsck , as the followings :
#fsck -s /dev/hda3
But after rebooting the server it will come back again at the similar prompt asking for "give root password for maintenance" . Can you please do me favor and let me know how can I try for advanced fsck to fix the bug?
Thank you

vinaytp · 01-28-2010, 01:37 AM

Even I have encountered this issue while working with VMs. Sometimes running fsck to all file systmes will fix this issue.

Many times it gives ctrl-D option to reboot the machine even after running fsck to all filesystems. In such cases I have reinstalled the OS on VMs.

This has been happened to me when I play with LVM or fdisk commands in VMs. This is not acceptable when it comes to Real Machine. Can any expert guide us to fix this issue...

Awaiting for Positive replys...

Thanks in advance....

JZL240I-U · 01-29-2010, 08:18 AM

Quote:

Originally Posted by vinaytp

...Sometimes running fsck to all file systmes will fix this issue...

So as to be sure to fsck "/" as well I use from the Ctrl-D environment

Code:

shutdown -r -F now

That will force a check on all partitions listed in /etc/fstab while they are not mounted yet.

onebuck · 01-29-2010, 08:30 AM

Hi,

Quote:

Originally Posted by hadimotamedi

Dear All
My Red Hat 7.2 server got file system inconsistency , asking for "type Ctrl-D for normal boot or give root password for maintenance to run fsck manually". I tried for manually run fsck , as the followings :
#fsck -s /dev/hda3
But after rebooting the server it will come back again at the similar prompt asking for "give root password for maintenance" . Can you please do me favor and let me know how can I try for advanced fsck to fix the bug?
Thank you

You must run 'fsck' on a unmounted filesystem. By running in single user mode you insure that the filesystem can be repaired. You can pass 'single' to your kernel or use a LiveCD/install CD to boot the system then perform maintenance on the filesystem.