Jump to content
RESET Forums (homeservershow.com)

WD RED 8tb (WD80EFZX)


buranov
 Share

Recommended Posts

Hello!

I have a problem with my WD RED 8th and HP MicroServer Gen8.
From time to time my server lost some hdd (in 2 and 3 slot).
I can't see this hdd until power off/on (reset don't help).
OS: CentOS Linux release 7.3.1611 (Core)
kernel: 3.10.0-514.26.2.el7.x86_64
log massages:
Jul 31 11:43:54 srv kernel: ata3.00: exception Emask 0x0 SAct 0xffff800 SErr 0x50000 action 0x6 frozen
Jul 31 11:43:54 srv kernel: ata3: SError: { PHYRdyChg CommWake }
Jul 31 11:43:54 srv kernel: ata3.00: failed command: READ FPDMA QUEUED
Jul 31 11:43:54 srv kernel: ata3.00: cmd 60/20:58:00:d2:2a/00:00:96:01:00/40 tag 11 ncq 16384 in#012 res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Jul 31 11:43:54 srv kernel: ata3.00: status: { DRDY }
Jul 31 11:43:54 srv kernel: ata3.00: failed command: READ FPDMA QUEUED
Jul 31 11:43:54 srv kernel: ata3.00: cmd 60/20:60:20:d2:2a/00:00:96:01:00/40 tag 12 ncq 16384 in#012 res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Jul 31 11:43:54 srv kernel: ata3.00: status: { DRDY }
Jul 31 11:43:54 srv kernel: ata3.00: failed command: READ FPDMA QUEUED
Jul 31 11:43:54 srv kernel: ata3.00: cmd 60/20:68:e0:d1:2a/00:00:96:01:00/40 tag 13 ncq 16384 in#012 res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Jul 31 11:43:54 srv kernel: ata3.00: status: { DRDY }
Jul 31 11:43:54 srv kernel: ata3.00: failed command: READ FPDMA QUEUED
Jul 31 11:43:54 srv kernel: ata3.00: cmd 60/20:70:40:d2:2a/00:00:96:01:00/40 tag 14 ncq 16384 in#012 res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Jul 31 11:43:54 srv kernel: ata3.00: status: { DRDY }
Jul 31 11:43:54 srv kernel: ata3.00: failed command: READ FPDMA QUEUED
Jul 31 11:43:54 srv kernel: ata3.00: cmd 60/20:78:60:d2:2a/00:00:96:01:00/40 tag 15 ncq 16384 in#012 res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Jul 31 11:43:54 srv kernel: ata3.00: status: { DRDY }
Jul 31 11:43:54 srv kernel: ata3.00: failed command: READ FPDMA QUEUED
Jul 31 11:43:54 srv kernel: ata3.00: cmd 60/20:80:80:d2:2a/00:00:96:01:00/40 tag 16 ncq 16384 in#012 res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Jul 31 11:43:54 srv kernel: ata3.00: status: { DRDY }
Jul 31 11:43:54 srv kernel: ata3.00: failed command: READ FPDMA QUEUED
Jul 31 11:43:54 srv kernel: ata3.00: cmd 60/20:88:a0:d2:2a/00:00:96:01:00/40 tag 17 ncq 16384 in#012 res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Jul 31 11:43:54 srv kernel: ata3.00: status: { DRDY }
Jul 31 11:43:54 srv kernel: ata3.00: failed command: READ FPDMA QUEUED
Jul 31 11:43:54 srv kernel: ata3.00: cmd 60/20:90:c0:d2:2a/00:00:96:01:00/40 tag 18 ncq 16384 in#012 res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Jul 31 11:43:54 srv kernel: ata3.00: status: { DRDY }
Jul 31 11:43:54 srv kernel: ata3.00: failed command: READ FPDMA QUEUED
Jul 31 11:43:54 srv kernel: ata3.00: cmd 60/20:98:e0:d2:2a/00:00:96:01:00/40 tag 19 ncq 16384 in#012 res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Jul 31 11:43:54 srv kernel: ata3.00: status: { DRDY }
Jul 31 11:43:54 srv kernel: ata3.00: failed command: READ FPDMA QUEUED
Jul 31 11:43:54 srv kernel: ata3.00: cmd 60/20:a0:00:d3:2a/00:00:96:01:00/40 tag 20 ncq 16384 in#012 res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Jul 31 11:43:54 srv kernel: ata3.00: status: { DRDY }
Jul 31 11:43:54 srv kernel: ata3.00: failed command: READ FPDMA QUEUED
Jul 31 11:43:54 srv kernel: ata3.00: cmd 60/20:a8:20:d3:2a/00:00:96:01:00/40 tag 21 ncq 16384 in#012 res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Jul 31 11:43:54 srv kernel: ata3.00: status: { DRDY }
Jul 31 11:43:54 srv kernel: ata3.00: failed command: READ FPDMA QUEUED
Jul 31 11:43:54 srv kernel: ata3.00: cmd 60/20:b0:40:d3:2a/00:00:96:01:00/40 tag 22 ncq 16384 in#012 res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Jul 31 11:43:54 srv kernel: ata3.00: status: { DRDY }
Jul 31 11:43:54 srv kernel: ata3.00: failed command: READ FPDMA QUEUED
Jul 31 11:43:54 srv kernel: ata3.00: cmd 60/20:b8:60:d3:2a/00:00:96:01:00/40 tag 23 ncq 16384 in#012 res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Jul 31 11:43:54 srv kernel: ata3.00: status: { DRDY }
Jul 31 11:43:54 srv kernel: ata3.00: failed command: READ FPDMA QUEUED
Jul 31 11:43:54 srv kernel: ata3.00: cmd 60/20:c0:c0:d3:2a/00:00:96:01:00/40 tag 24 ncq 16384 in#012 res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Jul 31 11:43:54 srv kernel: ata3.00: status: { DRDY }
Jul 31 11:43:54 srv kernel: ata3.00: failed command: READ FPDMA QUEUED
Jul 31 11:43:54 srv kernel: ata3.00: cmd 60/20:c8:80:d3:2a/00:00:96:01:00/40 tag 25 ncq 16384 in#012 res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Jul 31 11:43:54 srv kernel: ata3.00: status: { DRDY }
Jul 31 11:43:54 srv kernel: ata3.00: failed command: READ FPDMA QUEUED
Jul 31 11:43:54 srv kernel: ata3.00: cmd 60/20:d0:a0:d3:2a/00:00:96:01:00/40 tag 26 ncq 16384 in#012 res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Jul 31 11:43:54 srv kernel: ata3.00: status: { DRDY }
Jul 31 11:43:54 srv kernel: ata3.00: failed command: READ FPDMA QUEUED
Jul 31 11:43:54 srv kernel: ata3.00: cmd 60/20:d8:e0:d3:2a/00:00:96:01:00/40 tag 27 ncq 16384 in#012 res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Jul 31 11:43:54 srv kernel: ata3.00: status: { DRDY }
Jul 31 11:43:54 srv kernel: ata3: hard resetting link
Jul 31 11:44:03 srv kernel: ata3: softreset failed (device not ready)
Jul 31 11:44:03 srv kernel: ata3: hard resetting link
Jul 31 11:44:13 srv kernel: ata3: softreset failed (device not ready)
Jul 31 11:44:13 srv kernel: ata3: hard resetting link
Jul 31 11:44:24 srv kernel: ata3: link is slow to respond, please be patient (ready=0)
Jul 31 11:44:48 srv kernel: ata3: softreset failed (device not ready)
Jul 31 11:44:48 srv kernel: ata3: limiting SATA link speed to 1.5 Gbps
Jul 31 11:44:48 srv kernel: ata3: hard resetting link
Jul 31 11:44:54 srv kernel: ata3: softreset failed (device not ready)
Jul 31 11:44:54 srv kernel: ata3: reset failed, giving up
Jul 31 11:44:54 srv kernel: ata3.00: disabled
Jul 31 11:44:54 srv kernel: ata3: EH complete
Jul 31 11:44:54 srv kernel: sd 2:0:0:0: [sdc] FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Jul 31 11:44:54 srv kernel: sd 2:0:0:0: [sdc] CDB: Read(16) 88 00 00 00 00 01 96 2a d3 e0 00 00 00 20 00 00
Jul 31 11:44:54 srv kernel: blk_update_request: I/O error, dev sdc, sector 6814356448

