Hardware Patch change on Boot from SAN

[Mynor Aguilar]

Hello All,

a customer decided to replace the existing switches from old Brocades to newer MDS switches.   unfortunately, no precautionary measures were taken and all the SAN boot / filesystem volumes are unmountable due to the difference on the hardware path.   the LUNS are visible from EFI but I was wondering if there's something that be done in order to regain connectivity without unplugging the SAN and Server to the old switches (they are on a different datacenter now).   

fso: and fs1: directories are visible.   However, the system crashes at boot due to the lack of swap space (as all the LUNS were presented/mapped from the SAN).

regards,

Mynor

[Torsten.]

I assume the OS is below 11.31 - because of the new switches you have different h/w paths, hence new device files.You

 need to

 vgexport/vgimport the VGs to make them working again. For vg00 boot into LVM maintenance mode.

[Mynor Aguilar]

Hello Torsten,

you're correct.   it is HP-UX 11.23

Try to log in into maintenance mode but the server crashed, I guess it is related to the same issue.   so far I cannot even boot the server going into LVM maintenance mode.   Maybe there's something obvious that I'm not doing.

I have attached the output in case somebody can take a quick look.

Loading.: EFI Shell [Built-in]
EFI Shell version 1.10 [14.62]
Device mapping table
  fs0   : Acpi(HWP0002,PNP0A03,700)/Pci(1|0)/Fibre(WWN5000D3100012FA18,Lun4000000000000000)/HD(Part1,Sig0E06CD8A-D7F2-11E0-8002-D6217B60E588)
  fs1   : Acpi(HWP0002,PNP0A03,700)/Pci(1|0)/Fibre(WWN5000D3100012FA18,Lun4000000000000000)/HD(Part3,Sig0E06CDBC-D7F2-11E0-8004-D6217B60E588)
  blk0  : Acpi(HWP0002,PNP0A03,0)/Pci(2|1)/Usb(0, 0)
  blk1  : Acpi(HWP0002,PNP0A03,200)/Pci(1|0)/Sas(Addr5000C50005483BE1,Lun0)
  blk2  : Acpi(HWP0002,PNP0A03,200)/Pci(1|0)/Sas(Addr5000C5000543BBCD,Lun0)
  blk3  : Acpi(HWP0002,PNP0A03,700)/Pci(1|0)/Fibre(WWN5000D3100012FA18,Lun4002000000000000)
  blk4  : Acpi(HWP0002,PNP0A03,700)/Pci(1|0)/Fibre(WWN5000D3100012FA18,Lun4017000000000000)
  blk5  : Acpi(HWP0002,PNP0A03,700)/Pci(1|0)/Fibre(WWN5000D3100012FA18,Lun4003000000000000)
  blk6  : Acpi(HWP0002,PNP0A03,700)/Pci(1|0)/Fibre(WWN5000D3100012FA18,Lun4016000000000000)
  blk7  : Acpi(HWP0002,PNP0A03,700)/Pci(1|0)/Fibre(WWN5000D3100012FA18,Lun4004000000000000)
  blk8  : Acpi(HWP0002,PNP0A03,700)/Pci(1|0)/Fibre(WWN5000D3100012FA18,Lun4012000000000000)
  blk9  : Acpi(HWP0002,PNP0A03,700)/Pci(1|0)/Fibre(WWN5000D3100012FA18,Lun401C000000000000)
  blkA  : Acpi(HWP0002,PNP0A03,700)/Pci(1|0)/Fibre(WWN5000D3100012FA18,Lun4005000000000000)
  blkB  : Acpi(HWP0002,PNP0A03,700)/Pci(1|0)/Fibre(WWN5000D3100012FA18,Lun4015000000000000)
  blkC  : Acpi(HWP0002,PNP0A03,700)/Pci(1|0)/Fibre(WWN5000D3100012FA18,Lun4006000000000000)
  blkD  : Acpi(HWP0002,PNP0A03,700)/Pci(1|0)/Fibre(WWN5000D3100012FA18,Lun4011000000000000)
  blkE  : Acpi(HWP0002,PNP0A03,700)/Pci(1|0)/Fibre(WWN5000D3100012FA18,Lun4007000000000000)
  blkF  : Acpi(HWP0002,PNP0A03,700)/Pci(1|0)/Fibre(WWN5000D3100012FA18,Lun4014000000000000)
  blk10 : Acpi(HWP0002,PNP0A03,700)/Pci(1|0)/Fibre(WWN5000D3100012FA18,Lun4018000000000000)
  blk11 : Acpi(HWP0002,PNP0A03,700)/Pci(1|0)/Fibre(WWN5000D3100012FA18,Lun4008000000000000)
  blk12 : Acpi(HWP0002,PNP0A03,700)/Pci(1|0)/Fibre(WWN5000D3100012FA18,Lun4000000000000000)
  blk13 : Acpi(HWP0002,PNP0A03,700)/Pci(1|0)/Fibre(WWN5000D3100012FA18,Lun4000000000000000)/HD(Part1,Sig0E06CD8A-D7F2-11E0-8002-D6217B60E588)
  blk14 : Acpi(HWP0002,PNP0A03,700)/Pci(1|0)/Fibre(WWN5000D3100012FA18,Lun4000000000000000)/HD(Part2,Sig0E06CD9E-D7F2-11E0-8003-D6217B60E588)
  blk15 : Acpi(HWP0002,PNP0A03,700)/Pci(1|0)/Fibre(WWN5000D3100012FA18,Lun4000000000000000)/HD(Part3,Sig0E06CDBC-D7F2-11E0-8004-D6217B60E588)
