I have tried to flash several copies of the Raspberry PI raspbian image and it always comes back as failed.
The image is: 2018-04-18-raspbian-stretch.img
The card SD card is mounted on an ANKER USB - SD card adapter.
The SD card is a Kingston 32 GB card, but I have tried several.
I am on Windows 10 build 1709
Hey there!
What image flasher are you using? Maybe try Etcher (https://etcher.io) and use its validating mechanism to rule out any SD Card / adapter problems?
I am using Etcher. That is what is giving me the error that it has failed when it does the verification. I have used other utilities and get no errors and no problems with the images, but those utilities are not doing a verification pass.
That sounds like the problem. Other tools don’t do verification, so they are not catching this. Can you try other SD Card adapters, or other adapter port?
I have now tried other ports, a regular USB thumb drive, even a different computer. ALL transfers I do with Etcher of this image ALL come back failed on verification.
Could there be something wrong with the image or with Etcher?
From here:
RASPBIAN STRETCH WITH DESKTOP
Download ZIP
I see. I’d suggest flashing it using a different tool and confirming whether it’s etcher or the image that has the problem. What OS are you using to flash with?
I am on Windows 10 build 1709
I was having the same problem - nearly every attempt to write Raspbian to an SD card failed. Turns out it was caused by having my SD card reader attached to a weak USB hub, in this case the one built into my monitor. When I plugged it directly into my motherboard, writes stabilized. Hope that fixes it for you.
Thanks for the feedback!
I have the same problem, it always fails on verification. I tried to put the USB thumb drive near to the motherboard, but it did not change anything. It worked only one time, maybe the first time I did it on this particular SD card.
+++ The written image can be read back and matches the source.
sudo fdisk -l /dev/mmcblk0
Disk /dev/mmcblk0: 59.64 GiB, 64021856256 bytes, 125042688 sectors
Device Boot Start End Sectors Size Id Type
/dev/mmcblk0p1 8192 334116 325925 159.1M c W95 FAT32 (LBA)
/dev/mmcblk0p2 335872 4677631 4341760 2.1G 83 Linux
sudo parted /dev/mmcblk0
Disk /dev/mmcblk0: 64.0GB
Partition Table: msdos
Number Start End Size Type File system Flags
1 4194kB 171MB 167MB primary fat32 lba
2 172MB 2395MB 2223MB primary ext4
sudo mount /dev/mmcblk0p1 /mnt/mmcblk0p1
/dev/mmcblk0p1 on /mnt/mmcblk0p1 type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/mmcblk0p2 on /mnt/mmcblk0p2 type ext4 (rw,relatime)
+++ the contents of both file systems looks correct, and can be modified.
+++ Back to Windows 10
DISKPART> list part
Partition ### Type Size Offset
Partition 1 Primary 159 MB 4096 KB
Partition 2 Primary 2120 MB 164 MB
Windows can see files in Partition 1, which should be the Raspberry /boot volume.
Windows cannot see a file system in Partition 2, which should be the Raspberry / volume (Linux ext4)
+++ The card boots in the Raspberry Pi.
What is likely occurring is that Windows is adding it’s “System Volume Information” folder upon the SD Card being written, prior to Etcher finishing the validation step, thus causing the validation to fail. The contents have in fact been written properly, this is why the Pi does boot properly.