grandprix

To add, interestingly enough, as of last evening/this morning, all dockers were up to date. PlexPy, Radarr, Sonarr, Plex and Sabnzbd had updates ready upon checking just a moment ago. So in case it does matter, when looking at the updated diagnostics I provided above, know that I have updated them just this moment. They're all linuxserver's dockers fwiw.

Thank you for your reply, I had a honey-do list to take care of today, else I would have replied much sooner. #1, #4 - Perhaps. I only use the cache drive for dockers, fwiw. #3 - This may be, I'll search for the forums for sure. Hopefully not the port, but if anything the thumb drive. I mean it's possible, it's been in use now for, well, 4-5 years? Just to recap: I upgraded to 6.3.3 from 6.2.4 roughly a week ago I guess it was. Rebooted server, all was well with the world. Then the electricity went out a day (or two now?), I suspect it did a clean shutdown (UPS), as it had turned off. Had my son power up the server, things seemed well, but upon my return I noticed all mapped drives on my Win7 machine weren't able to reconnect and I cannot even browse to "tower" without Win7 wanting credentials. Upon looking in the logs to see if there may have been a clue as to why this was happening, I noticed the token error every minute. I provided a diagnostics (second post) after I noticed all this happening and made my OP. I did not yet provide a diagnostics after the "not enough space" errors though, I honestly, plum forgot, my bad. Which plugin I am not running Margarita / controlR (not even sure what the latter is, though I assume another Android/Iphone based app? if so, then indeed, neither are being run, at least not to my authority and knowledge). Just myself, my wife and two children. I'm the only one with access to the server (authorized anyway) directly, the wife and children only via Plex to their Roku's (PMS is docker on this unraid box). I can only say, on my end, it displays as all plugins (and dockers) as being up to date. Well at least as of this morning, I admit, I just got home and haven't checked again, though I plan on doing that immediately following this reply for sure. I am attaching an up to this minute diagnostics. I only edited disk.cfg and flash.cfg to mask the usernames (though keeping a consistent masking convention throughout). I want to thank everyone participating in this thread offering assistance, if there is anything else I can do/try, offer, etc. please dont hesitate. Seriously! tower-diagnostics-20170422-1932.zip

Right then. Questioning 6.3.3 stability. In either case, I have an unraid that can barely be used. Downgrading to 6.2.4 would require I rewrite/redo dockers (assuming information from the forum post is valid). So, that sounds like even more fun. 1. Samba broken 2. token error every minute 3. Parity started for no apparent reason after what I have to assume was a proper shutdown 4. Now this error below I've got over 4TB of total free space. The HDMovies share is highwater set, 30GB minimum space and the data drives all have 180GB+ free space on them (majority of them are 250GB+). No idea why it believes I have no space left?

That wasn't to be read as sarcasm bud, I was legitimately asking if the diagnostics ZIP show up and can be downloaded, as I'm unsure if the new forums shows the number of times an attachment is download like the old ones did (if it does, then it doesnt indicate it was downloaded, leading me to believe that maybe it's not showing up?). Sorry if it came across that way, definitely wasn't my intent.

I've attached them in the second post, are they not accessible? The only thing I did was mask usernames, however if a user name of "johnnyboy" existed, I made it a consistent "j-------y" in only two files where user names existed.

I only ever have unraid on one computer's browser, ever. It's been closed, rebooted (three times), etc. (in an attempt to rid a stale connection as well as try to fix this Samba issue -- such as the registry IsBrowser entry thus rebooting after making that addition). Still, just keeps giving that error every minute. <shrug> Maybe something more telling is in the dianostics? I admit, I don't know how to read them nearly as thoroughly as others here. I still have no idea why the server decided to do a parity check. How can one tell if a clean shutdown actually happened if the logs before the shutdown are overwritten? Or aren't they anymore? I'm at you guys' mercy, will provide whatever I can and will gladly try whatever I can.

All plugins are up to date according to GUI. I mentioned that initially, so I'm guessing that is why no replies? In either case, I can be patient about it (for now heh), otherwise it's a rollback for me. Not the safe way to correct an issue that is susceptible to an invulnerability of course, but, between that error populating my log, the still unexplained parity check and a lack of Samba browsing of this unraid using my Win7 machine (most problems seem to concern Win10) -- I may have little choice in the matter. I'm not sure which plugin cmdStatus is, if it is even a plugin? I appreciate the reply, any other ideas? As I'm clueless where to go from here.

In regards to the Samba issue (where my Win 7 cannot browse the unraid as guest), I've done the following in accordance with threads I read: Installed the Local Master Browser plugin as well. Also installed the Common Fixes (just in case it would tell me something that would point me in the direction of either the Samba or that error message issues I'm experiencing). Vulnerabilities or not, I'm nearly ready to roll back to 6.2.4 (likely would have by now if I could find a thread on it -- but then I'm faced with possible dockers/plugins that were updated that may only work with something special in 6.3.3), however naturally, forward progress is what anyone should be after and it seems counter-productive to roll back. Unless of course its the only option to get rid of an error that didn't exist in 6.2.4 not to mention a broken Samba. Anyone with leads? I know it's only been a few hours, so I'll make an attempt at better patience, but did want to update the thread with what I've done thus far. I'm -trying- to help myself, but it's not helping lol.

Decided to browse a little more as well as try to diagnose things (or at least be in a position to provide more information for this thread). I've stopped my dockers I run one by one, to see if one of them were the culprit (until none were started/running), no change, same error each minute (on the minute + :01 seconds). I did see under Settings -> Notification Settings, that Pushover was enabled (not sure why, never knowingly used it). However, I cannot seem to disable it without having first entered a user key and app token (it was the "token" that caught my eye). I entered some gibberish for both so that I was able to "Apply" the "disable" change. The error still persists. I'll just sit back now and not try anything that doesn't come recommended, as to not make matters possibly worse and to keep from bumping my thread (which isnt my intent).

Ok, two files within the diagnostics have user names. I've masked them and here is the diagnostics file. Thank you to any/all that assist. tower-diagnostics-20170421-0029.zip

I searched for this error, finding only one thread. I followed any applicable advice on that thread, but that OP's issue turned out to be the use of Margarita (I believe it was, as I have no idea -what- it is), which I do not use (don't own a Mac nor never heard of that software). I recently upgraded to 6.3.3 from a 6.2.x (if I remember correctly, wish I could revert to old logs but they're still being overwritten with every reboot by the looks of it), roughly 6 days ago. Last night I experience my first electricity outage since that upgrade. I was away from home, but my son was not. He called to report the electricity was back on, I gave him the go ahead to turn on the server and all seemed well, until an hour or so later when my server emailed me (I was still away from home) that it was running a parity check. Upon returning home later that evening, I encountered "cmdStatus: missing csrf_token" errors nearly every minute. Also, I seemed to have lost the ability to navigate to "tower" in windows explorer, clicking on it requires credentials. All folders should be nobody:users and I never had to enter credentials before (accept way back in the day when all my shares weren't public). I'd like to post a diagnostics, but, in a quick browse, it had things such as my user names, which are first names of family members.. call me paranoid, but I'd rather omit them, so I'll go through all files in the diagnostics ZIP, mask the "sensitive" data, then will post it. Until then please know, I have ensured all plugins are up to date, all dockers are up to date and I'm not running any VM's. dynamix.plg does not exist in the /boot/config (or wherever the thread I found while searching said it was precisely). TL;DR 1. Upgraded from 6.2.x to 6.3.3 roughly 6 days ago 2. Experienced first electrical outage last night (it seemed to shutdown properly, UPS turned off after as should) 3. Turned on, then it decided to run a parity check and I seemed to have lost access to server via samba (Windows explorer) without having to enter non-existent credentials 4. cmdStatus: missing csrf_token error is populating logs each minute 5. All plugins and dockers are up to date, dynamix.plg does not exist in /boot/config/plugins Thank you in advance. P.S. Performing a manual "Shutdown" (where it seems manually stopping the array first is no longer necessary) takes roughly three times longer than the method I took in previous years of manually stopping the array, then shutting down, fwiw.

http://www.ebay.com/itm/201882843766 The above link for reference. I'll be transplanting a server from a Norco 4224 to a "TAMS Server", which is already en route, but I'd like to place the order for the forward breakout cable in an effort to get them in before or on the day the server/case arrives. However, I'm not certain what length I'll need. Anyone (and there appear to be many) that could clue me in on what length 8087 -> SATA forward breakout to get, or even a link, I would definitely appreciate it. TIA!

The default theme leaves little to be desired. Just as mentioned above, there is far too much "whitespace" (whoever made the push a few years back in the marketing realm suggesting "whitespace" is good should be shot, multiple times over). Maybe its a color blind thing (the white washes out any possibly distinguishable color perception), not sure. It just plain hurts these eyes. I prefer "dark" themes, personally. Dark, compact, etc.

Many thanks! So very many thanks.

