On Mon, May 02, 2011, AJ ONeal wrote:
Warning... fsck.ext3 for device /dev/mmcblk0p2 exited with signal 11.
fsck.ext3 segfaulting is pretty bad
- Plymouth's availability reported/y affects `/` being mounted
That might be normal (see other message)
- yet there are no errors on the filesystem and it still mounts (though
in read-only mode)fsck -y /dev/mmcblk0p2
Well even without errors, something causes fsck to segv when run from mountall apparently; maybe different flags?