Chunks

I'm not sure I'm doing this correctly, but I grabbed the XML. I don't think there's anything sensitive in there, the only change I made was to the path. Here's the command that runs (successfully as far as I can tell): root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker create --name='rmlint' --net='bridge' -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -e 'GUAC_USER'='' -e 'GUAC_PASS'='' -e 'PUID'='99' -e 'PGID'='100' -p '8322:8080/tcp' -v '/mnt/user/Photos/':'/root':'rw' -v '/mnt/user/appdata/rmlint':'/config':'rw' 'bobbintb/docker-rmlint-unraid' d86f95afa658ec3ac59acf94325c058d73b9afe1a140f01a0991049069b4e849 The command finished successfully! --- I really hope none of this data is sensitive. I think it's not Thanks for checking this out, I appreciate it. There's a chance it's a system issue. I dunno. rmlint.xml

I've tried getting this to run, and after downloading/installing the image, I am stuck. When I start the container, the log gets filled with a TON of "Exec Format Errors". It looks like they're just looping after that. These are the first few lines of the log, in case that's helpful. I can provide the rest of the log as well if it would help.. 2021-04-11T11:34:39.048094872Z foreground: warning: unable to spawn /docker-mods: Exec format error 2021-04-11T11:34:39.078252944Z [s6-init] making user provided files available at /var/run/s6/etc...exited 0. 2021-04-11T11:34:39.145482632Z [s6-init] ensuring user provided files have correct perms...exited 0. 2021-04-11T11:34:39.148697163Z [fix-attrs.d] applying ownership & permissions fixes... 2021-04-11T11:34:39.150926422Z [fix-attrs.d] done. 2021-04-11T11:34:39.152785844Z [cont-init.d] executing container initialization scripts... 2021-04-11T11:34:39.155464041Z [cont-init.d] 01-envfile: executing... 2021-04-11T11:34:39.157618520Z foreground: warning: unable to spawn /var/run/s6/etc/cont-init.d/01-envfile: Exec format error I googled a little, and maybe this is a problem with the shell command? I dunno.... I know just enough about linux to be a danger to myself

This has happened a couple times to me as well. In the last few weeks I've left browsers open and viewing the dashboard page for many days at a time (I'm the guy with 10 windows, 50 tabs in each, and since I've been working on a few things I end up with a bunch of Unraid dashboard / Main windows open). I'm using Chrome. I can confirm that running "/etc/rc.d/rc.nginx restart" via SSH resolved the problem for me (temporarily?) before my system completely locks up. Last time this happened the Web UI was completely hosed and I had to restart by force (I forgot to try SSH).

Out of curiosity, are temperature threshold values for drives reset when you do a version update? Ever since I installed the new release, my nvme drive is giving temperature alerts - at first I thought it was being pushed harder, but then I realised that I might have increased the temperature alert values in 6.8.3, ages ago.

Dumb question, but I'm a linux newb. I see a fair few comments about it being easier with 6.9.* to add modules. I can tinker and screw around some weekend, so I'm not asking for someone to do the work for me, but my motherboard has a module for reading more sensors. https://github.com/electrified/asus-wmi-sensors Is this feasible for a relative newbie to do? Can I build it as a plugin or even put it on the app store if I figure out that far?

Aha, thank you. That makes me feel a bit better, especially if it's so rare that this is the first time in a year and a half. I'm not sure what I'd use IOMMU for, but I feel like my VM's may use it.. but I'll definitely look into making any updates that I can.

Last diag update, ran this on the same reboot as the previous one, but after the extended tests had finished. I'm not even sure if the files will include these updates, but at least none of them reported errors. After.Long.Smart.chunksunraid-diagnostics-20201226-0701.zip

Here's a fresh diag, but the extended tests haven't finished yet. Still waiting on those... Thanks so much for having a look. I appreciate it a lot!! After.Reboot.chunksunraid-diagnostics-20201225-1935.zip

Hello! I was greeted today by two drives (out of five) giving read errors. One is a second parity, one is a regular drive. (I do have a handful of crap unassigned devices in there as well.) I grabbed the diagnostics, then rebooted, I'm currently running extended smart tests on all drives. After the reboot, unraid reported all errors cleared, but I have two disabled drives now. I can't see any errors in the smart diags, but I reading badly on my phone until I can get home to the computer itself. I'd appreciate any "next step" type advice, and thoughts on trying to keep using these drives) Thanks in advance chunksunraid-diagnostics-20201225-1046.zip

