Before I start I'll point out I know nothing about FDE until reading up about it over the last few days, and trying to piece together information from Lenovo. The only experience I have of encryption is using truecrypt containers.I am extremely interested too... I was looking at the intel320 (sata2) series as I know they AES FDE support works well, but I have decided to wait as the new intel 520 (sata3) series is going to drop any week now... and will support AES FDE.
I think you should try with your Samsung 830 and report back
First, I ran the Lenovo SSD Firmware Update Utility. It recognized the drive, but said that there was no update required/available.
I removed the SSD and put it in a caddy. I then ran Gparted Live on an old non-Lenovo desktop, and plugged in the drive. As expected, it saw all the partitions.
I then put the SSD back in the x121e and set HDD user + master passwords. I restarted the x121e and after entering the password Grub booted up as normal. I put the SSD into the caddy again and tried it on the old desktop with Gparted as before. This time the scan for devices would not stop after finding only the desktop's drive.
So I took it to another non-Lenovo computer running Ubuntu and plugged it in - nothing seen in Disk Utility at all.
I then put the SSD back in the x121e, removed the passwords, put it back in the caddy and repeated. Both Gparted Live and Ubuntu's Disk Utility could see the drive as normal.
To my simple mind, this would appear to mean FDE works. But what I'm confused about is:
1. How it managed to encrypt the drive so quickly (setting the password took about a second to process);
2. How it did it without wiping the original data.
I'm sure this confusion is because I don't understand how FDE works properly, or indeed the disk has not been encrypted.
Opinions appreciated