grandprix

The PMS version which has Live TV enabled is Beta, or so is my understanding anyway. How are you guys enabling Beta from within the linuxserver.io docker? I looked at the Github FAQ and it doesn't list beta as a valid version choice. Or is this just conversation regarding the new Live TV function in a general sense of it all?

Yeah, usually I would have added a disk, but, that isn't an option, only upgrading existing ones. Amazon sent them SurePost, sooo, now instead of receving them yesterday (as would've been the case using UPS Ground or heck even USPS Priority), I won't be getting them until Tuesday. I hate packages sitting at the post office, this is what I see happening the longer it sits there:

Oh you know, you're right, I think it may have been BTRFS that I recall seeing maintenance threads on. Either way, I'll definitely give it a go. And thank you, I was just wracking my brain last night trying to remember the name of the plugin/app for moving files around so I wouldn't have to putty in and use MC.

I have and it sounds like an awfully long process, one that once things are running straight again, I had planned to do once the bigger drives come in. I'm weary about doing it, as reiserfs has served me well for 6 years now, never a hitch. xfs though I swear I see threads on it here and there about having to do some sort of maintenance on them.. perhaps that's just a side effect of more people using xfs (aka statistics), but, does concern me just the same. Once the 8TB for this unRAID come in (just 4 atm which unfortunately two have to go to the parities of course) I'm definitely going to give it a whirl though. I'll try nearly anything once (read nearly lol) Thanks for all your help johnnie. I'm not much concerned about rebuilding the docker/image, that's such a breeze to redo since docker authors make things so simple (thanks to the authors).

Yeah. I'd just as this point rather ask, what is the proper 6.3.x -> 6.2.4 reversion instructions? From my understanding I'll just unzip 6.2.4 onto the thumb drive, keeping the "config" (which file or files that is precisely I don't know at the moment off hand) and I'll have to scrap my dockers and redo them from scratch. I never intended to be one of those "everything worked fine before I upgraded" but the facts are simply, they did. This box could stream 7 transcodes and 3 direct streams (Plex) while sab was unzipping and moving a file to the array. Now, 4 streams max it seems and, forget about it if I'm moving files to the array (or sab is). Samba issues (initially), now this issue. Even if the errors were on my end with misconfigurations, that just goes to show 6.2.4 was more forgiving (assuming it was any settings on my end). Just nothing but small issues with 6.3.x and I'm at my limit now. Maybe its my hardware it's not playing nice with, I dunno. But yeah, if I could respectfully ask what I'll have to do to revert (since it doesn't seem to be found in a clear and concise manner in any post that I've been able to search for), I'd like to do that.

Sorry, I'm a hoarder and that includes evidently not closing old paint windows. This is the share settings (the other one was an old paint window I left open).

Oh, its very possible, because it is happening. The last 2TB or so of data written to this unRAID has only been that of the same share. So just look up top to see the configuration for that share, besides for the change you recommended of "Split any directories as needed" which, seems to have nothing to do with high-water, I set it just the same. And instead of just 30GB high-water it is now 80GB (and was upon making the change you recommended). Which seemed moot because it's not even following the "old" high-water of 30GB. Pictures provided of Global Share Settings, Share Settings and of course the menu/disk/whatever proper name is given to that display screen. I know I don't have much room left among my disks (that is soon to change on this unRAID, but not for another two months "soon"), but even still..

Yeah that didn't do the trick. Still, if there is only 92GB of physical space left on the drive, and there are three 8GB files that are soon to be written to the array, regardless if after the second 8GB file will drop the space on a physical drive to less than the high-water, the third or any other subsequent file will be written to that drive until it is empty. unRAID seemed to dither, or spread out the data fine to around 100-140GB free on each drive (200-230GB before that), but once they're down to 100GB, it seems all bets are off and unRAID says "frick it", and will just hammer a single physical drive until it is empty, completely ignoring the high-water.

Could you reiterate for me please. "Automatically split only top level..." is how it's set (keep in mind, I haven't changed the split levels since 4.7 and back then numbers were used, I had the Movies set to level 1, as all movie files were directly on the share (ex. /Movies/Star Trek (1970).mkv ) I -am- aware that "release convention" is /media/Movies/Star Trek (1970)/Star Trek (1970).mkv -- but I had already been in a thousand or two movies in deep before I had been instilled such knowledge. It -appeared- to be working as intended, until recently. When you have a moment johnnie, could you elaborate where my error is/how to resolve it please. Perhaps it was because I would just add a new drive (essentially indirectly forcing unRAID to use that new drive for new media) when I had gotten below 7TB free space in the past that I never experienced this issue?

Not an oddity I suppose and a known situation? I moved data from that disk to two others. Upon adding some data tonight, now disk 1, which was at 130GB free (or somewhere near that), is now at 59GB. Each file has only been 7-8 GB, so, it again ignored the 80GB minimum free space (what it is now, as 30GB wasn't cutting it obviously). Never had this issue, but then again, never ran out of physical hard drives this close to empty before (would normally add more, but, am at my max hard drive per controller ports).

I have pretty much all shares on automatic split handling, besides music which is assigned to use only disk 4 and 8 (I had planned to reduce that to only one drive entirely, but I have many CD's from my brothers DJ'ing days that I owned and ripped to FLAC and they used to be only 2TB drives so, I never did change it). And a minimum space of either 30GB (in case of movies) and 80GB (in case of TV series) required for each share (as shown in the picture). I'm curious, how it filled drive 8 entirely, before spreading out to the other drives with space (each drive is set to use defaults and only one spin up host exists and that too is drives 4 and 8 so that they're both spun up whenever someone is listening to music to avoid long pauses). "HDMovies" share is showing as having 3.98TB of space available, yet, it was a recent addition of several movies (thus the "HDMovies" share) that managed to fill the drive to 0 space. Any and all ideas/clues is greatly appreciated.

I've yet to have an opportunity to "test" the UPS with the setting to "NO". I assume you have the same UPS as me, does yours turn off? If so, may I ask your settings please? TIA bud.

My memory isn't quite what it used to be. It very much sounds like the same issue. Now, did I change the setting to "Yes" in my absent mindedness assuming no settings were changed, whereas it would have obviously qualified as changing a setting (duh if so and my goof), or did it default to "Yes" after upgrade for whatever reason (I'm thinking that isn't likely based on the date of apcuspd but, I don't know what version was being run on 6.2.4 even so, I don't think it would have a need to change the config). Good eye jonathan, thanks buddy. I'll change it to "No" and give it a test, if nothing else but to remind myself/confirm of it's behavior.

Ok. Since 4.7 or whichever version first had apcupsd compatibility with it (the plugin from days old), I've never had an issue with this UPS being turned off by unRAID after it's done its clean shutdown. I know of no other variables aside from the 6.2.4 -> 6.3.3 upgrade I did roughly a month ago, sorry. No cable changes, no nothing. Know, that unRAID will properly shutdown (seems to take longer to unmount drives than 6.2.4 but, that's tolerable and very likely insignificant), but it just refuses to turn off my UPS afterward. I will say, that on the LCD of the UPS, that after unRAID shuts down, it will show a "Schedule" with a picture of a clock/timer, which according to the user manual, suggests that the UPS has been set to a "scheduled shutdown." So, I have to wonder, is the setting in unRAID "Battery level to initiate shutdown" being passed onto the UPS (or any other shutdown criteria)? Because, as it is (and has been) set of performing an unRAID shutdown at 70% battery, the UPS would go from say 60% (right before unRAID is completely shutdown/off) to about 90% battery life, thus, perhaps waiting to hit 70% battery life again? This would conceivably be considered a "schedule shutdown" to the UPS. But those values should only apply to unRAID itself I would think.. I'm speaking aloud here just to get the thought juices flowing perhaps. Anyway. Any and all assistance is greatly appreciated as always. tower-diagnostics-20170514-2232.zip

Right, I was thinking of my 1240v3 box that used to run the Plex docker, that and seeing where I mentioned the 32GB ECC that I used with it. Typing fart. Still, greater than 64GB (288GB). But if VM's aren't what you roll with, nor foresee doing so (the mention of the Windows VM and having dual X5670's I suppose I figured you leaned towards VM's), I wouldn't put it past that 1245v5 running 10 streams. Do what I do, if able. I have 4-5 streaming at any given time on my server it seems. I fired up the PMS docker on the E3-1240v3 (those I share with probably wondered where all the new content was but lolz to be had in a weird sick way temporarily) yesterday to test this. The users didn't fail me. 7 streams at 720p 3MB going out, then I began playing the following (in this order): stream to Android S8, then iPhone 6s (or whatever it is, is my wife's and I'm Apple ignorant for the most part), then cellular iPad, then two Roku's sticks (both set to lowest 1080p MB/s), it didn't start choking a little until I started up a stream to the Roku 4k (was only 1080p material though fwiw), however.. with that said, things seem to roll fine (on my end that I could watch) once the transcoding caught up on the stream going to the 4k. This on a 30M upstream line, and 1 and 10 Gbps LAN (mix).

The clock speeds are negligible, imo. I mean, it comes down to heat/electric or how I would view it. I know a 1240v3 will handle 10 concurrent streams (that's with Plex running in a docker) with a bump here or there, 6 being transcoded streams, I've done it with 32MB ECC RAM, fwiw. So I imagine the 1245v5 would at least do the same. If I could have only one, I would likely choose the Dual X5670 (depending on how many VM's I was interested in running, otherwise the more L2 and > 32MB RAM limit may not be worth the electric/heat), the 1245v5 has AES-Ni thus a higher AES benchmark, which, is nice you're running a VPN (pfSense or otherwise). I think I'd probably hardware hoard them both. <grin> Not a great help I know but.. yeah.

Ok gang. Parity check finished and I just got a moment to breathe a few minutes ago. So I reboot in safe mode, kept watch on the logs, the missing csrf token error did not present itself. So, I figured that told me, a plugin was the culprit. I decided to start bottom up in removing plugins, with the first above the last (unRAID OS) being NerdPack.plg (Nerd Tools). 15 minutes later after removal, no error messages. I don't recall exactly why I ever installed it, for MC I guess? Should I try to reinstall it fresh now? I don't suppose it would hurt, in fact, I'm somewhat interested in knowing if the error would return if I did. One other thing to note. While poking around, I saw in my "go" file that I had a line in there which was cp'ing (copying) a file for smartdb monitor or something or another. The remark before it stated it was a "temporary fix until 6.1.x upgrade", needless to say, now being on 6.3.3, I figured I would remark that line out. But, back to the question regarding the "go" file, so it have -anything- in it? I also noticed it had a line to load up unmenu which, of course, is, well old. Doubtful it has anything to do with unRAID not turning off my UPS after clean shutdown of unRAID, but, that is next on my agenda to figure out. Because I erroneously left it to granted, I do appreciate the assistance.

It is an SMT1500 and on my oscope it's output is a sinewave, it feeds into a CyberPower CP1500PFCLCD

You quoted "issue" in such a manner suggesting "issue" was referring to a possible debate of opinion. Instead "issue" was in reference to unRAID not turning off my UPS as I have it set to do after shutdown. Just FYI. I do understand where you're coming from in regards to the up/down of electric, surge, etc. though. There is good point to it, but, before the CyberPower I have an online APC and a surge protector before it. Still not immune, I know, but, if things get destroyed through all that, then I think some godly wrath has been taken out on my gear.

Rather not. That way when the electric comes back online, the UPS will power up again and the server will come up, hopefully with a clean powerdown (which with the exception of this new issue of the UPS not getting turned off, powerdown's have always been clean). Otherwise, if I'm away from home, I won't have things available to me until I return. That would stink. It's worked for years, not quite sure what the issue is. I'm beginning to think my system simply doesn't care for 6.3.x for whatever stubborn reason(s). Though I'm not willing to give up quite yet (it's tempting, but, not yet).

I'm thinking he did and I have BIOS set to "Last State". unRAID "Turn off UPS after shutdown" is set to YES. No settings have changed with either for a long while, but, after upgrading from 6.2.4, unRAID doesn't turn off my UPS. Now, it IS a CyberPower rather than APC, however, in the past, it's worked fine with APC's API. But parity check still running (of course, will be a few hours). I appreciate the replies.

No sir, I think I may have missed that tucked away within the posts. I've run into another slight issue, having lost electricity (seems to be a trend here lately). And now running a parity check, as it seems, after this upgrade, unraid isn't turning off my UPS after shutdown. So, the battery goes dead in the UPS, then finally shuts off, but, turns on when the power comes back on, thus turning on the unraid in the process. But, one issue at a time I guess. But for now, I'll have to wait for the parity check to finish. I did want to respond though, so you know you weren't being ignored (had to wait to respond also due to the electricity outage sorry mate).

Well, my topic got slightly hijacked. I'm still experiencing these issues and am not quite sure up from down within the thread.

This one supports > 2TB and SATA3, the 846TQ is direct, not an expander like most. http://www.ebay.com/itm/172614516263 Not sure if it's quite the case you're looking for, but, works out fine for my dual E5-2670 with ASRock SSI EEB mobo.

Samba issue is, at this time at least, resolved. In an attempt to try nearly whatever I could. I deleted all users aside from root. Then I ran the permissions script. Now I can click on "Tower" from the Network (workgroup) within Windows Explorer and access it again. Also my mapped drives to "Tower" are working again as well without being prompted for credentials. I don't know the why's or how's precisely, that made this do the trick, but, at least for now, it's working. So I'll take that. Now only the token error remains. Which, while it doesn't seem to affect anything, sure does fill up the log files and besides, being an "error", I would of course rather resolve it. I'll keep digging, trying and listening to advice.