Disk Bad Sector

[Matthew Murdock]

I have a disk that was running fine, partially (meaning a section of the lvol was o.k, but another directory on the same fs portion could not be read), so I unmounted and ran fsck. I got back "CANNOT READ: BLK 50224". I am unable to re-mount for a backup. Is there a way to bypass the bad blocks and re-mount the fs....Please...

[Helen French]

If there is a hardware (I/O) error on the disk, most likely you will be out of luck. If it's a software or file system error, then run a full fsck on the file system:

# man fsck_vxfs

Say 'YES' to fix your software errors and you will be able to mount the file system back. If needed, you can reformat the file system after taking a full backup. If there is a hardware error, then you may have to replace the disk and restore files from the recent backup.

[Matthew Murdock]

Each time I run fsck (fsck -F hfs -y /dev/vg02/rlvol1)I get the same problem. I do not get any i/o errors, just cannot read blocks, then fsck continues, and then fails because of the bad blocks (fsck could not finish). It appears to be a media error (bad spot). is there any way via scsi low level commands from the console prompt to mark those spots bad (HPUX/10.20)?

[A. Clay Stephenson]

Since this is an hfs filesystem, you can assert the mount -f flag to force the mounting of the filesystem. Man mount_hfs for details.

e.g.

mount -F hfs -f -o ro /dev/vg01/lvol4 /user1

Now having mounted a corrupt filesystem, may the Force be with you.

[Matthew Murdock]

Bless the maker of backup devices.....Thank you for all your help. Both of you.