June 20, 20233 yr Hi there, So last week my server seemed like it crashed, I restarted it, and then it did its parity check thing and was all good from there. Today it has crashed again, not accessible from Web GUI or ssh and nothing was coming up when I put my monitor into it and the keyboard wasn't even being picked up. So, so much for trying to get diagnostics for that, so I force restarted my machine and now when loading in the array I have been welcomed with this. Is there any way to fix this or bring it back or do damage control. I'm not an expert on Linux, It's still something I'm learning over time. Any help or guidance would be appreciated.
June 20, 20233 yr Community Expert Solution If the log tree is the only issue this may help: btrfs rescue zero-log /dev/nvme2n1p1
June 20, 20233 yr Author I ran that and got this "Clearing log on /dev/nvme2n1p1, previous log_root 210335744000, level 0". Will restarting my array bring them back to be mountable or will this require a restart?
June 20, 20233 yr Author Do you mind explaining also what that was that happened there? Could it of been something I caused from a force restart? And does that mean data loss on that cache pool, or is it an error picked up from a read and write on the SSD?
June 20, 20233 yr Community Expert 1 hour ago, Nath2125 said: Could it of been something I caused from a force restart? Yes. 1 hour ago, Nath2125 said: does that mean data loss on that cache pool If that fixes it usually data is fine, only the log tree was affected.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.