Bigdady92

How? Is that under Advanced settings?

if i remove the folder mapping the docker container won't start. That path for mlyar needs to be populated in the template.

I don't have a mylar db at all, wasn't aware I needed one. I thought this would be a selfcontained docker image with everything.

1. Gotta populate that, understood 2. Getting this fun error now: WARNING 2018-01-04 08:54:38,367 gazee.comicscan.comic_info_parse: Mylar DB is locked or doesn't exist

1. In the default template you set your /comics and your /mylar config. These drive mappings are not carried over when the application starts to automatically populate the Settings>Server>Comic Library Path or Mylar Path. You have to manually go in and set them in the application's WebUI 2. I'm not selecting anything but letting the system use the default which is mapped to my cache/docker/appdata/gazee/mylar I'm not entirely sure it's writing to that dir or to the base image itself.

started using this today found a problem 1. Default directories do not map back: /comics and /mylar do not map in the docker image, you have to go into the app itself after startup to add the config file locations. This will cause any changes you make to be null and void. 2. mylar directory: i changed this once to be /mylar in the application itself but when i restarted the app the changes was not saved and it reverted my user additions and password changes.

Thanks John_M learned something new every day. I'll wait for the update then.

I have 2 10GBT cards installed. All are loading the ixgbe driver on 6.3.5, will start my testing as I'm able to assign IP's and so far we are golden.

Is there anyway to get multiple network interfaces to appear in the stats page? I only see a single interface and want to have all 4 that I currently use displayed. Sorry for not searching this thread it's 75 pages long

Mellanox is still the 10GB with SFP+/GBICs not Ethernet in the RJ45 sense. I have 3 10GBT cards coming and a netgear 10GBT switch, will set it up and see how the magic works with 6.3.5.

also this massively: Connection lost to daemon at 127.0.0.1:58846 reason: Connection was closed cleanly.[INFO ] 21:35:33 client:217 Connecting to daemon at 127.0.0.1:58846..[INFO ] 21:35:33 client:121 Connected to daemon at 127.0.0.1:58846..[INFO ] 21:35:33 client:224 Connection lost to daemon at 127.0.0.1:58846 reason: Connection was closed cleanly.[INFO ] 21:35:34 client:217 Connecting to daemon at 127.0.0.1:58846..[INFO ] 21:35:34 client:121 Connected to daemon at 127.0.0.1:58846..[INFO ] 21:35:34 client:224 Connection lost to daemon at 127.0.0.1:58846 reason: Connection was closed cleanly.[INFO ] 21:35:38 client:217 Connecting to daemon at 127.0.0.1:58846..[INFO ] 21:35:38 client:121 Connected to daemon at 127.0.0.1:58846..[INFO ] 21:35:38 client:224 Connection lost to daemon at 127.0.0.1:58846 reason: Connection was closed cleanly.[INFO ] 21:35:38 client:217 Connecting to daemon at 127.0.0.1:58846..[INFO ] 21:35:38 client:121 Connected to daemon at 127.0.0.1:58846..[INFO ] 21:35:38 client:224 Connection lost to daemon at 127.0.0.1:58846 reason: Connection was closed cleanly.[INFO ] 21:35:43 client:217 Connecting to daemon at 127.0.0.1:58846..[INFO ] 21:35:43 client:121 Connected to daemon at 127.0.0.1:58846..

I've been getting this error constantly and my deluge container is crashing repeatedly. I get errors all the time with connecting and torrent downloads. Any ideas? kernel: deluged[20403]: segfault at 2b29722f5000 ip 00002b2979713ba7 sp 00002b29722f4118 error 6 in libtorrent-rasterbar.so.8.0.0[2b29795bb000+46f000]

How stable is 6.4 RC? I have a 10GBT switch and interested in these cards.

The network chip used is the AQC 107 from Aquantia

Anyone have any idea on these cards if they are supported in the latest 6.2 kernel? Any PCI-Express 10gbT cards work in the latest Released version of Unraid No i don't want to use mellanox, I have a 10GbT switch that I want to use RJ45 cables to.

