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
OK, when you have the Macrium Rescue CD booted, you have some tools:
1) A Command Prompt icon.
2) "diskpart" in Command Prompt (equiv to Disk Management)
diskpart
list disk
select disk 2
list partition
select partition 3
detail partition
exit
That's how you get some WinPE detected details about your disks.
You can iterate over disks and partitions, and dump info about
all of them.
3) Macrium has its own Explorer-like icon on the desktop.
Look in there for the partitions. Are they present ? Or missing ?
If present, it implies Macrium "remembers" something about
that disk. But, where would that info be stored ?
Is there a "LOCK" file at the top root level of any partition
on that disk, signaling the disk is "in usage by Macrium" ?
The thing is, if there are identical disk identifiers, that
can cause a problem. But normally, you only see evidence
of that system-wide, if Disk Management shows a disk on
the left hand side as being "Offline". That's evidence
of one of two things:
a) Two disks have the same identifier, coming from around byte
442 or so of the MBR. Other disk identifiers which could be
identical, don't hurt anything. Identical labels on disks
like "DATA" "DATA" "WIN10" "WIN10" don't hurt either. Only
the disk identifier around byte 442 is an issue.
b) You can manually set a disk to the Offline state, which
helps if TXF (NTFS transactions) won't allow a USB hard drive (HDD)
to be Safely Removed. When this is done on a persistent OS,
the OS "remembers" the offline state, so you have to switch
it online again the next time you're in that OS.
Since you see the disk under all ordinary circumstances, we can't
blame either of these reasons for the indigestion in Macrium.
I'm stumped as to what to blame it on. Nothing is a match.
*******
Using a Linux LiveCD, you can install "disktype" and do
sudo disktype /dev/sdb # dump info on disk 2
and it will tell you what the partitions are. Some
file systems, it uses multiple checks that the file system
is what it says it is. So if it said "5 of 5 FAT32", then
you'd know that the five characteristic checks passed. Not
all file systems have thorough checks like that.
And if I was in the room there right now, that's the only
additional check I'd do.
I have a Cygwin copy of "disktype.exe", which I use on this
machine, and that saves me the bother of booting Linux. If you
already have Cygwin set up, and know how to use the package
manager to add stuff, it would take no time at all to add
that one.
http://disktype.sourceforge.net/
No one seems to be interested in doing a Windows version,
which would likely require some small namespace tweaks
in there somewhere. The Cygwin version still uses this
syntax, which is not a Windows syntax.
sudo disktype /dev/sdb # sdb would be the second row of Disk Management
*******
The fact that $MFTMIRR is getting damaged by Win10, doesn't
seem to affect Macrium that I can see. And the $BITMAP problem
should not have affected things when using the Macrium
Rescue CD, since the file system is "at rest" at that point,
and the $BITMAP is likely correct at that point in time.
Paul