JorgeB

This should not make any difference, but you can try starting the array in maintenance mode and importing using the pool using the md device, if it still fails, and most likely will, post the output from tail -n 50 /proc/spl/kstat/zfs/dbgmsg

This error is not on the diagnostics posted, but it means the Unraid driver is crashing, and it's almost always a hardware issue, most often bad RAM or a bad CPU.

If you can log in from the CLI using a monitor/monitor see if you can get the diags, if not, post a photo of where the boot stops.

This is an actual issue that should be resolved; post new diags after you get some errors.

Looks good, rebuild finished without any errors or warnings logged.

If it doesn't post, it won't be in the logs, it's also not an Unraid issue.

You can, but it's not required to run the SMART test.

There's nothing relevant logged; it suggests more of a hardware issue, Post the diagnostics mostly to see the hardware used.

You can still run

There are constant Samba errors being logged: Jun 29 18:35:46 hightower nmbd[2503]: [2026/06/29 18:35:46.378765, 0] ../../source3/lib/interface.c:716(load_interfaces) Jun 29 18:35:46 hightower nmbd[2503]: WARNING: no network interfaces found Jun 29 18:35:46 hightower nmbd[2503]: [2026/06/29 18:35:46.629355, 0] ../../source3/lib/interface.c:716(load_interfaces) Jun 29 18:35:46 hightower nmbd[2503]: WARNING: no network interfaces found Don't see what's causing them. My first suggestion would be to rename /config/network.cfg on the flash drive to network.bak then reboot, this will revert the LAN settings to default DHCP, then post new diags after array start.

If it's not FUSE there's some other bottleneck or issue; it's certainly not an Unraid limitation. I can get line speed with 25GbE (writing to an exclusive share, though FUSE it drops to around 1.8GB/s with this server)

It's logged as a disk error, but SMART looks OK. Recommend running another parity check or an extended SMART test.

Best bet is to look for the support thread for that container

So it's not the same issue; I recommend starting your own thread to avoid confusion. Also, please post there the basic hardware you are using.

You can disable the Docker and/or VM services for a few hours or a day, and check the SMART stats before and after, it that stops the increase, then start enabling them one by one and retest.

There are issues logged with multiple devices. Are there any power splitters in use?

That looks like a BIOS issue, the problem happens before loading Unraid.

That suggests a compatibility issue between the hardware and the newer kernel. My suggestion is to remain on 7.2 for now and retest once a release is available with a newer kernel

Is it better if you write to a disk (or exclusive) share?

Syslog is not downloading for me, please try attaching it again. Also, post the diagnostics mostly to see the hardware.

Yep

Looks good, and the data on disk 7 should all be fine, since it was a partition issue, not the filesystem. If you are happy with the emulated disk9 contents, the main thing left is to rebuild it.

And did it mount correctly after array start?

The partition still isn't correct; do this, first, wipe the existing one (this won't wipe the data) wipefs -a /dev/sde then again sgdisk -o -a 8 -n 1:32K:0 /dev/sde You shouldn't see any errors this time; if so, reboot again.

If a different flash drive using a stock install still does' boot, it suggests some incompatibility between the newer kernel and the hardware. My suggestion would be to remain on 7.2.x for now and retest once a release with a newer kernel is out.