lvlnboot -c

[David Burgess]

I just ran lvlnboot -c instead of lvlnboot -v.

I assume as it updates the /stand/rootconf file with the location of the root volume in the currently booted volume group that I haven't done anything wrong and the system will still reboot.

Regards,

Dave.

[Patrick Wallek · Accepted solution]

If you do an 'lvlnboot -v' does everything still look normal?

You SHOULD be OK, I think.

[Uday_S_Ankolekar]

Hello,

The /stand/rootconf file will create everytime you reboot the box. So you can carry on with your lvlnboot -v stuff!

Goodluck,
-USA..

[David Burgess]

/software/jetadmin/HPUX_11.00 > lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c0t6d0 (8/12.6.0) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c0t6d0
Root: lvol3 on: /dev/dsk/c0t6d0
Swap: lvol2 on: /dev/dsk/c0t6d0
Dump: lvol2 on: /dev/dsk/c0t6d0, 0

Looks ok to me.

Dave.

[ashish nanjiani]

You should not have any problem with -c option.

[Helen French]

Hi David:

Running lvlnboot -c will not create any problems for you ! As you already mentioned, it will create/modify the file /stand/rootconf which will be used by the system during a Maintenance boot. This command (lvlnboot -c) will be automatically done every time during a normal system boot by /sbin/ioinitrc command. If you have booted from the normaly boot disk and if lvlnboot -v displays OK, then you don't have any problems. It is not necessary to reboot the system if you have done this accidently.

HTH,
Shiju

[David Burgess]

Thanks for all your help. I have now rebooted and all is well.

Regards,

Dave.