lvlnboot error during system boot.

[David Burgess]

When I rebooted a D350/2 I got this error :-

lvlnboot: Warning: Couldn't query physical
volume "/dev/dsk/c3t5d0": The specified path does not correspond to physical volume attached to this volume group.

I've deleted /etc/lvmtab and run vgscan to rebuild it.

# diskinfo -v /dev/rdsk/c3t5d0

SCSI describe of /dev/rdsk/c3t5d0:
vendor: SEAGATE
product id: ST34572WC
type: direct access
size: 4194157 Kbytes
bytes per sector: 512
rev level: HP03
blocks per disk: 8388314
ISO version: 0
ECMA version: 0
ANSI version: 2
removable media: no
response format: 2
(Additional inquiry bytes: (32)4b (33)38 (34)35 (35)31 (36)35 (37)34 (38)39 )

The disk is mirrored to /dev/dsk/c0t5d0. It's not the root VG.

# diskinfo -v /dev/rdsk/c0t5d0
SCSI describe of /dev/rdsk/c0t5d0:
vendor: SEAGATE
product id: ST34572WC
type: direct access
size: 4194157 Kbytes
bytes per sector: 512
rev level: HP03
blocks per disk: 8388314
ISO version: 0
ECMA version: 0
ANSI version: 2
removable media: no
response format: 2
(Additional inquiry bytes: (32)4b (33)39 (34)32 (35)33 (36)36 (37)39 (38)35 )

Has anyone seen this before?

Regards,

Dave.

[Steve Steel]

Hi


I saw this once and it went away with the latest LVM patches.

Check your patch level and monitor in case it happens again.


Steve Steel

[Peter Kloetgen]

Hi David,

you would also get this effect, when you have a volume group which is in inactive status. Entries in lvmtab are still there, but the error message is exactly what you described. Reactivate the volume group and the problem is gone.

Allways stay on the bright side of life!

Peter

[Bill McNAMARA_1]

Have you being doing dd's of the disk?

Two PVRAs and VGRAs (lvm headers) of the same PV on different disks would cause this.

strings /etc/lvmtab
to check which PV is in which vg.

Did vgscan report any errors?

Other than that, I too would suggest patching, but I don't really think that would have been a real cause...

Later,
Bill

[David Burgess]

This server is 10.20 and was last patched in Feb '99 well before my time here!

XSW800GR1020 B.10.20.43 Extension Software Patch Bundle

I guess there's a fair chance patching will fix the problem. It's a good first step.

lvmtab looks ok. It matches other systems with the same configuration.

vgscan had no problems at all.

Thanks for all your help.

Regards,

Dave.

[Klaus Schmitz]

David

If you try on your system lvlnboot -c hopefully you will see the same message as on bootup. If so, your vg00 is not the first one in /etc/lvmtab. So the devices that are listening are that ones before vg00 is mentioned in /etc/lvmtab.
the lvlnboot -c looks in /etc/lvmtab and search for the VG's. At this time there is only vg00 active and then you got this message from all the other devices.
Try lvlnboot -c /dev/vg00 and the we search for vg00 and do the right job.
You can modify this in /sbin/ioinitrc

[Joe Colucci_1]

I had a similar problem on an rp7400. The volume group was mirrored and one of the scsi controllers went bad. Therefore, the system could not see one of the physical volume groups. You may have a bad disk or bad controller.