/stand not mounted

[Bishwajit Kumar]

Hi.  I can't install a patch bundle because /stand/vmunix is not available which is due, in turn, to inability to mount because the device needs fsck.  But fsck fails with a media error.  Interestingly, reboot works -- it complains about fsck too, though.  Is there a way to get fsck to fix this?

# fsck -y /dev/vg00/lvol1
** /dev/vg00/lvol1
** Last Mounted on /stand
** Phase 1 - Check Blocks and Sizes

CANNOT READ: BLK 319728
CONTINUE?  yes

CANNOT READ: BLK 319728
CONTINUE?  yes

CANNOT READ: BLK 319728
CONTINUE?  yes

FAILED READ OF BLOCK #319728, RETRIED 2 TIMES
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
SUMMARY INFORMATION (INODE FREE) BAD
BAD CYLINDER GROUPS
FIX?  yes

** Phase 6 - Salvage Cylinder Groups
161 files, 0 icont, 11046 used, 210961 free (545 frags, 26302 blocks)
DISK MEDIA PROBLEMS ENCOUNTERED!
BAD BLOCKS WERE FOUND ON THE DISK.
***** FILE SYSTEM IS NOT CLEAN -- DISK MEDIA PROBLEMS ENCOUNTERED *****

***** FILE SYSTEM WAS MODIFIED *****

# mount /stand
mount: /dev/vg00/lvol1 needs to be fsck'ed before mounting
mount: warning: if device /dev/vg00/lvol1 is mounted to another system
                then do not run fsck

[Dennis Handly]

>Is there a way to get fsck to fix this?

I don't think so, you'll have to replace the disk.

Anything in /stand/lost+found/?

[Patrick Wallek]

If this isn't mirrored, I hope you've got a good Ignite/UX make_tape_recovery or make_net_recovery backup.

[Bill Hassell · Accepted solution]

> DISK MEDIA PROBLEMS ENCOUNTERED!
> BAD BLOCKS WERE FOUND ON THE DISK.

fsck is a tool that fixes the structure of a filesystem, things like used and free blocks of data and pointers to  inodes. fsck cannot fix bad spots on the disk. The message above means that the data on the disk is unreadable and cannot be repaired. If the disk is not mirrored, you should try to save anything you haven't already backed up and then replace the disk. Reformatting the disk might possibly fix the bad spots with the disk's built-in bad track handler, but once a disk gets a bad spot, it never gets better, only worse. Replace the disk and either restore from the mirror or reinstall HP-UX from your Ignite backup.

[Bishwajit Kumar]

I figured.  Thanks all.