LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 05-24-2020, 12:43 PM   #16
keeneadt
Member
 
Registered: Feb 2020
Distribution: Slackware
Posts: 56

Original Poster
Rep: Reputation: Disabled

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.

Last edited by keeneadt; 05-24-2020 at 12:45 PM.
 
Old 05-24-2020, 01:00 PM   #17
Gnisho
Member
 
Registered: Aug 2012
Location: WA
Distribution: slackware
Posts: 72

Rep: Reputation: Disabled
Quote:
Originally Posted by keeneadt View Post
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.
 
Old 05-24-2020, 03:52 PM   #18
Panther_
LQ Newbie
 
Registered: Jan 2012
Location: Podlasie [Pl]
Distribution: Slackware-current
Posts: 14

Rep: Reputation: Disabled
And you have packages installed libgcrypt, libgpg-error ? (from /n)
 
Old 05-24-2020, 11:33 PM   #19
Thom1b
Member
 
Registered: Mar 2010
Location: France
Distribution: Slackware
Posts: 479

Rep: Reputation: 333Reputation: 333Reputation: 333Reputation: 333
Hi,

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"
 
Old 05-25-2020, 12:19 AM   #20
keeneadt
Member
 
Registered: Feb 2020
Distribution: Slackware
Posts: 56

Original Poster
Rep: Reputation: Disabled
@Gnisho, I see now. Thanks.

@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.
 
Old 05-25-2020, 12:32 AM   #21
Thom1b
Member
 
Registered: Mar 2010
Location: France
Distribution: Slackware
Posts: 479

Rep: Reputation: 333Reputation: 333Reputation: 333Reputation: 333
Quote:
Originally Posted by keeneadt View Post
@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.
 
Old 06-26-2021, 07:35 AM   #22
dfwrider
Member
 
Registered: Feb 2010
Location: San Antonio, Texas, USA
Distribution: Slackware
Posts: 43

Rep: Reputation: 34
@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.

Last edited by dfwrider; 06-26-2021 at 10:00 AM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Unlocking several LUKS volume groups at boot with one passphrase kestralis Slackware 6 02-06-2020 03:58 AM
[SOLVED] LUKS device unavailable for unloacking chandru.in Slackware - Installation 2 09-05-2016 01:31 PM
nonblocking pool message while unlocking luks on current. dmcrtr Slackware 5 09-03-2015 07:03 AM
Unlocking LUKS with keyfile on USB slaka Linux - Software 1 05-16-2014 03:04 PM
LUKS on RAID or RAID on LUKS? retch Linux - Server 3 05-05-2010 01:57 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 03:06 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration