lvlnboot info lost

[mogiro]

Hi,
I've got a rx6600 with 11.31 OS and after a reboot it seems that the HW paths of the disk are changed. The data VG was not mounted, but renaming /etc/lvmtab and recreating it with vgscan solved the problem.
The issue now is:
bidbcn1:/home/root # lvlnboot -v
Warning: Cannot determine block size of Physical Volume "/dev/rdisk/disk7_p2".
Assuming a default value of 1024 bytes. Continuing.
fail in reading_lvmrec, nread = 0, btor = 1024.
fail in reading_lvmrec, nread = 0, btor = 0.
Warning: Cannot determine block size of Physical Volume "/dev/rdisk/disk5_p2".
Assuming a default value of 1024 bytes. Continuing.
fail in reading_lvmrec, nread = 0, btor = 1024.
fail in reading_lvmrec, nread = 0, btor = 0.
Warning: Cannot determine block size of Physical Volume "/dev/rdisk/disk7_p2".
Assuming a default value of 1024 bytes. Continuing.
Warning: Cannot determine block size of Physical Volume "/dev/rdisk/disk5_p2".
Assuming a default value of 1024 bytes. Continuing.
Current path "/dev/dsk/c1t0d0" is an alternate link, skip.
Current path "/dev/dsk/c1t0d1" is an alternate link, skip.
Current path "/dev/dsk/c1t0d2" is an alternate link, skip.
Current path "/dev/dsk/c1t0d3" is an alternate link, skip.


It means I have no boot info on the disk?

[Vihang.]

Hi,

What does you "vgdisplay -v vg00" show? Have you tried running "lvlnboot -R"?


Regards,
Vihang.

[mogiro]

bidbcn1:/home/root # vgdisplay -v vg00
--- Volume groups ---
VG Name /dev/vg00
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 9
Open LV 9
Max PV 16
Cur PV 2
Act PV 2
Max PE per PV 4356
VGDA 4
PE Size (Mbytes) 32
Total PE 8694
Alloc PE 3456
Free PE 5238
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0
VG Version 1.0.0

--- Logical volumes ---
LV Name /dev/vg00/lvol1
LV Status available/syncd
LV Size (Mbytes) 1792
Current LE 56
Allocated PE 112
Used PV 2

LV Name /dev/vg00/lvol2
LV Status available/syncd
LV Size (Mbytes) 8192
Current LE 256
Allocated PE 512
Used PV 2

LV Name /dev/vg00/lvol3
LV Status available/syncd
LV Size (Mbytes) 1024
Current LE 32
Allocated PE 64
Used PV 2

LV Name /dev/vg00/lvol4
LV Status available/syncd
LV Size (Mbytes) 2048
Current LE 64
Allocated PE 128
Used PV 2

LV Name /dev/vg00/lvol5
LV Status available/syncd
LV Size (Mbytes) 1024
Current LE 32
Allocated PE 64
Used PV 2

LV Name /dev/vg00/lvol6
LV Status available/syncd
LV Size (Mbytes) 7712
Current LE 241
Allocated PE 482
Used PV 2

LV Name /dev/vg00/lvol7
LV Status available/syncd
LV Size (Mbytes) 5120
Current LE 160
Allocated PE 320
Used PV 2

LV Name /dev/vg00/lvol8
LV Status available/syncd
LV Size (Mbytes) 12000
Current LE 375
Allocated PE 750
Used PV 2

LV Name /dev/vg00/lvswap
LV Status available/syncd
LV Size (Mbytes) 16384
Current LE 512
Allocated PE 1024
Used PV 2


--- Physical volumes ---
PV Name /dev/disk/disk7_p2
PV Status available
Total PE 4347
Free PE 2619
Autoswitch On
Proactive Polling On

PV Name /dev/disk/disk5_p2
PV Status available
Total PE 4347
Free PE 2619
Autoswitch On
Proactive Polling On



What lvlnboot -R does exactly?

[Vihang.]

Hi,

"lvlnboot -R" will recover any missing links to all of the logical volumes specified in the Boot Data Reserved Area and update the Boot Data Reserved Area of each bootable physical volume in the volume group.


Regards,
Vihang.

[Jeeshan]

#man lvlnboot

[Deepak Kr]

You need to run following to set again!!

root
lvlnboot -r /dev/vg00/lvol3
swap
lvlnboot -s /dev/vg00/lvol2
dump
lvlnboot -d /dev/vg00/lvol2

info abt lvlnboot -R option

-R Recover any missing links to all of the
logical volumes specified in the Boot Data
Reserved Area and update the Boot Data
Reserved Area of each bootable physical
volume in the volume group

[sreekanthtm]

Hope there is some corruption in boot area.
You can remove the special definition of the VG using lvrnboot command and then recreate it....
#lvrmboot -v -r -s /dev/vg00

#lvlnboot -r /dev/vg00/lvol3
#lvlnboot -s /dev/vg00/lvol2
#lvlnboot -b /dev/vg00/lvol1

This safely recreate the boot area.....

Cheers
Sreekanth

[TTr · Accepted solution]

Did you add any internal disks to the server some time ago? If so this is what caused the HW paths to change. It is a known issue with these servers and I think with the rx3600 as well. The vgscan routine corrected the paths in the LVM information on the disk headers. The "lvlnboot -R" will update the boot headers and will clear the error.

[mogiro]

Yes, we were experiencing some problems with the usb entry and I tried to mount a pen drive there...
This machine is involved with another issue, and the HP tehcnicians recommend me not to touch the boot config till they analize the crash dump file, so once they let me do it, I will launch the lvlnboot -R command.
Thanks to all!!

[Torsten.]

Yes, we were experiencing some problems with the usb entry and I tried to mount a pen drive there...

Dangerous - an unsupported pen drive may or may not crash the system.

There are many USB driver related changes recently - refer to the relevant driver release notes.

[mogiro]

Hi all again,
Now I've got a data backup and a ignite image, so I ran the lvrmboot command. But:

lvrmboot -v -r -s /dev/vg00
Warning: Cannot determine block size of Physical Volume "/dev/rdisk/disk7_p2".
Assuming a default value of 1024 bytes. Continuing.
fail in reading_lvmrec, nread = 0, btor = 1024.
fail in reading_lvmrec, nread = 0, btor = 0.
Warning: Cannot determine block size of Physical Volume "/dev/rdisk/disk5_p2".
Assuming a default value of 1024 bytes. Continuing.
fail in reading_lvmrec, nread = 0, btor = 1024.
fail in reading_lvmrec, nread = 0, btor = 0.
Warning: Cannot determine block size of Physical Volume "/dev/rdisk/disk7_p2".
Assuming a default value of 1024 bytes. Continuing.
Warning: Cannot determine block size of Physical Volume "/dev/rdisk/disk5_p2".
Assuming a default value of 1024 bytes. Continuing.
No valid Boot Data Reserved Areas exist on any of the
Physical Volumes in the Volume Group "/dev/vg00".
Issue the pvcreate -B command to create a Boot Area on a Physical Volume.

My vg00 is mirrored, maybe it can help.
Any suggestion?