From mboxrd@z Thu Jan 1 00:00:00 1970 From: urgrue Subject: Re: Computer suddenly failed Date: Tue, 28 Feb 2006 13:26:22 +0200 Message-ID: <1141125982l.25013l.0l@hyttynen> References: <6639BA20B265594590E97DD72A8EE0359DA0C1@exosw.osw.ori.local> Mime-Version: 1.0 Content-Transfer-Encoding: 8BIT Return-path: In-Reply-To: <6639BA20B265594590E97DD72A8EE0359DA0C1@exosw.osw.ori.local> (from Peter.Jevos@Oriflame-SW.Com on Tue Feb 28 13:05:15 2006) Content-Disposition: inline Sender: linux-admin-owner@vger.kernel.org List-Id: Content-Type: text/plain; charset="us-ascii"; delsp="Yes"; format="Flowed" To: "Jevos, Peter" Cc: linux-admin@vger.kernel.org sounds like your hard drive is dead/dying. replace hde with a new disk. On 02/28/2006 01:05:15 PM, Jevos, Peter wrote: > Hi all > > I'd like to ask you about strange problem. I hope I chose a correct > mailing list > I have 2 IDE disks in RAID 1 with Reiserfs. > Once I noticed message in the log: > > hde: dma_timer_expiry: dma status == 0x20 > hde: timeout waiting for DMA > PDC202XX: Primary channel reset. > hde: timeout waiting for DMA > hde: (__ide_dma_test_irq) called while not waiting > hde: status timeout: status=0xd0 { Busy } > PDC202XX: Primary channel reset. > hde: drive not ready for command > ide2: reset: success > hde: status error: status=0x58 { DriveReady SeekComplete DataRequest > } > hde: drive not ready for command > hde: status error: status=0x58 { DriveReady SeekComplete DataRequest > } > > DMA on hde was turned off so I turned it on again. Than I tried to > made > files backup on the hde, but when I ran tar computer didn't response > even for sysrq, no log was written. I had to made a hard restart. It > repeats for 4 times when I tried to did something with files on the > hde. > Now I'm afraid to do anything on that machine,unfortunately it is > production server. > What's goning on ? > Thanks a lot for an answers > > BR > Pet > - > To unsubscribe from this list: send the line "unsubscribe linux-admin" > in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html >