startup.nsh> echo -off

  setting hpux path(\EFI\HPUX)...
  type 'fs[x]:' where x is your bootdisk (0, 1, 2...)
  type 'hpux' to start hpux bootloader
Shell> fs0:

fs0:\> cd efi

fs0:\EFI> hpux

(C) Copyright 1999-2006 Hewlett-Packard Development Company, L.P.
All rights reserved

HP-UX Boot Loader for IPF  --  Revision 2.029

Press Any Key to interrupt Autoboot
\efi\hpux\AUTO ==> boot vmunix
Seconds left till autoboot -   9
   Type 'help' for help

HPUX>


HPUX> boot -lm vmunix
> System Memory = 32747 MB
loading section 0
............................................................ (complete)
loading section 1
............... (complete)
loading symbol table
loading System Directory (boot.sys) to MFS
....
loading MFSFILES directory (bootfs) to MFS
......................
Launching /stand/vmunix
SIZE: Text:30507K + Data:7295K + BSS:5362K = Total:43165K

Console is on a Serial Device
Booting kernel...


Memory Class Setup
-------------------------------------------------------------------------
Class     Physmem              Lockmem              Swapmem
-------------------------------------------------------------------------
System :  32747 MB             32747 MB             32747 MB
Kernel :  32747 MB             32747 MB             32747 MB
User   :  30994 MB             27011 MB             27117 MB
-------------------------------------------------------------------------
Loaded ACPI revision 2.0 tables.
NOTICE: cachefs_link(): File system was registered at index 5.
NOTICE: nfs3_link(): File system was registered at index 8.
NOTICE: mod_fs_reg: Cannot retrieve configured loading phase from KRS for module: cifs. Setting to load at INIT

NOTICE: USB device attached.  Identification String:
Devices/Device/USB/Standard/hp/Unknown/0_1
 <2.1.3.10.1008.4390.1>
NOTICE: USB device attached.  Identification String:
Devices/Keyboard/USB/Boot/hp/Unknown/0_1
 <2.305.3.100.1008.4390.1>
NOTICE: USB device attached.  Identification String:
Devices/Mouse/USB/Boot/hp/Unknown/0_1
 <2.307.3.100.1008.4390.1>
NOTICE: USB device attached.  Identification String:
Devices/Device/USB/Standard/hp/Multibay/0_a1
 <2.1.3.10.1008.294.161>
NOTICE: USB device attached.  Identification String:
Devices/MassStorage-SCSI/USB/BulkOnly/hp/Multibay/0_a1
 <2.310.3.150.1008.294.161>
NOTICE: USB device attached.  Identification String:
Devices/ScsiControllerAdaptor/USB/BulkOnly/hp/Multibay
 <2.1000.3.150.1008.294>
sasd: [ALERT] Driver detected a software downgrade.
sasd: The current driver version is unsupported
sasd: for the Serial SCSI HBA at hw path 0/1/1/0.
sasd: Please install the latest SerialSCSI-00 depot ASAP.
Boot device's HP-UX HW path is: 0/4/1/0.3.9

    System Console is on the Built-In Serial Interface
igelan0: INITIALIZING HP PCI-X 1000Base-T Dual-port Built-in at hardware path 0/1/2/0
igelan1: INITIALIZING HP PCI-X 1000Base-T Dual-port Built-in at hardware path 0/1/2/1
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
    Swap device table:  (start & size given in 512-byte blocks)

