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
cover that disk.

Then, when 1903 is released, it's going to have that

Funny you should mention it... I don't
understand most of what your post talks about,
but I locked onto "file system, Macrium and
power glitch".

I updated my 5 year old win7home system to
win10home last week. Did the update approach
rather than a clean install. (It appears to
have activated with no problem at all.) I have
been running Macrium Free for a few years with
no issues needing further exploration. After
installing Win10 and finding that it wasn't so
bad after all, just a little different, I
decided that I would need to start over on my
backups so I deleted all previous backups and
their XML command files and started over.
Listed below are my 4 drives.

Samsung SSD 840 EVO 500GB [Hard drive] (500.11
GB) -- drive 3, s/n S1DKNEAF600219Y, rev
EXT0DB6Q, SMART Status: Healthy

ST1000DM003-1CH162 [Hard drive] (1000.20 GB) --
drive 2, s/n S1DH893W, rev CC49, SMART Status:
Healthy

ST31000528AS [Hard drive] (1000.20 GB) -- drive
0, s/n 6VP40RF6, rev CC3E, SMART Status: Healthy

WDC WD10EACS-00D6B1 [Hard drive] (1000.20 GB) --
drive 1, s/n WD-WCAU43948314, rev 01.01A01,
SMART Status: Healthy

Updated Macrium to 7.2 and did the image on the
SSD and drive 0 with no problem (drive 1 is the
target). But then and somewhere in there we had
a wide area electrical glitch (just a second or
so).

When I went to select drive 2 I found that
macrium wouldn't select it and that as far as
Macrium knows, there is no file system on drive
2!! I honestly don't know if Macrium could see
a file system on disc 2 before the glitch.
Thinking about it for a while, I exited and
rebooted... no change. Tried to go on line to
the Macrium forums and post a question, but that
didn,t work cause I have the free version of
Macrium. Ok, maybe Macrium got sick. Deleted
all of the backups and command files again and
deleted/uninstalled Macrium. Reinstalled a new
download of Macrium and it still can't see disc
2.

Ok, get this... Win10Home is still perfectly
happy with disc 2 (see the Belarc status of the
drives above). Macrium is the only thing
unhappy with drive 2.

Any thoughts?
T2


You can do a backup from your Macrium Emergency CD.

That would prove that the disk detection, without
the Windows Registry to muddle things, was working.

Most of the failure mechanisms I know of, happen
when you try to run the backup. Just sitting in
the main screen, there should be fewer things to
go wrong.

And the Error 9 I was getting yesterday, I think
it was happening in the middle of a backup of
four partitions or so.

Paul