JorgeB

Not sure, it may be better just in case.

Persistent syslog doesn't come with the diags, you will need to get it from wherever it was being saved to.

If it works fine again after downgrading it, it could be a kernel regression, the other LSI controller is apparently working fine, problem is just the 9305-16e. It may be worth looking for a firmware update; we can also see if any other users report similar issues.

Note that those values are what devices themselves report for each power state, and may be an approximation; I've seen older NVMes reporting similar values, but possibly Optane may require a little more power in standby.

Try removing the plugin, rebooting, then reinstalling.

Memtest is a good place to start. Also, does the parity check typically find errors or not?

May 28 08:57:00 BrunnhildeTwo smbd[140213]: build_sam_account: smbpasswd database is corrupt! username htmini with uid 1002 is not in unix passwd database! May 28 08:57:00 BrunnhildeTwo smbd[140213]: [2026/05/28 08:57:00.933085, 0] ../../source3/smbd/msdfs.c:107(parse_dfs_path_strict) smbpasswd also is corrupt, try deleting that from the flash drive/internal boot. Note that I think it will reset the passwords for all SMB users.

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

Does a different flash drive using a stock install boot? No key needed.

If you move the storage over, you can boot from the flash drive and recreate the boot pool with the current config, just make sure you save or have access to the X15 key before doing it, and then reinstall it.

BTW this bug has been fixed some time ago, make sure you update.

If you imported the pool manually, the GUI will always show it as unmountable. Export the pool manually with zpool export zpool Then restart the array, and if it doesn't mount, post the diagnostics.

No issues logged that I can see suggesting more a hardware issue. Make sure this has been taken care of: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-819173

Btrfs detected data corruption on the pool; start by running memtest.

May 22 15:38:26 NASA php-fpm[6475]: [WARNING] [pool www] child 1479914 exited on signal 9 (SIGKILL) after 24.830572 seconds from start May 22 15:38:52 NASA php-fpm[6475]: [WARNING] [pool www] child 1479943 exited on signal 9 (SIGKILL) after 19.976203 seconds from start May 22 15:39:20 NASA php-fpm[6475]: [WARNING] [pool www] child 1479957 exited on signal 9 (SIGKILL) after 23.828378 seconds from start May 22 15:39:43 NASA php-fpm[6475]: [WARNING] [pool www] child 1479983 exited on signal 9 (SIGKILL) after 19.020641 seconds from start In my experience, these errors can be the result of the server being close to exhausting the memory, GUI can become extremely slow, like 1 minute to open the dashboard, try limiting the memory for VMs/docker services, or adding a little more RAM. It could also be one or more containers hogging the CPU, try pinning only some cores to them, and leave cores 0/1 available for Unraid. Also, recommend trying a couple of other things, go to Settings - Global share settings and set the Number of fuse File Descriptors to the max, and enable this: https://docs.unraid.net/unraid-os/release-notes/7.0.0/#excessive-flash-drive-activity-slows-the-system-down

That should not be possible, don't see how a Stater key could work with more than 6 devices, unless they were first connected with the array started.

Disk2 is online, the one being resilvered is disk3 NAME STATE READ WRITE CKSUM zfs DEGRADED 0 0 0 raidz2-0 DEGRADED 0 0 0 sda1 ONLINE 0 0 0 sdc1 ONLINE 0 0 0 replacing-2 DEGRADED 0 0 0 5034914802460489689 FAULTED 0 0 0 was /dev/sdc1 sdb1 ONLINE 0 0 0 (resilvering) sde1 ONLINE 0 0 0 sdd1 ONLINE 0 0 0 sdh1 ONLINE 0 0 0 sdg1 ONLINE 0 0 0 sdf1 ONLINE 0 0 0

Errors are not logged as a disk error but are soon after spin up, so you may want to retest with spin down disabled to see if it's related.

Yes. Boot from a flash drive and rerun the wizard. Yes, with a paid license, trial licenses cannot be transferred.

Most likely because it was fixed by the kernel update without LT knowing, since it only happened with a few UPS models.

That's bizarre, but yeah, if you can test a new VM with a new vdisk.

You have a Starter key, so you can only have a max of 6 attached devices; there are currently 10. That's why you cannot start the array.

The pool is raid1 only now, you should be able to replace a device.

You can assign one if you like, this is normal, it will always show that slot with the array stopped. You can also assign an extra disk there, you can reduce the slot count to 11 to not show that.

Since this thread is still active, and to avoid confusion, please start a new one and post the diagnostics.