Arrg! Gentoo Linux is driving me nuts!

raid517 · 06-20-2003, 03:25 PM

Arrg not again! This is my second attempt installing Gentoo Linux and I finally finished with KDE and rebooted. However this time I got some complaint about line 1 in fstab being bad and that proc couldn't be found in fstab or mtab. If I navigate now to the / directory, just to check proc was there, here is a print out of what I currently see:

bin boot dev etc home lib mnt opt proc root sbin tmp usr var

So proc is definately there.

I tried /proc instead of just proc in fstab, but I still got the same message. If I could just mount this damn proc file system I would be up and flying. As it is, bott hangs at that point. I have definately included native support for it (i.e. not simply as a kernel module) in the kernel.

Here is my partition table and other details:

Partition Table

Code:

   hda1                    Primary   boot  NTFS                        122926.81
    hdb1                    Primary   Linux  ext2                          213.86
    hdb2                    Primary   Linux  swap                        542.87
    hdb3                    Primary   Linux ReiserFS                   31815.39
    hdb5                    Logical   Win95 FAT32                      45526.93
    hdb6                    Logical   Win95 FAT32                      45420.00
    sda5                     logical    NTFS                                  122926.81

fstab

Code:

proc       /proc proc defaults 0 0
/dev/fd0   /mnt/auto/floppy user,noauto,exec,umask=022 0 0
/dev/cdrom /mnt/auto/cdrom auto user,noauto,exec,rw 0 0
/dev/sda5  /mnt/sda5 ntfs noauto,users,exec,ro,umask=022 0 0
/dev/hda1  /mnt/hda1 ntfs noauto,users,exec,ro,umask=022 0 0
/dev/hdb2  none swap defaults 0 0
/dev/hdb3  / ReiserFS noauto,users,exec,umask=022 0 0
/dev/hdb5  /mnt/hdb5 noauto,users,exec,rw,umask=022 0 0
/dev/hdb6  /mnt/hdb6 noauto,users,exec,rw,umask=022 0 0

lilo.conf

Code:

# $Header: /home/cvsroot/gentoo-x86/sys-apps/lilo/files/lilo.conf,v 1.3 2002/09/30 00:55:18 woodchip Exp $
# Author: Ultanium
# Start LILO global section
menu-scheme=Wb
boot = /dev/hda
prompt
#boot=/devices/discs/disc0/disc
map = /boot/System.map
#compact    	# faster, but won't work on all systems.
lba32
#if lba32 do not work, use linear
#linear
#if you always want to see the prompt with a 15 second timeout:
#timeout=150
delay = 50
vga = normal                              
# End LILO global section
# Linux bootable partition config begins
	image = /boot/bzImage
	root = /dev/hdb3
	#root = /devices/discs/disc0/part3
	label = Gentoo
	read-only # read-only for checking
# Linux bootable partition config ends
# DOS bootable partition config begins
	other = /dev/hda1
	#other = /devices/discs/disc0/part1
	label = WindowsXP
	table = /dev/hda
# DOS bootable partition config ends

Can anyone please advise and help me get out of this final hole? All input is extremely welcome.

Q

Half_Elf · 06-20-2003, 03:38 PM

can you tell us the REAL error msg? it's pretty hard to kinow what's really the problem without the full error msg. Sometime, error msg are a bit dumb, maybe your fstab isn't the problem.

nuzzy · 06-20-2003, 03:39 PM

I'd go off of this:

/dev/sda1 / ext2 defaults 1 1
/dev/sda2 /usr/local ext2 defaults 1 1
/dev/sda4 /home ext2 defaults 1 1
/dev/sdb1 swap swap defaults 0 0
/dev/sdb3 /export ext2 defaults 1 1
none /proc proc defaults 0 0
/dev/fd0 /mnt ext2 defaults 0 0
/dev/cdrom /cdrom iso9660 ro 0 0

Of course tailor it to your system. It looks like you're missing "none" in the beginning of your proc line.

IMHO...this should work. You can still add your permissions to it.

fancypiper · 06-20-2003, 03:46 PM

Double check your kernel compile, referring to Code listing 15.3 in the install instructions:

Quote:

Code listing 15.3: make menuconfig options

Code maturity level options --->[*] Prompt for development and/or incomplete code/drivers"
(You need this to enable some of the options below.)
...

