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 ?

*******

OK, so they caused my copy of Macrium to fail. This
means I'm forced to bump up the version of Macrium, to

Macrium can't see disc 2 from there either.
Everything still works fine in Win10Home.
T2

The OS-installed version, has a registry entry that can
be used to "exclude" disks from the backup screen. Such
as excluding the disk that will be used to hold all the
..mrimg files and won't itself be backed up.

https://knowledgebase.macrium.com/di...lect+starts+up

HKLM : SOFTWARE : Macrium : Reflect
Disks DWORD 2 # Ignore "2", whatever that is

The reason for having the feature, is to save time
parsing a complicated drive structure. My test though
with Process Monitor, shows that for most regular
disks, not a lot of I/O is done on a disk at startup.
EXT4 partitions get a lot more inspection than
NTFS ones do.

The above page was found in this "jumbo" articles page.

https://knowledgebase.macrium.com/di...roubleshooting

Paul