Steviewunda

Thanks Jorge - I removed the Unraid flash drive, reverted to F54a, shutdown and replaced the Unraid drive, booted and everything appears normal. Thanks for your help 😉

The PC booted up eventually but the array is stopped with missing disks. Diagnostics attached tower-diagnostics-20261113-1958.zip

I just created more problems. I updated the BIOS to the latest, and now it won't boot at all. SATA drives 0, 1, 2, 3, and 6 are not being recognized. The boot sequence loops on "SATA link down..limiting speed to 1.5 Gbps" or something similar. I loaded the optimized defaults, but no go. The PC won't let me update the BIOS either - it only recognizes my Unraid flash drive now, not the other flash drive I used to update the bios. Any suggestions?

About the same in safe mode (with GUI)

It takes about 9 mins to boot from cold...5 mins 30 secs spent verifying boot/* checksums. I'll try safe mode.

I should mention that at one point I was unable to logon via the web interface until I removed Tailscale

Boot times have slowed down considerably, especially since installing Tailscale. I have since removed Tailscale but no change, Diagnostics included tower-diagnostics-20261111-1443.zip

I just did a reboot and was able to format and mount them 😉

I performed the balance, stopped the array, and removed one SSD drive (not physically). I was then unable to format and mount the disks

Thanks Jorge, but I'm unable to format and mount the disks - diags attached tower-diagnostics-20261023-2323.zip

Hi - I'm trying to reduce my pooled cache drives (500 GB SSD's) from 2 to 1, and use the 2nd drive for Tdarr. (I'm tired of having the cache fill up and crash my Dockers etc). But when I follow the unRaid instructions for removing a disk from the cache pool, I get this response when I try to re-enable the array - "Wrong Pool State cache - too many wrong or missing devices" . Diagnostics attached tower-diagnostics-20261023-2013.zip

Thanks JorgeB - everything appears to be good again (once I remembered to mount my unassigned disks on my node-only server)

I setup Tdarr server and node on Tower, and a node on Tower1. Initially I had the Movie and Temp shares setup as cache>array and the Mover setup to run hourly, but the cache pool was filling up, so I changed the Movie share to be array-only, and went to bed thinking I had solved the cache-filling problem. But I woke to find that the cache was full, and the Docker service had shut down. I have changed the Movie share back to cache>array and I'm running the Mover to reduce the cache-pool usage. The used space is dropping on the cache pool, but the Docker service is still "Failed to start". What should I do? Would a restart be appropriate? The diagnostics file is attached. tower-diagnostics-20261017-0451.zip

I seem to have resolved this by deleting the categories in SABNZB - I'll see how we go 😉

And here is the SABNZBD image