Re: scsi parity error
Am Monday, 10. October 2005 21:50 schrieb tony@mancill.com:
> My Asus A8V Athlon 3500 just started giving me these this morning
> (after 9 months of continuous usage), and unfortunately becomes
> unresponsive after only a few minutes of use. I'm frantically
> trying to get everything copied off of the SATA drive onto a PATA
> disk, and after that will look into it further. I'm running the
> stock 2.6.13 kernel, and the only thing that has changed was a
> recent apt-get upgrade run against unstable (last Sunday -
> hmmm....) Still, at this point I suspect a hardware failure.
But the disk itself is OK? I mean do you suspect the disk or the MB?
My machine is still running. 3 hours no without a problem.
Martin
>
> Good luck,
> tony
>
> On Mon, Oct 10, 2005 at 07:09:38PM +0200, Martin Kuball wrote:
> > Hi!
> >
> > I have a machine with a Asus A8N-SLI board, a AMD Athlon64 3500
> > and a Samsung SP1614C SATA-1 hard disk. I'm running debian sarge
> > with kernel 2.6.11 since may. Everything is OK, except for
> > occasional hang ups in GRUB. But otherwise very stable. Until
> > Last Saturday, when I got the following error(s):
> >
> > scsi error: <2 0 0 0> ret code = 0x8000002
> > sda: current: sense key: aborted command
> > addintional sense: parity error
> > end request: I/O error: dev sda, sector 3268390 (and others)
> > abnormal status 0xD0 on port 0x947
> >
> > The system was still responding, but I couldn't start any new
> > process more and more processes got blocked when trying to read
> > or write something. After a reboot everything was fine again.
> > Until Sunday evening when the same problem happened again.
> >
> > Now what could possibly cause this trouble? Is it the hard disk?
> > Is it the controller? I have not yet tried smartmon because it
> > does not work with sata disks and kernel 2.6.11. Does it work
> > with a recent kernel?
Reply to: