trurl

Contact support 

https://docs.unraid.net/unraid-os/manual/changing-the-flash-device/#what-to-do-if-you-have-no-backup-and-do-not-know-your-disk-assignments

All of your webUI settings are in the config folder on flash, including the user share settings.
 
But without any data, the shares won't actually exist.
 
You could create an empty top level folder named for the share on an assigned disk. That would be an empty user share and it would have the settings from the corresponding config/shares/*.cfg file.
 
Or you could just create the user shares in the webUI, and copy their settings from your flash backup.

Simple as that, except no need to set slot to no device. Just select the new device in that slot.
 
I prefer to reserve the verb "add" for situations where you are actually adding a disk to a new slot that didn't already have a disk assigned. Parity2, for example, in your case, but could be used when talking about a new data slot. What you are doing with the data disk is "replace".

You only need the config folder from your flash backup. It has all of your configuration (all settings made in the webUI), including your license and your disk assignments.

https://docs.unraid.net/unraid-os/manual/storage-management/#backing-up-the-pool-to-the-array

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.
 

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?