Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Burn drive without completely erasing it #2670

Closed
kornpow opened this issue Feb 27, 2019 · 1 comment
Closed

Burn drive without completely erasing it #2670

kornpow opened this issue Feb 27, 2019 · 1 comment

Comments

@kornpow
Copy link

kornpow commented Feb 27, 2019

  • Etcher version:
    1.4.9
  • Operating system and architecture:
    Ubuntu 18.04 AMD64
  • Image flashed:
    Balena Image
  • Do you see any meaningful error idnformation in the DevTools?

I have been using etcher for burning Balena disk images onto a SSD. Is it typical behavior that it deletes the partition table of the drive prior to the image burn? Is there any way around that.

Example:
Have a SSD drive that is 120gb. At position 80-120gb I have a partition that needs to stay on the drive. I want to be able to burn the drive, and have my new fairly small balena partitions at the beginning of the drive, and keep the previous partition at the end?

Am I understanding image burning correctly?

@lurch
Copy link
Contributor

lurch commented Feb 27, 2019

This isn't possible with Etcher, it always overwrites the MBR too, since some disk images (typically for Linux) contain multiple partitions.
You might be looking for #413 ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants