trurl

Are you saying that it doesn't crash in SAFE mode?

https://wiki.unraid.net/UnRAID_6/Storage_Management#Drive_shows_as_unmountable

Mar 8 15:33:17 Tower kernel: mdcmd (9): import 8 Mar 8 15:33:17 Tower kernel: md: import_slot: 8 empty Mar 8 15:33:17 Tower kernel: mdcmd (10): import 9 Mar 8 15:33:17 Tower kernel: md: import_slot: 9 missing Why did disk9 go missing when you were getting ready to rebuild disk8? Could also be a problem with the disk. You should monitor SMART attribute 1 and 200 on WD RED disks. Also noticed that disk did not have an extended SMART test.

If the nvme was disk1, then adding parity and letting it build will allow you to replace disk1 with a spinner and let it rebuild then nvme will be free and you can use it as cache and add other spinners to the array as needed. The parity array does not do raid5 or 6, see here for an idea of how Unraid differs from traditional RAID: https://wiki.unraid.net/Overview

Are you booting UEFI?

That's considerably faster than I would expect for writes to the parity array and makes me wonder if you aren't misinterpreting something. See here for an explanation of why writes to an array with parity cannot happen at the speed of "a spinning disk":

Preferably with the array started Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread.

Yet another example of

Prefer should be OK unless you fill up cache. Probably the only thing that could overflow to the array in that case would be appdata since system already exists on cache. The most likely cause of system winding up on the array is having the docker service enabled when there isn't a working cache drive in the system.

Having 2 Unraid flash drives at the same time is asking for trouble and is the cause of all your problems. The config folder on flash has everything you need to start with a new install and get your configuration back. Figure out which flash drive has the correct config folder and make a copy of it. The license is also on flash in the config folder. But, each flash has its own license and won't work with the license of another flash. Make a new install on the correct flash drive, copy the config folder, copy the correct license for that flash to that config

Probably better to just delete and recreate docker.img Settings - Docker, disable then delete docker.img on that same page. Enable will recreate it on cache as specified. Then you can reinstall your containers exactly as they were with the Previous Apps feature on the Apps page.

Go to Settings - Docker and delete docker.img. Enable will recreate it in accordance with the settings on that page, so it will get created on cache where it belongs. Then your containers can all be reinstalled exactly as they were using the Previous Apps feature on the Apps page.

Looks hardware related, perhaps dynamix system fan plugin. Try removing that.

Mover can't move open files. You have to disable the Docker service in Settings to get that moved.

If booting UEFI and GUI don't work together for you, try changing one or the other.

Possibly unrelated but your appdata and system shares have files on the array. You should clean that up. What do you get from the command line with this? ls -lah /mnt/disk23/system

Possibly unrelated but your system share has files on the array. You should clean that up. What do you get from the command line with this? ls -lah /mnt/disk2/system

I didn't see any indication in your diagnostics (perhaps they had not manifested since reboot), but the symptoms suggest a problem writing to flash. Are you booting from USB2? (recommended)

That was for a completely different situation and purpose. You have learned some things that can be done during this thread, but not why or when you should do them. Please ask for advice.

Can you post a link to what you think needs updating? Since Unraid has already determined the disk is unmountable, there is no way to mount it to replay the log. You have to use -L to continue without that. Also, there was no point in doing this: That was for a completely different situation and purpose.

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

Always

What do you get from the command line with this? ls -lah /mnt/cache/appdata

Is 6.9 the only version you have ever tried?

Do you have any VMs?