Leaderboard

Popular Content

Showing content with the highest reputation since 05/22/21 in Report Comments

  1. For Unraid version 6.10 I have replaced the Docker macvlan driver for the Docker ipvlan driver. IPvlan is a new twist on the tried and true network virtualization technique. The Linux implementations are extremely lightweight because rather than using the traditional Linux bridge for isolation, they are associated to a Linux Ethernet interface or sub-interface to enforce separation between networks and connectivity to the physical network. The end-user doesn't have to do anything special. At startup legacy networks are automatically removed and replaced by the new netwo
    9 points
  2. Until now every Unraid 6.x version relied on traditional polling of the server to update the GUI in real-time. On the Dashboard there are multiple fields which are getting updated regularly. It is the task of the browser to initiate each time a poll request to obtain the new information and update the GUI accordingly. Polling puts load on both the browser and server, and may consume more memory over time (depending on the browser). Starting with Unraid version 6.10 the traditional polling mechanism is replaced by a websocket event driven model using Nchan.
    4 points
  3. Manged to catch this today. With the lightest of google searches it looks like it may be a bug/regression in the kernel. I very well could be wrong but maybe? https://askubuntu.com/questions/1293945/20-10-complete-system-freeze-with-general-protection-fault-smp-nopti https://www.spinics.net/lists/linux-nfs/msg78091.html https://www.spinics.net/lists/amd-gfx/msg48596.html Jun 12 14:00:01 thelibrary kernel: Jun 12 14:00:44 thelibrary kernel: general protection fault, probably for non-canonical address 0x1090000ffffff76: 0000 [#1] SMP NOPTI Jun 12 14:00:44 thelibr
    3 points
  4. Can confirm. Running PMC 8001, system boots and driver loads successfully. Many thanks to @Linux for his continued efforts and working somewhat blindly with my system to remedy, and improve, the situation. Looking forward to installing Nvidia Drivers now and offloading my transcoding back to my GPU.
    2 points
  5. I have some good news after some work with @DrBeaker we got a build off the 5.10.28 with backport fixes included in the 5.10.30 kernel 5.10.28 -> 5.10.30 pm80xx scsi driver fix We are able to successfully initialize the pm8003 card with link and see drives as expected with this simple patch thanks to @ich777 unraid kernel helper made it easy to build the kernel and dropping in patches. I am not sure if this is against the guidelines, but linking the 5.10.28 kernel built with these changes this is intended ONLY for 6.9.2 release zip package of the 5.10.28 pm80xx patch
    2 points
  6. sure, let me zip up and send you DM, i don't want people downloading until we get a confirmed use case.
    2 points
  7. Ok, solved it. It seems there is a bug which breaks the spin down if a slot is not used. After re-assigning all disks through New Config without leaving empty disk slots, the spin down works as expected! before (disk slots 5, 7 and 9 were empty): after: Why I left them empty: I planned to extend some shares by adding new disks without putting them on the bottom. So it was only a "visual thing" for me.
    1 point
  8. Standards are so good that everyone wants their own, so that's what Microsoft did: See here: https://tldp.org/HOWTO/CDROM-HOWTO/x1186.html#AEN1328 Perhaps Joliet support is not included in the Unraid kernel but it is in the Ubuntu kernel. That would make sense because Unraid is not a general purpose Linux and has a lot of unnecessary options removed. If that's the case then your options would be: re-create your .iso with Rock Ridge enabled; use a different image file format that supports long filenames and mixed case natively; use an Ubuntu
    1 point
  9. It's an Unraid/GUI bug, you can still do it manually using the console.
    1 point
  10. From the mount(8) man page: What is the origin of your .iso file? Is it Rock Ridge compatible? Using a standard Kubuntu installation image, it works fine for me: root@Pusok:~# mkdir t root@Pusok:~# mount -t iso9660 /mnt/user/isos/kubuntu-20.10-desktop-amd64.iso t mount: /root/t: WARNING: source write-protected, mounted read-only. root@Pusok:~# ls t EFI/ boot/ casper/ install/ pics/ preseed/ README.diskdefines boot.catalog dists/ md5sum.txt pool/ ubuntu@ root@Pusok:~# ls t/casper filesystem.manifest filesystem.si
    1 point
  11. It is now working correctly once I did according to your recommendation. Thanks again for your help.
    1 point
  12. Hum thanks but I just participated as a moderator to mark it Solved.
    1 point
  13. @Chris Mot & @ChatNoir I've updated the Intel-GPU-TOP plugin yesterday so that no modification to the syslinux.cfg is necessary anymore. Please make sure that you are on the latest version from Intel-GPU-TOP (2021-06-15), remove the added parameter to the syslinux.cfg (i915.force_probe=4c8a) and reboot. Everything should now be enabled automatically. Please leave me a short message here if everything worked fine.
    1 point
  14. Hey, I just upgraded and made a post about this over here. Just to keep things simple i'm going to roll back. (I don't need any of the new features or NVidia driver support). But is there a timeline of when this will be fixed? -Thanks
    1 point
  15. Changed Status to Solved Changed Priority to Other
    1 point
  16. I'm not sure how true this is, but I was under the impression that it was broadcast traffic, in conjunction with static IPs that was causing macvlan to s*** the bed and cause kernel panics. Now I'm not sure if this is true with every vendor, but Ubiquiti switches/routers do not route broadcast packets between networks (so I was told/read), which was the idea behind creating vlans for docker containers with static IPs. I also think it was thrown out there that certain network adapters may be more prone to this than others. This is a very good point since it could b
    1 point
  17. I went this route and even created user defined bridge networks on a completely different NIC and still had the same issues. I suspect you'll see the issue resurface in a week or so, as this is exactly what happened to me. I have not tested using VLANs, but moved any containers needing their own IPs off of Unraid and haven't had issues for months.
    1 point
  18. What service is it? Out of curiosity at this point really. What about adding another NIC (if your motherboard doesn't already have 2 or more LAN ports?) That could be a very cheap $15 card for a gigabit NIC. https://amzn.to/3zfpmzF (referral link) I beleive that way you could keep the same IP address, but give it its own network interface instead?
    1 point
  19. Which container has a size of more than 1GB?! And most of them re-use the same packages. 100GB is really crazy ^^
    1 point
  20. I don't know, but who cares? It contains only docker related files. Rebuilding is done fast.
    1 point
  21. This is something which needs to be solved by docker: https://github.com/moby/moby/issues/42200
    1 point
  22. I added the card after, im sure kernel had nothing to do with it. After a whole day of troubleshooting it appears the card was being fussy about the particular PCIE port it was in, i dont understand why as the port and card functions but moving it to a different slot caused it to show up with absolutely no issues. though this causes the card to take up 2 slots im just going to have to do without something for now, thanks for your help.
    1 point
  23. Thanks for the solution works great!
    1 point
  24. After building a custom QEMU 5.2 slackpkg and implementing the workaround described above, I was also able to use virtiofs to pass-through directories on my Unraid host to my VMs. However, determining the correct compilation options for QEMU was a time-consuming, iterative process. I reached out to @limetech and they confirmed that QEMU 6.0 will be included in Unraid 6.10 which is coming "soon". For future readers of this thread, if you are not in immediate need of this functionality, I would recommend waiting for Unraid 6.10. If you cannot wait I have a few notes that may help you get this wo
    1 point
  25. I've never had host access to custom networks enabled and still see this problem. I thought I resolved the issues by putting all docker containers in standard bridge mode on their own NIC, but this doesn't seem to have resolved the issue. I was thinking that for some reason UNRAID did not like Docker Sharing an IP on the same NIC that hosted the UNRAID UI and/or any other services, but this doesn't seem to be the case. I'm starting to think this issue is more related to how Docker is implemented on UNRAID. I tend to agree with @CorneliousJD that this issue is related to the use of
    1 point
  26. hi sorry to disturb but a question from a amateur-linux guy, so every user for share´s does need to be in the right directory in etc/passwd right? How is this for Active Directory integration? My secondary Server does have 6.9.0 now and i can´t even make a public smb-share since 6.9.0.... in 6.8.3 all is fine Maybe im missing something or its a whole other issue.. Regards Xutho
    1 point
  27. I've done some digging on this - here's what I found. Mount unraid share system on my mac and check its spotlight status: [macbook-pro]:~ $ mdutil -s /Volumes/system /System/Volumes/Data/Volumes/system: Server search enabled. [macbook-pro]:~ $ But as best I can tell "server search" is not in fact enabled. Turns out samba 4.12.0 changed this search-related default: Note that when upgrading existing installations that are using the previous default Spotlight backend Gnome Tracker must explicitly set "spotlight backend = tracker" as the new default is "noindex
    1 point