Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 11 Jan 2006 20:04:36 +0100
From:      "Raphael H. Becker" <rabe@p-i-n.com>
To:        freebsd-stable@freebsd.org
Subject:   [6.0-RELEASE] Trouble with
Message-ID:  <20060111200436.C30165@p-i-n.com>

next in thread | raw e-mail | index | archive | help

Hi *,

there's another system causing me headaches:

It is an Intel-Server with onboard SATA-RAID Controller 
(Adaptec Firmware [1]). The two Seagate Barracuda SATA Drives[2] are
configured as RAID1(mirror). The system worked fine, for example cvsup,
bonnie++, make world and so on worked for me for some weeks.

Since I've installed the server in our housing the following happened
just an hour after leaving it:
[...]
Jan  7 12:11:07 top kernel: ar0: WARNING - mirror protection lost. RAID1 array in DEGRADED mode
Jan  7 12:11:07 top kernel: ar0: writing of Adaptec HostRAID metadata is NOT supported yet
Jan  7 12:11:07 top kernel: subdisk4: detached
Jan  7 12:11:07 top kernel: ar0: writing of Adaptec HostRAID metadata is NOT supported yet
Jan  7 12:11:07 top last message repeated 22 times
Jan  7 12:11:07 top kernel: ad4: detached
Jan  7 12:11:07 top kernel: unknown: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=18390271
Jan  7 12:11:07 top kernel: unknown: timeout waiting to issue command
Jan  7 12:11:07 top kernel: unknown: error issueing WRITE_DMA command
Jan  7 12:11:07 top kernel: ar0: writing of Adaptec HostRAID metadata is NOT supported yet
[...]

So Murphy is as redundand as my RAID was configured, he crashed the second disk
(ad6) while running a backup to the external USB-Storage, same things:
TIMEOUT - WRITE_DMA retrying (1 retry left) etc

Few hours later back in the data center the system was at the manual
fsck, the RAID was "optimal" (since FreeBSD was not able to update the
meta-information on the controller), everything was messed up
(out-of-sync, ufs-panics, ... )

I guess the RAID-controller is not fully supported by FreeBSD and the
DMA-Timeouts caused the disks to crash, which damaged the RAID (no
metadata written).

So I guess will need another SATA-RAID-Controller (PCI).  
Which SATA-RAID-controller works "rock solid" with 6.0-RELEASE?

Any other solutions? Known issues? Patches? Ideas?

TIA

Regards

Raphael Becker


Hardware is

atapci1: <Intel 6300ESB SATA150 controller> port 0xe400-0xe407,0xe000-0xe003,0xdc00-0xdc07,0xd800-0xd803,0xd400-0xd40f irq 18 at device 31.2 on pci0
atapci1: failed to enable memory mapping! <-- W*F !?!?
[...]
ad4: 190782MB <Seagate ST3200826AS 3.03> at ata2-master SATA150
ad6: 190782MB <Seagate ST3200826AS 3.03> at ata3-master SATA150
ar0: 190782MB <Adaptec HostRAID RAID1> status: READY
ar0: disk0 READY (master) using ad4 at ata2-master
ar0: disk1 READY (mirror) using ad6 at ata3-master
[...]
atapci1@pci0:31:2:      class=0x01048f card=0x34308086 chip=0x25b08086 rev=0x02 hdr=0x00
    vendor   = 'Intel Corporation'
    device   = '6300ESB Serial ATA Controller (RAID mode)'
    class    = mass storage
    subclass = RAID
[...]

See dmesg.boot[3] and pciconf[4] for more details.

Links & Images:
[1] http://rabe.uugrn.org/uugrn/bilder/top/2006-01-06_18-30-28_001.jpg
[2] http://rabe.uugrn.org/uugrn/bilder/top/2006-01-06_18-21-43_001.jpg
[3] http://rabe.uugrn.org/FreeBSD/top.uugrn.org/dmesg.boot
[4] http://rabe.uugrn.org/FreeBSD/top.uugrn.org/pciconf-vvl.txt




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060111200436.C30165>