I have seen this question asked elsewhere, and originally I was going to post my question in one of those threads. But the forum rules popped up and told me that I'm only supposed to answer the original question in a reply, rather than asking for help. Which means that to ask my question, I need to start my own thread (which seems redundant).
I saw this question asked for 10.10 and 11.04, in this thread.
I also saw this one, which looks specifically Wubi-related
I'm having the same problem, but with 12.04, and unfortunately I'm not getting anywhere with the solutions that are being offered. (Probably because I don't understand what it's trying to do.) I have read through threads in this forum and others that seem related, but have not been able to make use of those solutions. I can attempt to follow the instructions there, but it doesn't accomplish anything.
I am not an experienced Ubuntu sysadmin. A few years ago, I used to use Ubuntu 8.04 pretty regularly (32-bit on a dedicated desktop system), and never had a problem. Then didn't use Ubuntu at all for a while. Now I have acquired a brand-new laptop, and I have (repeatedly) set it up with Ubuntu 12.04, which fails with this error every few days. The error seems unrecoverable, and I have to completely reinstall everything from the ground up, which very time-consuming and frustrating.
Lenovo Edge E530, 64-bit Intel core i7. The E520 was listed as certified hardware on the Ubuntu site, I was hoping the E530 would be good also.
Came with Win7 Pro 64-bit installed. I am using Wubi (Windows Ubuntu Installer) to make it into a dual-boot system with Ubuntu 12.04 64-bit. I know there are other ways of accomplishing the dual-boot setup, but this seemed like the fastest and easiest, and I'm not enough of a guru to think I can accomplish it any but the simplest way.
Ubuntu seems to install correctly. I can use it successfully for a few days, configuring it and adding the tools I need, and it seems okay. Then after a while, it simply fails. A couple times it was after running a system update and restarting, a couple times it's been after doing nothing at all except doing a shutdown and restart. I always do a proper shutdown, I do not at any time just power it down without executing a proper shutdown.
On restart, I see:
Checking disk drives for errors. This may take several minutes. Checking disk 1 of 1 (n% complete) Press C to cancel all checks in progress
I let it proceed uninterrupted. After a short time (usually when it's reached about 6% or 7% complete) I get this error:
The disc drive for / is not ready yet or not present
The disc drive for /tmp is not ready yet or not present
Press F to attempt to fix the errors, I to ignore, S to skip mounting, or M for manual recovery
Pressing "F" does nothing, just switches the message to
Continue to wait, or Press S to skip mounting, or M for manual recovery
I don't know anything about how to do a manual recovery. I tried the steps above, pressing M to get to a command-line screen, where I see the error:
Filesystem check or mount failed. A maintenance shell will now be started. CONTROL-D will terminate this shell and continue booting after re-trying filesystems. Any further errors will be ignored.
(Sometimes the first line is replaced by "
Root filesystem check failed.")
Then a bunch of errors like this:
[ 194.935443] loop: Write error at byte offset 29970400256, length 1024. [ 194.935457] Buffer I/O error on device loop0, logical block 30457792 [ 194.935514] Buffer I/O error on device loop0, logical block 30457793
and a command prompt. (There can be anywhere from half a dozen, to many screens-full of that error message.) I try to use the commands:
mount -o remount,rw / dpkg --configure -a mount -o remount,ro / sync reboot
as described previously in a related thread. The first command does nothing (gives no response except the next prompt). Is it silently failing, silently succeeding, or just doing nothing? And the second one gets an error of:
dpkg: warning: 'ldconfig' not found in PATH or not executable dpkg: error: 1 expected program not found in PATH or not executable Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin, and /sbin
So apparently something has whacked my PATH, and the 'ldconfig' executable can't be found. So it seems like if those are the right commands to fix this, they're not available to me.
Since I didn't have any other ideas of what to do, I just gave it a
CTRL-D to restart. And when I power up again, I'm in exactly the same state.
So, for now I will simply remove Wubi, and re-install everything again, and hope it'll be more than a couple days until the next time it fails on me. But I need to get this remedied, because I'm going to be using this system for school for at least the next nine months, and can't be rebuilding my system from the ground up every couple of days.
Is 12.04 inherently unstable in this way? Seems like a lot of people are seeing this problem, so I'm pretty sure it's not just something I'm doing.
Is the problem with trying to dual-boot? (I don't have any choice in that. I can't take Windows off, and I need Ubuntu for class.)
Is the problem with using Wubi? (If so, I could try to find a different way to make my system dual-bootable.)
When I execute the "
mount -o remount,rw /" command, what am I supposed to see, if anything?
This is getting to be extremely frustrating. I'm not doing anything unusual to the system. I haven't even had a crash. It's happening after normal-seeming shutdowns. I really like Ubuntu, and absolutely must have it installed for a class I'm taking. But having to tear down the whole system every few days and start over from scratch is getting ridiculous, especially since I am adding more tools and configuration to the system as I go, and have to repeat that every time as well.
Thanks for any assistance or explanations.