No Boot Logical Volume configured

[JHA]

( rp8400, vg00 EMC disks ) A vpar during maintenance reboots without boot logical volume configured. vg00 resides on 2 mirrored disks.

vparstatus -e results in a
Unkown filesystem for path (/device...;)/stand/vmunix

What would actually be the best way to get the system up and running again and restore the boot information? is there a workaround?

[Steven E. Protter]

It would seem you need to boot somehow, probably off install media and do the following:

vlnboot -r /dev/vg00/lvol3 # root fs /
lvlnboot -s /dev/vg00/lvol2 #swap
lvlnboot -d /dev/vg00/lvol2 #swap/dump
lvlnboot -b /dev/vg00/lvol1
lvlnboot -R
lvlnboot -v
setboot
setboot -a 52.1.0 # second disk

However, since this is vpar, its likely you can at least boot off of some other device and avoid the media boot. You might want to consider re-creating the vpar if indeed the path its complaining about exists and contains valid boot information.

What happened, you were doing maintenance or something?

SEP

[JHA]

Ok I can access the disks if I boot up the npar only. But how am I supposed to solve the problem? guess you have to run lvlnboot on an active vg and I can't boot on the disk cause it's missing the boot colume config.

[Steven E. Protter]

I don't know how the vpar's got modified or destroyed, but it looks like they need to be re-created.

I'm scanning through the vpar manual, looking if there is a backup they can be read from.

Did you take an ignite backup of the system prior to doing whatever it is that was done to cause this situation?

Hopefully someone can be more specific. Right now I'm not sure you have anything to work with due to the vparstatus.

It would be very helpful to know the exact steps taht were taken to get the system into this condition.

SEP