HDD read Errors


Recommended Posts

Hi Guys,

 

I have a problem with one of my drives. It is a new Drive from Western Digital. I tried to preclear this drive, but it fails in Pre-Read.

 

This is a piece of my Disk Log. Maybe some can tell me, if the drive is bad or something else.

Jan 31 18:17:04 PC-Server kernel: sd 11:0:0:0: [sde] tag#0 Sense Key : 0x4 [current]
Jan 31 18:17:04 PC-Server kernel: sd 11:0:0:0: [sde] tag#0 ASC=0x0 ASCQ=0x0
Jan 31 18:17:04 PC-Server kernel: sd 11:0:0:0: [sde] tag#0 CDB: opcode=0x28 28 00 02 39 0a 00 00 00 f0 00
Jan 31 18:17:04 PC-Server kernel: print_req_error: I/O error, dev sde, sector 37292544
Jan 31 18:17:25 PC-Server kernel: sd 11:0:0:0: [sde] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08
Jan 31 18:17:25 PC-Server kernel: sd 11:0:0:0: [sde] tag#0 Sense Key : 0x4 [current]
Jan 31 18:17:25 PC-Server kernel: sd 11:0:0:0: [sde] tag#0 ASC=0x0 ASCQ=0x0
Jan 31 18:17:25 PC-Server kernel: sd 11:0:0:0: [sde] tag#0 CDB: opcode=0x28 28 00 02 39 0a 08 00 00 08 00
Jan 31 18:17:25 PC-Server kernel: print_req_error: I/O error, dev sde, sector 37292552
Jan 31 18:17:25 PC-Server kernel: Buffer I/O error on dev sde, logical block 4661569, async page read
Jan 31 18:17:45 PC-Server kernel: sd 11:0:0:0: [sde] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08
Jan 31 18:17:45 PC-Server kernel: sd 11:0:0:0: [sde] tag#0 Sense Key : 0x4 [current]
Jan 31 18:17:45 PC-Server kernel: sd 11:0:0:0: [sde] tag#0 ASC=0x0 ASCQ=0x0
Jan 31 18:17:45 PC-Server kernel: sd 11:0:0:0: [sde] tag#0 CDB: opcode=0x28 28 00 02 39 0a 08 00 00 08 00
Jan 31 18:17:45 PC-Server kernel: print_req_error: I/O error, dev sde, sector 37292552
Jan 31 18:17:45 PC-Server kernel: Buffer I/O error on dev sde, logical block 4661569, async page read
Jan 31 18:31:33 PC-Server kernel: sd 11:0:0:0: [sde] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x08
Jan 31 18:31:33 PC-Server kernel: sd 11:0:0:0: [sde] tag#0 Sense Key : 0x4 [current]
Jan 31 18:31:33 PC-Server kernel: sd 11:0:0:0: [sde] tag#0 ASC=0x0 ASCQ=0x0

If read this error can appear, when have bad cable or a bad powersupply.

    I change the corresponding SATA cable.

    The Powersupply is from Corsair, I think this isn't the problem.

    I even changed the SATA Controller.

 

The only explanation I have is a bad drive, but this a new one. I got it directly from WD, as replacement for another bad drive I had.

 

Any suggestion would be nice.

Link to comment
197 Current_Pending_Sector  -O--CK   200   200   000    -    2
Error 57 [8] occurred at disk power-on lifetime: 3 hours (0 days + 3 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 08 00 00 02 39 0a 08 e0 00  Error: UNC 8 sectors at LBA = 0x02390a08 = 37292552
Serial Number:    WD-WCC4N3UV6PFX

Personally, I'd return the drive since its only 3 hours old.

Link to comment

Agreed: return to sender.  Had lots of drives dead on arrival in my time.

 

Had a drive not quite failed but prone to future problems based upon SMART information and inconsistent data transfer rates after the first cycle was complete, so I cycled it through preclear for several days until it barfed so I had no hassle at the returns desk.

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.