I was nearing the end of setting up an encrypted home partition on my Thinkpad when I discovered that vol_id is missing.

root@obsidian:~# vol_id /dev/sdb3
vol_id: command not found

I did a search for it and came across two cryptsetup entries which proved just as useful.

root@obsidian:~# find / -iname *vol_id*
/lib/cryptsetup/checks/vol_id
/lib/cryptsetup/checks/un_vol_id

root@obsidian:~# /lib/cryptsetup/checks/vol_id /dev/sdb3
- WARNING: vol_id from udev is not available, impossible to run checks.

Unbeknownst to me, vol_id is being dropped in favor of blkid starting with Ubuntu 9.10 Karmic Koala, which is certainly a good thing. The blkid command’s output is very intuitive. My soon-to-be dual-boot, dual-drive T61p is a lot easier to set up and map out with blkid.

root@obsidian:~# blkid
/dev/sda1: UUID=”6A569ECC525CD967″ LABEL=”vista_boot” TYPE=”ntfs”
/dev/sda2: UUID=”D4BC0F29BC0F05A8″ LABEL=”vista_swap” TYPE=”ntfs”
/dev/sda3: UUID=”0ADE1B52DE1B3603″ LABEL=”Media” TYPE=”ntfs”
/dev/sdb1: UUID=”d2e9da2f-5e48-45f8-b0f5-d3edbe1b4695″ TYPE=”ext4″
/dev/sdb2: UUID=”6687c2b3-4c09-4d77-8a50-21bcac261247″ TYPE=”crypto_LUKS”
/dev/sdb3: UUID=”d2e7ac26-32f9-4123-94db-9b1d125f3951″ TYPE=”crypto_LUKS”
/dev/mapper/sdb2_crypt: UUID=”9769c898-c93e-4369-aa91-40d2728c70b1″ TYPE=”ext4″
/dev/mapper/sdb3: UUID=”f52ba5da-c97c-4e16-8889-8906f13018cd” TYPE=”ext4″

Now, I have both the partition and file-system UUIDs for sdb3, not to mention all of the others, which I need in order to finish setting up the encrypted partition.

Share