On 20 Jul 2018 09:17 -0600, from bradhaack@xxxxxxxxxxx (brad): > No errors in syslog or kern.log Unless you're _certain_ that you're looking in the right place, it's often a good idea to (also) check the output of running `dmesg`. Something like `dmesg | tail -n20` is usually a good start. > Using the proper syntax (this time), I can open it: > cryptsetup --debug luksOpen /dev/sdb dm-2 > [command successful, no warnings or errors in output] > > If I try to mount it: > Error mounting /dev/dm-2 at /media/brad/Maxtor1: can't read > superblock on /dev/mapper/dm-2. What is the output of `file -s /dev/mapper/dm-2` after the successful `luksOpen`? What does `dmesg` have to say about the mount attempt? Does running `cryptsetup luksDump` on the raw device print anything sensible? Please confirm that in your attempts to get this working, you haven't ever run a luksFormat, even by accident. -- Michael Kjörling • https://michael.kjorling.se • michael@xxxxxxxxxxx “The most dangerous thought that you can have as a creative person is to think you know what you’re doing.” (Bret Victor) _______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx https://www.saout.de/mailman/listinfo/dm-crypt
