Kilrah

If set up as boot+data that only refers to the data partitions.

You've set the array to autostart and it's supposedly doing that, so why would you try to also start it manually? What's the actual problem if any?

Appdata backup plugin.

I added the current location for Windows, but it's moved before. Don't know about linux/mac locations.

That's a different app/container.

It does not. It's physical drives that count, if you use an existing one for shared duties it's still one drive.

Check syslog to see if maybe the drive unexpectedly disconnects from USB during the process.

AFAIK it's an intentional protection in CA, if 2 plugins have the same URLs it triggers so there can't be a takeover whether intentional or not if someone forks a plugin and doesn't change it, requiring manual review/reapproval. Happened some time ago with major plugins when their ownership changed, IIRC there is talk about it in the CA thread. If you want 2 versions of a plugin your dev setup must be separate enough so that such a mistake of mixing them up can never happen.

No. You can choose whether you want the drives to be dedicated to boot or shared with data when setting up.

Yes that's what the new internal boot feature is for.

This typically happens if you unplug the drive without unmounting it first.

2026.5.31+300695de5 is fine here. You likely didn't delete the orphan image and thus reused 2026.05.30, check for updates again.

You'd use something like Wake on LAN for that.

GitHubDocker image crashes upon start · Issue #6178 · searxng/s...How To Reproduce? Start SearXNG using docker-compose Expected behavior The container starts and does not crash. Screenshots & Logs ❯ curl -fsSL \ -O https://raw.githubusercontent.com/searxng/searxn... Seems like it got fixed already.

7.3.1 is the latest. But along with the new licensing system the "previous" branch i.e. currently 7.2 still gets security updates for those whose updates expired and they can't upgrade to 7.3 without extending.

Yes. Just reformat it and make sure a partition was made, most OSes should do that. Maybe it was formatted in the device and that doesn't make a partition.

I have a couple of 16GB 2242s I've used for various things (not unraid boot) and yeah they're always hot.

You probably have a container path set wrong and something created an "admin" folder at the root of your cache drive. Any folder present at the root of any array/pool drive will become a share with default settings.

Missing the most important part, what's actually not working/the error you get?

Nope, has always been 6. Did you just buy it now? If you were on the trial until now then that lets you have unlimited devices.

No ad/script blocker? Try a different browser?

Correct, you can't have only the boot partition mirrored, has to be the whole boot+data.

16GB Optanes are a common choice. https://www.ebay.com/itm/375486928506?_skw=intel+optane+16gb&epid=936935701 I'd probably get a 2nd 1TB and make a common mirrored pool for boot and cache though, getting rid of the 500GB.

Yes. Would make no sense to restrict this user access to some shares when they log in, but they can just not log in and access everything since it's public... You'll have to submit user/pw once for each of your machines but then they'll remember it.

Sweet, works perfect Seems like I forgot to reply but I looked and the built-in dark mode on linux required a lot of hacking to work with manual patches/rebuilds of wxWidgets so that was a big nope to maintain.