2 new drives both reported errors during mover, bad drives?

March 21, 20188 yr

I am using two new seagate 8tb (ST8000DM004) drives both less than 30 days old ( horrible drives btw ). I woke up this morning with errors on the parity disks (around 5k of them). And smart errors on both drives. Do you guys think this is a drive issue or some other type of issue. I think its werid BOTH drive would start failing at the SAME time so early.

Quote


ATA Error Count: 198 (device log contains only the most recent five errors)
	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 198 occurred at disk power-on lifetime: 509 hours (21 days + 5 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 53 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 00 ff ff ff ef 00      07:19:48.623  READ DMA EXT
  27 00 00 00 00 00 e0 00      07:19:48.620  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 00 00 a0 00      07:19:48.600  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      07:19:48.598  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00      07:19:48.596  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]

Error 197 occurred at disk power-on lifetime: 509 hours (21 days + 5 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 53 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 00 ff ff ff ef 00      07:19:43.743  READ DMA EXT
  27 00 00 00 00 00 e0 00      07:19:43.740  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 00 00 a0 00      07:19:43.720  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      07:19:43.718  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00      07:19:43.716  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]

Error 196 occurred at disk power-on lifetime: 509 hours (21 days + 5 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 53 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 00 ff ff ff ef 00      07:19:38.911  READ DMA EXT
  27 00 00 00 00 00 e0 00      07:19:38.907  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 00 00 a0 00      07:19:38.888  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      07:19:38.886  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00      07:19:38.883  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]

Error 195 occurred at disk power-on lifetime: 509 hours (21 days + 5 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 53 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 00 ff ff ff ef 00      07:19:34.110  READ DMA EXT
  27 00 00 00 00 00 e0 00      07:19:34.107  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 00 00 a0 00      07:19:34.088  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      07:19:34.085  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00      07:19:34.083  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]

Error 194 occurred at disk power-on lifetime: 509 hours (21 days + 5 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 53 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 00 ff ff ff ef 00      07:19:29.446  READ DMA EXT
  27 00 00 00 00 00 e0 00      07:19:29.443  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 00 00 a0 00      07:19:29.423  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      07:19:29.421  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00      07:19:29.419  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]

From syslog

Quote

Mar 20 23:26:26 Icarus root: move: file /mnt/cache/Data/TV/Trailer Park Boys/2005 - Trailer Park Boys - Season 5/Trailer Park Boys - S05E10 - The Shit Blizzard.tbn
Mar 20 23:26:55 Icarus kernel: ata18.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
Mar 20 23:26:55 Icarus kernel: ata18.00: edma_err_cause=00000084 pp_flags=00000001, dev error, EDMA self-disable
Mar 20 23:26:55 Icarus kernel: ata18.00: failed command: READ DMA EXT
Mar 20 23:26:55 Icarus kernel: ata18.00: cmd 25/00:00:18:92:91/00:04:ac:00:00/e0 tag 24 dma 524288 in
Mar 20 23:26:55 Icarus kernel: res 53/40:00:38:95:91/40:00:ac:00:00/00 Emask 0x8 (media error)
Mar 20 23:26:55 Icarus kernel: ata18.00: status: { DRDY SENSE ERR }
Mar 20 23:26:55 Icarus kernel: ata18.00: error: { UNC }
Mar 20 23:26:55 Icarus kernel: ata18: hard resetting link
Mar 20 23:26:55 Icarus kernel: ata18: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar 20 23:26:55 Icarus kernel: ata18.00: configured for UDMA/133
Mar 20 23:26:55 Icarus kernel: ata18: EH complete
Mar 20 23:27:01 Icarus kernel: ata18.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
Mar 20 23:27:01 Icarus kernel: ata18.00: edma_err_cause=00000084 pp_flags=00000001, dev error, EDMA self-disable
Mar 20 23:27:01 Icarus kernel: ata18.00: failed command: READ DMA EXT
Mar 20 23:27:01 Icarus kernel: ata18.00: cmd 25/00:00:18:92:91/00:04:ac:00:00/e0 tag 26 dma 524288 in
Mar 20 23:27:01 Icarus kernel: res 53/40:00:38:95:91/40:00:ac:00:00/00 Emask 0x8 (media error)
Mar 20 23:27:01 Icarus kernel: ata18.00: status: { DRDY SENSE ERR }
Mar 20 23:27:01 Icarus kernel: ata18.00: error: { UNC }
Mar 20 23:27:01 Icarus kernel: ata18: hard resetting link
Mar 20 23:27:02 Icarus kernel: ata18: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar 20 23:27:02 Icarus kernel: ata18.00: configured for UDMA/133
Mar 20 23:27:02 Icarus kernel: sd 22:0:0:0: [sdl] tag#26 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Mar 20 23:27:02 Icarus kernel: sd 22:0:0:0: [sdl] tag#26 Sense Key : 0x3 [current]
Mar 20 23:27:02 Icarus kernel: sd 22:0:0:0: [sdl] tag#26 ASC=0x16 ASCQ=0x0
Mar 20 23:27:02 Icarus kernel: sd 22:0:0:0: [sdl] tag#26 CDB: opcode=0x88 88 00 00 00 00 00 ac 91 92 18 00 00 04 00 00 00
Mar 20 23:27:02 Icarus kernel: print_req_error: I/O error, dev sdl, sector 2895221272
Mar 20 23:27:02 Icarus kernel: md: disk29 read error, sector=2895221208
Mar 20 23:27:02 Icarus kernel: ata18: EH complete
Mar 20 23:27:02 Icarus kernel: md: disk29 read error, sector=2895221216
Mar 20 23:27:02 Icarus kernel: md: disk29 read error, sector=2895221224
Mar 20 23:27:02 Icarus kernel: md: disk29 read error, sector=2895221232
Mar 20 23:27:02 Icarus kernel: md: disk29 read error, sector=2895221240
Mar 20 23:27:02 Icarus kernel: md: disk29 read error, sector=2895221248
Mar 20 23:27:02 Icarus kernel: md: disk29 read error, sector=2895221256
Mar 20 23:27:02 Icarus kernel: md: disk29 read error, sector=2895221264
Mar 20 23:27:02 Icarus kernel: md: disk29 read error, sector=2895221272
Mar 20 23:27:02 Icarus kernel: md: disk29 read error, sector=2895221280
Mar 20 23:27:02 Icarus kernel: md: disk29 read error, sector=2895221288
Mar 20 23:27:02 Icarus kernel: md: disk29 read error, sector=2895221296
Mar 20 23:27:02 Icarus kernel: md: disk29 read error, sector=2895221304
Mar 20 23:27:02 Icarus kernel: md: disk29 read error, sector=2895221312

ETC....

ST8000DM004-2CX188_WCT09B3G-20180321-0856.txt

ST8000DM004-2CX188_WCT09B3G-20180321-0859.txt

syslog.1.txt

Quote

March 21, 20188 yr

Community Expert

It's strange the same number of UNC on both, and with a bogus LBA, run an extended test on both.

Quote

2 new drives both reported errors during mover, bad drives?

Featured Replies

Archived

Account

Navigation

Search

Configure browser push notifications

Chrome (Android)

Chrome (Desktop)

Safari (iOS 16.4+)

Safari (macOS)

Edge (Android)

Edge (Desktop)

Firefox (Android)

Firefox (Desktop)