Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 17 Aug 2015 07:56:49 -0500
From:      dweimer <dweimer@dweimer.net>
To:        FreeBSD Questions <freebsd-questions@freebsd.org>
Subject:   Quick Hard Drive Error Question
Message-ID:  <46e87057b2ac9672e581dcd794bf1111@dweimer.net>

next in thread | raw e-mail | index | archive | help
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.


-- 
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?46e87057b2ac9672e581dcd794bf1111>