Unable to recover system HPUX11,11

[Torsten.]

a partial dd is not a good idea.

where you get a "working disk" from???

[Nagarajan Balakrishnan_1]

Hi

I have 4 similar systems, one of them is in trouble. All the vg00 volumes are configured in a very similar fashion.

So, I am thinking of doing a dd from one of the working machines to this single hard disk. If it does not work, then still I have the other un-touched disk which is still having the original data (hopefully still intact!!)

BR
Baalki

[Torsten.]

dd would be the step behind my very last step. I would not do this.

You may try the suggested ignite procedure even if you have no tape drive. Set up one system as ignite server and make a backup of a known good system. build a golden image. restore it to the system in trouble.

[Nagarajan Balakrishnan_1]

Hi,

Mate, can you highlight the steps..I have never done a ignite backup/restore using the network.

Thanks
Baalki

[Nagarajan Balakrishnan_1]

Hi
I am sorry, there was an error in the mkboot command, I had mentioned earlier..

it was

mkboot -l /dev/rdsk/c2t0d0
etc..
not with s0

BR
Baalki

[Nagarajan Balakrishnan_1]

Hi all,

Just for additional info...

This is what I get in the recovery shell, trying to repair the corrupted /stand
--------------------------------------------
# /sbin/fs/hfs/fsck -b /dev/dsk/c2t0d0s1lvm
invalid alternate super block
# /sbin/fs/hfs/fsck /dev/dsk/c2t0d0s1lvm
** /dev/dsk/c2t0d0s1lvm
** Last Mounted on /STAND
** Phase 1 - Check Blocks and Sizes
WARNING: FOUND LARGE FILE(S) IN A NOLARGEFILES FILE SYSTEM. SEE fsadm(1M).
** Phase 2 - Check Pathnames
MISSING '.' I=4
OWNER=root MODE=40777
SIZE=8192 MTIME=Sep 22 13:30 2005
DIR=/lost+found
CANNOT FIX, FIRST ENTRY IN DIRECTORY CONTAINS #00003
MISSING '..' I=4
OWNER=root MODE=40777
SIZE=8192 MTIME=Sep 22 13:30 2005
DIR=/lost+found
CANNOT FIX, SECOND ENTRY IN DIRECTORY CONTAINS #08704
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
145 files, 0 icont, 11145 used, 26221 free (205 frags, 3252 blocks)
-------------------------------------------

any help?

BR
Baalki

[RAC_1]

Command is not right. It should be as follows.

fsck -b "alternate_superblock " disk_name
Now alternate superblock can be checked at by looking at /var/adm/sbtab file which you do not have. typically it will be 16.

fsck_hfs -b 16 "disk_name"

[Mark Nieuwboer]

Hi, our you could use when your in single user mode fsck -F hfs /dev/rdsk/c2t0d0.

But can you boot from your alt boot disk.
this question wasn't answered.

grtz. Mark

[Gavin Clarke]

Here is a link to the Ignite Admin Guide, I gather Chapter 5 is good if you are trying to ignite a server over the network.

http://docs.hp.com/en/B2355-90875/index.html

I'm under the impression that you can replace most if not all boot information from the recovery CD, which doesn't help you much if /stand is corrupt.

Have you tried fsck -F hfs /dev/vg00/rlvol1, from the recovery disk, answering yes to all the questions?

(That is if /stand is hfs, you can check against the other system /etc/fstab, which it is on ours).

The only other thing I can think of is to try putting one of the root disks in another system (if you have any spare slots) and see if you can vgimport the volume group from there.

Good Luck.

[Nagarajan Balakrishnan_1]

Hello everyone,

Thanks for all your responses. I finally arranged for a tape drive and just restored the /stand/rootconf file from another working system.

The system was able to mount the root and using which was able to enable vg00 and mount all other volumes.

Immediately after that, recreated the /stand and restored the whole contents of the /stand from another working machine. Then copied the /etc/ioconfig to /stand

All problems sorted out. Thanks for all your support

Best regards
Baalki