3016 Encryption Error

Trying to encrypt my partitions for swap, root and /home directories. However, when I go to partitioner and select the drives as sdb1, sbd2 or sbd3 and click on the encryption. it errors with a -3016 error. Can’t find anything in the release notes or the security documentation that would lead me to why this screen is popping. Any ideas?

Yast’s partitioner is weak, buggy, badly written and has multiple logical (usage) programming errors. They didn’t even bother to explain what error number -3016 means. Often certain operations can be accomplished with other partitioners only. And there is no improvement from version to version.

You must help Yast to succeed if it fails.

Here is how I deal with the bugs. I found the methods through trial and error.

  1. Unmount of course all partitions before any re-partitioning or encrypting. Wait for two minutes. Try again. If the error pops up again, proceed to next method.

  2. Comment out the lines with relevant partitons in /etc/fstab, and reboot. Try again. If the error pops up again, proceed to next method.

  3. Delete the partitons, reboot. Try again to create partitions.

  4. Boot the computer from opensuse Live CD. Call Yast and repartition.

  5. Use gparted Live CD.

You would figure OpenSuse would put an exceptional Partitioner in their package. something that is reliable. for the most part, I enjoy OpenSuse 11.3 It is more polished. So far very little problem. It loaded and configured just the way I expected it. Nice so far. Thanks for the advice, Maybe somebody from the team will get a partitioner that is less buggy.

On 2010-08-10 02:06, cherock1254 wrote:
>
> You would figure OpenSuse would put an exceptional Partitioner in their
> package. something that is reliable. for the most part, I enjoy OpenSuse
> 11.3 It is more polished. So far very little problem. It loaded and
> configured just the way I expected it. Nice so far. Thanks for the
> advice, Maybe somebody from the team will get a partitioner that is less
> buggy.

For that you have to report the bug - not here, that is useless - to Bugzilla.


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” GM (Elessar))