Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

ilnahro

Members
  • Joined

  • Last visited

  1. Since the release of 7.1.0 earlier in the year, I had been holding off updating my Unraid install because every time I did I encountered a network issue with the eth0 interface. In fact, my NAS is currently experiencing the issue and the only way I can access it is either locally or through WiFi (neither of which is really a sustainable option). This seems to be affecting all versions post 7.0.1. Here is what happens from a user perspective: When I start the server, it can briefly (about 10-15 seconds) communicate with the network. It received pings and I am able to load the WebGUI of Unraid. However after this time elapses, the connection becomes unusable. Ping request from other devices on the network fail, I can no longer access the web interface and also any attempt to use the network from the server itself (with the local terminal or GUI) result in failure. What makes this stranger is that when I unplug the network cable and reconnect it, there is a brief (~2 second) window in which connectivity is restored. Ongoing pings will suddenly succeed and the login screen will load. Only for the network to freeze up again. While the network cable is plugged in, the Unraid machine also becomes unreachable on its WIFI interface. I have tried using an USB external Ethernet Adapter and that seems to work just fine as eth1 (again, until I connect the onboard eth0 and any connect to the network becomes unavailable). I have also tried putting a switch in between the server and the router (given that there are ongoing discussion on reddit and co that the intel I225-V does not play nice with all routers directly) but this made no difference (always seemed like a long-shot to me). I have attached the diagnostic file (which hopefully shows what is going on). The system is build on an MSI Z790-P WIFI DDR4 and I am using the onboard 2.5G Intel NIC (I225-V). The board is running the latest BIOS (as of today) with default settings but had initially been on an older BIOS (given the current one was released after 7.1.0). I'm really at a loss here as I have practically no expertise around network interfaces and I am also generally a Windows-peasant. I haven't changed any settings before upgrading so I suspect this is an interaction between my specific hardware and some change introduced in 7.1.0. Maybe there is some setting that didn't cause an issue pre-7.1.0 that I could just toggle? From my experience this seems to be a driver-related issue, but I have no idea how to replace that on Unraid (if it is even possible?) So far, I have been resolving the issue by reverting to 7.0.1 after every update to a newer version but that of course isn't a proper fix and the first plugins (in my case TailScale) are beginning to not support 7.0.1 I'd appreciate any insights into how to resolve this so my standard ethernet will work again. nas-diagnostics-20251208-1918.zip
  2. Is anyone getting the "Ignore files recently modified" plugin to work as expected? Which timestamp does it read? I just recently discovered UnManic and am loving it so far but this plugin is driving me crazy. I have a decent size library accrued over many years but the plugin seems to block virtually all files from being considered despite the fact that many of them are literally years old. I seem to get a ton of errors like this: 2025-01-10T00:01:23:ERROR:Unmanic.PluginExecutor - [FORMATTED] - Exception while carrying out 'library_management.file_test' plugin runner 'ignore_files_recently_modified' Traceback (most recent call last): File "/usr/local/lib/python3.10/dist-packages/unmanic/libs/unplugins/executor.py", line 256, in execute_plugin_runner runner(data) File "/config/.unmanic/plugins/ignore_files_recently_modified/plugin.py", line 81, in on_library_management_file_test if not ensure_last_modified_time_on_file(data.get('path'), minimum_age): File "/config/.unmanic/plugins/ignore_files_recently_modified/plugin.py", line 48, in ensure_last_modified_time_on_file file_stats = os.stat(os.path.join(path))
  3. I do have this enabled but for some reason, Windows doesn't execute this frequently enough for it to fix the issue. Before I made the change suggested above, it literally set the wrong time every boot from the emulated UEFI without checking with the NTP servers
  4. This works like a charm. Which just begs the question: How can we get this implemented as default when users create a VM with the Windows presets? Windows has been like this for at least the better part of the last decade. Is there some way we can flag this 1 minute fix to Lime Tech to implement?
  5. Have there been any developments on this at all? I got the SR-IOV working with the thread linked above (not smooth on 6.12.4 but workable) but similarly to Ryan that does not really cover my use-case. I'd rather not have to add a dedicated GPU to use the GPU with display outputs from a power consumption perspective.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.