Revision history [back]

The fastboot recovery options lack support to essential btrfs filesystem command called btrfs-zero-log.

Quite often unbootable btrfs filesystem can be recovered by removing the last not completed actions by zeroing the journal log. I have personally manage to fix unbootable btrfs system with this command.

Latest effort to fix the broken btrfs system was with my Jolla which suffered crash during balance operation and was left unbootable state. Fastboot enviroment and it's recivery options did not work 'cause mmcblk0p28 was left unmountable state after balance crash.

I need to do dd mmcblk0p28 to mSD and run btrfs-zero-log in the Ubuntu PC. After dd'ing fs back to /dev/mmcblk0p28 my Jolla was all good again.

Please, bring the btrfs-zero-log to fastboot as Recovery option.

The fastboot recovery options lack support to essential btrfs filesystem command called btrfs-zero-log.

Quite often unbootable btrfs filesystem can be recovered by removing the last not completed actions by zeroing the journal log. I have personally manage to fix unbootable btrfs system with this command.command at least half dozen cases.

Latest effort to fix the broken btrfs system was with my Jolla which suffered crash during balance operation and was left unbootable state. Fastboot enviroment and it's recivery options did not work 'cause mmcblk0p28 was left unmountable state after balance crash.

I need to do dd mmcblk0p28 to mSD and run btrfs-zero-log in the Ubuntu PC. After dd'ing fs back to /dev/mmcblk0p28 my Jolla was all good again.

Please, bring the btrfs-zero-log to fastboot as Recovery option.

The fastboot recovery options lack support to essential btrfs filesystem command called btrfs-zero-log.

Quite often unbootable btrfs filesystem can be recovered by removing the last not completed actions by zeroing the journal log. I have personally manage to fix unbootable btrfs system with this command at least half dozen cases.

Latest effort to fix the broken btrfs system was with my Jolla which suffered crash during balance operation and was left unbootable state. Fastboot enviroment and it's recivery recovery options did not work 'cause mmcblk0p28 was left unmountable state after balance crash.

I need to do dd mmcblk0p28 to mSD and run btrfs-zero-log in the Ubuntu PC. After dd'ing fs back to /dev/mmcblk0p28 my Jolla was all good again.

Please, bring the btrfs-zero-log to fastboot as Recovery option.

The fastboot recovery options lack support to essential btrfs filesystem command called btrfs-zero-log.

Quite often unbootable btrfs filesystem can be recovered by removing the last not completed actions by zeroing the journal log. I have personally manage to fix unbootable btrfs system with this command at least half dozen cases.

Latest effort to fix the broken btrfs system was with my Jolla which suffered crash during balance operation and was left unbootable state. Fastboot enviroment and it's recovery options did not work 'cause mmcblk0p28 was left unmountable state after balance crash.

I need to do dd mmcblk0p28 to mSD and run btrfs-zero-log in the Ubuntu PC. After dd'ing fs back to /dev/mmcblk0p28 my Jolla was all good again.

Please, bring the btrfs-zero-log to fastboot as Recovery option.

The fastboot recovery options lack support to essential btrfs filesystem command called btrfs-zero-log.

Quite often unbootable btrfs filesystem can be recovered by removing the last not completed actions by zeroing the journal log. I have personally manage to fix badly corrupted, unbootable btrfs system with this command at least half dozen cases.

Latest effort to fix the broken btrfs system was with my Jolla which suffered crash during balance operation and was left unbootable state. Fastboot enviroment and it's recovery options did not work 'cause mmcblk0p28 was left unmountable state after balance crash.crash. The fs corruption segfaults both mount and btrfs check --repair attempts.

I need to do dd mmcblk0p28 to mSD and run btrfs-zero-log in the Ubuntu PC. After dd'ing fs back to /dev/mmcblk0p28 my Jolla was all good again.

Please, bring the btrfs-zero-log to fastboot as Recovery option.

The fastboot recovery options lack support to essential btrfs filesystem command called btrfs-zero-log.

Quite often unbootable btrfs filesystem can be recovered by removing the last not completed actions by zeroing the journal log. I have personally manage to fix badly corrupted, unbootable btrfs system with this command at least half dozen cases.

Latest effort to fix the broken btrfs system was with my Jolla which suffered crash during balance operation and was left unbootable state. Fastboot enviroment and it's recovery options did not work 'cause mmcblk0p28 was left unmountable state after balance crash. The fs corruption segfaults both mount and btrfs check --repair attempts.

I need to do dd mmcblk0p28 to mSD and run btrfs-zero-log in the Ubuntu PC. After dd'ing fs back to /dev/mmcblk0p28 my Jolla was all good again.

Please, bring the btrfs-zero-log to fastboot as Recovery option.