filmjock

Well amigos, I'm almost back to an even better place than where I started! New drive has cleared and been formatted. Having to shuffle around my settings folders a little bit, but for the most part everything is humming along. I can't tell you guys how much I appreciate the assist. I was utterly crushed when I started this process - not knowing how it would all work out. Your eally saved my bacon! Seriously...THANK YOU! Trurl, JorgeB and MrAndyBurns you guys rock!!!!

Diagnostics attached tower-diagnostics-20250506-1402.zip

Ok, so I've built the new system. New CPU, backplane, SAS card, etc Setup a new config, but when I did, it blew out several of the settings in my docker containers. Emby, HomeAssistant and several others basically are acting like fresh installs. The reason I started this whole process was because my data drives were full. I have found a few "good" settings folders on the data drives...drilling down individually, but I've had trouble restoring them in a way that works. I've tried creating new folders and copying the contents of the "good" folders to them using Krusader and the command line, but for some reason the containers come up with corrupted settings. Not sure if it's a permissions issue or what. Also of note, I attempted running the mover previously, but didn't have enough storage on the array to push the entire cache over, so I'm wondering if that also screwed me as well... Would I be smart to use the move tool in the share browser window to move the "good" settings folders back to cache or a new folder entirely? Not sure what the best strategy is? While working on the containers, I'm also running a parity check in the background - which is 60% complete and has corrected 1,033 sync errors so far on a 14TB parity. Once parity check is complete, I will add the new drive to the array and clear it. This will get me an additional 12Tb of space. Any advice on how I can get my Dockers back up with "good" settings would be appreciated. Thanks so much people! Getting There!!! You all really saved my bacon! Really can't thank you enough!

I've got a new system inbound. Will keep you posted on progress. I truly appreciate all the advice so far!

One additional question: What happens to my cache disk? If I do a new config, will it get toasted? if I drop it into a new machine will it get toasted? Is there a smart way to back it up? Thanks so much Mods and Friends!

I'm considering getting a new system with an external facing SAS card and JBOD with individual SATA connectors. From everything I've read a setup similar to this is WAY more optimal than what I've been using. The machine I'm using is a micro form factor dell with no PCI or external SATA connectors combined with a Yottamaster 5 bay enclosure. Am I playing with fire attempting to get this system back up and running when any time I attempt to expand the array could result in potential corruption of my drives? Want to know what you guys think is the smartest play here. When I started with Unraid, this setup seemed like a good start, but I'm rapidly realizing I need more processing power and reliability overall.

No I didn't. It spooked me, nor did I attempt to spin up the array until I felt like I was on a good footing for fear of data loss.

I am concerned about the disk that says it's emulated. Currently in slot disk 2. If I create a new config, will I potentially lose that if it's a corrupted disk? Also - if I move it from the drop down list in the array and put it into UD with read only, will that mean that any emulation is now toast? Also - 1)if I create a new config and nail the disk assignments, will parity need to rebuild or will it just "work"? 2)If the new config works, what happens to docker containers, etc? Will they disappear? 3)What about VMs that I've installed? 4)What happens to my cache drive? It has data on it. Sorry for all the questions. Just trying to go into this with as much information as I can to make this as easy as possible.

I don't know which drive is my parity. I have 3 14s in play for parity and 2nd data (the 3rd 14 is the WD unreliable disk). If I do a new config, wouldn't that essentially wipe my data drives? I hope I'm wrong... Also - I'm seeing an x next to one of the disk assignments showing contents are emulated----how does that come into play? And thanks again for all this. I owe all of you a debt of sincere gratitude!

The original configuration was 3 drives, 12Tb, 14Tb, and parity (14Tb). The problem WD was not part of the array and basically just listed as an unassigned disk device. The drive I was trying to add is not included in anything at this point. I just want to get back where I started and don't want to confuse myself. Would Love additional thoughts on other potential approaches on this.

It's included in the diags that I sent. I had plugged it back into the Yottamaster to try to get things back to where I started.

I'm definitely going to look into a non-USB solution after I get this sorted. Truly appreciate whatever advice you can all give. Diags attached tower-diagnostics-20250422-2000.zip

I was attempting to upgrade my array with a new drive. I have a Yottamaster PS500C3 enclosure. There are 4 drives in play. 1 X 14 TB Parity, 1 12TB Data and 1 14TB Data. There was an unreliable WD Drive (not in array, just in available pool) in the mix as well that has been hooked up to the system, but not part of the arry. For the record, I never got the new drive installed, because when I put it in (and switched with the WD that I thought was bad, everything went to shit). So these drives above are what I originally had installed in the array. Including the bad WD - because I am uncertain whether the "bad" WD drive was what I pulled out or whether it was a drive originally in the array and the "spare" WD is in slot 1 or 2. I have not touched either of those and don't intend to. I have 5 slots. Slots 1,2 have been untouched. The issue arose with slots 3,4,5. I had 2 drives in those two slots. I removed what I thought was the unreliable WD drive. When I placed the new drives in all hell broke loose. Through much shuffleing, trying to get the drives back to their original order, I've managed to put myself in a situation where the raid is now reporting " You may not add new disk(s) and also remove existing disk(s)." I'm seeing 3 of 4 disks. I don't know what's what, because the Yottamaster won't tell me what drive is where. What is my best approach here? The raid will not allow me to start up because it's reporting "Invalid Expansion - You may not add new disk(s) and also remove existing disk(s)." Is my best course of action to create a new config and assign all drives as data and see what comes up? I'm freaking out to say the least. I'm seeing Disk4 as what it WANTS to assign as my parity, but I'm not sure how these Disk #s are derived when using this enclosure. Worried I will accidently toast a data drive because it was assigned as parity. I've moved the lower disks around and am just not confident where things are I'm freaking out here, because drive assignments seem to be F^%$ Thanks in advance to anyone and everyone that can help. I am normally really careful with Unraid and I am just so ashamed I screwed this up so royally. And no - I don't have a backup of my flash drive..Such an IDIOT!