Anxiously but patiently keeping my eyes peeled for this to change. Thank you for what you do. obideuce: Because I have only elementary knowledge of Dockers, I'm not sure if this would work in the meantime or not.. much less how to apply it (I've grown reliant on docker containers being built for me, bad I know but..): https://github.com/rogueosb/docker-ombi

Yes, or can send email directly to me: [email protected] Roger that. It was your email address that the invoice for the second-key originated, thus the one I replied to. I sent a second email just in case and I'll exercise patience. Appreciate the reply.

*Nevermind, ninja add or I simply didn't see the attachment before.

A failing PSU can do this as well, actually a number of hardware components (obviously), though, not sure if you did the PSU conversion on the SuperMicro or if you're still running the redundant stock PSU's.

This seemed to be the place to post. For those of us whom had purchased the "unRAID Server Second-Key" back in the day (mine specifically was Feb. 2014) who are just now finally getting around to utilizing it (bigger hard drives in an already 24 bay case post-pone this build), is the process of replying to the email that was generated with our Flash GUID still correct? It's only been 11 hours that I replied to the email as instructed (but again back in 2014) with my Flash GUID and currently I am not exceeding any device limitation, however, I'd like to. I haven't received a bounce back, nor is Tom's email address going to spam (as that was the email addressed used back then). So this isn't a "hey its been a whole 11 hours, get movin'!" type of email, rather, just asking for confirmation if replying to the email is the process one should take still. Again, for those that purchased the "second-key" back in the day. Nothing more nothing less. TIA!

Good stuff John, thank you very much. I too do a monthly parity check and it is non-correcting. It's good to hear that I haven't been doing it wrong all these years. I've only once (knock on wood) had errors on the parity and it was a breakout cable gone awry. Then I'll just plan to do a 1st of the month parity check, then immediately assign the 2nd parity to the array then. Just to be extra safe/anal. Appreciate the response.

I've tried desperately to search using the forum search feature, Google with "unraid" as keyword, using the wiki, etc. and still I cannot find "procedures" on adding a second parity (likely just stopping array, assigning the drive, then viola)... but. Should a parity check be performed first? If so, a correcting one? (oddly enough in my search for an answer I found a post from Tom that implied if not explicitly stated we should be doing correcting parity checks -- so I may have been doing things wrong all these years however, that's another topic I think) Also, what can we expect when a 2nd parity is added? Will it be like adding an initial parity drive/data drive that is simply built from the ground up or?

Might also be worth mentioning that recent versions of unRAID do NOT take the array offline to clear a disk. If you add a data disk to a new slot in an array that already has parity, it must be clear so parity will remain valid. It used to be that unRAID would take the array offline for this, so preclearing was invented. People still use preclear to test disks, but the clearing part isn't strictly necessary anymore, and in any case, a new data slot in a parity array is the only scenario that requires a clear disk. Yeah, these hard drives will be replacing the remaining three 2TB drives in this particular unRAID. So the purpose of pre-clearing is for testing for sure. @Frank I appreciate the links. I used to know how to do it inside and out, but, had gotten, erm, accustomed (dare I say lazy lol) to using the Plugin. *Edited: Also trurl, thank you for that. I thought I had screen on before, but, evidently (and clearly) not. Not sure I would've looked at the settings had you not mentioned it, so I thank you.

Frank, thank you, I'll begin looking into that. I don't mind CLI at all, thankfully and it's nice to know it's still an option, modifications or not. I have the Nerd Pack plugin, have had it, yet, upon telnetting and issuing "screen" nadda. So I may need to find where it is specifically. I appreciate the response bud.

Tried with ie edge, ie 11, firefox and chrome. None works. Any ideas? i have same problem and the plugin is up to date 2016.12.24 up-to-date any ideas or help i have waited for a hour and still just stays at starting... thanks ps. i uninstalled the plugin and then download directly from github in case i was missing any dependencies and same story just sits starting I too am experiencing this issue. Unfortunately, I cannot provide any meaningful logs, as there isn't anything about it in them that I have found. Have four drives to pre-clear. Are there any recommendations on how I can get this done outside of the plugin (it was recommended awhile ago in a thread that anyone on v6 should use the plugin vice the script)? Or a possible roll-back or such (I suspect the preferred resolution is to whack the bug, but figured I'd ask never-the-less). Thank you.

*Edited: Actually seems I have a backplane/controller port that is shot. So my initial post regarding a strictly pre-clear failure is on hold to say the least. Darnit. Bad day gone worse. I've included a small log of what I'm looking at thus far. If it's not at all pre-clear related (which this drive not being shown in the main menu is leading me to believe), let me know and I'll not post anything further regarding pre-clear itself with these new drives. kik.txt