BlueMagician
Explorer
- Joined
- Apr 24, 2015
- Messages
- 56
Dear all,
I wonder if anyone could shed some light on an error I've received from my FreeNAS box overnight (during a scheduled Scrub):
DA5 is one of the six WD Red drives that make up my RAIDz2 vDEV.
I queried ZPOOL STATUS that morning whilst the scrub was still in progress. It showed that 128KB of data had been fixed, and one of the drives in the status list had '(REPAIRED)' or such, tagged onto it.
I ran an Extended (long) SMART test on DA5 the following evening, and the test completed with no errors.
Most interestingly, the drive is not showing any pending nor any reallocated sectors - so does this mean that the read error was more likely a controller issue than a sector/disc problem?
The drive in question has about 3 months warranty left - so I'm wondering if I need to poke it harder to see if there's an underlying issue, or whether I should just forget this ever happened, and move on.
Sanity check much appreciated! Thank you in advance,
S.
I wonder if anyone could shed some light on an error I've received from my FreeNAS box overnight (during a scheduled Scrub):
Code:
(da5:mps0:0:6:0): READ(16). CDB: 88 00 00 00 00 01 0e a0 06 40 00 00 01 00 00 00 length 131072 SMID 152 terminated ioc 804b scsi 0 state 0 xfer 0 > (da5:mps0:0:6:0): READ(16). CDB: 88 00 00 00 00 01 0e a0 06 40 00 00 01 00 00 00 > (da5:mps0:0:6:0): CAM status: CCB request completed with an error > (da5:mps0:0:6:0): Retrying command > (da5:mps0:0:6:0): READ(16). CDB: 88 00 00 00 00 01 0e a0 05 40 00 00 01 00 00 00 > (da5:mps0:0:6:0): CAM status: SCSI Status Error > (da5:mps0:0:6:0): SCSI status: Check Condition > (da5:mps0:0:6:0): SCSI sense: MEDIUM ERROR asc:11,0 (Unrecovered read error) > (da5:mps0:0:6:0): Info: 0x10ea00540 > (da5:mps0:0:6:0): Error 5, Unretryable error
DA5 is one of the six WD Red drives that make up my RAIDz2 vDEV.
I queried ZPOOL STATUS that morning whilst the scrub was still in progress. It showed that 128KB of data had been fixed, and one of the drives in the status list had '(REPAIRED)' or such, tagged onto it.
I ran an Extended (long) SMART test on DA5 the following evening, and the test completed with no errors.
Most interestingly, the drive is not showing any pending nor any reallocated sectors - so does this mean that the read error was more likely a controller issue than a sector/disc problem?
The drive in question has about 3 months warranty left - so I'm wondering if I need to poke it harder to see if there's an underlying issue, or whether I should just forget this ever happened, and move on.
Sanity check much appreciated! Thank you in advance,
S.