Adaptec 5805

Adaptec 5805.
Raid 5ee - 6disks.
Read & Write cache off (or on).
Operation system freebsd 7.1 x86
Drivers: aac or aacu (get from adaptec).
At the big loadings can`t "sync" disks, after 5-10 minutes system freeze. In system logs - no records.

ansver for me

tunefs softupdate set off

not found

System freeze now every 60-90 minutes...
In console see error from adaptec controller.

Hi, Dmitry.

Please, specifies a problem.

Interested in:
- version number of build conroller firmware
- what are the operations loaded logical volume

link to my problem
http://lists.freebsd.org/pipermail/freebsd-hackers/2009-March/028037.html
http://lists.freebsd.org/pipermail/freebsd-scsi/2009-March/003874.html

BIOS
Adaptec RAID 5805 Firmware Build 16501

DRIVERS
From FreeBSD distributive or
AACRAID 32- and 64-bit Driver Build 16343 for FreeBSD

SCHED_4BSD or SCHED_ULE - i try - and see error
aacd0: COMMAND 0xffffffff808599e0 TIMEOUT AFTER XXXX SECONDS or
aacdu0: COMMAND 0xffffffff808599e0 TIMEOUT AFTER XXXX SECONDS
or system freeze.

Operations:
1. NONE ~24h uptime max and freeze
2. blogbench ~10min uptime - freeze or error message


I have only one work configuration now and wait change controllers.

arcconf GETCONFIG 1
Controllers found: 1
----------------------------------------------------------------------
Controller information
----------------------------------------------------------------------
Controller Status : Optimal
Channel description : SAS/SATA
Controller Model : Adaptec 5805
Controller Serial Number : 8C4310BCEE5
Physical Slot : 4
Temperature : 46 C/ 114 F (Normal)
Installed memory : 512 MB
Copyback : Disabled
Background consistency check : Disabled
Automatic Failover : Enabled
Global task priority : High
Performance Mode : Default/Dynamic
Defunct disk drive count : 0
Logical devices/Failed/Degraded : 1/0/0
--------------------------------------------------------
Controller Version Information
--------------------------------------------------------
BIOS : 5.2-0 (16501)
Firmware : 5.2-0 (16501)
Driver : 2.2-4 (16343)
Boot Flash : 5.2-0 (16501)
--------------------------------------------------------
Controller Battery Information
--------------------------------------------------------
Status : Optimal
Over temperature : No
Capacity remaining : 99 percent
Time remaining (at current draw) : 1 days, 19 hours, 55 minutes

----------------------------------------------------------------------
Logical device information
----------------------------------------------------------------------
Logical device number 0
Logical device name : XeXeXeXeXe
RAID level : 5EE
Status of logical device : Optimal
Status of RAID 5EE : Expanded
Size : 1904640 MB
Stripe-unit size : 64 KB
Read-cache mode : Enabled
Write-cache mode : Enabled (write-back)
Write-cache setting : Enabled (write-back) when protected by battery
Partitioned : Yes
Protected by Hot-Spare : No
Bootable : Yes
Failed stripes : No
--------------------------------------------------------
Logical device segment information
--------------------------------------------------------
--------------------------------------------------------
Logical device segment information
--------------------------------------------------------
Segment 0 : Present (0,0)
Segment 1 : Present (0,1)
Segment 2 : Present (0,2)
Segment 3 : Present (0,4)
Segment 4 : Present (0,5)
Segment 5 : Present (0,6)


----------------------------------------------------------------------
Physical Device information
----------------------------------------------------------------------
Device #0
Device is a Hard drive
State : Online
Supported : Yes
Transfer Speed : SATA 3.0 Gb/s
Reported Channel,Device : 0,0
Reported Location : Connector 0, Device 0
Vendor : WDC
Model : WD5002ABYS-0
Firmware : 02.03B02
Size : 476940 MB
Write Cache : Disabled (write-through)
FRU : None
S.M.A.R.T. : No
.....

Hi, I had the same problem with an Adaptec 5805. It seems that it's fixed with revision 188896 which has made it in to FreeBSD 7.2
The commit message doesn't even mention anything that could be related to what I know about the crashes, but the server has been running happily for several days now without a single crash.

Rada, please try to stress test (long & high-load) on `bogbench` tool

* `blogbench`

I'll have the opportunity to do so next month when we get a replacement server for the one currently running with the adaptec card.

Right now the server processes about 1TB of data (from a 6x1TB RAID5 array) using find and egrep through perl, so I don't want to interrupt it.
Running fine since 5th may on GENERIC kernel.

FreeBSD xx.xx.xx 7.2-RELEASE FreeBSD 7.2-RELEASE #0: Tue May 5 19:23:21 UTC 2009 xx@xx.xx.xx:/usr/obj/usr/src/sys/GENERIC amd64

Click to expand...

need high & long load (~100% in gstat)

Problem resolved for me - change controllers to new 5805

OS: FreeBSD amd 7.1 and amd 7.2
FirmWare: Adaptec RAID 5805 Firmware Build 16501
Driver version: AACRAID 32- and 64-bit Driver Build 16343 for FreeBSD (compile for os as module and in kernel)
Raid level: 5ee (6x500gb or 6x750gb)
Uptime: 3-5 weeks - all work.

urpyLLIKa, your problem was in hardware ?

Yes.
I`m tested M$ Window$ and Linux (CentOS) on old hardware - trouble 1:1 - work same time and freeze. After change to new hardware - problem resolved.

