Creating bootable USB corrupts the key
See original GitHub issueI 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)
Issue Analytics
- State:
- Created 7 years ago
- Comments:19 (11 by maintainers)
Top Results From Across the Web
How to Repair Corrupted Bootable USB Drive in Windows 10?
Corrupted USB Drive is the Most Common Issue? Here is a Complete Guide to Fix Corrupted Bootable USB Drive in Windows 10 PC....
Read more >How to Fix Bootable USB Not Working Problem?
If you face trouble with a bootable USB not working, we will help you find straightforward and simple solutions with a stepwise guide....
Read more >Windows 10 Media Creation Tool corrupting USB drives
Hello,. I've twice attempted to create a boot USB using the most recent version of the Media Creation Tool. Each time, an error...
Read more >How to Fix Corrupted USB Flash Drive and Recover Data?
Are you looking for corrupted USB flash drive repair solutions? Here is the right place. In this video, you will learn how to...
Read more >How to fix 'BOOTMGR image is corrupted' on a boot flash drive
Step 1: Make a bootable hard disk! Download a program called balena etcher and install it. Find the .iso file for the os...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
“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 😕
Same problem using etcher on Debian Stretch with Debian’s ISO (original or remastered Debian Stretch, LMDE3, Primtux …) on different usb stick (brand and space). It works to copy and boot the image but if you want to use gparted for partitioning the HD, “Driver descriptor indicates a physical bloc size of 2048 bytes, but Linux says 512 bytes.”. It is impossible to make any operation on the stick (copy or delete a file for exemple) It was also impossible to reuse the stick if I don’t use the sudo dd if=/dev/zero of=/dev/sdX bs=512 count=1 et build a new ms-dos table of partition (like it was describe in documentation)