May be it because of diferent sata version (slot 1 and 2 - sata3, slot 3 and 4 - sata2)?

However my kernel settings is
ibata.force=noncq libata.force=3.0

Any ideas?

P.S.
[root@srv opt]# ./wd5746_64.dat -d?
WD5746 Version 3
Update Drive
Copyright (C) 2014 Western Digital Corporation

-Dn Model String Serial Number Firmware
-D0 WDC WD80EFZX-68UW8N0 VKKWUPXY 83.H0A83
-D1 WDC WD80EFZX-68UW8N0 VLH6G5HY 83.H0A83
-D2 WDC WD80EFZX-68UW8N0 VKK4KLDX 83.H0A83
-D3 WDC WD80EFZX-68UW8N0 VKKXG1HY 83.H0A83
-D4 INTEL SSDSC2BF480A5 CVTR528201K3480EGN TG26
[root@srv opt]# ./wd5746_64.dat -dall
WD5746 Version 3
Update Drive
Copyright (C) 2014 Western Digital Corporation

WDC WD80EFZX-68UW8N0 83.H0A83 Drive update not needed
WDC WD80EFZX-68UW8N0 83.H0A83 Drive update not needed
WDC WD80EFZX-68UW8N0 83.H0A83 Drive update not needed
WDC WD80EFZX-68UW8N0 83.H0A83 Drive update not needed
INTEL SSDSC2BF480A5 TG26 Drive update not needed
[root@srv opt]#

