ChatNoir

There is a known issue with 6.11.1, did you look into that ? https://forums.unraid.net/topic/129257-6111-vpn-tunnel-failing/page/2/#comment-1182737 (not sure if it applies to your case, I don't use WG)

Nerdtools is not part of the base OS, you should look for support on the plugin in it's support page.

So, not the same issue as the OP. If you want to have someone look at you issue : diags from the OS version where you have the issue of course.

Set up a syslog server and post the file after the next crash.

Pretty sure that this is not part of stock Unraid. Probably a plugin ? You should ask for changes on that Dashboard section in the plugin support thread.

This makes no sense. An unclean shutdown is Unraid not being able to shut down properly and launching a parity check. If you want to close your forum account, that's something completely different.

Pools are not limited to RAID1. It defaults to RAID1, but once the Pool is built, you can balance it (in the GUI, no CLI required )to whatever BTRFS profile you can support with the material. In your case, probably RAID5/6 or RAID1c3/4 etc.

You should probably post new diagnostics.

People have crashes all the time. The fact that some people have a specific issue right now with 6.11 does not mean that your crashes have the same cause. Please attach your diagnostics in your next post and post your log from the syslog server after the next crash. That way, we can see if it's the same thing or not.

Yes

It is recommended to make a backup after every significant change but in that case it is even more important. If you use an old backup with a data disk as a parity drive, Unraid might accept that as valid (technically it would be), assign the data drive as parity and start the Array. Then, the data on that drive will be at risk.

If you plan to use the old parity drive as a data drive, I strongly suggest to make a new flash backup once it is done.

Could be that, could be even before that. Are you using a UPS ?

Probably was an issue with Ryzen and linux, adjusting c-states in BIOS and making sure that RAM speed is correct generally solve the problem if that's the root cause. You should probably start you own thread and attach your diagnostics.

https://wiki.unraid.net/Manual/Changing_The_Flash_Device It is recommended to keep a recent backup of your flashdrive. The simplest way is to use the plugin My Servers so the backup is always up to date.

I think that now you cannot run an extended SMART if spin down is active.

It is not guaranteed as faulty flashdrive do drop down, we see that on the forum regularly. As for a second flashdrive, you make live with the My Servers plugin or regular backups with CA Backup / Restore Appdata. However, it is not possible to have two flashdrives called UNRAID in the server. And that's required for Unraid to boot on a flashdrive.

Mover logging should only be used when trying for find an issue with mover. Otherwise, it will fill up the logs quickly.

Yes, the clearing should only affect the new drive.

AFAIK, a write does not automatically require to read all drives, it depends if turbo write is enabled or not. The default behavior is to read the content of the block on the drive, change it and update parity. In that case, if disk 1 dropped and you only access disk 2, it might not be detected immediately.

Didn't see much in the logs as they are just after a reboot. You should set up a syslog server and post the file after the next crash.

Do you now have a lost+found share ?

You should remplace all the bz* files on your flash drives with one pulled from the release you are using. You can get the files in the zip here : https://unraid.net/download

If the S3 plugin is not compatible with the new kernel on your system, you should ask on the plugin support thread.

I would guess that you cannot have twice the same type of licence on the same directory (/config) : Basic.key , Plus.key or Pro.key So the one being used should coincide with what is indicated on the top right of the WebUI : You can confirm with JorgeB's suggestion.