[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: VFS: Cannot open root device 2141 ... Kernelpanic: VFS: Unable to mount root fs on unk-blk(33,65)



Gayle Lee Fairless wrote:

On Thu, 23 Jun 2005, Debian User Leonard Chatagnier wrote:

Gayle Lee Fairless wrote:

I just upgraded from the 2.4.18bf2.4 kernel, now LinuxOLD on my LILO menu, to the 2.6.8 .... 686 kernel available from sarge. Unfortunately the 2.6 kernel gives me the following panic:

VFS: Cannot open root device 2141 or unknown-block(33,65)
Please append a correct "root=" boot option

Kernelpanic: VFS: Unable to mount root fs on unknown-block(33,65)

The computer is a Gateway 500 with a Pentium III at 500 MHZ. I looked through the man pages for lilo.conf, syslog, and a few others. I also looked at the source, somewhat briefly, of course, for any special options for 2.6 kernels that I needed to put into the lilo.conf file. (I've also downloaded the source code for the 2.6.8 kernel.) The bf2.4 kernel works fine. However, both the 2.4.16-686 and the 2.6.8-2-686 kernels will panic. I'm only concerned about booting and using the 2.6 kernel, of course.

  I am subscribed to the list, but CC's are fine.

What options or docs did I miss? Hopefully, it's just a change to my lilo.conf file? Although my boot drive is /dev/hde, my root for Linux is on /dev/hdf1 as you can see from the lilo.conf file. This Gateway 500 also has Window 98SE on it. I added a second hard drive and decided to put Debian GNU/Linux 3.0 (woody) on it.

Thank you for any help giving or pointing me to the correct information!

This is my /boot directory:

gayle@Gcomm:~/docs$ cat bootdir.txt
total 12620
drwxr-xr-x   2 root    4096 Jun 23 10:03 .
drwxr-xr-x  24 root    4096 Jun 23 10:00 ..
-rw-r--r--   1 root  398501 Nov 27  2001 System.map-2.4.16-686
-rw-r--r--   1 root  559088 May 14  2004 System.map-2.4.18-bf2.4
-rw-r--r--   1 root  843026 May 19 04:27 System.map-2.6.8-2-686
-rw-r--r--   1 root     512 May 14  2004 boot.2100
-rw-r--r--   1 root     512 Jun 19 15:39 boot.2140
lrwxrwxrwx   1 root      11 May 14  2004 boot.b -> boot-menu.b
-rw-r--r--   1 root  308326 Jun 19 15:13 coffee.bmp
-rw-r--r--   1 root   34159 Nov 27  2001 config-2.4.16-686
-rw-r--r--   1 root   16984 May 14  2004 config-2.4.18-bf2.4
-rw-r--r--   1 root   55399 May 19 03:51 config-2.6.8-2-686
lrwxrwxrwx   1 root      15 Jun 19 15:13 debian.bmp -> /boot/sarge.bmp
-rw-r--r--   1 root  153720 Jun 19 15:13 debianlilo.bmp
-rw-r--r--   1 root 2682880 Apr 20 00:46 initrd.img-2.4.16-686
-rw-r--r--   1 root 4636672 Jun 23 10:00 initrd.img-2.6.8-2-686
-rw-------   1 root   42496 Jun 23 10:03 map
-rw-r--r--   1 root   23662 Jun 19 15:13 sarge.bmp
-rw-r--r--   1 root   24116 Jun 19 15:13 sid.bmp
-rw-r--r--   1 root  611285 Nov 27  2001 vmlinuz-2.4.16-686
-rw-r--r--   1 root 1263339 May 14  2004 vmlinuz-2.4.18-bf2.4
-rw-r--r--   1 root 1170965 May 19 04:27 vmlinuz-2.6.8-2-686
gayle@Gcomm:~/docs$

gayle@Gcomm:~/drivers$ cat lilo.conf
# /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=0x80

disk=/dev/hdf
bios=0x81

# 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/hde

# Specifies the device that should be mounted as root. (`/')
#
root=/dev/hdf1

# 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

# 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=20

# 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
timeout=150
#       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=""

# Boot up Linux by default.
#
#default=Linux
# Make menu 'wife-proof'
default=Windows(hde1)

image=/vmlinuz
      label=Linux
      read-only


	initrd=/initrd.img

	^^^^^^^^^^^^^^^^^^^^

This was probably the reason my 2.4 ... 686 kernel would also panic, but that doesn't matter, the bf2.4 works fine, and now the 2.6.8 kernel boots!



#       restricted
#       alias=1

image=/vmlinuz.old
      label=LinuxOLD
      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/hda4
#       label=HURD
#       restricted
#       alias=3
other=/dev/hde1
label="Windows(hde1)"

#other=/dev/hdf5
#  label="Linux(hdf5)"

#other=/dev/hdf6
#  label="Other(hdf6)"

#other=/dev/hdf7
#  label="Windows(hdf7)"

#other=/dev/hdf8
#  label="Linux(hdf8)"

#other=/dev/hdf9
#  label="Windows(hdf9)"

gayle@Gcomm:~/drivers$

  I also have the source code for 2.6.8-2-686.

gayle@Gcomm:/lib/modules/2.6.8-2-686$ ll
total 832
drwxr-xr-x   5 root   4096 Jun 23 10:00 .
drwxr-xr-x   6 root   4096 Jun 23 09:59 ..
drwxr-xr-x   2 root   4096 Jun 23 09:59 boot
lrwxrwxrwx 1 root 35 Jun 20 07:40 build -> /usr/src/kernel-headers-2.6.8-2-686
drwxr-xr-x   2 root   4096 Jun 23 09:59 initrd
drwxr-xr-x  10 root   4096 Jun 23 09:59 kernel
-rw-r--r--   1 root 138720 Jun 23 10:00 modules.alias
-rw-r--r--   1 root     69 Jun 23 10:00 modules.ccwmap
-rw-r--r--   1 root 233307 Jun 23 10:00 modules.dep
-rw-r--r--   1 root    517 Jun 23 10:00 modules.ieee1394map
-rw-r--r--   1 root   1061 Jun 23 10:00 modules.inputmap
-rw-r--r--   1 root  16427 Jun 23 10:00 modules.isapnpmap
-rw-r--r--   1 root 131958 Jun 23 10:00 modules.pcimap
-rw-r--r--   1 root 104901 Jun 23 10:00 modules.symbols
-rw-r--r--   1 root 157116 Jun 23 10:00 modules.usbmap
lrwxrwxrwx 1 root 100 Jun 23 09:59 source -> /home/horms/tmp/debian-kernel-test/kernel-image-2.6.8-i386/kernel-image-2.6.8-i386-2.6.8/install-686
gayle@Gcomm:/lib/modules/2.6.8-2-686$


Gayle, having had this problem before when I first installed a sarge kernel, I see 2 things wrong in your lilo.conf file. Both sarge kernels are initrd images and you need an initrd= and root= entries in your image=/vmlinuz. I'm having the same problem on my stable dist-upgrade and wasn't able to fix it. I seem to have a corrupt swap partition having /Solaris on it. All newbie debian config issues, I think. I have a link on my root partition, initrd.img -> boot/initrd.img-2.4.27-2-386, and believe all I need is initrd=initrd.img. Look at your / partition and if you have the link try the above as you probably don't have my other issues. Any way, if it doesn't work your no worse off and some of the gurus are bound to read this and correct me if I'm wrong. You'll find what I'm talking about in the image= examples in lilo.conf. Good luck and hope this helps.

Leonard Chatagnier, a highly experience newbie who still doesn,t know anything about Debian

You're right. I put initrd-/initrd.img where max(sp?) suggested when he replied.

I now have a 2.6.8-2-686 kernel that works. I now have to do some fine tuning. Fox example, I got rid of the isdn stuff that I don't have on the computer; however, removing the .kde and .kderc as suggested to you did not work for me, perhaps because I never reinstalled. This system is now a sarge system upgraded from woody, period!

On bit of good news! I noticed that snd-ens1371 is now being installed so I may be closer to getting my sound system working withy ALSA. I was looking back in my notes for the stuff someone said about unmuting the alsamixer and then saving it.

Unfortuately, I'm going to have time out to attend a funeral visitiation. But that's OT.

	I just noticed that you sent another message so this may be OBE.

(Mr.) Gayle Lee Fairless




Gayle, glad to hear it works as it means my config is ok and I have other issues. About sound, all the mixer defaults have muted volume, at least mine did. Just find your favorite mixer, gamix, etc., I used kmix this time, and adjust everything appropriately(80-90%) and you should be in business. On my latest woody reinstall I just used kmix and had sound already enabled. Regarding kde, I didn't have to reinstall, just get rid of .kde/* and kderc and relogin, that's all. However, a dist-upgrade should pick up all of kde; it did for me at least and I did just that prior to removing the above.
Good luck as I see we're having the same issues for the most part.

Leonard



Reply to: