I went back to the point before upgrading to 2.6.31.13 I installed your repository I did sudo apt-get -f install sudo apt-get --fix-missing install sudo apt-get clean sudo apt-get update sudo apt-get dist-upgrade sudo apt-get clean sudo apt-get autoremove
I checked if the VirtualBox drive is in /etc/fstab groan I now call it VBd Then I booted: Same hang. How can I go shure, that the new update to 2.6.31-13 is made before your ~beta5 is installed? BTW I removed the VBd from /etc/fstab and it was o.k. which is IMHO a slightly different scenario, because when upgrading the VirtualBoxGuestadditions are not active any more. So I booted again with Guestadditions installed (and no VBd) -> o.k. I activated the VBd and booted -> let me say it this way: I stared that long on the ubuntu logo that I can see it on this page as dark violett halo. The good news for you: I can't bother you with screenshots because they are all black. ;-) So I tried it with 2.6.31-12 generic (and your mountall, I did NOT go back this time) -> same freeze. And by typing this essay of #...@!* bugs it becomes clear to me: please give me ~beta6 because without ~beta5 nothing goes, with ~beta5 nothing goes either. -- difficult to recover from filesystem errors https://bugs.launchpad.net/bugs/432237 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
