Kilrah

It's in the list of fixes for 7.2.1.
Version 7.2.1-rc.1 2025-11-07 | Unraid Docs
This is a small update with some great fixes and improvements.

Ah the 10TB doesn't need to be rebuilt, so then yes you can do it in one go, do New Config, assign all the drives as desired and let it build parity. Just won't have protection during that process.

What's that "source" in the router? Might need to be empty or it'd only forward stuff coming from the address specified which will never happen.

The standard TZ variable. As you can see anytime a container is added/edited the run command contains it.



If they decided to require a different variable then I'm not sure how to reference the existing one.

GitHub
unraid_scripts_and_guides/guides/recreate_dockerimg.md at...
Unraid scripts and guides I've put together. Contribute to jcofer555/unraid_scripts_and_guides development by creating an account on GitHub.Change the size to something more sensible between steps 3 and 4.

It's the program that will have misidentified it as sqlite3, since you know it's a raw disk image rename it to img and try to mount it on a linux distro that has btrfs tools installed (assuming the image is the default btrfs format).

Unassigned Devices is what you need to mount external drives yes. Might need Unassigned Devices Plus too for exfat.

People often tend to assume everyone has those installed already

There is nothing automated for this, so that's what you need to do.

You ran out of RAM and litellm was killed.
Did you reboot since? FCP will keep warning an out of memory event happened until a reboot.

Reboot?

Did you unmount and remove it from UD before decommissionning it?

I think what i would do is
Remove Parity 2
Start, now running array in normal state with 1 parity
Remove failing drive, start, now array degraded with the failing drive emulated
Assign the 3TB that was parity 2 as replacement for the failed drive, let it rebuild
Once you have your new 8TB assign it to parity 2.

Yes, same for reboot.

That should be in the support thread for that plugin. Seen it mentioned a few times there.

Parity check does not keep state across a reboot unless you use the parity check tuning plugin. If you do and it didn't work in that case then you should post in that plugin's support thread, if you don't then it's correct and it was cancelled by shutting down.

Try that


Uploading Attachment...

Github broke and that apparently wasn't handled correctly.

Correct

Yep




Fine for me, I don't care that it's the first day of the month, but starting it on a Sunday is good since I don't have much regular stuff scheduled that day, since most things are day of week dependent it makes more sense to me than day of month.

Nothing wrong there.

Make sure you don't have any ad/script blocking extensions in your browser, try another one

Well what you can do is in the 2nd step instead of copying only the config folder you basically delete everything on the new drive and copy everything from the old onto it (then remove old .key files and put the one for that drive). Then everything will be identical, just the license key is replaced with the one for the new drive.

Docker when using the native zfs driver internally uses datasets for lots of things e.g. each individual image layers, so that's normal.

When storing the Docker filesystem on ZFS storage it's recommended to either use a Docker image, or use the overlay driver if you want folder mode.

Just don't proxy? If you want proxy enabled for other things create another subdomain that's not proxied and thus will return your wan ip, that you said works.

Probably not. LUKS will mount just fine on any linux distro, Windows there are workarounds using WSL.

If you like Veracrypt that's probably still the more appropriate solution for you, just you have to make an image file instead of whole disk encryption. I doubt it'd have much impact on perf.

Run that command in unraid's terminal.

Actions-Reinstall brings you to the edit page, only ticking the checkbox then install at the bottom does it directly since it's meant for multi-selection.

Probably technically possible but not easy and slow since that'd mean emulating the code meant for the Pi's ARM chip on x86. Also the Pi's boot sequence is weird so while the apps could be emulated a whole image probably can't be run as is.
Just installing klipper on a Debian install should be easier and more straightforward.