From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Adrian C." Subject: Re: Computer suddenly failed Date: Tue, 28 Feb 2006 13:51:02 +0200 Message-ID: <7.0.0.16.0.20060228134704.01a95e98@foo.teinet.ro> References: <6639BA20B265594590E97DD72A8EE0359DA0C1@exosw.osw.ori.local> <6639BA20B265594590E97DD72A8EE0359DA0C1@exosw.osw.ori.local > Mime-Version: 1.0 Return-path: In-Reply-To: <6639BA20B265594590E97DD72A8EE0359DA0C1@exosw.osw.ori.local > References: <6639BA20B265594590E97DD72A8EE0359DA0C1@exosw.osw.ori.local> Sender: linux-admin-owner@vger.kernel.org List-Id: Content-Type: text/plain; charset="us-ascii"; format="flowed" Content-Transfer-Encoding: 7bit To: linux-admin@vger.kernel.org What hardware RAID controller is that? Some lspci and dmesg will also help. --Adrian At 01:05 PM 2/28/2006, you 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