Not sure if this will help anyone on this issue, but I just experienced it as 
well. For my own personal reasons, I have my android build environment on a 
separate partition. I opened it and decided to do some work on a project and 
suddenly all my partitions became read only. I found that after a reboot, I was 
forced to run fsck, but I also found that if I did not try to change anything 
in my android partition, that this error would not happen. I also noticed that 
prior to this error, when  I tried to compile any of my android projects, my 
computer would become very slow and seemingly overloaded. So... After a reboot, 
I ran fsck /dev/sda3 (my android partition)and now I am read only error free, 
and I am currently compiling a ROM, listening to youtube videos, typing out 
this reply and have supertuxcart (I love that game...lol) running in the 
background with no lag. So, my system is back up and running like it should be. 
Oh, and for your information:
Machine: Acer Aspire 5560
Kernel: Linux 3.5.0-25-generic (x86_64)
Distribution: Linux Mint 14 Nadia
Processor: 4x AMD A6-3400M APU with Radeon(tm) HD Graphics

I know Linux Mint is not Ubuntu, but it is still based on 12.10
I'm sure if this is happening on your main partition (/dev/sda1 for me), you 
would need to do this from a live cd.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1063354

Title:
  Sudden Read-Only Filesystems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063354/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to