Good afternoon,

For background/reference, see https://forums.unraid.net/topic/191918-array-upgrade-questionplan/. I rearranged/added drives and the parity recalculation just completed.

I stopped the array and got a notification that one of the drives had read errors, went disabled, and then resolved (?), yet the drive still shows as disabled.

The drive in question is one of my former 16TB parity drives. It was empty. I restarted the array (without making any changes) and the drive shows as emulated.

Did the drive die when I stopped the array? I really hope not, but if so at least there's no data lost.

Please take a look at the diags (attached) and let me know what's going on and if there's any help for this drive...

TIA!!

nasbox-u1-diagnostics-20250715-1647.zip

FYI,

I have tried starting in maintenance mode, stopping the array, reassigning the disk, and starting again.

Problem is when I try to select it in the dropdown. It's there, I select it, then the page blinks and the drive disappears from the list and it's not assigned.

Edited July 16, 2025Jul 16 by SickPup404
spelling

have you tried to reboot (with power down) or at least pull out the power cable from the drive (and put it back in again after a few seconds) ?

(and check the cables of course, maybe one of them became loose?)

Disk is dropping offline; try replacing cables like mentioned, both power and SATA.

Sorry for the delay in responding, was busy with other stuff.

I pulled the drive and reseated the cables. Array is rebuilding now.

Thank you both for your help/advice, I appreciate it!

Well, apparently I spoke too soon....

The rebuild finished, everything was fine for about two hours, I stopped the array to rearrange disk slot assignments and the same drive promptly dropped out disabled again...

What am I looking for in the diagnostics that shows why it's dropping? I'm frustrated because this drive is a drive that previously was a parity drive for about six months without issue using cables that had another drive hooked up to them for about six months without issue (I changed the position of the drive in my case is all).

Thanks for any pointers!

[EDIT] In the meantime, I've shrunk the array and removed the drive since it was empty anyway. [/EDIT]

Edited July 21, 2025Jul 21 by SickPup404
add comment

Post new diags.

47 minutes ago, SickPup404 said:

Well, apparently I spoke too soon....

Yeah, S@$§! happens (often) :-(

But as Jorge said: post new diagnostics WITH that drive.

If it is out the array now, make it a pool device and fill it up a bit.

Sorry about that - forgot them. Attached now.

Note that the problem drive (s/n ZL2KV4R4) is currently out of the array and shows disabled in unassigned drives. Parity recalc is running...

nasbox-u1-diagnostics-20250721-1035.zip

Disk dropped offline during spin up, possibly a power/connection issue, or it has issues with spin up, possibly in combination with the controller, since it has been happening with some Seagate drives and LSI HBAs. You can try connecting to the onboard SATA and retest.

Thanks, I will wait for parity recalc to finish before I try that.

While I wait for the parity recalc to complete, I got thinking and looking around.

• The 16TB drive with the issue is a Dell branded Exos X16 (ST16000NM005G)

• I have another 16TB drive that’s fine on the LSI HBA. It’s an Exos X18 (normal Seagate, ST16000NM000J)

• The Dell drive used to be on my mobo SATA ports since I run my parity drives off there and not the HBA, so that’s why I didn’t have issues with it previously.

• They have different firmware IDs, and the Dell drive has a message that it’s not in the smartctl database.

Interesting differences between the X16 Dell and the X18 Seagate…

Also, where in the diagnostics did you see where it dropped out during spin up?

Thanks!

Jul 20 21:06:40 NASBox-U1 emhttpd: read SMART /dev/sdp

Jul 20 21:06:40 NASBox-U1 kernel: sd 1:0:9:0: [sdp] Synchronizing SCSI cache

Jul 20 21:06:40 NASBox-U1 kernel: sd 1:0:9:0: [sdp] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK

Jul 20 21:06:40 NASBox-U1 kernel: mpt2sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x5001e677bbc4fff6)

Jul 20 21:06:40 NASBox-U1 kernel: mpt2sas_cm0: removing handle(0x0013), sas_addr(0x5001e677bbc4fff6)

Jul 20 21:06:40 NASBox-U1 kernel: mpt2sas_cm0: enclosure logical id(0x5001e677bbc4ffff), slot(22)

Jul 20 21:06:41 NASBox-U1 kernel: mpt2sas_cm0: handle(0x13) sas_address(0x5001e677bbc4fff6) port_type(0x1)

Jul 20 21:06:42 NASBox-U1 kernel: scsi 1:0:11:0: Direct-Access ATA ST16000NM005G-2K EAL6 PQ: 0 ANSI: 6

Jul 20 21:06:42 NASBox-U1 kernel: scsi 1:0:11:0: SATA: handle(0x0013), sas_addr(0x5001e677bbc4fff6), phy(22), device_name(0x0000000000000000)

Jul 20 21:06:42 NASBox-U1 kernel: scsi 1:0:11:0: enclosure logical id (0x5001e677bbc4ffff), slot(22)

Jul 20 21:06:42 NASBox-U1 kernel: scsi 1:0:11:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)

Jul 20 21:06:42 NASBox-U1 kernel: scsi 1:0:11:0: qdepth(32), tagged(1), scsi_level(7), cmd_que(1)

Jul 20 21:06:42 NASBox-U1 kernel: sd 1:0:11:0: Power-on or device reset occurred

Jul 20 21:06:42 NASBox-U1 kernel: sd 1:0:11:0: Attached scsi generic sg15 type 0

Jul 20 21:06:42 NASBox-U1 kernel: end_device-1:0:11: add: handle(0x0013), sas_addr(0x5001e677bbc4fff6)

Jul 20 21:06:42 NASBox-U1 kernel: sd 1:0:11:0: [sdq] 31251759104 512-byte logical blocks: (16.0 TB/14.6 TiB)

Jul 20 21:06:42 NASBox-U1 kernel: sd 1:0:11:0: [sdq] 4096-byte physical blocks

Jul 20 21:06:42 NASBox-U1 kernel: sd 1:0:11:0: [sdq] Write Protect is off

Jul 20 21:06:42 NASBox-U1 kernel: sd 1:0:11:0: [sdq] Mode Sense: 7f 00 10 08

Jul 20 21:06:42 NASBox-U1 kernel: sd 1:0:11:0: [sdq] Write cache: enabled, read cache: enabled, supports DPO and FUA

Jul 20 21:06:42 NASBox-U1 kernel: sdq: sdq1

Jul 20 21:06:42 NASBox-U1 kernel: sd 1:0:11:0: [sdq] Attached SCSI disk

Jul 20 21:06:43 NASBox-U1 unassigned.devices: Disk with ID 'ST16000NM005G-2KH133_ZL2KV4R4 (dev2)' is not set to auto mount.

Read SMART line gets logged when a disk spins up, and the disk immediately drops offline and reconnects with a different ID (sdq)