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.

Introduction to Linux - A Hands on Guide

This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.

I am so happy about the new release of Slackware 14.0 that I immediately started to reinstall my test boxes.
The first is a Slackbox with LVM and LUKS encrypted partition. Ẃhere I have my hard-drive partitioned the same way how it is described in the README_CRYPT.TXT.

/dev/sda1 /boot
/dev/sda2 /LUKS-LVM

I have completed such installations successfully several times but now I was surprised that I couldn't choose /dev/sda1 for /boot. I just cannot see my partition /dev/sda1 in the list.

Are you sure you added /dev/sda1 partition to be mounted at /boot when installing? I have just seen this error as I am doing basically the same as you. It turns out that the problem was that I forgot to add /dev/sda1 mapping, so the installation put /boot on the root, which is in the LVM part...

I think I could fix this by hand (copying the contents of the old /boot to the new one in /edv/sda1 and fixing /etc/fstab), but I thought it would be safer to go the slow route: run setup again and let it do the job right.

I think I could fix this by hand (copying the contents of the old /boot to the new one in /edv/sda1 and fixing /etc/fstab), but I thought it would be safer to go the slow route: run setup again and let it do the job right.

I added the partition exactly as you noted - manually into fstab and copy the content from the existing boot before I run mkinitrd... .

When I first run setup (in this installation) at point where you choose / ,/home I exit the script and verified whether the /dev/sda1 exists. It was there and I rerun the setup but all I could see was:
/dev/cryptvg/root
/dev/cryptcg/home
/dev/mapper/slackluks

I will see whether the second install on another box will give the same result.

I just finished reinstalling and confirm that now lilo works and sees /dev/sda1 as /boot.
All is well.

What do you mean with "now lilo works"? It means that you tried the installation of such encrypted system and it works for you - or something has been changed and now it works?

I am asking because I tried to do everything from the beginning and I found out that at step "Setting up root Linux partition" I can still see the /dev/sda1 partition in the list. But after this step when I choose /dev/cryptvg/root > Format with ext4 > I get back to the Step "Setting up other Linux partitions" and here in the list of devices I already cannot see the /dev/sda1.
-------------------
EDIT
Ok it looks like there is some problem with that hardware (HP Proliant micro N36L) on the other box it works (I can see /dev/sda1 - maybe hardware bug).