December 5, 2025Dec 5 Hi, folks. For the first time in a very long time, I am experiencing some issues with my unRAID setup. I have been a user for a number of years, but rarely interact with the system, these days, other than backing up appdata and monitoring basic array health reports. The server is primarily used for VPN access via Pritunl in a Docker container, and it has worked flawlessly for years. As a result of this reliability, I find that my familiarity with the system has diminished significantly. I'm hoping that the community will be patient with my incompetence, and help me navigate my way through the issue. A bit of background: I rebooted the system yesterday, and failed to notice that the Docker Service failed to start. I checked on the system, and found the message "! Docker Service failed to start". Looking at the Docket settings, I see the following warnings:I am in the process of reading through many threads on the subject, but I'm concerned about blundering around trying to fix things that I don't fully understand, and hoping that someone might be able to provide a little (very) basic guidance. Any assistance would be greatly appreciated as I try to get back up to speed!Diagnostics attached.Thanks,Shaun gisl-cr1-ur1-diagnostics-20251205-0942.zip
December 5, 2025Dec 5 Author Thanks, JorgeB. I have checked the filesystem, and corruption was found. Here are the results:Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ALERT: The filesystem has valuable metadata changes in a log which is being ignored because the -n option was used. Expect spurious inconsistencies which may be resolved by first mounting the filesystem to replay the log. - scan filesystem freespace and inode maps... sb_ifree 149, counted 148 - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 imap claims a free inode 1005 is in use, would correct imap and clear inode - agno = 1 - agno = 2 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 2 - agno = 1 - agno = 3 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... Maximum metadata LSN (132:1644261) is ahead of log (132:1632164). Would format log to cycle 135. No modify flag set, skipping filesystem flush and exiting.I will attempt the fix.Thanks again,Shaun
December 5, 2025Dec 5 Author A dirty log was indicated. Tried to mount the file system again to replay the log, but this was unsuccessful. So I cleared the log (as the guide recommended), ran the check again, followed by the fix. Corruption was repaired, Disk1 successfully mounted, and the Pritunl Docker has started. All great news, and thanks again for your help! Unfortunately, Pritunl won't accept connections, so something was potentially corrupted. I will dig in to that next!Thanks,Shaun
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.