Waiting for encrypted source device

[Jax667]

Hello,

I need help after updating to Linux Mint 21: My desktop doesn't boot anymore, instead I get the following message:

Code: Select all

cryptsetup: Waiting for encrypted source device /dev/mapper/isw_ceeiiegeid_Raiden3...
volume group "vgmint" not found
cannot process volume group vgmint
Gave up waiting for root device. Common problems:
  - Boot args (cat /proc/cmdline)
    - Check rootdelay= (did the system wait long enough?)
    - Check root= (did the system wait for the right device?)
  - Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/mapper/vgmint-root does not exist. Dropping to a shell! 

BusyBox v.1.30.1 (Ubuntu 1:1.30.1-7ubuntu3) built-in shell (ash)   
Enter 'help' for list of built-in commands.  

(initramfs)

To clarify: I combined two SSDs via Raid Mode to one storage and installed Linux Mint with LUKS encryption. I got another SSD (ADATA) on which I installed Windows. The USB drive is the bootable Linux Mint 21 obviously.

I created a bootable usb disk and booted into Linux Mint 21 from there and opened a terminal:

Code: Select all

mint@mint:~$ sudo sfdisk -l
Disk /dev/loop0: 2.13 GiB, 2285047808 bytes, 4462984 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
GPT PMBR size mismatch (976783871 != 488397167) will be corrected by write.


Disk /dev/sda: 232.89 GiB, 250059350016 bytes, 488397168 sectors
Disk model: Crucial_CT250MX2
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x00000000

Device     Boot Start       End   Sectors   Size Id Type
/dev/sda1           1 488397167 488397167 232.9G ee GPT

Partition 1 does not start on physical sector boundary.


Disk /dev/sdb: 232.89 GiB, 250059350016 bytes, 488397168 sectors
Disk model: Crucial_CT250MX2
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/sdc: 238.47 GiB, 256060514304 bytes, 500118192 sectors
Disk model: ADATA SU800     
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: CDE4D834-50E9-4F13-8A13-517077AB5D49

Device     Start       End   Sectors   Size Type
/dev/sdc1   2048 500117503 500115456 238.5G Microsoft basic data


Disk /dev/mapper/isw_ceeiiegeid_Raiden: 465.77 GiB, 500113342464 bytes, 976783872 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 131072 bytes / 262144 bytes
Disklabel type: gpt
Disk identifier: 5E08A2B8-894B-421F-BE26-CACBB74C380A

Device                                    Start       End   Sectors   Size Type
/dev/mapper/isw_ceeiiegeid_Raiden-part1    2048   1050623   1048576   512M EFI System
/dev/mapper/isw_ceeiiegeid_Raiden-part2 1050624   2549759   1499136   732M Linux filesystem
/dev/mapper/isw_ceeiiegeid_Raiden-part3 2549760 976783359 974233600 464.6G Linux filesystem


Disk /dev/sdd: 28.64 GiB, 30752636928 bytes, 60063744 sectors
Disk model: Ultra USB 3.0   
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xe7938363

Device     Boot Start      End  Sectors  Size Id Type
/dev/sdd1  *     2048 60063743 60061696 28.6G  c W95 FAT32 (LBA)


mint@mint:~$ sudo /sbin/cryptsetup luksOpen /dev/mapper/isw_ceeiiegeid_Raiden isw_ceeiiegeid_Raiden_crypt
Device /dev/mapper/isw_ceeiiegeid_Raiden is not a valid LUKS device.

mint@mint:~$ sudo cryptsetup luksOpen /dev/mapper/isw_ceeiiegeid_Raiden-part3 isw_ceeiiegeid_Raiden-part3_crypt
Device /dev/mapper/isw_ceeiiegeid_Raiden-part3 does not exist or access denied.

mint@mint:~$ ls -l /dev/mapper
total 0
crw------- 1 root root  10, 236 Aug 14 22:38 control
brw-rw---- 1 root disk 253,   0 Aug 14 22:38 isw_ceeiiegeid_Raiden

I suspect "/dev/mapper/isw_ceeiiegeid_Raiden isw_ceeiiegeid_Raiden" is my encrypted device which consists of both sda and sdb SSDs? Is it possible to repair this without deleting my files? I hope you guys can help and thank you in advance.

P.S. I need the Raid Mode to stay on for both SSDs to be able to be recognized as one storage, so switching to ACHI mode in bios as some solutions suggested is no option.

[deepakdeshp]

Does this help?
viewtopic.php?f=42&t=315207
Encryption complicates ,they say veracrypt is better.

[Jax667]

Thank you for your answer. Unfortunately, the encrypted storage is not detected at all and I also tried to check if /dev/dm-0 is the encrypted device without success.

[t42]

Does this help?
viewtopic.php?f=42&t=315207

?
The OP has issue with FDE. Under your link was a discussion about recovery of home directory encryption encrypted with ecryptfs.

[Jax667]

Hello,

I am back from vacation and thought I'd give it a try.

Code: Select all

sudo cryptsetup luksOpen /dev/mapper/isw_ceeiiegeid_Raiden isw_ceeiiegeid_Raiden_crypt

gives the answer

Code: Select all

Device /dev/mapper/isw_ceeiiegeid_Raiden is not a valid LUKS device

I tried that with different names, e.g. -part1...part3 etc.

[t42]

revoked

[Jax667]

Hello, the Raid Mode is activated through the bios and is not connected to the Live USB.

Also, I'm not sure what you want me to do. Would you like me to try certain commands via Live USB terminal? Which ones exactly?

Also look at fstab and crypttab files.

Since the device cannot be opened, I cannot access any files.

[t42]

Hello, the Raid Mode is activated through the bios and is not connected to the Live USB.
...
Since the device cannot be opened, I cannot access any files.

My comment was mainly based on your phrasing "I suspect "/dev/mapper/isw_ceeiiegeid_Raiden isw_ceeiiegeid_Raiden" is my encrypted device which consists of both sda and sdb SSDs?" and other little inconsistencies. Sorry for misunderstanding.

[Jax667]

Did I explain something wrong? What exactly are the inconsistencies? Depending on your answer, I'll try to understand the problem better. Thx