JorgeB

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.

2026-06-27T17:42:28-07:00 ZimaCube kernel: usb 2-1.3: USB disconnect, device number 3 2026-06-27T17:42:28-07:00 ZimaCube kernel: device offline error, dev sda, sector 11716424 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 2026-06-27T17:42:28-07:00 ZimaCube kernel: I/O error, dev loop0, sector 115904 op 0x0:(READ) flags 0x800 phys_seg 4 prio class 2 2026-06-27T17:42:28-07:00 ZimaCube kernel: SQUASHFS error: Failed to read block 0x38936dd: -5 2026-06-27T17:42:28-07:00 ZimaCube kernel: device offline error, dev sda, sector 11697752 op 0x0:(READ) flags 0x80700 phys_seg 10 prio class 2 2026-06-27T17:42:28-07:00 ZimaCube kernel: device offline error, dev sda, sector 11697752 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 2026-06-27T17:42:28-07:00 ZimaCube kernel: device offline error, dev sda, sector 11715032 op 0x0:(READ) flags 0x80700 phys_seg 12 prio class 2 2026-06-27T17:42:28-07:00 ZimaCube kernel: device offline error, dev sda, sector 11715032 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 2026-06-27T17:42:28-07:00 ZimaCube kernel: device offline error, dev sda, sector 12924448 op 0x0:(READ) flags 0x80700 phys_seg 10 prio class 2 Flash drive is dropping offline, you can first try using a different USB port and/or recreating the flash drive, if the issue persists, replace it.

Post a photo/video showing at what point it reboots, you can also try booting with a different flash drive using a stock install; no key needed, just to see if that boots.

Try booting with a different flash drive using a stock install, no key needed, just to see if it boots.

That's an MBR partition, only using 2TB for an 8TB disk. With the array stopped type: sgdisk -o -a 8 -n 1:32K:0 /dev/sde Then reboot and see if that disk no longer shows as wrong, if it doesn't start the array and post new diags.

There have been other reports with those NICs and performance issues in one direction, see if this helps: https://forums.unraid.net/topic/123594-poor-ssd-cache-read-speed-25gbe/

It will never wotk with those 3 partitions; you can try Rufus if the USB tool is not working (though not sure why that is) Get the Unraid zip from https://docs.unraid.net/unraid-os/download_list/ - Open Rufus and change "Boot selection" to "Freedos" - Set the "Volume label" to UNRAID - set filesystem to FAT32 - click START - once done, unpack the Unraid ZIP to the flash drive If you are booting UEFI nothing else you need to do, if you are booting legacy/CSM, run the make_bootable.bat as administrator first.

Test must be made between a client and the server, a loop test is not really worth anything.

Why not just relogin using the correct account?

Run an iperf test between both PCs to confirm the LAN is all working at 2.5GbE

It will never work with the flash drive being detected without partitions; that should not happen if it was recreated with the USB tool. Post the output from fdisk -l /dev/sdn

Not sure what you mean; the link was up for many hours.

If you are logged in with a different account, you cannot use the same trial; you must use the same account that was used to create the trial.

That suggests a problem with the flash drive, enable the syslog server and set it to save to a share, then post that after it happens again.