LinuxQuestions.org
Go Job Hunting at the LQ Job Marketplace
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 02-02-2008, 10:40 AM   #1
/y0shi
Member
 
Registered: Jan 2006
Location: berlin, germany
Distribution: slackware 12.0
Posts: 58

Rep: Reputation: 15
dm-crypted root with filesystem checking


To be more specific I followed http://wiki.linuxquestions.org/wiki/...t_partition.3F
to install Slackware Linux 12.0 onto my thinkpad, its not so detailed but worked pretty well with hints from http://de.gentoo-wiki.com/DM-Crypt#R...chl.C3.BCsseln for building init.

Now booting into an encrypted system works until and beyond one error message:

[...]
*** ERROR: Root partition has already been mounted read-write. Cannot check! [...]

(this comes from /etc/rc.d/rc.S line 208 - 227)

If I boot my ram0 with read-only then booting fails because he needs to create stuff for cryptsetup and so one (I dont really know, but trial and error ...).

After luksOpen my init mounts /dev/mapper/root to /mnt I tried to put a -o ro flag in there but thats not what it wants ...

Has some one out there experience with stuff like that - any help is much appreciated!

Thanks --y0shi
 
Old 02-02-2008, 06:07 PM   #2
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,223

Rep: Reputation: Disabled
Maybe you should read http://slackware.osuosl.org/slackwar...ADME_CRYPT.TXT first.
It's on your Slackware 12.0 install CD too.

Eric
 
Old 02-03-2008, 11:31 AM   #3
/y0shi
Member
 
Registered: Jan 2006
Location: berlin, germany
Distribution: slackware 12.0
Posts: 58

Original Poster
Rep: Reputation: 15
I have to admit, I was not aware of that file (-:

Thank you I will see what I understand ...
 
Old 02-16-2008, 06:55 AM   #4
/y0shi
Member
 
Registered: Jan 2006
Location: berlin, germany
Distribution: slackware 12.0
Posts: 58

Original Poster
Rep: Reputation: 15
Thats nice! I think it is remarkable how good encrypted root filesystem support in Slackware 12.0 is.

I used the the mentioned file README_CRYPT.TXT and I think everyone should read http://alien.slackbook.org/dokuwiki/...lackware:setup for actually changes.

Everything works now really nicely but I was confused by the hints for your lilo.conf in Row 246. I think there is a typo in here:

Quote:
* We have one additional change to make, and that is almost at the top
of the file. Look up the line that says "boot = /dev/mapper/cryptroot"
and which was the reason for lilo to fail installing itself. Change the
boot device to name of the small *unencrypted* partition you've created
and which is mounted under '/boot'. Assuming the name of that partition is
'/dev/sda4', the "boot =" line must become like this:

boot = /dev/sda4
Because at the top of the lilo.conf file where it says "boot =" I put the the device not a partition. In my case it is "boot = /dev/hda" and the bootpartition (in my case /dev/hda1) is called in the line with "root = /dev/hda1". So my lilo.conf looks like that and works perfectly:

Code:
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
lba32 # Allow booting past 1024th cylinder with a recent BIOS
boot = /dev/hda
compact # faster, but won't work on all systems.
#prompt
#timeout = 5
# VESA framebuffer console @ 1024x768x256
vga = 773
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# ramdisk = 0 # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz-generic-smp-2.6.21.5-smp
initrd = /boot/initrd.gz
root = /dev/hda1
label = nemesis
read-only # Partitions should be mounted read-only for checking
# Linux bootable partition config ends
So I'm not sure what the best lilo.conf would be, but I think the lilo.conf in README_CRYPT.TXT is not working as far as I'm concerned.
 
  


Reply

Tags
dmcrypt, rootfs, slackware


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
Problem checking root filesystem when booting Slackware daschaich Slackware 2 09-01-2006 09:55 PM
Freeze at "Checking root filesystem" Xycaleth Linux - General 2 12-15-2005 01:34 AM
booting stops at - checking root filesystem varun_saa Mandriva 3 09-29-2005 12:58 AM
mandrake10.1 hangs while "Checking Root Filesystem" whatpot Linux - Newbie 2 02-25-2005 09:28 PM
hang @ "CHECKING ROOT FILESYSTEM" whatpot Mandriva 2 02-13-2005 05:03 PM


All times are GMT -5. The time now is 05:30 AM.

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