Re: devfs and 2.4.19-686
On Fri, 2002-10-11 at 13:12, Herbert Xu wrote:
> Kenneth Macdonald Karlsen <ken@fiona-victor.com> wrote:
> >
> > It loads cramfs and finds the disks but for some reason it tries to find
> > root in
> > /dev2/root. I have used devfs before on my system (stable with
>
> /dev2/root is a temporary device created by the initrd scripts.
> Please show me the last few lines on the screen so we can find the
> real problem.
> --
Here is error messages:
It detects disks ok: (all ide devices)
hda ... harddrive (windows)
hdb ... dvd
hdc ... harddrive (linux)
hdd ... cdrw
Partition check
/dev/ide/host0/bus0/target0/lun0
/dev/ide/host0/bus1/target0/lun0
ext3: No journal on filesystem on ide1 (22,6)
mount: wrong fs type, bad option, bad superblock on /dev2/root, or too
many mounted filesystems
warning cant open /etc/mtab no such file or directory
pivot_root; no such file or directory
/sbin/init cannot open dev/console: no such file
kernel panic: attempted to kill init
It boots ok with 2.4.19 homebuilt, kernel-image-2.4.18-686 from
stable,and 2.2.20 from stable, that follows from install.
Im also including my lilo.conf.
Hope you can help
Thanks
Kenneth
> Debian GNU/Linux 3.0 is out! ( http://www.debian.org/ )
> Email: Herbert Xu ~{PmV>HI~} <herbert@gondor.apana.org.au>
> Home Page: http://gondor.apana.org.au/~herbert/
> PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
# /etc/lilo.conf - See: `lilo(8)' and `lilo.conf(5)',
# --------------- `install-mbr(8)', `/usr/share/doc/lilo/',
# and `/usr/share/doc/mbr/'.
# +---------------------------------------------------------------+
# | !! Reminder !! |
# | |
# | Don't forget to run `lilo' after you make changes to this |
# | conffile, `/boot/bootmess.txt', or install a new kernel. The |
# | computer will most likely fail to boot if a kernel-image |
# | post-install script or you don't remember to run `lilo'. |
# | |
# +---------------------------------------------------------------+
# Support LBA for large hard disks.
#
lba32
# Overrides the default mapping between harddisk names and the BIOS'
# harddisk order. Use with caution.
#disk=/dev/hde
# bios=0x81
#disk=/dev/sda
# bios=0x80
# Specifies the boot device. This is where Lilo installs its boot
# block. It can be either a partition, or the raw device, in which
# case it installs in the MBR, and will overwrite the current MBR.
#
boot=/dev/hda
# Specifies the device that should be mounted as root. (`/')
#
root=/dev/hdc6
# Enable map compaction:
# Tries to merge read requests for adjacent sectors into a single
# read request. This drastically reduces load time and keeps the
# map smaller. Using `compact' is especially recommended when
# booting from a floppy disk. It is disabled here by default
# because it doesn't always work.
#
# compact
# Installs the specified file as the new boot sector
# You have the choice between: bmp, compat, menu and text
# Look in /boot/ and in lilo.conf(5) manpage for details
#
#install=/boot/boot-menu.b
#linje over kommentert ut naar gikk til testing se /root/lilo.beskjed
install=menu
# Specifies the location of the map file
#
map=/boot/map
# You can set a password here, and uncomment the `restricted' lines
# in the image definitions below to make it so that a password must
# be typed to boot anything but a default configuration. If a
# command line is given, other than one specified by an `append'
# statement in `lilo.conf', the password will be required, but a
# standard default boot will not require one.
#
# This will, for instance, prevent anyone with access to the
# console from booting with something like `Linux init=/bin/sh',
# and thus becoming `root' without proper authorization.
#
# Note that if you really need this type of security, you will
# likely also want to use `install-mbr' to reconfigure the MBR
# program, as well as set up your BIOS to disallow booting from
# removable disk or CD-ROM, then put a password on getting into the
# BIOS configuration as well. Please RTFM `install-mbr(8)'.
#
# password=tatercounter2000
# Specifies the number of deciseconds (0.1 seconds) LILO should
# wait before booting the first image.
#
delay=100
# You can put a customized boot message up if you like. If you use
# `prompt', and this computer may need to reboot unattended, you
# must specify a `timeout', or it will sit there forever waiting
# for a keypress. `single-key' goes with the `alias' lines in the
# `image' configurations below. eg: You can press `1' to boot
# `Linux', `2' to boot `LinuxOLD', if you uncomment the `alias'.
#
# message=/boot/bootmess.txt
# prompt
# single-key
# delay=100
# timeout=100
# Specifies the VGA text mode at boot time. (normal, extended, ask, <mode>)
#
vga=ask
# vga=9
#
#vga=normal
# Kernel command line options that apply to all installed images go
# here. See: The `boot-prompt-HOWO' and `kernel-parameters.txt' in
# the Linux kernel `Documentation' directory.
#
# append=""
append=" hdb=ide-scsi hdd=ide-scsi"
# Boot up Linux by default.
#
default=Egen
image=/vmlinuz.2.4.19.egen
label=Egen
read-only
# initrd=/initrd.img
# restricted
# alias=1
image=/vmlinuz
label=Linux
read-only
initrd=/initrd.img
# restricted
# alias=1
image=/vmlinuz-2.4.18-686
label=Linux-2.4.18
read-only
initrd=/initrd.img-2.4.18-686
image=/vmlinuz-2.2.20
label=Linux-2.2.20
read-only
optional
# restricted
# alias=2
# If you have another OS on this machine to boot, you can uncomment the
# following lines, changing the device name on the `other' line to
# where your other OS' partition is.
#
other=/dev/hda1
label=xp
# restricted
# alias=3
Reply to: