View Single Post
  #9  
Old March 20th 19, 05:47 PM posted to alt.comp.os.windows-10
MrTsquare
external usenet poster
 
Posts: 21
Default Macrium Error 9 And Trust in Microsoft

In article ,
lid says...

MrTsquare wrote:
In article ,
lid says...
MrTsquare wrote:
In article ,
lid says...
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 ?

*******


Maybe I have been misleading you by saying
Macrium couldn't see the disc. As I said in my
first post, Macrium apparently will not select
disc2 apparently cause it cannot see a file
system on disc2. The others show NTFS, but
disc2 shows "file system empty". Kindof a black
hole disc. That's why I tried replacing
Macrium, thinking that it had been corrupted by
the power glitch.
T2
Ads