johnny121b

Thanks, johnnie.black! I'll give that a try this evening. J

I have a second, licensed USB drive, and I would like to Shut down my running 6.3.5 server Copy my flash drive config to my second (freshly formatted 6.5.3) flash drive Swap the two flash drives Start up my (now) 6.5.3 server IS it as-simple-as copying my config folder from my existing flash drive to my new flash drive and starting from it?

bonienl is correct. I have seen Linux can start up consistently ordering USB ports (and network ports for that matter) 99% of the time, and then one day, it wakes up and decides to shuffle ports- for no discernible reason. It can be maddening. (Not actually speaking of Slackware- but I've experienced it in my work environment)

I have a white-label drive I'm thinking of adding into my system as second parity. (I can't bring myself to trust the drive despite its passing a preclear.) My question: If one parity drives fails, is the array left unprotected OR does my level of protection decrease to allow for only one drive failure?

Well that's a bit of bad news. Those controllers are Pci-X, so you're really saying- 'replace your entire server'

At my age, my head doesn't wrap around abstraction as well as it once did. Hard to believe I could once write code in assembly. Adding to BinHex's response, here's a shot of an example show in Sonarr. If you're like me, you're overthinking the paths. Even now, i look at BinHex's reply, and I struggle with the logic in USING abstract paths- IF everything has to be the same anyways. I -SO- want to specify absolutes....complete absolutes...from every application. But times change, and we all have to adapt. I blurred out some details on the page, but I think you'll get the idea. (I was once scolded for including too much detail, but now I only record public domain shows.) The second shot, is the path configuration for NZBGet. Its paths are unchanged from the docker defaults. Not sure if this all helps, but hopefully it might.

I'll take some screenshots later today. I'm about to head to work. I understand your frustration. The added layer of abstraction when dealing with dockers absolutely drove me crazy.. so-much-so, that when I finally got it running, I squirreled away screenshots of everything- because despite the fact that I had it running, I still didn't fully UNDERSTAND why it worked..so I knew I couldn't fix it when it broke. (unfortunately for you, I'm not sure where those screenshots are at-the-moment, because it's been so long ago.) What are you working with besides PLEX? NZBGet/Sabnzbd/? Sonarr/Sickbeard/?

My movies are largely in a single folder in my 'movie' share. Some of the more important titles merit their own subdirectory (for special features mostly), but 99% of them are tossed into the movie share. My TV shows are in my 'tv' share, but each series [does] have its own subdirectory. I don't do season folders. For me, that just added too much to the path length in the occasional series. (Windows doesn't handle path lengths over 255-characters) When PLEX does its scanning, it doesn't care whether the movie is in \movie or in \movie\Raiders of the Lost Ark.

I don't know if I'm a good example to follow. Someone may-well pop up and tell me I have something incorrectly configured, BUT the setup shown, works smoothly for my docker trio- PLEX, Sonarr & NZBGet under 6.35. The trick (for me) was to use dockers from the same author- makes life much simpler.

Put your server into the same area as your water heater, and replace your water heater (if necessary) with the heat-pump variety- a symbiotic relationship.

I've never had problems with SanDisk or Lexar sticks. As some have hinted at, mechanical damage is a significant consideration long-term. I use only sticks with minimal protrusion- a 0.25" drive will probably be protected by the normal recesses of your machine, while a 2" long stick just begs to be broken off by the accidental bump, a drop, or a cable snag.

When updating PLEX, is it best to Update the docker or Update PLEX from within the WebUI ??

"There was an unexpected error loading the dashboard" This is how it's starting up today- It HAD been loading correctly, so it's obviously taken a step backwards. My situation: New install. Public PLEX version. Binhex docker on Unraid 6.35 system. System doesn't seem to be updating the libraries as episodes are added, though it did spend a few days doing nothing but scanning/updating the libraries...just no sign of episodes added to my server in the last few days. Search function sporadically works. Seldom loads the seasons once you select a series. Nothing looks wrong or presents any sort of outward appearance of malfunction- but PLEX just seems brain-dead. I've stopped and restarted the docker. Really need some direction- I know almost nothing about dockers. UPDATE 10/31: Eventual resolution: I deleted and reinstalled the docker. I'm guessing the container became filled with logs, but I didn't know how to tell.

IS the wiki up-to-date?

Yup, I know. And it's precisely all the 'working thru issues' that made me decide to ask the question. I'd rather know now, than find-out on release day. Don't wanna become a victim of my own enthusiasm.

Are there any caveats for upgrading from 5.06 to 6.1? (I wasn't comfortable upgrading to a version ending in [glow=red,2,300].0[/glow] .....but I will be taking the plunge in upgrading to 6[glow=red,2,300].1[/glow]) Or are the 6.0 instructions still valid as-is? (My plan: store my existing flash drive and format/use a secondary (also-licensed) flash drive, copying over only the relevant config settings per the wiki instructions)

I looked into tape drives but couldn't justify the enormous initial cost PLUS the creation of a single point of failure. If the uber-expensive tape drive FAILS or is damaged by the same circumstance that creates the need for restoration (thinking lightning, fire, theft, server falling face-first onto the floor....etc.), you have no way to restore anything. All that, for me, equals a big "NOPE" for tape drive$$$ External hard drives' prices are typically lower than internal drives. And while I detest their slimming warranties and mysterious/unknown internals, that fear is balanced out by the realization that they don't have to perform 24/7. They only need to work during backups and during the restore, and I handle them like dynamite, in hopes they will be there if/when I need them.

Is it only me that's concerned that the whole 'helium-filled' concept isn't a viable long-term construction method? I worry these drives won't be sealed well enough to contain helium for years. Granted, I'm basing that on science knowledge that's decades old, but I [do] know it's at the top of the periodic chart. And I know I've seen a lot of fogged windows in my day- all of which, started out life sealed with a warranty a LOT longer than any hard drive's. Am I the only one whose OCD snags on that suspicion?