topic Re: System won't boot - missing LVM.... in Operating System - HP-UX

System won't boot - missing LVM....

Coolmar — Mon, 03 Apr 2006 07:36:40 GMT

Hi,

A little background: Our HP-UX 11i vpars boot off our SAN. We had to move some of the fibre channel cables around and the system would no longer boot. I booted up the Npar and did and ioscan and found the new hardware path of the boot disk. All we did was move the cable from one fabric to another, so the hardware address was basically the same except for the fabric changed from 202 to 201. I changed the vpar boot disk to the new address, deleted the old address that no longer exists with vparmodify and now it won't boot. Here is the error that I get:

Host is virtual System Console slave
WARNING: ROOT device 0x1f030000 is a non-LVM partition, disallowed on LVM disk.
WARNING: ROOT device 0x1f030000 has been deconfigured (set to 0xffffffff).
..
..
panic: LVM: Configuration failure
...

I have also attached the Npar ioscan as well as the vparstatus and more details of the boot error.

Thanks!

Re: System won't boot - missing LVM....

Steven E. Protter — Mon, 03 Apr 2006 07:43:23 GMT

Shalom Sally,

Your instance numbers on the fiber channel adapters changed.

Your system is set to boot off the old address.

setboot
setboot -a 52.1.0

You need to find the path you now wish to boot off of in your ioscan and setboot to it.

SEP

Re: System won't boot - missing LVM....

Coolmar — Mon, 03 Apr 2006 07:57:08 GMT

thanks Steven but I am not sure that I am following...the old hardware device was 0.0.14.1.0.202.6.0.0.0.0 When we moved the cable and did an ioscan from the Npar the new address became 0.014.1.0.201.7.0.0.0.0 I went into vparmodify and changed the boot disk accordingly and the errors above is what I got. Is that what you mean?

Re: System won't boot - missing LVM....

Kent Ostby — Mon, 03 Apr 2006 08:07:37 GMT

Sally -- When you boot, choose to interact with ISL.

From ISL, type:

hpux -lm

Once there, you probably need to rebuild your lvm boot header information as follows:

vgchange -v /dev/vg00
lvrmboot -r /dev/vg00
lvlnboot -s /dev/vg00/lvol2
lvlnboot -d /dev/vg00/lvol2
lvlnboot -r /dev/vg00/lvol3
lvlnboot -b /dev/vg00/lvol1

Then reboot and come up off the disk again

Re: System won't boot - missing LVM....

Coolmar — Mon, 03 Apr 2006 08:41:50 GMT

I was able to boot with the -lm options. I did the following:

ioscan -fn
insf -e
mv /etc/lvmboot /etc/lvmboot.prev
vgscan -a

This was the output of the vgscan -a:

vgscan -a
Couldn't stat physical volume "/dev/dsk/c3t4d0":
Invalid argument
Couldn't stat physical volume "/dev/dsk/c3t5d0":
Invalid argument
Couldn't stat physical volume "/dev/dsk/c3t6d0":
Invalid argument
Couldn't stat physical volume "/dev/dsk/c3t7d0":
Invalid argument
Couldn't stat physical volume "/dev/dsk/c3t8d0":
Invalid argument
Couldn't stat physical volume "/dev/dsk/c3t9d0":
Invalid argument
Couldn't stat physical volume "/dev/dsk/c3t10d0":
Invalid argument
Couldn't stat physical volume "/dev/dsk/c3t11d0":
Invalid argument
Couldn't stat physical volume "/dev/dsk/c3t12d0":
Invalid argument
Couldn't stat physical volume "/dev/dsk/c3t13d0":
Invalid argument
Couldn't stat physical volume "/dev/dsk/c3t14d0":
Invalid argument
Couldn't stat physical volume "/dev/dsk/c3t15d0":
Invalid argument

Following Physical Volumes belong to one Volume Group.
Unable to match these Physical Volumes to a Volume Group.
Use the vgimport command to complete the process.
/dev/dsk/c3t0d0

