pvcreated OS disks, now, surprise surprise, it won't boot.

[Vball23]

Well, I did a malformed, ioscan, grep, awk, pvcreate and pvcreated /dev/rdsk/c0t6d0 and c2t6d0 on a system that I just loaded the OS on and was configuring SAN disks. Total noob action, I know.

This is a 11.23 system, so it had the c0t6d0s2 slices, etc. for the OS. I didn't notice c0t6d0 and c2t6d0 were in my pvcreate statement, but was surprised afterwarrds when I noticed it actually let me pvcreate them, which I now assume wiped out the slices for the OS.

So, is there any way back from this, other than reloading the OS?

[Rita C Workman]

Do you have an ignite tape of this server you could rebuild from ??

Just a thought,
Rita

[Vball23]

I'll have to check to see if they created an ignite tape after the OS load, which was done from an ignite tape from another system. I guess I could use that one.

[Rita C Workman]

Let's hope they did, and if they didn't then using the previous tape to build from again would probably be quicker then rebuilding from scratch.

Rgrds,
Rita

[Torsten.]

There was no pvheader at this area of the disk (it is in "s2") to pvcreate does not complain.

Because it only writes the header, I would guess all the partitions are still there. There is a secondary partition table also at the end of the disk.

Your pvcreate did destroy the EFI partition "s1" only IMHO, so I think if you boot the installer DVD, start a recover and restore this area you will be fine.

[Vball23]

I've gotten this far:

Entering boot area repairing...

Loading commands necessary for boot recovery...

idisk: Primary partition information not valid.
Run idisk with -r option to restore.
The verification failed. Trying to restore
the partitions of /dev/rdsk/c0t6d0.

Restoring Primary Header and Table from Alternate.
Restoration of partitions on /dev/rdsk/c0t6d0 completed OK.

Verification of partitions on /dev/rdsk/c0t6d0 completed OK.

Running mkboot to verify/repair boot areas.

Specifying -e option requires devices files for EFI and HP-UX partitions.
Specifying -e option requires devices files for EFI and HP-UX partitions.
mkboot failed.

[Emil Velez]

1. Boot from a support media
2. get into a command mode.

Do you know how idisk partitioned your boot disk ? Partition it the same way it was before using idisk and put a boot area on s1. You might be lucky that s2 did not get wacked.

[Vball23]

Fell back on original ignite tape. Thanks for the help.