devin.buell

Below is what i pulled from the boot drive after reboot syslog-previous.txt

So this just happened again. I had interacted with the WebUI and opened up a few docker containers. And when i came back to the tab, the UI was down and refreshing didn't solve it (This site can’t be reached message). i have tried to ssh into the machine but get and operation timed out when trying to connect. So i end up having to reboot the machine. When i last checked the Log Viewer tool (yesterday) there weren't any logs in the mcelog file.

Any advice on how to perserve /var/loog/mcelog in the event the machine becomes unresponsive again? (I don't have a monitor keyboard attached to this machine so i rely on SSH or the WebGUI). Good call out on the BIOS its been a while since i have updated it though I could have sworn it was more recent in 2021.

My server has recently become unstable, - as evidence by services being unreachable (including the WebUI or via SSH) requiring a reboot to get it up and running. Today I had a situation where i logged into the WebUI and saw that a has cpu core pinned at 100% and then the WebUI returned 500 error. I was able to still ssh into the box and grab a diagnostic file. But a little while later it was unreachable again (either way) and I had to reboot it. I have turned off docker services and vms with no really success. Yesterday I turned on the mirror syslogs to boot drive in hopes of capturing more logs about why the lock up was happening. Im wondering if that potentially wore out my bootdrive (which was ~6 years old?) unraid-diagnostics.zip

You are amazing! The pool has been restored. Going to make a fresh backup of everything now!

root@BuellVault:~# btrfs fi show Label: none uuid: b242ecb7-0712-4962-8ae2-ac3d49ad64fd Total devices 4 FS bytes used 142.30GiB devid 1 size 447.13GiB used 63.00GiB path /dev/sdc1 devid 2 size 447.13GiB used 63.00GiB path /dev/sdd1 devid 3 size 465.76GiB used 82.03GiB path /dev/sdb1 devid 4 size 465.76GiB used 82.03GiB path /dev/sde1 root@BuellVault:~#

Output below: root@BuellVault:~# btrfs-select-super -s 1 /dev/sdc1 using SB copy 1, bytenr 67108864 root@BuellVault:~# btrfs-select-super -s 1 /dev/sdd1 using SB copy 1, bytenr 67108864 root@BuellVault:~#

THis is the output after I start the array: root@BuellVault:~# btrfs fi show Label: none uuid: 19173620-859f-437e-b39c-fbe64123cf0a Total devices 1 FS bytes used 348.00KiB devid 1 size 1.00GiB used 126.38MiB path /dev/loop2 bad tree block 2386712559616, bytenr mismatch, want=2386712559616, have=0 Couldn't read tree root Label: none uuid: b242ecb7-0712-4962-8ae2-ac3d49ad64fd Total devices 4 FS bytes used 142.30GiB devid 3 size 465.76GiB used 82.03GiB path /dev/sdb1 devid 4 size 465.76GiB used 82.03GiB path /dev/sde1 *** Some devices missing

Sorry for the delay - was traveling. Output is below bad tree block 2386712559616, bytenr mismatch, want=2386712559616, have=0 Couldn't read tree root Label: none uuid: b242ecb7-0712-4962-8ae2-ac3d49ad64fd Total devices 4 FS bytes used 142.30GiB devid 3 size 465.76GiB used 82.03GiB path /dev/sdb1 devid 4 size 465.76GiB used 82.03GiB path /dev/sde1 *** Some devices missing

I made a mistake thinking I could reduce my cache pool size and removed two drives and then restarted the array. This resulted in a now obvious messaging saying two many disks missing and that the pool was unmountable. I added the drives back in the same order and restarted the array but have the same error message. Is it possible to restore my pool or do I need to manually pull of the files from one of the drives and then rebuilt the pool? Diagnostic files attached. buellvault-diagnostics-20230320-2130.zip