Jump to content

Help me RMA a disk please...

abs0lut.zer0

By abs0lut.zer0
in General Support (V5 and Older)

Recommended Posts

abs0lut.zer0 Enthusiast

abs0lut.zer0

Posted
Posted

my one wd20ears has been giving me errors and i have changed slots and indirectly that means i have changed cables too...

i have taken the drive out of the array and then rebuilt it again and still i get a few errors ...

here is a part of the syslog ..

 

Sep 11 11:22:08 Terok-Nor kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Sep 11 11:22:08 Terok-Nor kernel: ata1.00: failed command: READ DMA EXT

Sep 11 11:22:08 Terok-Nor kernel: ata1.00: cmd 25/00:08:00:f7:ae/00:00:d4:00:00/e0 tag 0 dma 4096 in

Sep 11 11:22:08 Terok-Nor kernel:          res 51/04:08:00:f7:ae/00:00:d4:00:00/e0 Emask 0x1 (device error)

Sep 11 11:22:08 Terok-Nor kernel: ata1.00: status: { DRDY ERR }

Sep 11 11:22:08 Terok-Nor kernel: ata1.00: error: { ABRT }

Sep 11 11:22:08 Terok-Nor kernel: ata1.00: configured for UDMA/133

Sep 11 11:22:08 Terok-Nor kernel: ata1: EH complete

Sep 11 11:22:11 Terok-Nor kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Sep 11 11:22:11 Terok-Nor kernel: ata1.00: failed command: READ DMA EXT

Sep 11 11:22:11 Terok-Nor kernel: ata1.00: cmd 25/00:08:00:f7:ae/00:00:d4:00:00/e0 tag 0 dma 4096 in

Sep 11 11:22:11 Terok-Nor kernel:          res 51/04:08:00:f7:ae/00:00:d4:00:00/e0 Emask 0x1 (device error)

Sep 11 11:22:11 Terok-Nor kernel: ata1.00: status: { DRDY ERR }

Sep 11 11:22:11 Terok-Nor kernel: ata1.00: error: { ABRT }

Sep 11 11:22:11 Terok-Nor kernel: ata1.00: configured for UDMA/133

Sep 11 11:22:11 Terok-Nor kernel: ata1: EH complete

Sep 11 11:22:14 Terok-Nor kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Sep 11 11:22:14 Terok-Nor kernel: ata1.00: failed command: READ DMA EXT

Sep 11 11:22:14 Terok-Nor kernel: ata1.00: cmd 25/00:08:00:f7:ae/00:00:d4:00:00/e0 tag 0 dma 4096 in

Sep 11 11:22:14 Terok-Nor kernel:          res 51/04:08:00:f7:ae/00:00:d4:00:00/e0 Emask 0x1 (device error)

Sep 11 11:22:14 Terok-Nor kernel: ata1.00: status: { DRDY ERR }

Sep 11 11:22:14 Terok-Nor kernel: ata1.00: error: { ABRT }

Sep 11 11:22:14 Terok-Nor kernel: ata1.00: configured for UDMA/133

Sep 11 11:22:14 Terok-Nor kernel: ata1: EH complete

Sep 11 11:22:17 Terok-Nor kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Sep 11 11:22:17 Terok-Nor kernel: ata1.00: failed command: READ DMA EXT

Sep 11 11:22:17 Terok-Nor kernel: ata1.00: cmd 25/00:08:00:f7:ae/00:00:d4:00:00/e0 tag 0 dma 4096 in

Sep 11 11:22:17 Terok-Nor kernel:          res 51/04:08:00:f7:ae/00:00:d4:00:00/e0 Emask 0x1 (device error)

Sep 11 11:22:17 Terok-Nor kernel: ata1.00: status: { DRDY ERR }

Sep 11 11:22:17 Terok-Nor kernel: ata1.00: error: { ABRT }

Sep 11 11:22:17 Terok-Nor kernel: ata1.00: configured for UDMA/133

Sep 11 11:22:17 Terok-Nor kernel: ata1: EH complete

Sep 11 11:22:20 Terok-Nor kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Sep 11 11:22:20 Terok-Nor kernel: ata1.00: failed command: READ DMA EXT

