HPE EVA Storage

HP bl20p g3 + EVA 4400 + RHEL 4 boot problem (hangs)

 
Nuno  Gameiro
New Member

HP bl20p g3 + EVA 4400 + RHEL 4 boot problem (hangs)

Hi,
I recently upgraded from an EVA4000 to an EVA4400, the replication went well. My trouble now is that I can't boot the servers if the Fibre cables are plugged. I need to unplegged them, boot the server and the plugged them again.
This is a nightmare since the servers are an Oracle RAC.
I'm stucked in here for almost a week, but I noticed the following. Before this change my dmesg give me this:
Freeing unused kernel memory: 192k freed
SCSI subsystem initialized
QLogic Fibre Channel HBA Driver
HP CISS Driver (v 2.6.18-10)
cciss: Device 0x46 has been found at bus 2 dev 2 func 0
ACPI: PCI Interrupt 0000:02:02.0[A] -> GSI 24 (level, low) -> IRQ 58
cciss: using DAC cycles
Using cfq io scheduler
cciss/c0d0: p1 p2 p3 p4 < p5 p6 p7 p8 p9 p10 > <---- LOCAL DISKS
ACPI: PCI Interrupt 0000:04:03.0[A] -> GSI 48 (level, low) -> IRQ 201
qla2300 0000:04:03.0: Found an ISP2312, irq 201, iobase 0xf8820000 <------ FROM DOWN HERE THE STORAGE DISKS
qla2300 0000:04:03.0: Configuring PCI space...
qla2300 0000:04:03.0: Configure NVRAM parameters...
qla2300 0000:04:03.0: Verifying loaded RISC code...
qla2300 0000:04:03.0: Extended memory detected (512 KB)...
qla2300 0000:04:03.0: Resizing request queue depth (2048 -> 4096)...
qla2300 0000:04:03.0: Allocated (1308 KB) for firmware dump...
qla2300 0000:04:03.0: Waiting for LIP to complete...
qla2300 0000:04:03.0: LIP reset occured (f7f7).
qla2300 0000:04:03.0: LOOP UP detected (2 Gbps).
qla2300 0000:04:03.0: Topology - (F_Port), Host Loop address 0xffff
scsi0 : qla2xxx
qla2300 0000:04:03.0:
QLogic Fibre Channel HBA Driver: 8.01.07.25-fo
QLogic QLA2312 -
ISP2312: PCI-X (100 MHz) @ 0000:04:03.0 hdma+, host#=0, fw=3.03.19 IPX
scsi: unknown device type 12
Vendor: HP Model: HSV200 Rev: 5031
Type: RAID ANSI SCSI revision: 05
qla2300 0000:04:03.0: scsi(0:0:0:0): Enabled tagged queuing, queue depth 16.


After de change, and after appliyng the last Porliant support pack, my dmesg cames out this way:

Freeing unused kernel memory: 192k freed
SCSI subsystem initialized
QLogic Fibre Channel HBA Driver: 8.02.23-fo <---- FROM DOWN HERE IT TRIES TO SCAN THE LUNS (it can't beacuse I unplegged the cables it's the only way it boot)
ACPI: PCI Interrupt 0000:04:03.0[A] -> GSI 48 (level, low) -> IRQ 201
qla2xxx 0000:04:03.0: Found an ISP2312, irq 201, iobase 0xf881c000
qla2xxx 0000:04:03.0: Configuring PCI space...
qla2xxx 0000:04:03.0: Configure NVRAM parameters...
qla2xxx 0000:04:03.0: Verifying loaded RISC code...
qla2xxx 0000:04:03.0: Extended memory detected (512 KB)...
qla2xxx 0000:04:03.0: Resizing request queue depth (2048 -> 4096)...
qla2xxx 0000:04:03.0: Allocated (1308 KB) for firmware dump...
qla2xxx 0000:04:03.0: Waiting for LIP to complete...
qla2xxx 0000:04:03.0: Cable is unplugged...
scsi-qla0-adapter-port=50060b0000ea5092\;
scsi0 : qla2xxx
qla2xxx 0000:04:03.0:
QLogic Fibre Channel HBA Driver: 8.02.23-fo
QLogic QLA2312 -
ISP2312: PCI-X (100 MHz) @ 0000:04:03.0 hdma+, host#=0, fw=3.03.27 IPX
Using cfq io scheduler
ACPI: PCI Interrupt 0000:04:03.1[B] -> GSI 49 (level, low) -> IRQ 209
qla2xxx 0000:04:03.1: Found an ISP2312, irq 209, iobase 0xf881e000
qla2xxx 0000:04:03.1: Configuring PCI space...
qla2xxx 0000:04:03.1: Configure NVRAM parameters...
qla2xxx 0000:04:03.1: Verifying loaded RISC code...
qla2xxx 0000:04:03.1: Extended memory detected (512 KB)...
qla2xxx 0000:04:03.1: Resizing request queue depth (2048 -> 4096)...
qla2xxx 0000:04:03.1: Allocated (1308 KB) for firmware dump...
qla2xxx 0000:04:03.1: LIP reset occurred (f7f7).
qla2xxx 0000:04:03.1: Waiting for LIP to complete...
qla2xxx 0000:04:03.1: Cable is unplugged...
scsi-qla0-adapter-port=50060b0000ea5092\;
scsi-qla1-adapter-port=50060b0000ea5093\;
scsi1 : qla2xxx
qla2xxx 0000:04:03.1:
QLogic Fibre Channel HBA Driver: 8.02.23-fo
QLogic QLA2312 -
ISP2312: PCI-X (100 MHz) @ 0000:04:03.1 hdma+, host#=1, fw=3.03.27 IPX
HP CISS Driver (v 2.6.20-23)
cciss: Device 0x46 has been found at bus 2 dev 2 func 0
ACPI: PCI Interrupt 0000:02:02.0[A] -> GSI 24 (level, low) -> IRQ 58
cciss: using DAC cycles
cciss/c0d0: p1 p2 p3 p4 < p5 p6 p7 p8 p9 p10 > <-- LOCAL DISKS
libata version 2.00 loaded.

The order is changed why? I didn't setup boot from SAN.


Thanks in advance
1 REPLY 1
Nuno  Gameiro
New Member

Re: HP bl20p g3 + EVA 4400 + RHEL 4 boot problem (hangs)

Sorry folks I forgot to create de new initrd file, after changing the modprobe.conf.

Now I have another problem, the server takes 20 minutes to boot, and I'm having the following messages in the messages files:
Nov 16 16:00:55 artemis kernel: ACPI: Power Button (FF) [PWRF]
Nov 16 16:00:55 artemis kernel: EXT3 FS on cciss/c0d0p3, internal journal
Nov 16 16:00:55 artemis kernel: device-mapper: 4.5.5-ioctl (2006-12-01) initialised: dm-devel@redhat.com
Nov 16 16:00:55 artemis kernel: qla2xxx 0000:04:03.0: scsi(0:0:1:2): ABORTing cmd=c23bc800 sp=f7102600 flags=1002 state=2 ext_hist=0 jiffies = 0xfffc1c74, timeout=7, dpc_flags=0, vis_ha->dpc_flags=0 q->flag=2 ha=f7e78258 vis_ha=f7e78258 sp->ha=f7e78258
Nov 16 16:00:55 artemis kernel: qla2xxx_eh_abort(0): aborting sp f7102600 from RISC. pid=1074 sp->state=2 q->q_flag=2
Nov 16 16:00:55 artemis kernel: qla2xxx 0000:04:03.0: scsi(0:0:1:2): ABORTing cmd=c23bc800 sp=f7102600 flags=1002 state=2 ext_hist=0 jiffies = 0xfffc3bb5, timeout=7, dpc_flags=0, vis_ha->dpc_flags=0 q->flag=2 ha=f7e78258 vis_ha=f7e78258 sp->ha=f7e78258
Nov 16 16:00:55 artemis kernel: qla2xxx_eh_abort(0): aborting sp f7102600 from RISC. pid=1075 sp->state=2 q->q_flag=2
Nov 16 16:00:55 artemis kernel: qla2xxx 0000:04:03.0: scsi(0:0:1:2): ABORTing cmd=c23bc800 sp=f7102600 flags=1002 state=2 ext_hist=0 jiffies = 0xfffc5af6, timeout=7, dpc_flags=0, vis_ha->dpc_flags=0 q->flag=2 ha=f7e78258 vis_ha=f7e78258 sp->ha=f7e78258
Nov 16 16:00:55 artemis kernel: qla2xxx_eh_abort(0): aborting sp f7102600 from RISC. pid=1076 sp->state=2 q->q_flag=2
Nov 16 16:00:55 artemis kernel: qla2xxx 0000:04:03.0: scsi(0:0:1:2): ABORTing cmd=c23bc800 sp=f7102600 flags=1002 state=2 ext_hist=0 jiffies = 0xfffc7a38, timeout=7, dpc_flags=0, vis_ha->dpc_flags=0 q->flag=2 ha=f7e78258 vis_ha=f7e78258 sp->ha=f7e78258


there are hundreds of them, my new question is. Is this Storage related or Operating system related?