April 9, 20251 yr Hi Unraid users Last night I decided to download a few large ISO's, filling my cache drive up and I noticed my Overseerr container became unresponsive and was not letting me log in. When I checked around the server dashboard, thats when I noticed the cache was full and I decided to execute the mover function. What I probably should have done is stop the array docker itself and then execute move... But bad on me, I didnt.... So now, I am unable to start any docker that was stopped during that time. Fix common problems is showing it as "docker image is either full or corrupted". I have not restarted the server, or stopped the docker image. I do have CA app data running and backing up, most recent was on 4/7. Before I go any further and cause more mayhem on my Unraid box, should I restore from backup, or is there other steps I should take. Below is the main error I see: Quote 2025-04-08 21:35:38,551 DEBG 'overseerr' stdout output: 2025-04-09T04:35:38.550Z [[31merror[39m]: Error: SQLITE_IOERR: disk I/O error --> in Database#run('PRAGMA journal_mode = WAL', [Function (anonymous)]) at /usr/lib/overseerr/node_modules/typeorm/driver/sqlite/SqliteDriver.js:109:36 at new Promise (<anonymous>) at run (/usr/lib/overseerr/node_modules/typeorm/driver/sqlite/SqliteDriver.js:108:20) at SqliteDriver.createDatabaseConnection (/usr/lib/overseerr/node_modules/typeorm/driver/sqlite/SqliteDriver.js:122:19) at async SqliteDriver.connect (/usr/lib/overseerr/node_modules/typeorm/driver/sqlite-abstract/AbstractSqliteDriver.js:170:35) at async DataSource.initialize (/usr/lib/overseerr/node_modules/typeorm/data-source/DataSource.js:129:9) at async /usr/lib/overseerr/dist/index.js:72:26 2025-04-08 21:35:38,563 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23192747774352 for <Subprocess at 23192747571056 with name overseerr in state STARTING> (stdout)> 2025-04-08 21:35:38,563 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23192747772816 for <Subprocess at 23192747571056 with name overseerr in state STARTING> (stderr)> 2025-04-08 21:35:38,563 WARN exited: overseerr (exit status 1; not expected) 2025-04-08 21:35:38,563 DEBG received SIGCHLD indicating a child quit 2025-04-08 21:35:39,564 INFO gave up: overseerr entered FATAL state, too many start retries too quickly 2025-04-08 21:38:20,724 WARN received SIGTERM indicating exit request Logs attached. docker.log syslog.txt
April 9, 20251 yr Community Expert Solution Docker image is unable to handle writes: Apr 8 21:48:28 GarciaUnraid kernel: I/O error, dev loop2, sector 3508128 op 0x1:(WRITE) flags 0x100000 phys_seg 2 prio class 2 Apr 8 21:48:28 GarciaUnraid kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 1, rd 0, flush 0, corrupt 0, gen 0 Apr 8 21:48:29 GarciaUnraid kernel: loop: Write error at byte offset 1791381504, length 4096. This typically means it's full, make sure you don't have an incorrect mapping in a container, but recreating it should fix it for now: 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 9, 20251 yr Author 50 minutes ago, JorgeB said: Docker image is unable to handle writes: Apr 8 21:48:28 GarciaUnraid kernel: I/O error, dev loop2, sector 3508128 op 0x1:(WRITE) flags 0x100000 phys_seg 2 prio class 2 Apr 8 21:48:28 GarciaUnraid kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 1, rd 0, flush 0, corrupt 0, gen 0 Apr 8 21:48:29 GarciaUnraid kernel: loop: Write error at byte offset 1791381504, length 4096. This typically means it's full, make sure you don't have an incorrect mapping in a container, but recreating it should fix it for now: 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 So this only occurred last night, after I executed the mover function. For future reference, should I not do that while the array is live? Also, I run the CA Backup plugin/app, am I able to recreate/restore from that? Edit: Also, my cache drive is no longer full since I had executed the mover function. Edited April 9, 20251 yr by DirtyDan
April 9, 20251 yr Community Expert Then post new Diagnostics and we can make recommendations to prevent this going forward.
April 9, 20251 yr Author Awesome, will do. Should have some time to work on this later today. I appreciate the help.
April 10, 20251 yr Author All done. Everything seems to be back in order. Edit: I may have spoke to soon, seems I am still having the same error as before. Here are the new diagnostics garciaunraid-diagnostics-20250409-1712.zip Edited April 10, 20251 yr by DirtyDan
April 10, 20251 yr Community Expert Do you mean an error trying to start containers? Is it all containers?
April 10, 20251 yr Author @trurl i saw a couple containers showing that they werent started, then tried to start which gave the same error as before. Didnt notice I had selected two different containers from different repo's, they were using the same port allocation and that was causing the error. Seems things are working normally. you mentioned on recommendations to make sure this doesn't happen again. What do I need to be looking at?
April 10, 20251 yr Community Expert Your appdata has files on both pools, but is configured to only write new files to cacheapps. Don't know if you want some of appdata to stay on cache or not, but only those files already there will be there and they won't be moved. Unraid V7 can move files between pools, but nothing can move open files so you have to disable Docker in Settings to work on that. https://docs.unraid.net/unraid-os/manual/shares/user-shares/#primary-and-secondary-storage-unraid-612 https://docs.unraid.net/unraid-os/release-notes/7.0.0/#share-secondary-storage-may-be-assigned-to-a-pool Neither of your pools have Minimum Free set https://docs.unraid.net/unraid-os/manual/storage-management/#minimum-free-space-for-a-pool You might also want to examine Minimum Free settings for each of your shares. Looks like they are probably using a calculated "default". https://docs.unraid.net/unraid-os/manual/shares/user-shares/#minimum-free-space
April 13, 20251 yr Author @trurl I would like to have my data stored in the safest, but fastest possible spot. Which I would feel like would be the the cacheapps pool, since it has 2 drives in that array for redundancy plus those are NVME drives. Is that best use case? I will work on getting Minimum Free Set for pools and shares.
April 13, 20251 yr Community Expert 17 minutes ago, DirtyDan said: the cacheapps pool, since it has 2 drives in that array for redundancy plus those are NVME drives. That's what I would do. Might be good to put system share on cacheapps for the same reasons. Nothing can move open files, so you have to go to Settings - Docker and disable Docker before you can work with those shares. Set appdata and system shares to Primary:cacheapps; Secondary:cache; Mover action:cache->cacheapps. Then run mover, wait for it to complete, and post new diagnostics.
April 17, 20251 yr Author New Diagnostics here: I am now realizing 500gb is barely enough for my app storage. How can I go about increasing the size? Would I just follow the instructions in the thread below? Or follow instructions here? garciaunraid-diagnostics-20250417-0648.zip
April 17, 20251 yr Community Expert 43 minutes ago, DirtyDan said: 500gb is barely enough for my app storage Looks like that is mostly appdata. Any idea why appdata is so large? My appdata is less than 20G, but I don't have nearly as many containers as some. Still, 500G appdata seems like more than should be needed. Many containers have a /config path or equivalent that is mapped to /mnt/user/appdata, but other data produced by the container should be mapped to other host paths.
April 17, 20251 yr Author Looking into the appdata share, I’ve been storing my app data backups there. I’ll probably move it to the array and/or reduce to 1(maybe 2) backups kept.
April 17, 20251 yr Community Expert 2 hours ago, DirtyDan said: my app data backups there. I’ll probably move it to the array Certainly no reason to have that on fast storage.
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.