trurl

Remove these plugins and don't reinstall them ca.cleanup.appdata.plg - 2024.11.28 (Deprecated) (Up to date) NerdTools.plg - 2024.02.17 (Unknown to Community Applications)Remove these plugins for now and see what happens gpustat.plg - 2025.11.23 (Up to date) nvidia-driver.plg - 2026.03.19 (Up to date) radeontop.plg - 2023.02.22 (Up to date)

Then post new diagnostics after restarting the array in normal (not maintenance) mode.

Your docker/VM related shares need some rework, we can discuss that after everything is working normally again.

Are you sure it said it was checking parity instead of rebuilding? I see write errors for disk6 where it tried to writeback to the disconnected disk, but don't see any write errors for disk5 that would have disabled it. Maybe it didn't try to writeback to disk5 since only 1 parity was valid. Or maybe the disk5 writeback wasn't logged since log space filled up. All disks are mounted, including the disabled/emulated disks. Dual parity can emulate 2 disks, but it seemed likely that only 1 parity disk would still be valid. Maybe since the disks had lots of free space enough of the rebuild completed that it could emulate both. And all disks including the disabled/emulated disks have files in user shares. Why do you think anything is missing? Don't do anything to that original parity disk you replaced. Might still be useful if the replacement rebuild wasn't complete.

And no way rebuild could finish that quickly. I doubt new parity can be trusted at this point. Hopefully nothing really wrong with any disk and we can just New Config.

Probably nothing wrong with the original parity disk. UDMA CRC ERRORS are connection problems not disk problems. And you may have disturbed connections to other disks. Attach Diagnostics ZIP to your NEXT post in this thread.

If you edited Minimum Free for cache or for that share, you might try restarting the array to see if it will apply the new settings.

Click the ... in the upper right corner of your post and you should be able to edit, hide, delete, etc. Some people like to edit their posts to delete their diagnostics, for example. Worth noting, though, that if you edit one of your posts, it won't show up as unread to anyone that already read the original post. Sometimes when asked for diagnostics, a user will edit the original post in the thread to attach the diagnostics. But anyone who had already read that post, and may be waiting for diagnostics so they could help, wouldn't know there was anything new in the thread so might not ever visit it again.

Can you boot something besides Unraid? memtest86 for example?

CPU cooling?

What user share are you writing to?

Does it crash if you disable Docker and boot in SAFE mode?

Attach Diagnostics ZIP to your NEXT post in this thread.

Attach Diagnostics ZIP to your NEXT post in this thread.

Looks like your flash drive is read-only. Put it in your PC and checkdisk. Or reformat and restore from your flash backup.

Everyone makes mistakes

Without a valid license you can't start the server. All features are available for valid licenses, only license restrictions are the number of drives for each license level. You have to enable VM Manager in Settings before you can setup any VMs. Don't know what might be happening with Tailscale. Have you tried removing your server at Tailscale Admin and adding it again?

If you notice, itimpi is a moderator and community expert. He certainly understand how flash is used.

When we are trying to see what happened leading up to the server becoming unresponsive, we usually don't need a very big file. 1MB is probably plenty, and maybe only keep 1. You can do more if you want, it won't be using a lot of your storage capacity. Please zip before posting though. It is text and will compress very well.

Nobody in this thread said it did happen. If they had I would have corrected them. Any changes you make in the webUI (your configuration) are written to flash at that time so they can be reapplied at boot. And sometimes people will mirror syslog to flash (Syslog Server) but I usually try to work with them to get it setup to log to a user share instead.

And enable syslog rotation so the files don't get too large. It's OK to leave Syslog Server enabled if it isn't writing to flash, you can just delete the logs manually after a while.

OK, that looks good for syslog server. You might consider turning off Mirror to flash now since it will be saving to your Photos share. Next time you have the "disconnect", you can get the syslog from your Photos share, zip it, and post it.

Attach Diagnostics ZIP to your NEXT post in this thread.

Post a new screenshot of your Syslog Server settings.