- Integrated Systems
- About Us
- Integrated Systems
- About Us
07-22-2015 03:04 AM
I've had to copy two hpvm disks to a different san.
Boot fails with lvm issues.
Initially, it looked straight forward with lvmtab expecting root to be on c0t0d2 and the new disks present as c0t0d0 and c0t0d1. I went through the vgexport and vgimport process to point to c0t0d0 but no joy
Anyway, my question relates to what is -lm in boot /stand vmunix -lm command
I seem to be booted single user, have a subset of commands (ls, cat but not df or strings) and it appears to be the correct / filesystem. If it cannot find the boot disk I'm suprised I have been able to boot into anything that gives me single user style control so I'm wondering how I've managed to boot into anything usable if lvm info is not found
Also, this is the problem I am trying to resolve
2 disks found:
# ioscan -fnC disk
Class I H/W Path Driver S/W State H/W Type Description
disk 0 0/0/0/0.0.0 sdisk CLAIMED DEVICE HP Virtual Disk
disk 1 0/0/0/0.1.0 sdisk CLAIMED DEVICE HP Virtual Disk
vgscan: Warning: couldn't query physical volume "/dev/dsk/c0t0d0s2":
The specified path does not correspond to physical volume attached to
this volume group
vgscan: Warning: couldn't query all of the physical volumes.
vgscan: has no correspoding valid raw device file under /dev/rdsk.
Verification of unique LVM disk id on each disk in the volume group
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vg00".
# vgchange -a y vg00
vgchange: Couldn't activate volume group "vg00":
Quorum not present, or some physical volume(s) are missing.
# LVM: VG 64 0x000000: Quorum check failed!
# mkdir /dev/vg00
# mknod /dev/vg00/group c 64 0x000000
# vgimport -m /vg00.map vg00 /dev/dsk/c0t0d0
Physical Volume "/dev/dsk/c0t0d0" contains no LVM information
Solved! Go to Solution.
07-22-2015 07:09 AMSolution
The '-lm' means LVM Maintenance Mode. It is kind of like single-user mode, but the VG has not been activated. It is meants for situations like you are in right now.
>># vgchange -a y vg00
>>vgchange: Couldn't activate volume group "vg00":
>>Quorum not present, or some physical volume(s) are missing.
To activate a VG that does not have a quorum, you must add the '-q n' to the vgchange command.
# vgchange -a y -q n vg00
>># mkdir /dev/vg00
>># mknod /dev/vg00/group c 64 0x000000
>># vgimport -m /vg00.map vg00 /dev/dsk/c0t0d0
>>Physical Volume "/dev/dsk/c0t0d0" contains no LVM information
Since this is an Itanium server you boot disks have the 'slices' (notice the s1, s2, s3 in your ioscan.). So to import the boot disk into the VG you must do:
# vgimport -m /vg00.map vg00 /dev/dsk/c0t0d0s2
If you need to have both disks c0t0d0 and c0t1d0 in VG00, then you need to do:
# vgimport -m /vg00.map vg00 /dev/dsk/c0t0d0s2 /dev/dsk/c0t1d0
Once you have done that you can try booting your system normally again and see how it goes.
07-24-2015 08:00 AM
Re: boot /stand/vmunix -lm - what is the -lm ?
actually I was a bit quick on saying that it had fixed things. When booted in -lm mode I can successfully activate the volume group but on boot up it still looks to boot in quorom mode. Currently looking to see how to pass the "-q n" flags to vchange on boot up. If I find out I'll post back