ioscan shows new disks after SAN firmware upgrade

[JCamp]

I have taken ownership of an HPUX 11.11 box. Last week the storage team upgraded the firmware on the Dell Compellent and now the HP box doesn't fully boot. This is what I've figured out so far. vg00 was actually a mixture of 2 internal disk and 2 SAN disk. The OS partially boots and I get a login prompt but I can't log in because it says it can't find path for shared library: libxti.2

If I do a vgdisplay, the disk names it shows are different then what an ioscan shows. See below

Is this fixable?

Thanks for any advice you may have!!!

BTW... I got the following info by logging into single user mode

vgdisplay output-

vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c48t1d4":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c48t1d5":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
--- Volume groups ---
VG Name                     /dev/vg00
VG Write Access             read/write
VG Status                   available
Max LV                      255
Cur LV                      8
Open LV                     8
Max PV                      16
Cur PV                      4
Act PV                      2
Max PE per PV               4350
VGDA                        4
PE Size (Mbytes)            8
Total PE                    8680
Alloc PE                    8680
Free PE                     0
Total PVG                   2
Total Spare PVs             0
Total Spare PVs in use      0

ioscan output-

disk     30  1/0/6/0/0.1.0.2.0.0.1   sdisk    CLAIMED     DEVICE       COMPELNTCompellent Vol
                            /dev/dsk/c52t0d1   /dev/rdsk/c52t0d1
disk     31  1/0/6/0/0.1.0.2.0.0.2   sdisk    CLAIMED     DEVICE       COMPELNTCompellent Vol
                            /dev/dsk/c52t0d2   /dev/rdsk/c52t0d2
disk     33  1/0/6/0/0.1.0.2.0.0.4   sdisk    CLAIMED     DEVICE       COMPELNTCompellent Vol
                            /dev/dsk/c52t0d4   /dev/rdsk/c52t0d4
disk     34  1/0/6/0/0.1.0.2.0.0.5   sdisk    CLAIMED     DEVICE       COMPELNTCompellent Vol
                            /dev/dsk/c52t0d5   /dev/rdsk/c52t0d5
disk     37  1/0/6/0/0.1.0.2.0.0.6   sdisk    CLAIMED     DEVICE       COMPELNTCompellent Vol
                            /dev/dsk/c52t0d6   /dev/rdsk/c52t0d6
disk     38  1/0/6/0/0.1.0.2.0.0.7   sdisk    CLAIMED     DEVICE       COMPELNTCompellent Vol
                            /dev/dsk/c52t0d7   /dev/rdsk/c52t0d7
disk     39  1/0/6/0/0.1.0.2.0.1.0   sdisk    CLAIMED     DEVICE       COMPELNTCompellent Vol
                            /dev/dsk/c52t1d0   /dev/rdsk/c52t1d0
disk     40  1/0/6/0/0.1.0.2.0.1.1   sdisk    CLAIMED     DEVICE       COMPELNTCompellent Vol
                            /dev/dsk/c52t1d1   /dev/rdsk/c52t1d1
disk     43  1/0/6/0/0.1.0.2.0.1.2   sdisk    CLAIMED     DEVICE       COMPELNTCompellent Vol
                            /dev/dsk/c52t1d2   /dev/rdsk/c52t1d2
disk     44  1/0/6/0/0.1.0.2.0.1.3   sdisk    CLAIMED     DEVICE       COMPELNTCompellent Vol
                            /dev/dsk/c52t1d3   /dev/rdsk/c52t1d3
disk     45  1/0/6/0/0.1.0.2.0.1.4   sdisk    CLAIMED     DEVICE       COMPELNTCompellent Vol
                            /dev/dsk/c52t1d4   /dev/rdsk/c52t1d4
disk     46  1/0/6/0/0.1.0.2.0.1.5   sdisk    CLAIMED     DEVICE       COMPELNTCompellent Vol
                            /dev/dsk/c52t1d5   /dev/rdsk/c52t1d5
disk     62  1/0/6/0/0.1.0.2.0.1.6   sdisk    CLAIMED     DEVICE       COMPELNTCompellent Vol
                            /dev/dsk/c52t1d6   /dev/rdsk/c52t1d6
disk     67  1/0/6/0/0.1.0.2.0.1.7   sdisk    CLAIMED     DEVICE       COMPELNTCompellent Vol

[likid0]

Hello,

Yes, you can fix the problem.

you should boot in mantainace mode:

boot /stan/vmux -lm

And then you need to export/import vg00.

Once you have imported vg00 with the right disks you need to fix the LABEL on the disks with lvrmboot/lvlnboot.

Then a final reboot and you are ready to go.