fsck reporting "CANNOT READ: BLK 14992" on Logical Volume on HPUX 10.20 running on HP735

[Norman Woo]

Hi folks

Encountered a problem during the fsck phase after a system reboot
(there goes the non-down time of 455 days!!!!). Reports that it
cannot read block 14992 and kicks the process into the bcheckrc prompt
directing me to run 'fsck' manually. After running fsck manually I
still cannot continue with boot process.

System is the ole-trustworthy HP735 running HPUX 10.20.

During the first time when I ran fsck it did prompt me with about 10
system files under /usr/lib that it encountered problem with and asked
if I wanted it to remove it from the system. I forgot to note what
those 10 files were and answered "no". Subsequent running of "fsck"
no longer prompts for the removal of those 10 files.

I was hoping to say yes and then recover those 10 files from backups.
Is there a way to get fsck to prompt me for those files?

Or is there a way to tell fsck to skip block 14992 or mark it bad?

The data in question is under /usr which is physically on another disk
via Logical Volume mounted under /usr. The 10 files were /usr/lib/lib
something (I should have noted them down the first time!!!). So I
should be able to get those from another HPUX system we have.

Thanks for all your suggestions.

[Oh yeah, found out that the system went bersek when the
air-conditioner in the server room failed and temperature shot up to
40 degress celcius!!!]

[Frank Slootweg]

If you do not get a "CANNOT SEEK: BLK ..." for the same block, which
you probably don't because the block number is quite low, it is a
physical read error, i.e. you can not physically read that block. For
'modern' (less than about 10 years old) disk, you can not 'fix' a bad
block and it's no using trying to 'skip' it because your disk is about
to fail. So I advise to get it replaced.

If you still need to backup this filesystem and it is HFS (which it
looks to be, considering the format of the error message), then (try to)
mount it forced, i.e. "mount -f -F HFS ...." and back it up.

[kevin bale]

> [Oh yeah, found out that the system went bersek when the
> air-conditioner in the server room failed and temperature shot up to
> 40 degress celcius!!!]

That happened to us once or twice. What happened was 12 mths of pain as the
shocked components failed at random intervals.