mirror third root disk to be used in another server

[cokehpux]

two  mirrored root disks (70GB each) exist in a working server ( HP-UX B.11.23  / 9000/800/rp3440 )

we have a new 140GB disk...we need a bootable OS image in this new 140GB disk to be placed in another server(rp3440)

so we inserted this new 140GB disk in this working server - identfied it.

Now we need to mirror this new 140GB disk. then break the mirror? then remove it from the working server and use it to boot some other server. Appreciate some suggestions please. Many thanks

[root:]# ioscan -fnC disk|more
Class I H/W Path Driver S/W State H/W Type Description
=============================================================================
disk 0 0/0/2/0.0.0.0 sdisk CLAIMED DEVICE _NEC DVD+-RW ND-6650A
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0

disk 1 0/1/1/0.0.0 sdisk CLAIMED DEVICE HP 73.4GMAX3073NC
/dev/dsk/c2t0d0 /dev/rdsk/c2t0d0 - (root disk 70GB)

disk 17 0/1/1/0.1.0 sdisk CLAIMED DEVICE HP 73.4GST373455LC
/dev/dsk/c2t1d0 /dev/rdsk/c2t1d0 - (another root disk 70GB)

disk 428 0/1/1/1.0.0 sdisk CLAIMED DEVICE SEAGATE ST3146855LC
/dev/dsk/c3t0d0 /dev/rdsk/c3t0d0 (new disk to be mirrored 140GB)

disk 427 0/1/1/1.2.0 sdisk NO_HW DEVICE SEAGATE ST3146855LC
/dev/dsk/c3t2d0 /dev/rdsk/c3t2d0

[root:/var/spool/cron]# lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c2t0d0 (0/1/1/0.0.0) -- Boot Disk
/dev/dsk/c2t1d0 (0/1/1/0.1.0) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c2t0d0
Root: lvol4 on: /dev/dsk/c2t0d0
Swap: lvol2 on: /dev/dsk/c2t0d0
Dump: lvol3 on: /dev/dsk/c2t0d0, 0

..

...

working server

/dev/vg00/lvol1 1009705 90555 818179 10% /stand
/dev/vg00/lvol4 1032192 568752 459856 55% /
dev/vg00/lvol5 4096000 19400 4045968 0% /tmp
/dev/vg00/lvol6 8192000 5193128 2975520 64% /opt
/dev/vg00/lvol7 8192000 2888088 5262648 35% /usr
/dev/vg00/lvol8 8192000 5232664 2937128 64% /var
/dev/vg00/lvol9 12288000 2122755 9529965 18% /var/adm/crash
/dev/vg00/lvol10 2048000 1049716 935902 53% /home

[feigenL]

Hello there, mirror disk is good option but it requires more time and effort. You may also consider using DRD Clones.

DRD clone allows you clone the boot disk exactly as it is and then you can just use it on the other server.

Here's the download link: https://myenterpriselicense.hpe.com/cwp-ui/product-details/DRD/A.3.17.65/sw_free

and here's a quick guide:  https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&ved=2ahUKEwiGp5j0yvf8AhU5RDABHQmzAyoQFnoECBcQAQ&url=https%3A%2F%2Fcommunity.hpe.com%2Fhpeb%2Fattachments%2Fhpeb%2Fitrc-855%2F2096%2F1%2F355758.pdf&usg=AOvVaw0BgPdUfLmmwdtkJZFqNCcx

Regards.

[cokehpux]

[root@:~]# swlist -l product|grep -i drd
DRD A.1.1.0.344 Dynamic Root Disk
[root@:~]#

DRD already present

will go though the doc you shared

thank you

[cokehpux]

I am following that document DRD

/var/opt/drd/drd.log is not very encouraging as I see old logs where there were many errors

also today I did this preview - taking a lot of time

[~]# /opt/drd/bin/drd clone -p -v -t /dev/dsk/c3t0d0

--

Just want to be ready with third mirror strategy if this DRD doesnt work

I would appreciate if I can get some inpts for third mirroring steps

Many thanks

[feigenL]

Here you go:

HP 9000 11i v1 (11.11) / 11i v2 (11.23)

1. Identify the available disk to mirror the vg00 logical volumes.

# strings /etc/lvmtab | grep dev
/dev/vg00
/dev/dsk/c3t3d0

# ioscan -funC disk
disk      0  1/0/1/0/0/1/3.0.6   sdisk    CLAIMED     DEVICE       HP 36.4GST336607FC
                           /dev/dsk/c3t6d0   /dev/rdsk/c3t6d0
