Leaderboard
Popular Content
Showing content with the highest reputation on 07/27/22 in Posts
-
Just so we're all clear here... Jellyfin + Unraid 6.10 (or later) = Works Jellyfin + Unraid 6.10 (or later) + iGPU = Works Plex + Unraid 6.10 (or later) = Works Plex + Unraid 6.10 (or later) + iGPU = Does not work3 points
-
2 points
-
I have an i9-12900K and upgraded yesterday to 6.11-RC1 and so far no issues to report. I have enabled the iGPU in PLEX again but only did a very brief test and transcoding worked for me without crashing. I did have HDR Tone mapping set to off and did a basic test on a 1080p movie. I know its still hit and miss at the moment so have turned HW transcoding off for the moment until PLEX release their new version and some more fixes in PMS 1.28.1 or 1.28.2. At least we are moving forward and now we have the Linux Kernel updated to the version we need. Now we wait for PLEX to catch up 😞2 points
-
The only discussion to the contrary are people who set it up and it initially seems to work (it will work, after all) right up till when the crashing starts. To be absolutely clear, *with the current Unraid 6.10 build*, Plex (and Jellyfin, and Emby) work fine, *so long as you don't pass them the iGPU and/or enable hardware transcoding.* This isn't debated at all.2 points
-
Tons of posts related to Windows 10 and SMB as the root cause of the inability to connect to unRaid that were fruitless so I'm recording this easy fix for my future self. If you cannot access your unRaid shares via DNS name ( \\tower ) and/or via ip address ( \\192.168.x.y ) then try this. These steps do NOT require you to enable SMB 1.0; which is insecure. Directions: Press the Windows key + R shortcut to open the Run command window. Type in gpedit.msc and press OK. Select Computer Configuration -> Administrative Templates -> Network -> Lanman Workstation and double click Enable insecure guest logons and set it to Enabled. Now attempt to access \\tower Related Errors: Windows cannot access \\tower Windows cannot access \\192.168.1.102 You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network.1 point
-
In this blog series, we want to put a spotlight on key community members to get to know them a little better and recognize them for all that they've done for the Unraid community over the years. This next blog features two outstanding community members who have helped out countless new Unraid users over the years: @JorgeB and @ich777 https://unraid.net/blog/rockstars-jorgeb-ich777 If either have helped you out over the years here, please consider buying them a beer or lunch! JorgeB ich7771 point
-
No that diagnostics was the second thing I did with the server after the reboot. (the first thing was to start the VM "Daily-driver", via my mobile phone, wich is my "daily-use-computer")1 point
-
Yes, I was aware of this and was thinking of mentioning it, I just hadn't rebooted due to an ongoing parity-check. The parity-check was on 96% or something like that so I "forced" it, and I have now rebooted. Guess what.... It now works to create the diagnostics via the "Tools". EDIT: I would like to give a big thanks to you guys, this community is amazing!! unraid-diagnostics-20220727-2024.zip1 point
-
1 point
-
Okay, it seems to have come back online but because it's yet another new flash drive my license key isn't valid and needs to be transferred over. I'll contact support and see if they can allow another transfer to a new drive within the year.1 point
-
1 point
-
Now I'm able to login. So that looks OK, but I still cannot create a diagnostics... Though that might be anothr matter.1 point
-
root@Unraid:~# /etc/rc.d/rc.unraid-api install API has been running for 1s and is in "production" mode! -----UNRAID-API-REPORT-----> SERVER_NAME: Unraid ENVIRONMENT: production UNRAID_VERSION: 6.10.3 UNRAID_API_VERSION: 2.49.2 (running) NODE_VERSION: v14.15.3 API_KEY: invalid MY_SERVERS: signed out CLOUD: API key is missing RELAY: disconnected MINI-GRAPH: disconnected ONLINE_SERVERS: Unraid OFFLINE_SERVERS: HAS_CRASH_LOGS: no </----UNRAID-API-REPORT----->1 point
-
root@unraid:~# ls -al /usr/local/sbin/unraid-api lrwxrwxrwx 1 root root 36 Jul 27 17:38 /usr/local/sbin/unraid-api -> /usr/local/bin/unraid-api/unraid-api root@unraid:~# ls -al /usr/local/bin/unraid-api/ /bin/ls: cannot access '/usr/local/bin/unraid-api/': No such file or directory1 point
-
Well it says the same for me, but if you check the logs I attached you can see that the installation was completed.1 point
-
1 point
-
FWIW, I confirmed that it does not work for me before making my post.1 point
-
1 point
-
from your screenshot it looks like you defined the 'Name' of the port incorrectly, its not 'WEBUI PORT' its 'WEBUI_PORT' and the type is wrong, its a variable NOT a port. @Squid you are quite right, the user should not be redefining the container port - however qbittorrent is an exception to the case here, here are my notes from the qbittorrent README.md (geared more towards non unraid users, but you get the gist):- so for unraid users that means setting WEBUI_PORT to the port you want and then re-creating the port to match (host and container side being the same). i then have some code to pick up the env var WEBUI_PORT to set the port for the running application (qbittorrent in this case).1 point
-
1 point
-
If a share is created automatically in this way, it will have default settings. One of those defaults is cache:no I just tested this by creating a top level folder directly on cache. The resulting user share is cache:no despite the fact that it only has files on cache. So any new files would go to the array.1 point
-
FYI just upgraded to v7.1.68 as it didn't seem to have many changes. No issues upgrading. Will report back if anything goes haywire.1 point
-
so containers talking to each other in the SAME network can be done via localhost and the port the application uses, you should not be defining ports in VPN_OUTPUT_PORTS unless you want an application using the VPN network to communicate OUTSIDE of the VPN network to another application. see A24 note 1 for details about localhost:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md see A27 for details about correct usage of VPN_OUTPUT_PORTS https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md you should be able to use a custom network - at least it did work in testing a long time ago!, what you cannot use is specific ip addresses for the vpn container, that will not work. p.s. i do not like the usage of VPN_OUTPUT_PORTS or VPN_INPUT_PORTS actually, its a little confusing for the average user, however its a necessary evil (havent found a better way) to guarantee zero ip leakage which of course is the most important thing, so for now thats how it is.1 point
-
Jul 26 12:51:19 unraid kernel: BTRFS error (device nvme0n1p1): block=230151340032 write time tree block corruption detected Btrfs went read only because it detected corruption before writing the data to the device, this is usually bad RAM or something else causing kernel memory corruption. P.S. also saw some macvlan call traces, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right))1 point
-
Error: [autovideoconverter] Skipping '/watch/TEST_MOVIE': not readable, check permissions. Unraid: 6.9.1 Handbrake 1.5.1 I'm new to using this HandBrake docker and am also having trouble with auto video conversion /watch. A manual conversion of the same folder is successful so the path(s) are read/writeable. Any ideas? Shares: /watch : /mnt/user/movies/TEST/ : (public) /output : /mnt/user/mkv/ : (public) Watch folder permissions: drwxrwxrwx 1 nobody users 32 Jul 26 21:22 TEST_MOVIE/1 point
-
as a side note i just uninstalled unassigned devices and so far my speeds are around 150mb/s1 point
-
Both come up with the same answer. Looks like a display issue. I'll have a look.1 point
-
AFAIK yes. Two different concepts. The VPN_INPUT and OUTPUT ports are to punch holes in the delugevpn containers internal firewall. The container is sealed up pretty tight to keep the VPN connection secure from accidental real WAN IP exposure.1 point
-
du solltest die Optionen für CPPC im BIOS aktivieren. Konnte ich bisher aber noch nicht verifizieren. Danke für den Einsatz @ich777 ! Ich hab mein System gerade erst wieder stabil bekommen, will es eigentlich ungern auf ein Prerelease loslassen.... aber neugierig was man messen kann bin ich schon ... vielleicht nächste Woche.1 point
-
Both docker.img and cache are readonly due to corruption. You can recreate docker.img after you fix cache. You may have to copy what you can from cache and reformat it. Have you done memtest recently?1 point
-
Du solltest diesen Thread mal lesen, weil das selbst in Windows nicht trivial ist: https://www.computerbase.de/forum/threads/renoir-und-b550-die-idle-kuenstler.1967755/ Hier auch mein Beitrag: https://www.computerbase.de/forum/threads/renoir-und-b550-die-idle-kuenstler.1967755/post-24812476 Es sollte in jedem Fall ASPM und ALPM forciert werden. Je nach Board hat die Deaktivierung von Komponenten wie zb LED Controller keinen oder einen großen Einfluss auf den Verbrauch. Da hilft nur durchprobieren und jede Änderung messen.1 point
-
1 point
-
Personally I would prefer a "G" type processor. UNRAID does not need the full power of the 5800X (which is overkill too if you do not plan to overclock). I've picked a 5700G for myself and am quite pleased with it. The "G" also comes handy if you plan to put in another graphics card to be passed thru to a VM (though I have no experience with this, but the forum here contains a lot of problems with passthru, so better search for them and look for solutions.) 4-5 VMs are no problem, unless you do evil things with them like DOWNLOADING. Unraid's QEMU is a snail when it comes to fast LAN transfers. The cores hit 100% usage rather easily and the temp goes up through the sky 😞 Even with one VM doing heavy downloading, you can kill the box already. Its really a shame. AMD CPUS and RAM is a delicate combination with UNRAID. If ECC or not, you need to run "memtest86" (download the newest version, the version that comes with unraid does not recognize modern CPUs/RAM) for some time and experiment with the BIOS settings if any problems show up. Even buying "3200" ram does not guarantee that your board/cpu/power supply combination allows you to use this speed safely. Some advice you to raise certain voltages (which will result in a fast wearout of the ramchips), I would personally say "don't go over 1,35V. instead lower the speed". My box for instance runs stable with 1,35V and 3000 Mhz only. (you dont need to wait for memtest to finish each time. Once an error shows up, cancel, change bios and restart memtest skipping the tests that have been successful before, After all tests have passed, play it even safer and rerun memtests from the beginning (all tests) once more) Instead putting money on ECC better spend a week on memtest. Unless you change ram sticks (or your values are too high), you will be safe for years.1 point
-
@SpencerJ and the team worked hard through the 4th of July to bring a surprise, which awaits at:1 point
-
can confirm that ich777 is the one of the best and fastest answers from him you can get for help if needed ...1 point
-
Indeed, thank you both. The Community and Unraid will not be the same without the great work you do. 🤘1 point
-
Hi all, any chance of a mobile friendly ui being implemented? Current experience on mobile is terrible.1 point
-
Is the build for today borked for anyone else? Seeing this over and over in the logs and can't reach the admin page:1 point
-
1 point
-
the point is not actually to prepare the disk for unraid, that is just a nicety that this utility can/should do, the MAIN purpose is to exercise your drive and ensure it doesn't suffer from infant mortality.1 point
-
1 point
-
I finally found a fix, that works with my machine! I added the following code to the /flash/config/go file: #fix video for VM echo 0 > /sys/class/vtconsole/vtcon0/bind echo 0 > /sys/class/vtconsole/vtcon1/bind echo efi-framebuffer.0 > /sys/bus/platform/drivers/efi-framebuffer/unbind Those lines unbind the console & by adding it to /flash/config/go will execute this piece of code on every boot of the system.1 point
-
I realize this is a serious necropost, but wanted to give @maciekish a huge thank you for sticking with this after the responses he got. I'm using a reverse proxy with Nginx and had the same problem and this lead me to the same solution. So for anybody getting here from Google you'll want to add the following to your Nginx config to get things working again. You could be clever and only apply it to the locations that are broken, but since my reverse proxy is not even exposed outside my network I just disabled gzip for the whole server definition: server { gzip off; ... } As an FYI to all the doubters above, if they still hold their positions. A reverse proxy is a very handy way to make it so you don't have to remember unique port numbers of all your internal services. http://unraid.home.local or http://sonarr.home.local are totally valid internal domains if your DNS is setup right and will hint the server to your password database tool of choice so you don't have it offering up 30 passwords because everything is on the same IP address of the server.1 point
-
It was actually complaining every eight minutes. Toggling Use SSL to Off (click Apply) and back to Auto (click Apply) seems to have stopped the messages.1 point
-
Is the image UEFI compatible? Try creating a new VM template, this time select SeaBIOS instead of OVMF before starting it for the first time. Advanced view.1 point
-
KVM can handle vmdk files directly. The only caveat is that you have to enter the full path to the vmdk when creating the VM as the GUI does not provide a selector for that file type.1 point