Here we go:
On 2/6/24 9:09 PM, home user wrote:
Thank-you, Michael, for both posts. I've installed it. It looks like it will take a while to run, and it's late here now. So I'll give it a try tomorrow.
----- -bash.4[~]: f3probe --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: 57.30 GB (120176640 blocks) Announced size: 57.30 GB (120176640 blocks) Module: 64.00 GB (2^36 Bytes) Approximate cache size: 0.00 Byte (0 blocks), need-reset=no Physical block size: 512.00 Byte (2^9 Bytes)
Probe time: 1'17" Operation: total time / count = avg time Read: 21.76s / 4197137 = 5us Write: 54.71s / 4192321 = 13us Reset: 0us / 1 = 0us -bash.5[~]: ----- That took a lot less time than I anticipated.
Tim: I saw your post. Thank-you. I understand.
Michael: I saw your early-this-morning post. What you said makes sense.
Everyone/Anyone... Follow-up questions: 1. For a new stick, does the --destructive option matter? 2. What is the --reset-type option about? 3. What's taking up all that 6.7 GB (64 GB - 57.3 GB) unavailable space? That's a lot!