JorgeB

Looks like the partition is missing or not valid, post the output of: fdisk -l /dev/sdd and blkid

Yes, you just need one LSI with a single cable.

If you are using macvlan switch to ipvlan (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)).

It already comes with stock Unraid v6.11.x

That suggests some compatibility issue with your hardware, most likely the board, other users had success after updating (or downgrading if using latest) the BIOS.

LSI 9200-8e or 9300-8e or similar, with a QSFP to SFF-8088 cable for the former and QSFP to SFF-8644 cable for the latter, but like mentioned cannot say the current controller is the problem, just that an LSI usually works better.

Yes, but would should still keep backups of anything important, any type of RAID adds redundancy, but it's not a backup.

Yes, those have been known to cause some issues in the past, and the driver is likely not as stable and widely used as the LSI driver.

You can thank @NDDanhe had the same problem and remembered changing that file, I would never think of looking at the go file for that, also keep in mind that if something storage related stops working in the future after an Unraid update you might need to do the same.

After the parity copy completes you must start the array to begin the rebuild, without changing anything else, or will need to start over.

Copy 60-persistent-storage.rules from the newer release and modify that file again, that should work, problem is likely because you are using a modified file from an older release.

Firefox is known to sometimes cause this stale GUI issue, using another browser after it happens won't work, you need to reboot first.

First set the SATA controller to AHCI, it's set to IDE, then try again.

Did you start the array to begin the rebuild after the copy finished?

Lots of errors with the controller, though cannot say the controller is the problem, do you have an LSI HBA you could try with?

Check if the docker image or appdata are using it, those are best moved to a cache device, if one exists.

Server load is extremely high, reboot then monitor it so see if you can find the service causing that if it happens again. Also a good idea to disable the mover log so it won't spam the log.

Disk5

It's logged as a disk problem, run an extended SMART test.

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

Try using ddrescue on it.

This suggests a problem with the NVMe device: Oct 23 11:02:46 BTV kernel: blk_update_request: critical medium error, dev nvme0n1, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 And the SMART report confirms it: === START OF SMART DATA SECTION === SMART overall-health self-assessment test result: FAILED! - available spare has fallen below threshold - media has been placed in read only mode You need to replace it.

Do a new config without them and sync parity.

Yes, this is normal, you should schedule the trim inside the VM OS, or run it manually when needed.

Yes: Oct 9 05:00:31 Helios kernel: FAT-fs (sda1): error, fat_get_cluster: invalid start cluster (i_pos 0, start e22d2585) Oct 9 05:00:31 Helios kernel: FAT-fs (sda1): Filesystem has been set read-only Oct 9 05:00:31 Helios kernel: FAT-fs (sda1): error, fat_get_cluster: invalid start cluster (i_pos 0, start e22d2585) Oct 9 05:00:31 Helios kernel: FAT-fs (sda1): error, fat_get_cluster: invalid start cluster (i_pos 0, start c1dc2174) ### [PREVIOUS LINE REPEATED 1 TIMES] ### Oct 9 05:00:31 Helios kernel: FAT-fs (sda1): error, fat_get_cluster: invalid start cluster (i_pos 0, start bbb5ad69) Run chkdsk on the flash drive.