February 25, 20197 yr 15 minutes ago, dmacias said: 47 minutes ago, tjb_altf4 said: Only issue I've come across is a few plugins that have been updated recently won't allow install on 6.6.7 plugin: installed Unraid version is too low, require at least version 6.7.0-rc1 Not a biggie, but something to be aware of. Which plugins? The maximum in the plg file might have been set to 6.6.6 Only Dynamix System Stats now, other one updated for me just then.
February 25, 20197 yr The latest version of Dynamix System Stats only runs on Unraid 6.7. For Unraid 6.6 you'll keep using the existing installed version.
February 26, 20197 yr I think he meant that the latest version of Dynamix Syststats does not run on this release version of unRaid 6.7.0 - it requires a RC1 or higher. I observed the same behavior. Edited February 26, 20197 yr by Kir
February 26, 20197 yr 43 minutes ago, Kir said: I think he meant that the latest version of Dynamix Syststats does not run on this release version of unRaid 6.7.0 - it requires a RC1 or higher. I observed the same behavior. This is a thread for version 6.6.7, so still not 6.7 and not compatible with the latest System stats version.
February 27, 20197 yr upgrade from 6.6.6 to 6.6.7 successful and smooth. thank you. no docker/vm/network issues.
February 28, 20197 yr I upgraded to 6.6.7 2 days ago. Today I got an alert that system notifications were disabled and I seemingly can not enable them. Is this associated with the upgrade, or do I have something else going on?
February 28, 20197 yr 11 minutes ago, patm95 said: I upgraded to 6.6.7 2 days ago. Today I got an alert that system notifications were disabled and I seemingly can not enable them. Is this associated with the upgrade, or do I have something else going on? That sounds like either flash drive problems, or it dropped offline
February 28, 20197 yr 47 minutes ago, Squid said: That sounds like either flash drive problems, or it dropped offline Thank you for the heads up. I will get an extra flash drive ordered and ready. Then reboot and see what happens. I still have the original flash drive and it's 8 years old.
February 28, 20197 yr Upgraded from 6.6.6 to 6.6.7, no problems with Dockers (Plex, Sickbeard) or VMs (LAMP, Win10, Win7) Uptime for 6.6.6: 67 days, 9 hours, 30 minutes Uptime for 6.6.7: 15 hours, 4 minutes and counting
February 28, 20197 yr On 2/26/2019 at 10:56 PM, Kir said: Now I feel stupid for misreading the version number 😏 I upgraded, then started questioning my sanity...
February 28, 20197 yr 16 minutes ago, PSYCHOPATHiO said: I upgraded, then started questioning my sanity... Hmmm, yep, forum name checks out. 😀
February 28, 20197 yr I upgraded yesterday from 6.6.6 to 6.6.7 and now all my docker containers are not showing IP addresses in the docker console and non of my containers are network stable. SAB will open after a while and display the interface. Hitting F5 once will cause the interface to go away with a messgae in the browser stating that the page cannot be reached. Hitting F5 again might / might not display the interface again and it cycles thought this. This happens on all containers.
March 1, 20197 yr Before you do anything else, get rid of CA resource Monitor. Long deprecated. Who knows if it's even compatible.
March 1, 20197 yr I upgraded yesterday from 6.6.6 to 6.6.7 and now all my docker containers are not showing IP addresses in the docker console and non of my containers are network stable. SAB will open after a while and display the interface. Hitting F5 once will cause the interface to go away with a messgae in the browser stating that the page cannot be reached. Hitting F5 again might / might not display the interface again and it cycles thought this. This happens on all containers.This happened on all my custom networked (br0) dockers. I edited to network on each one to bridge and let it reconfigure itself and changed it back to custom (br0) and they are back up and running.
March 3, 20197 yr Hey folks - I ran into a problem with this upgrade. I have custom network's configured for Docker (MACVLAN). After the update, all of my containers started just fine. But one of them started to have some networking issues and I started investigating. I tried changing a setting in that container and when I saved the container, it disappeared! Looking deeper, I notice now that under the networking options for the container config any network which was using a MACVLAN network (e.g. br0.55) now shows Network Type of "None" and the custom networks for MACVLAN aren't an option in the container config. If I apply any changes to a container now, it functionally disappears. I'm going to try rolling back to 6.6.6 to see if it solves the issue... but thought you should know. Anyone else seeing this?
March 3, 20197 yr Confirmed. Rolling back to 6.6.6 solved this issue. Container configs can now select the Custom networks for Network Type.
March 3, 20197 yr Doing this update caused my nginx to not start, however when I tired to manually start it I noticed the dhparams file was empty so once I regenerated it all was fine.
March 4, 20197 yr Upgraded from 6.6.6 to 6.6.7 and now have a boot loop at the blue menu screen, it counts backwards down from 5 then just resets it's self and counts down again. I tried each of the menu options and only memtest86 works.
March 4, 20197 yr Author 1 hour ago, ThatDude said: pgraded from 6.6.6 to 6.6.7 and now have a boot loop at the blue menu screen, it counts backwards down from 5 then just resets it's self and counts down again. I tried each of the menu options and only memtest86 works. Reformat the flash device and reinstall your flash backup zip.
March 4, 20197 yr Author On 3/2/2019 at 6:42 PM, user457453944 said: Doing this update caused my nginx to not start, however when I tired to manually start it I noticed the dhparams file was empty so once I regenerated it all was fine. Sounds like a flash corruption problem.
March 5, 20197 yr Please try the following after upgrading to 6.6.7 rm /var/lib/docker/network/files/local-kv.db /etc/rc.d/rc.docker restart The above resets the Docker network definitions.
March 7, 20197 yr I cannot tell you why or how, but after downgrading from 6.6.7 -> 6.6.6 four days ago, and then upgrading again today from 6.6.6 -> 6.6.7 the issue I reported before (i.e. Custom Network Types not appearing in Docker Container configuration) appears to have gone away. 🤷♂️
March 13, 20197 yr Since the upgrade, I can no longer access unraid via web GUI, nor via any other machine.
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.