USBoot w/XPsp2 not booting after DiskCryptor system encryption, BSOD Stop Code = UNMOUNTABLE_BOOT_VOLUME External links Options

[Zoso]

Im having a really hard time getting a working encrypted system USB drive to boot on my new notebook (Intel Centrino Duo with ICH9 Chipset and Controllers)

as mentioned in this thread:
http://www.boot-land.net/forums/index.php?showtopic=8802
thanks again to Jaclaz for lots of help here.

I have successfully booted several USB devices in this notebook with USBoot prepaired XPsp2 in various configurations but it fails to boot after any type system encryption on USB drives but after the encryption these USB devices do successfully boot in my desktop PC (AMD Athelon)

system encryption successfully boots in this notebook from the internal HDD but not from USB drives allthough the USB drives also boot successfully in it without the encryption

I have tried so far with TrueCrypt, DriveCrypt Plus, and DiskCryptor.


with TrueCrypt and DriveCrypt on the USBoot prepaired USB device it only gets only as far as a blinking cursor after entering the password.

with DiskCryptor it gets much father along, all the way to the point just after initializing "ArcGuard" just before disk checking. it seems to fail at the start of the disk check but I cant say for certain.

fails with BSOD Stop Code "UNMOUNTABLE_BOOT_VOLUME"


Jaclaz, I would like your help starting from scratch again if you are still willing to guide me through your proccess of elimintation for tracking down this problem.

unlike the other system encryption software DiskCryptor does not offer a Pre Boot Authentication test so I must encrypt first. this is not good for experimenting since it takes some time so I would like to test with a 40GB USB HDD except only using 8GB of the drive. would that be reasonable or should I use the full amount? I ask first because the full amount would add hours to each retry due to the lack of pre test in DiskCryptor.


in my previous attempts I have been starting with a fresh install of XPsp2 with only chipset and memory drivers added then prepping with USBoot with no options. the documentation of USBoot is also severely lacking as to what each steps alternats do.

Im not opposed to leaning a manual way to prepair OS for USB booting but I dont have alot of time to spare and especially for experiments that may or may not succeed. the USBoot method does work in this notebook without encryption and with encryption in my desktop. if I can figure out how to skip its disk checking phase that might be the issue (just thinking aloud, obviously I have no clue)

if anyone here has any insight into what it might possibly be causing the BSOD in this case then Please post your ideas or suggestions. I really need this to work.

thanks

[was_jaclaz]

From what you report, it seems to me that:
the device is partitioned/formatted in such a way that (without encryption):

• it works on the desktop
• it works on the laptop

and, as soon as the BOOT CODE (in either the MBR or PBR, or BOTH) is changed to one of the Truecrypt, DriveCrypt Plus, or DiskCryptor ones:

• it continues working on desktop
• it STOPS working on the laptop

Thus the problem must be in some incompatibilities between the laptop BIOS and the "encrypt apps" BOOT CODE.

Or in other words, it is possible that the setup is in some way NOT "kosher", and while the Desktop BIOS "accept" this, being of "largish view", the laptop BIOS refuses to, being a little, provincial, narrow minded BIOS.

The only possibilty we (actually you ) have is to try and create a "very compatible" partitioning/format of the stick/disk and hope that it will be enough to overcome the problem, since the BIOS CANNOT be touched/hacked and, as well, whilst doable, the procedure of patching/hacking the BOOT CODE is beyond the scope 8and even if succesful may provoke a reversion, i.e. succeeding in booting on the laptop but failing to do so on the desktop.

Of the three behaviours you described, the DiskCryptor actually seems the most "promising", since the STOP error comes from a Windows file, so that the problem might derive from somethng to be corrected "at a higher level or merely at the drive addresses.



jaclaz

[Zoso]

the laptop BIOS refuses to, being a little, provincial, narrow minded BIOS.

great, my really old desktop BIOS out performs the latest laptop BIOS.

The only possibilty we (actually you wink.gif) have is to try and create a "very compatible" partitioning/format of the stick/disk and hope that it will be enough to overcome the problem

I would like to try that, what do you reccomend? as you know, Im game for just about anything at this point.

Of the three behaviours you described, the DiskCryptor actually seems the most "promising", since the STOP error comes from a Windows file, so that the problem might derive from somethng to be corrected "at a higher level or merely at the drive addresses

yes, I agree that DiskCryptor seems to be the most promising.

Ive been reading about the stop codes. here is an informative link Ive found on them:

http://www.geekstogo.com/forum/Windows-XP-...des-t43519.html

not that it will help you Jaclaz, I just linked for my referance and other noobs may find it helpful.

from other reading I recall a modified NTDETECT was a solution in some of these "INACCESSABLE_BOOT_DEVICE" USB booting cases and seems closely related. I havnt tried it, just making a note for myself.

it also seems that the Intel ICH family chipsets comes up in more cases than not when searching for USB boot errors involving "UNMOUNTABLE_BOOT_VOLUME"

might be worth mentioning.

[Zoso]

just reporting that with diskcryptor version 0.09 this problem went away.

[Wonko the Sane]

just reporting that with diskcryptor version 0.09 this problem went away.

Happy to know that problem is solved.

Wonko