Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation on 11/15/19 in all areas

  1. 1 point
    Application Name: Heimdall Application Site: https://heimdall.site or https://github.com/linuxserver/Heimdall Docker Hub: https://hub.docker.com/r/linuxserver/heimdall/ Github: https://github.com/linuxserver/docker-heimdall Please post any questions/issues relating to this docker you have in this thread. If you are not using Unraid (and you should be!) then please do not post here, instead head to linuxserver.io to see how to get support.
  2. 1 point
    When you swap out a router, you usually have to reboot all of the computers on the network. If, for no other reason, to make sure you don't have two computers with the same IP address. EDIT: Way back in the dark ages, you had to manually assign static IP addresses to everything on the physical network (remembering 10BASE2 hardware). That was fun as the administrator had to keep of them to make sure each address was unique.
  3. 1 point
    The old router maintained a non-volatile table of IP address reservations (most consumer routers / Internet modems do this). It does this so that the same IP address is assigned to the same MAC address (device) each time things are rebooted or power cycled. When you replaced the router, all those IP reservations are gone, and you get reassigned (likely different) IP addresses for the various devices on your network as the new router finds various devices and assigns them IP addresses (assuming it's running as DHCP master, which is usually default in consumer devices). However you may have told your browser to look for the Unraid GUI on a specific IP address (for example via a bookmark), which is no longer the right IP address. Similarly, Windows is looking for SMB files which are now at a different IP addresses. Rebooting the Windows computers causes them eventually to find the new IP addresses, and it can then figure things out. Your browser (or browser bookmark) [probably] doesn't know how to find the new IP address, and you may have to manually enter that. -- Tom
  4. 1 point
    Probably could use a change to the default label to add something like "non-UEFI only" to prevent against confusion.
  5. 1 point
    I thought I might post this here as it's taken me a while to piece it all together and it may help someone else get Fan Auto Control working. I have a Gigabute Z390 Aorus Elite board. Unraid can't support the fan PWM controler out of the box. I spent a couple of evenigns playing with sensors-detect btu noting was recognised. Then I found this page: https://github.com/a1wong/it87/issues/1 Essentially, you go to Main -> Boot Devices ->Flash -> Syslinux Configuration -> Unraid OS Change the second line from: append initrd=/bzroot to: append initrd=/bzroot acpi_enforce_resources=lax Then add this line to your /boot/config/go file: modprobe it87 force_id=0x8628 Reboot and Fan Auto Control should see your PWM fan.
  6. 1 point
    You can only run the memtest included with Unraid if booting in legacy mode. If you want a version that can be used when booting in UEFI mode then you need to download it yourself from the memtest web site.
  7. 1 point
  8. 1 point
    Yea, those lists. Problem solves itself by using the "Safe docker permissions" thingy, but as soon as I download something new the rights gets broken. Hmm, well it seems that I was correct using TRANSMISSION_UMASK as I did at the start, I have now switched back, will try with some small downloads. What I have read, 000 is the same as 777 so I am going back to this to try again, maybe I missed something. Thanks, will report back my findings.
  9. 1 point
    I've never used this particular setting, But I believe your key should be set to TRANSMISSION_UMASK , not just UMASK Basically any variable you see here or here can be added to your docker template with TRANSMISSION_whichever_setting_you_want_to_be_Static_after_reboot_of_the_container set as the key as you indicated in your post. For instance, I have my Queue size set :
  10. 1 point
    Hi! I'm having an issue with the Transmission_VPN docker image regarding the UMASK settings that is driving me nuts. Hopefully someone could nudge me in the right direction. I am unsure of the correct variable name, according to some variable chart I found all variables are "TRANSMISSION_WHATEVER" (which worked for all other variables I have set), however that did not seem to work for umask so I switched to just "UMASK" as variable, but still can't get it to work. For some reason I get this in the download folder: Topfolder = drwxrwxr-x 1 nobody users - Can't edit Subfolder = drwxrwxr-x 1 nobody users - Can edit Files = -rw-rw-r-- 1 nobody users - Can edit (and execute...?) How come the same rights, topfolder and subfolder behave differently when browsing samba? Download folder is accessed using a unraid user with R/W access (private samba share), are these settings interfering? Whats the correct variable and setting to use to have it set 777 (or at least 775) on all folders and files? Right now I have the settings like this:
  11. 1 point
    Overview: Support for Docker image arch-jellyfin in the binhex repo. Application: Jellyfin - https://github.com/jellyfin/jellyfin Docker Hub: https://hub.docker.com/r/binhex/arch-jellyfin/ GitHub: https://github.com/binhex/arch-jellyfin Documentation: https://github.com/binhex/documentation If you appreciate my work, then please consider buying me a beer 😁 For other Docker support threads and requests, news and Docker template support for the binhex repository please use the "General" thread here