Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 27 Aug 2018 11:55:00 +0000
From:      ixbug@riseup.net
To:        tech-lists <tech-lists@zyxst.net>, FreeBSD Questions <freebsd-questions@freebsd.org>
Subject:   Re: disk or cable error? (CAM status: ATA Status Error)
Message-ID:  <23f23c0f-11aa-e00c-42a9-8c9865656c2f@riseup.net>
In-Reply-To: <dd5dbfd6-4429-d110-f83f-4b16f8d27c14@zyxst.net>
References:  <c9124cc8-7be9-a0ad-62f3-2ebebbd00a9b@riseup.net> <dd5dbfd6-4429-d110-f83f-4b16f8d27c14@zyxst.net>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help


tech-lists:
> On 26/08/2018 16:01, ixbug@riseup.net wrote:
>> Do any of these errors provide hints as to whether this is a disk
>> error affecting both at the same time or broken cable? (both disks
>> are connected to the mainboard via the same cable)
> 
> these values:
> 
> 5 Reallocated_Sector_Ct
> 196 Reallocated_Event_Count
> 197 Current_Pending_Sector
> 198 Offline_Uncorrectable
> 
> are all zero for both disks, so if these remain zero after a successful long test with *no LBA errors* then that would seem to me at least to indicate there's no problems with the disks themselves. If, in the face of those results, this persisted:
> 
>> (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 08 90 a4 aa 40 1d 00 00 00 00 00
>>  (ada1:ahcich1:0:0:0): CAM status: ATA Status Error
>>  (ada1:ahcich1:0:0:0): ATA status: 41 (DRDY ERR), error: 10 (IDNF )
> 
> then yeah I'd say bad cable/bad interface


thanks for your input.
(long test is running..)



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?23f23c0f-11aa-e00c-42a9-8c9865656c2f>