Got bit by this bug last weekend. My setup had a 20GB loop file on C:\, so I don't know how that affects @ago's diagnosis in #105.
This same bug is also the subject of http://ubuntuforums.org/showthread.php?t=1317397, and the guess there is that it has something to do with initscripts_2.87dsf-4ubuntu12_i386. See item #34:
<blockquote>It is because of the package initscripts_2.87dsf-4ubuntu12_i386 which is installed as an update. This changes the initrd scripts. So the solution is to revert back to the original initrd file in /boot. Mount the root.disk inside the live CD or Virtualbox(for those those who have only the iso) and copy the following file to the /boot after taking the backup of original initrd.img-2.6.31-14-generic which is found in the /boot of the LiveCD or the VBox machine. This would solve the problem</blockquote>
Can't confirm the above, though. I did reinstall with Wubi and just skipped that file altogether in the updates. So far it's okay.
Got bit by this bug last weekend. My setup had a 20GB loop file on C:\, so I don't know how that affects @ago's diagnosis in #105.
This same bug is also the subject of http:// ubuntuforums. org/showthread. php?t=1317397, and the guess there is that it has something to do with initscripts_ 2.87dsf- 4ubuntu12_ i386. See item #34:
<blockquote>It is because of the package initscripts_ 2.87dsf- 4ubuntu12_ i386 which is installed as an update. This changes the initrd scripts. So the solution is to revert back to the original initrd file in /boot. Mount the root.disk inside the live CD or Virtualbox(for those those who have only the iso) and copy the following file to the /boot after taking the backup of original initrd. img-2.6. 31-14-generic which is found in the /boot of the LiveCD or the VBox machine. This would solve the problem< /blockquote>
Can't confirm the above, though. I did reinstall with Wubi and just skipped that file altogether in the updates. So far it's okay.