_0m0t3ur

Oh, my. I feel so deceived, since my gut feeling has always been that @Squid is 25. But despite this, and me being late to this amazing party, HAPPY BIRTHDAY, Squid!!

Servers are no small chunk of change; $$ add up quick. Glad to hear you've got a starting point. I just ordered this motherboard/RAM as a combo, minus the cpu, which was also a good deal. A friend is lending me an i3-9100 to try out for a week. If that works out for my needs, then I'll grab one. They're very affordable. If not, then I'll look at talking with this seller or Provantage, depending on the cpu I'm after.

Curious, how did this work out for you? I picked up the motherboard/RAM as a combo. Very eager to switch out my current setup for this.

Using 6.8.3.

Today, I updated dynamix pluggins (sleep, trim, system info). Directly afterward, unassigned devices were not visible on the main tab. And I received this error when trying to stop the array: emhttpd: error: cmdStop: missing csrf_token Figuring it was a problem with one of the three plugins causing a conflict after update, I decided to begin uninstalling these three plugins. Since my server never sleeps, I don't need the sleep plugin, so I uninstalled it first. My unassigned devices immediately showed on the "Main" tab. Additionally, I was able to stop the array. My server seems to be functioning normally. Please let me know if you have any questions.

What about making a guide and posting it here: //home/community/guides/docker containers (https://forums.unraid.net/forum/71-docker-containers/)

Updated 6.8.2 to 6.8.3. No problems. Thank you to the unRAID team for continued development and support. Update: since the update, when making a ~80GB file transfer between a unassigned USB drive (mac os extended journaled) and another XFS unassigned drive using Krusader, Krusader stalled and Unassigned Devices became unresponsive. I attempted to cleanly stop the array from the command line but was ultimately unsuccessful, because the problem was related to a kernel error. Prior to the update, I've had success with Krusader. To resolve, ultimately I had to do a hardware force shutdown.

Perhaps this git will be of some help. Look at the second to last comment. https://github.com/nextcloud/server/issues/15299

The first post of this thread offers an easy way to update Nextcloud by command line. I've resorted to only updating via command line ever since problems started (within the last few months or so) with updating via the GUI updater.

I had a little time waiting for some background code processing so decided to read your rather lengthy post. You have some good ideas here. Probably would help to give the Cliff Notes version at the beginning of the post in succinct, numbered points to capture more readers.

The Nextcloud webui updater was giving me grief. So, I updated via the command line using the guide from post #1 of this thread; it worked perfectly. I'm going to use the command line moving forward.

I agree with you that "docker groups" would be helpful. To help improve overall viewing and function right now, I list my dockers in order of dependencies, the order I need to start the dockers to avoid conflicts and errors. But it is definitely not the same as actual docker groups.

You're correct. I'm not really sure how many other unRAID users already do what you and I do, manually alphabetizing content. Prior to posting this feature request, I searched for "alphabetize" and derivations but didn't quite find what I was thinking about, so I posted this. Setting up to manually alphabetize is fairly straight forward, BUT maintaining it is a fair amount of work. The real value for me with alphabetizing some content is that I know what disk contains content that starts with any specific letter. For normal day-to-day, it doesn't really matter, but when there have been problems, I just go directly the correct disk without much thought because everything is well organized. And for backups, it's a real dream to simply replace data at very granular levels with ease. So, being able to set this up at the share level would be very nice. And as you stated, since "split-level" takes priority over allocation method, this might be achieved easier with an extension of the current "Split-Level: Manual" setting. Thanks again for all your feedback. I might just, in the interim, look at following in your stead by automating some stuff with scripts.

I've basically been doing this, minus the folder named "A", etc. So, I create the folder "Arrow" in the TV shows share on disk 1, using Krusader, then all the season folders and episodes of each season are placed in the "Arrow" folder on disk 1. BUT this is a lot of manual work. As a share setting, I envision an allocation option "Alphabetize". Then in the "included disks" section of the share, a drop down menu next to each disk allows for choosing the desired letter of the alphabet for that particular disk. Thus all items for that share that start with letter "A" would be placed on the disk corresponding to the choices set up in the share settings, eliminating routine user intervention. Essentially, this could become an extension of the "Manual" split level, called "Manual: Alphabetize". And since this is applied at the share level, some shares could be alphabetized by disk and others could be set to a non-manual split-level, thus not alphabetized. And as you pointed out, this would work because split-level takes priority over allocation method.

Gottcha! That makes sense. With your method, you still need to create the folders in "A" for each specific show, such as "Arrow", so that all the episodes of Arrow, show up there? Or is unRAID automatically putting all the "A" shows in the "A" folder on disk 1? Because, by alphabetize, I'm looking for unRAID to create the "Arrow" folder for the share TV shows on disk 1. Or if we're talking about movies, I would like the share settings to allow for unRAID to put all the movies that start with the letter "A" on disk 1, the movies that start with the letter "B" on disk 2, etc., without my intervention.

Thanks for sharing. As you have stated, I also believe having alphabetized content would simplify backups, and more importantly finding the specific backups in the event a restore of "TV show X" or "movie Y" is needed. So, to help me be clear about this, you're saying that if I want disk 1 to hold "letter A" TV shows, I should create a top level folder named "A" on disk 1. Since this "A" folder is top level, does unRAID treat this folder as a share?

Share - Allocation Method: Alphabetically 1. For share "X", having the option to choose "alphabetical" share allocation. 2. For share "X", then being able to choose the alpha for each disk. OR Share - Split-Level: Manual-Alphabetize (an extension of the current "Split-Level: Manual") 1. For share "X", having the option to choose split-level "Manual: Alphabetize". 2. Then under "Included Disks", choose the included disks for share "X" and a drop down menu next to each included disk to set the letter for alphabetizing share content. I envision this giving the ability to designate what share content goes to each disk by its alpha/numeric name. So, if it was desirable to have some content alphabetized, such as movies, then this could be achieved across multiple disks in a user defined way. Example: D1: symbols/numbers D2: A D3: B, C D4: E, F, G D5: H, I, J, K, L, M D6: N D7: O D8: P, Q, R, S, T, U, V D9: W, X, Y, Z

Updated from 6.8.1 to 6.8.2. No issues. Thank you for another hassle free unRAID experience.

A fairly large array using shucked drives.

Curious what the timeline is for moving this docker from v2 to v3?

Ran CHKDSK but no errors. So ran FirstAid in Mac OS and it scanned and fixed the file system. Unraid back up and running on 6.7.2. Thanks for your help.

I updated all dockers and plugins. Ran the Update Assistant for added verification. Got the all clear. Attempted to update but got this error: I have not rebooted. Unraid still shows the option to Upgrade to 6.8.0. Unraid is attempting to start services. The logs show scrolling errors:

Another NZBHydra2 update came through. Deleted existing docker. Deleted appdata. Cleared browser cache. Reinstalled. Reconfigured. Working fine.

I just updated binhex-NZBHydra2 to the latest. Now no access to the webui and other dockers cannot communicate with binhex-NZBHydra2. The binhex-NZBHydra2 docker log shows failed database migration and "Migration V1.21__LINK_SEARCHENTITY_TO_INDEXERSEARCHENTITY.sql failed". Anyone else having any issues after upgrade?

First off, thank you! Read the FAQ, and the execution of the pre-clear, while CL, seems very straight forward. I've installed and will give this a try with some used disks I picked up recently.