trurl

Go to MAIN - Array Operation, START the array without checking the Maintenance mode box. Then go to Tools - Diagnostics, download, and post that complete downloaded zip file.

Try again. You didn't get those diagnostics with the array started in normal mode.

That may be, but you didn't post that download, you posted something different.

You are posting syslog. You posted diagnostics earlier in the thread. I want diagnostics. Start the array in normal (not maintenance) mode, go to Tools - Diagnostics, download, and attach the complete zip to your next post.

You posted diagnostics earlier in the thread, but the array was not started in normal mode.

Those are not the diagnostics

A lot more would have to be done to actually get it to save syslogs to another computer, including setting up a syslog server on the other computer. Just set Remote syslog server to localhost then the syslogs will be saved to the isos share on your Unraid server, then when we ask for them, you can get the sylogs from there, zip and post them. Not sure where you got those, did you have it mirrored to flash? What I really am asking for now is

There is help in the Unraid webUI. Many settings have help which you can toggle on/off by clicking on the label for the setting. You can also toggle on/off help for the whole webUI by clicking the help (?) button in the main bar.

Setup Syslog Server and post a screenshot of those settings. Start the array in normal (not maintenance mode) and post new diagnostics.

Start the array and post new diagnostics

Attach Diagnostics ZIP to your NEXT post in this thread.

You really should run memtest86 for several hours. If RAM has problems it will continue to create other problems.

Tailscale is also built-in. That is what I use for remote access these days. All computers on the same tailnet (such as your Unraid server) can be accessed. You can access other computers on the tailnet even if your Unraid server isn't running. I still use Wireguard on Unraid to route certain containers to a VPN Service.

Another link in case you haven't seen it: https://forums.unraid.net/topic/84226-wireguard-quickstart/

This is a little out-of-date (no Wireguard plugin required) but might be useful: https://unraid.net/blog/wireguard-on-unraid

Never do this

Even if the hardware supports hot swap, Unraid won't do anything with the new drive until you assign it, and you can't assign a drive without stopping the array. If you do hot swap, be careful to not disturb any other disks.

If you decide to New Config instead, parity is not valid because the disabled disk is out-of-sync.

Not entirely clear what happened, except for the fact that the drive was disabled because a write to it failed. This is the only thing that disables a disk because it is the only thing that makes it out-of-sync with parity. The failed write that disables the disk, and any subsequent write to that (now emulated) disk, updates parity so those writes can be recovered by rebuild. Sometimes if a read fails Unraid will try to write the calculated data back to the disk, and if that write fails the disk is disabled. But ultimately, a write failed so the disk was disabled. Emulated disk9 is mounted, and SMART for the Unassigned Device that was disk9 look OK. It hasn't had an extended test. Should be OK to rebuild on top if you get the problem that caused this sorted out.

You can always select a template from the Add Container page (ADD CONTAINER button at bottom of DOCKER page). The list of user templates comes from flash in config/plugins/dockerMan/templates-user

Parity has no file system. Just assign them and start the array to being parity build.

Tools -> New Config just like the other method except you do check the parity valid box.