kopuz

Thank you, sure sounds like it could be my issue. Going to look into this now.

I had another Seagate drive in my array go to disabled after recently changing my array to spin down idle drives.. Currently trying to rebuild it in case it came unseated. Not seeing any errors in the SMART but not sure what I am looking for. I RMA'd the first drive that went down so that is still emulated. Really uncomfortable that I have 2 drives in the array down with my dual parity. Shipping from all online vendors and even local BB show weeks for delivery. Does my diagnostics show any error I am not catching? epicenter-diagnostics-20241231-2250.zip

Most importantly Merry Christmas everyone! Thanks for your time.

Interesting. Wasn't digging through log files all day at work so was able to actually focus on the serials and they appear to be different for each of the partitions. epicenter-diagnostics-20241224-2057.zip

Both found drives do have the same serial.

I was mistaken in my original post. I am seeing Unraid detect the drive as 2 7TB drives, so that is working as intended for the Unraid OS. I am not sure I can return my drives just yet so I am bit curious if I was to use one of the drives as a cache pool with 2 x 7 TB. Would that compare in performance to my Old 2x 1 TB SSDs I am using.

Working on it. lscsi doesn't appear to be installed and NerdPack seems to be obsolete now.

I recently acquired 2 x 2x14 14 TB Seagate SAS Mach-2 drives. I put one in my NetApp DS4246 and one directly into my server. The dual actuator drives show up as 7TB drives and only 1 drive each. Is there a way to get Unraid to recognize them as 14TB drive?

I am running the latest version of Unraid with a NetApp ds4243. Few months back I started getting some pretty consistent CRC errors on some drives in the JBOD. I have an extra SAS SFF cable so I decided to swap it to rule out cable failure as the cause of the CRC errors. I powered down both my server and the JBOD and swapped the cables. Didn't see any of the drives in Unraid. I went back to the old cable and still not seeing the drives. I believe I went through every line in the attached logs, but tossing them up just in case I am missing something obvious. Looks like Unraid is still seeing my LSI SAS 2308 RAID Controller still. Attached logs. epicenter-diagnostics-20230806-1531.zip

Replaced 2 of my drives recently that were getting old. I used UD Pre-clear and both replacement drives passed. When replacing the 2nd drive the rebuild completed with no errors but immediately following the device had an error and was disabled by UR. Attached diag file. My apologizes I did reboot the system before downloading the logs. My best course of action? Used to follow a Re-Enable Drive guide but link is no longer working, must be outdated processes. diagnostics-20230404-1425.zip

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.

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?

Adding diag zip epicenter-diagnostics-20220814-2313.zip

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

Any plans to add a custom set Storage Location?