![]() |
|
Computer booting into drive which doesn't exist? - Printable Version +- Hack Forums (https://hackforums.net) +-- Forum: Tech (https://hackforums.net/forumdisplay.php?fid=444) +--- Forum: Computing (https://hackforums.net/forumdisplay.php?fid=88) +---- Forum: Microsoft Windows (https://hackforums.net/forumdisplay.php?fid=347) +---- Thread: Computer booting into drive which doesn't exist? (/showthread.php?tid=4185921) |
Computer booting into drive which doesn't exist? - Keystroke - Apr 21, 2014 Hi guys, Earlier today I plugged a secondary hdd into my computer and installed Windows Server 2008r2 on it (My server's CPU didn't support hyper-v but my computer did), I did what needed to be done with Hyper-v then unplugged the hdd. I now expected my computer to boot into my primary truecrypt encrypted HDD but it doesn't; it tried to boot into Windows Server 2008R2 again which doesn't make any sense as the HDD which contains that OS is no longer in the computer! Bios detects my primary HDD as the only one available which is correct. Help please. Thanks. * - Aura - Apr 21, 2014 Is your HDD set to be the primary boot device ? Also, is your HDD plugged in SATA0 ? * - Keystroke - Apr 21, 2014 (Apr 21, 2014 11:20 AM)Aurа Wrote: Is your HDD set to be the primary boot device ? Also, is your HDD plugged in SATA0 ? Yes and yes. Don't know what else to write here but 35 characters. * - Aura - Apr 21, 2014 (Apr 21, 2014 11:24 AM)Keystroke Wrote: Yes and yes. When you boot, what happens ? You hit a black screen with a blinking cursor ? You get a message (if so, what one) ? * - Keystroke - Apr 21, 2014 (Apr 21, 2014 11:25 AM)Aurа Wrote: When you boot, what happens ? You hit a black screen with a blinking cursor ? You get a message (if so, what one) ? Windows failed to start File: \windows\system32\winload.exe Status: 0xc000000e The selected entry could not be loaded because the application is missing or corrupt. It then takes me to a screen asking me to choose which OS to boot into with the only option as ws2008r2 which isn't even in the computer..... * - Aura - Apr 21, 2014 (Apr 21, 2014 11:30 AM)Keystroke Wrote: Windows failed to start Are you able to boot in a Safe Mode ? * - Keystroke - Apr 21, 2014 (Apr 21, 2014 11:38 AM)Aurа Wrote: Are you able to boot in a Safe Mode ? No, it would be weird as hell if I could boot into safe mode seen as the harddrive I'm booting into is encrypted and the truecrypt boot loader hasn't asked me to enter my password :P * - Aura - Apr 21, 2014 (Apr 21, 2014 11:43 AM)Keystroke Wrote: No, it would be weird as hell if I could boot into safe mode seen as the harddrive I'm booting into is encrypted and the truecrypt boot loader hasn't asked me to enter my password :P Then you're honestly most likely fucked up. One of your system file used for boot is damaged and you need to repair it. Either in Recovery Mode (with a Windows 7 Recovery media) or Safe Mode. * - Keystroke - Apr 21, 2014 (Apr 21, 2014 11:49 AM)Aurа Wrote: Then you're honestly most likely fucked up. I don't think you fully understand the issue. If it was as simple as what you're saying then I'd just pop in a windows 7 disk boot into it open cmd and edit my boot configuration using bcdedit. What I'm asking pretty much is: Is there a way to manually start the truecrypt boot loader without the Truecrypt rescue disk? If not I'll just format the computer and have to live with the data loss. EDIT: I'm going to plug the WS2008R2 hdd back in alongside the Win7 truecrypt encrypted one, install truecrypt on WS2008R2 and mount the HDD as a drive, decrypt the entire thing save the files I need then re-encrypt. * - Aura - Apr 21, 2014 (Apr 21, 2014 11:52 AM)Keystroke Wrote: I don't think you fully understand the issue. If it was as simple as what you're saying then I'd just pop in a windows 7 disk boot into it open cmd and edit my boot configuration using bcdedit. Then why don't you ask this question in the OP ? Because no one can know what you're asking from it right now. And I have no idea. TrueCrypt is known to be pretty secure, so you're looking to call it's bootloader with a certain F key without the CD ? * - Keystroke - Apr 21, 2014 (Apr 21, 2014 11:56 AM)Aurа Wrote: Then why don't you ask this question in the OP ? Because no one can know what you're asking from it right now. I put the relevant information in the OP such as that it was encrypted with TrueCrypt, I wasn't going to push my own train of thought in the OP as that limits the responses you recieve. TrueCrypt is installing on my WS2008R2 HDD atm, I'm going to try decrypt the drive then boot into it. I'll let you know how this goes. * - Aura - Apr 21, 2014 (Apr 21, 2014 12:02 PM)Keystroke Wrote: I put the relevant information in the OP such as that it was encrypted with TrueCrypt, I wasn't going to push my own train of thought in the OP as that limits the responses you recieve. That's what I would do. This is what we used to do at work. All our laptops HDD are encrypted via PGP (Symantec), and when one had issues and we needed to access it, we were plugging it in slave mode in another computer having PGP installed and we were decrypting it. Best method to try right now. * - Polymath 1.0 - Apr 21, 2014 The problem is because you appear to have installed WS2008 to a machine that already had an O/S installed even though it was to a 2nd HD and not the original System HD. In essence you created a dual boot situation. That caused the Windows Server installer to create a daisy chained boot manager sequence in which the now non existent HD with Windows Server no longer exists but still holds the actual boot manager that would then be passed to the original true crypt boot handler. Had you simply reconnected the 2nd HD you could have booted into the 1st HD where the dual boot ended up over writing your original HDs boot manager on that 1st HD. Had you used True Crypt's rescue disk you could have simply rebuilt the boot manager and had access to your original HD and its' O/S and data without either connecting the 2nd HD or bothering with encrypting the O/S on it. That is the purpose of the True Crypt rescue disk, to gain access to the drive when the TrueCrypt boot manager is missing/corrupted. Take care |