• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 245
  • Last Modified:

problem creating new luks volume on new VM disk

Running RHEL 6 on ESXI 6


I am running into problems.... see below... I have a new disk sdc.  I add a single primary partition, then I run luksFormat, seems OK but when I try to run luksUUID it tells me "Device /dev/sdc1 is not a valid LUKS device."

What am I doing wrong?



[root@server.vm.domain.com] /root # ls -l /dev/sd*
brw-rw---- 1 root disk    8,   0 Oct 24 04:30 /dev/sda
brw-rw---- 1 root disk    8,   1 Oct 24 03:46 /dev/sda1
brw-rw---- 1 root disk    8,  16 Oct 24 04:30 /dev/sdb
brw-rw---- 1 root disk    8,  17 Oct 24 03:46 /dev/sdb1
brw-rw---- 1 root disk    8,  32 Oct 24 04:32 /dev/sdc



[root@server.vm.domain.com] /root # parted /dev/sdc
GNU Parted 2.1
Using /dev/sdc
Welcome to GNU Parted! Type 'help' to view a list of commands.


(parted) print
Model: VMware Virtual disk (scsi)
Disk /dev/sdc: 1100GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start  End  Size  Type  File system  Flags


(parted) mkpart primary 1 -1s

(parted) print
Model: VMware Virtual disk (scsi)
Disk /dev/sdc: 1100GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start   End     Size    Type     File system  Flags
 1      1049kB  1100GB  1100GB  primary


(parted) quit
Information: You may need to update /etc/fstab.

[root@server.vm.domain.com] /root # cryptsetup -c aes-xts-plain64 luksFormat /dev/sdc1

WARNING!
========
This will overwrite data on /dev/sdc1 irrevocably.

Are you sure? (Type uppercase yes): yes
[root@server.vm.domain.com] /root # cryptsetup luksUUID /dev/sdc1
Device /dev/sdc1 is not a valid LUKS device.

[root@server.vm.domain.com] /root # ls -l /dev/sd*
brw-rw---- 1 root disk    8,   0 Oct 24 04:30 /dev/sda
brw-rw---- 1 root disk    8,   1 Oct 24 03:46 /dev/sda1
brw-rw---- 1 root disk    8,  16 Oct 24 04:30 /dev/sdb
brw-rw---- 1 root disk    8,  17 Oct 24 03:46 /dev/sdb1
brw-rw---- 1 root disk    8,  32 Oct 24 04:32 /dev/sdc
brw-rw---- 1 root disk    8,  33 Oct 24 04:31 /dev/sdc1
0
Xetroximyn
Asked:
Xetroximyn
  • 2
  • 2
2 Solutions
 
Gerwin Jansen, EE MVETopic Advisor Commented:
Did you type YES ?


>> Are you sure? (Type uppercase yes): yes
0
 
XetroximynAuthor Commented:
facepalm.jpg
In my defense I've never seen a linux utility require an uppercase yes.   And in linux "no output" commonly means "success".  How hard would it be a print a message "aborting..." or something like that.
0
 
Gerald ConnollyCommented:
Just another reason why i hate Linux!
0
 
Gerwin Jansen, EE MVETopic Advisor Commented:
A message would have been nice, yes. You can try showing the return code after the program exist using:

echo $?

Did you manage getting it setup?
0
 
XetroximynAuthor Commented:
To answer if I got this done yet.... The change got put on hold for a couple weeks because we are in a critical production period and can't risk ANY downtime.    But I have followed the same instructions before a few months ago and been just fine... so I think I should be good :-)  Apparently I was being a little more observant the first time around.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now