disk      1  1/0/1/0/0/1/3.#.0   sdisk    CLAIMED     DEVICE       HP 36.4GST336607FC
                           /dev/dsk/c#t#d#   /dev/rdsk/c#t#d#

2. Create and populate the boot disk LIF area. Be sure to use the "-B" flag to allocate space for the BDRA

# pvcreate -fB /dev/rdsk/c#t#d#
# mkboot /dev/rdsk/c#t#d#

3. Change the AUTO file on both boot disks to hpux -lq so the host can boot without quorum if one mirror disk fails.

# mkboot -a "hpux -lq" /dev/rdsk/c#t#d#
# mkboot -a "hpux -lq" /dev/rdsk/c#t#d#

4. Check the boot string in the AUTO file. This command should output: "hpux -lq"

# /usr/bin/lifcp /dev/rdsk/c#t#d#:AUTO -

5. Add the disk to vg00.

# vgextend vg00 /dev/dsk/c#t#d#

6. Mirror all vg00 logical volumes

# lvextend -m 1 /dev/vg00/lvol# /dev/dsk/c#t#d#

7. Verify that the BDRA is up to date.

# lvlnboot -R

8. Add a line to /stand/bootconf so SD-UX knows which disks are boot disks.

# vi /stand/bootconf
l /dev/dsk/c#t#d#
l /dev/dsk/c#t#d#

9. Configure the second disk as an alternate boot path in the system NVRAM.

# setboot -p #/#/#/#/#.#.#
# setboot -a #/#/#/#/#.#.#

10. Check the status of the NVRAM configuration.

# setboot

[cokehpux]

thank you

in my server there are two boot disks - mirrored

I need to add a third disk now: /dev/rdsk/c3t0d0

disk 1 0/1/1/0.0.0 sdisk CLAIMED DEVICE HP 73.4GMAX3073NC
/dev/dsk/c2t0d0 /dev/rdsk/c2t0d0 (boot disk1)
disk 17 0/1/1/0.1.0 sdisk CLAIMED DEVICE HP 73.4GST373455LC
/dev/dsk/c2t1d0 /dev/rdsk/c2t1d0 (mirrored boot disk2)

disk 428 0/1/1/1.0.0 sdisk CLAIMED DEVICE SEAGATE ST3146855LC
/dev/dsk/c3t0d0 /dev/rdsk/c3t0d0 (new empty blank disk to be mirrored)

[root:~]# strings /etc/lvmtab | grep dev
/dev/vg00
/dev/dsk/c2t0d0
/dev/dsk/c2t1d0

[root:~]# lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c2t0d0 (0/1/1/0.0.0) -- Boot Disk
/dev/dsk/c2t1d0 (0/1/1/0.1.0) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c2t0d0
Root: lvol4 on: /dev/dsk/c2t0d0
Swap: lvol2 on: /dev/dsk/c2t0d0
Dump: lvol3 on: /dev/dsk/c2t0d0, 0

Like I said above - I need to add a third disk now: /dev/rdsk/c3t0d0 to this VG00 to mirror

so that I ca use this newly mirrored disk to be used as a boot disk in another server

# pvcreate -fB /dev/rdsk/c3t0d0
# mkboot /dev/rdsk/c3t0d0

mkboot -a "hpux -lq" /dev/rdsk/c3t0d0

# /usr/bin/lifcp /dev/rdsk/c3t0d0:AUTO -  

vgextend vg00 /dev/dsk/c3t0d0

lvextend -m 2 /dev/vg00/lvol# /dev/dsk/c3t0d0  (use 2 instead of 1 as this will be third disk?)

# lvlnboot -R

# vi /stand/bootconf
1 /dev/dsk/c2t0d0  (existing line)
l /dev/dsk/c3t0d0 (newly added line)

# setboot -p 0/1/1/1.0.0 (new disk path?)

Once I have a boot image in this third disk.... I need to remove it from server1, insert it in another server(server2) in the same DC

Use this disk to boot up that server2

so before remving this newly mirrored disk from server1, do I need to break the mirror and then take it out?

[feigenL]

Hello, thanks for the kudos.

To break the mirror, try with this sequence:

# lvreduce -m 1 /dev/vg00/lvol8 /dev/dsk/c2t2d0 ---use your disk id
# lvreduce -m 1 /dev/vg00/lvol7 /dev/dsk/c2t2d0
# lvreduce -m 1 /dev/vg00/lvol6 /dev/dsk/c2t2d0
# lvreduce -m 1 /dev/vg00/lvol5 /dev/dsk/c2t2d0
# lvreduce -m 1 /dev/vg00/lvol4 /dev/dsk/c2t2d0
# lvreduce -m 1 /dev/vg00/lvol3 /dev/dsk/c2t2d0
# lvreduce -m 1 /dev/vg00/lvol2 /dev/dsk/c2t2d0
# lvreduce -m 1 /dev/vg00/lvol1 /dev/dsk/c2t2d0

 Reduce the physical volume from the volume group using "vgreduce /dev/vg00 /dev/dsk/c#t#d0" command. Remember to specific the physical volume that will be removed.

# vgreduce /dev/vg00 /dev/dsk/c2t2d0

 Finally remove LVM headers from the physical volume using "pvremove /dev/rdsk/c#t#d#" command. Remember to use the character (raw) device special file.

# pvremove /dev/rdsk/c2t2d0

I know there's another command, lvsplit, but I am not quite familiar with it, but this really old thread may be usefull

https://community.hpe.com/t5/lvm-and-vxvm/how-to-break-a-root-mirror/td-p/4791899

Regards.

[cokehpux]

thank you

I think I understood that mirror break part

can you try to verify my steps that I posted earlier...the steps to mirror this third disk 

vg00 has two disks already

need to add third disk - mirror it

then break it away - take it away to another server and boot that another server is the plan

[shiva_jr]

Hi cokehpux,
    we have the video on mirroring the root disk, please find the link below-
HP-UX - How to mirror a LVM root disk using Command Line Interface (CLI)

Regards,
SHIVA_JR

[cokehpux]

thank you

but my servers are running 11.23 and they are PA RISC (9000/800/rp3440)

the server already has two mirrored root disks

I want to add another/third disk to the mirror...then break it....then take this third root disk to boot aother server 

[cokehpux]

DRD clone completed. then to use this clone to boot ANOTHER server, apparently i need drd rehost..

drd rehost works only for integrity servers and my server is PA RISC.....so - drd clone is not viable now

=====

I have mirrored the disk now with the exiting two root disks

now my server has three mirrored disks and i need to break this third disk from mirror to use it to boot ANOTHER server

any suggestions pls like how do we do this?

[root@parisc:~]# strings /etc/lvmtab | grep dev|more
/dev/vg00
/dev/dsk/c2t0d0
/dev/dsk/c2t1d0
...
[root@parisc:~]# pvcreate -fB /dev/rdsk/c3t0d0   (nwly added disk )
Physical volume "/dev/rdsk/c3t0d0" has been successfully created.
[root@parisc:~]#
[root@parisc:~]# mkboot /dev/rdsk/c3t0d0
[root@parisc:~]# mkboot -a "hpux -lq" /dev/rdsk/c2t0d0 - existing root disk
[root@parisc:~]# mkboot -a "hpux -lq" /dev/rdsk/c2t1d0 - existing root disk
[root@parisc:~]# mkboot -a "hpux -lq" /dev/rdsk/c3t0d0 - new disk
[root@parisc:~]#
[root@parisc:~]# /usr/bin/lifcp /dev/rdsk/c3t0d0:AUTO -
hpux -lq
[root@parisc:~]#
[root@parisc:~]# vgextend vg00 /dev/dsk/c3t0d0
vgextend: Warning: Max_PE_per_PV for the volume group (4384) too small for this PV (8750).
Using only 4384 PEs from this physical volume.
Volume group "vg00" has been successfully extended.
...
[root@parisc:~]#
[root@parisc:~]# /usr/bin/lifcp /dev/rdsk/c2t0d0:AUTO -
hpux -lq
[root@parisc:~]# /usr/bin/lifcp /dev/rdsk/c2t1d0:AUTO -
hpux -lq
[root@parisc:~]# /usr/bin/lifcp /dev/rdsk/c3t0d0:AUTO -
hpux -lq
[root@parisc:~]#
[root@parisc:~]# lvextend -m 2 /dev/vg00/lvol1 /dev/dsk/c3t0d0
The newly allocated mirrors are now being synchronized. This operation will
take some time. Please wait ....
Logical volume "/dev/vg00/lvol1" has been successfully extended.
Volume Group configuration for /dev/vg00 has been saved in /etc/lvmconf/vg00.conf
[root@parisc:~]#
...
...
...
[root@parisc:~]# lvextend -m 2 /dev/vg00/lvol10 /dev/dsk/c3t0d0
The newly allocated mirrors are now being synchronized. This operation will
take some time. Please wait ....
Logical volume "/dev/vg00/lvol10" has been successfully extended.
Volume Group configuration for /dev/vg00 has been saved in /etc/lvmconf/vg00.conf
[root@parisc:~]#
[root@parisc:~]#
[root@parisc:~]# vgdisplay -v vg00|egrep "LV Name| Used PV"
LV Name /dev/vg00/lvol1
Used PV 3
LV Name /dev/vg00/lvol2
Used PV 3
LV Name /dev/vg00/lvol3
Used PV 3
LV Name /dev/vg00/lvol4
Used PV 3
LV Name /dev/vg00/lvol5
Used PV 3
LV Name /dev/vg00/lvol6
Used PV 3
LV Name /dev/vg00/lvol7
Used PV 3
LV Name /dev/vg00/lvol8
Used PV 3
LV Name /dev/vg00/lvol9
Used PV 3
LV Name /dev/vg00/lvol10
Used PV 3
[root@parisc:~]#

