Windows 10: System encrypt "Disk not initialized" when plugging in. Worked...
Open source disk encryption with strong security for the Paranoid
Brought to you by:
idrassi
Menu
▾
▴
Hey!
I have a few system encrypted NVMe SSDs that Ive pulled out from laptops and inserted into NVME to USB-cases which I have used for a long time without any problems before. I just plug in the USB cable => Select the disk in Veracrypt and enter password without pre boot authentication and it mounts.
Now... For sure with a different VeraCrypt version i.e. the latest (and perhaps latest Windows 10 update), I cannot see the harddrives under Veracrypts "Select drive". And when I go to the Windows Disk Management, it asks me to Initialize the disk and chose either GPT or MBR.
Before...... It always worked. The exact same NVME to USB-case & cable. It would always pop up "Do you want to format this drive" instantly when I plugged in the drive. Now nothing.. I cant see the disk under "My Computer". Only as "Not Initialized" under Disk Management.
QUESTIONS:
What should I do?!
What should I chose?
How come it worked before but not anymore?
Although I am not sure its because I am using the latest Veracrypt version & Windows 10 updates, thats the only thing I can think of. Does not work 2 different laptops.
I will try to do a sector by sector clone with CloneZilla or similar. Hopefully thats still possible.
Last edit: Veracrypt Bootloader 2022-02-15
Just tried CloneZilla which does not see any of the drives when plugged via the usb case => to usb.
So any input on how to safely Initializing the disk with GPT/MBR without data loss is welcome =D
From what you wrote, I assume that you initially encrypted the system partition on the NVME, not the entire device. Is this correct?
In case, the above is correct, the current behavior of the device suggests that at least the partitioning information on the NVME got damaged or deleted. There are many reasons for this, like incomplete device dismount, device failure, power loss while in use, accidental deletion… you name it.
The only way I could think of getting data back would be booting an Ubuntu based live Linux distribution (as these ship a convenient disk partitioning tool). Then, reformatting the device to MBR or GPT (depends on what was used before) without overwriting data (quick mode). Afterwards, recreating the partitions like they were before (size, position) as raw filesystem without overwriting data (quick mode, again).
For this to work out mostly depends on you knowing about the original partitioning scheme and the data still being intact.
Greets
Thanks for your reply. VERY appreciated.
Damn! Thats bad news. They are indeed encrypted system partitions.. Which just to be sure is the first option when going through encryption steps, and not second "Encrypt whole drive" since its always greyed out.'
They are all GPT.
Will the VeraCrypt rescue disk be handy here?
Will inserting the hard drive into a laptop make it bootable and show the Veracrypt password prompt?
That's very unlikely, as there is no partitioning information on the device.
Just tried GParted from a USB stick which does not show the harddrive. Neither do the installed Windows version of "Macrium Reflect".
So far only Windows own disk management.
Tried Acronis bootable version: Did not show the disk
Ubuntu Live disk utility showed the disk but with only one option @ right click which I am afraid to touch.
After unticking the "use default" box, these fields can be modified.
Would enabling that help? I obviously cancelled it right away =)
Whaaat to dooooooo =(((
Have a look at the following thread, as it discusses a similar issue. The difference in your case seems to be that you do not have reformatted the device yet, giving better chances of getting data back.
But the steps in recreating the partitioning should be similar. I've uploaded some screens there with the steps how to achieve the partitioning.
https://sourceforge.net/p/veracrypt/discussion/technical/thread/2ebaf9581c/
Update: I just inserted each NVME SSD disk into a laptop without changing/doing aaanything. Worked!
So, the USB case was the issue?