FreeNAS 11.0-U2 (disk power-on errors)

Status
Not open for further replies.

Andrew076

Patron
Joined
Apr 5, 2015
Messages
206
Is it possible that the new version is causing ATA errors? Specifically I started getting the following errors after the update. At first I thought that it was the drives failing (and they probably were) so I started replacing them. However after burn in and testing (and passing) the new drives are now showing the same error message (see below, this drive is only 165 hours old and already has 2 errors). Just wondering if it is bad luck, in which case I have a lot of it with drives, or if the new version is sending some command that could be causing this. I have no idea if that is even possible, but I wanted the communities feed back, and was wondering if I was alone with this error.

Code:
ATA Error Count: 2
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 2 occurred at disk power-on lifetime: 165 hours (6 days + 21 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  10 51 08 70 02 40 40  Error: IDNF at LBA = 0x00400270 = 4194928

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC  Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ca 00 08 70 02 40 40 08  4d+07:20:44.476  WRITE DMA

Error 1 occurred at disk power-on lifetime: 85 hours (3 days + 13 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  10 51 08 f8 01 40 40  Error: IDNF at LBA = 0x004001f8 = 4194808

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC  Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ca 00 08 f8 01 40 40 08  22:35:08.291  WRITE DMA

Test_Description  Status  Remaining  LifeTime(hours)  LBA_of_first_error
Extended offline  Completed without error  00%  10  -
 

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,194

Andrew076

Patron
Joined
Apr 5, 2015
Messages
206
No.


So that's going to be bad cabling, bad power, bad backplane, ...
Okay, so the error is at disk power-on, where would you suggest I start looking for the fault? With the Power supply?
 

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,194
Yeah, that's a good place to start.
 

Stux

MVP
Joined
Jun 2, 2016
Messages
4,419
Error 2 occurred at disk power-on lifetime: 165 hours

This does not mean the error occurred at disk power-on.

The error is a write UDMA error. Check your Sata cables.
 

Andrew076

Patron
Joined
Apr 5, 2015
Messages
206
This does not mean the error occurred at disk power-on.

The error is a write UDMA error. Check your Sata cables.

Check for what? Breaks or to be sure they are properly attached? If the latter, done. I guess I will see if any more errors occur.
 

Stux

MVP
Joined
Jun 2, 2016
Messages
4,419
Well... best way to check them is to replace them ;)

Alternatively, you move swap the cables between known good and bad drives... ie unplug from the hd, and plug into the other. if the problem moves with the cable, it the cable or port on the mobo. Its normally the cable.

Cheap cables fail overtime because the plug plastic is too thin and flexible, and eventually bulges allowing the cable to form a bad connection to the hd.
 

Andrew076

Patron
Joined
Apr 5, 2015
Messages
206
Well... best way to check them is to replace them ;)

Alternatively, you move swap the cables between known good and bad drives... ie unplug from the hd, and plug into the other. if the problem moves with the cable, it the cable or port on the mobo. Its normally the cable.

Cheap cables fail overtime because the plug plastic is too thin and flexible, and eventually bulges allowing the cable to form a bad connection to the hd.
Anyone have a suggestion for a good brand for the cables? I saw Cable Matters on Amazon and they seem good.
 
Last edited:
Status
Not open for further replies.
Top