Sergeant_Stevie

I prefer doing things manually via CLI as I can specify the quality (e.g. fhd) and also see if some shows are only available in other formats (e.g. sometimes a TV show is only available Audio Described despite all others in the series being "original") as it throws an error if that happens. If I put a single PID in and let it download, is it going to apply the same settings to the console commands? Or does the incomplete/complete behaviour only apply to the script that checks every x hours?

So I've checked under advanced view and I do not have a DEBUG variable, I added one but the log doesn't contain much in the way of "DEBUG" information, only 3 entries for "DEBG" and nothing else gets written to the log even after downloading a program from iPlayer (via CLI, not by entering a PID/Show to the container config). I tried starting from scratch again, including deleting the binhex-get-iplayer folder in appdata, but it seems to do the same thing as before and there is no options file in the newly created folder. Attached the two files as requested. binhex-get-iplayer command execution.txt supervisord.log

I must admit this was not the case for me. Those folders were created at the location I pointed /data to when I first installed the docker last year, but they're not being used by the current more recently updated docker. I've only just started using the docker version, but I haven't changed anything (except what I wrote yesterday). So, some time between December 24 and now something changed with my docker that made it revert to using the vDisk. Which again is strange because I can clearly see that there is an options file in appdata/binhex-get-iplayer which is where /config is pointing to, but for some reason it isn't being used. Although it is strange that it knows where FFMPEG is but not Atomic Parsley. I guess I can try deleting the Docker image entirely and setting it up again and see if it works 🤷🏻.

I spent quite a while trying to figure out how to fix my issue of not being able to find where get_iplayer via CLI is storing the files. Without specifying any specific output location when running the command, it seems that it just stores it in the docker vDisk which is not accessible to SMB or root on the GUI. There does seem to be an open issue on Github about this very problem from May 20th 2021...yet other people seem to manage to use it just fine, so unless everyone is used to specifying output or it just isn't automatically added to the preferences when you first start the Docker. Likewise, the atomicparsley location is also not known when using the command line, despite this being in the options file in the config location, so it has to be specified as part of the command in order for it to be able to tag the MP4 files. FFMPEG works just fine however, despite the path to that also being in the options file. EDIT: I tried to update the preferences with the output location, but it saves the options file in /home/nobody/.get_iplayer/options which I have no idea where that is or if it exists. So I'm guessing that the options file in the binhex-get-iplayer folder is not the one actually in use by get_iplayer itself. According to the generic get_iplayer wiki, the user preferences directory can be changed at runtime with --profile-dir, but this isn't saved in your options file, so you should instead use the environment variable. Is there any change this can be remidied?

Safe mode or normal mode, the result is the same. The only "fix" seems to be enabling "Deep Sleep in S5" in the Chipset Configuration in the BIOS. I am absolutely certain that the server shut down perfectly to begin with when the Deep Sleep setting was "disabled" (which it is by default), and this behaviour started after enabling Wake on Lan for eth 1. I still don't have an answer to the question of WHY Wake on Lan is not staying disabled when all I did to enable it was follow the instructions here: https://docs.unraid.net/unraid-os/guides/wol-setup-for-unraid/ If running "ethtool -s eth1 wol g" permanently enables WoL, then by the same logic surely following the same instructions in reverse would permanently disable it? So why when I run "ethtool -s eth1 wol d" does it revert to "Wake-on: g" when I next reboot Unraid? Yes I can put code in the go script to be run at boot to disable it, but why should that be needed if it wasn't needed to enable it?

I made sure that there are no options to wake set to enabled in the BIOS, I've checked again and in the meantime I added "/usr/sbin/ethtool eth1 wol d" to the "go" script and checked with "ethtool eth1" and saw "Wake-on: d" so assumed it was disabled, told unraid to shut down and it stayed powered again. I have an AsRock Z790 Pro Rs ATX DDR5 (no WiFi) motherboard with an i9-12900k, and made sure that under Advanced > ACPI Configuration, PCIE Devices Power On was set to disabled, and I'm at a loss as to why it's staying powered.

I have been troubleshooting why my server does not fully shut down when I tell Unraid to Shut Down, as when I did this the server would leave the Power LED on and would have to be physically power cycled by the switch on the PSU/unplugged from power in order to boot the server again. I have now tracked this issue to Wake on Lan being enabled, I disabled it on eth0 (onboard 2.5G NIC) and then disabled it on the Asus 10G PCIe NIC which is eth1. I then checked that with WoL disabled on both NIC's it will properly shut down, which it does. However, every time I now tell Unraid to shut down or reboot, and I check "ethtool eth1" via terminal again, I find that it has again enabled WoL on eth1. I've run "ethtool -s eth1 wol d" and that disables it, but as said only until you reboot. How do I get Wake on Lan permanently disabled on eth1?

I have 7 fans in my system, those along with the Motherboard & CPU temps, and also the Data Volume Monitor Plugin, means that when they are all loaded into the Status Bar, the text is too long and it overlaps "Array Started" so it gets put onto a new line, which is off the bottom of the screen. So far, the only way I've found to stop this is to set the text to very small, which is less than ideal as it affects all text, not just that of the Status Bar. So, is there a way to adjust the height of the status Bar, and/or remove the copyright/manual links from the beginning? Or even remove things from the Status Bar? I've tried Google and looked through everything in Unraid's settings and that of Theme Engine, and haven't seen anything to let me change the status bar height or text size separately from everything else. Also, is there any easy way to change the Fan names on the dashboard, as currently They're just "FAN 1" to "FAN 7", I know which fans are which, and I tried using Theme Engine with custom CSS as suggested elsewhere, but the CSS/script doesn't work so it does nothing to the UI.

Is there a way to run it via terminal/ssh? I'd like to be able to download in 1080p which means using: --tv-quality="fhd" when running the get_iplayer command. Normally get_iplayer downlaods TV shows only in 1280x720, and having downloads at 1920x1080 would be nicer.

So I configured several SMB shares on my newly built Unraid server, but the only time I can get them to show up in Windows 10 is when I enable NetBIOS on Unraid and re-enable SMBv1/CIFS on Windows 10. Something that nobody should be doing due to the insecurities involved in it. I can access the server just fine using the \\server-name method, which allowed me to pin it to quick access, however this is not ideal as it's not obvious or simple to use (despite telling my Father where I'd linked it he still couldn't find it). I assumed that WS-Discovery being enabled on Unraid should allow for the shares to be seen in Windows 10's "Network", but this doesn't seem to make any difference even though I can see from a port scan that port 3702 for Web Services Discovery and port 5355 for LLMNR are active along with 139 for NetBIOS Session Service & 445 for SMB. I've had issues with Windows before, but usually it eventually works itself out. I've already checked Windows has the Network set to Private and all the appropriate services (FDHost etc etc) are enabled and running. The Workgroups match (both set to HOME), and like I said it is possible to access it manually, but it just doesn't appear in the Network List until you turn to insecure methods. Is this just one of those limitations of Unraid that because it's not Windows Server it just won't appear unless you use SMBv1/CIFS?

Hi, Would it be possible to make one for the Jonsbo N5 case please? Thanks :)