Root Volume Extents Stale after Disk Change

[Chad Brindley]

We had a disk die on us this morning so the HP engineer came out today, replaced the hardware restored the config, set the lvlnboot params and did a vgsync. We then amended the alternate bootpath in the EFI shell to point to the replaced disk.

After booting the system off the replaced disk it booted up fine but all lvols 1 - 9 were showing as stale.

Sync them manually after boot and they are synchronised and stay synchronised until next re-boot.

This is on an Itanium RX4640 also happened on another RX4640 of ours. Coincidentally both times it has happened after the root volume disks have been changed with the engineers not knowing how to resolve the issue onsite it was deemed a software issue and because our systems patch level is low.

So both systems are at the same level patch wise so this is a possibility but just wondered before we entertain patching the systems (they will be replaced in the near future) which isnt really worth the trouble in our current status is there anything you can see config wise.

We have a 3 2600's without this problem which I would hope run the same patch level as our other HP-UX boxes all on 11.23.

I have put the config of our disk info below from system with the disk replaced today. The disk showing as stale was c2t0d0, the disk replaced was c2t0d0

# diskinfo /dev/rdsk/c2t0d0
SCSI describe of /dev/rdsk/c2t0d0:
vendor: HP 73.4G
product id: ST373454LC
type: direct access
size: 71687369 Kbytes
bytes per sector: 512

# diskinfo /dev/rdsk/c2t1d0
SCSI describe of /dev/rdsk/c2t1d0:
vendor: HP 73.4G
product id: ST373453LC
type: direct access
size: 71687369 Kbytes
bytes per sector: 512

The only difference being the product id showing a slightly different disk (same size though), on the other system with the same problem they are both product id ST373453LC.

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

# setboot

Primary bootpath : 0/1/1/0.1.0
HA Alternate bootpath : 0/1/1/0.0.0
Alternate bootpath : 0/0/3/0.0.0.0

Please note the HA Alternate boot path is the disk replaced.

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

#lvlnboot -v

Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:

/dev/dsk/c2t1d0s2 (0/1/1/0.1.0) -- Boot Disk
/dev/dsk/c2t0d0s2 (0/1/1/0.0.0) -- Boot Disk

Boot: lvol1 on: /dev/dsk/c2t1d0s2
/dev/dsk/c2t0d0s2

Root: lvol3 on: /dev/dsk/c2t1d0s2
/dev/dsk/c2t0d0s2

Swap: lvol2 on: /dev/dsk/c2t1d0s2
/dev/dsk/c2t0d0s2

Dump: lvol2 on: /dev/dsk/c2t1d0s2, 0

Can anyone see anything strange with the above?

I need to test booting off the other disk to see if that has the same problem and also changing the setboot primary to be the other disk.

Regards,

Chad

[Steven E. Protter]

Shalom Chad,

You need to split all your mirrors, pvcreate the disk and completely re-mirror your boot disk.


pvcreate -B /dev/rdsk/c1t0d0 #use real disk

mkboot -l /dev/rdsk/c1t0d0
mkboot -a "hpux -lq (;0)/stand/vmunix" /dev/rdsk/c1t0d0 # use real disk


# mkboot -b /usr/sbin/diag/lif/updatediaglif -p ISL -p AUTO -p HPUX -p PAD -p LABEL /dev/rdsk/c?t?d?

If you are running 64-bit OS:

# mkboot -b /usr/sbin/diag/lif/updatediaglif2 -p ISL -p AUTO -p HPUX -p PAD -p LABEL /dev/rdsk/c?t?d?


vgextend /dev/vg00 /dev/dsk/c1t0d0 # same thing
lvextend -m 1 /dev/vg00/lvol1 /dev/dsk/c1t0d0

# real disk. repeat for other lvols

lvlnboot -r /dev/vg00/lvol3 # root fs /
lvlnboot -s /dev/vg00/lvol2 #swap
lvlnboot -d /dev/vg00/lvol2 #swap/dump
lvlnboot -b /dev/vg00/lvol1
lvlnboot -R
lvlnboot -v
setboot
setboot -a 52.1.0 # second disk

Thanks to all that made this doc right.

SEP

[Chad Brindley]

Hi,

Thanks for the note,

The engineer used the instructions from the Itanium cook book so is it likely that something has been missed from their procedure!

They went through most of the bits you suggested I am sure.

I will try and find out what they have and havent done.

Chad