| 2 | | |
| 3 | | Replying to [comment:1 socratis]: |
| 4 | | > Replying to [ticket:18448 wtfcowisown]: |
| 5 | | > > ''VM files stored on separate internal hdd, !VirtualBox on my ssd. Had to wipe my ssd, so I reinstalled !VirtualBox.'' |
| 6 | | > |
| 7 | | > When you talk about "VM files", what exactly do you mean? ''All'' the VM files, or just the VDIs? Because here's the error that you're getting: |
| 8 | | > {{{ |
| 9 | | > 00:00:05.227473 VD#0: DEK is missing |
| 10 | | > 00:00:05.227530 VM: Raising runtime error 'DrvVD_DEKMISSING' (fFlags=0x6) |
| 11 | | > }}} |
| 12 | | > And here's I think what happened... |
| 13 | | > |
| 14 | | > * You encrypted your VMs, but the VDIs were in the HDD, and the definition, the "recipe", the "`.vbox`" files were on their default folder in the SSD. |
| 15 | | > * When you wiped out the SSD, you wiped out the "`.vbox`" files, leaving the VDIs without their encryption key, which is stored in the "`.vbox`" file, not in the VDI itself. |
| 16 | | > * You then tried to recreate the setup, by creating a new VM and attaching the ''existing'' VDI to the ''new'' VM. |
| 17 | | > |
| 18 | | > That '''__is__''' going to fail. And unfortunately, unless you restore your original "`.vbox`" files from a backup, you're out of luck. |
| 19 | | > |
| 20 | | > BTW, it's usually better and faster, if issues get first addressed in the [https://forums.virtualbox.org/ VirtualBox forums], a lot more eyes there. More than 95% of the issues are resolved in the forums, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of. For example, yours is most probably '''not a bug''' and someone from the developers has to deal with it and close it as "'''Invalid'''". |
| 21 | | > |
| 22 | | > Plus a discussion and analysis on the bug tracker is going to help you, me, and potentially a future drive-by user or two. Not so in the forums, many more tend to benefit... |
