So, I’m writing this post in the hopes that someone with more knowledge will read it and hopefully be able to track down the issue.
It started last Friday (February 8th) on my husbands Gateway laptop while he was at work. When he got home on Monday morning, he informed me of it – ‘I think I broke my computer…’ After looking at it for a little while, I realized that his file system had been marked ‘read-only’. A bit of googling informed me that this was usually a mark of a dying hard drive. After backing it up, I decided to try formatting and re-installing to see if that would, by chance, fix the problem. And it did! At least, initially. However, as soon as I updated all the packages and installed a couple of programs (Samba, Chromium), it reoccurred. Which made me suspect, initially that his hard drive as in deed dying or dead.
At approximately this point however, the exact same thing started happening on my laptop (a Lenovo IdeaPad). As a result I posted on ubuntuforums.com (http://ubuntuforums.org/showthread.php?s=19c5720cfb4ab8a14e1f6d7b264e6118&t=2115225) and was directed to a bug report (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354), which matches it. It appears to be a problem related to the kernel, though why it has taken several months to rear its ugly head I couldn’t say. In any case, I did a bit more googling and found a couple of ideas on how to fix it, at least temporarily. By booting into a live image of Ubuntu 12.10 I was able to run sudo dpkg-reconfigure -a – which fixed it on my laptop, mostly. It still goes into read-only mode, semingly at random, but a reboot immediately afterwards has, (thus far) fixed it.
The same can not be said for my husbands’ Gateway. After a third re-install of Ubuntu 12.10 (and giving him instructions to upgrade everything *except* the kernel), it worked fine for approximately 2 days, but has now reverted to read-only filesystem status, when booted. However, when I boot into a live image, the files do not appear to be read-only, and sudo dpkg-reconfigure -a has not worked the same way it did on mine😦. I think I’m going to try a fourth re-install (using 12.04), and hope that it remains functioning…
Any other suggestions are greatly appreciated!!