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

NAME
extendfs - Extends UFS file systems SYNOPSIS
/sbin/extendfs [- s] [disk_blocks] device_name DESCRIPTION
Use the extendfs command to increase the storage space in a UFS file system. The file system must not be mounted when you perform this operation. To extend a mounted (in use) UFS file system, use the mount command with the -o extend option. The procedure for increasing the storage space of a UFS file system is as follows: Look at the contents the /etc/fstab file to identify the disk partition that maps to the file system. Ensure that there is available storage space on the target disk as follows: If LSM is in use on your system, use LSM commands to increase the size of the LSM volume as described in the Logical Storage Manager guide. If LSM is not in use on your system, use the disklabel command or the diskconfig graphical user interface to check the current size and use of partitions on the disk. If there is adequate space on an adjacent partition, use the disklabel command to write the current label to a file as fol- lows: # disklabel -r dsk4 > d4label Edit the disklabel file to change the size of the partition on which your UFS file system resides. Increase the number of disk blocks on the partition and decrease the disk block size of the adjacent partition by an equivalent number. Use the disklabel command with the -R option to write the revised label to the raw disk as follows: # disklabel -R /dev/rdisk/dsk4 d4label When the disk label is revised, extend the file system using the extendfs command. You can either use the full extent of the newly sized partition or extend the file system in stages. The following example commands show both methods. To extend the file system to use all the available space, you specify the disk partition on which the file system resides, as follows: # extendfs /dev/disk/dsk4g To extend the file system to use only part of the available space, you specify a number of disk blocks, as follows: # extendfs -s 300000 /dev/disk/dsk4g The remainder of the extended partion is reserved for future use. You can extend a file system as many times as necessary, up to the physical limit of the storage device. When no more space is available on the storage device, you must back up the file system using the dump command and restore the file system to a storage device that has more available space. Once you have extended a file system, the operation cannot be reversed except by a back up and restore operation. Use the dump command to back up the file system. You can then reset the partition sizes manually and restore the file system to the storage device. ERRORS
The disklabel command produces output similar to that of the newfs command. If a list of disk blocks is not displayed on the terminal, the command has failed. Verify the partition settings and the mount status of the target file system. The disklabel command does not permit you to overwrite a partition if it is in use. Refer to the disklabel(8) reference page for more information on label errors. FILES
Specifies the command path. RELATED INFORMATION
diskconfig(8), disklabel(8), mount(8), and fstab(4). extendfs(8)