It's absolutely possible. The disk itself hasn't really *failed* although its probably on its way, you just got some corruption that the journaling couldn't correct. While its mounted RO, fsck it. This could also be related to other issues like bad cables or worse a flaky drive controller. Although you'd probably see issues on the other partitions then. You might consider turning down your hdparm settings also.
This happens to me from time to time on my laptop's HD. It started when the MB went flaky, and I never re-installed gentoo after it was replaced. A quick fsck and its fixed for a while. Of course if key parts of your glibc are corrupted thats a different matter :( I'd try re-emerging after the fsck just to be sure. > Hi, > 1h ago on my server partition with / was remounted readonly - its hda1 > - because disk failure I think. > There is somthing in dmesg: > EXT3-fs error: (device hda1) in start_transaction: Journal has aborted > /tmp is also on hda. When I try to write on / it says it's readonly, > but on /tmp it writes successfully. > Is it possible that failure of hard disk is only on one partition?? or > is it some kind of software failure? All other disks, those heavyly > used too, are still working. On / I have whole gentoo with logs, /tmp > is on hda2, swap is on hda4 but it wasn't used much and it still > works. > This failure happend while glibc was qmerged to filesystem... :/ > please help > > -- > [email protected] mailing list > > ---- Chris Ripp <[EMAIL PROTECTED]> http://ripp.net/ -- [email protected] mailing list