Sep 11 11:22:20 Terok-Nor kernel: ata1.00: cmd 25/00:08:00:f7:ae/00:00:d4:00:00/e0 tag 0 dma 4096 in

Sep 11 11:22:20 Terok-Nor kernel:          res 51/04:08:00:f7:ae/00:00:d4:00:00/e0 Emask 0x1 (device error)

Sep 11 11:22:20 Terok-Nor kernel: ata1.00: status: { DRDY ERR }

Sep 11 11:22:20 Terok-Nor kernel: ata1.00: error: { ABRT }

Sep 11 11:22:20 Terok-Nor kernel: ata1.00: configured for UDMA/133

Sep 11 11:22:20 Terok-Nor kernel: ata1: EH complete

Sep 11 11:22:22 Terok-Nor kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Sep 11 11:22:22 Terok-Nor kernel: ata1.00: failed command: READ DMA EXT

Sep 11 11:22:22 Terok-Nor kernel: ata1.00: cmd 25/00:08:00:f7:ae/00:00:d4:00:00/e0 tag 0 dma 4096 in

Sep 11 11:22:22 Terok-Nor kernel:          res 51/04:08:00:f7:ae/00:00:d4:00:00/e0 Emask 0x1 (device error)

Sep 11 11:22:22 Terok-Nor kernel: ata1.00: status: { DRDY ERR }

Sep 11 11:22:22 Terok-Nor kernel: ata1.00: error: { ABRT }

Sep 11 11:22:22 Terok-Nor kernel: ata1.00: configured for UDMA/133

Sep 11 11:22:22 Terok-Nor kernel: sd 0:0:0:0: [sdb] Result: hostbyte=0x00 driverbyte=0x08

Sep 11 11:22:22 Terok-Nor kernel: sd 0:0:0:0: [sdb] Sense Key : 0xb [current] [descriptor]

Sep 11 11:22:22 Terok-Nor kernel: Descriptor sense data with sense descriptors (in hex):

Sep 11 11:22:22 Terok-Nor kernel:        72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00

Sep 11 11:22:22 Terok-Nor kernel:        d4 ae f7 00

Sep 11 11:22:22 Terok-Nor kernel: sd 0:0:0:0: [sdb] ASC=0x0 ASCQ=0x0

Sep 11 11:22:22 Terok-Nor kernel: sd 0:0:0:0: [sdb] CDB: cdb[0]=0x28: 28 00 d4 ae f7 00 00 00 08 00

Sep 11 11:22:22 Terok-Nor kernel: end_request: I/O error, dev sdb, sector 3568236288

Sep 11 11:22:22 Terok-Nor kernel: ata1: EH complete

Sep 11 11:22:22 Terok-Nor kernel: md: disk3 read error

Sep 11 11:22:22 Terok-Nor kernel: handle_stripe read error: 3568236224/2, count: 1

 

 

what i am asking is how i can prove there is something wrong so i can return the disk as the retailer is full of **** and just plugs it in and formats it and says look it's working ...

 

so what can i do?

 

thanks all..

 

mbryanr Collaborator

mbryanr

Posted
Posted

You could run one of the WD tools, and RMA it through WD.

Run a smart test.

Beat the crap out of it with pre-clear.

 

1.  Your smart test should report that the test was aborted because it could not be read from, but it will say pass.

Example from my recent disk...

Syslog entries (see attached)

 

 

Smart Test

  1        0        0  Completed_read_failure [90% left] (0-65535)

 

Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error

# 1  Short offline       Completed: read failure       90%       532         71131104

# 2  Short offline       Completed: read failure       90%       532         71101112

# 3  Short offline       Completed: read failure       90%       532         71094760

# 4  Short offline       Aborted by host               90%       532         -

# 5  Short offline       Completed without error       00%       426         -

# 6  Short offline       Completed without error       00%       237         -

# 7  Short offline       Completed without error       00%       181         -

 

 

2.  You will also have a count of pending sectors or reallocated that will increase

3.  Run pre-clear...multiple times ;)

 

synosyslog_1.zip

talmania Explorer

talmania

Posted
Posted

Have WD to cross-ship your drive.  Guarenteed to get a different one that way.

 

This...avoid the retailer all together.  And then don't give them anymore of your business!  ;)

Archived

This topic is now archived and is closed to further replies.

Go to topic listing
×
×
  • Create New...