JorgeB

I don't think so, to rule out a FM issue, try using Mindnight COmmender (mc on the console).

If the NVMe device is dropping try this: On Main click on the flash drive, scroll down to "Syslinux Configuration", make sure it's set to "menu view" and add this to your default boot option, after "append initrd=/bzroot" nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off e.g.: append initrd=/bzroot nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off Reboot (or power cycle the server if just a reboot doesn't bring the device back) and then see if it makes a difference.

Stock Unraid can only spin down SATA drives, you can try the SAS spindown plugin, but not all SAS drives support spin down.

You can see here: https://forums.unraid.net/topic/102010-recommended-controllers-for-unraid/

Yes, already mentioned it above.

This would suggest a hardware problem, most often bad RAM, so I would recommend investigating this first. If you ahve enough space you can use the mover to empty an array drive, format it, then move on to the next one

Actual disk also has filesystem issues, you can try the recovery options here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-543490 Since the problem is the same, they could be used with the actual disk or the emulated one

appdata is set to use cache_nvme pool, but no such pool exists, should it exist?

Jun 20 13:11:02 Hector-2 kernel: hpsa 0000:0a:00.0: Controller lockup detected: 0xffff0000 after 30 Jun 20 13:11:02 Hector-2 kernel: hpsa 0000:0a:00.0: Telling controller to do a CHKPT Jun 20 13:11:02 Hector-2 kernel: hpsa 0000:0a:00.0: controller lockup detected: LUN:0000000000800001 CDB:01030000000000000000000000000000 Jun 20 13:11:02 Hector-2 kernel: hpsa 0000:0a:00.0: Controller lockup detected during reset wait Jun 20 13:11:02 Hector-2 kernel: hpsa 0000:0a:00.0: failed 28 commands in fail_all Problem with the controller. Make sure it's well seated and suficially cooled, you can also try a different PCIe slot if available. You can do that

You can always make a feature request: https://product.unraid.net/b/unraid-os-feature-requests

Possibly this

I assume via a single cable? That would mean SATA port multipliers, which were never recommended, but I suspected there may be some kernel regression where they don't work correctly with more recent ones, since other users have experienced issues with them after upgrading.

Don't see anything relevant logged. If you want to try donwgrading you just need to copy the current config from /boot/config to the flash drive and boot from there.

Looks OK

You must unmount before unpluging it.

RAM is overclocked, start here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-819173

Alwsys good to try other options, but IIRC TrueNAS is the same regarding this.

This is typically not needed, so it's not really a feature that someone has requested or is on LT's radar, you can create a feature reuqest here if you like: https://product.unraid.net/b/unraid-os-feature-requests

IIRC , Unraid will always repartition a pool device if the existing partition is not the default layout, you could create the parrion and format it ZFS outside the GUI, then just import the pool using the GUI, that would work.

Type reboot in the CLI, but if it doesn't reboot after 5 minutes you may need to force it.

Those are not the complete diagnsotics, but not seeing any obious issues on the syslog, post a screeshot showing the error you see.

Note as far as I know, only root has SSH access.

Do you see the same speed with the array started in maiantnce mode?

Jun 20 00:12:09 Tardis unassigned.devices: Mounting partition 'sdj1' at mountpoint '/mnt/disks/transport data'... This unassigned disk dropped offlione: Jun 20 11:33:51 Tardis kernel: sd 1:0:5:0: device_block, handle(0x000d) Jun 20 11:33:53 Tardis kernel: sd 1:0:5:0: device_unblock and setting to running, handle(0x000d) Jun 20 11:33:53 Tardis kernel: sd 1:0:5:0: [sdj] tag#5829 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=DRIVER_OK cmd_age=5s Jun 20 11:33:53 Tardis kernel: sd 1:0:5:0: [sdj] tag#5829 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 Jun 20 11:33:53 Tardis kernel: sd 1:0:5:0: [sdj] tag#5830 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=DRIVER_OK cmd_age=0s Jun 20 11:33:53 Tardis kernel: sd 1:0:5:0: [sdj] tag#5830 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 98 00 Jun 20 11:33:53 Tardis kernel: sd 1:0:5:0: [sdj] Synchronizing SCSI cache Jun 20 11:33:53 Tardis kernel: sd 1:0:5:0: [sdj] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK Jun 20 11:33:53 Tardis kernel: mpt2sas_cm1: mpt3sas_transport_port_remove: removed: sas_addr(0x4433221104000000) Jun 20 11:33:53 Tardis kernel: mpt2sas_cm1: removing handle(0x000d), sas_addr(0x4433221104000000)

Enable the syslog server and post that after the next crash.