More fbreseal strange behavior

[Slobodan Brcin \(eMVP\)]

Hi Desi,

Are you 100% sure that you are booting from disk 1?
BIOS-es tend to swap disk numbers so that disk that you choose to boot from is actually disk 0.
What is written in your boot.ini that you use? This value is only relevant information that we need to know.

In any case I find hard to believe that all information's that you gave us are accurate, since I can't explain this unnatural driver
letter assignment.

Regards,
Slobodan

 

[Desi]

KM,

I did not apply a ghost image to the drive, I merely made an image so
that I could return to it later.

So the volume GUID should not have changed - Right?

I merely configured the machine, ran fbreseal, shut down, made an
image, then turned the machine back on. I wouldn't expect the drive
mounting information to change as a result of running fbreseal, but it
apparently did.

 

[KM]

Desi,

You are right. I just checked the thread, you have already mentioned you are running the post FBA image on the same hardware.
GUIDs should be the same. Please disregard my earlier comment.

I am not yet convinced this is fbreseal bug.
What did you mean by "made an image" below?

Also, what is your boot.ini content?
Also, try to compare the [HKLM\System\MountedDevices] values BEFORE the fbreseal, AFTER the fbreseal offline, AFTER the first boot
after the fbreseal.

 

[Desi]

Slobodan,

My Boot.ini shows:
multi(0)disk(0)rdisk(0)partition(1)\windows="Microsoft Windows XP
Embedded" /fastdetect

When I referenced drive 0 & drive 1, I was using the values provided by
diskpart when running under WinPE. In that case, Disk 0 was the drive
located in the primary master IDE location, and disk 1 was on the
secondary master IDE location.

 

[Slobodan Brcin \(eMVP\)]

Desi,

When I referenced drive 0 & drive 1, I was using the values provided by
diskpart when running under WinPE.

This was the reason why you did not understand the problem. WinPE show you information's based on current disk order which usually
change each time you change disk boot order.

My Boot.ini shows:

Only relevant disk order is the one that work when specified in boot.ini.
So if you do not change boot.ini your XPe disk reported by BIOS is always Disk 0 and it changes each time you change boot disk in
BIOS.

Boot disk is in most cases Disk 0. And OS disk is ALWAYS the one that you specify in boot.ini.

Regards,
Slobodan

 

[Desi]

My issue was that the target device was booting with the drives just as
I wanted (Whatever they were, drive 0 or drive 1), and after running
fbreseal the drives are now mounted in a different order. (The opposite
of what they were before fbreseal).

If the volume GUID did not change, and the location of the drives did
not change, and the mounting was already in the registry, what is it
that fbreseal resets that causes the drives to be reordered? I used
the same target device to create, seal, and reopen the image.

I will follow up with some before/after registry settings, etc. later,
after the urgency of the moment passes and I deliver some items. I
would like to get to the bottom of the issue at some point, so that it
does not come back and bite me at a later date.

To everyone that has provided help in this thread, I want to express my
thanks. This group is indeed a very valuable resource.

Desi

 

[Slobodan Brcin \(eMVP\)]

Hi Desi,

I have reread this complete thread and can't make sense on information's that you have provided.

Is following true if not please let us know what else do you use.

Drive 0: - Primary Master
- Partition 1 = 1GB

Drive 1: - Secondary Master <----- Selected as boot in BIOS?
- Partition 1 = 384 MB (boot.ini and XPe)
- Partition 2 - 550 MB

Arc path from Boot.ini:
multi(0)disk(0)rdisk(0)partition(1)\windows


Is above information's that I gathered from this thread 100% correct?

Regards,
Slobodan

PS:
Observe rdisk(x) value x - tell you number or disk that contain XPe.