Kilrah

Because it only netdata's debatable point of view that it is...

Yeah, the UI is still broken for 7.3...

You probably want to reset container order to default after you removed the plugin and rebooted. Yes it does do funky things with the order.

TBF the beeper is probably something nobody has cared about in decades and it's a stroke of luck on any board if the bios code that probably was never touched or checked for ages still works from an OS... AFAIK you can't even make the beeper go from Windows at all, it'll make a beep sound on the default sound card instead.

It's writes that do, not reads. You can always make your own script if you want to back up only the essential stuff, for the vast majority of people it's still probably best to have a full self-contained backup they can restore without having to piecemeal stuff from the backup and official distribution.

There's usually no reason to disperse across multiple drives, that's actually usually detrimental, so why do you want that? That said I believe you can achieve it in with the appropraite share settings.

That's the whole point, this will make the copy appear as part of the same share (a share is just "any top level folder on any array or pool drive with that name"), so anything accessing the "Photos" share will wake up that pool to list its content as a result. Make a new share on that drive and copy the contents of the Photos share to that new share on that pool instead.

Current Unraid version is 7.2.3. Anything before 7.1 is deprecated.

Group the containers of the stack so they're all stopped together, and use excludes on each of them as required?

Use pre/post backup scripts to stop/start stacks?

Unraid automatically adds the TZ value to every container managed by templates with the timezone Unraid is set to.

As long as it's only the container limit that's hit yes.

The whole question was precisely whether the plugin would add support for the 8126/7...

Then excluding them is what you want. Seems to be Docker volume names rather than folders.

P----s shareUseCache="no" # Share exists on disk1, disk2, disk3, photoscopyAssuming that pool is named "photoscopy" it looks like you made your copy use the same share name, so anything that reads from the (I assume) "Photos" share will have to list its contents too. Should use a different share name and set it to only live on that pool.

The trick is to use msconfig to set windows to boot in safe mode. Shutdown, change disk mode, boot in safe mode once, it'll switch to the new driver, and set it back to normal boot.

8125 has worked without plugin for a long time. In some setups the plugin works better, in others default is fine.

What pool config? RAIDZ1?

Tried a reboot yet?

Run it in a tmux session, or add & at the end to detach it from the terminal?

And what host path did you give to that volume? Something valid e.g. a subfolder of your appdata share?

Probably since it was fixed a while ago, we're on 5.1.4 now

Usual resource allocation. Yes it "wouldn't hurt" if it had feature X as a choice, but feature X requires development time, and that's development time that could be instead put into something else deemed more useful for the intended market segment.

check filesystem on any affected drives.

So they are not "in the pool" which would mean "all of them in the same pool", they're each in separate pools. So yes you should be able to move them to the array as is. You need to do a "new config" then add them, and that will then rebuild parity.