From: Manish Lachwani <m_lachwani@yahoo.com>
To: Aryix <aryix@softhome.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: another seagate for the black-list?
Date: Tue, 17 Dec 2002 07:52:55 -0800 (PST) [thread overview]
Message-ID: <20021217155255.31227.qmail@web20507.mail.yahoo.com> (raw)
In-Reply-To: <courier.3DFF30A8.000033A8@softhome.net>
>From dmesg that you sent me:
hdc: dma_intr: status=0x51 { DriveReady SeekComplete
Error }
hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdc: dma_intr: status=0x51 { DriveReady SeekComplete
Error }
hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdc: dma_intr: status=0x51 { DriveReady SeekComplete
Error }
hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdc: dma_intr: status=0x51 { DriveReady SeekComplete
Error }
hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide1: reset: success
hdc: dma_intr: status=0x51 { DriveReady SeekComplete
Error }
hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdc: dma_intr: status=0x51 { DriveReady SeekComplete
Error }
hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdc: dma_intr: status=0x51 { DriveReady SeekComplete
Error }
hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdc: dma_intr: status=0x51 { DriveReady SeekComplete
Error }
hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide1: reset: success
which shows CRC errors. And in this case, there will
be a UDMA downgrade. Send me the SMART data using
smartctl and replace the cabling. The drive is
initialized UDMA 66
hda: 58633344 sectors (30020 MB) w/418KiB Cache,
CHS=3649/255/63, (U)DMA
blk: queue c030a928, I/O limit 4095Mb (mask
0xffffffff)
hdc: 12596850 sectors (6450 MB) w/256KiB Cache,
CHS=13330/15/63, UDMA(66)
but the UDMA is downgraded on CRC. Thats the expected
behavior
--- Aryix <aryix@softhome.net> wrote:
> On Tue, 17 Dec 2002 06:07:34 -0800
> Manish Lachwani <manish@Zambeel.com> wrote:
>
> > Did you send me dmesg o/p?
> >
> > Send me e-mail at m_lachwani@yahoo.com since I
> will access that shortly
> >
> >
> >
> > -----Original Message-----
> > From: Aryix
> > To: Manish Lachwani
> > Sent: 12/17/02 5:48 AM
> > Subject: Re: another seagate for the black-list?
> >
> > On Tue, 17 Dec 2002 05:45:57 -0800
> > Manish Lachwani <manish@Zambeel.com> wrote:
> >
> > > When you use hdparm -X ..., can you also check
> dmesg for any IDE
> > warnings.
> > > Also, do a hdparm -I /dev/hdX
> > >
> Thank you!
>
--------------------------------------------------------------------------
> pub 1024D/BE8E00BE 2002-12-06 Aryix Berius
> (nothing) <aryix@softhome.net>
> Key fingerprint = 249D C5BC 8B9A C46A C7F4
> 397D 2A6D 9FF6 BE8E 00BE
> sub 2048g/C1C6CB29 2002-12-10 (linux.sophia.org.ar
> at 200.70.32.145)
>
>
> ATTACHMENT part 2 application/octet-stream
name=dmesg
__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
next parent reply other threads:[~2002-12-17 15:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <courier.3DFF30A8.000033A8@softhome.net>
2002-12-17 15:52 ` Manish Lachwani [this message]
2002-12-12 10:56 another seagate for the black-list? Aryix
2002-12-13 10:25 ` Måns Rullgård
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021217155255.31227.qmail@web20507.mail.yahoo.com \
--to=m_lachwani@yahoo.com \
--cc=aryix@softhome.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox