RE: Hard disk problems

[Ernest Ellingson]

Title: Message

Here's some more information on this problem.  I got the machine up and running, logged in changed to root, did an fsck -ANV.  No problems reported.  I ftp'd to a local server, retrieved a file.tar.gz.  gunzipped the file OK, then applied tar xvf OK then I did a make.  No problem.  Then I got the error.  Hit a cairrage return and returned to the prompt.  Did another fsck , no problem reported.  Then the disk started churning.  I did a top.  Saw rebuilddb running as the top most pid.  That ended and the problem automagically disappeared. ( I thought).  Am in the process of doing up2date on this machine.  Went through most of initial stuff without a hitch.  But as the packages are coming in and being installed I get this error (at the bottom of this email) repeatedly.  It simply slows down the up2date, doesn't kill it.  It's still going on.  It seems that when files are written or deleted the problem occurs sporadically.  I noticed it occurs more often on big files than on smaller ones.    My question remains ("Does this mean the disk is bad?) New question ("Could it be the controller?") Another new one("Is there a way to change the ide_dmaproc timeout?")   Ernie -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Ernest Ellingson Sent: Tuesday, February 04, 2003 12:25 PM To: [EMAIL PROTECTED] Subject: RE: Hard disk problems I never get a chance to run up2date.  The message below occurs right after the install, on the first boot from the hard drive.  I've installed it 3 times now after pulling the modem and the sound card to reduce IRQ conflicts that may be causing the problem.  None of this has helped.  I still see the error.   Ernie -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Douglas Myers Sent: Tuesday, February 04, 2003 12:10 PM To: [EMAIL PROTECTED] Subject: Re: Hard disk problems I would guess since you ran up2date, you updated kernel rpm as well? Maybe to 2.4.18-X?   I saw this same thing, when I installed 8.0 yesterday, except with hdc (first cdrom) both my hard disks were fine. I hadn't seen this in 6.2 or 7.3 running same hardware, so I suspected some sort of change on the install.   I upgraded to 2.4.20 (not because of this, because I wanted to), and using essentially same config; problem immediately went away, any chance that kernel-2.4.18.X might have a problem from RH?   -------Original Message-------   From: [EMAIL PROTECTED] Date: Tuesday, February 04, 2003 08:06:11 To: [EMAIL PROTECTED] Subject: Hard disk problems   Managed to install redhat 7.1 and up2date it on two computers this weekend after struggling with a few issues and thanks to the help I received here finished without problems. The machines are running great. I've installed 7.1 on a third machine last night. However, I'm running into a problem. This shows up after I've logged in. hda: timeout waiting for DMA ide_dmaproc: chipset supported ide_dma_timeout func only: 14 hda: irq timeout: status=0x58 {Drive Ready SeekComplete DataRequest} hda: DMA disabled hda: Drive not ready for command. Does this mean the hard drive is bad? Or is something else going on? I can't run fsck because no prompt is available. I tried re-installing with a check for bad blocks. It took a little longer but the install occurred. I was able to log on again, but started receiving this above message again. Any advice? Ernie -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list . ____________________________________________________   IncrediMail - Email has finally evolved - Click Here