inittab trouble

Axeman747 · 06-02-2006, 05:49 PM

I installed Slackware 10.2 got it all set up and running fine, I then updated my kernel to 2.6.16.18 got that all set up, sound working mouse working installed Nvidia drivers all without a hitch. I set up Lilo with the new kernel info did a few reboots without any trouble, then it all went wrong, I edited my inittab to boot into X (runlevel 4) well when I rebooted I t wouldn't boot into 2.6 kernel it gave these errors

Code:

ext2 -fs: hda1: couldn't mount because of unsupported optional features(4)

Code:

UDF -f: no partition found(1)

Code:

Kernel Panic - not syncing: VFS: unable to mount root fs on unknown block (3,1)

. If I tried to boot to the 2.4.31 kernel it goes all the way to saying starting X then a grey window would flash and then go right back to the black boot screen with no prompt or anything. I tried a few times in each kernel with no luck so I Ctrl-Alt-f6 ed into a console and edited the inittab file back to run level3 now all is back to running good again (both kernels).I guess my question is why did editing inittab cause this?

masonm · 06-02-2006, 07:02 PM

Can you start X from the CLI?

Bruce Hill · 06-02-2006, 07:18 PM

Welcome to LQ!

You should post the output of:
/etc/lilo.conf
/etc/inittab
lsmod
fdisk -l
mount
uname -a

Maybe that's overkill, or not enough, but we need to see what you've done.

Axeman747 · 06-02-2006, 07:22 PM

Once I changed inittab back to runlevel3 I have no problem starting X with "startx". With inittab at runlevel4 I couldn't get into anything.
Chinaman- I'll post them up.

Bruce Hill · 06-02-2006, 07:28 PM

One thing about changing kernels with Nvidia drivers.
They are free, but not open source. So they can't be
included in the kernel. Therefore, every time you boot
into a different kernel you have to install the Nvidia
driver again or you can't start X. This is assuming of
course that you change the video driver from 'vesa' to
'nvidia' in /etc/X11/xorg.conf. If you leave it 'vesa'
then X will load, but you won't get the benefits of the
Nvidia driver -- it must say nvidia -- not nv or vesa,
to load and use the Nvidia driver.

Bruce Hill · 06-02-2006, 07:30 PM

Please also post the output of '/etc/fstab' so we can see what caused that fs error.

Axeman747 · 06-02-2006, 07:36 PM

I installed the Nvidia drivers in the new Kernel and they worked. I did try to start X without and found that I hsd to change Xorg back to "vesa" driver first. Heres the file output you asked me to post.

Code:

lsmod
Module                  Size  Used by
snd_pcm_oss            39584  0
snd_mixer_oss          17024  1 snd_pcm_oss
lp                     10056  0
parport                33224  1 lp
ipv6                  240768  12
ohci_hcd               18564  0
via_agp                 8320  1
shpchp                 44736  0
snd_cmipci             32288  1
gameport               11784  1 snd_cmipci
snd_pcm                78600  2 snd_pcm_oss,snd_cmipci
snd_page_alloc          8840  1 snd_pcm
snd_opl3_lib            9984  1 snd_cmipci
snd_timer              20356  2 snd_pcm,snd_opl3_lib
snd_hwdep               7556  1 snd_opl3_lib
snd_mpu401_uart         6528  1 snd_cmipci
snd_rawmidi            20000  1 snd_mpu401_uart
snd_seq_device          7180  2 snd_opl3_lib,snd_rawmidi
snd                    47844  12 snd_pcm_oss,snd_mixer_oss,snd_cmipci,snd_pcm,snd_opl3_lib,snd_timer,snd_hwdep,snd_mpu401_uart,snd_rawmidi,snd_seq_device
soundcore               7520  1 snd
uhci_hcd               30608  0
ehci_hcd               29832  0
i2c_viapro              7700  0
via_rhine              20868  0
mii                     4992  1 via_rhine
nvidia               4547028  12
pcmcia                 32164  0
firmware_class          8320  1 pcmcia
yenta_socket           24716  0
rsrc_nonstatic         12032  1 yenta_socket
pcmcia_core            36752  3 pcmcia,yenta_socket,rsrc_nonstatic
nls_iso8859_1           4096  1
nls_cp437               5760  1
vfat                   10752  1
fat                    48540  1 vfat
ide_scsi               14852  0
usb_storage            85696  0
agpgart                29488  2 via_agp,nvidia

Code:

fdisk -l

