All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <willy@w.ods.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Compactflash cards dying?
Date: Mon, 3 Feb 2003 00:57:59 +0100	[thread overview]
Message-ID: <20030202235759.GA6859@alpha.home.local> (raw)
In-Reply-To: <20030202223009.GA344@elf.ucw.cz>

Hi Pavel !

I had this same problem with my very first CF (16 MB) connected to a home-made
IDE adapter. I quickly discovered that the power wire (+5V) had been cut and
that the power was driven through the logic signals, which were strong enough
to let the card work correctly... nearly correctly. Because it got uncorrectable
defects, detected as bad sectors at IDE level. So may be your adapter is too
weak. Or may be you also use it in a battery-powered device which has frequent
power outages ?

Cheers,
Willy

On Sun, Feb 02, 2003 at 11:30:09PM +0100, Pavel Machek wrote:
> Hi!
> 
> I had compactflash from Apacer (256MB), and it started corrupting data
> in few months, eventually becoming useless and being given back for
> repair. They gave me another one and it is just starting to corrupt
> data.
> 
> First time I repartitioned it; now I only did mke2fs, and data
> corruption can be seen by something as simple as
> 
> cat /mnt/cf/mp3/* > /mnt/cf/delme; md5sum /mnt/cf/delme.
> 
> [Fails 1 in 5 tries].
> 
> Anyone seen something similar? Are there some known-good
> compactflash-es?
> 
> 								Pavel
> -- 
> Worst form of spam? Adding advertisment signatures ala sourceforge.net.
> What goes next? Inserting advertisment *into* email?
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

  reply	other threads:[~2003-02-02 23:53 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-02 22:30 Compactflash cards dying? Pavel Machek
2003-02-02 23:57 ` Willy Tarreau [this message]
2003-02-03 12:53   ` Pavel Machek
2003-02-03  0:36 ` Daniel Egger
2003-02-03  2:04   ` Martin K. Petersen
2003-02-03  8:39     ` Jörn Engel
2003-02-03 13:58       ` Martin K. Petersen
2003-02-03  8:50   ` Miquel van Smoorenburg
2003-02-03  7:12 ` Bryan Andersen
2003-02-03 14:08   ` Martin K. Petersen
2003-02-03 14:10     ` Padraig
2003-02-03 14:30       ` John Bradford
2003-02-03 14:25     ` John Bradford
2003-02-03 21:18       ` Bryan Andersen
2003-02-04 20:59       ` Bill Davidsen
2003-02-04 21:07         ` John Bradford
2003-02-03  7:30 ` Andreas Jellinghaus
2003-02-03 12:54   ` Pavel Machek
2003-02-03 23:12     ` David Woodhouse
2003-02-04  3:39       ` H. Peter Anvin
2003-02-04 11:24       ` Pavel Machek
2003-02-04 11:30         ` David Woodhouse
2003-02-04 19:28           ` Pavel Machek
2003-02-03 23:56 ` Roger Larsson
2003-02-04  0:10   ` David Woodhouse
2003-02-04 23:28     ` Pavel Machek
2003-02-04  0:34   ` Andrew McGregor
2003-02-04 23:27   ` Pavel Machek

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=20030202235759.GA6859@alpha.home.local \
    --to=willy@w.ods.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.