| View previous topic :: View next topic |
| Author |
Message |
mayhew
Tux's lil' helper
Joined: 25 Feb 2013
Posts: 77
|
 Posted: Wed Jul 15, 2020 1:09 pm Post subject: [SOLVED]Luks external drive cant open on new install |
 |
|
TL;DR Mount your boot 
I have a usb-hdd with luks it worked on previous installs of 17.0 gentoo and other Linux-os's.
I recieve...
| Code: | | Error unlocking /dev/sdb1: Failed to activate device: Invalid argument |
and dmesg says
| Code: | 577.088974] sd 1:0:0:0: [sdb] Mode Sense: 2b 00 10 08
[ 577.090886] scsi 1:0:0:1: Enclosure WD SES Device 2010 PQ: 0 ANSI: 4
[ 577.092554] sd 1:0:0:0: [sdb] No Caching mode page found
[ 577.092556] sd 1:0:0:0: [sdb] Assuming drive cache: write back
[ 577.096611] scsi 1:0:0:1: Attached scsi generic sg2 type 13
[ 577.142019] sdb: sdb1 sdb2 sdb3
[ 577.147392] sd 1:0:0:0: [sdb] Attached SCSI disk
[ 588.046413] traps: ck-remove-direc[3286] trap int3 ip:7eff7c8ee175 sp:7ffe43e63970 error:0 in libglib-2.0.so.0.6200.6[7eff7c8b4000+81000]
[ 588.329515] FAT-fs (sdb3): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 588.530701] FAT-fs (sdb2): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 598.429514] device-mapper: table: 253:0: crypt: unknown target type
[ 598.429515] device-mapper: ioctl: error adding target to table
[ 641.054926] r8169 0000:02:00.0 enp2s0: Link is Up - 100Mbps/Full - flow control rx/tx
[ 641.054940] IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready
[ 723.067881] pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0
[ 723.067898] pcieport 0000:00:1c.0: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
[ 723.067907] pcieport 0000:00:1c.0: AER: device [8086:9d14] error status/mask=00001000/00002000
[ 723.067914] pcieport 0000:00:1c.0: AER: [12] Timeout
[ 1384.688605] device-mapper: table: 253:0: crypt: unknown target type
[ 1384.688606] device-mapper: ioctl: error adding target to table
|
Im not sure what to do, i can recover my files but its inconvenient to do.
thank you for the help.
Luks Dump
| Code: |
# cryptsetup luksDump /dev/sdb1
LUKS header information for /dev/sdb1
Version: 1
Cipher name: aes
Cipher mode: xts-plain64
Hash spec: sha256
Payload offset: 4096
MK bits: 256
MK digest: 5a e4 a0 25 a1 14 d0 af bc 60 b2 58 3b 30 87 90 08 a8 01 d4
MK salt: 6c b9 17 ad 68 81 20 74 5a 48 a5 aa 3d 9c 8d 85
26 7c 1e 1a ef 60 35 57 13 d5 88 46 73 3f 91 21
MK iterations: 118509
UUID: 15eebe48-ddd2-45b5-8c20-e623e7e7c3eb
Key Slot 0: ENABLED
Iterations: 1896158
Salt: 9b 19 25 5a 04 31 32 3e 43 e5 b6 15 7b 2c da 87
f5 97 07 52 fb 81 a0 08 65 79 63 b2 37 6e db 6e
Key material offset: 8
AF stripes: 4000
Key Slot 1: DISABLED
Key Slot 2: DISABLED
Key Slot 3: DISABLED
Key Slot 4: DISABLED
Key Slot 5: DISABLED
Key Slot 6: DISABLED
Key Slot 7: DISABLED
|
_________________
Last edited by mayhew on Fri Jul 17, 2020 8:51 pm; edited 1 time in total |
|
| Back to top |
|
 |
fturco
Veteran
Joined: 08 Dec 2010
Posts: 1181
|
| Posted: Wed Jul 15, 2020 5:12 pm Post subject: |
|
|
| Is the CONFIG_DM_CRYPT kernel option enabled? |
|
| Back to top |
|
|
mayhew
Tux's lil' helper
Joined: 25 Feb 2013
Posts: 77
|
| Posted: Thu Jul 16, 2020 1:12 pm Post subject: |
|
|
| fturco wrote: | | Is the CONFIG_DM_CRYPT kernel option enabled? |
it is.
| Code: | │ <*> Device mapper support │
│ [ ] Device mapper debugging support │
│ [ ] Block manager locking │
│ <*> Unstriped target │
│ <*> Crypt target support │
│ <*> Snapshot target │
│ <*> Thin provisioning target │
│ < > Cache target (EXPERIMENTAL) │
│ <*> Writecache target │
│ < > Era target (EXPERIMENTAL) │
│ < > Clone target (EXPERIMENTAL) │
│ <*> Mirror target │
|
_________________
|
|
| Back to top |
|
|
Banana
Moderator
Joined: 21 May 2004
Posts: 1857
Location: Germany
|
|
| Back to top |
|
|
mayhew
Tux's lil' helper
Joined: 25 Feb 2013
Posts: 77
|
| Posted: Thu Jul 16, 2020 10:06 pm Post subject: |
|
|
| Banana wrote: | | are you using a kernel in which this option is enabled? (just want to rule out some basic problems) |
Please elaborate, thank you. I am not certain.
_________________
|
|
| Back to top |
|
|
AlexJGreen
Tux's lil' helper
Joined: 19 Sep 2018
Posts: 149
|
| Posted: Thu Jul 16, 2020 10:56 pm Post subject: |
|
|
_
Last edited by AlexJGreen on Mon Dec 28, 2020 3:05 am; edited 1 time in total |
|
| Back to top |
|
|
Banana
Moderator
Joined: 21 May 2004
Posts: 1857
Location: Germany
|
|
| Back to top |
|
|
mayhew
Tux's lil' helper
Joined: 25 Feb 2013
Posts: 77
|
| Posted: Fri Jul 17, 2020 8:48 pm Post subject: |
|
|
| coderanger wrote: | mayhew,
The most common problem is when the user forgot to mount /boot before installing a new kernel. The user believes that he is using a new kernel, but the point is that the system boots from the old kernel.
The easiest way to check if any option is enabled in the kernel is to look at /proc/config.gz (managed by CONFIG_IKCONFIG_PROC) - this is the actual config of the currently running kernel | Code: | | zgrep CONFIG_DM_CRYPT /proc/config.gz |
|
 This was it! I've been using boot on root partitioning for so long i forgot to mount before make installing. (first successfull EFI boot)
Thank you
_________________
|
|
| Back to top |
|
|
|
Networking & Security
