On 29.08.21 07:09, detr...@tuta.io wrote:
(...)
Before:
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE%
MOUNTPOINTS
sda
├─sda1
│ vfat FAT32 A2BD-D233 70,8M 26%
/boot/efi
├─sda2
│
├─sda3
│ ntfs 2AD4C9CED4C99C87
├─sda4
│ ntfs 584044B640449C9E
└─sda5
ext4 1.0 15dd568a-ec98-4470-8812-a82b15d44995 212,2G 60% /
After:
NAME FSTYPE FSVER LABEL UUID FSAVAIL
FSUSE% MOUNTPOINTS
sda
├─sda1 vfat FAT32 A2BD-D233 70,8M
26% /boot/efi
├─sda2
├─sda3 ntfs 2AD4C9CED4C99C87
├─sda4 ntfs 584044B640449C9E
└─sda5 ext4 1.0 15dd568a-ec98-4470-8812-a82b15d44995 212,2G
60% /
sdb
├─sdb1 ext2 1.0 a066ddce-69d9-47df-9030-ccbb8305fd1b
├─sdb2
└─sdb5 crypto_LUKS 2 992108a2-0a0c-4dfc-9482-ce86cbfdfa98
cryptsetup --version
cryptsetup 2.4.0
cryptsetup -v isLuks --type luks1 /dev/sdb
Device /dev/sdb is not a valid LUKS device.
Command failed with code -1 (wrong or missing parameters).
cryptsetup -v isLuks --type luks2 /dev/sdb
Command failed with code -1 (wrong or missing parameters).
(...)
The device name in your command should be for the specific situation as
indicated by you lsblk command the string: /dev/sdb5
Thus, you are supposed to run this command (as root, or using sudo):
cryptsetup -v isLuks --type luks1 /dev/sdb5
cryptsetup -v isLuks --type luks2 /dev/sdb5
If the partition could be recognized to be of type LUKS version 1, or
LUKS version 2, the respective command instead of any error message
would answer:
"Command successful."
---
Good Luck!
Marco.