Link to comment
Share on other sites

Well, the good news is that it's probably not your disks that are faulting, since it is happening on two separate drives. The bad news is that this might mean it's your cabling/disk controller/motherboard that's faulty. I would try to connect the drives with known-good SATA cables first, if that doesn't work, you might need to RMA the unit.

 

EDIT: Also a faulting PSU can sometimes cause strange errors, might want to look there too.

 

Good luck!

Edited by fricadelli
Link to comment
Share on other sites

Hello!

 

I thought about it...

1. The server is second. :) I changed previous to new. (I don't think what the matherboard/controller is faulty)

2. If it SATA cables I think I can't start the serverg againe... I don't touch the server. I just power off/on. 

I think about two variant:

1. uncompatible HDD and controller

2. kernel bug (but I can't catch the bug. :( )

 

P.S. How I can check SATA cable?

 

 

Link to comment
Share on other sites

Easiest way would be to replace the old cable with a new cable. Do that first. Are you running in AHCI mode? If not, you could also try that. WR Red:s are popular drives, and gen. 8:s are extremely popular homeservers. I highly doubt that it's some controller/kernel incompatibility going on here.

Link to comment
Share on other sites

Yes, I use AHCI.

I'll try change the cable...

But I doubt in success. :( 

Last time was VERY strange behaviour: 

# fdisk -l 

showed only 1 HDD - 8tb (no other 3 8tb HDD, no system SSD). And in this time OS works fine (SSD disk) and mdadm can work with RAID5 (r/w files)...

Link to comment
Share on other sites

11 hours ago, buranov said:

showed only 1 HDD - 8tb (no other 3 8tb HDD, no system SSD). And in this time OS works fine (SSD disk) and mdadm can work with RAID5 (r/w files)...

Ok? You need to start eliminating the possibilites. I have given you several suggestions.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...