running fsck interactively

[paula hawk_2]

My system took a power hit and didn't shutdown properly. When rebooted I received a message to run FSCK interactively and to enter "d" when file is fixed. I am then at a prompt that is "in bcheckrc" When i run FSCK it aborts with a message "can not read block 125784" What can I do to resolve this? What happens if I run "mediainit"? This system is at a remote site and i do not have access to the server so I am stepping user through the commands.

thanks...paula

[Helen French · Accepted solution]

1) DONOT run mediainit. That will destroy all data.
2) from bcheckrc prompt, you can safely run this:

# fsck
This will check all file systems and will prompt you for Y/N if found any error. If you want to answer all questions with Y, then invoke:

# fsck -y

3) for a full check on vxfs file systems, invoke:

# fsck -o full lv_name

4) Once the fsck finish, you can tell the user to enter Ctrl+D to proceed with normal system startup

[PIYUSH D. PATEL]

Hi Paula,

do a fsck -y /dev/vg00/rlvol1

This will run in interactive mode and gives a yes for correcting all the problems.

If there is a bad sector then it may keep on trying ....sometimes it may be sucessful. If there is a bad sector, pls try to run it in interactive mdoe and mount the filesystem. Then take a backup quickly.

You can even try fsck /dev/vg00/rlvol1 but then you will have to answer all the questions it asks.

Also remember that after checking the filesystems, do a

# reboot -n and not shutdown.

Piyush

[S.K. Chan]

When you run your fsck you probably did it as interactive mode, meaning it'll prompt for a "CONTINUE" waiting for you to enter "yes" or "no". Entering "no" will abort it. You should enter "yes".
Or simply run fsck with the "-y" option like suggested by Shiju. Typically .. I think you're getting ..

CANNOT READ: BLK 125784(CONTINUE)?

If you enter "yes" it'll simply continue to run the file system check. If the error comes back again you may need to run fsck for the second time.
If after all is done and system still cannot completely check it then most likely the disk is bad.

[MANOJ SRIVASTAVA]

Hi Paula

fsck -y /dev/vgxx/rlvolxx

this will by default give yes to all responses , if there is problem wiht only one block then I dont think the problem can be resolved with media init , as the system must be ahving bad block reallocation. I would recoomend a disk change.


Manoj Srivastava

[paula hawk_2]

Thank you all for responding so quickly. We were able to get the system up and running, but a block on the disk is still bad. I am replacing the drive as a precaution.