Etcher: Avoid "not large enough" checks for Windows drives that report themselves as 0.0 GB

Created on 1 Jun 2017  路  5Comments  路  Source: balena-io/etcher

See https://github.com/resin-io-modules/drivelist/issues/142

In summary, WMI sometimes fails to detect the real size of the drive, and detects a unreasonably small drive size (e.g. 8 MB) that gets coerced into 0.0 GB by the Etcher UI.

We have a real fix for this (which involves to re-write drivelist on C++), but let's make Etcher not take the size of these problematic drives into consideration for now.

windows bug

Most helpful comment

Yeah, my bad, I totally mixed things up. I'll rephrase the issue.

All 5 comments

Umm nope, this is in fact opposite to what @alexandrosm was suggesting in gitter!
We don't want to filter out (ignore) drives that report themselves as 8MB, we want to ignore the size they report, and allow any-size-image to be written to them anyway.

Yeah, my bad, I totally mixed things up. I'll rephrase the issue.

basically we should set a "minimum plausible drive size" and ignore any responses that are below that, simply reporting them as "unknown size", and as a result, not applying any size checks

...and there's then a nice symmetry between drives who's size we don't know, with images who's size we don't know ;-)

Was this page helpful?
0 / 5 - 0 ratings