https://bugzilla.novell.com/show_bug.cgi?id=332095#c3 --- Comment #3 from Dirk Stoecker <opensuse@dstoecker.de> 2007-10-09 04:04:36 MST --- You see in above fstab, that the test device I used for the examples uses twofish2, so the call is correct. The second argument can be everything, the result is the same. As there is no update-guide available commandline errors are possible, but as long as the systems tells me the device does not exist there is no real use in digging deeper into possible commandline problems (BTW I really tried lot's of different commandlines). Anyway the same problem appears for /dev/private2, which is an old twofish and thus uses twofish-cbc-null. The mount crash produces no backtrace, as I have no debug-stuff installed. The problem is so central, that I don't believe it is specific to my machine. I would start installing debug stuff and doing debugging only, when the easy reproducability tests on your side fail (especially as my 10.3 test system I talk about has no network access for easy installation). Regarding corruption: a) If encryption is correct, there is either a no-or-nothing. Wrong encryption cannot produce nearly correct results, but totally wrong results, else the encryption is not strong. The filesystem will no discover the partition at all then. b) Loading too many modules should not influence the results at all (BTW: I also tried with loading only subsets of the specified kernel modules, Result is the same). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.