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
FDISK(8)						      System Manager's Manual							  FDISK(8)

NAME
fdisk - partition a hard disk [IBM] SYNOPSIS
fdisk [-hm] [-sn] [file] OPTIONS
-h Number of disk heads is m -s Number of sectors per track is n EXAMPLES
fdisk /dev/hd0 # Examine disk partitions fdisk -h9 /dev/hd0 # Examine disk with 9 heads DESCRIPTION
When fdisk starts up, it reads in the partition table and displays it. It then presents a menu to allow the user to modify partitions, store the partition table on a file, or load it from a file. Partitions can be marked as MINIX, DOS or other, as well as active or not. Using fdisk is self-explanatory. However, be aware that repartitioning a disk will cause information on it to be lost. Rebooting the sys- tem immediately is mandatory after changing partition sizes and parameters. MINIX, XENIX, PC-IX, and MS-DOS all have different partition numbering schemes. Thus when using multiple systems on the same disk, be careful. Note that MINIX, unlike MS-DOS , cannot access the last sector in a partition with an odd number of sectors. The reason that odd partition sizes do not cause a problem with MS-DOS is that MS-DOS allocates disk space in units of 512-byte sectors, whereas MINIX uses 1K blocks. Fdisk has a variety of other features that can be seen by typing h. Fdisk normally knows the geometry of the device by asking the driver. You can use the -h and -s options to override the numbers found. SEE ALSO
part(8). FDISK(8)