[SOLVED] Getting the odd drive error SAMSUNG_HD204UI


Recommended Posts

Hi, I`m getting the odd drive error on the main unRaid screen and in the logs I get lines like these,

 

Jan 12 15:10:55 Tower kernel: ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Jan 12 15:10:55 Tower kernel: ata8.00: BMDMA stat 0x4

Jan 12 15:10:55 Tower kernel: ata8.00: failed command: READ DMA EXT

Jan 12 15:10:55 Tower kernel: ata8.00: cmd 25/00:08:08:0c:33/00:00:d8:00:00/e0 tag 0 dma 4096 in

Jan 12 15:10:55 Tower kernel:          res 51/40:08:08:0c:33/40:00:d8:00:00/e0 Emask 0x9 (media error)

Jan 12 15:10:55 Tower kernel: ata8.00: status: { DRDY ERR }

Jan 12 15:10:55 Tower kernel: ata8.00: error: { UNC }

Jan 12 15:10:57 Tower kernel: ata8.00: configured for UDMA/133

Jan 12 15:10:57 Tower kernel: sd 8:0:0:0: [sdf] Unhandled sense code

Jan 12 15:10:57 Tower kernel: sd 8:0:0:0: [sdf] 

Jan 12 15:10:57 Tower kernel: Result: hostbyte=0x00 driverbyte=0x08

Jan 12 15:10:57 Tower kernel: sd 8:0:0:0: [sdf] 

Jan 12 15:10:57 Tower kernel: Sense Key : 0x3 [current] [descriptor]

Jan 12 15:10:57 Tower kernel: Descriptor sense data with sense descriptors (in hex):

Jan 12 15:10:57 Tower kernel:        72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00

Jan 12 15:10:57 Tower kernel:        d8 33 0c 08

Jan 12 15:10:57 Tower kernel: sd 8:0:0:0: [sdf] 

Jan 12 15:10:57 Tower kernel: ASC=0x11 ASCQ=0x4

Jan 12 15:10:57 Tower kernel: sd 8:0:0:0: [sdf] CDB:

Jan 12 15:10:57 Tower kernel: cdb[0]=0x28: 28 00 d8 33 0c 08 00 00 08 00

Jan 12 15:10:57 Tower kernel: end_request: I/O error, dev sdf, sector 3627224072

Jan 12 15:10:57 Tower kernel: md: disk2 read error, sector=3627224008

Jan 12 15:10:57 Tower kernel: ata8: EH complete

Jan 12 16:10:08 Tower kernel: ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Jan 12 16:10:08 Tower kernel: ata8.00: BMDMA stat 0x4

Jan 12 16:10:08 Tower kernel: ata8.00: failed command: READ DMA EXT

Jan 12 16:10:08 Tower kernel: ata8.00: cmd 25/00:08:20:6b:69/00:00:df:00:00/e0 tag 0 dma 4096 in

Jan 12 16:10:08 Tower kernel:          res 51/40:08:20:6b:69/40:00:df:00:00/e0 Emask 0x9 (media error)

Jan 12 16:10:08 Tower kernel: ata8.00: status: { DRDY ERR }

Jan 12 16:10:08 Tower kernel: ata8.00: error: { UNC }

Jan 12 16:10:08 Tower kernel: ata8.00: configured for UDMA/133

Jan 12 16:10:08 Tower kernel: sd 8:0:0:0: [sdf] Unhandled sense code

Jan 12 16:10:08 Tower kernel: sd 8:0:0:0: [sdf] 

Jan 12 16:10:08 Tower kernel: Result: hostbyte=0x00 driverbyte=0x08

Jan 12 16:10:08 Tower kernel: sd 8:0:0:0: [sdf] 

Jan 12 16:10:08 Tower kernel: Sense Key : 0x3 [current] [descriptor]

Jan 12 16:10:08 Tower kernel: Descriptor sense data with sense descriptors (in hex):

Jan 12 16:10:08 Tower kernel:        72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00

Jan 12 16:10:08 Tower kernel:        df 69 6b 20

Jan 12 16:10:08 Tower kernel: sd 8:0:0:0: [sdf] 

Jan 12 16:10:08 Tower kernel: ASC=0x11 ASCQ=0x4

Jan 12 16:10:08 Tower kernel: sd 8:0:0:0: [sdf] CDB:

Jan 12 16:10:08 Tower kernel: cdb[0]=0x28: 28 00 df 69 6b 20 00 00 08 00

Jan 12 16:10:08 Tower kernel: end_request: I/O error, dev sdf, sector 3748227872

Jan 12 16:10:08 Tower kernel: md: disk2 read error, sector=3748227808

Jan 12 16:10:08 Tower kernel: ata8: EH complete

 

I was looking on the wiki for drive issues and did a smart report but that looks OK to me, but I must admit that I don`t understand everything that I`m looking at.  I`m guessing from the lines in the syslog that I have some bad sectors on the drive. When I precleared it there were 3 pending re-allocation sectors but they cleared. I have read some bad reports on this drive being a budget Seagate etc.  If someone could have a quick look over logs and reports and just let me know if I should investigate this or not. I bought the drive in 2011 but what did shock me is that the drive is still in warranty until May 14. BTW unRaid version 5.0.4 Plus.

