SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Actually, I found one strange thing. Every new initrd.gz I create differ from previous with it checksum. Is it normal? I mean with exactly the same system components if I create 5-6 initrd one by one they all have different checksums.
Actually, I found one strange thing. Every new initrd.gz I create differ from previous with it checksum. Is it normal? I mean with exactly the same system components if I create 5-6 initrd one by one they all have different checksums.
initrd is actually a small filesystem image loaded to RAM at boot. Because it includes timestamps, you'll never get the same checksum on regenerating it.
Did you create your luks partition on slackware current, then install slackware 14.2? By default cryptsetup-2.3.2 (current) creates LUKS2 type but cryptsetup-1.7.1 (slackware 14.2) only knows LUKS1 type. You can check that with "cryptsetup luksDump /dev/sdb2"
@Panther_, I didn't check exactly for libgcrypt and libgpg, but "N" package set was installed for sure.
@Thom1b, every installation (from creating partition table to configuring elilo) I've mentioned in this thread was performed using slackware-current iso from here.
@Thom1b, every installation (from creating partition table to configuring elilo) I've mentioned in this thread was performed using slackware-current iso from here.
OK, I wasn't sure because you said you follow README_CRYPT.TXT from slackware 14.2 on your first post.
@keeneadt, Did you ever sort this out? Installing current from ISO, I get the same thing. The needed /dev/sdb device simply does not exist, even though I'm looking at the sata drive plugged into a usb cable (which exists perfectly fine in every other conceivable linux scenario, plug it in "hey there's /dev/sdb!"). The /dev/sda device does exist, but it's an unmounted/unopen laptop internal sata drive which is encrypted with a different OS.
A few steps differed from yours. From within the slackware installer I skipped LILO, and installed ELILO when prompted. I had the same /boot/efi fat32 partition (/dev/sdb1, which the installer acknowledged, non-luks), I had the LVM partition (/dev/sdb3 luks), but I also had a linux partition (/dev/sdb2 non-luks) for /boot.
Basically right at the point where I expect to be prompted for luks password to open /dev/sdb3, it drops to the prompt and one of the last things the terminal shows is something "luks" blah blah "/dev/sdb3" blah blah "unavailable for unlocking".
After that, an "fdisk -l" only shows /dev/sda device and partitions. The cryptsetup commands also work. If I run lsmod, I see the usb storage module. If I unplug/plug the sata drive on a usb cable, and run "fdisk -l" again, no change. ...Strange.
EDIT: googling: "linux" "unavailable for unlocking" ...has 8 results, so apparently this almost never happens. Must be something about my install process.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.