On Mon, Mar 27, 2006 at 12:44:50PM -0500, linux-os (Dick Johnson) wrote:
> Experimental data show that it is not possible to 'destroy' the
> chip by interrupting a write as previously reported by others.
> In fact, one of the destroyed devices was recovered by writing
> all the sectors in the device as in:
> `dd if=/dev/zero of=/dev/hdb bs=1M count=122`.
I have a destroyed card here. And I tried doing that. A rep from
sandisk told me, that yes that model/generation of sandisk could
encounter that situation where the device was simply impossible to
access because of corruption during a write. He also said the card
would have to be sent back to the factory to have the table reset.
Newer generations were going to fix that so it didn't happen again.
> Note that there __is__ a problem that may become a "gotcha" if
> you intend to RAW copy devices, one to another, for production.
> The reported size (number of sectors) is different between
> devices of the same type and manufacturer! Apparently, the size
> gets set when the device is tested.
Yeah, I load cards by partitioning, mkfs'ing, and extracting data.
Different manufacturers almost never have the same excact size.
Len Sorensen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
