I recently was trying to flash from an IMG file with dd
, and it took a lot shorter than normal, and when I checked the drive, it had names like
\u2584\u00bc\u2591+\u03c6\u256bv\u2559.|
I don't know if I'm being stupid, or if it's a drive error. This is the code I used:
sudo dd if=~/Downloads/tails-amd64-4.20.img of=/dev/sdd1 bs=1M
\u2584
is unicode for a bottom half block.\u00bc
is unicode for1/4
. This looks like an encoding issue. Did you intend for this image to have unicode-characters in the filenames? – Stewart Aug 02 '21 at 13:29file
should be able to tell you what it thinks (e.g. if it's a compressed file rather than an actual image, for example) andfsck -n
can check it, I think. And you should be able to loopback-mount the file and inspect it. If those succeed, then start to look at the copy command (probably worth issuing async
before using it, too). – Toby Speight Aug 02 '21 at 13:43bs
withoutcount
is safe with a moderndd
, but just in case, try usingcat
instead. Of course, check that the image is good —sudo mount -o loop ~/Downloads/tails-amd64-4.20.img /mnt
. – Gilles 'SO- stop being evil' Aug 02 '21 at 13:58