trurl

https://docs.unraid.net/unraid-os/manual/troubleshooting/#bzimage-checksum-errorfailure-reading-flash-drive

Good plan.
 
Some try to make this too complicated instead of just using parity for its intended purpose. 

SMART Extended Self-test Log Version: 1 (1 sectors) Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed: read failure 70% 4527 13602456 replace

disklocation-master.plg - 2024.03.06 (Update available: 2024.03.06c)  

I don't know if Unassigned Devices will let you mount that single nvme without starting the array. Probably older version of UD didn't but maybe later version will,
 
Any linux should be able to mount it.
 
If you know which disks are parity you can just New Config and assign disks in whatever order and rebuild parity. Be careful with the parity slot assignments as mentioned.

You can check this yourself in Settings - Management Access - Unraid Connect

Replace. 
 
The disk firmware has tested it and says it is bad

Are you sure it didn't get moved into another share?
 
Why do you have so many (45) shares? Have you been creating folders at the top level of disks? Top level folders on pools and array are automatically user shares.
 
Why do you have 325G docker.img? Default 20G is often more than enough, maybe a little more if you have a lot of containers. The usual cause of filling docker.img is an application writing to a path that isn't mapped. Making it larger is not the fix for this. Usage shouldn't be growing.
 
Why are your docker and VM related files on the array? Ideally, these would all be on fast pool such as cache, so Dockers/VMs will perform better, and so array disks can spin down since these files are always open.

https://docs.unraid.net/unraid-os/manual/tools/#new-config

Looks like your boot flash drive has gone read-only.
 
Do you have a current backup of the boot flash?

You have btrfs csum errors on sdc, which is probably the reason for corruption.
 
And a very good reason to do memtest.
 
Do memtest before doing anything else.
 
You don't even want to attempt to run any computer unless memory is working perfectly. Everything goes through RAM, the OS and other executable code, your data, everything. The CPU can't do anything with anything until it is loaded into RAM.
 

Nothing in logs since reboot.
 
To rebuild the disk to itself:
Stop array Unassign disk Start array with disk unassigned Stop array Reassign disk Start array to begin rebuild If it offers to format anything, DON'T

https://docs.unraid.net/unraid-os/manual/storage-management/#changing-a-file-system-type

If you don't have any configuration you want to keep, all you need is the license .key file in the config folder, or at least keeping that .key file associated with that flash drive in some way. The bz files are included in every version install.

If you can make the to-be parity drive empty with all of its data elsewhere, then you can just New Config with all of the disks as you want them to be assigned, rebuild parity on the new parity (formerly data) disk, and format the new data (formerly parity) disk so it is ready for access.

Looks like Minimum Free on that share is larger than the free space on any of your array disks.

Tools-New Permissions

You still have a (probably self-induced) network problem, possibly with Unraid or possibly with your router.
 
Delete config/network.cfg on the flash drive so Unraid will use default settings, which includes DHCP to make it get its settings from the router.

Looks like you originally created this as a 2 device pool with the Acer SSD. Since they are not the same size you would have gotten a mirror with only the capacity of the smaller.
 
Have you tried removing the pool and doing that all over with only the nvme?

Your data disk should be fine and is probably even mountable if Unraid knew what filesystem it was. If you stop the array, can you click on the drive and set its filesystem to XFS?
 
 
What else besides the data on that disk do you want to keep?

Which explains why Mover can't work. It can't make any changes to cache, which is required when you move files off cache.
 
btrfs seems a little fragile when you fill it up.

Looks like this controller
01:00.0 Serial Attached SCSI controller [0107]: Broadcom / LSI SAS3224 PCI-Express Fusion-MPT SAS-3 [1000:00c4] (rev 01) Subsystem: Broadcom / LSI SAS9305-24i [1000:31a0] Kernel driver in use: mpt3sas Kernel modules: mpt3sas Maybe try reseating it.
 
Is it overheating?

Reformat your flash drive then recreate it from your backup. If you have changed any disk assignments since the backup was taken, edit config/disk.cfg to disable autostart so you can check your assignments before starting the array.

All attached storage devices when the array is started except the boot flash drive are counted. You can attach additional unassigned Devices after starting the array.