public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Matt Schulkind" <mschulkind@mailandnews.com>
To: <linux-kernel@vger.kernel.org>
Subject: Re: HPT370 (KT7A-RAID) *corrupts* data - SAMSUNG SV8004H does it as well
Date: Sat, 1 Dec 2001 13:19:22 -0500	[thread overview]
Message-ID: <00dc01c17a94$b37c2290$0500a8c0@myroom> (raw)

> On Sat, Dec 01, 2001 at 11:34:00AM +0100, you
[Sven.Riedel@tu-clausthal.de] claimed:
> > On Sat, Dec 01, 2001 at 11:58:03AM +0200, Ville Herva wrote:
> > > - how come anyone else is not seeing this corruption (Abit KT7A,
nevermind
> > >   HPT370 is fairly popular)?
> >
> > A friend of mine had an IBM DLTA drive attached to his HPT370
> > controller, and this combination proved to produce a whole lot of drive
> > errors (I can confirm this first hand), which went away after attaching
> > the drive to the main motherboard controller.
> > I can't say anything about data corruption though - I just asked him and
> > he said he didn't know of any, but that doesn't mean it didn't happen.
>
> Of course the drive is longer attached to HPT370 and your friend is
propably
> reluctant to reattach it, but it would still be nice to know if he gets
> consistent results which for example this simple test:
>
>   cat /dev/hde | mdsum
>
> run for several (5-10, perhaps) times.
>
> OTOH, I haven't had corruption with reading only
> one disk at a time, but then again I haven't tried too hard as they
> should really work in parallel.
>
>
> -- v --
>
> v@iki.fi
> -

In my experience, the HPT370 chipset likes corrupting harddrives. When I was
using it, I had the PCI Raid version and it kept corrupting my hard drives.
I tried updating the BIOS, but the bios program locked up and completly
killed my board. When I RMAed the board, the new BIOS was put on for me and
after that I ahven't had a single problem. Maybe you should try upgrading
the BIOS, but I don't know if you can for an onboard version.

-Matt Schulkind



             reply	other threads:[~2001-12-01 18:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-01 18:19 Matt Schulkind [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-12-04  4:44 HPT370 (KT7A-RAID) *corrupts* data - SAMSUNG SV8004H does it as well gdf
2001-12-04 12:59 ` Ville Herva
2001-12-04 16:01   ` Lee Packham
2001-12-04 17:04   ` William N. Zanatta
2001-12-04 19:25     ` Ville Herva
2001-12-01  9:58 Ville Herva
2001-12-01 10:34 ` Sven.Riedel
2001-12-01 10:39   ` Ville Herva
2001-12-02  5:51     ` Sven.Riedel
2001-12-04 18:15 ` Jonathan Amery
2001-12-04 19:26   ` Ville Herva
2001-12-04 22:23 ` Anthony DeRobertis
2001-12-05 22:53   ` Ville Herva

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='00dc01c17a94$b37c2290$0500a8c0@myroom' \
    --to=mschulkind@mailandnews.com \
    --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