I have a 2 drive system. 1 SSD drive with normal CentOS stuff; encrypted.
The second hardrive is for SAMBA and has the home directories.
After set up of second drive I reboot and run blkid
I have NO Luks-.... showing up for the sdb drive.
Thanks to all in advance.


======================
I have used the following steps to do dozens of such boxes.

fdisk -l | grep '^Disk' # L not #1
cryptsetup -y -v luksFormat /dev/sdb
cryptsetup luksOpen /dev/sdb BIGDRIVE
ls -l /dev/mapper/BIGDRIVE
cryptsetup -v status BIGDRIVE
cryptsetup luksDump /dev/sdb
dd if=/dev/zero of=/dev/mapper/BIGDRIVE
mkfs.ext4 /dev/mapper/BIGDRIVE
mkdir /home/BIGDRIVE
mount /dev/mapper/BIGDRIVE /home/BIGDRIVE
df -H
cd /home/BIGDRIVE
ls -l
#### ALL TO HEAR WORKS I CAN SEE THE 1TB 2ND DRIVE

reboot
blkid

But I only get (which should be there) which on my other boxes is the first line, here on this one it is the last line on the screen:
/dev/sdb: UUID="31e49c7a-7071-4a36-a58d-9a35638e5235" TYPE="crypto_LUKS"

I should have something like this also:
/dev/mapper/luks-f28862ef-6be7-487f-80c0-aa21ce26319e: UUID="c4ccc1dc-6738-48a0-8922-afa3b7ee11fd" TYPE="ext4"

Hi,

first a tip : use the code tags

For automatic opening of encrypted partitions, you need to add the correct uuid to /etc/crypttab. Then you get a device in /dev/mapper which you can mount.
Not sure if this is systemd specific, but seeing you run CentOs, is should be what you need.

But I can't get the Lux.... stuff to put into cryptab or fstab that is the problem blkid does not show the hard drive after reboot.

/dev/sdb is the hard drive. To see inside the luks container you must open it first. Then blkid (and you) can see the filesystem encased within.

I don't know what you are talking about, sorry.

I have always ran blkid and it gives me the "lux.... " stuff I need to put in fstab & cryptab.

Are you telling us you don't understand the commands you entered in your original post ?.

blkid not seeing the data is a symptom - the problem is that the luks container hasn't been opened.

I basically understand the commands I have in the list from my notes.

The problem is a command is either missing or some upgrade to one of the programs has stop this all from working and I can NOT find out what is the Lux.. goo that need to be put in the fstab & cryptab

Until the password/passphrase is entered, the disk cannot be decoded to get the information...

When you WERE getting the information everything was already set up and decrypted.

Excuse me, but the LUKS header itself has a UUID and type that will be seen and reported by blkid:I assure you that this container has not been unlocked.

The /dev/mapper entry will indeed not be present until the LUKS container has been unlocked.

how do I unlock the sdb luks container?

Start at the beginning. Does /dev/sdb even exist? If so, what does "file -s /dev/sdb" (run as root) report?

CertainlyI never said anything to the contrary - even the quote you used specifically referred to the data within the container.

Sorry, I thought you were referring to blkid not reporting the ' /dev/sdb: UUID="31e49c7a-7071-4a36-a58d-9a35638e5235" TYPE="crypto_LUKS"' that the OP was expecting to see. That is data from the LUKS header, not from within the container.

I am so lost...

I type in on every box I have out there that was setup prior to this box blkid
it give me 2 lines of code associated with SDB and 7 lines associated with SDA the OS/Boot/Swap partition which is fine.

/dev/sdb: UUID="f25862ef-6be7-487f-80c0-aa21ce26319e" TYPE="crypto_LUKS" #line 1

/dev/mapper/luks-f25862ef-6be7-487f-80c0-aa21ce26319e: UUID="c4ccc1dc-6738-48a0-8922-afa3b7ee11fd" TYPE="ext4" #line 9

===============================================
on this computer having followed (I believe exactly the same steps as prior boxes) I only get:

/dev/sdb: UUID="e35862ef-6be7-123f-80c0-aa21ce2234e" TYPE="crypto_LUKS" #line 8 which should be 1st line.

That UUID is what you need to put in /etc/crypttab for the "UUID=" parameter.