Weatherby

Does anyone know which file I need to edit to make the 70-kohya install pull a branch other than main? Main is way behind, I need to train flux and it has yet to be merged into the main branch. So I need to switch to sd3-flux.1 branch. But where is this file and how to change it to pull that?

Hi all. How are you all setting up things like Kohya with this container? I mean as far as storage locations? My cache drive is only 1tb so having AI models and or even the outputs on it is not going to work.. The last time I tried to configure an array drive instead, I kept getting errors about system incorrect configurations... Any thoughts?

That's the problem: THe drive is not detected at all. It's connected. 9 was removed months ago. I started trying to remove it from the array, and set it to unassigned, but it always showed up as unassigned. Drive 2 is the one that just 'disappeared' from the system on me. It's connected to the unraid box for that diagnostic, it's even spinning. I tried an external caddy via usb, no luck even on a windows box. It spins up but no data connection is made.

Ok, here's the diagnostic zip from the unraid server with the bad drive attached. diagnostics-20241114-1628.zip

Thanks!!

Oh, one other thing: SHOULD I be able to get the bad 10tb drive to register to where I can pull data off, is there any specific things I need to do to clone it to a other 10tb drive to salvage the data? Or will any clone software do the trick? (I've never tried it with unraid)

Ok, ill power up the server when I get off work and pull the diagnostics. Also, tha k you for the parity explanation. I guess I was thinking traditional raid with parity.

I was just thinking, and I know what you said, but hypothetically: If I put in a new 10tb hdd and removed the 1tb drive then re-sync parity, worst that would happen is id still loose both disks data...but best might be to recover some of the 10tb feom parity to the new hdd? Either way, I need a new 10tb drive.

Ok, so, unless i can recover data off the 10tb that doesn't register, I'm looking at data loss, correct? But if I could recover that data and clone it to a new hdd, the parity check would restore?

Of course not. 😮‍💨 So, now what? Can any of the array be recovered??

Well, that's what I'm trying to sort out. The first drive died months ago and parity was rebuilt many times. It was checked weekly as well. I'm not sure that the 1tb drive is even in the parity data anymore. (It was empty when it failed) I was just wondering if I could create a new co fig, remove that 1tb drive from the array properly, the. Rebuild using a new 10tb drive to replace the one that died lastnight? (Any info from the server I have to get when near it later)

Hi, I have a 12 drive array. 1 parity (10 tb), 1 cache (2 tb), ane a 10 drives for storage. Back in Jan or Feb i lost a 1tb drive out of the array and removed it from the array. It still shows as unassigned (it's drive 9 for reference), but hasn't been in for months. I have my parity check set to run weekly. It takes about 20+hrs but, i figured better safe than sorry. Lastbight, I got some alerts and upon looking into them, realized drive 2 was showing as missing. I found the drive physically, and it will spin up but doesn't register as being present. The parity drive is a 10tb drive, the drive that is missing g is 10tb. My question is, can i somehow restore the array by replacing the bad 10tb drive and letting ubraid so it's thing? The 1tb drive has been out and the parity has been checked and , I believe even rebuilt, more than once since that drive was removed. Any help would be greatly appreciated!