Run from these drives. They are HOT and stay hot. You creep past any of the internal temps for any amount of time and your drive will fail on you. I RMA'd 5 of them recently and the RMA process is a nightmare. You dont' get new drives, you get Gift Cards and you MUST have your receipt.

I've never heard of simplefeature and I've cleared dozens of disks without having the array starting. Make sure you have all the required dependencies for preclear. Update to the latest version of applicable and worse comes to worse reboot your unraid system gracefully.

I owe you a beer/coffee/gluten free water. That's the one thing I did not do and rebooting my router fixed the issue.

*eats my hat* So after much digging around I've come down to "It's a network issue". I've rolled back to 6.2.4 to see what went south and for the life of me I cannot ping ANYTHING outside of my local network from Unraid. I have the default route set properly. I've done DHCP from static. I've booted into safe mode to see if it's a plugin issue. It's not. I can connect to the system from another PC via SSH. I can connect from my phone to it over wireless. The system, for whatever reason, has no clue what to do when it tries to go out. My firewall does not show the system being blocked, it's on the same DHCP pool as other systems which are going out to the internet, i can connect over SMB. The default route is corrrect, tried adding that manually. I've swapped cables, I've swapped interfaces. Tried to use bond's. I've plugged this system straight into the back of the router bypassing my switch. I'm stumped why after the upgrade my network stack just went to crap. I have another 6.3.0 system that works like a champ, mostly. For further giggles I tested from my firewall to 8.8.8.8. traceroute and ping tests. No issues no problem. Ping to the UnRAID system from the firewall? Pings fine. Normally I would diagnose a routing issue but the route is correct ironduke-diagnostics-20170206-1329.zip

I've got this exact same problem. What would cause this error to appear? This error message is causing all my docker and plugin updates to fail yet I can get to github.com without a problem on my PC. Usually Going to network settings, and making sure the default gateway points to your router and setting static DNS addresses of 8.8.8.8 and 8.8.4.4 will fix you up I set google's DNS to be my 2nd/3rd DNS left my router as 1st when I thought that was the problem. I'll revise the order and see if that helps. I'll be mega irritated if it's that simple.

I've got this exact same problem. What would cause this error to appear? This error message is causing all my docker and plugin updates to fail yet I can get to github.com without a problem on my PC.

Looks like the reference to your fan controller has changed, maybe you updated unRAID? Easiest would be to select your appropriate PWM controller (may need to test which one works) and do a new detection of the PWM fan. updated to 6.3.0. Updated all my plugins. I am hit 'detect' and I see all 10 different pwm modules. I've tried all of them and they still error out. Do I need to blow away any of the files and reload them?

I scream at 75MB/s replicating primary to secondary raid array as well as pulling in 10MB/s from the internet on torrents. With my managed network switch and firewall I see minimal traffic when trying to pull in data from the internet. Networking is not an issue. Is there a way to download/downgrade to 6.2.4 for now? I don't see the download link anywhere.

Upgraded from 6.2.4 to 6.3 Network shares work like a champ but I'm having problems with Docker and Plugins 1. I see at the console "ping Unable to contact github.com" not sure why that is. 2. The statistics plugin for pulling diagnostic information using tor/anonymous stats did not upgrade cleanly, uninstalled that. 3. I see nothing but "upgrade available" for all my docker images and when I try to update to the latest images I see the gray box at the top right notification pane but I never see the docker images upgrading in the log. This is causing plex to not work fully but my other docker images are working OK. 4. When scanning plugins the notification pane appears but it takes 7-10min to scan 15 plugins. This is not normal at all. Why did my unraid go from being lightning fast to running like a pig in the mud. I'm tempted to go back to 6.2.4 at this rate as i uinstalled a ton of plugins that were not critical but still the problem persists. I did not start in "Safe Mode" yet, I'll try that tonite.

Looks like the reference to your fan controller has changed, maybe you updated unRAID? Easiest would be to select your appropriate PWM controller (may need to test which one works) and do a new detection of the PWM fan. I havent updated unraid to 6.3 yet but i am today. I moved the boot drive to a new server with vastly different specs so that may be it. I thought unraid would clear everything out on a new config install.