topic Re: drd clone failure ...... in Operating System - HP-UX

drd clone failure ......

hpuxrocks — Fri, 06 May 2011 11:50:17 GMT

Hi

Heres the problem.

(rx6600 : HP-UX rex B.11.31 U ia64 -> DRD B.1131.A.3.4.39 Dynamic Root Disk)

rex:/dev/disk# drd clone -t /dev/disk/disk28 -x verbosity=5

======= 05/06/11 17:42:38 PST BEGIN Clone System Image (user=root) (jobid=rex)

* Reading Current System Information
* Selecting System Image To Clone
* Converting legacy DSF "/dev/dsk/c0t0d0" to "/dev/disk/disk13"
* Selecting Target Disk
ERROR: Selection of the target disk fails.
- Selecting the target disk fails.
- Validation of the disk "/dev/disk/disk28" fails with the following error(s):
- The device special file "/dev/disk/disk0" does not represent a disk.
* Selecting Target Disk failed with 1 error.

======= 05/06/11 17:42:45 PST END Clone System Image failed with 1 error. (user=root) (jobid=rex)

When I checked disk0, I found ....

rex:/dev/disk# ioscan -m dsf /dev/disk/disk13_p2
Persistent DSF Legacy DSF(s)
========================================
/dev/disk/disk13_p2 /dev/dsk/c0t0d0s2
rex:/dev/disk# ioscan -m dsf /dev/disk/disk0_p2
Persistent DSF Legacy DSF(s)
========================================
/dev/disk/disk0_p2 /dev/dsk/c0t0d0s2

and

rex:/dev/disk# lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/disk/disk13_p2 -- Boot Disk
Boot: lvol1 on: /dev/disk/disk13_p2
Root: lvol3 on: /dev/disk/disk13_p2
Swap: lvol2 on: /dev/disk/disk13_p2
Dump: lvol2 on: /dev/disk/disk13_p2, 0

and
rex:/dev/disk# ll | grep disk13
brw-r----- 1 bin sys 1 0x000001 Jun 29 2010 disk13
brw-r----- 1 bin sys 1 0x000008 Jun 29 2010 disk13_p1
brw-r----- 1 bin sys 1 0x000009 Jun 29 2010 disk13_p2
brw-r----- 1 bin sys 1 0x00000a Jun 29 2010 disk13_p3
rex:/dev/disk# ll | grep disk0
brw-r----- 1 bin sys 1 0x000001 Jul 9 2010 disk0
brw-r----- 1 bin sys 1 0x000008 Jul 9 2010 disk0_p1
brw-r----- 1 bin sys 1 0x000009 Jul 9 2010 disk0_p2
brw-r----- 1 bin sys 1 0x00000a Jul 9 2010 disk0_p3

So the boot disc is mapped to disk13 rather than disk0 and drd clearly wants to
See disk0. Is there a way round this ?

As an aside

How would we go about removing / swapping the
boot dsfs to disk0 ?

Many thks in advance

Re: drd clone failure ......

Michael Steele_2 — Fri, 06 May 2011 12:15:02 GMT

Looks like you're booted off of the mirror instead of the primary.

echo 'boot_string/s' | adb /stand/vmunix /dev/mem

-or-

echo 'boot_string/s' | adb -o /stand/vmunix /dev/mem

-or-

echo "boot_string/S" | adb -k /stand/vmunix /dev/kmem

Depending on the version adb needs a -o or -k or nothing

Re: drd clone failure ......

hpuxrocks — Fri, 06 May 2011 13:57:27 GMT

Hi

actually all those failed but heres what I did do:

cat /stand/bootconf
l /dev/disk/disk0_p2
l /dev/disk/disk13_p2

setboot
Primary bootpath : 0/6/0/0/0/0/4/0/0/0.0x0.0x4000000000000000 (/dev/rdisk/disk13)
HA Alternate bootpath : 0/6/0/0/0/0/4/0/0/0.0x0.0x4000000000000000 (/dev/rdisk/disk13)
Alternate bootpath : 0/6/0/0/0/0/4/0/0/0.0x0.0x4000000000000000 (/dev/rdisk/disk13)

Autoboot is ON (enabled)
Hyperthreading : ON
: ON (next boot)

Now I did a
setboot -p /dev/disk/disk0 -b on

and the next setboot produced exactly the same result.

The root/ boot discs are mirrored but using the SmartArray RAID Controller.

So what confuses me now is that
ioscan -funC disk shows

disk 18 0/6/0/0/0/0/4/0/0/0.0.0 sdisk CLAIMED DEVICE HP LOGICAL VOLUME
/dev/dsk/c0t0d0 /dev/dsk/c0t0d0s2 /dev/rdsk/c0t0d0 /dev/rdsk/c0t0d0s2
/dev/dsk/c0t0d0s1 /dev/dsk/c0t0d0s3 /dev/rdsk/c0t0d0s1 /dev/rdsk/c0t0d0s3

So from the bootconf file, it sees 2 discs. The setboot command returns no errors but doesnt update the boot paths (there is only 1 ....is this why). Given that there is hardware mirroring, is this normal behaviour ?

How do I check what physical disc is being used as the boot disc ? (bear in mind its not mirrored via LVM)?

Has the setboot command worked but not "updated" ?

thks

Re: drd clone failure ......

