From mboxrd@z Thu Jan  1 00:00:00 1970
From: kaushal <kaushal@rocsys.com>
Subject: Re: weird cd-drive behaviour
Date: 19 Jan 2005 11:29:16 +0530
Message-ID: <1106114356.9591.488.camel@kaushal>
References: <1106027068.9440.462.camel@kaushal> 
	<3446.192.168.99.70.1106061720.squirrel@192.168.99.70>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Return-path: <linux-admin-owner@vger.kernel.org>
In-Reply-To: <3446.192.168.99.70.1106061720.squirrel@192.168.99.70>
Sender: linux-admin-owner@vger.kernel.org
List-Id: <linux-admin.vger.kernel.org>
Content-Type: text/plain; charset="us-ascii"
To: Scott Taylor <scott@dctchambers.com>
Cc: admin <linux-admin@vger.kernel.org>

hi Scott,
	The hdd is having few bad clusters ,but in the C drive and why should
linux (Win=C,D,E;Linux rest of the disk)report it as a problem.What
about the corrupt /dev node.I couldn't get you.The configuration is:
	40GB samsung hdd.
	Intel 815E motherboard.
	PIII processor.
	samsung 52X cd-drive.
	Windowx XP
	Fedora core-1
	Grub.
Can this is a problem due to faulty IDE-slot/IDE-connector?Is there any
s/f or method  by which I can test the integrity of my motherboard and
its components?
Thanks in advance.
kaushal 
On Tue, 2005-01-18 at 20:52, Scott Taylor wrote:
> 
> kaushal said:
> > Hello all,
> > 	My cd-drive is behaving weirdly when I insert a cd-rom in it.It reacts
> 
> Some info on your operating system, distribution, version might be helpful.
> 
> <snip>
> > hdd:command error:status=0x51 {Drive Ready SeekComplete Error}
> > hdd:command error:error=0x54
> 
> Must be a Maxtor drive.
> 
> > After those error messages the system got stuck.Then I restarted the m/c
> 
> m/c?
> 
> > and the /var/log/messages showed the following two messages at two
> > different times:
> >
> > kernel:hda:hda:dma_intr:status=0x51 {Drive Ready SeekComplete Error}
> > kernel:hda:dma_intr:error=0x84 {Drive StatusError Bad CRC}
> 
> Hard drive is corrupt and getting seek errors, very common amongst cheap,
> Maxtor drives.
> 
> > I guess there is some system initialization problem.
> >  or DMA problem(last 2 messages}
> 
> > Please help me in this aspect.Any way to debug further and diagnose and
> > corner the faulty section?
> 
> Well, try replacing anything yet?  My guess is the hard drive, seems how
> that is what your OS is trying to tell you.  The first problem might be a
> CDROM trying to mount to a corrupt /dev node.
> 
> Let us know if your hard drive is a Maxtor, what size, and how old is it.
> 
> --
> Scott
> -
> 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