After trying to mount, dmesg:
[ 8137.643373] sd 4:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[ 8137.643377] sd 4:0:0:0: [sdb] tag#0 Sense Key : Illegal Request
[current]
[ 8137.643380] sd 4:0:0:0: [sdb] tag#0 Add. Sense: Invalid command
operation code
[ 8137.643383] sd 4:0:0:0: [sdb] tag#0 CDB: Synchronize Cache(10) 35 00
00 00 00 00 00 00 00 00
[ 8137.643387] print_req_error: critical target error, dev sdb, sector 0
[ 8137.643401] JBD2: recovery failed
[ 8137.643405] EXT4-fs (dm-2): error loading journal
dt1:file -s /dev/mapper/dm-2
/dev/mapper/dm-2: symbolic link to ../dm-2
dt1:sudo cryptsetup luksDump /dev/sdb
[sudo] password for brad:
LUKS header information for /dev/sdb
Version: 1
Cipher name: aes
Cipher mode: xts-plain64
Hash spec: sha1
Payload offset: 4096
MK bits: 256
MK digest: 11 cc c9 84 47 cb c2 96 fe 1b 83 64 6a 35 3a 57 c8 2f
2d 5b
MK salt: 8d fd d6 2b 52 a3 5a f7 49 7f f6 67 b4 a1 ec fa
de 00 85 66 7b af fa 81 78 6a 85 e3 57 62 9e f7
MK iterations: 50000
UUID: 3bddbc2d-6432-46df-9851-c86e15478ded
Key Slot 0: ENABLED
Iterations: 213333
Salt: 74 93 8f 45 b3 9a 87 04 69 10 f6 08 74 7c
08 7e
dc 9c 88 3f 5c 65 53 0b cf 50 f4 0a 69 c0
02 c8
Key material offset: 8
AF stripes: 4000
Key Slot 1: ENABLED
Iterations: 216215
Salt: 30 36 67 43 b0 12 aa 67 c8 b6 c5 6a 68 87
42 3d
94 e5 c6 58 10 dc 9c ab aa 82 ea a6 27 89
44 7c
Key material offset: 264
AF stripes: 4000
Key Slot 2: DISABLED
Key Slot 3: DISABLED
Key Slot 4: DISABLED
Key Slot 5: DISABLED
Key Slot 6: DISABLED
Key Slot 7: DISABLED
I haven't run luksformat recently, I don't recall what I ran years
ago, but it was working up until the OS update.
On 07/20/2018 10:21 AM, Michael Kjörling wrote:
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.
_______________________________________________
dm-crypt mailing list
dm-crypt@xxxxxxxx
https://www.saout.de/mailman/listinfo/dm-crypt
