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.

KoPVM

Members
  • Joined

  • Last visited

Everything posted by KoPVM

  1. Hi there, I have been having some issues recently with IPV6 on docker and it managing to break IPV6 on the VLAN. I think I have managed to identify the issue with some AI help (who knew they can sometimes be helpful) but I wanted to check that this is the expected behaviour. When I use SLAAC to give Unraid an IPV6 address it appears to configure a global address and then a link local address for the gateway. So far so good. The issue appears because Docker IPAM then appears to allocate ::1 to the first container because no global IPV6 address has been defined within the subnet. The router then detects this and effective turns off IPV6 on the VLAN. The only way to define the global IPV6 address for the gateway is to statically assign the IPV6 address for Unraid itself. Im still a bit new to IPV6 networking but wanted to check if this is expected behaviour. Im on the latest version of Unraid Have mercy if I am doing something silly! Thanks
  2. When I updated to 7.2.0-beta.1 docker containers that had the network type set to custom:br0 failed to load. On trying to edit the container it appeared that the option for custom:br0 had disappeared. I had a look at my syslog on disabling and reenabling docker and there was a strange few lines in it: Aug 17 17:48:46 newUnraid rc.docker: Processing... br0 Aug 17 17:48:46 newUnraid root: "docker network create" requires exactly 1 argument. Aug 17 17:48:46 newUnraid root: See 'docker network create --help'. Aug 17 17:48:46 newUnraid root: Aug 17 17:48:46 newUnraid root: Usage: docker network create [OPTIONS] NETWORK Aug 17 17:48:46 newUnraid root: Aug 17 17:48:46 newUnraid root: Create a networkI have since managed to get it to appear again using a version of the command in this thread: https://forums.unraid.net/topic/187522-missing-br0-network-with-unraid-701/#findComment-1531134 All appears to be working but I thought I'd submit this just incase it is causing other people issues. newunraid-diagnostics-20250817-1806.zip
  3. Hi First time doing a bug report so if you need anymore information just let me know. I upgraded to 7.0.0-beta.2 and removed my array leaving only pool devices which are all zfs. Now when Fix Common Issues runs it is discovering that a disk1 folder is being created in /mnt. The folder is empty however even when it is deleted it comes back again. Minor issue and everything else has been working great! Thanks Jamie
  4. Thanks JorgeB, I think it might have been related to the docker networking changes. I have actually went back to the old method with macvlan and bridging enabled and everything seems ok. Common issues isnt reporting any of the call traces in the logs either so I think i'm all good and will just keep an eye on it. Any issues I'll reopen the post
  5. Hi, I seem to be having troubles accessing the web interface on the latest version of Unraid. I have been running it for a few weeks without issue and then just realised I cant access the webgui. A restart hasnt solved the problem either. I have attached my syslog file. If anyone has any ideas it would be greatly appreciated. Cheers syslog
  6. The only solution I have found to the above problem is to bind the 2070 to vfio at boot. I have then created a small ubuntu vm which can be enabled to put the graphics card into low power states when it isn't being used on my windows vm. Might not be the most elegant solution but it appears to be working.
  7. Thanks for your reply. Yeah iI'll keep a close eye on it. Since i have removed the new RAM there hasnt been any further issues
  8. I think I may have solved the problem. I added more RAM to the system recently so I just did a memtest and it showed some errors. I then removed the 2 new sticks and from a quick test there was no more errors so it might just be a case of some bad RAM.
  9. Hi Everyone, I have been having a problem with my server where after a random amount of time I cant access the server via the webgui or ssh. I can sometimes still access plex which is running in a docker container when this happens. A restart seems to fix everything for a while. I have attached my logs from just after I have restarted the server. Any help or ideas would be greatly appreciated. newunraid-diagnostics-20230418-1950.zip
  10. Hi, Thanks to this guide i have managed to get GPU transcoding working on my intel iGPU while also having an Nvidia 2070 installed using the HardwareDevicePath="/dev/dri/renderD129" in the preferences file. The problem I am having is after rebooting unraid it seems like the number of the graphics cards sometimes switches. ie the iGPU is now renderD128 instead of renderD129. Is there anything I can do to stop this happening? Thanks
  11. Hi Everyone, I was having the exact same problem as the original post. Removing the Core Freq plugin solved the problem.

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.