[root@parisc:~]# lvlnboot -R /dev/vg00
Volume Group configuration for /dev/vg00 has been saved in /etc/lvmconf/vg00.conf
[root@parisc:~]#
[root@parisc:~]# strings /etc/lvmconf/vg00.conf
CONFIG01
/dev/vg00
/dev/rdsk/c2t0d0
/dev/rdsk/c2t1d0
/dev/rdsk/c3t0d0
LVMREC01
HPLVMBDRc
LVMREC01
HPLVMBDRc
LVMREC01
HPLVMBDRc
VGDA0001
VGSA0001c
[root@parisc:~]# cat /stand/bootconf
l /dev/dsk/c2t0d0
[root@parisc:~]# lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c2t0d0 (0/1/1/0.0.0) -- Boot Disk
/dev/dsk/c2t1d0 (0/1/1/0.1.0) -- Boot Disk
/dev/dsk/c3t0d0 (0/1/1/1.0.0) -- Boot Disk (new disk)
Boot: lvol1 on: /dev/dsk/c2t0d0
/dev/dsk/c2t1d0
/dev/dsk/c3t0d0
Root: lvol4 on: /dev/dsk/c2t0d0
/dev/dsk/c2t1d0
/dev/dsk/c3t0d0
Swap: lvol2 on: /dev/dsk/c2t0d0
/dev/dsk/c2t1d0
/dev/dsk/c3t0d0
Dump: lvol3 on: /dev/dsk/c2t0d0, 0

[root@parisc:~]# setboot
Primary bootpath : 0/1/1/0.0.0
Alternate bootpath : 0/1/1/0.1.0

Autoboot is ON (enabled)
Autosearch is ON (enabled)

[root@parisc:~]#

[cokehpux]

the inserted new disk –  has been mirrored with the two existing root disks

to test if this disk is good enough to be used to boot another server....i wanted to test it this same server

Restarted server. Interrupted boot process

Tried to boot the server with the newly mirrored root disk (new disk)

The server did not boot

Main Menu: Enter command or menu > BO 0/1/1/1.0.0
Interact with IPL (Y, N, or Cancel)?> Y

Booting...
Not a valid boot device (DEV CLASS ERR).
.... FAILED.

 The server, when tested, successfully boots up with existing two root disks, but not with this new disk

any comments pls, suggestions please ?

[cokehpux]

[root@:~]# lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c2t0d0 (0/1/1/0.0.0) -- Boot Disk
/dev/dsk/c2t1d0 (0/1/1/0.1.0) -- Boot Disk
/dev/dsk/c3t0d0 (0/1/1/1.0.0) -- Boot Disk =======> newly mirrored disk

Processor is booting from the first available device.

To discontinue, press any key within 10 seconds.

Boot terminated.

---- Main Menu ---------------------------------------------------------------

Command Description
------- -----------
BOot [PRI|ALT|<path>] Boot from specified path
PAth [PRI|ALT] [<path>] Display or modify a path
SEArch [DIsplay|IPL] [<path>] Search for boot devices

COnfiguration menu Displays or sets boot values
INformation menu Displays hardware information
SERvice menu Displays service commands

DIsplay Redisplay the current menu
HElp [<menu>|<command>] Display help for menu or command
RESET Restart the system
----
Main Menu: Enter command or menu > BO 0/1/1/1.0.0
Interact with IPL (Y, N, or Cancel)?> Y

Booting...
Not a valid boot device (DEV CLASS ERR).
.... FAILED.

---- Main Menu ---------------------------------------------------------------

Command Description
------- -----------
BOot [PRI|ALT|<path>] Boot from specified path
...