Hello all, I had some time this week to tinker around with my Unraid machine, and noticed the new docker setting "Host access to custom networks:" on the Settings -> Docker page. I enabled it, even though I wasn't sure I needed it, but I wanted to play around. Immediately I noticed that my router went bonkers, complaining of a ton of IP conflicts. I use Arpwatch on PFSense, and it was complaining about a ton of IP's being assigned to multiple MAC addresses. Turns out this is expected behaviour, because the way that "Host access to custom networks" works is by creating a bunch (in my case anyway, with a few VLANs on my machine) of extra "shim" network interfaces. For reference: Today however I noticed a second ... thing. My Windows 10 VM (on Unraid) started having connectivity problems to my local Network shares (also on the same Unraid machine). All worked fine for weeks before this setting was turned on. The symptoms for me, was that if I used my VM (which lives on a VLAN bridge interface) to say, create a torrent file from a file that it was accessing from a share, it was running fine for a few seconds, and then freezing, and then marking itself completed. The torrent files were being filled with "null" values, and were invalid. I also had it try to recheck a known good torrent file, and this one failed as well - it rechecked for a few seconds, and then died. The torrent client reported an I/O error and killed the recheck process. Disabling the "Host Access Custom Networks" setting rectified the problem. The checks completed successfully immediately. I'm not sure exactly why I'm posting except maybe in case anyone else has issues after enabling this setting like I did. Edit to add, I have diagnostics (from after the setting is turned off) but I'm not really comfortable sharing even the anonymised ones publicly. I can send 'em directly if someone is interested though.

After upgrading to RC8 - My dockers are all running, my VM is up on my VLAN interface, no errors since last night when I upgraded. Looks like I'll be sticking with RC8 for a while! Thank you.

Was disabling Wireguard enough for you? I just gave that a shot - disabled my wireguard tunnels and then directly started up my VM (on br0.xx vlan) and it started erroring all over the place as soon as I logged in and started using it.

Do you have a lot of traffic going through it? When I start up my VM's, I get a couple of log entries, but if I don't really use it nothing happens. It's when I try to put some bandwidth through it (going online to do a speedtest for example) the logged errors start flowin'.

I do not have good info regarding when this started - I first noticed after upgrading to RC6, but I just rolled back to RC5 and it's still there, and due to really light VM usage, it's possible I just didn't notice. So count me out as far as useful datapoints.

Just to add (I sent this directly to LT as well) but for other users who are troubleshooting - I can cause the errors to start by starting a Linux (ubuntu) VM on my VLAN as well, so while the issue is connected to VM's (at least it appears to be in my case) it's not the OS on the VM itself.

I was trying to get Telegram notifications working with the Docker. From what I can see, you just enable the "notification script" option, and then fill out some variables to send to "sabnzbd-notify.py" I'm getting errors and it's not working. I cannot remember if I added the Notify script myself to "appdata\sabnzbd\scripts" or if it was included with the configuration. But it's there now. I made the python files executable (I just 777'd them, because I don't understand security, or linux I guess) and it seems like it's missing other things. Anyone got this working? Or have tips on what I should do? Most of my googling comes back to installing missing Python libraries (setuptools), but I'm not sure I want to go too deep down that rabbit hole without asking here first.

I grabbed my diagnostics and was about to send them but then I had a thought - I am using firefox which is having the problem. I switched to Edge (it's what I have) and the page loaded fine. Chrome just finished installing and that works fine too. It may just be Firefox that is choking?

I have the same issue, I updated this morning without any errors but now it hangs at "Updating Content" and doesn't do anything or give any errors. I just removed and reinstalled the plugin and that did not fix it - the same issue persists. I am running 6.7.0-rc5 not the latest, if that matters.

I completely understand. I was so focused on filling everything out, I kind of forgot the point of the plugin. What you said definitely makes sense. Thanks again though, as I said, everything else works perfectly.

I've set this up and I didn't have any problems except that my Samsung NVME cache drive isn't showing up at all. I'm not super linux friendly, but I did dig through the thread looking for anyone else with this problem. I saw someone running the command "lsscsi -u -g" but when I do that, my NVME drive isn't shown at all. I can see 4 HDD's from my onboard controller, and 2 other HDD's from my External controller, and my Flash Drive is also visible (sg0). But not the NVME drive (pardon the silly obfuscation) :~# lsscsi -u -g [0:0:0:0] disk none /dev/sda /dev/sg0 [1:0:0:0] disk 500xxxxxxaf48d06 /dev/sdd /dev/sg3 [2:0:0:0] disk 500xxxxxx2d2cedb /dev/sde /dev/sg4 [3:0:0:0] disk 500xxxxxx2da8bbe /dev/sdf /dev/sg5 [4:0:0:0] disk 500xxxxxx7286f91 /dev/sdg /dev/sg6 [10:0:0:0] disk 500xxxxxx6e9b2d7 /dev/sdb /dev/sg1 [10:0:1:0] disk 500xxxxxx664e6dc /dev/sdc /dev/sg2 However running "fdisk -l" I can see it here: Disk /dev/nvme0n1: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: Samsung SSD 970 EVO 1TB Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x00000000 Device Boot Start End Sectors Size Id Type /dev/nvme0n1p1 64 1953525167 1953525104 931.5G 83 Linux Any ideas on how I can get it to show up? Is there any further information that would be useful to share?