JorgeB

Unless all your data is not important they should be replaced, don't forget that Unraid requires all other disks to be OK to rebuild a failed disk.

Unlikely that was the problem, unless there were also filesystem corruption besides the main problem, main problem is this: This is what Unraid uses to detect the filesystem when set to auto, since it can't detect it won't try to mount, blkid not showing correct output means something is wrong there, but you're not the first with this and as long as the filesystem is manually set it shouldn't cause any other issues, but you must remember that if in the future you do a new config you'll need to set this again.

Basically of you have to rule out any of these:

No NIC being detect, either it's disable in the BIOS or it's not working, check BIOS or use add-on NIC.

Can't see how that is possible, number of devices his checked before array start, it won't start with more devices than the license allows, likely some disk(s) had dropped offline, so they din't count.

Yes, Docker service should be disable, mover should also move them to the array for cache=yes, we'd need diags with mover logging enable to see the problem it it doesn't work.

You'll likely need to force it.

Boot Unraid, run two consecutive correcting parity checks and post new diags.

Yes.

Flash drive dropped offline: Aug 29 10:20:12 Abazuu kernel: usb 2-5: USB disconnect, device number 2 Aug 29 10:20:12 Abazuu kernel: xhci_hcd 0000:00:14.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state. Aug 29 10:20:12 Abazuu kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00 cmd_age=0s Aug 29 10:20:12 Abazuu kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 07 9f b9 00 00 1f 00 Aug 29 10:20:12 Abazuu kernel: blk_update_request: I/O error, dev sda, sector 499641 op 0x0:(READ) flags 0x80700 phys_seg 31 prio class 0 Aug 29 10:20:12 Abazuu kernel: blk_update_request: I/O error, dev sda, sector 499642 op 0x0:(READ) flags 0x80000 phys_seg 30 prio class 0 Aug 29 10:20:12 Abazuu kernel: blk_update_request: I/O error, dev sda, sector 499641 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Try a different USB port, ideally USB 2.0.

If you're starting over that's all you need.

On the main GUI page click on each disk and change fs from auto to XFS, start array, disks should now mount.

You have a plus license with 13 devices connected, it won't allow you to start the array unless you upgrade to Pro, note that if the array is started with 12 or less devices it will allow you to connect more and it will work until the next time you need to start the array again.

Enable syslog mirror to flash then post that after a crash.

It's a known issue with some upgrades, you need to re-enable user shares: Settings -> Global share settings

First need to fix this: Aug 25 21:21:13 Tower kernel: md: disk2 read error, sector=54793824 Aug 25 21:21:13 Tower kernel: md: disk2 read error, sector=54793832 Aug 25 21:21:13 Tower kernel: md: disk2 read error, sector=54793840 Aug 25 21:21:13 Tower kernel: md: disk2 read error, sector=54793848 Disk appears to be failing, extended SMART test will confirm.

One full disk write (not read) is usually enough to get rid of pending sectors, but they could or not comeback again soon.

If you just need the license from the current flash you only need the key file from the config folder, they redo the flash with v6 and restore the key.

Please post the diagnostics to check if a driver is being loaded: Tools -> Diagnostics (if booting in GUI mode) or just type "diagnostics" in the console.

Looks like under certain circumstances, e.g., if a new share is created, and then minimum free space is set, it doesn't take until next array start, and this happens with Krusader or MC, so you might want to try that also.

Please try doing the same thing with Midnight Commander (mc on the console), that will confirm if there's an issue with Krusader or some other thing. I did repeat the test I did yesterday with v6.10, since before I did it with 6.9.2, and the first time I did it with Krusader it did go well beyond the minimum free space set, curiously a 2nd try after rebooting worked as expected, so there might be something there.

See if the flash boots on another computer to confirm where the problem is.

That's a known limitation with pools, see here for better pool monitoring.

Posting them might help see what the problem is.