error: please check that the archive is not corrupted. every iso i try

roadh0use commented 5 years ago

Etcher version: 1.5.51
Operating system and architecture: ubuntu 19.04 64bit
Image flashed: every manjaro iso i can find
Do you see any meaningful error information in the DevTools? /tmp/.mount_balenaD4…js/dist/raven.js:58 {"stack":"Error: The elevated process died unexpectedly\n at Object.exports.createError (/tmp/.mount_balenaD4uKeB/resources/app.asar/lib/shared/errors.js:253:17)\n at Object.exports.createUserError (/tmp/.mount_balenaD4uKeB/resources/app.asar/lib/shared/errors.js:292:18)\n at Bluebird.using (/tmp/.mount_balenaD4uKeB/resources/app.asar/lib/shared/permissions.js:207:22)","message":"The elevated process died unexpectedly","description":"The process error code was 126","report":false,"image":"manjaro-architect-18.0.2-stable-x86_64.iso"}

every iso i try to flash i get an error saying "something went wrong. if it is a compressed image, please check that the archive is not corrupted." i have tried manjaro architect iso, manjaro i3 iso, manjaro kde iso, etc. every one gives this error.

lurch commented 5 years ago

@zvin @thundron https://www.gnu.org/software/bash/manual/html_node/Exit-Status.html says If a command is found but is not executable, the return status is 126.

thundron commented 5 years ago

@roadh0use are you using the portable version?

roadh0use commented 5 years ago

@thundron sorry i just had a chance to reply. no i was just using regular iso's. here is a link to the architect download i was using. https://osdn.net/projects/manjaro/storage/architect/18.0.2/manjaro-architect-18.0.2-stable-x86_64.iso/

roadh0use commented 5 years ago

also just tried with the new 1.5.52 appimage with a different iso. this time it was the manjaro i3 x86_64 iso. /tmp/.mount_balena9GuAtS/resources/app.asar/node_modules/raven-js/dist/raven.js:58 {"stack":"Error: The elevated process died unexpectedly\n at Object.exports.createError (/tmp/.mount_balena9GuAtS/resources/app.asar/lib/shared/errors.js:253:17)\n at Object.exports.createUserError (/tmp/.mount_balena9GuAtS/resources/app.asar/lib/shared/errors.js:292:18)\n at Bluebird.using (/tmp/.mount_balena9GuAtS/resources/app.asar/lib/shared/permissions.js:207:22)","message":"The elevated process died unexpectedly","description":"The process error code was 126","report":false,"image":"manjaro-i3-18.0.4-stable-x86_64.iso"}

edit. i also tried with the arch iso found here https://www.archlinux.org/download/. same output and error. /tmp/.mount_balenac3cDvX/resources/app.asar/node_modules/raven-js/dist/raven.js:58 {"stack":"Error: The elevated process died unexpectedly\n at Object.exports.createError (/tmp/.mount_balenac3cDvX/resources/app.asar/lib/shared/errors.js:253:17)\n at Object.exports.createUserError (/tmp/.mount_balenac3cDvX/resources/app.asar/lib/shared/errors.js:292:18)\n at Bluebird.using (/tmp/.mount_balenac3cDvX/resources/app.asar/lib/shared/permissions.js:207:22)","message":"The elevated process died unexpectedly","description":"The process error code was 126","report":false,"image":"archlinux-2019.07.01-x86_64.iso"}

roadh0use commented 5 years ago

interesting. i removed the newest appimage and tried the newest .deb instead and its working.

thundron commented 5 years ago

@roadh0use Thank you, I'm gonna fiddle with the latest appimage to see if I can reproduce!

ghost commented 5 years ago

Dont use appimage, install etcher package with pacman, or try installing gconf and using appimage. I had same problem and then checked for etcher package, installed it and saw that it installed gconf also and now etcher works.

thundron commented 5 years ago

@roadh0use Did you try @vgaleksa 's suggestion?

iMerica commented 5 years ago

I had the same problem. The solution was to unmount all the extra volumes.

diskutil list

/dev/disk2 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     FDisk_partition_scheme                        *31.3 GB    disk2
   1:             Windows_FAT_32 NO NAME                 31.3 GB    disk2s1

diskutil unmount disk2s1

Etcher should work now.

Optional:

Skip etcher and just use dd:

sudo dd if=/path/to/your/disk.img of=/dev/rdisk2 bs=1m diskutil eject /dev/disk2

lurch commented 5 years ago

The solution was to unmount all the extra volumes.

AFAIK, Etcher should be doing that automatically?

pczekalski commented 5 years ago

Same problem with Ubuntu 19.04: Appimage fails to flash caliming image is corrupted, same image using DEB installation works like a charm

lurch commented 5 years ago

@pczekalski Can you check if the AppImage still fails after you've installed the DEB package?