hpuxrocks — Fri, 06 May 2011 14:02:13 GMT

Another "strange thing" , below is the output from another machine configure (mirrored ) in the same way ...

disk 0 64000/0xfa00/0x1 esdisk CLAIMED DEVICE online HP LOGICAL VOLUME
0/6/0/0/0/0/4/0/0/0.0x0.0x4000000000000000
/dev/disk/disk0 /dev/disk/disk0_p2 /dev/rdisk/disk0 /dev/rdisk/disk0_p2
/dev/disk/disk0_p1 /dev/disk/disk0_p3 /dev/rdisk/disk0_p1 /dev/rdisk/disk0_p3

the equivalent on the problem machine is ..

disk 0 64000/0xfa00/0x1 esdisk CLAIMED DEVICE online HP LOGICAL VOLUME
0/6/0/0/0/0/4/0/0/0.0x0.0x4000000000000000
/dev/disk/disk0 /dev/disk/disk0_p3 /dev/disk/disk13_p2 /dev/rdisk/disk0_p1 /dev/rdisk/disk13 /dev/rdisk/disk13_p3
/dev/disk/disk0_p1 /dev/disk/disk13 /dev/disk/disk13_p3 /dev/rdisk/disk0_p2 /dev/rdisk/disk13_p1
/dev/disk/disk0_p2 /dev/disk/disk13_p1 /dev/rdisk/disk0 /dev/rdisk/disk0_p3 /dev/rdisk/disk13_p2
...

How come the latter shows another set of persistent names but not the former (that I managed to clone via drd btw ) ?

thks

Re: drd clone failure ......

hpuxrocks — Fri, 06 May 2011 14:06:02 GMT

Another bit of useful info...
Note that the persistent file name associated with the boot disk is 13 and not 0

saconfig /dev/ciss0 -N

******************** SmartArray RAID Controller /dev/ciss0 ********************

Auto-Fail Missing Disks at Boot = disabled
Cache Configuration Status = cache enabled
Cache Ratio = 25% Read / 75% Write

---------- PHYSICAL DRIVES ----------

Location Ct Enc Bay WWID Size Status

Internal 1I 1 4 0x5000c50016d18259 146.8 GB OK
Internal 1I 1 3 0x5000c50016d16f25 146.8 GB OK
Internal 2I 1 8 0x5000c50016d15509 146.8 GB OK
Internal 2I 1 7 0x5000c50016cf7bbd 146.8 GB UNASSIGNED
Internal 2I 1 6 0x5000c50016d17dd1 146.8 GB UNASSIGNED
Internal 2I 1 5 0x5000c50016d16619 146.8 GB OK

---------- LOGICAL DRIVE 0 ----------

Device File = /dev/disk/disk13
RAID Level = 1+0
Size = 139979 MB
Stripe Size = 128 KB
Status = OK

Participating Physical Drive(s):

Ct Enc Bay WWID
1I 1 4 0x5000c50016d18259
1I 1 3 0x5000c50016d16f25

Participating Spare Drive(s):

None

---------- LOGICAL DRIVE 1 ----------

Device File = /dev/disk/disk22
RAID Level = 0
Size = 139982 MB
Stripe Size = 128 KB
Status = OK

Participating Physical Drive(s):

Ct Enc Bay WWID
2I 1 5 0x5000c50016d16619

Participating Spare Drive(s):

None

---------- LOGICAL DRIVE 2 ----------

Device File = /dev/disk/disk28
RAID Level = 0
Size = 139982 MB
Stripe Size = 128 KB
Status = OK

Participating Physical Drive(s):

Ct Enc Bay WWID
2I 1 8 0x5000c50016d15509

Participating Spare Drive(s):

None

Re: drd clone failure ......

hpuxrocks — Fri, 06 May 2011 14:23:12 GMT

atedms02:/# echo boot_string/S | adb -o /stand/vmunix /dev/kmem
boot_string:
boot_string:
(;)/stand/vmunix
rex:/# lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/disk/disk13_p2 -- Boot Disk
Boot: lvol1 on: /dev/disk/disk13_p2
Root: lvol3 on: /dev/disk/disk13_p2
Swap: lvol2 on: /dev/disk/disk13_p2
Dump: lvol2 on: /dev/disk/disk13_p2, 0

rex:/# cat /stand/bootconf
l /dev/disk/disk0_p2
l /dev/disk/disk13_p2

so it looks like it booted of the 2nd dev (13).

How do I get it to boot off 1st if setboot isnt changing.

Why doesnt my other machine OR indeed this one show 2 discs with lvlnboot ? - thks

Re: drd clone failure ......

hpuxrocks — Fri, 06 May 2011 14:29:21 GMT

Update
======
atedms02:/# echo "bootdev/x"|adb -n /stand/vmunix /dev/kmem
bootdev:
0x1000009

so according to this...the boot disc in the kernel is

disk0_p2

OR

disk13_p2

since both point to 0x1000009

?

Many thks for your thoughts

Re: drd clone failure ......

hpuxrocks — Sat, 07 May 2011 03:04:07 GMT

Sorted!

The /stand/bootconf had the ref to disk0 ...removed it and all is well !

thks

Re: drd clone failure ......

hpuxrocks — Sat, 07 May 2011 03:05:39 GMT

see above