Calling function e000000001086f20 for Shutdown State 8 type 0x2

Stored message buffer up to panic:
/0.3.15.255.0.0 tgt
0/4/1/0.3.15.0.0.0.0 sctl
0/4/1/0.3.15.255.0.0.0 sctl
0/2/1/0.4.0.0.0.0 tgt
0/2/1/0.4.0.255.0.0 tgt
0/2/1/0.4.0.0.0.0.0 sctl
0/2/1/0.4.0.255.0.0.0 sctl
0/4/1/0.3.31.0.0.0 tgt
0/4/1/0.3.31.255.0.0 tgt
0/2/1/0.2.15.255.14.4 tgt
0/4/1/0.3.31.0.0.0.0 sctl
0/4/1/0.3.31.255.0.0.0 sctl
0/4/1/0.3.27.0.0.0 tgt
0/4/1/0.3.27.255.0.0 tgt
0/4/1/0.3.27.0.0.0.0 sctl
0/4/1/0.3.27.255.0.0.0 sctl
0/4/1/0.3.0.0.0.0 tgt
0/4/1/0.3.0.255.0.0 tgt
0/4/1/0.3.0.0.0.0.0 sctl
0/4/1/0.3.0.255.0.0.0 sctl
0/2/1/0.2.15.255.14.4.0 schgr
0/2/1/0.2.15.255.14.4.1 stape
0/2/1/0.2.15.255.14.4.2 stape
0/2/1/0.2.15.255.14.4.3 sctl
sasd: [ALERT] Driver detected a software downgrade.
sasd: The current driver version is unsupported
sasd: for the Serial SCSI HBA at hw path 0/1/1/0.
sasd: Please install the latest SerialSCSI-00 depot ASAP.
0/1/1/0.0.0 sasd_vbus
0/1/1/0.0.0.2 tgt
0/1/1/0.0.0.2.0 sdisk
0/1/1/0.0.0.3 tgt
0/1/1/0.0.0.3.0 sdisk
0/4/1/0.49.5.0.0.0 tgt
0/4/1/0.49.5.255.0.0 tgt
0/4/1/0.49.5.0.0.0.0 sctl
0/4/1/0.49.5.255.0.0.0 sctl
0/4/1/0.49.4.0.0.0 tgt
0/4/1/0.49.4.255.0.0 tgt
0/4/1/0.49.4.0.0.0.0 sctl
0/4/1/0.49.4.255.0.0.0 sctl
0/2/1/0.143.5.0.0.0 tgt
0/2/1/0.143.5.255.0.0 tgt
0/4/1/0.49.7.0.0.0 tgt
0/4/1/0.49.7.255.0.0 tgt
0/2/1/0.143.5.0.0.0.0 sctl
0/2/1/0.143.5.255.0.0.0 sctl
0/4/1/0.49.7.0.0.0.0 sdisk
0/4/1/0.49.7.255.0.0.0 sctl
0/2/1/0.143.0.0.0.0 tgt
0/2/1/0.143.0.255.0.0 tgt
0/4/1/0.49.6.0.0.0 tgt
0/4/1/0.49.6.255.0.0 tgt
0/4/1/0.49.7.0.0.0.2 sdisk
0/2/1/0.143.0.0.0.0.0 sctl
0/2/1/0.143.0.255.0.0.0 sctl
0/4/1/0.49.6.0.0.0.0 sctl
0/4/1/0.49.6.255.0.0.0 sctl
0/4/1/0.49.7.0.0.0.3 sdisk
0/4/1/0.49.7.0.0.0.4 sdisk
0/4/1/0.49.7.0.0.0.5 sdisk
0/4/1/0.49.7.0.0.0.6 sdisk
0/4/1/0.49.7.0.0.0.7 sdisk
0/4/1/0.49.7.0.0.1 tgt
0/4/1/0.49.7.0.0.1.0 sdisk
0/2/1/0.143.6.0.0.0 tgt
0/2/1/0.143.6.255.0.0 tgt
0/2/1/0.143.6.0.0.0.0 sdisk
0/2/1/0.143.6.255.0.0.0 sctl
0/2/1/0.143.7.0.0.0 tgt
0/2/1/0.143.7.255.0.0 tgt
0/2/1/0.143.6.0.0.0.2 sdisk
0/2/1/0.143.7.0.0.0.0 sctl
0/2/1/0.143.7.255.0.0.0 sctl
0/2/1/0.143.6.0.0.0.3 sdisk
0/4/1/0.49.7.0.0.2 tgt
0/2/1/0.143.6.0.0.0.4 sdisk
0/2/1/0.143.6.0.0.0.5 sdisk
0/2/1/0.143.6.0.0.0.6 sdisk
0/4/1/0.49.7.0.0.2.1 sdisk
0/2/1/0.143.6.0.0.0.7 sdisk
0/4/1/0.49.7.0.0.2.2 sdisk
0/2/1/0.143.6.0.0.1 tgt
0/4/1/0.49.7.0.0.2.4 sdisk
0/2/1/0.143.6.0.0.1.0 sdisk
0/4/1/0.49.7.0.0.2.5 sdisk
0/4/1/0.49.7.0.0.2.6 sdisk
0/4/1/0.49.7.0.0.2.7 sdisk
0/4/1/0.49.7.0.0.3 tgt
0/4/1/0.49.7.0.0.3.0 sdisk
0/4/1/0.49.7.0.0.3.4 sdisk
0/2/1/0.143.6.0.0.2 tgt
0/2/1/0.143.6.0.0.2.1 sdisk
0/2/1/0.143.6.0.0.2.2 sdisk
0/2/1/0.143.6.0.0.2.4 sdisk
0/2/1/0.143.6.0.0.2.5 sdisk
0/2/1/0.143.6.0.0.2.6 sdisk
0/2/1/0.143.6.0.0.2.7 sdisk
0/2/1/0.143.6.0.0.3 tgt
0/2/1/0.143.6.0.0.3.0 sdisk
0/2/1/0.143.6.0.0.3.4 sdisk
Boot device's HP-UX HW path is: 0/4/1/0.3.9

    System Console is on the Built-In Serial Interface
