fsck fail

[Tarek]

Hi all,
i'm having a problem on boot.
On an HP9000 J200, OS 10.20, during boot i have:
Checking root file system:
/dev/rroot: Cannot read BLK 1258608
/dev/rroot: unexpected inconsistency: run fsck manually.
/sbin/fsclean:/dev/vg00/lvol3 not ok, run fsck.
File system non properly shutdown, beginning file system repair.
/dev/rroot: Cannot read BLK 1258608
/dev/rroot: unexpected inconsistency: run fsck manually.
Could not fix file system with fsck.
Cannot read: BLK 1258608
Continue ?
Cannot read: BLK 1258608
Continue ?
Failed read of Block #1258608, retried 2 times.
Disk media problems encountered .....
Then with CTRL + D the system goes up.
I also tried by sam to modify the option of /dev/dsk/lvol3 "Use Bad Block Relocation" but after boot i have same problems.
Is there on HP a way to erase or to skip or move that bad block, not using it more, so at boot i don't encounter this problem?
Thanks in advance for your help.
Tarek

[Sanjay_6]

Hi Tarek,

Have you tried booting into LVM maintainance mode and running fsck. Then use reboot inplace of shutdown.

To boot into lvm maintainance mode, interrupt the boot process and proceed like this

at the boot prompt type

bo pri

type "Y" to interact with the IPL. at the ipL prompt type
IPL>hpux -lm (;0)/stand/vmunix

It will boot into the maintainance mode. Run fsck on /dev/dsk/lvol3 and then reboot, don't do a shutdown.

hope this helps.

thanks

[James R. Ferguson]

Hi Tarek:

This doesn't look good. The inability of 'fsck' to read a block suggests that the filesystem or the disk is badly damaged. You are probably not going to be able to retrieve the data.

Regards!

...JRF...

[Tarek]

Thanks both. But i can enter in the ws and work, so i can retrieve data. How can i know if the filesystem is damaged or it's a hardware problem (disk to change). So if it's only fs i format and reinstall the OS.
Is it possible that there is no command that allows to eliminate that bad block? On Sun with format command you can do that. What is the same commnad on HP?

[James R. Ferguson]

Hi Tarek:

I trust you have an Ignite recovery tape. If not, I'd make one as soon as possible.

The next thing I think I'd do to attempt to differentiate between as hard disk error and a logical volume or filesystem corruption is this:

# dd if=/dev/rdsk/cXtYdZ of=/dev/null bs=1024k

See if any errors are detected via this.

Regards!

...JRF...

[Tarek]

James, i issued that command and i had this output:
dd read error: I/O error
1967+0 records in
1967+0 records out
What does it mean?
Thanks again,
Tarek

[James R. Ferguson]

Hi Tarek:

I'd definitely arrange to have this disk replaced. This is a physical level error.

Regards!

...JRF...