elmetal

btrfs check --repair --tree-root 9917919625216 /dev/sdX1 mount -o ro,usebackuproot /dev/sdq1 /mnt/recovery Allowed me to remount it as rw, and allowed me to scrub for errors, it's all working now

I copied what I could via btrfs restore etc. Then I tried to do the --repair portion and got this as a result: enabling repair mode WARNING: Do not use --repair unless you are advised to do so by a developer or an experienced user, and then only after having accepted that no fsck can successfully repair all types of filesystem corruption. E.g. some software or hardware bugs can fatally damage a volume. The operation will start in 10 seconds. Use Ctrl-C to stop it. 10 9 8 7 6 5 4 3 2 1parent transid verify failed on 9917928243200 wanted 835404 found 835380 parent transid verify failed on 9917928243200 wanted 835404 found 835380 parent transid verify failed on 9917928243200 wanted 835404 found 835380 Ignoring transid failure parent transid verify failed on 9917928259584 wanted 835404 found 835380 parent transid verify failed on 9917928259584 wanted 835404 found 835380 parent transid verify failed on 9917928259584 wanted 835404 found 835380 Ignoring transid failure ERROR: child eb corrupted: parent bytenr=9917925277696 item=23 parent level=2 child bytenr=9917928259584 child level=0 ERROR: failed to read block groups: Input/output error ERROR: cannot open file system Starting repair. Opening filesystem to check...

thank you. step 1 of mounting it RO appears to allow me to read SOME stuff. I am copying everything from /temp to the array so I can rebuild the cache. when I try to du -h --max-depth=1 /temp I get input/output error on 2 files and 2 VM folders. Is it worth doing anything to repair those errors in order to not lose those 2 VMs?

Here it is plexmart-diagnostics-20260312-1856.zip

I've read through other I read through other posts and tried a bunch of different things but I am unable to mount my 4 disk cache pool I've tried to attach the diagnostic but I can't figure it out

I can access the container remotely but the container has access to the server via the wg3 address 10.253.3.1.... how can I make sure the container cannot see the server. is it possible when the server itself is its route back to the internet?

that's a great point I didn't think about the fact that it just needs to accept inbounds and not outbounds... Guess I have some testing to do

sorry, forgot to mention: The docker does need access to the internet. and since it'll need to be accessed from the internet (for gameplay)

So I am having an issue I need help with. I currently run all my dockers on the default bridge. Everything works great. What I want to do is one specific docker I want to open to the world (it's a MC server) and I want to use this as a "testing the waters" point for a new idea I had. I want my new docker to be connected to the internet. I want to be able to manage said docker. But I do not want that docker to access my LAN or my server. Some assumptions: Gateway/Router = 192.168.1.1 unRAID = 192.168.1.10 What I was thinking was the docker could live in maybe its own wg network, call it wg3 (wg0-2 already in use for other things). then somehow wg3 needs access to the gateway, but only the gateway. then when I Need to manage the docker I could also join wg3 by connecting to the VPN as a client. 1: does this sound like a good idea? 2: I tried putting it on wg3 and while I can get on wg3 with my computer, the docker cannot see the outside world...

Works here now. updated 7:15am eastern on 3/12

Just realized everyone is having htis issue

Been using this tool forever! Love it. Recently I removed the image (because I'm an idiot and didn't read the prompt when it asked if I had chosen the right docker to remove. Anyway. I re-added via CA appstore and here's the error I get on startup... https://pastebin.com/z6xzhPj7

It just started working after a reboot... wtf?

I too am getting the Array index [2] out of range, array size is [1] when trying to benchmark

dead links in main post. anybody have final version vmdk for 5.0?