hikvision brand flash drives are garbage do not buy

hi. I have a low-quality usb ssd drive, hikvision brand. I have engaged with you on this particuilar drive before. When I try copy files to it, it fails quite quickly. I remember that f3 (fighting flash fraud) software can check a drive for integrity (hardware). I also believe there are ways to mark and deallocate bad blocks. Please give me a script to do this, asssumiing bash ubuntu linux 24 and that it must pre-install any apt-get packages needed when it runs

Below is a single self-contained bash script that:

Installs required tools (f3, e2fsprogs, smartmontools where applicable)
Destructively tests the USB SSD with f3 (integrity / fake-capacity check)
Optionally recreates the filesystem and marks bad blocks (only works reliably for ext4)

⚠️ WARNING: THIS WILL ERASE ALL DATA ON THE DRIVE.

`usb_ssd_check_and_repair.sh`


#!/usr/bin/env bash

set -e

if [ "$EUID" -ne 0 ]; then
  echo "Run as root."
  exit 1
fi

DEV="$1"

if [ -z "$DEV" ]; then
  echo "Usage: sudo $0 /dev/sdX"
  exit 1
fi

echo "Target device: $DEV"
echo "ALL DATA WILL BE DESTROYED."
read -p "Type YES to continue: " CONFIRM
[ "$CONFIRM" = "YES" ] || exit 1

echo "[1] Installing required packages..."
apt-get update -y
apt-get install -y f3 e2fsprogs smartmontools

echo "[2] Unmounting device..."
umount ${DEV}?* 2>/dev/null || true

echo "[3] Creating single partition..."
wipefs -a "$DEV"
parted -s "$DEV" mklabel gpt
parted -s "$DEV" mkpart primary ext4 0% 100%

PART="${DEV}1"
sleep 2

echo "[4] Formatting ext4 (initial)..."
mkfs.ext4 -F "$PART"

MNT=$(mktemp -d)
mount "$PART" "$MNT"

echo "[5] Running f3 write test (destructive)..."
f3write "$MNT"

echo "[6] Running f3 read verification..."
f3read "$MNT"

umount "$MNT"
rmdir "$MNT"

echo "[7] Scanning for bad blocks (non-destructive read test)..."
badblocks -sv "$PART" > /tmp/badblocks.txt || true

if [ -s /tmp/badblocks.txt ]; then
  echo "[8] Reformatting and marking bad blocks..."
  mkfs.ext4 -F -l /tmp/badblocks.txt "$PART"
else
  echo "[8] No bad blocks detected."
fi

echo "[DONE]"
echo "If f3 reported corruption or capacity mismatch, the drive is FAKE or FAILING."

Run it


sudo bash usb_ssd_check_and_repair.sh /dev/sdX

(replace sdX with the actual device, not a partition)

Important realities (no fluff)

f3 failures = dying or fake flash → bin it
USB SSDs cannot truly remap blocks like enterprise SSDs
badblocks + ext4 only avoids bad areas; failures will continue
Hikvision USB SSDs are well-known for silent write failure

If you want:
• a non-destructive f3 probe, or
• an exFAT variant, or
• a read-only forensic confidence test,

say which one and I’ll give exactly that.

wipefs: error: /dev/sdb2: probing initialization failed: Device or resource busy

Do this one step only:


sudo lsof +f -- /dev/sdb2

Paste the exact output here.

john@localhost:~$ sudo lsof +f -- /dev/sdb2 lsof: WARNING: can't stat() fuse.portal file system /run/user/1000/doc Output information may be incomplete. lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs Output information may be incomplete. lsof: WARNING: can't stat() fuse.rclone file system /home/john/DropboxMount Output information may be incomplete. lsof: WARNING: can't stat() fuse.rclone file system /home/john/GDriveMount Output information may be incomplete. john@localhost:~$

Do this one step only:


lsblk -o NAME,FSTYPE,MOUNTPOINTS /dev/sdb

Paste the exact output here.

john@localhost:~$ lsblk -o NAME,FSTYPE,MOUNTPOINTS /dev/sdb NAME FSTYPE MOUNTPOINTS sdb ├─sdb1 └─sdb2 exfat /media/john/SCC_DIGIDOX john@localhost:~$

Do this one step only:


sudo umount /media/john/SCC_DIGIDOX

After running it, reply either with the exact error output or with done.

done

Do this one step only:


sudo wipefs -a /dev/sdb