Looks like in my case, the issue did end up being hardware.. or 3.5+
kernel fault tolerance. After doing multiple SMART scans and replacing
my cabling and still getting corruption (but only in 3.5+ kernels while
3.2 continued to be ok), I finally removed the hard drive from the case
bay (which has
gunwald, my file has "max_performance" in it. did you completely delete
the line or change it to something else?
--
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 Filesy
I have been following this bug from close to when it was first posted
(because I had the same issue myself) and I am now convinced that this
has become a gathering place for people who all have different hardware
issues which all end up producing the noticable issue of the hard drive
going into rea
Missed an extra step to take if you are using a SSD... make sure you
have the most up-to-date firmware (as mentioned by Mark above in this
thread).
Probably not a bad idea for everyone to check if their motherboard BIOS
is up-to-date as well.
--
You received this bug notification because you are
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/827975
Title:
package postgresql-common 114 failed to install/upgrade: subprocess
installed post-installation script returned error exit status 1
To m
Public bug reported:
Error came on routine upgrade this morning.
ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: postgresql-common 114
ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7
Uname: Linux 2.6.38-10-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date:
I updated from 12.04 to 12.10 (AMD 64bit) last night and have been
having this exact same problem. I have a fairly new WD 750Gig black HD
with / and /home partitions. Through-out the day, either / or /home has
been suddenly going into read-only mode and all I can do is reboot to
get it back to no
I have been using 12.10 BUT booting with the 3.2.0-32 kernel and have
not the problem at all anymore. I just tried booting into 3.5.0-17
again and the problem happened within minutes. If I get a chance I will
try installing some other kernels to test with.
--
You received this bug notification
On the weekend I installed and tried booting with the kernels mentioned
in an above post: v3.3 final, v3.4 final, and v3.5-rc4. I couldn't
reproduce the problem with any of these. I am currently running with
v3.5-rc4 and will stick with that until this issue is resolved.Once
again, I am run
For other people experiencing this problem, I suggest installing
smartmontools and doing some tests on your HD to rule out actual
hardware problems. Also, try booting with an older kernel from the grub
boot menu and see if your issue goes away (because if not, you may
actually have failing hardwar
I am trying 3.5.0-20 as well, and while it has not yet gone read-only, I
AM still seeing write errors in /var/log/syslog
--
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
@jsalisbury are there any other kernels you would like to have tested?
I have been running a number of days now on v3.5-rc4 without this
problem coming up, but I can test with some others if needed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
@derlars I did try the latest kernel again and got the problem to happen
once on boot already and another time after about 2.5 hours. I will try
out some of the kernels between rc4 and latest.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
I tried 3.5-rc5 and got the problem fairly quickly. Went back to
3.5-rc4 and noticed I was getting ext4 buffer write sda errors in syslog
for that as well... so it might be that 3.5-rc4 doesn't actually work
for me either, although I haven't had rc4 go into read-only mode at all
yet. Since yester
I just recently found out about the problems with ext4 corruption (as
mentioned in http://lwn.net/Articles/521022/ ) and am now wondering if
this is all related to that? Except that that bug is only supposed to
happen in rare cases, nothing like what I've been seeing. Also don't
understand why mo
Noticed that kernel 3.5.0-18 was included in my updates today so I just
tried booting with it. Within minutes I started getting errors in my
/var/log/syslog as follows:
Nov 6 17:04:31 Woogie kernel: [ 1676.289748] Buffer I/O error on device sda3,
logical block 96221046
Nov 6 17:04:31 Woogie ke
Wallo013, I believe there is not a consistent pattern to the issue yet.
Read all the posts here and you can see some people not having problems
with kernel 3.5.0-17 but do with 3.5.0-18... whereas myself I can't
reliably use any 3.5.* kernel it seems. I'm still not convinced that I
(and all others
I've been using 12.10 but have continued booting with the old 3.4.0
kernel for about 2 weeks now and have had no problems. I just installed
the 3.5.0-19 kernel and will see how I do with that... will report back
soon.
AMD Phenom X4 / ASUS M4A87TD / 16Gig DDR3 / 750M WD SATA HD / NVIDIA
GeForce 52
After using kernel 3.5.0-19 for 5 days I am still getting file
corruption reported in syslog, but not nearly as much as before (or
perhaps just seems that way). Going back to 3.4 again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
19 matches
Mail list logo
