etcher: Creating bootable USB corrupts the key
I have a 16GB USB dongle, classic. Using other tools to load a ubuntu image onto it creates a 16GB partition with about 1.5GB used, and it’s called “Ubuntu <version><arch>” or similar.
Here, it “seems” to do the same, but it doesn’t:
lsblk -l:
sdd 8:48 1 14,6G 0 disk
sdd1 8:49 1 1,1G 0 part /media/vankasteelj/Ubuntu 15.10 amd64
sdd2 8:50 1 2,2M 0 part
- gparted:

(keep in mind it’s a 16GB key, not 64 like etcher seemed to write it.)
- libparted log:
Driver descriptor indicates a physical bloc size of 2048 bytes, but Linux says 512 bytes.
somehow, that key does boot x)
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Comments: 19 (11 by maintainers)
Commits related to this issue
- docs: ubuntu iso's hybrid format and parted warnings Document that `parted` warnings about invalid GPT and physical block size issues can be safely ignored as they are a consequence of "hybrid iso's"... — committed to balena-io/etcher by jviotti 8 years ago
- docs: ubuntu iso's hybrid format and parted warnings Document that `parted` warnings about invalid GPT and physical block size issues can be safely ignored as they are a consequence of "hybrid iso's"... — committed to balena-io/etcher by jviotti 8 years ago
- docs: ubuntu iso's hybrid format and parted warnings (#585) Document that `parted` warnings about invalid GPT and physical block size issues can be safely ignored as they are a consequence of "hybri... — committed to balena-io/etcher by jviotti 8 years ago
“safe to ignore”, you’ll have to say that quick, it does mess up the partition table and render the usb key “broken” for people not knowing how to fix it 😕