[opensuse-support] How to fix btrfs Csum failure of root partition?
Dear all, Recently I got a lot of kernel panics with my openSUSE Tumbleweed laptop. Today, it brings me a rescue screen after reboot from a panic. It says the btrfs system of my root partition has failure of Csum. I put in root password and run 'btrfs rescue --init-chunk-tree' but failed. Any ideas to bring the system up without reinstallation? Regards, Haoxian
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 06/11/2019 06.23, CnZhx wrote:
Dear all,
Recently I got a lot of kernel panics with my openSUSE Tumbleweed laptop. Today, it brings me a rescue screen after reboot from a panic. It says the btrfs system of my root partition has failure of Csum.
I put in root password and run 'btrfs rescue --init-chunk-tree' but failed.
Any ideas to bring the system up without reinstallation?
I have none when btrfs is involved, sorry. But the generic advice is to run the "equivalent" to fsck from an external rescue system, like a rescue usb stick - so that the target partition is not mounted. - -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXcKVJgAKCRC1MxgcbY1H 1cCUAJ94V7UtKiuQ1MadjwE4jZxpO7polwCeJ9TIQgDtqui5L/Ba7inpwwBV6B4= =vjKY -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Hello, Am Mittwoch, 6. November 2019, 06:23:07 CET schrieb CnZhx:
Recently I got a lot of kernel panics with my openSUSE Tumbleweed laptop. Today, it brings me a rescue screen after reboot from a panic. It says the btrfs system of my root partition has failure of Csum.
I put in root password and run 'btrfs rescue --init-chunk-tree' but failed.
Any ideas to bring the system up without reinstallation?
Have a look at https://en.opensuse.org/SDB:BTRFS#How_to_repair_a_broken.2Funmountable_btrfs... Regards, Christian Boltz -- But for now is the most important to find how to put more hours in the day. The 24 is too little :-) [Rajko M in opensuse-wiki] -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On Thursday, 7 November 2019 01:19:02 CST Christian Boltz wrote:
Hello,
Am Mittwoch, 6. November 2019, 06:23:07 CET schrieb CnZhx:
Recently I got a lot of kernel panics with my openSUSE Tumbleweed laptop. Today, it brings me a rescue screen after reboot from a panic. It says the btrfs system of my root partition has failure of Csum.
I put in root password and run 'btrfs rescue --init-chunk-tree' but failed.
Any ideas to bring the system up without reinstallation?
Have a look at https://en.opensuse.org/SDB:BTRFS#How_to_repair_a_broken.2Funmountable_btrfs _filesystem
Regards,
Christian Boltz Thank you, Christian. I did not see the article you provided when I searched on my phone. I wish I have seen it earlier.
But I solved the problem by referring to the 1st advice on BtrFS Wiki hosted on kernel.org (https://btrfs.wiki.kernel.org/index.php/Problem_FAQ#I_can. 27t_mount_my_filesystem.2C_and_I_get_a_kernel_oops.21), although I do not know what's happen in the back. In summary, I booted the laptop in Rescue mode using a installation USB stick as suggested by Carlos. Then mounted the partition with `-o recovery`. This is successful and the files are there intact. Then, I umount the partition and `btrfs check` it again. It reported no problem. I rebooted and the system was up without a single glitch. Best wishes, Haoxian -- Best regards, ZHX -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On Thu, Nov 07, 2019 at 08:53:00AM +0800, H Zeng wrote:
... I rebooted and the system was up without a single glitch.
Thanks for summarising your success and contributing to the openSUSE community. It may seem obvious, but list archives are a really rich source of help when trying to resolve problems. Many support threads (notably on other platforms) end with suggestions of possible solutions but few clues as to which/if one worked. I know it's easy to forget to close the loop once the heat of battle abates a little, but it can really help the next guy :) Daniel -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
participants (5)
-
Carlos E. R. -
Christian Boltz -
CnZhx -
Daniel Morris -
H Zeng