Etcher seems to break USB installer.

Comments

10 comments

  • Forrest Smith

    We haven't had any reports of this. v83 is the first version where we began making changes to GRUB to respond to Boothole vulnerabilities, so that seems like it may be the likely cause... but I can't figure out why Etcher would be doing some thing different than all the other methods, especially considering that the goal of all those tools is to make a pure, bit-wise copy.

    "expected contents did not match written contents" - this text implies that the disk's "verity" check is failing, so perhaps etcher is mounting/editing in some miniscule way after writing the image. Its possible that something in CloudReady changed which now prompts etcher to automatically make such a change/inspection - not sure.

     

    0
    Comment actions Permalink
  • Alexander David Frick

    Yeah, exactly what I thought. Oh well, just use other methods and keep testing to see if it sometime fixes itself and works.

    0
    Comment actions Permalink
  • Aaron Dorman

    I found this thread because I ran into the same issue - when i used etcher, cloudready fails to install for the same reason as above (failing verity).

    Using the cloudready maker worked successfully.

    0
    Comment actions Permalink
  • SpacePiggy

    I have to report that Etcher fails for me as well. It seems to have started a while ago, with the early 80's CROS releases. I have to use a Mac to create installers, so I'm stuck with either Chrome Recovery tool or Etcher. 

    The installer/live boot USBs I make for Gallium OS and Debian work fine with Etcher. Just not Cloudready.

    0
    Comment actions Permalink
  • Alexander David Frick

    SpacePiggy Yussss Gallium OS. It tends to not work right on non chromebook hardware since it is tailored at the driver and kernel level for them, but I got lucky and use it on an intel board (has no case lol) since my chromebook was STOLEN from library after I got a drink from water fountain. Also, you can use dd or rufus (windows only) https://rufus.ie/en_US/  or popsicle flasher for flashing cloudready and many other images on mac and linux. https://osxdaily.com/2018/04/18/write-image-file-sd-card-dd-command-line/  & https://github.com/pop-os/popsicle 

    0
    Comment actions Permalink
  • Alexander David Frick

    Aaron Dorman The cloudready maker is slow. It is better to download the image directly. You can also download the "dev" channel versions of cloudready directly at http://go.neverware.com/previewrelease , which the maker doesn't let you do. Then you can write it with rufus or chromebook recovery utility. https://rufus.ie/en_US/  & https://chrome.google.com/webstore/detail/chromebook-recovery-utili/pocpnlppkickgojjlmhdmidojbmbodfm?hl=en 

    0
    Comment actions Permalink
  • SpacePiggy

    Alexander David Frick

    Thanks for the link to the MacOS CL tool, I'll give it a try later today. I'm currently down to one Chromebox and it needs to be tamper-free for the next three weeks as its primary use is streaming the Tour de France.

    I understand the focus of Gallium OS, it's my fix-it tool when Cloudready decides to get stupid. Mainly for gpartd to scrub the SSD before reinstalling.

    0
    Comment actions Permalink
  • Joe

    Just use the Google Chrome Browser Recovery Tool. Works with .BiN files

    0
    Comment actions Permalink
  • JCloud

    I agree Joe that first option should be Chrome Recovery tool, but actually on My Chromebook it crashes tons, works ok on Windows though, so nice to have other options.

    0
    Comment actions Permalink
  • SpacePiggy

    I now use Chrome browser with the recovery tool on my Intel iMac to make USB installers. As Cloudready images have gotten larger (perhaps to support more diverse hardware) the recovery tool no longer works on my Chromebox which has only 16GB SSD. Compared to "real" Google Chrome OS or a Linux flavor, Cloudready is a real hog. Even deleting all extensions, apps, and PWAs it runs out of memory when extracting the image.

    0
    Comment actions Permalink


ChromeOS Flex is replacing CloudReady, so this community is no longer accepting new comments.

Please visit the ChromeOS Flex Help Community to post any new questions or thoughts! You can still link back to this or other pages in this community in order to reference past conversations.

Please sign in to leave a comment.