Attempting to clone doesn't work because target drive is too small, however the difference is negligible
See original GitHub issue- Etcher version: 1.5.111
- Operating system and architecture: Windows 10, 64-bit
- Image flashed: N/A, cloning an image
- Do you see any meaningful error information in the DevTools? N/A
I have 2 SD cards, original is 32GB, target is 31.9 GB. Etcher won’t clone it because the target is too small, which is true, but there is definitely empty space on the original. Is there a was to bypass that check? Thanks!
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Clonezilla Destination Disk Is Too Small - Fixed Now!
This page shows you how to fix the Clonezilla destination disk is too small error with a workaround. You can also turn to...
Read more >Clonezilla won't clone to a smaller disk - Super User
Officially, Clonezilla requires the destination drive to be the same size or larger than the master drive. However, it can be done.
Read more >Clone Hard Disk Shows Wrong Size | Here's How to Fix and ...
Are you troubled by the “cloned hard disk shows wrong size” issue? Don't worry. This post analyzes the cause and provides solutions to...
Read more >Troubleshooting of a Failed Hard Drive to SSD Cloning
When you clone a hard drive to an SSD, there are chances that you could encounter problems with the process of cloning hard...
Read more >[IMPORTANT] CLONING - How NOT to do this | Acronis Forum
It is Highly Recommended to check both the Source and Target drives for any errors before attempting to clone - any bad sectors...
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
It’s still more data than what Etcher would be allowed to write, i.e. you can’t fit 4cm in 3.9cm, even if the difference is negligible, given there’s no way Etcher can possibly know what data to skip (outside of some exceptions, like ISOs). You can either increase the target data size or, as @shawaj mentioned, reduce the source data size.
@lurch exactly 😃