If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Rate Thread | Display Modes |
#1
|
|||
|
|||
Macrium Error 9 And Trust in Microsoft
I ran into this error today, while making a backup
of the Win10 Insider HDD. It seems the $BITMAP information is incorrect on the Insider. This causes a problem with Macrium Reflect (and potentially other software of the backup persuasion). https://knowledgebase.macrium.com/di...uild+18234+Bug The thing is, Microsoft has been maintaining the release number on the NTFS file system at 3.1 all through the Win10 period. Indicating that all the modern OSes are using *exactly* the same file system features. It has not been indicating that the design of the file system has changed. There's basically no version control, over what file system features have been buggered with. First it was the $MFTMIRR getting broken. Then, it was addition of some Reparse Point types, which seem to be handled by other OSes OK, but the other OSes, if you run CHKDSK, may do weird things to the partition. I don't really feel all that comfortable about that one. I don't dare run WinXP CHKDSK on an NTFS partition that's been over in the Win10 machine, because I no longer know if that is safe. And now, it appears that (perhaps) the $BITMAP is being lazy-evaluated, to avoid "wearing" an SSD by writing that part while the OS is running. By not writing it, if the OS crashes or there is a power failure, what protects that field ? Can the Journal be relied on, plus boot-up cleanup actions, to restore the $BITMAP properly ? Is there some nice web documentation from Microsoft on the subject ? ******* OK, so they caused my copy of Macrium to fail. This means I'm forced to bump up the version of Macrium, to cover that disk. Then, when 1903 is released, it's going to have that "bug" in it. The problem then spreads to all the Win10 installs which will be upgraded in a month or two. Macrium claims some backup software already calls an API, in place of reading the $BITMAP directly, and they will get the right answer. But which programs do that ? ******* And then the question is, why should we be trusting Microsoft exactly ? 1) Changing a spec, without updating the version number. 2) Seemingly causing "partner" companies to chase after them with a mop and pail. VirtualBox went through hell maybe a year or more ago, and like Macrium, didn't make a big stink about the extra labor entailed. 3) Destroying trust from an end-user perspective, by adding more and more "special handling" procedures for the "rolling release OS". I'm rapidly losing the ability to keep track of what I should be doing! To give a vivid example, if I boot Win10 and have data disks connected, Win10 *will* damage the $MFTMIRR. Then, I have to run Win7 CHKDSK to repair it. The CHKDSK log makes no mention that the $MFTMIRR was repaired, but it has been. So when I'm planning procedures, I have to remember: 29) *Don't* boot Win10, while the data disks are connected, or you'll have to slide the Win7 disk back in, boot up, and CHKDSK all the NTFS partitions. Such is life, Paul |
Thread Tools | |
Display Modes | Rate This Thread |
|
|