pczekalski commented 5 years ago

Edit: I tested it in 1:1 environment on the smaller (16GB) card and it fails as previously, for appimage distribution. Meanwhile, DEB version works without any errors.

zingbretsen commented 4 years ago

Same issue with the appimage on Ubuntu 19.10. It works when I install the DEB package and use that. The appimage version still does not work after installing the DEB package.

rotimi-best commented 4 years ago

Same issue with the appimage on Ubuntu 19.10. It works when I install the DEB package and use that. The appimage version still does not work after installing the DEB package.

This was what helped me. Instead of using the Appimage, I had to download the package using apt-get as stated in the README and it is working fine.

balena-ci commented 4 years ago

[garethtdavies] This issue has attached support thread https://jel.ly.fish/#/support-thread~aa55d22e-a11b-4818-a3a5-dd84ab7c6b81

garethtdavies commented 4 years ago

I've reproduced this on Ubuntu 19.10 and can confirm that the AppImage versions >= 1.5.66 have this issue so likely introduced in 1.5.66 as successfully tested on 1.5.65 and lower.

The current deb as noted above works.

jhoughjr commented 4 years ago

using etcher on Mac OS X Catalina. Also every image I burn it says is corrupted.

jtagcat commented 4 years ago

Fedora 31, same issue, with known-good isos written before on same machine, known-good usb-sticks- Installing via package manager fixes issue.

AeonFox commented 4 years ago

Have you tried downloading the newest BalenaEtcher? That fixed my issue! Hope this helps.

TwilightDuck commented 4 years ago

I still have this issue happening on the latest version as of writing. On the AppImage that is. I installed it through DEB and it's working again! :)

huahuayu commented 4 years ago

I had the same problem. The solution was to unmount all the extra volumes.

diskutil list
/dev/disk2 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     FDisk_partition_scheme                        *31.3 GB    disk2
   1:             Windows_FAT_32 NO NAME                 31.3 GB    disk2s1
diskutil unmount disk2s1

Etcher should work now.

Optional:

Skip etcher and just use dd:

sudo dd if=/path/to/your/disk.img of=/dev/rdisk2 bs=1m diskutil eject /dev/disk2

hi, why it's rdisk2 in of=/dev/rdisk2 instead of disk2

huahuayu commented 4 years ago

I download etcher in https://www.balena.io/etcher/ today, for mac the version is 1.5.45, but in github release page, the latest release is 1.5.79, so, the website download link should be updated.

zvin commented 4 years ago

@huahuayu the website fetches the latest release from github ( from here: https://raw.githubusercontent.com/balena-io/etcher/gh-pages/scrutinizer.json ). Something in your browser is blocking this request.

lurch commented 4 years ago

hi, why it's rdisk2 in of=/dev/rdisk2 instead of disk2

See #1042

tthebst commented 4 years ago

I had this issue as well on Mac OS. I solved it by running etcher from the terminal with following command: sudo /Applications/balenaEtcher.app/Contents/MacOS/balenaEtcher

vincegre commented 4 years ago

Used the deb package instead the AppImage and everything works fine :+1:

wzJun1 commented 4 years ago

I had this issue as well on Mac OS. I solved it by running etcher from the terminal with following command: sudo /Applications/balenaEtcher.app/Contents/MacOS/balenaEtcher

this is the correct solution

jellyfish-bot commented 4 years ago

[georgiats] This issue has attached support thread https://jel.ly.fish/0d3f8fa3-40f4-41c3-b6e8-c2ead25ef06c

gimdh commented 4 years ago

I'm on Ethcer 1.5.109, and it seems the error has come back with Catalina 10.15.7 update. I want to point out that the error message should be fixed as well as wrong behavior, since it's quite misleading.

thundron commented 4 years ago

@Sidordroid that looks like a separate issue than the one descripted above

pngimbwa commented 4 years ago

To solve the problem, just right-click the software (i.e. balenaEtcher) and run it as administrator on Windows PC.

TTiagha commented 4 years ago

To parrot pngimbwa, run Etcher as administrator.

kyxap commented 4 years ago

For Mac users (catalina): to resolve this issue just install app with brew like:

brew install balenaEtcher

and run app from Application folder without sudo\admin\etc

lborrazas commented 3 years ago

Two guys said this before, but ill say it once again cause it is important.

If your error message says "PERMISSION DENIED" Then just running Balena As An Administrator solves everything :D

NavadeepGaneshU commented 3 years ago

I got the same issue while using balena etcher while used when it opened by default after new installation. Closed that and reopened the software as administrator upon which it works very well.

ethaniel commented 3 years ago

Had this problem on my macbook, updated Etcher to 1.5.122 - problem is gone.

balena-io / etcher

error: please check that the archive is not corrupted. every iso i try #2859