Following Physical Volumes belong to one Volume Group.
Unable to match these Physical Volumes to a Volume Group.
Use the vgimport command to complete the process.
/dev/dsk/c3t0d1
/dev/dsk/c3t0d2
/dev/dsk/c3t0d3
/dev/dsk/c3t0d4
/dev/dsk/c3t0d5
/dev/dsk/c3t0d6
/dev/dsk/c3t0d7
/dev/dsk/c3t1d0
/dev/dsk/c3t1d1
/dev/dsk/c3t1d2
/dev/dsk/c3t1d3
/dev/dsk/c3t1d4
/dev/dsk/c3t1d5
/dev/dsk/c3t1d6
/dev/dsk/c3t1d7
/dev/dsk/c3t2d0
/dev/dsk/c3t2d1
/dev/dsk/c3t2d2
/dev/dsk/c3t2d3
/dev/dsk/c3t2d4
/dev/dsk/c3t2d5
/dev/dsk/c3t2d6
/dev/dsk/c3t2d7
/dev/dsk/c3t3d0
/dev/dsk/c3t3d1

The Volume Group /dev/vg00 was not matched with any Physical Volumes.
The Volume Group /dev/vg01 was not matched with any Physical Volumes.

Re: System won't boot - missing LVM....

Coolmar — Mon, 03 Apr 2006 10:09:39 GMT

Can anyone tell me how to do the vgimport?

Re: System won't boot - missing LVM....

Alzhy — Mon, 03 Apr 2006 10:37:26 GMT

Sally,

Okay so let's do this step by step:

1. You're booted off your nPar - so I assume your nPar's default boot path is NOT the same as any of your vPars.

2. You know your each vPar's SAN boot paths

3. How many SAN disks is your vg00 made up?

4. Did you have a backup of your vg00 mapfile at all?

Re: System won't boot - missing LVM....

Coolmar — Mon, 03 Apr 2006 10:40:54 GMT

Hi Nelson...thanks for the help! My responses are just below your questions:

1. You're booted off your nPar - so I assume your nPar's default boot path is NOT the same as any of your vPars.

Right now I am booted off the vpar in single-user mode. I cannot recreate the /etc/lvmtab with the vgscan

2. You know your each vPar's SAN boot paths

yes.

3. How many SAN disks is your vg00 made up?

Just one

4. Did you have a backup of your vg00 mapfile at all?

Yes, but it in in /usr/local/vgmaps and because I am in single user mode I can't access it and can't mount it because the lvm stuff is all messed up.

Re: System won't boot - missing LVM....

Alzhy — Mon, 03 Apr 2006 10:54:02 GMT

Okay:

1. Check /etc/lvmconf if you have a vg00.mapfile and check if it is still accurate.

2. vgexport vg00

3. mkdir /dev/vg00

4. mknod /dev/vg00/group c 64 0x000000

5. vgimport -m /etc/lvmconf/vg00.mapfile vg00 /dev/dsk/cXtYdZ

where cXtYdZ is the hpdev of your SAN boot disk. Let me know if you need help figuring this out.

6. vgchange -a y vg00

7. Then:

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

(subst lvolN for whatever are your approp lvol number of lvol name if you use names)

lvlnboot -R

8. Your final "lvlnboot -v" display should be something like:

Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c1t6d0 (0/0/2/0.6.0) -- Boot Disk
/dev/dsk/c2t6d0 (0/0/2/1.6.0) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c1t6d0
/dev/dsk/c2t6d0
Root: lvol3 on: /dev/dsk/c1t6d0
/dev/dsk/c2t6d0
Swap: lvol2 on: /dev/dsk/c1t6d0
/dev/dsk/c2t6d0
Dump: lvol2 on: /dev/dsk/c1t6d0, 0

9. You can now reboot and fix your other VGs in run level 3...

Re: System won't boot - missing LVM....

Pete Randall — Mon, 03 Apr 2006 10:54:26 GMT

Sally,

The only reason you would need a map file would be if you used non-conventional logical volume names. Considering that this is vg00, I expect that they were default: lvol1, lvol2, etc.

If that is true, then your import is simple:

vgimport vg00 /dev/dsk/cXXtYYdZZ

I would try it with the preview option (-p) first just to see what it looks like.

Pete