Just installed one of my new WD20EARS drives picked up on the recent combo deal from Newegg. The first made a horrible scratching noise shortly after booting up and caused the system to be unresponsive. After a forced shutdown and parity check, I tried the other. This one makes no bad noises, but the preclear has been running all night and now seems to be stuck at 30%. Did I really get two bad drives in one box?

 

Both drivers had the jumper installed on 7/8 before installing. The current stable server has 5 drives (3x - SAMSUNG HD103SI, 1x - WDC WD10EADS-00L and 1x - WDC WD10EARS-00Y). Power comes from a Corsair 400W (don't remember the exact model but I know it was the one that was constantly getting recommended around here for a stable PSU. The two new drives were plugged into a 2 port Promise SATA card that so far has gone unused.

 

Here is a snippet of the syslog if it helps :

Sep 22 07:31:54 Vault kernel: ata2: EH complete
Sep 22 07:31:57 Vault kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Sep 22 07:31:57 Vault kernel: ata2.00: irq_stat 0x00060002, device error via D2H FIS
Sep 22 07:31:57 Vault kernel: ata2.00: failed command: READ DMA EXT
Sep 22 07:31:57 Vault kernel: ata2.00: cmd 25/00:08:30:28:40/00:00:46:00:00/e0 tag 0 dma 4096 in
Sep 22 07:31:57 Vault kernel:          res 51/40:00:37:28:40/ca:00:46:00:00/e0 Emask 0x9 (media error)
Sep 22 07:31:57 Vault kernel: ata2.00: status: { DRDY ERR }
Sep 22 07:31:57 Vault kernel: ata2.00: error: { UNC }
Sep 22 07:31:57 Vault kernel: ata2.00: configured for UDMA/33
Sep 22 07:31:57 Vault kernel: sd 2:0:0:0: [sdb] Unhandled sense code
Sep 22 07:31:57 Vault kernel: sd 2:0:0:0: [sdb] Result: hostbyte=0x00 driverbyte=0x08
Sep 22 07:31:57 Vault kernel: sd 2:0:0:0: [sdb] Sense Key : 0x3 [current] [descriptor]
Sep 22 07:31:57 Vault kernel: Descriptor sense data with sense descriptors (in hex):
Sep 22 07:31:57 Vault kernel:         72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 
Sep 22 07:31:57 Vault kernel:         46 40 28 37 
Sep 22 07:31:57 Vault kernel: sd 2:0:0:0: [sdb] ASC=0x11 ASCQ=0x4
Sep 22 07:31:57 Vault kernel: sd 2:0:0:0: [sdb] CDB: cdb[0]=0x28: 28 00 46 40 28 30 00 00 08 00
Sep 22 07:31:57 Vault kernel: end_request: I/O error, dev sdb, sector 1178609719
Sep 22 07:31:57 Vault kernel: Buffer I/O error on device sdb, logical block 147326214
Sep 22 07:31:57 Vault kernel: ata2: EH complete
Sep 22 07:32:00 Vault kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Sep 22 07:32:00 Vault kernel: ata2.00: irq_stat 0x00060002, device error via D2H FIS
Sep 22 07:32:00 Vault kernel: ata2.00: failed command: READ DMA EXT
Sep 22 07:32:00 Vault kernel: ata2.00: cmd 25/00:08:90:69:40/00:00:46:00:00/e0 tag 0 dma 4096 in
Sep 22 07:32:00 Vault kernel:          res 51/40:00:97:69:40/ca:00:46:00:00/e0 Emask 0x9 (media error)
Sep 22 07:32:00 Vault kernel: ata2.00: status: { DRDY ERR }
Sep 22 07:32:00 Vault kernel: ata2.00: error: { UNC }
Sep 22 07:32:00 Vault kernel: ata2.00: configured for UDMA/33
Sep 22 07:32:00 Vault kernel: ata2: EH complete
Sep 22 07:32:02 Vault kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Sep 22 07:32:02 Vault kernel: ata2.00: irq_stat 0x00060002, device error via D2H FIS
Sep 22 07:32:02 Vault kernel: ata2.00: failed command: READ DMA EXT
Sep 22 07:32:02 Vault kernel: ata2.00: cmd 25/00:08:90:69:40/00:00:46:00:00/e0 tag 0 dma 4096 in
Sep 22 07:32:02 Vault kernel:          res 51/40:00:97:69:40/ca:00:46:00:00/e0 Emask 0x9 (media error)
Sep 22 07:32:02 Vault kernel: ata2.00: status: { DRDY ERR }
Sep 22 07:32:02 Vault kernel: ata2.00: error: { UNC }
Sep 22 07:32:02 Vault kernel: ata2.00: configured for UDMA/33
Sep 22 07:32:02 Vault kernel: ata2: EH complete
Sep 22 07:32:05 Vault kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Sep 22 07:32:05 Vault kernel: ata2.00: irq_stat 0x00060002, device error via D2H FIS
Sep 22 07:32:05 Vault kernel: ata2.00: failed command: READ DMA EXT
Sep 22 07:32:05 Vault kernel: ata2.00: cmd 25/00:08:90:69:40/00:00:46:00:00/e0 tag 0 dma 4096 in
Sep 22 07:32:05 Vault kernel:          res 51/40:00:97:69:40/ca:00:46:00:00/e0 Emask 0x9 (media error)
Sep 22 07:32:05 Vault kernel: ata2.00: status: { DRDY ERR }
Sep 22 07:32:05 Vault kernel: ata2.00: error: { UNC }
Sep 22 07:32:05 Vault kernel: ata2.00: configured for UDMA/33
Sep 22 07:32:05 Vault kernel: ata2: EH complete
Sep 22 07:32:08 Vault kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Sep 22 07:32:08 Vault kernel: ata2.00: irq_stat 0x00060002, device error via D2H FIS
Sep 22 07:32:08 Vault kernel: ata2.00: failed command: READ DMA EXT
Sep 22 07:32:08 Vault kernel: ata2.00: cmd 25/00:08:90:69:40/00:00:46:00:00/e0 tag 0 dma 4096 in
Sep 22 07:32:08 Vault kernel:          res 51/40:00:97:69:40/ca:00:46:00:00/e0 Emask 0x9 (media error)
Sep 22 07:32:08 Vault kernel: ata2.00: status: { DRDY ERR }
Sep 22 07:32:08 Vault kernel: ata2.00: error: { UNC }
Sep 22 07:32:08 Vault kernel: ata2.00: configured for UDMA/33
Sep 22 07:32:08 Vault kernel: ata2: EH complete
Sep 22 07:32:10 Vault kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Sep 22 07:32:10 Vault kernel: ata2.00: irq_stat 0x00060002, device error via D2H FIS
Sep 22 07:32:10 Vault kernel: ata2.00: failed command: READ DMA EXT
Sep 22 07:32:10 Vault kernel: ata2.00: cmd 25/00:08:90:69:40/00:00:46:00:00/e0 tag 0 dma 4096 in
Sep 22 07:32:10 Vault kernel:          res 51/40:00:97:69:40/ca:00:46:00:00/e0 Emask 0x9 (media error)
Sep 22 07:32:10 Vault kernel: ata2.00: status: { DRDY ERR }
Sep 22 07:32:10 Vault kernel: ata2.00: error: { UNC }
Sep 22 07:32:10 Vault kernel: ata2.00: configured for UDMA/33
Sep 22 07:32:10 Vault kernel: ata2: EH complete
Sep 22 07:32:13 Vault kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Sep 22 07:32:13 Vault kernel: ata2.00: irq_stat 0x00060002, device error via D2H FIS
Sep 22 07:32:13 Vault kernel: ata2.00: failed command: READ DMA EXT
Sep 22 07:32:13 Vault kernel: ata2.00: cmd 25/00:08:90:69:40/00:00:46:00:00/e0 tag 0 dma 4096 in
Sep 22 07:32:13 Vault kernel:          res 51/40:00:97:69:40/ca:00:46:00:00/e0 Emask 0x9 (media error)
Sep 22 07:32:13 Vault kernel: ata2.00: status: { DRDY ERR }
Sep 22 07:32:13 Vault kernel: ata2.00: error: { UNC }
Sep 22 07:32:13 Vault kernel: ata2.00: configured for UDMA/33
Sep 22 07:32:13 Vault kernel: sd 2:0:0:0: [sdb] Unhandled sense code
Sep 22 07:32:13 Vault kernel: sd 2:0:0:0: [sdb] Result: hostbyte=0x00 driverbyte=0x08
Sep 22 07:32:13 Vault kernel: sd 2:0:0:0: [sdb] Sense Key : 0x3 [current] [descriptor]
Sep 22 07:32:13 Vault kernel: Descriptor sense data with sense descriptors (in hex):
Sep 22 07:32:13 Vault kernel:         72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 
Sep 22 07:32:13 Vault kernel:         46 40 69 97 
Sep 22 07:32:13 Vault kernel: sd 2:0:0:0: [sdb] ASC=0x11 ASCQ=0x4
Sep 22 07:32:13 Vault kernel: sd 2:0:0:0: [sdb] CDB: cdb[0]=0x28: 28 00 46 40 69 90 00 00 08 00
Sep 22 07:32:13 Vault kernel: end_request: I/O error, dev sdb, sector 1178626455
Sep 22 07:32:13 Vault kernel: Buffer I/O error on device sdb, logical block 147328306
Sep 22 07:32:13 Vault kernel: ata2: EH complete

 

I'll try putting the drive on the one remaining onboard SATA and see if that makes a difference while at work, but I'm certainly open to any thoughts based on current data.

 

Thanks much.

 

David

Those are all media errors.

 

If you get a smart report you'll probably see a lot of sectors re-allocated or pending re-allocation.

That's what I was afraid of Joe. I started up another preclear cycle before leaving for work. This time it's hooked up to the onboard SATA, but it certainly seems like I'll be RMAing both drives. I've never had a DOA drive before and now I get 2 at once. What are the odds?

That's what I was afraid of Joe. I started up another preclear cycle before leaving for work. This time it's hooked up to the onboard SATA, but it certainly seems like I'll be RMAing both drives. I've never had a DOA drive before and now I get 2 at once. What are the odds?

 

If they were bought at the same time from the same retailer the odds are actually higher than you would think.  I try to avoid buying same brand drives from the same place all at one time.  Its the main reason i have a mix of WD, Seagate, Hitachi, and Samsung drives in my server.

I guess I've learned a lesson about buying strategy At least Newegg customer service is top notch. Their providing a prepaid shipping label to get the drives back to them for the RMA. Hopefully the replacements fare better.