LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
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 10-20-2011, 10:23 PM   #1
BashTin
Member
 
Registered: May 2003
Location: West Midlands, United Kingdom.
Distribution: Slackware 13.37
Posts: 249

Rep: Reputation: 32
Trouble booting new Slack 13. LVM on Luks


First thanks for those who helped me out on a related thread

http://www.linuxquestions.org/questi...drives-908866/

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?

My the fstab looks like this
Code:
/dev/slack13-group/root /                reiserfs    defaults         1   1
/dev/slack13-group/home /home            reiserfs    defaults         1   2
/dev/slack13-group/usr /usr             reiserfs    defaults         1   2
/dev/sdb1        /boot            ext2        defaults         1   2
#/dev/cdrom      /mnt/cdrom       auto        noauto,owner,ro  0   0
/dev/fd0         /mnt/floppy      auto        noauto,owner     0   0
devpts           /dev/pts         devpts      gid=5,mode=620   0   0
proc             /proc            proc        defaults         0   0
tmpfs            /dev/shm         tmpfs       defaults         0   0
I've tried reinstalling a few times but the result is the same.

Ok, to the rescue someone, please.

BashTin.
 
Old 10-21-2011, 05:35 AM   #2
titopoquito
Senior Member
 
Registered: Jul 2004
Location: Ruhr Area, Germany
Distribution: Slackware64 14.0
Posts: 1,517

Rep: Reputation: 90
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?
 
Old 10-21-2011, 06:17 AM   #3
BashTin
Member
 
Registered: May 2003
Location: West Midlands, United Kingdom.
Distribution: Slackware 13.37
Posts: 249

Original Poster
Rep: Reputation: 32
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.
 
Old 10-21-2011, 07:19 AM   #4
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,191

Rep: Reputation: Disabled
Next time, also show us the mkinitrd command you used to create the initrd image. As well as the relevant lilo.conf section.

Eric
 
Old 10-21-2011, 09:29 AM   #5
BashTin
Member
 
Registered: May 2003
Location: West Midlands, United Kingdom.
Distribution: Slackware 13.37
Posts: 249

Original Poster
Rep: Reputation: 32
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?

BashTin

Last edited by BashTin; 10-21-2011 at 09:31 AM.
 
Old 10-21-2011, 11:06 AM   #6
titopoquito
Senior Member
 
Registered: Jul 2004
Location: Ruhr Area, Germany
Distribution: Slackware64 14.0
Posts: 1,517

Rep: Reputation: 90
Start with the Slackware CD. When you've mounted the root partition on /mnt, I am not sure if you also need

Code:
mount -o bind /proc /mnt/proc
mount -o bind /sys /mnt/sys
but you don't have any disadvantage of it. Then chroot to /mnt and try another mkinitrd line
 
Old 10-21-2011, 12:19 PM   #7
BCarey
Senior Member
 
Registered: Oct 2005
Location: New Mexico
Distribution: Slackware
Posts: 1,453

Rep: Reputation: Disabled
Quote:
Originally Posted by titopoquito View Post
Start with the Slackware CD. When you've mounted the root partition on /mnt, I am not sure if you also need

Code:
mount -o bind /proc /mnt/proc
mount -o bind /sys /mnt/sys
but you don't have any disadvantage of it. Then chroot to /mnt and try another mkinitrd line
Is it not necessary to mount the boot partition and the other partitions under /mnt?

Brian
 
Old 10-22-2011, 01:33 AM   #8
titopoquito
Senior Member
 
Registered: Jul 2004
Location: Ruhr Area, Germany
Distribution: Slackware64 14.0
Posts: 1,517

Rep: Reputation: 90
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
 
Old 10-22-2011, 07:56 PM   #9
BashTin
Member
 
Registered: May 2003
Location: West Midlands, United Kingdom.
Distribution: Slackware 13.37
Posts: 249

Original Poster
Rep: Reputation: 32
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!!

BashTin

Last edited by BashTin; 10-22-2011 at 07:58 PM.
 
  


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
Trouble booting up to LVM partition on Raid1. gammahermit Linux - General 2 07-11-2010 11:37 AM
Luks/Lvm after dd duplication brodo Slackware 10 03-12-2009 03:56 PM
New kernel and existing Luks/Lvm ? brodo Slackware 3 09-14-2008 09:44 AM
luks cryptsetup and lvm question ruzzed Linux - Software 3 09-16-2007 07:21 PM
Trouble booting Slack 9.1 after a restart bdevcich Slackware 3 12-28-2003 07:02 PM


All times are GMT -5. The time now is 10:33 PM.

Main Menu
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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration