Re: Compaq Prolian CL380 & Array Controller CR3500 Problems: Any Suggestions Please

From: Dew Ediho (eccmqv_at_gmail.com)
Date: 07/22/04

Next message: Nikos Vassiliadis: "Re: Finding package dependancies - Where are they?"

Previous message: Ogre : "Re: Finding package dependancies - Where are they?"
Maybe in reply to: Dew Ediho: "Compaq Prolian CL380 & Array Controller CR3500 Problems: Any Suggestions Please"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Date: Thu, 22 Jul 2004 10:13:31 -0400
To: freebsd-questions@freebsd.org

I believe the problem is solved. I reloaded the firmware for the
controller following instructions available at
http://h18000.www1.hp.com/support/files/server/us/download/13739.html.

I followed the Netware version of the instruction and all. The update
time was well over an hour. HP manual suggested 15 minutes and after
50 minutes the first time out, I cancelled the operaqtion with the
belief that the process had hanged.

I later repeated the process and left it to run overnight (i had to go
home) and when I came im this morning, the update was complete (so I
can't tell you how long) and now all seem to be fine.

>
> Message: 35
> Date: Wed, 21 Jul 2004 12:10:31 -0400
> From: Dew Ediho <eccmqv@gmail.com>
> Subject: Compaq Prolian CL380 & Array Controller CR3500 Problems: Any
> Suggestions Please
> To: freebsd-questions@freebsd.org
> Message-ID: <65006f5e040721091042f549ff@mail.gmail.com>
> Content-Type: text/plain; charset=US-ASCII
>
> Dear List members,
>
> I run freebsd 4.10 on a proliant cl380 server. I split the nodes and
> do not use them as a clustered server.
>
> I created a /Data dir for the primary node using the accompnying SCSI
> array (RAID 5) with controller CR3500.
>
> I configured the controller and created the array using Compaq Array
> Utility software .
>
> The machine ran perfectly for more than 60 days until a power outage
> resulted into the box not booting up properly.
>
> I was able to get the server to boot but accessing the SCSI array is impossible.
>
> The following are logs from the system
>
> The machine runs and but I can not use the /Data directory.
>
> The screen shot of the CR3500 configuration has been convinently located at
>
> http://www.morgan.edu/newtemp/ErrorReport.pdf
>
> mailed# df
> Filesystem 1K-blocks Used Avail Capacity Mounted on
> /dev/idad0s1a 387006 35912 320134 10% /
> /dev/da0s1e 70012386 134 64411262 0% /Data
> /dev/idad0s1f 2064302 20 1899138 0% /tmp
> /dev/idad0s1g 2675182 1026494 1434674 42% /usr
> /dev/idad0s1e 2064302 23986 1875172 1% /var
> procfs 4 4 0 100% /proc
>
> /Data directory is on the SCSI array. Others are on the node hard drive.
>
> mailed# dmesg
> Copyright (c) 1992-2004 The FreeBSD Project.
> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
> The Regents of the University of California. All rights reserved.
> FreeBSD 4.10-RELEASE #0: Tue May 25 22:47:12 GMT 2004
> root@perseus.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC
> Timecounter "i8254" frequency 1193182 Hz
> CPU: Intel Pentium III (797.48-MHz 686-class CPU)
> Origin = "GenuineIntel" Id = 0x683 Stepping = 3
> Features=0x383fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE>
> real memory = 671072256 (655344K bytes)
> avail memory = 646737920 (631580K bytes)
> Preloaded elf kernel "kernel" at 0xc0551000.
> Pentium Pro MTRR support enabled
> md0: Malloc disk
> npx0: <math processor> on motherboard
> npx0: INT 16 interface
> pcib0: <ServerWorks NB6635 3.0LE host to PCI bridge> on motherboard
> pci0: <PCI bus> on pcib0
> ida0: <Compaq Integrated Array controller> port 0x2000-0x20ff mem
> 0xc4000000-0xc4ffffff,0xc5000000-0xc5ffffff irq 15 at device 1.0 on
> pci0
> ida0: drives=1 firm_rev=1.42
> idad0: <Compaq Logical Drive> on ida0
> idad0: 8670MB (17756160 sectors), blocksize=512
> fxp0: <Intel 82559 Pro/100 Ethernet> port 0x2400-0x243f mem
> 0xc3e00000-0xc3efffff,0xc3fff000-0xc3ffffff irq 5 at device 2.0 on
> pci0
> fxp0: Disabling dynamic standby mode in EEPROM
> fxp0: New EEPROM ID: 0x40a0
> fxp0: EEPROM checksum @ 0xff: 0x6bc5 -> 0x6bc5
> fxp0: Ethernet address 00:02:a5:09:31:ed
> inphy0: <i82555 10/100 media interface> on miibus0
> inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> pci0: <ATI Mach64-GV graphics accelerator> at 3.0
> pci0: <unknown card> (vendor=0x0e11, dev=0xa0f0) at 4.0
> fxp1: <Intel 82559 Pro/100 Ethernet> port 0x2c00-0x2c3f mem
> 0xc3c00000-0xc3cfffff,0xc3dfd000-0xc3dfdfff irq 5 at device 5.0 on
> pci0
> fxp1: Ethernet address 00:50:8b:b8:2f:33
> inphy1: <i82555 10/100 media interface> on miibus1
> inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> isab0: <ServerWorks IB6566 PCI to ISA bridge> at device 15.0 on pci0
> isa0: <ISA bus> on isab0
> atapci0: <ServerWorks ROSB4 ATA33 controller> port 0x2c40-0x2c4f at
> device 15.1 on pci0
> ata0: at 0x1f0 irq 14 on atapci0
> ata1: at 0x170 irq 15 on atapci0
> pcib3: <ServerWorks NB6635 3.0LE host to PCI bridge> on motherboard
> pci3: <PCI bus> on pcib3
> sym0: <896> port 0x3000-0x30ff mem
> 0xc6ffc000-0xc6ffdfff,0xc6fffc00-0xc6ffffff irq 10 at device 4.0 on
> pci3
> sym0: No NVRAM, ID 7, Fast-40, LVD, parity checking
> sym1: <896> port 0x3400-0x34ff mem
> 0xc6ff8000-0xc6ff9fff,0xc6ffbc00-0xc6ffbfff irq 11 at device 4.1 on
> pci3
> sym1: No NVRAM, ID 7, Fast-40, LVD, parity checking
> eisa0: <EISA bus> on motherboard
> mainboard0: <CPQ0681 (System Board)> on eisa0 slot 0
> orm0: <Option ROMs> at iomem
> 0xc0000-0xc7fff,0xc8000-0xcbfff,0xcc000-0xcd7ff,0xe8000-0xedfff,0xee000-0xeffff
> on isa0
> pmtimer0 on isa0
> fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
> fdc0: FIFO enabled, 8 bytes threshold
> fd0: <1440-KB 3.5" drive> on fdc0 drive 0
> atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
> atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0
> kbd0 at atkbd0
> psm0: <PS/2 Mouse> irq 12 on atkbdc0
> psm0: model IntelliMouse, device ID 3
> vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
> sc0: <System console> at flags 0x100 on isa0
> sc0: VGA <16 virtual consoles, flags=0x300>
> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
> sio0: type 16550A
> sio1 at port 0x2f8-0x2ff irq 3 on isa0
> sio1: type 16550A
> ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0
> ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
> plip0: <PLIP network interface> on ppbus0
> lpt0: <Printer> on ppbus0
> lpt0: Interrupt-driven port
> ppi0: <Parallel I/O> on ppbus0
> ata0-slave: ATAPI identify retries exceeded
> acd0: CDROM <CD-224E> at ata0-master PIO4
> Waiting 15 seconds for SCSI devices to settle
> pass0 at sym0 bus 0 target 9 lun 0
> pass0: <Compaq CR3500 x2q> Fixed Storage Array SCSI-2 device
> pass0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged
> Queueing Enabled
> pass2 at sym0 bus 0 target 10 lun 0
> pass2: <Compaq CR3500 x2q> Fixed Storage Array SCSI-2 device
> pass2: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged
> Queueing Enabled
> da0 at sym0 bus 0 target 9 lun 1
> da0: <Compaq CR3500 x2q> Fixed Direct Access SCSI-2 device
> da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled
> da0: 69454MB (142241792 512 byte sectors: 255H 63S/T 8854C)
> Mounting root from ufs:/dev/idad0s1a
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> sym0: SCSI phase error fixup: CCB already dequeued.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> sym0: SCSI phase error fixup: CCB already dequeued.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> sym0: SCSI phase error fixup: CCB already dequeued.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> sym0: SCSI phase error fixup: CCB already dequeued.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> sym0: SCSI phase error fixup: CCB already dequeued.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> sym0: unexpected disconnect
> sym0:9:control msgout: 81 22 47 d.
> sym0: SCSI phase error fixup: CCB already dequeued.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> sym0: SCSI phase error fixup: CCB already dequeued.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> sym0: SCSI phase error fixup: CCB already dequeued.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> sym0: SCSI phase error fixup: CCB already dequeued.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> sym0: SCSI phase error fixup: CCB already dequeued.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> sym0: SCSI phase error fixup: CCB already dequeued.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> sym0: SCSI phase error fixup: CCB already dequeued.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> sym0: SCSI phase error fixup: CCB already dequeued.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> sym0: SCSI phase error fixup: CCB already dequeued.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> sym0: SCSI phase error fixup: CCB already dequeued.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> sym0: SCSI phase error fixup: CCB already dequeued.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> sym0: SCSI phase error fixup: CCB already dequeued.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> sym0: SCSI phase error fixup: CCB already dequeued.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> sym0: SCSI phase error fixup: CCB already dequeued.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> sym0: SCSI phase error fixup: CCB already dequeued.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> sym0: unexpected disconnect
> sym0:9:control msgout: 81 22 61 d.
> sym0: SCSI phase error fixup: CCB already dequeued.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> sym0: SCSI phase error fixup: CCB already dequeued.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> sym0: SCSI phase error fixup: CCB already dequeued.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> sym0: SCSI phase error fixup: CCB already dequeued.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> sym0: SCSI phase error fixup: CCB already dequeued.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> sym0: SCSI phase error fixup: CCB already dequeued.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> sym0: SCSI phase error fixup: CCB already dequeued.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> sym0: SCSI phase error fixup: CCB already dequeued.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> sym0: SCSI phase error fixup: CCB already dequeued.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> sym0: SCSI phase error fixup: CCB already dequeued.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> sym0: SCSI phase error fixup: CCB already dequeued.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> sym0: SCSI phase error fixup: CCB already dequeued.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> sym0: SCSI phase error fixup: CCB already dequeued.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
> (noperiph:sym0:0:-1:-1): SCSI BUS reset detected.
>
> ------------------------------
>
> _______________________________________________
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
>
> End of freebsd-questions Digest, Vol 69, Issue 10
> *************************************************
>
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"

Next message: Nikos Vassiliadis: "Re: Finding package dependancies - Where are they?"

Previous message: Ogre : "Re: Finding package dependancies - Where are they?"
Maybe in reply to: Dew Ediho: "Compaq Prolian CL380 & Array Controller CR3500 Problems: Any Suggestions Please"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Relevant Pages

Re: Graphic options for DS10L
... I take it the BIOS is made up of binary 8086 architecture code? ... That could be IA-32e instructions, or it could be the decades-old 8086 instructions. ... As Fred indicates in the following, the controller itself will very likely have the minimal instruction set in the firmware, and just needed to get the controller active in VGA mode. ... The EFI byte code and the byte code engine is intended to avoid having x86 instructions in the card, to allow the firmware to be more portable across platforms -- space in the controller firmware storage area is obviously limited, which is why systems not based on x86 presently have a way to process the x86 instructions out on the controller storage. ...
(comp.os.vms)
Re: How not to play nice with a GPS
... > and turned to a 060 heading. ... > controller committed an error. ... > but then gave me instructions contrary to the procedure. ... I had a final checkout with the chief ...
(rec.aviation.ifr)
Re: gvp_impact_a500
... I bought one off of ebay, and didn't get any instructions. ...
(comp.sys.cbm)
Re: Brake magnets have thermal protection?
... I will now re-adjust my controller to use a bit less voltage so the wheels will not lock-up. ... Also I'll say that I am one of few people who read installation instructions cover to cover. ...
(rec.outdoors.rv-travel)
Re: ILS critical area when the tower is closed?
... doesn't have to depend on a controller for instructions. ... >> I don't see what the tower being open or closed has to do with it. ... >>> the ILS critical area even when the tower was closed. ...
(rec.aviation.ifr)