...

[cokehpux]

disk      1  0/1/1/0.0.0     sdisk      CLAIMED     DEVICE       HP 73.4GMAX3073NC

                            /dev/dsk/c2t0d0   /dev/rdsk/c2t0d0 (primary boot disk)

disk     17  0/1/1/0.1.0     sdisk      CLAIMED     DEVICE       HP 73.4GST373455LC

                            /dev/dsk/c2t1d0   /dev/rdsk/c2t1d0  (alternate boot disk)

disk    428  0/1/1/1.0.0     sdisk      CLAIMED     DEVICE       SEAGATE ST3146855LC

                            /dev/dsk/c3t0d0   /dev/rdsk/c3t0d0   (new third mirror disk)

[root@:~]# lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c2t0d0 (0/1/1/0.0.0) -- Boot Disk
/dev/dsk/c2t1d0 (0/1/1/0.1.0) -- Boot Disk
/dev/dsk/c3t0d0 (0/1/1/1.0.0) -- Boot Disk (newly mirrored - third disk)
Boot: lvol1 on: /dev/dsk/c2t0d0
/dev/dsk/c2t1d0
/dev/dsk/c3t0d0
Root: lvol4 on: /dev/dsk/c2t0d0
/dev/dsk/c2t1d0
/dev/dsk/c3t0d0
Swap: lvol2 on: /dev/dsk/c2t0d0
/dev/dsk/c2t1d0
/dev/dsk/c3t0d0
Dump: lvol3 on: /dev/dsk/c2t0d0, 0

unable to boot up the server using that third disk and also  I do not see this new disk in SEA IPL

Primary boot path: 0/1/1/0.0
Alternate boot path: 0/1/1/0.1
Console path: 0/7/1/1.0
Keyboard path: 0/0/4/0.0

Processor is booting from the first available device.

To discontinue, press any key within 10 seconds.

Boot terminated.

---

---

Main Menu: Enter command or menu > SEA IPL

Searching for device(s) with bootable media
This may take several minutes.

To discontinue search, press any key (termination may not be immediate).

IODC
Path# Device Path (dec) Device Path (mnem) Device Type and Utilities Rev
----- ----------------- ------------------ ------------------------- ----
P0 0/1/1/0.1 intscsia.1 Random access media 1
IPL
P1 0/1/1/0.0 intscsia.0 Random access media 1
IPL

Main Menu: Enter command or menu >

[feigenL]

Well, it seems that something went wrong while creating the 3rd mirror copy, as the destination disk doesn't seem to have the boot structures.

You may try to mirror it one more time and then try again.