Disk /dev/hda: 120.0 GB, 120060444672 bytes
255 heads, 63 sectors/track, 14596 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hda1               1        1216     9767488+  83  Linux
/dev/hda2            1217        1459     1951897+  82  Linux swap

Disk /dev/hdb: 40.0 GB, 40020664320 bytes
255 heads, 63 sectors/track, 4865 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hdb1   *           1        2453    19703691    7  HPFS/NTFS
/dev/hdb2            2454        4865    19374390    f  W95 Ext'd (LBA)
/dev/hdb5            2454        4865    19374358+   b  W95 FAT32

Code:

mount
/dev/hda1 on / type ext3 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
/dev/hdb5 on /fat type vfat (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
usbfs on /proc/bus/usb type usbfs (rw)

Code:

uname -a
Linux localhost 2.6.16.18 #2 Thu Jun 1 20:30:17 EDT 2006 i686 unknown unknown GNU/Linux

Code:

# inittab	This file describes how the INIT process should set up
#		the system in a certain run-level.
#
# Version:	@(#)inittab		2.04	17/05/93	MvS
#                                       2.10    02/10/95        PV
#                                       3.00    02/06/1999      PV
#                                       4.00    04/10/2002      PV
#
# Author:	Miquel van Smoorenburg, <miquels@drinkel.nl.mugnet.org>
# Modified by:	Patrick J. Volkerding, <volkerdi@slackware.com>
#

# These are the default runlevels in Slackware:
#   0 = halt
#   1 = single user mode
#   2 = unused (but configured the same as runlevel 3)
#   3 = multiuser mode (default Slackware runlevel)
#   4 = X11 with KDM/GDM/XDM (session managers)
#   5 = unused (but configured the same as runlevel 3)
#   6 = reboot

# Default runlevel. (Do not set to 0 or 6)
id:3:initdefault:

# System initialization (runs when system boots).
si:S:sysinit:/etc/rc.d/rc.S

# Script to run when going single user (runlevel 1).
su:1S:wait:/etc/rc.d/rc.K

# Script to run when going multi user.
rc:2345:wait:/etc/rc.d/rc.M

# What to do at the "Three Finger Salute".
ca::ctrlaltdel:/sbin/shutdown -t5 -r now

# Runlevel 0 halts the system.
l0:0:wait:/etc/rc.d/rc.0

# Runlevel 6 reboots the system.
l6:6:wait:/etc/rc.d/rc.6

# What to do when power fails.
pf::powerfail:/sbin/genpowerfail start

# If power is back, cancel the running shutdown.
pg::powerokwait:/sbin/genpowerfail stop

# These are the standard console login getties in multiuser mode:
c1:1235:respawn:/sbin/agetty 38400 tty1 linux
c2:1235:respawn:/sbin/agetty 38400 tty2 linux
c3:1235:respawn:/sbin/agetty 38400 tty3 linux
c4:1235:respawn:/sbin/agetty 38400 tty4 linux
c5:1235:respawn:/sbin/agetty 38400 tty5 linux
c6:12345:respawn:/sbin/agetty 38400 tty6 linux

# Local serial lines:
#s1:12345:respawn:/sbin/agetty -L ttyS0 9600 vt100
#s2:12345:respawn:/sbin/agetty -L ttyS1 9600 vt100

# Dialup lines:
#d1:12345:respawn:/sbin/agetty -mt60 38400,19200,9600,2400,1200 ttyS0 vt100
#d2:12345:respawn:/sbin/agetty -mt60 38400,19200,9600,2400,1200 ttyS1 vt100

# Runlevel 4 used to be for an X window only system, until we discovered
# that it throws init into a loop that keeps your load avg at least 1 all 
# the time. Thus, there is now one getty opened on tty6. Hopefully no one
# will notice. ;^)
# It might not be bad to have one text console anyway, in case something 
# happens to X.
x1:4:wait:/etc/rc.d/rc.4

# End of /etc/inittab

Code:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hda
#message = /boot/boot_message.txt
prompt
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
  reset
# VESA framebuffer console @ 1024x768x256
vga = 773
install=/boot/boot-bmp.b
bitmap = /boot/logo64a.bmp
bmp-colors = 15,,0;5,,15
bmp-table = 59,5,1,18,
bmp-timer= 66,28,6,8,0
# 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
# End LILO global section
# Windows bootable partition config begins
#other = /dev/hdb1
#  label = Windows
#  table = /dev/hdb
# Windows bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/hda1
  label = Slack2.4.31
  read-only # Non-UMSDOS filesystems should be mounted read-only for checking
image = /boot/vmlinuz-custom-2.6.16.18
root = /dev/hda1
label = Slack2.6.18
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends

Axeman747 · 06-02-2006, 07:37 PM

fstab output

Code:

/dev/hda2        swap             swap        defaults         0   0
/dev/hda1        /                ext3        defaults         1   1
/dev/hdb5        /fat             vfat        defaults         1   0
/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

Thanks for the welcome Chinaman!

Bruce Hill · 06-02-2006, 09:13 PM

First, you obviously have the Nvidia driver installed properly with the running kernel, because it shows up in your "lsmod" output -- good.

Second, for this error:

Code:

ext2 -fs: hda1: couldn't mount because of unsupported optional features(4)

what optional features do you have in the kernel? And I don't see ext2, only an ext3 fs. Did you compile ext2 rather than ext3 into your 2.6.16.18 kernel there? Look below for how to "grep" your config file to determine that.
NB: It would be better to have a separate /home from your / filesystem. That would
allow you to reinstall your system if need be, without formatting /home and losing any of
your personal data.

Third, for this error:

Code:

UDF -f: no partition found(1)

where is the UDF partition you are trying to mount? Is there a UDF CD in the drive when you boot? From "man mount"

Code:

       -f     Causes everything to be done except for the actual system call; if it's not
              obvious, this ``fakes'' mounting the file system.  This option is useful in
              conjunction with the -v flag to determine what the mount command is  trying
              to  do.  It  can  also be used to add entries for devices that were mounted
              earlier with the -n option.

Fourth, for this error:

Code:

Kernel Panic - not syncing: VFS: unable to mount root fs on unknown block (3,1)

that usually means that you have support for your / (root) filesystem as a module (M) rather than built-in (Y) in your kernel. You can easily find that by issuing:

Code:

mingdao@silas:~$ cat kernel/linux-2.6.16.18/.config | grep -i ext3
# CONFIG_EXT3_FS is not set

where you will need to change my kernel path for yours. In my boxen I only use ReiserFS:

Code:

mingdao@silas:~$ cat kernel/linux-2.6.16.18/.config | grep -i reiserfs
CONFIG_REISERFS_FS=y
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
# CONFIG_REISERFS_FS_XATTR is not set

Your / (root) filesystem must be built into your kernel or it will not boot without an initrd image.

Also , in your "/etc/lilo.conf" it looks like you've included the LiLO bitmap image from
the Shiloh site. If so, you have omitted the first line which reads "map = /boot/map-bmp".
Don't know if that's important or not, as I do things the same as him. I do have a different
LiLO bitmap on this box and don't use such a line, either.

Fourth, you seem to have modules loading you might not need. Such as:

Code:

pcmcia                 32164  0
firmware_class          8320  1 pcmcia
yenta_socket           24716  0
rsrc_nonstatic         12032  1 yenta_socket
pcmcia_core            36752  3 pcmcia,yenta_socket,rsrc_nonstatic

Those are for PCMCIA cards that you insert into a laptop computer. There are other modules which you might not need, but they shouldn't hurt you.

masonm · 06-02-2006, 09:30 PM

Quote:

"map = /boot/map-bmp".

No longer needed.

Bruce Hill · 06-02-2006, 09:32 PM

Thanks, masonm -- I suspected that but wasn't sure.
Please correct or add to what I posted if needed...

Axeman747 · 06-03-2006, 06:17 PM

Chinaman cat shows

Code:

bryan@localhost:~$ cat /usr/src/linux-2.6.16.18/.config | grep -i ext3
CONFIG_EXT3_FS=m
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y

So what does this mean? Should I recompile the kernel? I would like to use runlevel4, I guess I'm a little lazy.

Bruce Hill · 06-03-2006, 07:27 PM

Quote:

Originally Posted by Axeman747

Chinaman cat shows

Code:

bryan@localhost:~$ cat /usr/src/linux-2.6.16.18/.config | grep -i ext3
CONFIG_EXT3_FS=m
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y

So what does this mean? Should I recompile the kernel? I would like to use runlevel4, I guess I'm a little lazy.

This tells me you have your / filesystem as a module, not built in. So this kernel will not boot unless you use an initrd - boot loader initialized RAM disk. Since I've never used an initrd.img, I don't know how this might effect other areas of the boot process.

In your first post you said "I Ctrl-Alt-f6 ed into a console and edited the inittab file back to run level3 now all is back to running good again (both kernels)."

Therefore, I'm at a bit of a loss. Could you post the contents of /boot/initrd.gz ?

And there were other questions you didn't answer.