[opensuse-factory] Help rescuing unbootable btrfs partition !
It finally happened. Had the system hard crash in KDE + NVIDIA drivers, latest 5.1.7 kernel as of today. Force powered off the system and on reboot the system fails to mount /var and /tmp. Not a good sign. I boot on a current TW USB image in rescue mode. I mount the btrfs partition and in dmesg I see this kernel crash fixed by a recent patch that will be in 5.2, that is related to power loss: https://patchwork.kernel.org/patch/10955321/ So I'm asking to kernel experts here if this situation can be recovered ? btrfs scrub seems to be stuck at 0%. I did not try anything else. Would booting with an old kernel eventually work ? Or booting with a recent kernel having that patch ? Anything that could recover the situation... This is really never fun when something happen. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Michael Pujos
It finally happened.
Had the system hard crash in KDE + NVIDIA drivers, latest 5.1.7 kernel as of today.
Force powered off the system and on reboot the system fails to mount /var and /tmp. Not a good sign.
I boot on a current TW USB image in rescue mode.
I mount the btrfs partition and in dmesg I see this kernel crash fixed by a recent patch that will be in 5.2, that is related to power loss:
https://patchwork.kernel.org/patch/10955321/
So I'm asking to kernel experts here if this situation can be recovered ? btrfs scrub seems to be stuck at 0%. I did not try anything else.
Would booting with an old kernel eventually work ? Or booting with a recent kernel having that patch ? Anything that could recover the situation...
This is really never fun when something happen.
maybe did you try booting to an earlier snapshot and didn't tell us. probably should have been your first step. that is actually what the snapshots are for, aiui. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 17/06/2019 04:06, Patrick Shanahan wrote:
* Michael Pujos
[06-16-19 19:57]: maybe did you try booting to an earlier snapshot and didn't tell us. probably should have been your first step. that is actually what the snapshots are for, aiui.
Booting on a previous snapshot or kernel does not work as it is a btrfs issue the kernel cannot handle and it just stops there. There's a fix for this issue in kernel 5.1.8. I'm going to boot with a live CD from another distro with kernel >= 5.1.8 and see how it goes. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 17/06/2019 09:26, Michael Pujos wrote:
It finally happened.
Had the system hard crash in KDE + NVIDIA drivers, latest 5.1.7 kernel as of today.
Force powered off the system and on reboot the system fails to mount /var and /tmp. Not a good sign.
I boot on a current TW USB image in rescue mode.
I mount the btrfs partition and in dmesg I see this kernel crash fixed by a recent patch that will be in 5.2, that is related to power loss:
https://patchwork.kernel.org/patch/10955321/
So I'm asking to kernel experts here if this situation can be recovered ? btrfs scrub seems to be stuck at 0%. I did not try anything else.
Would booting with an old kernel eventually work ? Or booting with a recent kernel having that patch ? Anything that could recover the situation...
This is really never fun when something happen.
This is not a general support mailing list, please use opensuse-support for support questions, if you have a question related to a specific kernel patch in openSUSE try opensuse-kernel@ (there is no guarantee all the kernel devs are on this list). Thanks -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 17/06/2019 04:48, Simon Lees wrote:
This is not a general support mailing list, please use opensuse-support for support questions, if you have a question related to a specific kernel patch in openSUSE try opensuse-kernel@ (there is no guarantee all the kernel devs are on this list).
Thanks
Noted. I just fixed this issue booting into the PCLInuxOS Live CD with kernel 5.1.10. Mounting the btrfs partition repaired it, thanks to the fix for it in 5.1.8. Glad to have my system recovered. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Althoug maybe slightly off-topic: I had a very similar issue today: - boot (root on /dev/sda5) being stuck on mounting subvolumes /var and /tmp. none of the earlier snapshots (I had about 10) worked(!) - since something in the btrfs itself seems broken? - booting from another partition (/dev/sda3) where I happen to have an older 4.16.4 kernel: executing "btrfs check /deb/sda5"(=broken btrfs) reported no error, but mounting it and the 2 subvolumnes once on /mnt... fixed the issue and I could boot normally on the formerly broken /dev/sda5 again. So even older kernel seem to be able to fix this strange issue? regards Christian Am 17.06.19 um 10:43 schrieb Michael Pujos:
On 17/06/2019 04:48, Simon Lees wrote:
This is not a general support mailing list, please use opensuse-support for support questions, if you have a question related to a specific kernel patch in openSUSE try opensuse-kernel@ (there is no guarantee all the kernel devs are on this list).
Thanks
Noted.
I just fixed this issue booting into the PCLInuxOS Live CD with kernel 5.1.10. Mounting the btrfs partition repaired it, thanks to the fix for it in 5.1.8. Glad to have my system recovered. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (4)
-
Christian Mahr
-
Michael Pujos
-
Patrick Shanahan
-
Simon Lees