etcher: "Unknown error" when writing .img.xz file on Windows
- Etcher version: 1.0.0-beta.10
- Operating system and architecture: Windows 10 x64, Insider Preview build 14385
- Do you see any meaningful error information on DevTools? Do I see anything? Yes. Meaningful? No. Just an error object with the same information as shown below.
When I attempt to flash an image (.img.xz) to an SD card, the operation often opens the UAC dialog for verification and then sits there with the message “Starting…” until I quit the application. When it gets past that, it progresses to around the 80% mark and then slows, before throwing an error (pictured below). The image that was written is corrupted, so Etcher did not successfully complete the imaging operation by the time the error was thrown.
I can’t find any useful info in the dev console and there are no other logs as far as I can tell, so past this screenshot I don’t have anything to go off of.
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Comments: 53 (46 by maintainers)
Commits related to this issue
- Fix diskpart clean command failed error For some reason, `diskpart clean` seems to randomly fail in some systems without any explanation, apart from the following entry in the Event Log: ``` Cannot ... — committed to balena-io-modules/etcher-image-write by jviotti 8 years ago
- Fix diskpart clean command failed error (#46) For some reason, `diskpart clean` seems to randomly fail in some systems without any explanation, apart from the following entry in the Event Log: ``... — committed to balena-io-modules/etcher-image-write by jviotti 8 years ago
- upgrade: etcher-image-write to v5.0.2 This version contains a fix for a `diskpart` error on Windows. Change-Type: patch Changelog-Entry: Upgrade `etcher-image-write` to v5.0.2 Link: https://github.c... — committed to balena-io/etcher by jviotti 8 years ago
- upgrade: etcher-image-write to v5.0.2 (#575) This version contains a fix for a `diskpart` error on Windows. Change-Type: patch Changelog-Entry: Upgrade `etcher-image-write` to v5.0.2 Link: https... — committed to balena-io/etcher by jviotti 8 years ago
- Fix drive without filesystem always being considered non-removable Before knowing about the `MediaType` property from the `Win32_DiskDrive` structure, we though we had no realiable way of doing this ... — committed to balena-io-modules/drivelist by jviotti 8 years ago
- fix(GUI): check drive size agains uncompressed image size We were currently checking if a drive was large enough for an image by checking the image file size, completely ignoring compression. This re... — committed to balena-io/etcher by jviotti 8 years ago
- fix(GUI): check drive size agains uncompressed image size We were currently checking if a drive was large enough for an image by checking the image file size, completely ignoring compression. This re... — committed to balena-io/etcher by jviotti 8 years ago
- fix(GUI): check drive size agains uncompressed image size We were currently checking if a drive was large enough for an image by checking the image file size, completely ignoring compression. This re... — committed to balena-io/etcher by jviotti 8 years ago
- fix(GUI): check drive size against uncompressed image size We were currently checking if a drive was large enough for an image by checking the image file size, completely ignoring compression. This r... — committed to balena-io/etcher by jviotti 8 years ago
- fix(GUI): check drive size against uncompressed image size (#582) We were currently checking if a drive was large enough for an image by checking the image file size, completely ignoring compression... — committed to balena-io/etcher by jviotti 8 years ago
- Throw a human-readable error if the drive runs out of space If we try to write a too large image to a drive, an `EIO` error will be eventually emitted. This error is very generic, and its hard to kno... — committed to balena-io-modules/etcher-image-write by jviotti 8 years ago
- Throw a human-readable error if the drive runs out of space (#47) If we try to write a too large image to a drive, an `EIO` error will be eventually emitted. This error is very generic, and its hard... — committed to balena-io-modules/etcher-image-write by jviotti 8 years ago
- feat(GUI): display a nice alert ribbon if drive runs out of space We try our best to check that the images the user select are too big for the selected drive as early as possible, but this probes to ... — committed to balena-io/etcher by jviotti 8 years ago
- feat(GUI): display a nice alert ribbon if drive runs out of space We try our best to check that the images the user select are too big for the selected drive as early as possible, but this probes to ... — committed to balena-io/etcher by jviotti 8 years ago
- feat(GUI): display a nice alert ribbon if drive runs out of space (#588) We try our best to check that the images the user select are too big for the selected drive as early as possible, but this pr... — committed to balena-io/etcher by jviotti 8 years ago
Using the “One retry” version, I ran it 6 times and every time it got past the “Starting…” phase when it previously threw the diskpart errors. I tried multiple drives and various other configurations, and every time it worked as it should have up to that point. It did not fix the later error (the original one mentioned in this issue), but as far as I can tell the diskpart ones are resolved. Reinstalling the standard beta 10 brought the error back first try.
So, I think that’s the fix to go with. However, it would be great if it warned you in the dev console that it was retrying so that it was clear that it had hit that problem. That way, we could be sure that the retry logic was in fact activating and future debugging would probably be easier as well.
I think that, based on what I saw with the one-time version, ten times is probably unnecessary. Would you like me to also try the one that rescans?
Now, I think the main thing that we have to figure out is the “unknown error, write” issue, which now happens every time for me. @jeffiscow would you mind installing the version that @jviotti linked to entitled “ONE RETRY”? I’d like to know if you now see an error there like I do or if it works without issue.
Agh, I hot-edited a dependency and then re-installed dependencies when packaging, so silly 😃