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.
For the first time I am trying full disc encryption with Luks and LVM over that. I followed Alien Bobs crypt.txt but it will not boot.
The initrd obviously works and does its thing but then the system cannot mount.
The error I get back while booting is
Code:
4 logical volumes in volume group "slack13-group" now active.
mount: mounting /dev/slack13-group/root on /mnt failed: invalid argument.
When I built initrd with mkinitrd I chroot to /mnt as instructed in the crypt.txt. I do not really know what I am doing at this point but it seems that it is trying to mount /root on /mnt which must surely be wrong?
Distribution: Slackware64 14.2 and current, SlackwareARM current
Posts: 1,647
Rep:
The switch to /mnt is normal. If you take a look at the "init" script in your initrd-tree, you will see that the root partition, /proc and /sys are first mounted in /mnt, then as last command the init script switches there (like a chroot) and gives control to the root partitions init script I think.
My best guess is that you have some wrong argument in your mkinitrd line. Are you sure you have given the right filesystem type?
ah yes, I think you are right. Was getting confused between root and boot partitions. boot is ext2 which is what I specified to mkinitrd but root is reiser. Will give it another shot, thanks.
Thanks for the advice, just one more question. Without having to go through all the install (setup) procedure again how can I get the system mounted so I can mkinitrd again? I mean I can put in the install cd and get the command prompt, unlock the root partition and activate the lv's but then how should I proceed?
Distribution: Slackware64 14.2 and current, SlackwareARM current
Posts: 1,647
Rep:
It is necessary to mount your root Slackware partition under /mnt first, if you have a seperate boot partition, mount it too. then /proc and /sys, after that do the chroot
Thanks guys, got it working. But have to confess had to go through the install process yet again. After I mounted everything and issued the chroot I got the message
Code:
chroot: can't execute '/bin/sh' no such file or directory
so rather than figure that just reinstalled it. As titopoquito said, I had used the wrong filesystem in my mkinitrd command. I has used the boot file system not the root one.
So Alien Bob, just goes to show you can write the clearest and most complete instructions on the planet and some people (me) will still manage to make a hash of it!!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.