crashman79

About 10 hours ago, my ls.io ombi docker went into a loop and is not able to keep running. Working beautifully up until that point. I've tried removing the docker and deleting the image, and reinstalling from CA, same result. Log output below. https://pastebin.com/NQt8avHp

Loving the steamcache docker! I discovered I can add the variables to the steamcache-dns docker to enable the Blizzard stuff, etc, but don't have the necessary knowledge to pull the steamcache / generic stuff into unraid to make that a seperate docker. Of course, the existing steamcache docker just passes through requests that the dns redirects to it for non-Steam downloads (yellow text when I tested with Hearthstone download). Any plans to make an unraid template for the steamcache/generic cache? Or possibly some hints on how to do my own? Edit: Disregard. Used the CA option to enable Dockerhub and installed it from there, using the path variable example from your steamcache docker template. Changed the steamcache container and the converted steamcache-generic container to use different IP addresses than unRaid's (linked here), so I could run both, and just pointed the steamcache and the 'generic' cache seperately in steamcache-dns. whew! http://prntscr.com/hfbjaa http://prntscr.com/hfbjsd

Much appreciated. This did indeed fix my issue. I did think it was strange that the way 6.1.9 'saw' the name of a drive vs 6.2 was odd, but never thought that would be the problem. I feel silly now, having searched off and on for the past several days before I broke down and asked in the forum, when it's in a sticky post here. I was too focused on the forum search and Google searches, and not even looking at the stickies in the forum where I asked for help.. Thanks again!

Hi all, I've searched and searched to no avail. I have a strange issue with Unraid 6.2 (stable). I've been using 6.1.9 for some time, I've tried the 6.2 beta(s) but I keep going back to 6.1.9 for one reason or another. I honestly can't recall the old reasons, but this latest one bothers me. I'm finally ready (and probably need) dual-parity for drive failure protection, and in the process I'm upgrading my 3TB WD Reds to 4TB HP SAS drives. The thought was that I'd switch to the 4TB drives, shrink the array and switch one to another parity drive. I replaced the parity drive with a 4TB drive first, of course, took a few days, then started moving onto the data drives. I've only gotten 3 total drives migrated over (2 data 1 parity) when I tried to update to 6.2 I'm fairly sure the problem is something in 6.2 vs 6.1.9 and not the drives, the hardware, etc. I did try clearing my flash drive off, except for the key file, but ran into the same issue with a clean start to the configuration. When I try to assign one of the 4TB SAS drives, the appear in the dropdown in unraid, but once selected the webui simply reloads. The drive is no longer selected, there's nothing in the syslog of any note to me. I've tried multiple (4TB HP SAS) drives in different hotswap slots without any change to the behavior of the dropdowns in unraid. Any help, ideas?