[SOLVED] Boot error on LFS 7.5 init scripts

hbinded · 04-11-2014, 02:56 AM

Hi there everyone!
I've built a couple of lfs versions in the past from hand and I've never had a problem that I couldn't solve. LFS really does teach some stuff

To my problem: I built version 7.5 successfully and continued with BLFS for a usable system (dhcp, curl/wget...you get the jist)
I also successfully deployed pacman as my package manager from chapter six (creating directories) to the end. Now after a couple of BLFS packages I try a reboot and wham..red warnings. screenies attached.

BTW, I'm building on an HP635, with amd-e350, 6GB RAM and no optimizations. all is done as per the book.

Keith Hedger · 04-11-2014, 10:02 AM

Had this and similar errors before it has been different things but usually its been a mucked up fstab, I'd check that first.

ReaperX7 · 04-11-2014, 06:03 PM

Can you chroot in from another distribution and post your /etc/fstab?

hbinded · 04-12-2014, 03:07 AM

Okay, here is my fstab:

Code:

# Begin /etc/fstab

# file system  mount-point  type     options             dump  fsck
#                                                              order

/dev/sda8     /            ext3    defaults            1     1
/dev/sda6     swap         swap     pri=1               0     0
proc           /proc        proc     nosuid,noexec,nodev 0     0
sysfs          /sys         sysfs    nosuid,noexec,nodev 0     0
devpts         /dev/pts     devpts   gid=5,mode=620      0     0
tmpfs          /run         tmpfs    defaults            0     0
devtmpfs       /dev         devtmpfs mode=0755,nosuid    0     0

# End /etc/fstab

I went into chroot from ubuntu 12.04 to get that.

hbinded · 04-12-2014, 03:15 AM

okay, an update after reading a couple of google entries...
in the book under 6.6. Creating Essential Files and Symlinks
I didn't notice but my scripts were written to touch the "/etc/mtab" file. I forgot to change it to a symlink to /proc/self/mounts.

Created the symlink and hey presto! everything works wunderbar! Thanks for all your help. This is now SOLVED!

For all those who may run into this problem, check the /etc/mtab file. It should be a symlink and not a file on its own.