Loading
@mcraa @zwhitchcox folks, I feel like we’ve not got a handle on Etcher distribution… Do you know what process publishes to cloudsmith.io?
The source of truth for Etcher is https://www.balena.io/etcher/, which fetches (out of date) release from GitHub. We’ve also had community maintainers pull support for Homebrew, AUR, etc., since our release cadence increased.
I feel like we need a single source of truth for Etcher releases (official) and if we want to support additional package repositories, we should automate it in our CI pipeline and not rely for external contributors for distribution (core piece of Etcher).
cc @chrisys
- Etcher version: 1.5.50-x64.AppImage
- Operating system and architecture: Both Debian 64-bit and macOS latest edition
- Image flashed: Trying to flash various Linux install ISOs.
- Do you see any meaningful error information in the DevTools? I attached my log. Not sure if that helps.
I keep getting a message saying the following after verification step:
«Something went wrong. If it is a compressed image, please check that the archive is not corrupted.»
-1561517786134.log
I get the same error at the same stage when trying to write a Raspbian .img image to an SD card, on a Mac running macOS 10.15 beta.
I dunno the cause of your error, but I see in your log you have:
Verifying 1 devices, 64% at 617.4 MB/s (total 617.4 MB/s)
I highly doubt that your device is really being read at that speed, and I think that’s another example of #1523 (comment)
@lurch this is an unrelated issue.
@sohrob it looks like sudo or the elevated command printed 0\n on its stderr and we consider this as an error. Not sure how this could happen. Can you please try with etcher 1.5.51 ?
This comment has been minimized.
@DG12 How can that be related to #2843 when that’s specifically concerned with Mac OS Catalina, and @sohrob here is running the AppImage version of Etcher, which means he must be using Linux ? 😕
Not sure if this is related, but on Mac v1.5.33, I am also having trouble writing a bootable linux image. Worked ok with Raspbian Buster but my app requires Jessie. Downloaded Jessie and it won’t work. Clues-
- Doesn’t appear to properly unmount the SD card at the end
- Mac OS pops up saying it can’t read the card, would I like to initialise it?
- Mac OS thinks the SD card has an ‘Apple Partition Map’ partitioning scheme
My machine is a 6,1 Mac Pro running 10.14.5
@adamphetamine where did you got the Jessie image from? Have you tried with another sd card /usb drive ?
more info- I was able to get this to work with a different ISO, and after updating Etcher to 1.5.51 and allowing Etcher full access in System preferences/ Security & Privacy.
Sorry I don’t know if it was the ISO that was the problem
Worked- 2018-03-13-raspbian-stretch.zip
Did not work- 2019-04-11-rpd-x86-stretch.iso
I may have more time to diagnose tomorrow. Also note one of these was compressed, the other not…
Have you tried this solution? #2833 https://github.com/balena-io/etcher/issues/2833#issuecomment-505145234
This lazy steps work for me.
Workaround:
Moving your image insidebalenaEtcher.appseems to do the trick.
You can do this by selecting «Show Package Contents» onbalenaEtcher.appand dragging your image inside of it. Then you can select your image as usual from Finder and the flashing will go ahead. Make sure you select the image insidebalenaEtcher.app
rostislaved, bar5um, cloud-worm, and sim-kelly reacted with hooray emoji
bar5um and cloud-worm reacted with heart emoji
cloud-worm reacted with rocket emoji
sorry I forgot to add that- yes I did try that solution but it didn’t work for me. I guess that makes it more likely my image was corrupt in some way. But I did have success with an older image as described above, thanks!
I get the same reading…
Sent from Yahoo Mail on Android
On Sun, Jun 30, 2019 at 10:45 AM, Dennis German<notifications@github.com> wrote:
Might this be «Long directory/filename seems to fail» #2843
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
2018-03-13-raspbian-stretch.zip is an image designed to be written onto an SD card, for booting on a Raspberry Pi.
2019-04-11-rpd-x86-stretch.iso is an image designed to be written onto a DVD or USB stick, for booting on a PC or Mac.
So depending on what it was you were trying to achieve, it doesn’t seem surprising that one or the other «didn’t work» 😉
P.S. If you’re looking for older versions of Raspbian, you can find them all at http://downloads.raspberrypi.org/raspbian/images/
Etcher is supposed to work with both formats if you read the docs.
Sorry, I wasn’t sure what you meant by «it won’t work».
I suspect (and this is just a guess, as I don’t have a Mac myself) some of the problems with MacOS being unable to read the contents of a USB stick flashed with the rpd-x86 ISO might be similar to https://github.com/balena-io/etcher/blob/master/docs/USER-DOCUMENTATION.md#flashing-ubuntu-isos (i.e. the USB stick might still boot your Mac, even if MacOS thinks the card isn’t readable?)
And to clarify, I’m only a «keen fan» of Etcher trying to help out where I can, I’m not an Etcher developer. Apologies if I’ve given the wrong impression or caused any offence.
Hi @lurch I apologise if I was short- going away tomorrow and trying to finish off a few things makes my responses to forums a bit brief. I’ll check out that link asap
Thanks
So I am now using the newest edition of Balena Etcher 1.5.51 and everything appears to be back to normal. Thank you for all your help and attention on this matter!
I have the same issue on the Latest MacOS Catalina 10.15. The solution is to run balenaEtcher.app/Contents/MacOS/balenaEtcher as sudo.
codedge, jeffmacdonald, balgamat, darkkatarsis, bavuongco10, anilcumulus, tylerpearson, mohammadbax98, wujunchuan, javaverse, and 33 more reacted with hooray emoji
mohammadbax98, RamonGebben, wujunchuan, javaverse, georgemblack, softdream1981, p0lux, MarcelWepper, leonardyhuang, anshulahuja98, and 24 more reacted with heart emoji
mohammadbax98, wujunchuan, javaverse, alex-wahl, cory-brown, georgemblack, softdream1981, p0lux, jayproulx, H-steven, and 16 more reacted with rocket emoji
worked perfectly for me thanks
I have the same issue on the Latest MacOS Catalina 10.15. The solution is to run balenaEtcher.app/Contents/MacOS/balenaEtcher as sudo.
You saved me a day thanks a lot!
I have the same issue on the Latest MacOS Catalina 10.15
See #2833
I have the same issue on the Latest MacOS Catalina 10.15. The solution is to run balenaEtcher.app/Contents/MacOS/balenaEtcher as sudo.
Yep, that does it on Catalina. Thanks a bunch!
Same issue Mac OS Catalina. I’ve tried different images
For issues with Etcher on macOS Catalina, see #2833
I have the same issue on the Latest MacOS Catalina 10.15. The solution is to run balenaEtcher.app/Contents/MacOS/balenaEtcher as sudo.
Thanks @blesspronexis !
@blesspronexis Well done !!!!!!!!
I got same issue (balenaEtcher 1.5.51, brand new Mac OS, freshly download ubuntu 16.04 LTS)
Your trick works !
To add further details for those landing here (likely Mac users who have upgraded to Catalina), run this in your terminal
sudo /Applications/balenaEtcher.app/Contents/MacOS/balenaEtcher
then you will be prompted to grant permission, then when you open Balena it should work.
Apparently the issue with Catalina is already fixed in the latest versions of Etcher #2833 (comment)
No need for the sudo workaround any more.
As of March 2020, this is still not fixed in Linux. It asks for the root password, then fails.
I guess the key problem is about etcher version. I met the same issue with v1.5.45, after updating to latest( brew cask install balenaetcher) v1.5.100 it worked well.
I was on an older version 1.5.52 (er something). Recently on Mac os I had wiped, reinstalled and restored from time machine, including apps (etcher). Some apps needed permissions again, Etcher was one of them. However, giving full drive access in Privacy didn’t fix the problem. Installed latest etcher, turned off full drive access, got the error. Turned full drive access on and it worked.
Apparently the issue with Catalina is already fixed in the latest versions of Etcher #2833 (comment)
No need for thesudoworkaround any more.
As of Sept 16, 2020, the latest release is still 1.5.109 (from the pre-made installer) for macOS and I’m on Catalina. I tried sudo opening it and still got the «Something went wrong. If it is a compressed image, please check that the archive is not corrupted» error.
The solution would be this comment in issue #2833
For a detailed step-by-step:
First you right click on Etcher to select «Show Package Content»
Then you drag and drop your iso image inside
Go back to Etcher and select this iso image from within the Etcher package folder
…et voila 
This worked for me too! thanks @kayx23 !!! all the above solutions failed for me 
In case it helps anyone with V1.5.109 on OS/X Big Sur v11.0.1 the solution that worked for me was to (after installing Etcher into Applications).
sudo su -
cd /Applications/balenaEtcher.app/Contents/MacOS/
./balenaEtcher
Then choose the downloaded ISO from my Downloads directory (/Users/$USER/Downloads) and flash that.
As documented above for Catalina.
On High Sierra using balena 1.5.111 and ubuntu 20.04LTS iso from their site. I tried both copying the iso to the balena folder as well as running the app sudo and they both didn’t work. I still got:
Attention
Something went wrong. If it is a compressed image, please check that the archive is not corrupt. The writer process ended unexpectedly.
Any other thoughts?
@NY3Ranger did you reset the computer. For me copying the image to the balena folder worked, I think I had to close and reopen the aplication, maybe try a system reboot just in case, I was using High Sierra.
This problem still exists on macOS Big Sur and 1.5.111 version of Etcher. However, either copying the image inside balenaEtcher.app/Contents/ or running it with sudo as a workaround works without any issue.
Table of Contents
Etcher (also known by its full name, balenaEtcher) is a free, open-source image flasher, a utility for creating bootable SD cards or USB flash drives from .img and .iso files. Simple and user-friendly, Etcher is a good choice even for those who are not particularly tech-savvy.
The issue
After you downloaded Etcher from Etcher’s official website, you make it executable by right click on it then select the checkbox Allow executing file as program.
After you give the AppImage permission to run as an application. When you right click on the app then select Run or double-click the app icon, nothing happened, and the Etcher app doesn’t show.
When you run the app from Terminal, you would get the following error:
The solution
To fix it, you need install FUSE in your Linux distribution as follows:
Install required packages for Ubuntu 22.04 and later.
sudo add-apt-repository universe
sudo apt install libfuse2Install required packages for other distributions:
###For Ubuntu 21.10 and older
sudo apt install fuse libfuse2
sudo modprobe fuse sudo groupadd fuse
user="$(whoami)" sudo usermod -a -G fuse $user
###For openSUSE:
sudo zypper install fuse libfuse2
sudo usermod -a -G trusted whoami
###For CentOS and Fedora
dnf install fuseNow. open the Etcher app from Terminal
As you can see, you got another issue GPU process isn’t usable.
To fix it, you need run Etcher in Terminal with one of the following parameters:
sudo ./balenaEtcher-* --disable-gpu-sandboxIf the above command doesn’t work, let’s trying to execute the below one:
sudo ./balenaEtcher-* --no-sandbox --disable-gpu-sandbox --disable-seccomp-filter-sandbox
Re: Balena etcher hangs with white screen -windows7 64
Post
by Reddog1 »
I’m coming in on this thread late, but, I really don’t think that you should be installing on an external drive. It can be done, but it really isn’t a task for a linux newbie, and, especially on an older laptop, the performance will be sub-par, even if you do succeed.
Your ‘old’ laptop specs aren’t all that bad. It appears you have an intel I5 with intel graphics (probably 3000), and probably 4GB of ram (maybe 2GB). If your hd actually is the stock 500GB-7400rpm drive, that isn’t bad at all. I run one on a desktop PC and it’s fine.
I recommend, if the specs I quoted are what you have, that you drop the idea of using an external usb drive for linux, and that you install Mint alongside your Windows 7 on your internal HD.
Now, if you have limited space on the W7 drive, you can get by with as little as 50GB for Mint 21. I install Mint 21 in a virtual machine and I get by with a 22GB drive. With a lack of space, you will be limited as to what extra programs you can install and how much data you can store, but the standard install of Mint is around 10GB. That is a complete install, with everything you need to run a viable linux desktop operating system.
If you can afford to give up more space for Mint, do so. At least 256GB would be really nice. To do it right, first start W7 and then use the Windows disk utility to shrink the Windows drive and leave free space for the Mint install. I have some basic Windows 10 installs, plus a few Windows programs that I need, on 40GB drives, but your mileage can vary. Then boot your Mint usb, start the installer, and install alongside Windows 7. Grub should be installed on the first partition of the first hard disk (/dev/sda). Be sure that you install Mint the way W7 was installed (probably legacy, but possibly uefi). If you do that, grub will become the boot manager for both systems and you should be good to go. You can format an ext4 or FAT32 partition on the external drive and use it for data that takes up a lot of space, such as saved videos and music, but you need to keep in mind that the transfer of files will be relatively slow.
I suspect that your present install has grub on the 1st HD, which is the internal HD, /dev/sda, with your Mint system on the external, which could be either /dev/sdb or /dev/sdc, and likely the latter when installed, but recognized as sdb after the install. Kind of a mess to sort out, especially for a newbie.
All this is JMO, but I’ve been running linux since I first installed Debian—from floppies.