JorgeB

No NVMe devices are being detect by Unraid (Linux), so likely a hardware issue.

Depends on the allocation mode and split level set for the share(s), default is high water and split always.

No need to run a balance, GUI replacement already does that. Usually yes, but always good to have backups in case something goes wrong. As you wish, it doesn't make any difference.

If it's not under lspci it's not being detected, so it's not a driver problem, it's hardware, also pretty sure those NIC are already supported by Unraid.

Don't known why it's reporting pending sectors, did it report they changed to 0 after? The disk does appear to be failing, though.

Please post diags, if the NIC isn' t even detected it will never work in Unraid.

Correct.

It should be.

There are csrf_token errors spamming the log due to having multiple browser windows on the GUI, that makes it more difficult to search the log for errors, but as far as I saw everything looks good.

Still macvlan call traces, are those dockers using custom IP?

Cache filesystem is corrupt, you need to backup and reformat, then recreate docker image.

It's not. You should do it using the GUI, first replace one of the devices with the new one, then remove the other device.

Yep. That's good news

You can, and add [SOLVED] to it.

Look for a lost+found folder, any partial/lost files should be there, all the rest should be OK. Unraid is not a backup, you need to have a backup of anything irreplaceable.

Now start the array in normal mode, not maintenance.

No, parity needs to be there since the disk is being emulated.

Don't format, post the output of xfs_repair -vL

Yes, that's expected, you have to run xfs_repair, using the GUI or the console.

You can do it now, since not much point rebuilding if the filesystem can't be fixed, to use the GUI check you need to set the filesystem on that disk to xfs, you can do that by clicking on it.

Like mentioned disk1 will likely be unmountable because you mounted the array without all devices, you can cancel the rebuild and run xfs_repair to see if it's fixable, if yes then start rebuilding again: https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui

No, but you can use a spare disk if available, same size or larger.

Try the latest v6.9-beta, if still not supported best bet is to ask LT to include the driver, they usually do on the next release, assuming one is available that works with current kernel.

Like already mentioned you should respect the max officially supported RAM speeds by AMD depending on the config, at least while you're troubleshooting to rule that out, several cases in the forum of instability and even data corruption with Ryzen and overclocked RAM.

Follow the instructions below carefully and ask if there's any doubt. -Tools -> New Config -> Retain current configuration: All -> Apply -Check all assignments and assign any missing disk(s) if needed, like old disk1 -Important - After checking the assignments leave the browser on that page, the "Main" page. -Open an SSH session/use the console and type (don't copy/paste directly from the forum, as sometimes it can insert extra characters): mdcmd set invalidslot 1 29 -Back on the GUI and without refreshing the page, just start the array, do not check the "parity is already valid" box (GUI will still show that data on parity disk(s) will be overwritten, this is normal as it doesn't account for the invalid slot command, but they won't be as long as the procedure was correctly done), disk1 will start rebuilding, disk should mount immediately (probably not in this case) but if it's unmountable don't format, wait for the rebuild to finish (or cancel it) and then run a filesystem check.