Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Can not format drive after writing a Chrome OS image #759
After writing http://chromium.arnoldthebat.co.uk/weekly/Cx86OS-20160515010101.img.7z in DD Image mode, it seems impossible to get the drive reformatted in Rufus (or anything Windows for that matter - Even Disk Management on Windows 10 produces an error when trying to delete one of the many GPT partitions this Chrome OS creates).
Even if you try to zap a drive (Alt-Z) you get an error:
The only option to recover the drive seems to be to reformat it in Linux...
I believe this is a Microsoft issue (no application I tried seems to be able to write the drive), but it still would be nice to have some kind of workaround if achievable...
Further investigation seems to indicate that the problems only arise after Rufus tries to clean the drive that got the ChromeOS image. If you use something else to repartition/reformat the drive after that first image write (e.g. Windows'
We may have to investigate more closely how the
Spoke too soon. Even using
So this is really not related to anything specific Rufus does, though it appears
So one possible workaround would be to write the MBR or GPT partition tables with zeroes, in sector mode, as
Well, the real workaround here is NOT to call
This is the root of the issue really: Microsoft's
I have now applied this workaround, which will be in Rufus 2.10, and it seems to provide good results with the ChromeOS images (you can now perform all of Rufus regular operations on a drive where such an image has been applied, without encountering write errors).
Sadly however, this will not help people who already issued an