LinuxQuestions.org - LFS Boot Problem(LILO,Two Distributions in Two Hard Disks)

- Linux From Scratch (https://www.linuxquestions.org/questions/linux-from-scratch-13/)

- - LFS Boot Problem(LILO,Two Distributions in Two Hard Disks) (https://www.linuxquestions.org/questions/linux-from-scratch-13/lfs-boot-problem-lilo-two-distributions-in-two-hard-disks-560147/)

LFS Boot Problem(LILO,Two Distributions in Two Hard Disks)

Like the title i mentioned, I had two hard disks, one disk for Windows&Slackware and one for the LFS(6.2).

Before i got another disk for LFS, i build the LFS system in Slackware.
And then copied all packages to the second hard disk.

I followed all the instructions in LFS 6.2 book until Chapter 7, i am a little confused what Chapter 7 says, so i skipped a few.

I edited /etc/lilo.conf, add this entry, and run the lilo command.

Code:

#LFS linux

image = /boot/vmlinuz-2.6.21.1

root = /dev/hdb1

label = LFS-2.6.21.1

read-only

But after reboot and enter the "LFS-2.6.21.1", i got the ERROR like this and stopped.

Code:

VFS: Mounted root (ext3 filesystem) readonly

INIT: version 2.85 ...............

INIT: /etc/rc.d/init.d.rc line:97 /dev/null Read-Only File System

Can someone help me out?

Can you post the contents of /etc/rc.d/init.d.rc on your LFS partition? It looks as though it's trying to use /dev/null for something (a file-system?) and failing at line 97.

Hi,

@51dunk: LFS doesn't have a /etc/rc.d/init.d.rc file, it does have /etc/rc.d/init.d/rc file (mind the slash between init.d and rc instead of the/your dot.

If this is not a typo, take a good look at your /etc/inittab file, especially the line that starts with s1. This line should look like this:

si::sysinit:/etc/rc.d/init.d/rc sysinit

Do check the other lines too, but the above line is used during start-up.

Hope this helps.

First of all, thanks for responding.

gilead: the rc file is directly created from lfs bootscript tar, so i don't think that's the reason of failure. I am not post the entire rc file content, because i think it is same as all yours.

druuna: Yes, it's /etc/rc.d/init.d/rc. I just check out the /etc/inittab file, and make sure all things are right, here is my /etc/inittab file content:

Code:

id:3:initdefault:



si::sysinit:/etc/rc.d/init.d/rc sysinit



10:0:wait:/etc/rc.d/init.d/rc 0

11:S1:wait:/etc/rc.d/init.d/rc 1

12:2:wait:/etc/rc.d/init.d/rc 2

13:3:wait:/etc/rc.d/init.d/rc 3

14:4:wait:/etc/rc.d/init.d/rc 4

15:5:wait:/etc/rc.d/init.d/rc 5

16:6:wait:/etc/rc.d/init.d/rc 6



ca:12345:ctrlaltdel:/sbin/shutdown -t1 -a -r now



su:S016:once:/sbin/sulogin



1:2345:respawn:/sbin/agetty tty1 9600

2:2345:respawn:/sbin/agetty tty2 9600

3:2345:respawn:/sbin/agetty tty3 9600

4:2345:respawn:/sbin/agetty tty4 9600

5:2345:respawn:/sbin/agetty tty5 9600

6:2345:respawn:/sbin/agetty tty6 9600

But after i reboot, i got the same error.

I will look at the linux boot process details these days, and i hope someone can pull me out quickly.

Well, I solved this problem, it's the problem of both /dev/null and /etc/inittab file. I make the wrong inittab file first and miss the /dev/null second, so i got success the third try. It's lucky that it has only 2 options, not 200 options ^_^, but it make me feel the linux boot process.