The server crashed, problem isn't fixed in 7.2...

urpyLLIKa, how do you explain that we both had exactly identically defect cards?

Rada, please give verbose description (with logs) of your`s server(controller crash) situation.

for identification defect cards need high&long load

I've analog situation with my Adaptec 51245 controller with accd and accu drivers.

aac:
aacu:
and at some time:
my dmesg:
Last Motherboard and Adapatec controller BIOS and last FreeBSD accu driver.

Please use code tags when posting system messages.
http://forums.freebsd.org/misc.php?do=bbcode#code

1. check backplane connected (if need change to direct connect) and test - example for supermicro there is a feature
2. get latest firmware and driver for controller and flash it and build driver for this system (optional).
3. install over os
4. see in ports arcconf util, need get information and logs from controller.
5. create support adaptec ticket and attach logs to ticket
6. if there is a possibility - change the controller

tracer said:

I've analog situation with my Adaptec 51245 controller with accd and accu drivers.

aac:

Code:

acc0: COMMAND xxx TIMEOUT AFTER xxx SECONDS
Controller is no longer running! code= 0xbc6201100

aacu:

Code:

Too aacu0: COMMAND xxx TIMEOUT AFTER xxx SECONDS

and at some time:

Code:

g_vfs_done():aacdu0s1d[WRITE(offset=xxx, length=xxx)]error = 5

my dmesg:

Code:

Copyright (c) 1992-2009 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 is a registered trademark of The FreeBSD Foundation.
FreeBSD 7.1-RELEASE-p2 #5: Fri May 15 19:17:27 MSD 2009
    [email]tracer@db.loca[/email]ldomain:/usr/obj/usr/src/sys/xxx
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Xeon(R) CPU           X5460  @ 3.16GHz (3166.69-MHz K8-class CPU)
  Origin = "GenuineIntel"  Id = 0x10676  Stepping = 6
  Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
  Features2=0xce3bd<SSE3,RSVD2,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA,<b19>>
  AMD Features=0x20100800<SYSCALL,NX,LM>
  AMD Features2=0x1<LAHF>
  Cores per package: 4
usable memory = 34351538176 (32760 MB)
avail memory  = 33315020800 (31771 MB)
ACPI APIC Table: <PTLTD          APIC  >
FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
 cpu2 (AP): APIC ID:  2
 cpu3 (AP): APIC ID:  3
 cpu4 (AP): APIC ID:  4
 cpu5 (AP): APIC ID:  5
 cpu6 (AP): APIC ID:  6
 cpu7 (AP): APIC ID:  7
ioapic0 <Version 2.0> irqs 0-23 on motherboard
ioapic1 <Version 2.0> irqs 24-47 on motherboard
kbd1 at kbdmux0
acpi0: <PTLTD   RSDT> on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
unknown: I/O range not supported
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0
acpi_hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
Timecounter "HPET" frequency 14318180 Hz quality 900
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib1: <ACPI PCI-PCI bridge> at device 2.0 on pci0
pci1: <ACPI PCI bus> on pcib1
pcib2: <ACPI PCI-PCI bridge> irq 16 at device 0.0 on pci1
pci2: <ACPI PCI bus> on pcib2
pcib3: <ACPI PCI-PCI bridge> irq 16 at device 0.0 on pci2
pci3: <ACPI PCI bus> on pcib3
pcib4: <ACPI PCI-PCI bridge> irq 17 at device 1.0 on pci2
pci4: <ACPI PCI bus> on pcib4
pcib5: <ACPI PCI-PCI bridge> irq 18 at device 2.0 on pci2
pci5: <ACPI PCI bus> on pcib5
em0: <Intel(R) PRO/1000 Network Connection 6.9.6> port 0x2000-0x201f mem 0xf8220000-0xf823ffff,0xf8200000-0xf821ffff irq 18 at device 0.0 on pci5
em0: Using MSI interrupt
em0: [FILTER]
em0: Ethernet address: 00:30:48:c4:2c:c4
em1: <Intel(R) PRO/1000 Network Connection 6.9.6> port 0x2020-0x203f mem 0xf8260000-0xf827ffff,0xf8240000-0xf825ffff irq 19 at device 0.1 on pci5
em1: Using MSI interrupt
em1: [FILTER]
em1: Ethernet address: 00:30:48:c4:2c:c5
pcib6: <ACPI PCI-PCI bridge> at device 0.3 on pci1
pci6: <ACPI PCI bus> on pcib6
pcib7: <ACPI PCI-PCI bridge> at device 4.0 on pci0
pci7: <ACPI PCI bus> on pcib7
pcib8: <ACPI PCI-PCI bridge> at device 6.0 on pci0
pci8: <ACPI PCI bus> on pcib8
pci0: <base peripheral> at device 8.0 (no driver attached)
pcib9: <ACPI PCI-PCI bridge> irq 17 at device 28.0 on pci0
pci9: <ACPI PCI bus> on pcib9
aacu0: <Adaptec RAID 51245> mem 0xf8000000-0xf81fffff irq 16 at device 0.0 on pci9
aacu0: Enabling 64-bit address support
aacu0: Enable Raw I/O
aacu0: Enable 64-bit array
aacu0: Adaptec 51245, aac driver 2.2.4-16343
aacu0: New comm. interface enabled
aacu0: [ITHREAD]
aacpu0: <SCSI Passthrough Bus> on aacu0
aacpu1: <SCSI Passthrough Bus> on aacu0
aacpu2: <SCSI Passthrough Bus> on aacu0
pcib10: <ACPI PCI-PCI bridge> at device 30.0 on pci0
pci10: <ACPI PCI bus> on pcib10
vgapci0: <VGA-compatible display> port 0x3000-0x30ff mem 0xf0000000-0xf7ffffff,0xf8400000-0xf840ffff irq 18 at device 1.0 on pci10
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel 63XXESB2 UDMA100 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1800-0x180f at device 31.1 on pci0
ata0: <ATA channel 0> on atapci0
ata0: [ITHREAD]
ata1: <ATA channel 1> on atapci0
ata1: [ITHREAD]
pci0: <serial bus, SMBus> at device 31.3 (no driver attached)
acpi_button0: <Power Button> on acpi0
atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
atkbd0: [ITHREAD]
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: [GIANT-LOCKED]
psm0: [ITHREAD]
psm0: model IntelliMouse, device ID 3
cpu0: <ACPI CPU> on acpi0
coretemp0: <CPU On-Die Thermal Sensors> on cpu0
est0: <Enhanced SpeedStep Frequency Control> on cpu0
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 4921492106004921
device_attach: est0 attach returned 6
p4tcc0: <CPU Frequency Thermal Control> on cpu0
cpu1: <ACPI CPU> on acpi0
coretemp1: <CPU On-Die Thermal Sensors> on cpu1
est1: <Enhanced SpeedStep Frequency Control> on cpu1
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 4921492106004921
device_attach: est1 attach returned 6
p4tcc1: <CPU Frequency Thermal Control> on cpu1
cpu2: <ACPI CPU> on acpi0
coretemp2: <CPU On-Die Thermal Sensors> on cpu2
est2: <Enhanced SpeedStep Frequency Control> on cpu2
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 4921492106004921
device_attach: est2 attach returned 6
p4tcc2: <CPU Frequency Thermal Control> on cpu2
cpu3: <ACPI CPU> on acpi0
coretemp3: <CPU On-Die Thermal Sensors> on cpu3
est3: <Enhanced SpeedStep Frequency Control> on cpu3
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 4921492106004921
device_attach: est3 attach returned 6
p4tcc3: <CPU Frequency Thermal Control> on cpu3
cpu4: <ACPI CPU> on acpi0
coretemp4: <CPU On-Die Thermal Sensors> on cpu4
est4: <Enhanced SpeedStep Frequency Control> on cpu4
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 4921492106004921
device_attach: est4 attach returned 6
p4tcc4: <CPU Frequency Thermal Control> on cpu4
cpu5: <ACPI CPU> on acpi0
coretemp5: <CPU On-Die Thermal Sensors> on cpu5
est5: <Enhanced SpeedStep Frequency Control> on cpu5
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 4921492106004921
device_attach: est5 attach returned 6
p4tcc5: <CPU Frequency Thermal Control> on cpu5
cpu6: <ACPI CPU> on acpi0
coretemp6: <CPU On-Die Thermal Sensors> on cpu6
est6: <Enhanced SpeedStep Frequency Control> on cpu6
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 4921492106004921
device_attach: est6 attach returned 6
p4tcc6: <CPU Frequency Thermal Control> on cpu6
cpu7: <ACPI CPU> on acpi0
coretemp7: <CPU On-Die Thermal Sensors> on cpu7
est7: <Enhanced SpeedStep Frequency Control> on cpu7
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 4921492106004921
device_attach: est7 attach returned 6
p4tcc7: <CPU Frequency Thermal Control> on cpu7
orm0: <ISA Option ROMs> at iomem 0xc0000-0xcafff,0xcb000-0xd17ff on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
Timecounters tick every 1.000 msec
acd0: DVDROM <DVD-ROM UJDA780/1.50> at ata0-slave UDMA33
aacdu0: <RAID 0/6> on aacu0
aacdu0: 839392MB (1719074816 sectors)
SMP: AP CPU #3 Launched!
SMP: AP CPU #2 Launched!
SMP: AP CPU #1 Launched!
SMP: AP CPU #5 Launched!
SMP: AP CPU #4 Launched!
SMP: AP CPU #7 Launched!
SMP: AP CPU #6 Launched!
Trying to mount root from ufs:/dev/aacdu0s1a
em0: link state changed to UP
em1: link state changed to UP

Last Motherboard and Adapatec controller BIOS and last FreeBSD accu driver.

Click to expand...

This problem is currently under investigation. Last version we are checking now is "support more than 4 GB RAM DMA issue" it's not confirmed yet!!!!. So, check on your systems (who can) with less than 4 GB.

Please, send to me with flag in letter body >>>> for D.Zotov (FreeBSD 7.x problem)

russia_sales@adaptec.com (have to use this addy to prevent spam)

These files:

support.zip (for thise who has ASM installed)
1 In the Enterprise View, click the local or remote system on which the problem is occurring.
2 In the menu bar, select Actions, then click Save support archive.
3 Enter a name for the archive file or accept the default name, then click Save.

also

arcconf getlogs (4 parts)

Provides access to the status and event logs of a controller. You can retrieve four types of logs:



DEVICE—A log of any device errors the controller has encountered.

DEAD—A log that records any occurrences of defunct devices.

EVENT—A log of special events that may have occurred (e.g., rebuilds, LDMs, etc.).

UART— most "recent" 2MB worth of the UART traces

Syntax



ARCCONF GETLOGS <Controller#> <Type> [clear]

Parameters



Controller# is the controller number

Type is one of the following types of log to retrieve:

DEVICE

DEAD

EVENT

UART

Example



ARCCONF GETLOGS 1 DEVICE



If you put a greater-than sign (>) and a filename after any command, the output of the command will be sent to that file. For instance, to capture the output of the getlogs commands you can enter:



ARCCONF GETLOGS 1 UART > uart.log

And /var/log/messages

That could help to identify the problem and make changes if they are from Adaptec FW or driver level.

Di Ma

Dear Dmitry.
I send for you, open trouble ticket and recive more answer from February (now 16 JUNE)
Memory 4Gb, 8Gb - Not essentially.
Problem resolved then change controllers.

approve user urpyLLIKa

From time 2 time life brings quite difficult problem (oh, sound like shit happens) Anyway,,, We know now that sometimes replacement helps but sometimes not. I would like to stress that this problem is under investigation, if it turns to be a hardware problem with cards we will accept it and replace all cards,,,, no problem... but now we can't say so.

My system with 2405 (2 Series cards also had this problem on clients site) 32 works perfectly.

We now have 32 and 64 in Germany 16GB out of the box driver ... so far so good.

So, to help you I need you help.

1. If you make RMA replacement let me know what disti were used and what were S/N of replaced cards I could pick up cards for testing..

2. Some general info

FreeBSD Version:

Architecture:

System Host Memory:

Controller FW Version:

Driver Status – Update or out of the box – Version.

3. Log files from my previous post.


As soon as it's fixed or any assumptions are confirmed we will post it here.

Thank you for your help and understanding.

This problem was never met under Windows. If you tested a FreeBSD problem card under Windows OS and Windows got frozen? How it happened (that's stunningly new info for me)? BSOD? Anything else?

Around 20 complaints FreeBSD 7.x Worldwide.

One ///without this forum/// for Linux.

Zero ///without this forum/// for Windows.

>>>>>Dear Dmitry.
I send for you, open trouble ticket and recive more answer from February (now 16 JUNE)
Memory 4Gb, 8Gb - Not essentially.
Problem resolved then change controllers.
=================================


Please, explain... you sent to me (for sure I answer and take care of all letters) or to Adaptec tech support? If so do you know your ref. number. //I found only one request 090528-000027 about this problem checking stat. data//? But it was sent in May.