A suggested fix for this would be: initrd: - At every boot, do a minimal fsck check for problems, if problem, write "fsck <partition>" to /cache/recovery/ubuntu_command and reboot to recovery
recovery: - Add support for the fsck stanza, when getting it, run fsck in fix mode, if possible, supporting the usual yes/no questions using pixelflinger and button input. rootfs: - If /cache/recovery/broken_root exists, immediately pull the latest full image and reboot for flashing system-image-client: - Add a fsck run to the standard ubuntu_command prior to flashing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1387214 Title: file corruption on touch images in rw portions of the filesystem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android/+bug/1387214/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
