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
cmdk(7D)							      Devices								  cmdk(7D)

NAME
cmdk - common disk driver SYNOPSIS
cmdk@target, lun : [ partition | slice ] DESCRIPTION
The cmdk device driver is a common interface to various disk devices. The driver supports magnetic fixed disks and magnetic removable disks. The cmdk device driver supports three different disk labels: fdisk partition table, Solaris x86 VTOC and EFI/GPT. The block-files access the disk using the system's normal buffering mechanism and are read and written without regard to physical disk records. There is also a "raw" interface that provides for direct transmission between the disk and the user's read or write buffer. A sin- gle read or write call usually results in one I/O operation; raw I/O is therefore considerably more efficient when many bytes are transmit- ted. The names of the block files are found in /dev/dsk. Raw file names are found in /dev/rdsk. I/O requests to the magnetic disk must have an offset and transfer length that is a multiple of 512 bytes or the driver returns an EINVAL error. Slice 0 is normally used for the root file system on a disk, slice 1 as a paging area (for example, swap), and slice 2 for backing up the entire fdisk partition for Solaris software. Other slices may be used for usr file systems or system reserved area. The fdisk partition 0 is to access the entire disk and is generally used by the fdisk(1M) program. FILES
/dev/dsk/cndn[s|p]n block device (IDE) /dev/rdsk/cndn[s|p]n raw device (IDE) where: cn controller n. dn lun n (0-1). sn UNIX system slice n (0-15). pn fdisk partition (0-36). /kernel/drv/cmdk 32-bit kernel module. /kernel/drv/amd64/cmdk 64-bit kernel module. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Architecture |x86 | +-----------------------------+-----------------------------+ SEE ALSO
fdisk(1M), mount(1M), lseek(2), read(2), write(2), readdir(3C), scsi(4), vfstab(4), attributes(5), dkio(7I) SunOS 5.11 4 Nov 2008 cmdk(7D)