Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 17 Aug 2015 11:16:13 -0500
From:      dweimer <dweimer@dweimer.net>
To:        "William A. Mahaffey III" <wam@hiwaay.net>
Cc:        FreeBSD Questions <freebsd-questions@freebsd.org>, owner-freebsd-questions@freebsd.org
Subject:   Re: Quick Hard Drive Error Question
Message-ID:  <5c64233984c92f7ad32c5c001ba89349@dweimer.net>
In-Reply-To: <55D1DE33.1060208@hiwaay.net>
References:  <46e87057b2ac9672e581dcd794bf1111@dweimer.net> <55D1DE33.1060208@hiwaay.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On 2015-08-17 8:19 am, William A. Mahaffey III wrote:
> On 08/17/15 08:03, dweimer wrote:
>> I have an external SATA drive dock that I use to write backups to, I 
>> have steadily been getting more parity/CRC errors over the last couple 
>> of weeks.
>> 
>> 
>> Aug 17 00:14:14 freebsd kernel: (ada4:ahcich5:0:0:0): 
>> WRITE_FPDMA_QUEUED. ACB: 61 00 70 e7 53 40 85 00 00 01 00 00
>> Aug 17 00:14:14 freebsd kernel: (ada4:ahcich5:0:0:0): CAM status: 
>> Uncorrectable parity/CRC error
>> Aug 17 00:14:14 freebsd kernel: (ada4:ahcich5:0:0:0): Retrying command
>> Aug 17 00:14:14 freebsd kernel: (ada4:ahcich5:0:0:0): 
>> READ_FPDMA_QUEUED. ACB: 60 70 d0 c6 1c 40 84 00 00 00 00 00
>> Aug 17 00:14:14 freebsd kernel: (ada4:ahcich5:0:0:0): CAM status: 
>> Uncorrectable parity/CRC error
>> Aug 17 00:14:14 freebsd kernel: (ada4:ahcich5:0:0:0): Retrying command
>> 
>> I have ran smart tests on the drives, they report no errors, hers the 
>> most recent summary line from the currently mounted drive.
>> 
>> Num  Test_Description    Status                  Remaining 
>> LifeTime(hours)  LBA_of_first_error
>> # 1  Extended offline    Completed without error       00% 595         
>> -
>> 
>> I suspect since the smart tests are showing no errors, that the issue 
>> is with the drive dock or cabling. I am using a internal/external SATA 
>> bracket, and not receiving any errors on the internal drives so I 
>> don't suspect it's a controller issue with the on board SATA III 
>> controller.
>> 
>> The current drive dock and cables are SATA II, I have since upgraded 
>> to SATA III 2TB drives since it was purchased along with 1TB SATA II 
>> drives. So I have been considering purchasing a new SATA III dock and 
>> cables anyways, but just in case I need to spend the money somewhere 
>> else to fix this issue I just wanted to see if anyone else had any 
>> other ideas on what might cause this scenario.
> 
> 
> I have heard people on other lists lament eSATA drives/connectors/etc.
> *LOUDLY*, as in wailing, moaning, rending-of-garments,
> gnashing-of-teeth, etc. $0.02, no more, no less, YMMV, IANAL, & all
> that rot. I use external USB-drives myself when I use external drives,
> which isn't often, I have had trouble w/ them as well, short
> drive-life due to running hot. Good luck :-/ ....
> 

I have had decent luck with them, using WD Green drives, they are only 
used for backups, (3 disks) rotated weekly. Most of the time they are 
spun down sitting idle. Of course the room is kept at a cool 
temperature, I have been using this dock for about 3 years. 2.5 years 
with the original 1TB disks, and the last 6 months with the 2TB disks. I 
have had only one drive fail, and it was still under warranty and WD 
replaced it for only shipping cost.

The external/internal bracket was added when I switched to the 2TB disks 
which was shortly after a system board replacement, old system board 
didn't support hot plug on the on board sata. Those brackets and cabling 
are sold cheap, low margin passive devices, so I considered just 
replacing it. However I have been looking at some of the newer drive 
docks with SATA III. I went ahead and ordered one that mounts in a 5.25 
drive bay and makes use of the case's fans to help keep drive cool. It 
just uses a standard internal SATA cable and power, so its less thing 
taking up desk space, and one less power adapter plugged the UPS, and 
hopefully cleans up my errors. I have done some spot checks of restores, 
and it appears that so far the ZFS storage is doing its job and keeping 
the data intact. But I will feel better if I stopping seeing these 
errors in logs after each backup.

-- 
Thanks,
    Dean E. Weimer
    http://www.dweimer.net/



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