I do it the other way around: first write (zero wipe), then read (SMART long test). Served me well for many disks. :)
binaryriot
joined 2 years ago
I never had a bad block on a brand new drive. At least not a reported/ detectable one. So if it's truly a "bad block" (how exactly is it reported in your SMART data?) I would exchange the disks.
A little bit shell magic around a little Python3 helper will do the job quickly:
for i in $(seq 1 10); do grablinks.py --fix-links 'https://forums.aida64.com/topic/667-share-your-sensorpanel/page/'"${i}" --search 'file/attachment.php?' -f 'wget -c -O '\''%text%'\'' '\''%url%'\' | fgrep '.sensorpanel'; done | tee fetchscript.sh, then verify the generated shell script, and finally:sh fetchscript.sh.Happy waiting! :)
You can grab my
grablinks.pyPython3 script from here: https://github.com/the-real-tokai/grablinks