Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compatibility Issue for Samsung 850 Pro with LUKS partitions #51

Open
gill984 opened this issue May 24, 2016 · 2 comments
Open

Compatibility Issue for Samsung 850 Pro with LUKS partitions #51

gill984 opened this issue May 24, 2016 · 2 comments

Comments

@gill984
Copy link

gill984 commented May 24, 2016

I've been attempting to open LUKS partitions which I created using cryptsetup in Ubuntu on a Samsung SSD 850 PRO but I've had some issues. I'm on a Windows 7 64 bit laptop. I am using an eSATA cable to connect directly to the laptop, I have also tried using an eSATA to USB 3.0 adapter cable.

I create the LUKS partition in Ubuntu using cryptsetup and then make a fat32 filesystem inside of the LUKS partition. When I attempt to open the partition in Librecrypt, Librecrypt recognizes the partition as being LUKS. When I enter the password and hit OK I get the message "Unable to open container. Please check your keyphrase and settings, and try again."

When I use the exact same process on a USB flashdrive, the process works as expected and I can open the LUKS partition which I create in the exact same way.

Other things I have tried include using the 6.3 alpha executable and using FreeOTFE both of which behave similarly and did not fix my issue.

I was wondering if anyone has had this issue and might know how to fix it, thank you.

@gill984
Copy link
Author

gill984 commented Jun 1, 2016

I figured out that the issue was due to having too many partitions. If Windows is using up to drive Z, there are no spaces left to mount a LUKS partition. Does anyone know the best workaround for this?

@t-d-k
Copy link
Owner

t-d-k commented Jul 6, 2016

Thanks for reporting this. LC should report the error better.
There are some registry hacks to hide drive letters.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants