/usr fails to fsck. can a new disk be added and the old root disk re-imported

[Matthew Murdock]

I have  a 11.31 IA server that the vg00 lvol7 (/usr) somehow got hosed somehow. (not the first beast that lost /usr, seems to be a common area for a bad sector to pop up on),  Unfortunately very little i feel I can do at this point to recover /usr, even under maintainance mode.

Can a new disk be put in, the OS reloaded and the old disk vg00 be re-imported under a new vg and the old volumes accessed for data recovery? Im not the admin of the system. It is a single disk system.

I have also tried the fsck -F vxfs -o full,nolog /dev/vg00/rlvol7 and still no luck.

# fsck -y /dev/vg00/rlvol7
vxfs fsck: V-3-20836: file system had I/O error(s) on meta-data.
vxfs fsck: V-3-20726: OLT extent 0 has bad checksum
read of primary OLT failed
vxfs fsck: V-3-20726: OLT extent 1 has bad checksum
read of OLT copy failed
vxfs fsck: V-3-20718: no valid OLT, cannot continue
file system check failure, aborting ...

[shiva_jr]

Hi @Matthew Murdock ,

    I have some queries. 
1. You want only to recover /usr or whole VG00?
2. Do you already have the backup by ignite-UX server or any other ways?
3. Do you have any other HP-UX server in the same network ?
Regards,
Shiva_JR

[shuff]

Yes, a new disk can be added and the OS can be reloaded.

based on The old disk vg00 can be re-imported under a new volume group and the old volumes can be accessed for data recovery. However, you need to first edit and remove the current root disk entry. This can be achieved by selecting the File System > Add/Remove Disks > Settings > Usage > None on the root disk. If you have configured two or more root disks under the root volume group when the archive was created, and during restore you want to remove one of the root disks from the root volume group and add another new root disk to the root volume group, you need to perform the following steps: 1. In the tool, go to File System > Add/Remove Disks menu, and set Usage > None of the Physical Volume which you want to remove. 2. Confirm that the removed Physical Volume is not part of the root volume group and is not being marked as root disk. Go to Basic > Root Disk. If the removed Physical Volume in step 1 is displayed as the root disk, then select the alternate disk as root disk.