Currently my cache drive is online, but the Fix Common Problems says it is not able to be written. I looked into the diagnostics in the docker log and I'm thinking the drive itself is having some issues. Last event that happened was the scsi data cable fell off the drive. I was able to physically fix this and put the drive back in and the system rebuilt the drive. A few days later is when my docker apps stopped working. I have tried rebuilding the docker image as well as increasing the docker size. I've rebooted a couple times.

I'm attaching the diagnostics zip file. I just did a new one. I'm basing my thinking it is a bad drive off the docker.log from a previous diagnostic log from 2 days prior.

tower-diagnostics-20250926-2027.zip

The cache disk dropped offline, replace its cables and post new diagnostics after the array start.

Here is the new diagnostics after I replaced the power cable and connected it to an extra sata connector. The docker is now running, which is better than it was the last couple of reboots. Going to feel silly if it is just the power cable.

tower-diagnostics-20250927-1646.zip

Edited September 27, 2025Sep 27 by tnorman

I'm looking thru the diagnostics. I'm not sure what the rsyslogd errors mean. But the 

BTRFS error (device sdc1): incorrect extent count for 44044386304; counted 3960, expected 3959

is on the cache drive which has me wondering what to do. I've been reading about it and it sounds like there might be a problem I need to chase down.

Scrub the pool for the GUI and post the results, also, probably best to recreate the Docker image.

I scrubbed the pool. I then went to recreate the docker. I stopped the docker and deleted the disk image. When I tried to restart the docker, it wouldn't start. So I rebooted.

After reboot, the docker started but the apps wouldn't run... I was surprised to even see the apps in the docker since I had deleted the disk image and the apps needed to be reinstalled.

The internet went down during the reboot, which shouldn't change anything but since it was back up I thought I'd just reboot it again to see if it fixes itself.

Then the computer didn't reboot like normal. It looked like it got stuck on the display of the logo for the motherboard during reboot. I'm wondering why, but it wasn't giving any details. Turned the machine off and on and seemed to boot back up ok this time... except the cache drive was started in read only mode and the docker image is not able to be written to.

I've got to get some rest for work. I'm just going to look into it more tomorrow. Going to leave it running overnight. Maybe elves will come out and fix it for me. :)

Here is the most recent diagnostics. The cache drive continues to be in read only. I've tried moving to a different wire, but it doesn't seem to make a difference.

The only indication that there is a problem is if I look at the Cache drive's pool device status information under Corruption Errors. It shows 1. The Main tab doesn't show a problem. It seems to me if the cache drive is in read only mode the Main tab should have a notification on the cache drive indicating a problem.

I did a memtest for 24 hours. No errors over that time. It passed every time.

I'm scratching my head and not sure what to do.

tower-diagnostics-20250929-2142.zip

Pool still has filesystem issues:

BTRFS critical (device sdh1 state EA): unable to find ref byte nr 21364224000 parent 0 root 5 owner 25476311 offset 545701888 slot 17

Recommend backup, reformat, restore the data.

After a few days of issues, I finally seem to have my unraid server back in good condition. I had a few wrong turns and I learned that trusting what AI says can lead to major problems. Thankfully backups helped me when I fubared the server when a pool drive decided to disable itself.

None the less, the Cache drive has no been formatted and seems to be working fine.I'm recreating the apps i was using. I know I have a backup, but I figured I'd start fresh.

I've attached the diagnostic files. Please let me know if you seeing anything wrong.

tower-diagnostics-20251001-2313.zip

Not seeing fs issues so far, but my recommendation would still be to reformat it, or it can cause future issues.

I did reformat the cache drive. That's the one has been throwing the error. I've been thinking about changing it to an SSD. I even bought one expecting I would need to put a new drive in it. I think I'll keep an eye on it for now. I also want to buy a new power supply as I'm on the limits of the current one, but I think I want to wait a month or two before doing that. Right now I need to work on getting my apps back up and running, and maybe my vm I had on there.

1 hour ago, tnorman said:

getting my apps back up

Just in case you don't know

https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#reinstalling-docker-applications

I did not realize this. That may help me with a couple I have yet to setup. Thank you!