igelan0: INITIALIZING HP PCI-X 1000Base-T Dual-port Built-in at hardware path 0/1/2/0
igelan1: INITIALIZING HP PCI-X 1000Base-T Dual-port Built-in at hardware path 0/1/2/1
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
    Swap device table:  (start & size given in 512-byte blocks)
        entry 0 - auto-configured on root device; ignored - can't open device
WARNING: no swap device configured, so dump cannot be defaulted to primary swap.
WARNING: No dump devices are configured.  Dump is disabled.
mountfs:opend

System Panic:

panic: all VFS_MOUNTROOTs failed: NEED DRIVERS ?????
Stack Trace:
  IP                  Function Name
  0xe000000000ec96c0  vfs_mountroot+0x1d0
  0xe0000000011e0720  im_mountroot+0x60
  0xe000000001636d10  DoCalllist+0x3a0
End of Stack Trace

linkstamp:          Sun Aug 28 23:48:22 ADT 2011
_release_version:   @(#) $Revision: vmunix:    B11.23_LR FLAVOR=perf Fri Aug 29 22:35:38 PDT 2003 $

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:  No dump space is configured.  Physical memory will not be dumped.
ERROR:  Configured dump space is insufficient to hold dump metadata.
        Physical memory will not be dumped.

cheers,

Mynor

[Torsten.]

try "boot vmunix -lm"

[Mynor Aguilar]

thanks for your prompt reply, I tried boot vmunix -lm and got the same results.
any other ideas? I'm sort of desperate cause it is not possible to move the server/san back to their former fabric switches.

regards,
Mynor

[donna hofmeister]

it can't hurt to try to boot into single-user mode (-is).

is it possible to boot from an ignite image?

[Mynor Aguilar]

Thanks for you reply, basically booting up on single user mode of maintenance mode gave us the same results.   I'm wondering if there's something that we can do on the switches to fool the server into believing it is the same hardware path.   the domain ID of the switches is the same, maybe using the same ports we were using on the old Brocade switches can do the trick.     unfortunately, there is not a recent ignite copy of the server, there's a mirror copy of the server that was taken a while back on a old EVA storage array, worst case scenario we can revert to that old copy (and move the server back to the rack) but that would be last case scenario.

[Mynor Aguilar]

Well, escalated the issue to HP and they couldn't solve the problem.   the change of the hardware path on HP-UX 11.23 when you're booting from SAN seems to be a bit a on issue.   Anyway, lesson learned, make an ignite before doing these kind of changes, it would have been much faster to recover the base OS from the Ignite and then vgimport the other LUNS.    we were able to restore the boot LUNS from a SAN snapshot of the VG00 drives.   once the OS was able to boot it was easy to boot in single user mode and vgimport the foreign disks from the other SAN without any issues.

thanks for all your help.

regards,

Mynor Aguilar