• Re: [gentoo-user] Re: problem formatting new 256 GB USB stick : f3

    From Philip Webb@21:1/5 to All on Tue Feb 18 04:50:02 2025
    250217 Michael wrote:
    It is worth mentioning the sys-block/f3 package (Fight Flash Fraud),
    which is in Portage and can test a USB flash disk to discover if it is fake. Besides the slower f3write and f3read, the f3probe command
    will only take a few minutes and confirm the available space.

    Thanks ! -- 'f3write' + 'f3read' refused, as they expect a directory ; 'f3probe' need it to be compiled with 'USE="extra"', but does work :

    root:705 ~> f3probe /dev/sdb
    F3 probe 8.0
    Copyright (C) 2010 Digirati Internet LTDA.
    This is free software; see the source for copying conditions.

    WARNING: Probing normally takes from a few seconds to 15 minutes, but
    it can take longer. Please be patient.

    Probe finished, recovering blocks... Done

    Good news: The device `/dev/sdb' is the real thing

    Device geometry:
    *Usable* size: 231.05 GB (484540416 blocks)
    Announced size: 231.05 GB (484540416 blocks)
    Module: 256.00 GB (2^38 Bytes)
    Approximate cache size: 0.00 Byte (0 blocks), need-reset=no
    Physical block size: 512.00 Byte (2^9 Bytes)

    Probe time: 5'29"
    root:706 ~> f3probe /dev/sdb
    F3 probe 8.0
    Copyright (C) 2010 Digirati Internet LTDA.
    This is free software; see the source for copying conditions.

    WARNING: Probing normally takes from a few seconds to 15 minutes, but
    it can take longer. Please be patient.

    Probe finished, recovering blocks... Done

    Good news: The device `/dev/sdb' is the real thing

    Device geometry:
    *Usable* size: 231.05 GB (484540416 blocks)
    Announced size: 231.05 GB (484540416 blocks)
    Module: 256.00 GB (2^38 Bytes)
    Approximate cache size: 0.00 Byte (0 blocks), need-reset=no
    Physical block size: 512.00 Byte (2^9 Bytes)

    Probe time: 18'47"

    -- end of output --

    That's both sticks : NB the 2nd took 3 times as long.

    So both sticks are genuine, as I would expect from that store.

    I plan to try 'gparted' next, instead of 'fdisk'
    & will send the results when I get them.

    BTW yes, we do have consumer protection laws in Ontario.
    I once was able to exchange a defective dictionary at a bookstore :
    one of the signatures (bindings) was missing & another was repeated,
    so it was clearly unfit for its purpose & someone somewhere shd have checked.

    Also, the sticks didn't feel warm after their exercises ;
    'glance' is in Gentoo & might help show the details :
    I'll have a look at it.

    Thanks for all the interest : there's more yet (smile) !

    --
    ========================,,============================================
    SUPPORT ___________//___, Philip Webb
    ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto
    TRANSIT `-O----------O---' purslowatcadotinterdotnet

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Philip Webb@21:1/5 to All on Tue Feb 18 07:00:01 2025
    250218 Grant Edwards wrote:
    On 2025-02-18, Philip Webb <purslow@ca.inter.net> wrote:
    So both sticks are genuine, as I would expect from that store.
    Have you tried just doing mkfs.ext4 [options] /dev/sdb?
    You only want one filesystem, right? Why bother with a partition table
    if you don't want to partition the device?

    It had an M$ partition when I bought it. I replaced that with 4 partitions because using a 2/3.2 port took > 10 h to write a 256 GB filesystem & fail, whereas it took only 2 h 45 m to write a 64 GB partition & fail.

    FYI I bought 4 Kingston 128 GB sticks in 2023 & had no problem with them. At that time, the store didn't offer 256 GB sticks.

    --
    ========================,,============================================
    SUPPORT ___________//___, Philip Webb
    ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto
    TRANSIT `-O----------O---' purslowatcadotinterdotnet

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Frank Steinmetzger@21:1/5 to All on Tue Feb 18 10:20:01 2025
    Am Tue, Feb 18, 2025 at 12:53:42AM -0500 schrieb Philip Webb:
    250218 Grant Edwards wrote:
    On 2025-02-18, Philip Webb <purslow@ca.inter.net> wrote:
    So both sticks are genuine, as I would expect from that store.
    Have you tried just doing mkfs.ext4 [options] /dev/sdb?
    You only want one filesystem, right? Why bother with a partition table
    if you don't want to partition the device?

    It had an M$ partition when I bought it. I replaced that with 4 partitions because using a 2/3.2 port took > 10 h to write a 256 GB filesystem & fail,
    whereas it took only 2 h 45 m to write a 64 GB partition & fail.

    FYI I bought 4 Kingston 128 GB sticks in 2023 & had no problem with them. At that time, the store didn't offer 256 GB sticks.

    BTW, in case you come into this position again that you need mobile storage.
    I recommend an external USB case with an NVMe SSD inside. This may not be as compact and not as cheap, but they are much much much faster and prolly longer-lasting than any USB “stick”, b/c their flash controllers are more sophisticated and the parts of higher fidelity. A not-too-cheap NVMe will do fine, as long as it’s TLC, not QLC flash. And when used behind USB, an on-board DRAM cache is beneficial if you deal with many small files.

    A good metal case with 10 Gbps USB is around 20 bucks, and the older Kioxia Exceria G2 with 500 GB and DRAM can be had for 35 € on the Old Continent’s market. No idea about Canadian prices though.

    --
    Grüße | Greetings | Salut | Qapla’
    Please do not share anything from, with or about me on any social network.

    Latin: the late revenge of the Romans to all Germans.

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEEVbE9o2D2lE5fhoVsizG+tUDUMMoFAme0TzcACgkQizG+tUDU MMoS/BAAknsgwFXQ8bKpRLEM2/cwmMgWWElPfn9842Vc9BRn5tudC4YoyCEC0lrI yWGo3fYG51FvMw4cT9Ap+9OJF7M6AIaqVjmoRwUEw4cqn0DabFyKB+GrjJm3yz7w VGE7siXODJS7AwtUWBjq2+YRj84vp0z5zKmh1tZtrqxb4lltHClppowSEvrgogUL 2/WteivuINpjmBUK3LWwBZCYK24lUrR9m64gkqp6MLWTVhqgJ2Tw/7yPzWyiMkLv PnBsK9j7aN7lpDOKVaK9r6XU16vH0Ey6oct5pXhaTAs8XvA9Ck1RfruYMhXmtWNa wgCLrIgG+rxFhEXIhgp16C66XoZWbHz2z5XNqX0a83eC50eoKlmL5M9WHugthcpg S9NK91/C6XLxYoWNJMf7U+fMUPx3Urk86BRC4ykxyH6LcgosRX0IbuNLw/eRDWD7 pQULZLi9Ybm9Unfa7LV53Tr8YEDVykScpjrwfkiW4yedLU9sj6//Fr28qlI313Du c3taQKBbsQymyelc1PUuH5vllM/JUWpOXXy5RGpLMPjVKLitajt4iKaPf0EbYzqQ UiA3MdFQ2ZGGzcpHh3tY7YK1c9I+kdBVHttgdiggKCYrLPHrPcevRYnHXx8fUnl4 fHakEDsYTL9SkDhb8KYa9RK2hx465hVX/M3YyltHhN7HIZQsPXo=
    =dCGO
    -----END PGP SIGNATURE--
  • From Michael@21:1/5 to All on Tue Feb 18 11:57:57 2025
    On Tuesday 18 February 2025 03:46:26 Greenwich Mean Time Philip Webb wrote:
    250217 Michael wrote:
    It is worth mentioning the sys-block/f3 package (Fight Flash Fraud),
    which is in Portage and can test a USB flash disk to discover if it is fake. Besides the slower f3write and f3read, the f3probe command
    will only take a few minutes and confirm the available space.

    Thanks ! -- 'f3write' + 'f3read' refused, as they expect a directory ;

    The man page explains how to run these commands. You need to provide the mountpoint directory for the device after you mount it, e.g.:

    $ f3write /run/media/<username>/XXXX-XXXX

    then,

    $ f3read /run/media/<username>/XXXX-XXXX

    You'd probably want to create one big partition for the whole device, or no partition at all, i.e. run something like this:

    # mkfs.fat -F 32 -n New-USB1 /dev/sdb

    The f3write/f3read commands will check the large files written by f3 can be accessed and read without any problem and flag up any sectors which contain corrupted data.


    'f3probe' need it to be compiled with 'USE="extra"', but does work :

    root:705 ~> f3probe /dev/sdb

    The f3probe command needs to be run as root, after you unmount the device.
    From your prompt I expect you did this, but it is also advisable to run it destructively - any data on the sticks will be overwritten:

    f3probe --destructive --time-ops /dev/sdb


    F3 probe 8.0
    Copyright (C) 2010 Digirati Internet LTDA.
    This is free software; see the source for copying conditions.

    WARNING: Probing normally takes from a few seconds to 15 minutes, but
    it can take longer. Please be patient.

    Probe finished, recovering blocks... Done

    Good news: The device `/dev/sdb' is the real thing

    Device geometry:
    *Usable* size: 231.05 GB (484540416 blocks)
    Announced size: 231.05 GB (484540416 blocks)
    Module: 256.00 GB (2^38 Bytes)
    Approximate cache size: 0.00 Byte (0 blocks), need-reset=no
    Physical block size: 512.00 Byte (2^9 Bytes)

    Probe time: 5'29"
    root:706 ~> f3probe /dev/sdb
    F3 probe 8.0
    Copyright (C) 2010 Digirati Internet LTDA.
    This is free software; see the source for copying conditions.

    WARNING: Probing normally takes from a few seconds to 15 minutes, but
    it can take longer. Please be patient.

    Probe finished, recovering blocks... Done

    Good news: The device `/dev/sdb' is the real thing

    Device geometry:
    *Usable* size: 231.05 GB (484540416 blocks)
    Announced size: 231.05 GB (484540416 blocks)
    Module: 256.00 GB (2^38 Bytes)
    Approximate cache size: 0.00 Byte (0 blocks), need-reset=no
    Physical block size: 512.00 Byte (2^9 Bytes)

    Probe time: 18'47"

    -- end of output --

    That's both sticks : NB the 2nd took 3 times as long.

    This is good news, it confirms neither of them are counterfeit units.

    However, the 2nd stick appears to be defective. It takes almost 3.5 times as long than the first stick and from what we know for no good reason. This indicates the second stick has bad flash cells, a bad flash controller, or both.

    I don't know if checking for bad blocks when you format these drives may help at all. You'd expect the flash controller to manage defective NAND cells transparently to the OS by abstracting the hardware to a logical layer. However, if the controller is not sophisticated as would be the case in a more expensive SSD drive and keeps trying repeatedly to write into bad cells, it might help to ask the filesystem to manage the bad blocks and see what you
    get.

    Personally, I wouldn't bother and return the bad stick as defective, asking
    for it to be replaced.


    So both sticks are genuine, as I would expect from that store.

    In my experience stores are box shifters. Goods In - Goods Out. They try to buy from importers/wholesalers with whom they have some relationship based on price-reliability-convenience and who they hope also apply similar criteria in their relationships up the supply chain. Any link in this chain can go wrong and you end up with bad goods. I don't expect them to perform QA/QC beyond looking at the shipping labels and customs declarations. The manufacturers
    may perform some actual quality checks on a sampling basis after the
    prototypes have been put together and the brand reps may audit the odd production run. I would think the rigour of such checks is proportional to
    the value of the assembled items.

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCAAdFiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAme0dcUACgkQseqq9sKV Zxlg3RAAhHiYG0MvlrQE1ZYZ9S0R3ZpTB5EIovx+uVIS76f63F8ZSl+m1b+a6rDQ A2W4BjOmMpoG8Fxbq1jhg5kTtxLCvD9CvEeu6pgHcogg4ZD22ir05OyxMQPaNxVP yDpYqORGBY7yOtmv4Ho4+BWCTqD2+jAzBFCxtb4JgsFUY7Aod81WPEfCb05dAVSo nqjUIpY+WkiQK8//Mb8LC6jysDgQIR3AnLjToZ00E9gqh7uf3iZbvpp2qDirAIDW J6ClteGwYZ5DcdiPtvaYxoRccJ47hpHXc6Semdp6BOmrXPFc/31pZN81vF6A9WBH JRpIz4dhF2BYqqWx6aQuAYAuPFqMJV2a9krCCErpSGY5TY2j8Os1ztPieAZ437HW yCLsx46DIeZJi70r/XN/fajTwZfODibYtFE5sVAFdOeEt7/huq79WvALl2A/tAL6 HT0A5xOUa4e7C2wQnTz5cK05WyBBixXMctrb6Io31fk9drwFw5FpBHYOag9vOqCY Fdzl4iUvW7BPzeJha4qIO4PAXEgBOgvbmu9x0Mtlq3SZ0S6KpxibEwbkifUUi07E H2e+dZkMR+cmKNG43IpiRZBsYcvw6xaHDJEtWV+UJEqULY+aRA5eFtE+rVDf+fBi cWJnvPRfRh4xj9y81Sz9f1CRBPfwH0nepqmnaSvvDGMB/y88VnE=
    =y962
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)