SlackwareThis Forum is for the discussion of Slackware Linux.
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.
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.
Click Here to receive this Complete Guide absolutely free.
I upgraded to mkinitrd-1.3.2-i486-1, and I have the same problem than mkinitrd-1.3.1-i486-4.
When I upgraded, I typed mkinitrd whit arguments, and I get the same errors than mkinitrd-1.3.1-i486-4.Then, I reverted to mkinitrd-1.1.2-i486-3, typed mkinitrd with arguments, and It works fine. Then, upgraded to mkinitrd-1.3.2-i486-1, and typed mkinitrd whit no arguments, and It works fine.
I don't know what is the problem.
In my previous thread "Slackware-current and mkinitrd-1.3.1, I wrote:
""I have a laptop with Slackware-current. It has a hard disk with two partitions; one ,hda1,unencrypted, for the /boot filesystem, ant another, hda2, with three LV encrypted whit cryptsetup/LUKS for the /, /home and swap filesystems. All make according to README_CRYPT.TXT and README_LVM.TXT documents.
All works fine, until I upgraded mkinitrd whit the mkinitrd-1.3.1 package.
After I upgrades the package, I rebooted the laptop and, behind initrd loads the modules, it stops and I get the next error messages:
Command failed: dm_task_set_name: Device /dev/mapper/cryptroot not found
mount: mounting /dev/mapper//dev/mapper/cryptroot on /mnt failed: No such file or directory.
ERROR: No /sbin/init found on rootdev (or not mounted). Trouble ahead.
Behind the prompt, I run exit, and I get a kernel panic.
I search for help on Google, but the only valid answer was in the URL
<http://alien.slackbook.org/dokuwiki/doku.php?id=slackware:setup>. It was one modification to the README_CRYPT.TXT document, above mentioned.
I followed the next steps for make the modification above mentioned. Behind I boot the laptop with the CD1 from Slackware Installation, I run the next commands:
cryptsetup luksOpen /dev/mivg/root cryptroot
cryptsetup luksOpen /dev/mivg/home /crypthome
mount -t ext3 /dev/mapper/cryptroot /mnt
mount -t ext3 /dev/mapper/crypthome /mnt/home
mount -t ext3 /dev/ha1 /mnt/boot
mount -o bind /proc /mnt/proc
mount -o bind /sys /mnt/sys
mount -o bind /dev /mnt/dev (this is the modification above mentioned. It gets error,and I run the next command)
cp -a /dev/mapper/ /mnt/dev
mkinitrd -c -k 184.108.40.206 -m ext3 -f ext3 -r cryptroot -C /dev/mivg/root -L
I reboot the laptop, and I get the same errors.
If, in the prompt after the boot, I make ls -la /dev/mapper, I get
Don't appear the encrypted devices cryptroot and crypthome, why?
I have the makeinitrd-1.3.1-i486-4.tgz and I don't use lilo but grub
I reverted to mkinitrd-1.1.2-i486-3 (from CD1), and it works fine
When I reverted to mkinitrd-1.1.2-i486-3 and it worked fine, I upgraded to mkinitrd-1.3.1-i486-4 and typed mkinitrd with not arguments, and it worked fine.
Now, I upgraded kernel to kernel-220.127.116.11, and typed mkinitrd with arguments, and the problem return. I have the same error messages of the first post.
I reverted to mkinitrd-1.1.2-i486-3, and typed mkinitrd with arguments, it worked fine with the new kernel. Then upgraded to mkinitrd-1.3.1-i486-4, typed mkinitrd with no arguments, and it works fine with the new kernel.""
Now, I upgraded to mkinitrd-1.3.2-i486-1, typed mkinitrd with arguments, reboot the PC, and I see the same errors from above. If I revert to mkinitrd-1.1.2-i486-3, type mkinitrd with arguments, it works fine after reboot. I upgrade to mkinitrd-1.3.2-i486-1, type mkinitrd with no arguments, and it works fine after reboot.
Everyone I have seen sofar with mkinitrd trouble is using grub.
Can you try installing lilo into the /dev/hda1 boot partition and adding a chainloader command to your grub menu that loads lilo in turn? Something like
grub> chainloader +1