Path: ...!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Michael Schwingen <news-1513678000@discworld.dascon.de>
Newsgroups: comp.sys.raspberry-pi
Subject: Re: TF cards v MicroSD
Date: 13 Jul 2024 08:17:01 GMT
Lines: 17
Message-ID: <slrnv94dvt.52n.news-1513678000@a-tuin.ms.intern>
References: <v2fl8d$snp$1@dont-email.me> <v2flij$12u5$1@dont-email.me>
 <dCF*u8TKz@news.chiark.greenend.org.uk> <v2k5p3$12jui$1@dont-email.me>
 <cCF*IP4Kz@news.chiark.greenend.org.uk>
 <slrnv63i2m.1cjlk.nlazicBEZ_OVOGA@mudrac.ffzg.hr>
X-Trace: individual.net RSZN/atedkFgGNyR8aSfbgHXD0hCX+hQHiLcFQ7kLn52NnDmgX
Cancel-Lock: sha1:yOF+HIu2TKaHc28JQZhlDN/HyPs= sha256:+KutHJK9TRt/jep7YIsZWQEzj8z4Jlj/OfAhY2e+EeU=
User-Agent: slrn/1.0.3 (Linux)
Bytes: 1415

On 2024-06-06, Nikolaj Lazic <nlazicBEZ_OVOGA@mudrac.ffzg.hr> wrote:
>
> you can test the card with "badblocks -o /report -t random -swv /dev/your_sd"
> and see the report.

I don't think that works - if I read the manual correct, badblocks writes
the same pattern to all blocks, it will not detect fake cards where multiple
blocks map to the same memory location.

You can use f3write / f3read. Those write files with known, non-repeating
patterns to fill the whole device (you need a filesystem for that), and then
verify them.

cu
Michael
-- 
Some people have no respect of age unless it is bottled.