I'm not sure if this bug belongs here at all, but I have no better idea, what may cause it - so, if I'm going to talk silly things here, just say a word:

Yesterday, I left my Phone with some things opened, and due to battery being low, BME shut device down. For reasons unknown, something went bad, and my /dev/mmcblk0p2 went FCKD'ed totally, bringing device (for the first time, I must admit) to state of not being able to go past five dots.

I've opened backupmenu and recovery console, ensured that /dev/mmcblk0p2 is unmounted (just in case) and started fsck.ext4 (I use ext4 for home). fsck detected 3 wrong inodes and "unexpected inconsistency", so I was forced to run it manually, assuming "yes" to repair questions, as there were literally hundreds of them.

After passing stage 1 and 2 of fsck'ing (in fact, at this point, it was
e2fsck if I recall correctly), my showstopper bug manifested itself:

Any further attempts resulted in fsck segfaulting in exact same moment. In desperation, I also tried fsck.ext3 and even fsck.ext2, but they segfaulted in exactly same stage too. As You may presume, it left my partition in such state, that device *was* bootable, but acted like with totally empty /dev/mmcblk0p2 - You can imagine rest, I ended up restoring optFS from backup.

---

So, as I have said, I have no idea if fsck is related to busybox-power at all, but it seems it fails totally, when more advanced repair operations are required, Sorry, if it is not related here - in such case, please give me a hint about correct place, and I'll repost story there.

/Estel