File systems --->
<*> Reiserfs support
(Only needed if you are using reiserfs.)
...
<*> Ext3 journalling file system support
(Only needed if you are using ext3.)
...[*] Virtual memory file system support (former shm fs)
(Required for Gentoo Linux.)
...
<*> JFS filesystem support
(Only needed if you are using JFS.)
...[*] /proc file system support
(Required for Gentoo Linux.)[*] /dev file system support (EXPERIMENTAL)[*] Automatically mount at boot
(Required for Gentoo Linux.)
[ ] /dev/pts file system for Unix98 PTYs
(Uncheck this, it is NOT needed.)
...
<*> Second extended fs support
(Only needed if you are using ext2.)
...
<*> XFS filesystem support
(Only needed if you are using XFS.)

Here is my /etc/fstab for a reference

Code:

# /etc/fstab: static file system information.
# $Header: /home/cvsroot/gentoo-src/rc-scripts/etc/fstab,v 1.10 2002/11/18 19:39:22 azarah Exp $
#
# noatime turns of atimes for increased performance (atimes normally aren't
# needed; notail increases performance of ReiserFS (at the expense of storage
# efficiency).  It's safe to drop the noatime options if you want and to
# switch between notail and tail freely.

# <fs>                  <mountpoint>    <type>          <opts>          <dump/pass>

# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
/dev/hda2               /boot           ext3            noauto,noatime  1 1
/dev/hda3               /               reiserfs        noatime         0 0
/dev/hda8               /home           reiserfs        noatime         0 0
/dev/hda5               none            swap            sw              0 0
/dev/cdroms/cdrom0      /mnt/cdrom      iso9660         noauto,ro       0 0
proc                    /proc           proc            defaults        0 0

# glibc 2.2 and above expects tmpfs to be mounted at /dev/shm for
# POSIX shared memory (shm_open, shm_unlink). Adding the following
# line to /etc/fstab should take care of this:
# (tmpfs is a dynamically expandable/shrinkable ramdisk, and will use almost no
#  memory if not populated with files)

tmpfs                   /dev/shm        tmpfs           defaults        0 0

raid517 · 06-20-2003, 03:56 PM

Yeah, I think I've got file systems covered.

Is there anywhere I can get a log of my boot up so I can print it here? Sadly it isn't likely to be very long... I did get further (though not much) by putting the proc, virtual file system at the end of the fstab list.

Q

fancypiper · 06-20-2003, 04:16 PM

What system logger did you emerge?

If it was sysklogd, that logs to /var/log/messages

This is vital in the kernel for gentoo and proc:

Quote:

[*] /proc file system support
(Required for Gentoo Linux.)[*] /dev file system support (EXPERIMENTAL)[*] Automatically mount at boot
(Required for Gentoo Linux.)
[ ] /dev/pts file system for Unix98 PTYs
(Uncheck this, it is NOT needed.)

raid517 · 06-20-2003, 05:47 PM

Excuse me if I swear, but I think I deserve it! WTF is this all about??? :

Code:

Remounting fileststems read/write

You need to set /etc/hostname to a valid hostname

Setting hostname to local host

Calculating module dependancies

using /etc/modules.autoload.d/kernel-2.4

checking all filesystems

fschk 1.33

mounting local file systems

mount: mountpoint /mnt/auto/floppy does not exist

modprobe : safemode parameter contains '='

mount : fstype noauto,usrs.exec,rw,umask=022 not supported by the kernel

So essentially its seeing every entry I made in fstab as a file sytem type. How fragging weird is that?

I tripple checked all my file system selections in the kernel and have every one listed in the install instructions as being desirable compiled into the kernel and not just included as modules.

One other weird thing is that CFdisk is now listing my /boot partition as an ext2 partition which I have never used. I am certain I formatted it as ext3, but somehow the kernel and fsck think its an ext2 partition. Fsck also says the 9supposedly) ext2 partition is unreadable. (Which is natural considering it was formatted as ext3).

If my boot partition is hosed can I rebuild it somehow? Is it possible to do that from scratch?

Q

Half_Elf · 06-20-2003, 09:06 PM

herm...
you are missding the FILE SYSTEM TYPE at /dev/fd0
use "auto" if you don't know.
so it should look like :
/dev/fd0 /mnt/auto/floppy auto user,noauto,exec,umask=022 0 0