Drive will not mount in Unraid, but is on Windows device (Solved, USER ERORR)

[kopuz]

Hello,

 

Running Unraid with a NetApp ds4246 jbod.  The shelf currently has multiple drives working in Unraid.  Recently bought a WD 12TB drive that I was able to mount in Windows and appeared to be working as intended.  However in Unraid I never see it as a usable drive.  Syslog shows Read Capacity fail.   Anything else I can check?  Just not able to declare the drive DOA since Windows mounted it.

 

Aug 14 22:39:59 EPICENTER kernel: scsi 23:0:25:0: Direct-Access     WDC      WD1002FBYS-XXXXXXXX PQ: 0 ANSI: 5
Aug 14 22:39:59 EPICENTER kernel: scsi 23:0:25:0: SSP: handle(0x001e), sas_addr(0x5), phy(26), device_name(0x5)
Aug 14 22:39:59 EPICENTER kernel: scsi 23:0:25:0: enclosure logical id (0x5), slot(18) 
Aug 14 22:39:59 EPICENTER kernel: scsi 23:0:25:0: qdepth(254), tagged(1), scsi_level(6), cmd_que(1)
Aug 14 22:39:59 EPICENTER kernel: scsi 23:0:25:0: Power-on or device reset occurred
Aug 14 22:39:59 EPICENTER kernel: sd 23:0:25:0: Attached scsi generic sg21 type 0
Aug 14 22:39:59 EPICENTER kernel: end_device-23:0:25: add: handle(0x001e), sas_addr(0x500605ba000a8b19)
Aug 14 22:39:59 EPICENTER kernel: sd 23:0:25:0: [sdv] Spinning up disk...
Aug 14 22:40:17 EPICENTER kernel: .................not responding...
Aug 14 22:40:17 EPICENTER kernel: sd 23:0:25:0: [sdv] Read Capacity(16) failed: Result: hostbyte=0x00 driverbyte=0x08
Aug 14 22:40:17 EPICENTER kernel: sd 23:0:25:0: [sdv] Sense Key : 0xb [current] 
Aug 14 22:40:17 EPICENTER kernel: sd 23:0:25:0: [sdv] ASC=0x44 ASCQ=0x0 
Aug 14 22:40:17 EPICENTER kernel: sd 23:0:25:0: [sdv] Read Capacity(10) failed: Result: hostbyte=0x00 driverbyte=0x08
Aug 14 22:40:17 EPICENTER kernel: sd 23:0:25:0: [sdv] Sense Key : 0xb [current] 
Aug 14 22:40:17 EPICENTER kernel: sd 23:0:25:0: [sdv] ASC=0x44 ASCQ=0x0 
Aug 14 22:40:17 EPICENTER kernel: sd 23:0:25:0: [sdv] 0 512-byte logical blocks: (0 B/0 B)
Aug 14 22:40:17 EPICENTER kernel: sd 23:0:25:0: [sdv] 0-byte physical blocks
Aug 14 22:40:17 EPICENTER kernel: sd 23:0:25:0: [sdv] Write Protect is off
Aug 14 22:40:17 EPICENTER kernel: sd 23:0:25:0: [sdv] Mode Sense: 1f 00 00 08
Aug 14 22:40:17 EPICENTER kernel: sd 23:0:25:0: [sdv] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Aug 14 22:40:17 EPICENTER kernel: sd 23:0:25:0: [sdv] Unit Not Ready
Aug 14 22:40:17 EPICENTER kernel: sd 23:0:25:0: [sdv] Sense Key : 0xb [current] 
Aug 14 22:40:17 EPICENTER kernel: sd 23:0:25:0: [sdv] ASC=0x44 ASCQ=0x0 
Aug 14 22:40:17 EPICENTER kernel: sd 23:0:25:0: [sdv] Read Capacity(16) failed: Result: hostbyte=0x00 driverbyte=0x08
Aug 14 22:40:17 EPICENTER kernel: sd 23:0:25:0: [sdv] Sense Key : 0xb [current] 
Aug 14 22:40:17 EPICENTER kernel: sd 23:0:25:0: [sdv] ASC=0x44 ASCQ=0x0 
Aug 14 22:40:17 EPICENTER kernel: sd 23:0:25:0: [sdv] Read Capacity(10) failed: Result: hostbyte=0x00 driverbyte=0x08
Aug 14 22:40:17 EPICENTER kernel: sd 23:0:25:0: [sdv] Sense Key : 0xb [current] 
Aug 14 22:40:17 EPICENTER kernel: sd 23:0:25:0: [sdv] ASC=0x44 ASCQ=0x0 
Aug 14 22:40:17 EPICENTER kernel: sd 23:0:25:0: [sdv] Attached SCSI disk

 

Edited August 15, 2022 by kopuz

[kopuz]

Adding diag zip

epicenter-diagnostics-20220814-2313.zip

[JorgeB]

Disk is not even giving a valid SMART report, so looks like a disk problem. though you're suing SAS interposers, you can try without that.

[kopuz]

Thank you for the reply.  Need to use the inerposers so I went and tried a number of them.  All the same issue.

 

Does Unraid have a requirement for the SMART reports to be readable where Windows doesn't care?  Thus the drive working on windows and not in Unraid?

[trurl]

28 minutes ago, kopuz said:

Windows doesn't care?  Thus the drive working on windows and not in Unraid?

Windows doesn't care much about your data integrity.

[JorgeB]

34 minutes ago, kopuz said:

Does Unraid have a requirement for the SMART reports to be readable where Windows doesn't care? 

No, but the fact that it is not working suggests a device problem, SMART is independent of Unraid.

 

35 minutes ago, kopuz said:

Need to use the inerposers

 

Why? The shelf works with SATA, interposers are preventing you from monitoring SMART for all connected SATA devices.

 

[kopuz]

Ignorance has struck again.  Thank you for the education. 

 

Removed the interposer and the drive showed up immediately.  Initial SMART report passed.  If I gave excuses I am sure I would have a dandy of one. 

 

Thank you very much.