As stated before, you may try to use DRD Clone (for 11.23 there's no rehost support), but I know that the clone will boot on the other server, though you need to boot it into single user mode to change both the hostname and the IP address.

You may also check this old thread with the same inquiry:

https://community.hpe.com/t5/lvm-and-vxvm/how-to-mirror-another-disk-to-create-a-three-way-mirror/td-p/2751981

Best regards.

[cokehpux]

@feigenL 

are you saying

i drdclone the disk\

take it out

insert it in another server

boot it in single user mode and change hostname ip address etc

is there any documentation for that?

====

yes i checked that link earlier.... i followed standard process to mirror the third disk - unfortunately it did not work

[cokehpux]

are you saying.. i drdclone the disk ... then I simply take it out ? execute any commands before removing the disk from the slot?

then insert it in another server

boot it in single user mode and change hostname ip address etc

is there any documentation for that?

==

also - I will try mirroring again

[cokehpux]

I used another disk

followed the standard mirroring process

booted successfully using the newly mirrored disk

Now I need to work - to split the mirror

remove that third disk and use it to boot antoher server

 lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c2t0d0 (0/1/1/0.0.0) -- Boot Disk (pri boot)
/dev/dsk/c2t1d0 (0/1/1/0.1.0) -- Boot Disk (alt boot)
/dev/dsk/c3t2d0 (0/1/1/1.2.0) -- Boot Disk (newly mirrored disk to be used to boot another server)

need to remove c3t2d0 and use it to boot other server in the same DC

any help pls ?

[feigenL]

I think this should be useful

lvreduce -m 0 /dev/vg00/lvol8 /dev/dsk/c3t2d0
lvreduce -m 0 /dev/vg00/lvol7 /dev/dsk/c3t2d0
lvreduce -m 0 /dev/vg00/lvol6 /dev/dsk/c3t2d0
lvreduce -m 0 /dev/vg00/lvol5 /dev/dsk/c3t2d0
lvreduce -m 0 /dev/vg00/lvol4 /dev/dsk/c3t2d0
lvreduce -m 0 /dev/vg00/lvol3 /dev/dsk/c3t2d0
lvreduce -m 0 /dev/vg00/lvol2 /dev/dsk/c3t2d0
lvreduce -m 0 /dev/vg00/lvol1 /dev/dsk/c3t2d0

vgreduce /dev/vg00 /dev/dsk/c3t2d0
pvremove /dev/rdsk/c3t2d0

[cokehpux]

If you remember I have three disks in vg00

sO I will user -m 1 instead of -m 0

However the real question is - once I do this lvreduce, vgreduce and pvremove

can I remove this disk from its slot in the current server, insert it in another server's disk slot and boot it up?

that is question # 1

question # 2

if this c3t2d0 boots on other server (at the moment this server has no disks  in it - needs a build)

do I boot into single user mode, edit hostname IP etc ?

[# strings /etc/lvmtab|more
/dev/vg00
/dev/dsk/c2t0d0 ( pri )
/dev/dsk/c2t1d0 (alt)
/dev/dsk/c3t2d0 (newly added mirror)

lvreduce -m 1 /dev/vg00/lvol8 /dev/dsk/c3t2d0
lvreduce -m 1 /dev/vg00/lvol7 /dev/dsk/c3t2d0

...
lvreduce -m 1 /dev/vg00/lvol1 /dev/dsk/c3t2d0

vgreduce /dev/vg00 /dev/dsk/c3t2d0
pvremove /dev/rdsk/c3t2d0

[cokehpux]

lvreduce, vgreduce and pvremove

after this - pulled out the disk from one server and inserted it in another server with no disk

powered on that other server

it booted (or no?) then it crashed

Main Menu: Enter command or menu > 0/1/1/0.0

ERROR: Unknown command

Main Menu: Enter command or menu > BO 0/1/1/0.0

Interact with IPL (Y, N, or Cancel)?> Y

Booting...

Boot IO Dependent Code (IODC) revision 1

HARD Booted.

ISL Revision A.00.44  Mar 12, 2003

ISL> hpux -is

Boot

: disk(0/1/1/0.0.0.0.0.0.0;0)/stand/vmunix

15372288 + 4534272 + 6867048 start 0x22e3e8

alloc_pdc_pages: Relocating PDC from 0xfffffff0f0c00000 to 0x3e900000.

DoCalllist done

Memory Class Setup

-------------------------------------------------------------------------

Class     Physmem              Lockmem              Swapmem

-------------------------------------------------------------------------

System :  4094 MB              4094 MB              4094 MB

Kernel :  4094 MB              4094 MB              4094 MB

User   :  3692 MB              3216 MB              3228 MB

-------------------------------------------------------------------------

Warning: Setting the expanded_node_host_names parameter to 1 will allow administrators to set node and host names larger than 8 an                                      d 64 characters/bytes, respectively.  It is strongly recommended that all the documentation included with the NodeHostNameXpnd pro                                      duct bundle be understood before setting larger names. Larger names can cause some applications which use those names to exhibit a                                      nomalous or incorrect behavior.

gate64: sysvec_vaddr = 0xc0002000 for 2 pages

NOTICE: cachefs_link(): File system was registered at index 4.

NOTICE: nfs3_link(): File system was registered at index 7.

igelan0: INITIALIZING HP PCI 1000Base-T Core at hardware path 0/1/2/0

iether2: INITIALIZING HP A7012-60601 PCI/PCI-X 1000Base-T Dual-port Adapter at hardware path 0/3/1/0

iether3: INITIALIZING HP A7012-60601 PCI/PCI-X 1000Base-T Dual-port Adapter at hardware path 0/3/1/1

iether4: INITIALIZING HP A7012-60601 PCI/PCI-X 1000Base-T Dual-port Adapter at hardware path 0/4/1/0

iether5: INITIALIZING HP A7012-60601 PCI/PCI-X 1000Base-T Dual-port Adapter at hardware path 0/4/1/1

    System Console is on the Built-In Serial Interface

WARNING: ROOT device 0x1f020000 is a non-LVM partition, disallowed on LVM disk.

WARNING: ROOT device 0x1f020000 has been deconfigured (set to 0xffffffff).

        -----------------------------------------------------

        |                                                   |

        |       SYSTEM HALTING during LVM Configuration     |

        |                                                   |

                Non-lvm root on LVM disk

        |                                                   |

        -----------------------------------------------------

linkstamp:          Mon Jul 02 12:58:23 BST 2018

_release_version:   @(#) $Revision: vmunix:    B11.23_LR FLAVOR=perf Fri Mar 19 15:24:05 PST 2004 $

panic: LVM: Configuration failure

PC-Offset Stack Trace (read down, top of stack is 1st):

  0x00834420 (panic+0xc0)

  0x00699084 (lv_boothalt+0x7c)

  0x00698bac (lv_check_boot+0xfc)

  0x00698f50 (lvmconf_body+0x1f0)

  0x0070007c (lvmconf+0x24)

  0x0069cff8 (im_lvmconf+0x28)

  0x008b7108 (DoCalllist+0x100)

  0x0069ed88 (main+0x28)

  0x0012d4fc ($vstart+0x48)

  0x0022e9e0 (istackatbase+0x88)

End Of Stack

Firmware Version  50.40

Duplex Console IO Dependent Code (IODC) revision 1

Stored message buffer up to panic:

Warning: Setting the expanded_node_host_names parameter to 1 will allow administrators to set node and host names larger than 8 and 64 characters/bytes, respectively.  It is strongly recommended that all the documentation included with the NodeHostNameXp

nd product bundle be understood before setting larger names. Larger names can cause some applications which use those names to exhibit anomalous or incorrect behavior.

gate64: sysvec_vaddr = 0xc0002000 for 2 pages

NOTICE: cachefs_link(): File system was registered at index 4.

255/0 ms_fake_drv

NOTICE: nfs3_link(): File system was registered at index 7.

255/2 rdsk_root

0 sba

0/0 lba

0/0/1/0 hcd

0/0/1/1 hcd

0/0/1/2 ehci

0/0/2/0 side_multi

0/0/2/0.0 side

0/0/2/0.0.0 tgt

0/0/2/0.0.0.0 sdisk

0/0/2/0.0.7 tgt

0/0/2/0.0.7.0 sctl

0/0/2/0.1 side

0/0/2/0.1.7 tgt

0/0/2/0.1.7.0 sctl

0/1 lba

c8xx BUS: 2 SCSI C1010 Ultra160 Wide LVD  assigned CPU: 1

0/1/1/0 c8xx

c8xx BUS: 3 SCSI C1010 Ultra160 Wide LVD  assigned CPU: 0

0/1/1/1 c8xx

0/1/2/0 igelan

0/2 lba

0/3 lba

0/3/1/0 iether

0/3/1/1 iether

0/4 lba

0/4/1/0 iether

0/4/1/1 iether

0/6 lba

0/7 lba

0/7/1/0 asio0

0/7/1/1 asio0

8 memory

16 ipmi

128 processor

129 processor

0/1/1/0.0 tgt

0/1/1/0.0.0 sdisk

0/1/1/0.7 tgt

0/1/1/0.7.0 sctl

0/1/1/1.7 tgt

0/1/1/1.7.0 sctl

255/1 mass_storage

255/1/0 usb_ms_scsi

igelan0: INITIALIZING HP PCI 1000Base-T Core at hardware path 0/1/2/0

iether2: INITIALIZING HP A7012-60601 PCI/PCI-X 1000Base-T Dual-port Adapter at hardware path 0/3/1/0

iether3: INITIALIZING HP A7012-60601 PCI/PCI-X 1000Base-T Dual-port Adapter at hardware path 0/3/1/1

iether4: INITIALIZING HP A7012-60601 PCI/PCI-X 1000Base-T Dual-port Adapter at hardware path 0/4/1/0

iether5: INITIALIZING HP A7012-60601 PCI/PCI-X 1000Base-T Dual-port Adapter at hardware path 0/4/1/1

    System Console is on the Built-In Serial Interface

WARNING: ROOT device 0x1f020000 is a non-LVM partition, disallowed on LVM disk.

WARNING: ROOT device 0x1f020000 has been deconfigured (set to 0xffffffff).

        -----------------------------------------------------

        |                                                   |

        |       SYSTEM HALTING during LVM Configuration     |

        |                                                   |

                Non-lvm root on LVM disk

        |                                                   |

        -----------------------------------------------------

System Panic:

linkstamp:          Mon Jul 02 12:58:23 BST 2018

_release_version:   @(#) $Revision: vmunix:    B11.23_LR FLAVOR=perf Fri Mar 19 15:24:05 PST 2004 $

panic: LVM: Configuration failure

PC-Offset Stack Trace (read down, top of stack is 1st):

  0x00834420 (panic+0xc0)

  0x00699084 (lv_boothalt+0x7c)

  0x00698bac (lv_check_boot+0xfc)

  0x00698f50 (lvmconf_body+0x1f0)

  0x0070007c (lvmconf+0x24)

  0x0069cff8 (im_lvmconf+0x28)

  0x008b7108 (DoCalllist+0x100)

  0x0069ed88 (main+0x28)

  0x0012d4fc ($vstart+0x48)

  0x0022e9e0 (istackatbase+0x88)

End Of Stack

sync'ing disks (0 buffers to flush): (0 buffers to flush):

0 buffers not flushed

0 buffers still dirty

*** A system crash has occurred. (See the above messages for details.)

*** The system is now preparing to dump physical memory to disk, for use

*** in debugging the crash.

ERROR:  Your system crashed before I/O and dump configuration was complete.

        A crash dump cannot be taken under these circumstances without

        special configuration.  Contact your HP support representative.

[feigenL]

Try to boot into LVM Maintenance Mode: ISL> hpux -lm

if succeeded, then try this:

If positive, you can use ioscan -funCdisk to find all the disks you can see, and lifls /dev/dsk/cXtYdZ to identify the boot disk (it will be the one with a LIF partition containing the Initial System Loader (ISL), bootstrap kernel (HPUX) and auto-boot file (AUTO).

Once you know the new name of your boot disk, remove the existing config for vg00 by running:

vgexport -m /vg00.map /dev/vg00

Then re-create by doing the following:

mkdir /dev/vg00
mknod /deb/vg00/group c 64 0x000000
vgimport -m /vg00.map /dev/vg00 /dev/dsk/cXtYdZ
vgchange -a y vg00
vgcfgbackup vg00
vgchange -a n vg00

That should be good to go. Don't forget to update ypur NVRAM using setboot as well.

Taken from this POST: https://community.hpe.com/t5/system-administration/booting-into-maintenance-mode-isl-gt-hpux-lm/m-p/3570155#M228037

Hope this helps.

[cokehpux]

what is going wrong here

mirrir disk, drdclone - both techniques did not help in booting the other server

however - on the orginal server, when I boot using this mirrored disk (newly added third disk) original server bootsup

take it out and use it to boot another server - the other server doesnt boot

same is the case with drd clone

drd clone completed..I rebooted server, interuupted boot process....select clone disk to boot up the original server

the server boots.

but the same disk - is nto booting up when placed in another server

serverthird mirrored disk

i did lvreduce, vgreduce, pvremove

took the disk out, inserted in another server

i get this error after I enter hpux -is

 SYSTEM HALTING during LVM Configuration     |

        |                                                   |

                Non-lvm root on LVM disk

===

I used the same disk, did drdclone

shutdown original server. pull out cloned disk

insert it in anothe server - boot it up

fails to boot. got this:

System Console is on the Built-In Serial Interface
WARNING: ROOT device 0x1f021000 is a non-LVM partition, disallowed on LVM disk.
WARNING: ROOT device 0x1f021000 has been deconfigured (set to 0xffffffff).

-----------------------------------------------------
| |
| SYSTEM HALTING during LVM Configuration |
| |
Non-lvm root on LVM disk
| |
-----------------------------------------------------

linkstamp: Mon Jul 02 12:58:23 BST 2018
_release_version: @(#) $Revision: vmunix: B11.23_LR FLAVOR=perf Fri Mar 19 15:24:05 PST 2004 $
panic: LVM: Configuration failure

[cokehpux]

tried mirror again

server1 - two mirrored root disks exist. inserted third disk. mirrored it.

lvlnboot shows three boot disks. did server shutdown. directly removed the disk.

inserted it in another server. other server booted (this is acheived after two failed attempts to boot other server)

now server1 thinks it has three root disks. need to do some config changes to make sure there are only two boto disks

in server2 - did set_parms, changed hostname IP etc...server thinks it has three boot disks - but has only one.

need to work there also.

lvmtab, vgscan -v etc - need to be careful before I execute - I beleive - working on it.

[feigenL]

Hello there again! Glad to see good progress on this matter. Old PA_RISC systems weren't as friendly as I recall when it comes to cloning....

In order to remove the "ghost" disks on both systems, you should try to lvreduce and vgreduce the removed disks and see if it'll work.

If it doesn't, maybe the system is interpreting as a hardware failure on the disks. There were a really useful HPE document from HPE call "When Good disks go Bad".

https://support.hpe.com/hpesc/public/docDisplay?docId=c01911837&docLocale=en_US

Take a look at it and see if that is helpful.

Best regards.