How to run fsck manually?

[Tam_10]

We have a workstation base on HP 9000/B132L It cannot boot now and it’s messages as follow:

FILE SYSTEM (S) NOT PROPERLY SHUTDOWN
BEGINNING FILE SYSTEM REPAIR

RUN fsck MANUALLY

COULD NOT FIX FILE SYSTEM WITH fsck –P, RUN fsck INTERACTIVELY

LOGGING IN AS root FOR MANUALY fsck, ENTER ^D WHEN FILE SYSTEM FIXED

CANNOT READ: BLK 1627568

Please help me to solving this problem. Thank you very mu

[Naveej.K.A]

Hi,

Just type fsck on the prompt.

and when everything is fixed press ctrl and D to continue booting.

Regards,
Naveej

[Bharat Katkar]

Hi,
# fsck -F fstype /dev/vgxx/rlvolx

This shoudl work and will prompt you before doing changes to filesystem.

Now that you have got bad block some of your data may be lost.

Regards,

[Bharat Katkar]

Hi,
# fsck -F fstype /dev/rdsk/cxtxdx

This shoudl work and will prompt you before doing changes to filesystem.

Now that you have got bad block some of your data may be lost.

Regards,

[Gopi Sekar]

type fsck and press enter

it will launch fsck with appropriate options required to check all known partitions in the system and correct the errors.

generally fsck should be able to automatically fix the filesystem issues, only on rare case where the damage is more and require inputs from user fsck drops user into shell and prompts him to run fsck manually.

Regards,
Gopi

[Kyris]

For my system, HP9000, I go to single user mode and run fsck -F vxfs -o full /dev/vg01/rmyfs1 (if jfs file system) - specify the raw device file for optimal performance.
Once done then do reboot -n, which may take a bit of time but it does NOT flush the buffer cache, which may overwrite the corrections made by fsck.
Then check the lost+found directory for any files that exist. Use file \#1723 or strings \#1723 to see what it contains/useful. If usefull try and get the file from backup or mv \#1723 new_file_name.

[Sandman!]

fsck cannot read block generally indicates media failure. Best thing to do is replace/rebuild the disk and build the existing filesystem from backup.

This error won't be corrected by re-running fsck because fsck scans only the metadata blocks and not the actual data blocks.

[Geoff Wild]

Just try running:

fsck

It will prompt you along the way...


When complete - ^d (control d) to exit...

Rgds...Geoff

[Nguyen Anh Tien]

fsck - file system consistency check and interactive repair
recommend
#man fsck
for quick
#fsck -F VXFS /dev/rdsk/c0t0d2

[Pravin Salgaonkar]

hi
type
fsck -F fstype /dev/vgxx/rlvolx

this should work
Regards
Pravin S