We'll, I did what you suggested. I booted into recovery mode, and ran fsck /dev/sda1.
It found a file system with errors. After fixing them, my system boots fine. Thanks for the help. I've never actually done a manual fsck check before. I do not think I have a failing hard disk though. I think hardy heron just never installed right, because i was having a few problems to begin with. One of which was an error in wine about an lspci sound error or something. The fsck check fixed something called that, so maybe wine will run OK now. I had just chalked all that stuff up to bugs, since hardy was still in alpha. I will keep an eye out for future file system errors nonetheless though. -Andrew Barney (keen101) -- When fsck fails, the machine reboots and does the check again https://bugs.launchpad.net/bugs/204097 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
