snowe

Yeah no luck. What is the best way to recreate the pool though? I had tried with just unassigning the drive, restarting, reassigning, but it didn't try to rebuild the pool. Do I need to just wipe the drive?

Hm. restarting triggered a parity check operation, going to take a day to finish. that's weird. In any case, I'd tried restarting last week before making this post, so I don't think it's going to work. I did try to recreate the pool then but was unsuccessful, that's when I made this post. What are the proper steps for remaking the pool?

Started the command, got the same output, and then ran diagnostics (while the command was running). not sure if that's what you meant, but the command didn't seem to be doing anything yesterday so I had cancelled it (hadn't started it with a subshell, so it needed my computer to stay unlocked and connected). venus-diagnostics-20260811-0906.zip

Sorry for the delay here. when I went to run your commands the first time it showed that a balance had made it decently far. But it then got stuck at like 200 of 247 or something like that for a week. So I cancelled that balance today and ran your command. I've let it run for a few hours, but the only message it has shown is this: root@Venus:~# btrfs balance start -f -mconvert=dup,soft -dconvert=single,soft /mnt/cache WARNING: Conversion with missing device(s) can be dangerous. Please use 'btrfs replace' or 'btrfs device remove' instead. Safety timeout skipped due to --force When I run a status check in a different session I get: root@Venus:~# btrfs balance status /mnt/cache Balance on '/mnt/cache' is running 0 out of about 25 chunks balanced (267 considered), 100% left root@Venus:~# So seemingly nothing is happening, even with that command.

I don't know when it got to this point, but for some reason my cache drive thinks that it is a 2 device pool, even though I've only ever had one device there. I do not know if I misclicked at some point or what, but now anytime I restart my server, a btrfs balance starts and never goes anywhere (it will just get stuck at 0 out of 25) Overall: Device size: 715.41GiB Device allocated: 293.12GiB Device unallocated: 422.29GiB Device missing: 238.47GiB Device slack: 0.00B Used: 250.63GiB Free (estimated): 420.88GiB (min: 243.81GiB) Free (statfs, df): 121.30GiB Data ratio: 1.09 Metadata ratio: 2.00 Global reserve: 345.55MiB (used: 0.00B) Multiple profiles: yes (data, metadata, system) Data Data Metadata Metadata System System Id Path single RAID1 RAID1 DUP RAID1 DUP Unallocated Total Slack -- --------- --------- -------- -------- --------- -------- -------- ----------- --------- ----- 1 /dev/sdd1 239.00GiB 23.00GiB 1.00GiB 6.00GiB 32.00MiB 64.00MiB 207.85GiB 476.94GiB - 2 missing - 23.00GiB 1.00GiB - 32.00MiB - 214.44GiB 238.47GiB - -- --------- --------- -------- -------- --------- -------- -------- ----------- --------- ----- Total 239.00GiB 23.00GiB 1.00GiB 3.00GiB 32.00MiB 32.00MiB 422.29GiB 715.41GiB 0.00B Used 206.30GiB 21.58GiB 16.19MiB 582.61MiB 0.00B 64.00KiB I have to cancel the balance anytime I restart. How do I get rid of this detected second device that isn't actually part of the pool? I do have it only set to be 1 slot. I have taken the array down, unassigned the existing cache device, started the array again, chosen to "start array even with missing device", then restarted the server entirely, and reversed all of that and it still thinks there's a second slot. root@Venus:~# btrfs fi usage /mnt/cache Overall: Device size: 715.41GiB Device allocated: 292.12GiB Device unallocated: 423.29GiB Device missing: 238.47GiB Device slack: 0.00B Used: 249.95GiB Free (estimated): 421.36GiB (min: 244.00GiB) Free (statfs, df): 122.02GiB Data ratio: 1.09 Metadata ratio: 2.00 Global reserve: 343.09MiB (used: 0.00B) Multiple profiles: yes (data, metadata, system) Data,single: Size:238.00GiB, Used:205.51GiB (86.35%) /dev/sdc1 238.00GiB Data,RAID1: Size:23.00GiB, Used:21.64GiB (94.09%) /dev/sdc1 23.00GiB missing 23.00GiB Metadata,RAID1: Size:1.00GiB, Used:16.19MiB (1.58%) /dev/sdc1 1.00GiB missing 1.00GiB Metadata,DUP: Size:3.00GiB, Used:573.62MiB (18.67%) /dev/sdc1 6.00GiB System,RAID1: Size:32.00MiB, Used:0.00B (0.00%) /dev/sdc1 32.00MiB missing 32.00MiB System,DUP: Size:32.00MiB, Used:64.00KiB (0.20%) /dev/sdc1 64.00MiB Unallocated: /dev/sdc1 208.85GiB missing 214.44GiB

It actually has been broken for a few months. I'll try posting in that forum though, thanks.

Is anyone else having issues with their ghost container loading at all? I initially thought it was a SWAG issue, but I can't even get the 192 container address to load, it gives me a An error occurred during a connection to 192.168.1.169:2368. SSL received a record that exceeded the maximum permissible length. Error code: SSL_ERROR_RX_RECORD_TOO_LONG error. If I curl it (on http), I instead get a Moved Permanently status code with a redirect to https. No clue where to go from here, tried a bunch of different settings, different networks, etc. Nothing in the ghost documentation looks like it disables ssl anymore, so I'm not sure how to get past this.

Are these containers no longer supported? It seems like the github repo has been deleted.

Oh ok, so you want the diagnostics even without the crash?

I have done a memtest, 3 passes all fine. How can I attach diagnostics if they reset on reboot? Seems like I'll need to set up a syslog server to log everything to? I've changed that setting. Let's see if the system crashes now.

I'm getting constant kernel crashes. I've tried quite a few things: - Unplugging drives - switching motherboards - removing the GPU - more cooling - opening the case for even more cooling - idek what else. I keep my full system up to date, along with all docker containers, tools, packages, etc. I've attached my system logs. If anyone could help I'd really appreciate it.. If I need to provide more information please let me know. syslog.txt