Also running on Maverick with the same issue, another virtualbox.
This is what is printed to the plymouth VT (similar to above screenshot):
"
fsck from util-linux-ng 2.17.2
User cancelled filesystem checks
/dev/sda1: e2fsck canceled
fsck.ext4: Inode bitmap not loaded while setting block group checksum info
mountall: fsck / [207] terminated with status 8
mountall: Unrecoverable fsck error: /
"
If running fsck from a liveCD, cancelling it will produce the same error:
"
^C/dev/sda1: e2fsck canceled
fsck.ext4: Inode bitmap not loaded while setting block group checksum info
~$ echo $?
8
"
Is this error from fsck correct? Is the problem the error in fsck, or is it the way mountall/plymouth interprets the error as a serious failiure?
Letting the fsck run through correctly (in which case no errors are reported) does not affect this in any way.
Also running on Maverick with the same issue, another virtualbox.
This is what is printed to the plymouth VT (similar to above screenshot):
"
fsck from util-linux-ng 2.17.2
User cancelled filesystem checks
/dev/sda1: e2fsck canceled
fsck.ext4: Inode bitmap not loaded while setting block group checksum info
mountall: fsck / [207] terminated with status 8
mountall: Unrecoverable fsck error: /
"
If running fsck from a liveCD, cancelling it will produce the same error:
"
^C/dev/sda1: e2fsck canceled
fsck.ext4: Inode bitmap not loaded while setting block group checksum info
~$ echo $?
8
"
Is this error from fsck correct? Is the problem the error in fsck, or is it the way mountall/plymouth interprets the error as a serious failiure?
Letting the fsck run through correctly (in which case no errors are reported) does not affect this in any way.