Outlaws

Appreciate the reassurance Thomas, from another Thomas My upgrade went smooth, no issues. Sorry to hear you ran in to that issue Mellow - my AMD 5600G didn't run in to the same, don't believe I have that chipset anywhere. I hope you get it fixed soon!

Haha I've been procrastinating the upgrade from 6.11.5 - any notable concerns jumping from 6.11.x straight to 6.12.6?

Thanks for the response, Parm. I ended up nuking the docker.img and re-installing all the containers. Thankfully the CommunityAppdata backup helped retain all of the /appdata information.

Hello Unraid wizards, I come to you again in my time of need 🙏 I will spare you my full recollection of the morning, but please ask for any other details that would be helpful. I'm happy to troubleshoot. After a file share server, I primarily use Unraid for a number of Docker containers. I was looking in to improved monitoring for my home network, and had recently been playing with SNMP tools at work, so I was looking to enable something similar here. I found and installed some containers which looked relevant, and got those setup. When I was doing that however, I've somehow managed to break the ability to edit any other docker images I had previously? Here is a list of things leading up to the issue, and troubleshooting steps I've tried so far. Scenario: 1. Searched for & found relevant docker apps for system/network monitoring 2. Installed MariaDB & LibreNMS --- these are the only two docker containers that I am still able to edit. They are also the only 2 working on the 'eth0' interface, PiHole and Unifi controller are currently no longer starting 3. Oh cool, this works. Began adding switches and other devices to LibreNMS, wanted to add Unraid as a server to be monitored... 4. Found that the Unraid host was unable to communicate with the Docker containers, and this was by design. 5. Stopped all running docker containers 6. Under Settings -> Docker, changed 'Host access to custom networks' to 'Enabled' 7. Went back to Docker tab, and uh oh. Some won't start, but all except the two newest are now unable to be configured. Troubleshooting: 1. Step 1 in a bad change, undo the change. After observing the error trying to start PiHole, I disabled the containers and reverted to Host access to custom networks: Disabled. 2. Restarted the Docker service, but no change. Found that the containers are able to start except for PiHole and Unifi, but none except the two newest (MariaDB and LibreNMS) are able to be configured via the Unraid GUI. 3. Disabled containers, stopped array, reloaded server. Logged back in, but found that the issue persists. Issue: 1. No longer able to configure/edit any Docker containers, except 2 newest 2. Unable to launch 2x existing Docker containers Thankfully, I also have a CommunityAppData backup from this morning before everything, if restoring that would be helpful. As for why the two specific containers will not start at all, it seems to be mad about something with the network? When I look at the Unraid console, 'docker network instpect eth0' shows me definitions for the interface, mariadb, librenms.... but not the .7 or .8 values I expect for Pihole and Unifi. I can also generate: root@Unii:~# docker -D start unifi-controller Error response from daemon: network d824fbdfadf6027a607225e63a07f64cd92447e9197bb92efd287652167a91a5 not found Error: failed to start containers: unifi-controller But the same command is unable to recognize anything for the Pihole container, which should be pihole-dot-doh or pihole-dot-doh-2. I can get the Pihole container to appear in other outputs though, such as '~# docker image inspect devzwf/pihole-dot-doh' and '~# docker image history devzwf/pihole-dot-doh'. Before I continue down the rabbit hole myself: I've included some relevant diagnostic files and images of the issue, can share anything else that is needed. Please let me know what the best next steps would be? maybe something like 'recreate docker.img' from here? https://docs.unraid.net/unraid-os/manual/troubleshooting/#How_do_I_recreate_docker.img.3F update: 1. moved this to the correct subforum 2. Deleting and recreating docker.img kinda works, but I'd love to avoid it. I can re-install exactly one container. I don't remember all the docker container configs, can't easily view them now, and trying to 'restore docker apps' like mentioned in the link below doesn't work - it only shows the past few weeks of installed apps, not everything. So..... can anyone help me avoid fully rebuilding my docker setup Unraid_Diag_Files.7z

Understood. You are correct, when I open that FSCK0000 file in Notepad++, it's the ident.cfg file and then scrambled/unrendered text beneath it. I've gone thru the /config/shares for the August and today backups, and none of the files differ. The newer backups have this 'private.cfg' file which is not in the August version, though. I've attached the FSCK file, if it's of any use to you. With this chain of events, would you have any other recommendations? Replace the usb drive, or not necessarily? Thanks again FSCK0000.REC

Gotcha, thanks for the quick response. I do not see any *.fsck files in any of the 3 backup folders, no. However, in the pre and post update files from today, I do see one FSCK0000.REC file - is that the smoking gun? I am looking thru the other .cfg files in that folder, so far I'm not finding any anomalies between the August & latest backups in the domain.cfg, smart-one.cfg, share.cfg, network-rules.cfg (one change, but likely due to the Oct hardware upgrade), network.cfg, disk.cfg, or flash.cfg. I do see differences in docker.cfg, but this may be my initial troubleshooting before the original post. Are there other diagnostics or .cfg files you would recommend checking?

