Fedora Core 5 Issues
Roger
roger at wack.co.za
Tue Aug 15 10:05:10 UTC 2006
On Tue, 2006-08-15 at 10:16 +0100, Andy Green wrote:
> Roger wrote:
> > Has anyone had issues with Fedora Core 5 64bit version. I tried to use
> > it for one of my production servers and i had endless issues trying to
> > get it to work, first i had the segfaults caused by some of my
> > processes. Then the SATA drivers started giving errors and eventually my
> > hard drive started failing etc. I believe in Fedora and dumped FC5 for
>
> I used FC5 on x86_64 for several months completely happily. Then a
> couple of months ago that box killed first one SATA drive (this is on
> nVidia SATA driver/controller) and then after one week, its replacement
> SATA drive. By 'killed' I mean I came in one morning and the drive is
> repeatedly resetting itself on a 10-or-so second cycle, will not boot,
> etc. I abandoned the whole PC and moved my life into a laptop.
>
> I have three ideas what may have happened:
>
> - Power supply problem: the 12V became weak and unstable and the drive
> kept "powering up". Problem with believing this is that there were few
> devices in the box, and there had been no changes to the roster of
> devices in there for months
>
> - Driver problems: on a later kernel, changes in the driver cause it
> to try to reset the drive and there are problems with the logic that it
> will keep doing so until it kills the drive, perhaps because the drive
> firmware does not always handle soft resets properly (on a WD and a
> Seagate though?)
>
> - Karmic burden from a past life caught up with me and it is just random
>
> Please describe what happened with your dead drive.
>
> -Andy
> --
> fedora-list mailing list
> fedora-list at redhat.com
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
I installed FC on my new Intel 64 bit with SATA drives and i was
overwhelmed by the performance such that i decided to replace my very
old mail server which had been very faithful to me, it was a sad day
indeed. Then on the second day my logfile reported the following
Jul 16 10:29:57 asterix kernel: qmailadmin[13468]: segfault at
0000000000000000 rip 0000003f2a064da1 rsp 00007fffffcd37f0 error 4
Jul 16 10:30:00 asterix kernel: qmailadmin[13469]: segfault at
0000000000000000 rip 0000003f2a064da1 rsp 00007fffff9277d0 error 4
Jul 16 10:30:15 asterix kernel: ata1: handling error/timeout
Jul 16 10:30:15 asterix kernel: ata1: port reset, p_is 0 is 0 pis 0 cmd
4c017 tf 7f ss 0 se 0
Jul 16 10:30:15 asterix kernel: ata1: status=0x50 { DriveReady
SeekComplete }
Jul 16 10:30:15 asterix kernel: sda: Current: sense key: No Sense
......
Jul 16 19:50:18 asterix kernel: tcpserver[13903]: segfault at
0000000000000064 rip 00000000004049a0 rsp 00007fffffdf8a98 error 6
Jul 16 19:50:18 asterix kernel: tcpserver[13904]: segfault at
0000000000000064 rip 00000000004049a0 rsp 00007fffffdf8a98 error 6
Jul 16 19:50:18 asterix kernel: tcpserver[13905]: segfault at
0000000000000064 rip 00000000004049a0 rsp 00007fffffdf8a98 error 6
Jul 16 19:50:18 asterix kernel: tcpserver[13906]: segfault at
0000000000000064 rip 00000000004049a0 rsp 00007fffffdf8a98 error 6
Jul 16 19:50:18 asterix kernel: ata1: handling error/timeout
Jul 16 19:50:18 asterix kernel: ata1: port reset, p_is 0 is 0 pis 0 cmd
4c017 tf 7f ss 0 se 0
Jul 16 19:50:18 asterix kernel: ata1: status=0x50 { DriveReady
SeekComplete }
Jul 16 19:50:18 asterix kernel: sda: Current: sense key: No Sense
Jul 16 19:50:18 asterix kernel: Additional sense: No additional
sense information
Jul 16 19:50:18 asterix kernel: tcpserver[13907]: segfault at
0000000000000064 rip 00000000004049a0 rsp 00007fffffdf8a98 error 6
Jul 16 19:50:18 asterix kernel: tcpserver[13908]: segfault at
0000000000000064 rip 00000000004049a0 rsp 00007fffffdf8a98 error 6
Jul 16 19:50:18 asterix kernel: tcpserver[13909]: segfault at
0000000000000064 rip 00000000004049a0 rsp 00007fffffdf8a98 error 6
Jul 16 19:50:18 asterix kernel: tcpserver[13910]: segfault at
0000000000000064 rip 00000000004049a0 rsp 00007fffffdf8a98 error 6
etc.
I reset the machine and the machine worked for 7 seven days then it
stopped and gave the ata1: handling error timeout. Then 4 or days it
would run and then just suddenly stop, and i was thinking that maybe it
is a hard drive error. But what happens now is that the hard drive
starts to just die and then i guess switches to read-only mode and i
cant even use ssh to get into the machine, such that i always reset it,
but when i do it just runs for 4 days max and then just dies, do you
reckon it to be the hard drive that is now weak or what.
I have since replaced that server with a smaller machine running on FC3
with but uses a lot less memory and does not complain at all.
Do you reckon it could be the SATA Drivers which kill the hard drives!
Regards
Roger
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/fedora-list/attachments/20060815/346f7e0a/attachment-0001.htm>
More information about the fedora-list
mailing list