April 27, 20251 yr So I’ve been having this problem for a few weeks now and haven’t been able to figure out what I’ve done wrong. I’m sure it’s a me thing vs hardware. I get two errors in the fix common problems plugin. Unable to write to cache & unable to write to docker img. I realize this has happened because all of my docker containers get shut down when these errors happen. After a reboot everything is fine and works again for a little while. I’d really appreciate some guidance. Diag downloaded before touching anything after finding the errors again. edit: apparently this issue also corrupts my docker image so I have to delete it and reinstall all containers. Docker won’t start otherwise tairneanach-diagnostics-20250427-0948.zip Edited April 27, 20251 yr by Smithjo1696 New information
April 27, 20251 yr Community Expert btrfs csum errors are usually bad RAM memtest is on the boot menu
April 27, 20251 yr Author 22 minutes ago, trurl said: btrfs csum errors are usually bad RAM memtest is on the boot menu Running memtest now I’ll report back with results thanks for the fast response!
April 28, 20251 yr Community Expert Looks like one of the pool devices dropped offline in the past, reboot and post new diags after array start.
April 29, 20251 yr Author 18 hours ago, JorgeB said: Looks like one of the pool devices dropped offline in the past, reboot and post new diags after array start. Here’s the new diags. One of the pool devices dropped off? tairneanach-diagnostics-20250428-2236.zip
April 29, 20251 yr Community Expert Yes, this device: Apr 27 19:11:20 Tairneanach kernel: BTRFS info (device nvme1n1p1): bdev /dev/nvme1n1p1 errs: wr 34252462, rd 662642, flush 857703, corrupt 4363, gen 0 Scrub the pool and post the results.
April 29, 20251 yr Author 4 hours ago, JorgeB said: Yes, this device: Apr 27 19:11:20 Tairneanach kernel: BTRFS info (device nvme1n1p1): bdev /dev/nvme1n1p1 errs: wr 34252462, rd 662642, flush 857703, corrupt 4363, gen 0 Scrub the pool and post the results. I clicked scrub and it gave me this after about 30 seconds
April 29, 20251 yr Community Expert All errors were corrected, reset the stats, then recommend monitoring the pool in case it happens again. https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-700582
April 29, 20251 yr Author 33 minutes ago, JorgeB said: All errors were corrected, reset the stats, then recommend monitoring the pool in case it happens again. https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-700582 Docker said unable to start again today. tairneanach-diagnostics-20250429-1120.zip
April 29, 20251 yr Author 10 minutes ago, Smithjo1696 said: Docker said unable to start again today. tairneanach-diagnostics-20250429-1120.zip 379.16 kB · 0 downloads 7 minutes ago, trurl said: btrfs csum errors are usually bad RAM Wouldn’t memtest fail if it was bad RAM?
April 29, 20251 yr Community Expert Reboot to clean the log, then recreate the docker image, if it still fails after that, post new diags: https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file Then: https://docs.unraid.net/unraid-os/manual/docker-management/#re-installing-docker-applications Also see below if you have any custom docker networks: https://docs.unraid.net/unraid-os/manual/docker-management/#docker-custom-networks
April 30, 20251 yr Community Expert 18 hours ago, Smithjo1696 said: Wouldn’t memtest fail if it was bad RAM? Not necessarily. Memtest is only definitive if it fails.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.