Cannot add WD drives to array (protection error & Buffer I/O error)

[TastyTomato512]

Good evening

 

Description

I am evaluating the trial of unRAID and having a hard time adding some of my drives to the array. The problem occurs only with Western Digital drives, as it seems. I can add my Seagate drives, be it for parity or for data, without a problem. But after I try to add the WD drives to either of the two (parity/data), they simply disappear. After a reboot they are back again.
Those drives were in a TrueNAS pool before, so I suspect that the drives are healthy. 

 

Hardware

Controller: LSI 9211-8i (as on the recommended list)
Drives: all SAS, 2x Seagate ST4000NM0025 working fine, 2x WD WD4001FYYG not working
CPU: Core2Duo E8500
RAM: 8GB DDR2
Mobo: ASUSTeK Computer INC. P5K , Version Rev 1.xx, Version 1201

Software

unRAID version 6.11.5
No plugins added.

 

Steps taken

Ran Smart Short Self-test which completed.
Checked that cables are properly seated.
Found this thread: https://forums.unraid.net/topic/85471-disappearing-drives/ and then switched TrueNAS on again, deleted the pool & formatted both WD drives (low level wipe over night). Problem persists.

 

Error message

for /dev/sde:

Jan 23 18:19:23 Tower kernel: protection error, dev sde, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 0
Jan 23 18:19:23 Tower  emhttpd: error: ckmbr, 2291: Input/output error (5): read: /dev/sde
Jan 23 18:19:23 Tower  emhttpd: ckmbr error: -1
Jan 23 18:19:23 Tower kernel: mpt2sas_cm0: log_info(0x3112043b): originator(PL), code(0x12), sub_code(0x043b)
Jan 23 18:19:23 Tower kernel: sd 4:0:3:0: [sde] tag#654 UNKNOWN(0x2003) Result: hostbyte=0x05 driverbyte=DRIVER_OK cmd_age=0s
Jan 23 18:19:23 Tower kernel: sd 4:0:3:0: [sde] tag#654 Sense Key : 0x5 [current] 
Jan 23 18:19:23 Tower kernel: sd 4:0:3:0: [sde] tag#654 ASC=0x10 ASCQ=0x3 
Jan 23 18:19:23 Tower kernel: sd 4:0:3:0: [sde] tag#654 CDB: opcode=0x7f, sa=0x9
Jan 23 18:19:23 Tower kernel: sd 4:0:3:0: [sde] tag#654 CDB[00]: 7f 00 00 00 00 00 00 18 00 09 20 00 00 00 00 00
Jan 23 18:19:23 Tower kernel: sd 4:0:3:0: [sde] tag#654 CDB[10]: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 08
Jan 23 18:19:23 Tower kernel: protection error, dev sde, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jan 23 18:19:23 Tower kernel: Buffer I/O error on dev sde, logical block 0, async page read

 

and for /dev/sdd:

Jan 23 18:19:23 Tower kernel: protection error, dev sdd, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 0
Jan 23 18:19:23 Tower kernel: mpt2sas_cm0: log_info(0x3112043b): originator(PL), code(0x12), sub_code(0x043b)
Jan 23 18:19:23 Tower kernel: sd 4:0:2:0: [sdd] tag#656 UNKNOWN(0x2003) Result: hostbyte=0x05 driverbyte=DRIVER_OK cmd_age=0s
Jan 23 18:19:23 Tower kernel: sd 4:0:2:0: [sdd] tag#656 Sense Key : 0x5 [current] 
Jan 23 18:19:23 Tower kernel: sd 4:0:2:0: [sdd] tag#656 ASC=0x10 ASCQ=0x3 
Jan 23 18:19:23 Tower kernel: sd 4:0:2:0: [sdd] tag#656 CDB: opcode=0x7f, sa=0x9
Jan 23 18:19:23 Tower kernel: sd 4:0:2:0: [sdd] tag#656 CDB[00]: 7f 00 00 00 00 00 00 18 00 09 20 00 00 00 00 00
Jan 23 18:19:23 Tower kernel: sd 4:0:2:0: [sdd] tag#656 CDB[10]: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 08
Jan 23 18:19:23 Tower kernel: protection error, dev sdd, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jan 23 18:19:23 Tower kernel: Buffer I/O error on dev sdd, logical block 0, async page read
Jan 23 18:19:23 Tower  emhttpd: error: ckmbr, 2291: Input/output error (5): read: /dev/sdd
Jan 23 18:19:23 Tower  emhttpd: ckmbr error: -1

 

Any hints what's happening here are greatly appreciated.

Best regards

 

Edited January 24 by TastyTomato512

[JorgeB]

Formatted with type 2 protection

You need to remove this:

https://forums.unraid.net/topic/93432-parity-disk-read-errors/?do=findComment&comment=864078

https://forums.unraid.net/topic/110835-help-with-a-sas-drive/

[TastyTomato512]

Excellent! Thank you very much.

 

This solved it for me:

sg_format --format --fmtpinfo=0 /dev/sdX

 

Not sure how this format was different than the wipe I did in TrueNAS, but very glad it works now. Thanks again!

 

Best regards