SAMSUNG_HD204UI_smart_report.txt

preclear_finish_SAMSUNG_HD204UI_2014-01-05.doc

preclear_rpt_SAMSUNG_HD204UI_2014-01-05.doc

syslog-2014-01-12.txt

Link to comment

I'm with you...I'm not a big fan of the Samsung drives, but here is one of my smart reports. Normally, no reallocated or pending sectors is a good indicator.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   100   100   051    Pre-fail  Always       -       57
  2 Throughput_Performance  0x0026   252   252   000    Old_age   Always       -       0
  3 Spin_Up_Time            0x0023   067   067   025    Pre-fail  Always       -       10204
  4 Start_Stop_Count        0x0032   099   099   000    Old_age   Always       -       1342
  5 Reallocated_Sector_Ct   0x0033   252   252   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   252   252   051    Old_age   Always       -       0
  8 Seek_Time_Performance   0x0024   252   252   015    Old_age   Offline      -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       2109
10 Spin_Retry_Count        0x0032   252   252   051    Old_age   Always       -       0
11 Calibration_Retry_Count 0x0032   252   252   000    Old_age   Always       -       0
12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       32
181 Program_Fail_Cnt_Total  0x0022   252   252   000    Old_age   Always       -       0
191 G-Sense_Error_Rate      0x0022   100   100   000    Old_age   Always       -       5
192 Power-Off_Retract_Count 0x0022   252   252   000    Old_age   Always       -       0
194 Temperature_Celsius     0x0002   064   063   000    Old_age   Always       -       19 (Min/Max 15/37)
195 Hardware_ECC_Recovered  0x003a   100   100   000    Old_age   Always       -       0
196 Reallocated_Event_Count 0x0032   252   252   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   252   252   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   252   252   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0036   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x002a   100   100   000    Old_age   Always       -       3
223 Load_Retry_Count        0x0032   252   252   000    Old_age   Always       -       0
225 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       1343

 

 

It has an error as shown below

Error 20 occurred at disk power-on lifetime: 12311 hours (512 days + 23 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
  -- -- -- -- -- -- --
  40 51 08 40 00 3c e2  Error: UNC 8 sectors at LBA = 0x023c0040 = 37486656

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 40 00 3c e2 0a      00:00:40.214  READ DMA
  35 00 40 60 14 3b e0 0a      00:00:40.214  WRITE DMA EXT
  35 00 00 60 10 3b e0 0a      00:00:40.214  WRITE DMA EXT
  35 00 00 60 0c 3b e0 0a      00:00:40.214  WRITE DMA EXT
  25 00 40 60 14 3b e0 0a      00:00:40.214  READ DMA EXT[/quote]

I would prepare to swap that drive out. Run a long smart test as well.

Link to comment

Update, couldnt delete the files after I copied them so had to run a Reiser check, after that was finished I deleted the files and folders, removed the drive and let unRaid restart the array.  Put the drive in a windows box to run Seatools and it would not zero the drive or do a long generic smart test, both failed.  Although I was able to do a long generic smart test before I precleared the drive.

 

Anyway got an error code, emailed samsung and two hours later I got an rma number  So I will be getting a replacement drive, hopefully a good one.  Not bad when the drive was manufactured in Feb 2011.

 

Thanks Will

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.