Long long time same prob with VMs..
forgot to take a snapshot, it didn’t shutdown correctly, and in next boot stucks in fsck check..
It is a huge problem having lot of ppl with VMs..
Finaly i came to a solution reading lot of forums.. I combined them to a single solution..
Most ppl say that you’ll solve your prob doing this
mount -o remount,rw /
But that didn’t work in my case..
I fixed my issue in the followng steps..:
– First of all, while you are in the read-only filesystem, check your boot errors with [code]dmesg |grep mount[/code]
and you may see some msg saying that it remounted your system in read-only mode (like “remount-ro”)
Remember this.. we’ll compare it to the next dmesg after following these steps:
1. Boot with a ubuntu/backtrack live iso
2. Mount the filesystem
mkdir /root/test
mount /dev/sda1 /root/test
3. And edit /etc/fstab of the mounted drive in /root/test/etc/fstab nano /root/test/etc/fstab and change to zero all counters..
Also if there is an error status writing “error=…” and “remount-ro” delete it and replace with “defaults” save the file and exit..
4. Type the following inline bash script to fix all drive errors:
for i in $(ls /dev/sd*);do e2fsck $i -C0;done
..and reboot..
After reboot check errors dmesg |grep mount
If the remount-ro message is missing, you are ok.. :p
That’s it..