Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#4381 - kernel panic VFS unknown-block(0,0)

Attached to Project: Arch Linux
Opened by Andrew Simmons (Wolfman) - Wednesday, 05 April 2006, 17:02 GMT
Last edited by Judd Vinet (judd) - Wednesday, 05 April 2006, 17:49 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7.1 Noodle
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I installed the stock kernel26-2.6.16-5 last night, and I got the above kernel panic (VFS: unknown-block(0,0)). I have been using archck for a while, so I checked my mkinitrd.conf against my mkinitramfs.conf. Also, I checked my menu.lst for errors. After checking the forums, it seems alot of people have this problem, and after googling for a few minutes, it looks like the kernel is barfing on mounting the initrd. I decided to try installing an initramfs, which worked, and I am now running on the latest kernel26. I don't know what's wrong with my initrd, but it looks like a common enough problem to warrent a bug report, especially since it's the default ramdisk for kernel26.
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Saturday, 08 April 2006, 06:13 GMT
Reason for closing:  Not a bug
Comment by Judd Vinet (judd) - Wednesday, 05 April 2006, 17:49 GMT
Tpowa, is the init ramdisk size set properly in the latest kernel? Should be 16mb.
Comment by Andrew Simmons (Wolfman) - Wednesday, 05 April 2006, 18:38 GMT
$ cat kconfig26 | grep RAM
CONFIG_INITRAMFS_SOURCE=""
# CONFIG_HOTPLUG_PCI_COMPAQ_NVRAM is not set
CONFIG_TEKRAM_DONGLE=m
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=16384
# CONFIG_HOSTAP_FIRMWARE_NVRAM is not set
CONFIG_NVRAM=m
CONFIG_FRAMEBUFFER_CONSOLE=y
# CONFIG_FRAMEBUFFER_CONSOLE_ROTATION is not set
CONFIG_RAMFS=y
CONFIG_CRAMFS=m
# CONFIG_FRAME_POINTER is not set
CONFIG_X86_TRAMPOLINE=y

It appears to be set correctly (16384=16*1024).
Comment by Tobias Powalowski (tpowa) - Thursday, 06 April 2006, 06:23 GMT
hmm was your /boot not mounted while mkinitrd created your initrd?
mkinitrd checks the size if it is ok, kernel didn't changed in this part for ages.
Comment by Aaron Griffin (phrakture) - Thursday, 06 April 2006, 07:08 GMT
unknown-block(0,0) is a filesystem error - I'm going to assume your filesystem module is not loaded (perhaps it's not in your initrd).
Comment by Andrew Simmons (Wolfman) - Thursday, 06 April 2006, 07:58 GMT
Tpowa, my boot partition is always mounted, so that's not a problem.
Phrakture, I diffed the rd and ramfs config files, and all the differences involve archck features.
I also built a new initrd while running 2.6.16-ARCH, mounted it, and found the ext2 and ext3 drivers in /lib. I then tried rebooting with that initrd and had the same problem. Also the lines before the kernel panic look like the following.

Find and initialize a bunch of hardware
...
Found Initial Ramdisk at BLOCK 0
VFS: can not mount root device at unknown-block(0,0)

The system just hangs at that point, until i press the restart or power button.

Simply switching the initrd image with an identical initramfs image lets me boot into a perfectly working OS. This leads me to believe that something is wrong with the initrds on my system. Also, I can not say if any initrds have worked in the past, since I have been using archck before the transition to using initrds.
Comment by Tobias Powalowski (tpowa) - Thursday, 06 April 2006, 08:04 GMT
just out of interest, do you have ext2 as module???
ext2 must be in kernel if initrd should be used
Comment by Andrew Simmons (Wolfman) - Thursday, 06 April 2006, 17:35 GMT
That could be a problem with the kernel I compiled. I was not aware that I needed ext2 in the kernel. However, I tried installing the stock kernel from current, and I could not get it to work with an initrd.
Comment by Jan de Groot (JGC) - Thursday, 06 April 2006, 22:03 GMT
Hmm, this caught me the first time also when switching to a stock kernel: my home-made kernel didn't have ext2 support, so my kernel couldn't generate a correct initrd image.
Comment by Tobias Powalowski (tpowa) - Friday, 07 April 2006, 07:12 GMT
just an other question what fs is your root?
Comment by Andrew Simmons (Wolfman) - Friday, 07 April 2006, 09:05 GMT
I use ext3 for my root fs.
Comment by Tobias Powalowski (tpowa) - Friday, 07 April 2006, 10:29 GMT
ok, what does: mkinitrd auto -show give you?
Comment by Andrew Simmons (Wolfman) - Friday, 07 April 2006, 23:24 GMT
Since I installed the new stock kernel, everything seems to be working now.
   mkinitrd.txt (0.3 KiB)

Loading...