Hey trurl, thanks for the follow up. Comparing the three backup files I have, (Aug, this morning pre-upgrade, post upgrade), I do see where the August/oldest ident.cfg has my original configuration edits. I will copy the lines that are different below. Oldest/original: # Generated settings: NAME="Unii" timeZone="America/New_York" COMMENT="Unii" enableFruit="no" ---------------- what is this line? USE_NETBIOS="yes" NTP_SERVER1="<private>" NTP_SERVER2="time1.google.com" NTP_SERVER3="time3.google.com" NTP_SERVER4="time4.google.com" USE_SSH="yes" START_PAGE="Dashboard" This morning, post hardware upgrade but pre-6.11.5: # Generated settings: NAME="Tower" timeZone="America/Los_Angeles" COMMENT="" enableFruit="yes" USE_NETBIOS="no" USE_NTP="no" NTP_SERVER1="" NTP_SERVER2="" NTP_SERVER3="" NTP_SERVER4="" USE_SSH="no" START_PAGE="Main" This is more concerning, for sure. What other files would you recommend reviewing on the flash backups that I have retained?

Okay, fun times. I still wasn't able to find much difference between the 3 backup files other than the latest one missing the templates. I've run a few health checks on the USB drive using Hard Disk Sentinel, and it doesn't seem to be spitting out errors or bad blocks there. I've restored the template files from the last flash backup containing them, and seem to be back in business. I have some spare USB drives ready for if that main one fails, just in case. Thanks again for your help - I've seen you both in countless other forum posts, and I can't imagine the amount of headaches you've saved throughout the years. Have a great holiday 😃

That is a very good, and concerning, question that I'm thinking about. I didn't take any actions this morning except what was described, and also using the 'Cleanup Appdata' plugin to remove four unused appdata files, but don't recall if that was before or after running the flash backup where I am still seeing the templates. Also, I had noticed that the hostname of the server reset to 'Tower'. This was prior to the move to 6.11.5 as well, and shows the backup as 'tower-flash-backup'. (I performed a hardware update, new chassis/cpu cooler, on the server in October, which is the last time it was restarted - so this name change may have occurred then, however I only noticed the change this morning after creating the flash backup.) I created another flash backup now, and am comparing the 6.11.5 backup vs the 6.10.3 version this morning, and an older 6.10.3 backup from August. The only differences I see (aside from the bz system files) are in that config/plugins/dockerMan/templates-user folder. I can share these 3 if you would be interested in looking at them as well, or any other diag files.

root@Unii:/boot/config/plugins/dockerMan/templates-user# ls -la total 24 drwx------ 2 root root 8192 Dec 22 02:46 ./ drwx------ 4 root root 8192 Dec 22 02:28 ../ -rw------- 1 root root 3219 Dec 22 02:46 my-Duplicacy.xml root@Unii:/boot/config/plugins/dockerMan/templates-user# Found it - appears to be empty lol. So what would be the best way to restore at this point, copy the template files from the flash backup to here and reload the server?

I really appreciate the quick responses! So I did take a backup of the flash before the upgrade, and there I can see plenty of files in the /dockerMan/templates-user/ folder. I'm having a harder time navigating to that folder on the running server - what would that file path be? I typically use Krusader to interact with the unraid files - is the /config/plugins/dockerMan/templates-user on the USB drive accessible from here, or do I need to navigate there another way?

Hey all, Why can't upgrades go smoothly? They normally have - just not this time I tried to update my server from 6.10.3 to 6.11.5 this morning, and have found a strange issue. Update Assistant showed no concerns before the update, and I was able to access the machine again after a reboot. I experienced a separate issue when trying to start the array, where it showed 'array stopped - stale configuration'. Googling showed this to be a Firefox/webui issue, and I was able to start the array after restarting the server and using Edge to sign in. Now, the issue is that the update appears to have removed/corrupted the install of all my Docker images? The images still show on the page and are able to start, and appear to be working as expected - but I am not able to edit/update any of the Docker containers. So I am not able to modify the settings on any docker container that appears, and selecting 'Force Update' on the container gives a more ominous error: "Configuration not found. Was this container created using this plugin?" Cool. So I install a random new Docker image from the store, and that one works as expected - I can select the container name and modify settings. So somehow, it seems to no longer recognize the previously installed containers. I have restarted the server again, toggled the Docker service off/on, and can still view the folders in /appdata - but still the issue persists. Any recommendations on how to correct this, or just drop back to 6.10? Images below for reference https://imgur.com/a/DcyozwK