Problem with second Boot device

[Peter Klausner_1]

I am convinced, that i had two boot devices:


Output form lvlnboot -v:


Current path "/dev/dsk/c0t14d0" is an alternate link, skip.
Current path "/dev/dsk/c0t12d0" is an alternate link, skip.
Current path "/dev/dsk/c4t10d0" is an alternate link, skip.
Current path "/dev/dsk/c4t8d0" is an alternate link, skip.
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c4t12d0 (0/4/0/0.12.0)
/dev/dsk/c4t14d0 (0/4/0/0.14.0) -- Boot Disk
/dev/dsk/c0t14d0 (0/0/1/0.14.0) -- Boot Disk
/dev/dsk/c0t12d0 (0/0/1/0.12.0)
/dev/dsk/c0t10d0 (0/0/1/0.10.0) -- Boot Disk
/dev/dsk/c0t8d0 (0/0/1/0.8.0)
/dev/dsk/c4t10d0 (0/4/0/0.10.0) -- Boot Disk
/dev/dsk/c4t8d0 (0/4/0/0.8.0)
Boot: lvol1 on: /dev/dsk/c4t14d0
/dev/dsk/c0t14d0
/dev/dsk/c0t10d0
/dev/dsk/c4t10d0
Root: lvol3 on: /dev/dsk/c4t14d0
/dev/dsk/c0t14d0
/dev/dsk/c0t10d0
/dev/dsk/c4t10d0
Swap: lvol2 on: /dev/dsk/c4t14d0
/dev/dsk/c0t14d0
/dev/dsk/c0t10d0
/dev/dsk/c4t10d0
Dump: lvol2 on: /dev/dsk/c4t14d0, 0

But if i run

lifls -C /dev/rdsk/c0t10d0


I get the following error:

lifls: Can't list /dev/rdsk/c0t10d0; not a LIF volume

Is there any way that makes the device again bootable (mkboot ?)


Who can help ?


Thanks in advance

[James R. Ferguson]

Hi Peter:

Did you do 'pvcreate -B' when you started? It appears that you did not.

Regards!

...JRF...

[Stefan Farrelly]

er, that should read; ..try NOT to overwrite user data...

[Stefan Farrelly]

You can try a mkboot -u to install the lif area. The -u means it will try to overwrite user data, see the manpage for mkboot and -u.
Tere is an element of risk to running this though.

[harry d brown jr]

is this an L-class or N-class? What kind of storage are you using?

Being that you thought you had it setup, I'd suggest you re-evaluate the machine and carefully document everything again! And before you do a mkboot, make sure the disk is not in use, and please make sure you do backups!

live free or die
harry

[Peter Klausner_1]

Hi Stefan,


do you mean mkboot -l /dev/rdsk/c0t10d0

or

mkboot -u /dev/rdsk/c0t10d0

I use MirrorDisk

So Can use


vgcfgrestore -n /dev/vg00 /dev/rdsk/c0t10d0 ?


Peter

[harry d brown jr]

Peter,

Mirroring LV's doesn't make the "mirrored" disk bootable.

Again, please follow my previous advice and don't do a damn thing until you have satisified my previous suggestions!

live free or die
harry

[James R. Ferguson · Accepted solution]

Hi Peter:

You can try:

# 'mkboot /dev/rdsk/cXtYdZ'
# mkboot ???a ???hpux ???lq??? /dev/rdsk/cXtYdZ

...but I think 'mkboot' is going to complain:

"There appear to be non-boot logical volumes on this device. Overwriting them could destroy all the data on this device..."

If this is the case, you're stuck. Start from scratch with 'pvcreate -B...'.

Regards!

...JRF...

[Stefan Farrelly]

I mean mkboot -u /dev/rdsk/cxxxxx

ive just tried it on a test system on an existing bootable mirror disk and it worked fine and didnt corrupt anything! Read the manpage carefully first.

[Peter Klausner_1]

Hi everbody,


mkboot /dev/rdsk/c0t10d0
mkboot -a "hpux -lq" /dev/rdsk/c0t10d0

worked.


Thank you everbody and have a nice weekend.


Peter

[James R. Ferguson]

Hi (again) Peter:

/NO MORE POINTS for me, please.../

Your /dev/dsk/c0t10d0 device was indeed created as a bootable disk by 'pvcreate'. I missed the "Boot Disk" designation on it when I answered.

Had it not been, you would have indeed seen the message I posted when you issued 'mkboot'. The fact that you did not see the warning was a further indication that the disk was in fact bootable in the first place!

*Stefan* deserves more credit for his contributions, however, for his suggestion to use the '-u' option of 'mkboot'.

Regards!

...JRF...