Discussion
My Pixel 7 on GrapheneOS ran out of battery apparently during a pending update. Now it bootloops: lockscreen for 1s -> crash -> recovery: "Cannot load Android system. Your data may be corrupt." Tried everything data-preserving: sideloaded the newest OTA, safe mode, snapshot cancel via fastbootd, forced the full snapshot merge, with the OS verified clean on both slots. It still crashes.
Anyone recovered data from this state without a wipe, before I factory reset?
@jfkimmes It's likely an upstream f2fs data corruption bug. These issues will be greatly reduced when we get the 6th through 9th gen Pixels moved to the Linux 6.18 LTS branch as we recently did for the 10th gen Pixels. There are many unfixed f2fs bugs in the 6.1 LTS branch. We're working on moving the rest to the 6.18 LTS now. A lot f2fs issues were fixed in later kernel versions but many weren't backported. In some cases upstream LTS backports have been done incorrectly and contributed to it.
@GrapheneOS Good to hear that work is being done on this.
But this is a corrupted partition for user data not on the system image, right?
I take from this that there is likely nothing I can do to remedy the corruption since I am not able to unlock the user data partition without booting beyond the lock screen.
@jfkimmes It has nothing to do with the firmware or OS images. Corruption of the firmware or OS images would indicate a failing SSD and there's not much that can be done once that's happening. SSD failure is usually very quick rather than gradual due to how they're built with redundancy and error correction built in to handle random bit flips.
Linux kernel is extremely buggy and the filesystems are no exception. XFS would be most robust but is not an option due to lack of needed features.
@jfkimmes It's likely an upstream f2fs data corruption bug. These issues will be greatly reduced when we get the 6th through 9th gen Pixels moved to the Linux 6.18 LTS branch as we recently did for the 10th gen Pixels. There are many unfixed f2fs bugs in the 6.1 LTS branch. We're working on moving the rest to the 6.18 LTS now. f2fs wasn't very good at handling sudden loss of power which could happen if the battery drained all the way but the OS didn't get alerted before the power cut off.
