eybox

SOLVED. Removed all the notifications from within the Archive folder (since the creation of the server 8 years ago) and the notification Archive started working again. So as it appears, the following seems to be the Archived Notifications folder's limitations, as calculated by the system: "Total occupied space: 4.98 MB in 1 folder and 13,880 files" Cheers!

Hi, all! I've been running an unRAID server for around 8 years now. Currently on version 6.12.10. The issue I'm facing isn't anything that disturbing, but quite an odd little thing: The notifications that I'm getting normally on unRAID GUI are not being saved into the "ARCHIVED NOTIFICATIONS" section in unRAID Settings. But I do get them normally through the bell icon in the GUI. It's just that once I click "Acknowledge" or "Close all notifications". they seem to be gone forever. The curious part is, that this "ARCHIVED NOTIFICATIONS" section does contain a lot of previous notifications, just not recent ones. Not from a year or so ago till now. Have already searched the unRAID forums and Reddit for this a lot, but to no avail. That being said, here's some additional information, and do with it what you will: - Server run - ~8 years now - Earliest saved notification - from 2017 - Latest saved notification - 2nd of August 2023 - Flash drive - size 8GB, with 5.5GB free - Nothing stands out in the Dynamix Notification Settings page (attached) Please help me figure this out!

I can confirm, what you have confirmed - that this is exactly how it is currently working for me as well. I thought I was going insane with the constant crashes for several months now... Hopefully they get a fix out.

Finally bit the bullet, and did the same as you guys. Thanks! Tough luck, I guess.

In the same boat as you, my friend. Any resolution or help, anyone? I'm currently on: Unraid - 6.11.5 Radarr - 4.3.2.6857-ls163 by linuxserver.io

Hi, guys. Thanks to you @bonienl , @eschultz and @limetech for helping out. It finally seems to be working now. Upgraded and so far the initial couple of hours of testing are OK.

Thank you for this lead! I do have 4 NICs. And I use only one of them - eth0, with br0 attached to everything - Dockers and VMs. I tested eth1 a lot of time ago if it worked or not, but never used br1. What is the resolution to this? Removing everything eth1 and br1 related from network.cfg perhaps?

Here's everything we agreed upon on both 6.6.6 and 6.7.0. Hope this helps. Keeping fingers crossed, as I love Unraid and the latest UI change REGULAR-6.7.0-cortex-diagnostics-20190511-2334.zip SAFEMODE-6.7.0-cortex-diagnostics-20190511-2339.zip REGULAR-6.6.6-cortex-diagnostics-20190512-0203.zip SAFEMODE-6.6.6-cortex-diagnostics-20190512-0211.zip

Alas I already reverted back to 6.6.6 as I described in the original post. But this offers us an unique opportunity. Would you like me to do both of these: 1. Boot into SafeMode on 6.6.6, and get diagnostics zip 2. Upgrade again to 6.7.0. Then boot into SafeMode and get its diagnostics zip. This way you would be able to compare them both for differences?

First of all, please allow me to show my gratitude for the amazing work you and the people at limetech have done for all of us. As well as for you helping me right now. Cheers 🍺 Back to your question: - The router still didn't see the server as an active device on the network - Still couldn't ping the outside world from Tower. I do believe it's an in-OS change which triggered the network-related issues, at least that's what I deduced based on my troubleshooting. But I'm just not advanced enough to tackle these on my own 😢

In all the "Fail" cases, I meant that it kept on working improperly as described in the points above. Not that the OS failed to start. Sorry, my bad

Hi, team. I upgraded from 6.6.6 (stable) to 6.7.0 (stable). And it broke both the server and my heart. I guess this release starts off on the wrong foot for a lot of people. In Summary: - I'm having massive network-related and some PCI-related issues. - I need help. Diagnostics attached. Thank you in advance! In Full Detail: Been an extremely happy Unraid user for quite a while now. Never had any OS issues before, other than the occasional hiccups which I caused with my limited understanding of Linux. But nothing which a friendly chat here in the forums or a video from Ed wouldn't fix. This time is different though. Upon boot everything seemed fine - the Docker containers auto-started, everything was peachy at first glance. Alas as soon as I started clicking around I found out a lot of issues, namely: 1. The Apps tab (Community Plugins) - told me that it couldn't connect to download the latest list of apps, and according to it - there were DNS issues. Went to check the network settings - everything seemed fine. It had been fine up to 5 minutes ago before the upgrade, why wouldn't it be now? 2. A lot of Docker containers (most operating via regular bridge connection) didn't load in their respective Web UI's 3. The DelugeVPN Docker container - which as the name suggest utilizes VPN and Privoxy, told me it couldn't connect to its respective VPN server, as it couldn't resolve the name of the server... ****.privateinternetaccess.com. Hmm... so perhaps there was some DNS issue... 4. The Let'sEncrypt Docker container - couldn't pass on the necessary data and none of the nginx connections loaded properly. The plot thickened. 5. Decided to try the PING via the Web Terminal - it pinged through to the Router as well as other PCs on the network. But it didn't want to ping any hostnames like google.com for instance. 6. That's when I noticed that my router (Google WiFi mesh network) - didn't recognize the device as being live on the network at all. Apparently, I was able to connect to the Web GUI, so it did have the correct IP set up, but Docker and the Router seemed to think it's offline for whatever reason. The stuff which was working: 7. Finally, Unraid got the UI it deserved 8. The VMs worked normally for the most part - I say "for the most part", because the PCIe USB controller which I have in the system sort-of disappeared after the upgrade and the VMs didn't auto-start. At least they had a network connection and ran fine. 9. The PLEX Docker Container - couldn't connect locally, but at least the Remote connection worked, so my family wasn't going to be stranded media-less for that period of time. And that was sole because of that I've separated it on a separate IP address (different than the Tower one) via br0 bridge. What I tried (Troubleshooting steps I took) in resolving the networking situation: 10. Pinging from Tower (terminal) to the outside world - Still crap. 11. Connecting from the outside world to the Let's Encrypt / nginx / nextcloud - Still crap. 12. Connecting from the outside world to the Open VPN server running as a plugin - Still crap. 13. Running SpeedTest plugin to reach out to the outside world servers - Still crap. 14. Disabled Docker. Rebooted. - Still crap. 15. Disabled Libvirt. Rebooted. - Still crap. 16. Started Unraid in SafeMod - No plugins, everything else disabled (Docker, VMs, etc.). Couldn't be more barebones than this. Even the Array was stopped - Still crap. * And I did try to plug and unplug the network cable, as well as reboot all my network gear a couple of times along the tens of server reboots as well. That's when I decided it's time for a rollback. So now I'm back on 6.6.6 and everything is running as smoothly as ever again. Please help me. Diagnostics file attached. Thank you upfront! cortex-diagnostics-20190511-1238.zip