Hi there I've been exclusively using dm-crypt for around 9 months on my Dell laptop (running FC7) - with a /boot partition and "/" fully encrypted. In the beginning I also encrypted swap with a static password. I use suspend-to-disk a lot and it all worked - in principle. However every 3-4 "un-suspends" I'd end up with ext3 errors occurring and file loss. In the end it was diagnosed back to the encrypted swap (I have a ticket open with Fedora about all this - https://bugzilla.redhat.com/show_bug.cgi?id=281691). Once I went back to unencrypted swap, the problem appeared to disappear. However, I recently replaced my laptop and so went to FC8 in the same configuration. It worked well for around 3 weeks but today it totally killed itself. Once I enter the decrypt password, I just start getting "ata1.0" errors and eventually a EXT3 error and that's it - game over. I am 100% sure this isn't hardware-related. During this 8+ month period I have successfully harrassed Dell into replacing the disk 3 times, the motherboard once - and of course I've just got an entire new system. And yet these problems continue. And yet when I read this list, it appears to be working for others (although most are using to protect "sub-volumes" like /home). So does anyone else have any ideas what I am doing wrong? I mean - it works most of the time - but when an encrypted drive goes bad - it REALLY goes bad :-) It is obviously related to suspending to disk - but that feature is more important to me than encryption, so if no-one has any ideas, I'm just going to go back to non-encrypted - as it's safer. Thanks for any ideas Jason --------------------------------------------------------------------- dm-crypt mailing list - http://www.saout.de/misc/dm-crypt/ To unsubscribe, e-mail: dm-crypt-unsubscribe@xxxxxxxx For additional commands, e-mail: dm-crypt-help@xxxxxxxx
