trurl

Start a new thread in General Support with your Diagnostics. I help people with this all the time.

Since that was a modular PSU, are you sure you were using the cables that came with the PSU? There is no standard pinout for modular PSUs and using cables that were not included with the PSU has fried many drives.

If your backups are on you PC, over the network would be simplest. If your backups are on external drives, Unassigned Devices plugin is another approach.

What I've noticed examining some diagnostics is xfs img is named docker-xfs.img. So maybe both exist as separate files.

Looks like we have narrowed the problem down to the download pool.

Note that the user0 is not a typo. I really meant it. That is not the command you ran.

Have you done New Permissions on the data share yet?

Use a computer with multiple SATA ports. You would have to shuck your external drives to get to the internal drives inside them. Lots of builds in this subforum: https://forums.unraid.net/forum/35-unraid-compulsive-design/

Overclocking a file server doesn't really make much sense anyway.

Not much point in speculating until after memtest

Doesn't look like you ever did this

What are you using NerdTools for?

Don't use USB connections for assigned disks.

Should do that. How long does it run before crashing?

If you take a file that transfers successfully, can you then delete it from the server, and successfully transfer it again?

Bad disk

Can you try from another computer?

What do you get from command line with this? ls -lah /mnt/user

So do you mean it doesn't matter which subfolder of the media share you try?

Are you trying to write to a user share, or to a subfolder of a user share?

The go file is on flash in the config folder and it is definitely used by Unraid.

Correct. Be sure to only run it on that share.

USB not recommend for assigned disks for many reasons. And SSDs in the parity array can only be written at parity speed, and cannot be trimmed. The proper place for that nvme is in a pool outside the array. It would be best to reconsider your hardware.

In fact, the containers have no access to /var/log since it isn't mapped. That's sort of the whole point of dockers, they can't get to anything you don't specify in the mappings. You can examine the logs at the mapped host path

The shares in question are set to only include disk3. Also, they are set to exclude disks 1,2. You should never set both include and exclude. And there is never any good reason to think you might want to do that. Include means only the listed disks, so it already excludes all other disks. Exclude means except for the listed disks, so it already includes any disks not listed. Delete the .cfg file for each of those shares in config/shares on the flash drive, restart the array, and configure those shares again.