I encrypted my system partition ssd using veracrypt 1.23 for windows but was unable to boot.
I've decrypted the entire ssd using the rescue disk but was still unable to boot despite trying:
disabling secure boot
loading the original windows loader from boot parition
After a few days of unsuccessful attempts I've decided it is easier to just retrieve what data I can from the disk using another system. I've removed the ssd and connected to another machine running Ubuntu to recover data using the veracrypt GUI but I cannot seem to mount it. I've connected the drive using a NVMe m.2 ssd enclosure.
When connected, the drive appears as /dev/sdb: in the veracrypt GUI. I try to mount the whole device
I select 'Mount partition using system encryption (preboot authentication) enter my veracrypt password
After a few seconds I am greeted with an input/output error: dev/sdb Veracrypt::File::Read:293
Doing the same steps a second time results in a different error 'No such file or directory: /dev/sdb veracrypt::file:open232'
As indicated by the error message under Linux, this is not a VeraCrypt
issue but rather a problem with the drive itself or with the way it is
connected to the Linux system (faulty connector or bad driver).
Concerning the original problem, you didn't give much information about
the issue. Do you get the VeraCrypt password prompt and then Windows is
unable to boot or the machine directly boots into Windows Repair? In
almost all cases, it is not necessary to decrypt the drive and simple
troubleshooting steps can make Windows boot again. Sometimes, it is just
a matter of manually selecting VeraCrypt Bootloader entry in the BIOS.
In other cases, using the Rescue Disk to restore VeraCrypt Bootloader
fixes the problem.
Can you try the above suggestions?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Do you get the VeraCrypt password prompt and then Windows is
unable to boot or the machine directly boots into Windows Repair? In
almost all cases, it is not necessary to decrypt the drive and simple
troubleshooting steps can make Windows boot again. Sometimes, it is just
a matter of manually selecting VeraCrypt Bootloader entry in the BIOS.
In other cases, using the Rescue Disk to restore VeraCrypt Bootloader
fixes the problem.
I placed the drive back into the laptop and when it boots you're shown 'password' and the manufacturer logo. After entering the password and pin (none) 'authorising' is displayed then success. Then 'windows starting automatic repair' appears.
Restoring the VeraCrypt bootloader then selecting veracrypt (DCS) loader from the boot squence results in being asked for a password and pin. After entering them the display says 'success' then it boots directly into windows automatic repair.
Any ideas?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You mentioned that you used a rescue disk to decrypt the entire drive. You should not now need to use VeraCrypt in Linux to mount it.
Boot up Linux without connecting the drive. In a console type
dmesg -w
This will show you the system kernel messages and continue to show new ones as they occur. Now plug in the drive. You should see the kernel messages when the drive is recognized, along with any partitions on it. What partitions is it showing?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is troubling. There are no partitions being displayed when you plug the drive in.
When you first encrypted it, how far in that process did you get? Did you make it past the first reboot and password entry?
I've decrypted the entire ssd using the rescue disk
You decrypted it, but...
I placed the drive back into the laptop and when it boots you're shown 'password'
...it still asks for a password when you put the drive back into a laptop? And when you enter the password, it says "success"???
This is a /very/ odd set of circumstances. It doesn't make much sense.
Before you go further, do you have the resources to make an entire disk image? This is advisable in any case when you start having trouble with VeraCrypt. It is something I highly encourage. VeraCrypt problems make your data very fragile, and doing the wrong thing or the right thing in the wrong order can cause you to lose everything. If you can make an image now, do it, but it may be too late already.
Is this drive an MBR style partition or GPT? Is the computer an EFI boot, or legacy? The reason I ask is I am trying to figure out why there are no partitions showing up when you plug in the drive.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The drive partition is GBT and the computer uses EFI boot.
This is troubling. There are no partitions being displayed when you plug the drive in.
dmesg -w does not show any partitions, but using parted -l I'm able to see the partitions on the connected drive. Equally, partitions are also visible using the disks utility in linux.
Model: JMicron Tech (scsi)
Disk /dev/sda: 512GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 683MB 682MB fat32 EFI system partition boot, esp
2 683MB 817MB 134MB Microsoft reserved partition msftres
3 817MB 497GB 496GB Basic data partition msftdata
4 497GB 498GB 984MB ntfs hidden, diag
5 498GB 511GB 12.8GB ntfs hidden, diag
6 511GB 512GB 1158MB ntfs hidden, diag
When you first encrypted it, how far in that process did you get? Did you make it past the first reboot and password entry?
At the first reboot, the system booted right into windows repair.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I made an entire disk image(partition) before with windows( it was encrypted before hand) but...it really doesn't make an image of the first boot part. To make it work I had to reinstall windows to get some portions of the booting portion right. Copyed a back up image of the (encrypted) partition to the disk, then run the veracrypt repair boot disk to get the password boot section repaired. It really sucked.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Are you suggesting an image of the disk does not correctly backup the boot parition correctly? Or that there is simply something wrong with my boot parition?
So you suggest:
Create a fresh install of windows to a new disk
Replace the main encrypted image with my backup image
Using the Veracrypt repair USB, repair the boot parition
Is that correct?
Any ideas on how to do this from linux without having to run a windows install? I'm just trying to get the encrypted data from the disk, not reinstall windows.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I encrypted my system partition ssd using veracrypt 1.23 for windows but was unable to boot.
I've decrypted the entire ssd using the rescue disk but was still unable to boot despite trying:
After a few days of unsuccessful attempts I've decided it is easier to just retrieve what data I can from the disk using another system. I've removed the ssd and connected to another machine running Ubuntu to recover data using the veracrypt GUI but I cannot seem to mount it. I've connected the drive using a NVMe m.2 ssd enclosure.
Any ideas on what do try?
Anyone?
As indicated by the error message under Linux, this is not a VeraCrypt
issue but rather a problem with the drive itself or with the way it is
connected to the Linux system (faulty connector or bad driver).
Concerning the original problem, you didn't give much information about
the issue. Do you get the VeraCrypt password prompt and then Windows is
unable to boot or the machine directly boots into Windows Repair? In
almost all cases, it is not necessary to decrypt the drive and simple
troubleshooting steps can make Windows boot again. Sometimes, it is just
a matter of manually selecting VeraCrypt Bootloader entry in the BIOS.
In other cases, using the Rescue Disk to restore VeraCrypt Bootloader
fixes the problem.
Can you try the above suggestions?
Hi Mounir,
I placed the drive back into the laptop and when it boots you're shown 'password' and the manufacturer logo. After entering the password and pin (none) 'authorising' is displayed then success. Then 'windows starting automatic repair' appears.
Restoring the VeraCrypt bootloader then selecting veracrypt (DCS) loader from the boot squence results in being asked for a password and pin. After entering them the display says 'success' then it boots directly into windows automatic repair.
Any ideas?
Hi Naj,
You mentioned that you used a rescue disk to decrypt the entire drive. You should not now need to use VeraCrypt in Linux to mount it.
Boot up Linux without connecting the drive. In a console type
This will show you the system kernel messages and continue to show new ones as they occur. Now plug in the drive. You should see the kernel messages when the drive is recognized, along with any partitions on it. What partitions is it showing?
Hi Kurt,
[ 5549.206226] usb 2-1: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[ 5549.231061] usb 2-1: New USB device found, idVendor=152d, idProduct=0562, bcdDevice= 2.02
[ 5549.231068] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 5549.231072] usb 2-1: Product: External
[ 5549.231076] usb 2-1: Manufacturer: JMicron
[ 5549.231079] usb 2-1: SerialNumber: DD5641988388D
[ 5549.240557] scsi host4: uas
[ 5549.241569] scsi 4:0:0:0: Direct-Access JMicron Tech 0202 PQ: 0 ANSI: 6
[ 5549.242549] sd 4:0:0:0: Attached scsi generic sg1 type 0
[ 5550.412622] sd 4:0:0:0: [sdb] 1000215216 512-byte logical blocks: (512 GB/477 GiB)
[ 5550.412624] sd 4:0:0:0: [sdb] 4096-byte physical blocks
[ 5550.412786] sd 4:0:0:0: [sdb] Write Protect is off
[ 5550.412787] sd 4:0:0:0: [sdb] Mode Sense: 5f 00 00 08
[ 5550.413033] sd 4:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 5550.424831] sd 4:0:0:0: [sdb] tag#16 data cmplt err -71 uas-tag 1 inflight: CMD
[ 5550.424833] sd 4:0:0:0: [sdb] tag#16 CDB: Read(10) 28 00 00 00 00 20 00 00 08 00
[ 5560.795219] usb 4-1.4: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 5564.503429] r8152 4-1.4:1.0 enx00e04c680012: carrier on
Can't see any partition there, yet in veracrypt I can see the multiple partitions on the drive. Any ideas?
This is troubling. There are no partitions being displayed when you plug the drive in.
When you first encrypted it, how far in that process did you get? Did you make it past the first reboot and password entry?
You decrypted it, but...
...it still asks for a password when you put the drive back into a laptop? And when you enter the password, it says "success"???
This is a /very/ odd set of circumstances. It doesn't make much sense.
Before you go further, do you have the resources to make an entire disk image? This is advisable in any case when you start having trouble with VeraCrypt. It is something I highly encourage. VeraCrypt problems make your data very fragile, and doing the wrong thing or the right thing in the wrong order can cause you to lose everything. If you can make an image now, do it, but it may be too late already.
Is this drive an MBR style partition or GPT? Is the computer an EFI boot, or legacy? The reason I ask is I am trying to figure out why there are no partitions showing up when you plug in the drive.
Hi Kurt,
I've made an entire disk image using DD.
The drive partition is GBT and the computer uses EFI boot.
dmesg -w does not show any partitions, but using parted -l I'm able to see the partitions on the connected drive. Equally, partitions are also visible using the disks utility in linux.
Model: JMicron Tech (scsi)
Disk /dev/sda: 512GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 683MB 682MB fat32 EFI system partition boot, esp
2 683MB 817MB 134MB Microsoft reserved partition msftres
3 817MB 497GB 496GB Basic data partition msftdata
4 497GB 498GB 984MB ntfs hidden, diag
5 498GB 511GB 12.8GB ntfs hidden, diag
6 511GB 512GB 1158MB ntfs hidden, diag
At the first reboot, the system booted right into windows repair.
Any other ideas?
"...Hi Kurt,
I've made an entire disk image using DD...."
I made an entire disk image(partition) before with windows( it was encrypted before hand) but...it really doesn't make an image of the first boot part. To make it work I had to reinstall windows to get some portions of the booting portion right. Copyed a back up image of the (encrypted) partition to the disk, then run the veracrypt repair boot disk to get the password boot section repaired. It really sucked.
Hi John,
Are you suggesting an image of the disk does not correctly backup the boot parition correctly? Or that there is simply something wrong with my boot parition?
So you suggest:
Is that correct?
Any ideas on how to do this from linux without having to run a windows install? I'm just trying to get the encrypted data from the disk, not reinstall windows.