No bootable partition found - for the SECOND time. Rescue Disk not working.
Open source disk encryption with strong security for the Paranoid
Brought to you by:
idrassi
Menu
▾
▴
Hello,
I have a problem: My system drive is encrypted (newest VC version) and when trying to boot, Windows starts an automatic repair. This always fails and when proceeding, it only shuts the PC down.
When trying to use the Rescue Disk, it says "No bootable partition found." When restoring the headers, it says that it restored the boot loader, but it does not work.
For the other options, it always says the password would be wrong.
And when trying to mount on an other PC, it also says the password is wrong.
This is weird, because it happened the second time now. The drive is 100% fine according to Crystal Disk Info and still shown in BIOS/UEFI.
Could this be because of a Windows update?
How can I prevent this from happening??
My data is backed up, so dont worry about that.
Thank you in advance.
Last edit: darkx 2020-04-21
This has also happened to me. I'm guessing that it's because the image was not written back to the hard drive quite correctly. I'm guessing that startup repair can't actually do anything because the hard drive is atually not accessible yet, still encrypted, but for it to just shut down right away without giving you options, I'd guess that the startup repair partition is also messed up. What you could try doing is to boot up your working system, run cmd as an administrator, run diskpart, then "list volume" then "select volume 0" "assign letter=<whatever>" and assign drive letters for all teh volumes, then exit, and then run chkdsk /f on each assigned drive letter and see if that helps. But still, I know, I've been facing this issue, too, and it's frustrating to have to fix a system that supposedly was working fine before.</whatever>
Oh, I think I forgot to mention that I used a cascaded encryption. Now using AES only which seems to work fine.