Being a virtual machine (VirtualBox) the fsck took less than 10 seconds on the first too forced fscks (sudo touch /forcefsck; sudo reboot).
The third time it got stuck on the "Press C to cancel all checks currently in progress" screen after displaying the 98% (I think it got stuck just after completing the fsck), I pressed ESC to see the text mode messages and this was displayed:
-----------------
"(process: 216) GLib-WARNING **: getpwuid_r(): falied due to unknown user id (0)
Pressing ESC twice again (to go to the graphic screen and back to text mode) would cause another fsck message to be printed.
It remained stuck for several minutes until I pressed "C".
I tried doing the forced fsck a fourth and fifth time: it did got stuck again on the 5th. So the overall is 2 of each 5 times.
apt version mountall: 2.15
apt version plymouth: 0.8.2-2-1mint3
I just reproduced it on my Mint 9.
Being a virtual machine (VirtualBox) the fsck took less than 10 seconds on the first too forced fscks (sudo touch /forcefsck; sudo reboot).
The third time it got stuck on the "Press C to cancel all checks currently in progress" screen after displaying the 98% (I think it got stuck just after completing the fsck), I pressed ESC to see the text mode messages and this was displayed:
-----------------
"(process: 216) GLib-WARNING **: getpwuid_r(): falied due to unknown user id (0)
fsck from util-linux-ng 2.17.2
/dev/sda2: 134297/2498560 files (0.2% non-contiguous), 911478/9985280 blocks
-------------------
Pressing ESC twice again (to go to the graphic screen and back to text mode) would cause another fsck message to be printed.
It remained stuck for several minutes until I pressed "C".
I tried doing the forced fsck a fourth and fifth time: it did got stuck again on the 5th. So the overall is 2 of each 5 times.
apt version mountall: 2.15
apt version plymouth: 0.8.2-2-1mint3