Write Errors Digital Sans Enclosure

[VeGeTa-X]

Hi, I have a few errors that have been coming up for the past few months on my 4 bay Digital Sans Enclosure. At first I thought it was a single bad drive that needed to be replaced but closer look and I seeing errors on 4 3 od 4 drives does this mean the enclosure is going to crap out on me soon? or might it be the ESATA connection going to my freenas server?

Mar 26 02:21:44 freenas (ada0:siisch0:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 16 d0 57 79 40 23 00 00 00 00 00
Mar 26 02:21:44 freenas (ada0:siisch0:0:0:0): CAM status: ATA Status Error
Mar 26 02:21:44 freenas (ada0:siisch0:0:0:0): ATA status: 00 ()
Mar 26 02:21:44 freenas (ada0:siisch0:0:0:0): RES: 00 00 00 00 00 00 00 00 00 00 00
Mar 26 02:21:44 freenas (ada0:siisch0:0:0:0): Retrying command

Mar 26 11:33:08 freenas (ada3:siisch0:0:3:0): CAM status: ATA Status Error
Mar 26 11:33:08 freenas (ada3:siisch0:0:3:0): ATA status: 00 ()
Mar 26 11:33:08 freenas (ada3:siisch0:0:3:0): RES: 00 00 00 00 00 00 00 00 00 00 00
Mar 26 11:33:08 freenas (ada3:siisch0:0:3:0): Retrying command
Mar 26 11:33:08 freenas (ada3:siisch0:0:3:0): WRITE_FPDMA_QUEUED. ACB: 61 44 9d 9b 35 40 0d 00 00 00 00 00
Mar 26 11:33:08 freenas (ada3:siisch0:0:3:0): CAM status: ATA Status Error
Mar 26 11:33:08 freenas (ada3:siisch0:0:3:0): ATA status: 00 ()
Mar 26 11:33:08 freenas (ada3:siisch0:0:3:0): RES: 00 00 00 00 00 00 00 00 00 00 00
Mar 26 11:33:08 freenas (ada3:siisch0:0:3:0): Retrying command
Mar 26 11:33:08 freenas (ada3:siisch0:0:3:0): WRITE_FPDMA_QUEUED. ACB: 61 56 1a c5 87 40 23 00 00 00 00 00
Mar 26 11:33:08 freenas (ada3:siisch0:0:3:0): CAM status: Uncorrectable parity/CRC error
Mar 26 11:33:08 freenas (ada3:siisch0:0:3:0): Retrying command
Mar 26 11:33:08 freenas (ada3:siisch0:0:3:0): WRITE_FPDMA_QUEUED. ACB: 61 44 9d 9b 35 40 0d 00 00 00 00 00
Mar 26 11:33:08 freenas (ada3:siisch0:0:3:0): CAM status: Uncorrectable parity/CRC error
Mar 26 11:33:08 freenas (ada3:siisch0:0:3:0): Retrying command


Mar 27 11:54:17 freenas (ada2:siisch0:0:2:0): WRITE_FPDMA_QUEUED. ACB: 61 55 2d e4 30 40 1e 00 00 00 00 00
Mar 27 11:54:17 freenas (ada2:siisch0:0:2:0): CAM status: ATA Status Error
Mar 27 11:54:17 freenas (ada2:siisch0:0:2:0): ATA status: 00 ()
Mar 27 11:54:17 freenas (ada2:siisch0:0:2:0): RES: 00 00 00 00 00 00 00 00 00 00 00
Mar 27 11:54:17 freenas (ada2:siisch0:0:2:0): Retrying command

 

[Darren Myers]

I would never use a external enclosure and use it for FreeNAS....i think thats as bad as using a raid card

 

[VeGeTa-X]

Yeah just wanted to expanded since my freenas server is 4 bay HP Micro Server needed more storage so I decided to expanded 1 1/2 years ago. Its worked pretty well just seeing these errors in logs also sometimes error below but I just clear zfs status message.

CRITICAL: The volume Goku_Volume (ZFS) state is ONLINE: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected.

 

[Ericloewe]

Two things: SATA port multipliers are up there with RAID controllers on the list of things that are almost guaranteed to ruin your data. eSATA enclosures with a chip that does both are thus a genuine very bad idea (tm), regardless of which option you chose.

eSATA is strictly limited to 1m, in practice, like regular SATA. Longer runs are very error -prone.

 

[cyberjock]

I'm with the other two responses. The choice of hardware for this is very illconceived. It's great in theory. In practice we know its just a recipe for disaster. Unless ada0, ada2, and ada3 are failing via SMART output then I'd tend to say that it's the choice of hardware that is to blame.

From a file-server standpoint, external addons can be a disaster in waiting. We've seen quite a few people that pulled the plug on 1/2 of their pool on accident and as a result the disks diverged in the pool by transactions enough that the pool never mounted again. Not the kind of thing you want to happen to your data. ;)