Cryptsetup compains not a valid device

 
Thread Tools Search this Thread
Operating Systems Linux Red Hat Cryptsetup compains not a valid device
# 1  
Old 05-17-2017
Cryptsetup compains not a valid device

Hi,

We have a disk say /dev/sdx which is encrypted as whole disk (no partition)

Now after extending the disk and resizing the file system the cryptsetup comamnd compains that /dev/sdx is not a vaild LUKS device.

[xxxxxxxxxxxxxx]# cryptsetup luksOpen /dev/sdx sdxEncrypted
Device /dev/sdx is not a valid LUKS device.

Do I need to change anything with fdisk?

Quick Help is much appreciated.
Login or Register to Ask a Question

Previous Thread | Next Thread

5 More Discussions You Might Find Interesting

1. Debian

Problems with cryptsetup keyfile encrypted root partition under Debian 9, i386

Hello, i'm trying to set up a machine with an encrypted filesystem. It's a Debian 9/i386. The partition table on /dev/sda 1. 1 MiB BIOS BOOT (04) N/A N/A 2. 256 MiB Linux (83) ext4 /boot 3. 2304 MiB Linux (83) ext4 / 4. 1 MiB MINIX (81) N/A N/A 5. 510 MiB Linux... (7 Replies)
Discussion started by: tyuxar
7 Replies

2. Linux

Systemd cryptsetup fails to map drive during reboot

I have created an encrypted disk using the following command: # cryptsetup create testcui /dev/sdb --key-file= /etc/keys --verify-passphrase plain This created the correctly mapped device /dev/mapper/testcui I have create the crypttab file with the following: # # test disk #... (0 Replies)
Discussion started by: jlowry
0 Replies

3. HP-UX

Failed to open tape device /dev/rmt/0mn:Device busy (errno = 16)

Hi, Unable to make tape backup, please help. /opt/ignite/bin/make_tape_recovery -a /dev/rmt/?mn -I -v -m tar -x inc_entire=vg00 * Creating local directories for configuration files and archive. ======= 04/25/16 16:28:08 IST Started /opt/ignite/bin/make_tape_recovery. (Mon... (4 Replies)
Discussion started by: anuragr
4 Replies

4. Red Hat

Unable To Activate Ethernet Network Device in RHEL 5.5 - e100 device eth0 does not seem to be presen

Hi All, Could anyone please help to resolve the below problem. I installed RHEL5.5 in my desktop.But when i try to activate the ethernet connection then it gives me the error. I spent 2 days for the above and go through with several suggestion found by googling. But no luck. ... (0 Replies)
Discussion started by: Tanmoy
0 Replies

5. AIX

"rmt0" is not a valid backing device - VIO

hello to all, i am trying to assing a tape drive to a virtual partition through VIO but i get the message "rmt0" is not a valid backing device. the oslevel of my VIO is AIX 6.1.3.0. when i run the command lsdev |grep rmt i get the following result: rmt0 Available 08-08-00-0,0 ... (6 Replies)
Discussion started by: omonoiatis9
6 Replies
Login or Register to Ask a Question
HD(4)							     Linux Programmer's Manual							     HD(4)

NAME
hd - MFM/IDE hard disk devices DESCRIPTION
The hd* devices are block devices to access MFM/IDE hard disk drives in raw mode. The master drive on the primary IDE controller (major device number 3) is hda; the slave drive is hdb. The master drive of the second controller (major device number 22) is hdc and the slave hdd. General IDE block device names have the form hdX, or hdXP, where X is a letter denoting the physical drive, and P is a number denoting the partition on that physical drive. The first form, hdX, is used to address the whole drive. Partition numbers are assigned in the order the partitions are discovered, and only non-empty, non-extended partitions get a number. However, partition numbers 1-4 are given to the four partitions described in the MBR (the `primary' partitions), regardless of whether they are unused or extended. Thus, the first logi- cal partition will be hdX5. Both DOS-type partitioning and BSD-disklabel partitioning are supported. You can have at most 63 partitions on an IDE disk. For example, /dev/hda refers to all of the first IDE drive in the system; and /dev/hdb3 refers to the third DOS `primary' partition on the second one. They are typically created by: mknod -m 660 /dev/hda b 3 0 mknod -m 660 /dev/hda1 b 3 1 mknod -m 660 /dev/hda2 b 3 2 ... mknod -m 660 /dev/hda8 b 3 8 mknod -m 660 /dev/hdb b 3 64 mknod -m 660 /dev/hdb1 b 3 65 mknod -m 660 /dev/hdb2 b 3 66 ... mknod -m 660 /dev/hdb8 b 3 72 chown root:disk /dev/hd* FILES
/dev/hd* SEE ALSO
mknod(1), chown(1), mount(8), sd(4) Linux 1992-12-17 HD(4)