Hello, I encrypted my main ssd with my windows installation. I left my PC on overnight and when I came back the following day, the computer would not wake up. I turned the computer off and turned it back on and I received a message from my bios to select the proper bootable media. My encrypted SSD was no longer being detected in the bios.
The only thing I could find online was to take the recovery .iso file and burn it to a disk and then boot from the disc and go from there. I wanted to boot from a USB drive because CD/RW drives are hard to find these days and the one I ordered online won't be here quick enough. I found a thread that suggested using the program YUMI to burn the recovery .iso to the USB drive. I was able to do so and the computer did boot from the USB drive but it did not load into the Veracrypt recovery.
Instead, it loaded a cmd center / bios type screen with random commands that I could type in. I read on the thread that suggested to use YUMI that there was a file you may need to edit to make the Veracrypt recovery select the proper drive to recover, the file that they mentioned in that thread was the same file that seemed to have been executed.
I do not know how to get the Veracrypt recovery program to boot up and if I could / if I had to edit the file to make it select the proper drive, I don't know what the drive name is because now it is not being recognized. The drive was perfectly fine prior to the encryption and it was perfectly fine after the test reboot. Does anyone have any tips or leads as to what I should try next?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
No, the SSD does not show up in the BIOS. I think the encryption hides the headers or corrupted the SSD header. It would be incredibly coincidental for the drive to physically fail when it did. It's more likely that I fucked up the encryption somehow.
I have the Veracrypt Recovery disc working now, however it says no bootable media found still. I can continue to the repair options but when I enter the password correctly, it states that it is an invalid password. I am thinking that Veracrypt recovery is not trying to enter the password to decrypt the correct drive and that's why it thinks the password is wrong? What I need to do is somehow get the SSD to be recognized again, anyone know how to accomplish this?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
No, the SSD does not show up in the BIOS. I think the encryption hides the headers or corrupted the SSD header. It would be incredibly coincidental for the drive to physically fail when it did. It's more likely that I fucked up the encryption somehow.
Encrypting the drive does not hide it in the BIOS anyhow. If it does not show up in the BIOS, this clearly indicates that either the drive is physically damaged (which cannot be done by VeraCrypt) or any connector (data or power) is loose or damaged.
I have the Veracrypt Recovery disc working now, however it says no bootable media found still.
When the drive is not physically detected, that's the obvious result.
What I need to do is somehow get the SSD to be recognized again, anyone know how to accomplish this?
Check connectors of the drive / insert it into another port on your motherboard. Last resort: try it with another computer.
Greets
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello, I encrypted my main ssd with my windows installation. I left my PC on overnight and when I came back the following day, the computer would not wake up. I turned the computer off and turned it back on and I received a message from my bios to select the proper bootable media. My encrypted SSD was no longer being detected in the bios.
The only thing I could find online was to take the recovery .iso file and burn it to a disk and then boot from the disc and go from there. I wanted to boot from a USB drive because CD/RW drives are hard to find these days and the one I ordered online won't be here quick enough. I found a thread that suggested using the program YUMI to burn the recovery .iso to the USB drive. I was able to do so and the computer did boot from the USB drive but it did not load into the Veracrypt recovery.
Instead, it loaded a cmd center / bios type screen with random commands that I could type in. I read on the thread that suggested to use YUMI that there was a file you may need to edit to make the Veracrypt recovery select the proper drive to recover, the file that they mentioned in that thread was the same file that seemed to have been executed.
I do not know how to get the Veracrypt recovery program to boot up and if I could / if I had to edit the file to make it select the proper drive, I don't know what the drive name is because now it is not being recognized. The drive was perfectly fine prior to the encryption and it was perfectly fine after the test reboot. Does anyone have any tips or leads as to what I should try next?
Here is the thread that I referenced in the OP.
https://sourceforge.net/p/veracrypt/discussion/technical/thread/b32f9cb2/
When you take a look into the BIOS / UEFI, is your SSD still listed there? If not, it's most likely a hardware issue.
No, the SSD does not show up in the BIOS. I think the encryption hides the headers or corrupted the SSD header. It would be incredibly coincidental for the drive to physically fail when it did. It's more likely that I fucked up the encryption somehow.
I have the Veracrypt Recovery disc working now, however it says no bootable media found still. I can continue to the repair options but when I enter the password correctly, it states that it is an invalid password. I am thinking that Veracrypt recovery is not trying to enter the password to decrypt the correct drive and that's why it thinks the password is wrong? What I need to do is somehow get the SSD to be recognized again, anyone know how to accomplish this?
Encrypting the drive does not hide it in the BIOS anyhow. If it does not show up in the BIOS, this clearly indicates that either the drive is physically damaged (which cannot be done by VeraCrypt) or any connector (data or power) is loose or damaged.
When the drive is not physically detected, that's the obvious result.
Check connectors of the drive / insert it into another port on your motherboard. Last resort: try it with another computer.
Greets