'No bootable partition found' even after decrypting
Open source disk encryption with strong security for the Paranoid
Brought to you by:
idrassi
Menu
▾
▴
I encrypted my system drive which was on a single disc partitioned into two drives, the Windows system and a data partition.
After a few boots, it stopped responding when I entered my password so I rebooted it whilst it was attempting to load and was then met with the "no bootable partition found" message. So I decrypted. After decryption and restoring the original system loader it still has the Veracrypt loader with "no bootable partition found". The windows install and a bootable unix OS don't detect that the drive even exists in the system. Any suggestions what I can do next?
What do you mean by the boot stopped working? Did you have any specific error message?
Anyway, the symptoms you describe is those of a hardware failure since your drive stopped working suddenly and the bootable Linux can't detect the drive.
I'd entered my password and it was verifying for 5 mins rather than a minute or so as it had been previously so I forced a reboot. If the disk has failed how come VeraCrypt can see it?
Since VeraCrypt takes more time, it means that it could not open the normal header and it was looking for the hidden OS header.
If the password is correct, this means that the volume header is corrupted and one solution would have been to use the Rescue Disk to restore the volume header and try again. Unfortunately, some software have the bad habit of messing up with the boot loader (https://veracrypt.codeplex.com/wikipage?title=Incompatibilities)
Since you decrypted your drive, your data are on their so there is nothing to worry if the drive is OK.
The restoration of the original system loader should have removed the VeraCrypt booloader and I can't explain why it doesn't work for you.
Also the fact that the Windows and Linux bootable disks don't detect your drive is very suspicious. They should see it if it is working regardless of its content.
basically, your drive is visible through BIOS (that why VeraCrypt bootloader appears) but it is not visible through Windows/Linux install media. This leaves two possibilities:
For the second possibility,you should connect the drive to another PC or through IDE. The SATA missing driver is a common issue. Did you try booting using GParted?
Thanks for your reply. I've replaced the drive (about due to anyways) so I'm going to try getting access through USB. It was connected through SATA and I didn't try GParted.