You are not logged in.

Pages: 1

#1 2011-08-08 03:33:31

dcecile
Member
From: Canada
Registered: 2011-08-08
Posts: 14
Website

[SOLVED] Kernel panic at boot due to root FS not found

When I try to boot using a new kernel version (eg. 3.0.1 or 2.6.39), I get a kernel panic with an "init not found" error message. I haven't been able to get any more detailed error messages, but I assume that there's a problem with finding or mounting my root filesystem.

For now, I'm stuck with 2.6.38.7-1, which boots without any problems. (I keep trying the new kernel, then rolling it back using a Live CD.)

I have a shared EXT4 root and boot partition, and I'm using Grub 0.97. Other than that, I'm not sure what information would be helpful in tracking down this problem, and any help would be appreciated.

Last edited by dcecile (2011-08-10 00:41:46)

Offline

#2 2011-08-08 04:44:46

nixpunk
Member
Registered: 2009-11-23
Posts: 271

Re: [SOLVED] Kernel panic at boot due to root FS not found

http://www.archlinux.org/news/changes-t … filenames/

Also, make sure initrd is pointing to the correct image in menu.lst.

Last edited by nixpunk (2011-08-08 04:48:33)

Offline

#3 2011-08-08 11:21:55

dcecile
Member
From: Canada
Registered: 2011-08-08
Posts: 14
Website

Re: [SOLVED] Kernel panic at boot due to root FS not found

I cleaned up my Grub to use the files (instead of the symlinks), but I got the same error. Here's the Grub entry:

title  Arch Linux
root   (hd0,2)
kernel /boot/vmlinuz-linux root=/dev/sda3 ro panic=10
initrd /boot/initramfs-linux.img

Offline

#4 2011-08-08 11:30:13

karol
Archivist
Registered: 2009-05-06
Posts: 25,440

Re: [SOLVED] Kernel panic at boot due to root FS not found

Is 'root=/dev/sda3' correct? Do you have a separate /boot partition?
Can you paste the old menu.lst, the one that's working?

Offline

#5 2011-08-08 13:34:38

dcecile
Member
From: Canada
Registered: 2011-08-08
Posts: 14
Website

Re: [SOLVED] Kernel panic at boot due to root FS not found

Here's my current, working Grub entry:

title  Arch Linux
root   (hd0,2)
kernel /boot/vmlinuz26 root=/dev/sda3 ro panic=10
initrd /boot/kernel26.img

This works with 2.6.38, but strangely not with 2.6.39.

(Let me know if I should post the full menu.lst file.)

My boot and root are on the same EXT4 partition.

Offline

#6 2011-08-08 13:37:23

Inxsible
Forum Fellow
From: Chicago
Registered: 2008-06-09
Posts: 9,183

Re: [SOLVED] Kernel panic at boot due to root FS not found

Try using UUID instead of sda3 and see if that works for you.

Forum Rules

There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !

Offline

#7 2011-08-08 13:38:34

karol
Archivist
Registered: 2009-05-06
Posts: 25,440

Re: [SOLVED] Kernel panic at boot due to root FS not found

Inxsible wrote:

Try using UUID instead of sda3 and see if that works for you.

+1
https://wiki.archlinux.org/index.php/Pe … ice_naming

Although I'm wondering why .39 doesn't work for you ...

Offline

#8 2011-08-08 13:57:01

dcecile
Member
From: Canada
Registered: 2011-08-08
Posts: 14
Website

Re: [SOLVED] Kernel panic at boot due to root FS not found

Inxsible wrote:

Try using UUID instead of sda3 and see if that works for you.

Using a UUID didn't work for 2.6.39, but I haven't tried it yet for 3.0. I'll give it a shot this evening, and report back.

Offline

#9 2011-08-08 23:01:54

dcecile
Member
From: Canada
Registered: 2011-08-08
Posts: 14
Website

Re: [SOLVED] Kernel panic at boot due to root FS not found

dcecile wrote:
Inxsible wrote:

Try using UUID instead of sda3 and see if that works for you.

Using a UUID didn't work for 2.6.39, but I haven't tried it yet for 3.0. I'll give it a shot this evening, and report back.

UUID doesn't help for the 3.0 kernel. It gives the same "init not found" error.

Offline

#10 2011-08-09 00:24:29

oboedad55
Member
From: Baku
Registered: 2011-04-05
Posts: 392

Re: [SOLVED] Kernel panic at boot due to root FS not found

Are you sure about /sda2? Post the output of "fdisk -l".

Registered Linux user #436067

Offline

#11 2011-08-09 01:45:00

Fade
Member
Registered: 2008-06-27
Posts: 15

Re: [SOLVED] Kernel panic at boot due to root FS not found

There's been a lot of posts today regarding the same sort of thing regarding files not found or root devices not existing.

e.g. https://bbs.archlinux.org/viewtopic.php?id=124006
https://bbs.archlinux.org/viewtopic.php?id=124093

I have a feeling that they are all related however to this bug:

https://bugs.archlinux.org/task/25450?o … 885&status[0]=

as all the problems seem to be related to a faulty initramfs thingy. Feel free to correct me please as I only have the vaguest understanding of what's going on.

I have a similar issue. On boot with the normal kernel, it panics when udev tries to do its thing. The fallback kernel works fine. When I do I mkinitcpio -p linux, I get the same problem as indicated in the above bug. It says the image was generated successfully, but it LIES.

Offline

#12 2011-08-09 01:56:53

m4rcelo
Member
Registered: 2011-08-09
Posts: 1

Re: [SOLVED] Kernel panic at boot due to root FS not found

I'm running 2.6.39-ARCH. This is my grub entry:

 # (0) Arch Linux
title  Arch Linux
root   (hd0,1)
kernel /vmlinuz26 root=/dev/disk/by-uuid/0ed598aa-5102-444a-a773-ba79be23d7b6 ro
initrd /kernel26.img

Note that there is not "/boot" in kernel and initrd lines. ¿Could this be the reason?

Offline

#13 2011-08-09 02:17:22

lolilolicon
Member
Registered: 2009-03-05
Posts: 1,722

Re: [SOLVED] Kernel panic at boot due to root FS not found

dcecile wrote:
dcecile wrote:
Inxsible wrote:

Try using UUID instead of sda3 and see if that works for you.

Using a UUID didn't work for 2.6.39, but I haven't tried it yet for 3.0. I'll give it a shot this evening, and report back.

UUID doesn't help for the 3.0 kernel. It gives the same "init not found" error.

Does the same UUID work for your working kernel? Just to make sure you picked the right UUID, you know.

Edit: Also try explicitly adding ext4 to MODULES in /etc/mkinitcpio.conf and rebuild the initramfs.

Last edited by lolilolicon (2011-08-09 02:38:20)

This silver ladybug at line 28...

Offline

#14 2011-08-09 04:01:03

falconindy
Developer
From: New York, USA
Registered: 2009-10-22
Posts: 4,111
Website

Re: [SOLVED] Kernel panic at boot due to root FS not found

I'm going to assume the full error is "Root device mounted successfully, but /sbin/init does not exist." which means that you've got a healthy initramfs, but you're literally mounting the wrong device. Assuming you have a working keyboard at this point when you're dropped into the recovery shell, feel free to "ls /new_root" and see what did get mounted. Whatever you're specifying for the root clearly isn't correct.

Last edited by falconindy (2011-08-09 04:01:30)

blog | ±github

Offline

#15 2011-08-09 05:02:21

dcecile
Member
From: Canada
Registered: 2011-08-08
Posts: 14
Website

Re: [SOLVED] Kernel panic at boot due to root FS not found

Thanks for all your suggestions, everyone. I'll try to reply here to each question...

oboedad55 wrote:

Are you sure about /sda2? Post the output of "fdisk -l".

Here's my "fdisk -l" (sda1 is Windows, sda2 is swap, sda3 is root, sda4 is home). Note, the same root= Grub parameter works for me on an old kernel, but not on a new one.

Disk /dev/sda: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x29133921

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *        2048   102402047    51200000    7  HPFS/NTFS/exFAT
/dev/sda2       102402048   104394107      996030   82  Linux swap / Solaris
/dev/sda3   *   104394108   143464187    19535040   83  Linux
/dev/sda4       143464188   488392064   172463938+  83  Linux
Fade wrote:

I have a similar issue. On boot with the normal kernel, it panics when udev tries to do its thing. The fallback kernel works fine. When I do I mkinitcpio -p linux, I get the same problem as indicated in the above bug. It says the image was generated successfully, but it LIES.

Unfortunately for me, the fallback kernel doesn't work. We may have separate issues.

m4rcelo wrote:

I'm running 2.6.39-ARCH. This is my grub entry:

 # (0) Arch Linux
title  Arch Linux
root   (hd0,1)
kernel /vmlinuz26 root=/dev/disk/by-uuid/0ed598aa-5102-444a-a773-ba79be23d7b6 ro
initrd /kernel26.img

Note that there is not "/boot" in kernel and initrd lines. ¿Could this be the reason?

I get a 'file not found' error from Grub if I try to take out the /boot parts. My root directory and my boot directory are on the same partition.

lolilolicon wrote:

Does the same UUID work for your working kernel? Just to make sure you picked the right UUID, you know.

Edit: Also try explicitly adding ext4 to MODULES in /etc/mkinitcpio.conf and rebuild the initramfs.

The same UUID works for the other kernel, so I know I didn't blunder there.

And I also tried putting ext4 into MODULES, but that didn't help either.

falconindy wrote:

I'm going to assume the full error is "Root device mounted successfully, but /sbin/init does not exist." which means that you've got a healthy initramfs, but you're literally mounting the wrong device. Assuming you have a working keyboard at this point when you're dropped into the recovery shell, feel free to "ls /new_root" and see what did get mounted. Whatever you're specifying for the root clearly isn't correct.

Sorry for not copying it down earlier; the full error is "Kernel panic - not syncing: No init found." I'm not convinced that my root device got mounted, because I get the exact same "No init found" error message when I misspell the root=/dev/disk/by-uuid/... parameter. By the way, I tried adding "rootwait break=y" to my Grub entry, but I didn't get a recovery shell.

It still seems to me like the new kernel can't find my partition, or it can't mount it. Is it possible that my ext4 partition is corrupt in some way?

Offline

#16 2011-08-09 11:43:53

falconindy
Developer
From: New York, USA
Registered: 2009-10-22
Posts: 4,111
Website

Re: [SOLVED] Kernel panic at boot due to root FS not found

This is why complete error messages are important, because I'm way off. If you can't even get a recovery shell, then it sounds like your initramfs isn't even being loaded.

blog | ±github

Offline

#17 2011-08-09 12:33:13

dcecile
Member
From: Canada
Registered: 2011-08-08
Posts: 14
Website

Re: [SOLVED] Kernel panic at boot due to root FS not found

Yeah, my bad. So if my initramfs isn't being loaded, then that means adding ext4 to MODULES and regenerating initramfs-linux.img certainly won't do anything.

Is there a way to make sure that the ext4 module gets put in the vmlinuz-linux file and loaded first thing?

Offline

#18 2011-08-09 12:46:28

falconindy
Developer
From: New York, USA
Registered: 2009-10-22
Posts: 4,111
Website

Re: [SOLVED] Kernel panic at boot due to root FS not found

How about fixing the real problem instead of looking at a kernel build? Post your bootloader config, for starters, and check that what's in your initramfs is actually sane (lsinitcpio /boot/initramfs-linux.img)

Last edited by falconindy (2011-08-09 12:46:40)

blog | ±github

Offline

#19 2011-08-09 13:00:51

dcecile
Member
From: Canada
Registered: 2011-08-08
Posts: 14
Website

Re: [SOLVED] Kernel panic at boot due to root FS not found

No problem.

Here's my full Grub. It has a lot of trial-and-error entries, and I made *-old copies of my 2.6.38 kernel files:

# Config file for GRUB - The GNU GRand Unified Bootloader
# /boot/grub/menu.lst

# DEVICE NAME CONVERSIONS 
#
#  Linux           Grub
# -------------------------
#  /dev/fd0        (fd0)
#  /dev/sda        (hd0)
#  /dev/sdb2       (hd1,1)
#  /dev/sda3       (hd0,2)
#

#  FRAMEBUFFER RESOLUTION SETTINGS
#     +-------------------------------------------------+
#          | 640x480    800x600    1024x768   1280x1024
#      ----+--------------------------------------------
#      256 | 0x301=769  0x303=771  0x305=773   0x307=775
#      32K | 0x310=784  0x313=787  0x316=790   0x319=793
#      64K | 0x311=785  0x314=788  0x317=791   0x31A=794
#      16M | 0x312=786  0x315=789  0x318=792   0x31B=795
#     +-------------------------------------------------+
#  for more details and different resolutions see
#  http://wiki.archlinux.org/index.php/GRUB#Framebuffer_Resolution 

# general configuration:
timeout   2
default   0
color light-blue/black light-cyan/blue

# boot sections follow
# each is implicitly numbered from 0 in the order of appearance below
#
# TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.
#
#-*

title  Arch Linux
root   (hd0,2)
kernel /boot/vmlinuz-linux root=/dev/disk/by-uuid/2ec8f74e-3268-45d0-ae20-9ee94d1c983b ro panic=30 vga=0x318
initrd /boot/initramfs-linux.img

title  Arch Linux Fallback
root   (hd0,2)
kernel /boot/vmlinuz-linux root=/dev/disk/by-uuid/2ec8f74e-3268-45d0-ae20-9ee94d1c983b ro panic=30 vga=0x318
initrd /boot/initramfs-linux-fallback.img

title  Arch Linux Ext4
root   (hd0,2)
kernel /boot/vmlinuz-linux root=/dev/disk/by-uuid/2ec8f74e-3268-45d0-ae20-9ee94d1c983b ro panic=30 vga=0x318
initrd /boot/initramfs-linux-ext4.img

title  Arch Linux Log
root   (hd0,2)
kernel /boot/vmlinuz-linux root=/dev/disk/by-uuid/2ec8f74e-3268-45d0-ae20-9ee94d1c983b ro debug rootdelay=5 panic=30 ignore_loglevel vga=0x318
initrd /boot/initramfs-linux.img

title  Arch Linux Break
root   (hd0,2)
kernel /boot/vmlinuz-linux root=/dev/disk/by-uuid/2ec8f74e-3268-45d0-ae20-9ee94d1c983b ro rootwait break=y panic=30 vga=0x318
initrd /boot/initramfs-linux.img

title  Arch Linux Nonboot Log
root   (hd0,2)
kernel /vmlinuz-linux root=/dev/disk/by-uuid/2ec8f74e-3268-45d0-ae20-9ee94d1c983b ro debug rootdelay=5 panic=30 ignore_loglevel vga=0x318
initrd /initramfs-linux.img

title  Arch Linux Baduuid Log
root   (hd0,2)
kernel /boot/vmlinuz-linux root=/dev/disk/by-uuid/1ec8f74e-3268-45d0-ae20-9ee94d1c983b ro debug rootdelay=5 panic=30 ignore_loglevel vga=0x318
initrd /boot/initramfs-linux.img

title  Arch Linux LTS
root   (hd0,2)
kernel /boot/vmlinuz26-lts root=/dev/disk/by-uuid/2ec8f74e-3268-45d0-ae20-9ee94d1c983b ro panic=30 vga=0x318
initrd /boot/kernel26-lts.img

title  Arch Linux LTS Fallback
root   (hd0,2)
kernel /boot/vmlinuz26-lts root=/dev/disk/by-uuid/2ec8f74e-3268-45d0-ae20-9ee94d1c983b ro panic=30 vga=0x318
initrd /boot/kernel26-lts-fallback.img

title  Arch Linux LTS Log
root   (hd0,2)
kernel /boot/vmlinuz26-lts root=/dev/disk/by-uuid/2ec8f74e-3268-45d0-ae20-9ee94d1c983b ro debug rootdelay=5 panic=30 ignore_loglevel vga=0x318
initrd /boot/kernel26-lts.img

title  Arch Linux Old
root   (hd0,2)
kernel /boot/vmlinuz26-old root=/dev/disk/by-uuid/2ec8f74e-3268-45d0-ae20-9ee94d1c983b ro panic=30 vga=0x318
initrd /boot/kernel26-old.img

title  Arch Linux Old Fallback
root   (hd0,2)
kernel /boot/vmlinuz26-old root=/dev/disk/by-uuid/2ec8f74e-3268-45d0-ae20-9ee94d1c983b ro panic=30 vga=0x318
initrd /boot/kernel26-old-fallback.img

title  Arch Linux Old Log
root   (hd0,2)
kernel /boot/vmlinuz26-old root=/dev/disk/by-uuid/2ec8f74e-3268-45d0-ae20-9ee94d1c983b ro debug rootdelay=5 panic=30 ignore_loglevel vga=0x318
initrd /boot/kernel26-old.img

title Windows
rootnoverify (hd0,0)
makeactive
chainloader +1

This is the 3.0 entry that doesn't work:

title  Arch Linux
root   (hd0,2)
kernel /boot/vmlinuz-linux root=/dev/disk/by-uuid/2ec8f74e-3268-45d0-ae20-9ee94d1c983b ro panic=30 vga=0x318
initrd /boot/initramfs-linux.img

And this is the 2.6.38 entry that does work:

title  Arch Linux Old
root   (hd0,2)
kernel /boot/vmlinuz26-old root=/dev/disk/by-uuid/2ec8f74e-3268-45d0-ae20-9ee94d1c983b ro panic=30 vga=0x318
initrd /boot/kernel26-old.img

Here's "lsinitcpio /boot/initramfs-linux.img":

.
./etc
./etc/udev
./etc/udev/udev.conf
./etc/modprobe.d
./etc/modprobe.d/usb-load-ehci-first.conf
./init
./init_functions
./bin
./bin/busybox
./sys
./proc
./dev
./hooks
./hooks/udev
./run
./config
./usr
./usr/bin
./usr/sbin
./lib
./lib/udev
./lib/udev/usb_id
./lib/udev/firmware
./lib/udev/scsi_id
./lib/udev/path_id
./lib/udev/ata_id
./lib/udev/rules.d
./lib/udev/rules.d/50-udev-default.rules
./lib/udev/rules.d/80-drivers.rules
./lib/udev/rules.d/50-firmware.rules
./lib/udev/rules.d/60-persistent-storage.rules
./lib/modules
./lib/modules/3.0-ARCH
./lib/modules/3.0-ARCH/modules.alias.bin
./lib/modules/3.0-ARCH/modules.symbols.bin
./lib/modules/3.0-ARCH/kernel
./lib/modules/3.0-ARCH/kernel/fs
./lib/modules/3.0-ARCH/kernel/fs/ext4
./lib/modules/3.0-ARCH/kernel/fs/ext4/ext4.ko.gz
./lib/modules/3.0-ARCH/kernel/fs/mbcache.ko.gz
./lib/modules/3.0-ARCH/kernel/fs/jbd2
./lib/modules/3.0-ARCH/kernel/fs/jbd2/jbd2.ko.gz
./lib/modules/3.0-ARCH/kernel/sound
./lib/modules/3.0-ARCH/kernel/sound/core
./lib/modules/3.0-ARCH/kernel/sound/core/seq
./lib/modules/3.0-ARCH/kernel/sound/core/seq/snd-seq-device.ko.gz
./lib/modules/3.0-ARCH/kernel/sound/core/snd.ko.gz
./lib/modules/3.0-ARCH/kernel/sound/core/snd-rawmidi.ko.gz
./lib/modules/3.0-ARCH/kernel/sound/soundcore.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers
./lib/modules/3.0-ARCH/kernel/drivers/ata
./lib/modules/3.0-ARCH/kernel/drivers/ata/libata.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/ata/ahci.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/ata/libahci.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/usb
./lib/modules/3.0-ARCH/kernel/drivers/usb/core
./lib/modules/3.0-ARCH/kernel/drivers/usb/core/usbcore.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/usb/host
./lib/modules/3.0-ARCH/kernel/drivers/usb/host/uhci-hcd.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/usb/host/ehci-hcd.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/video
./lib/modules/3.0-ARCH/kernel/drivers/video/backlight
./lib/modules/3.0-ARCH/kernel/drivers/video/backlight/lcd.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/video/fb_sys_fops.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/video/sysimgblt.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/video/syscopyarea.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/video/sysfillrect.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/input
./lib/modules/3.0-ARCH/kernel/drivers/input/ff-memless.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/scsi
./lib/modules/3.0-ARCH/kernel/drivers/scsi/sd_mod.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/scsi/scsi_mod.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-ezkey.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-sjoy.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-gyration.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-samsung.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-roccat.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-lcpower.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-kye.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-dr.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-wacom.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-keytouch.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-uclogic.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-cherry.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-roccat-kovaplus.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-zpff.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-elecom.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-roccat-common.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-roccat-arvo.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-waltop.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-roccat-pyra.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-picolcd.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-twinhan.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-emsff.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-sunplus.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-apple.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-topseed.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-chicony.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-magicmouse.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-cypress.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-kensington.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-roccat-kone.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-axff.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-multitouch.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-logitech.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-petalynx.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-prodikeys.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/usbhid
./lib/modules/3.0-ARCH/kernel/drivers/hid/usbhid/usbhid.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-sony.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-zydacron.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-roccat-koneplus.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-gaff.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-microsoft.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-monterey.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-ntrig.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-belkin.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-pl.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-a4tech.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-ortek.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-quanta.ko.gz
./lib/modules/3.0-ARCH/kernel/drivers/hid/hid-tmff.ko.gz
./lib/modules/3.0-ARCH/kernel/lib
./lib/modules/3.0-ARCH/kernel/lib/crc16.ko.gz
./lib/modules/3.0-ARCH/modules.dep.bin
./sbin
./sbin/blkid
./sbin/udevadm
./sbin/modprobe
./sbin/udevd

Offline

#20 2011-08-09 13:31:28

falconindy
Developer
From: New York, USA
Registered: 2009-10-22
Posts: 4,111
Website

Re: [SOLVED] Kernel panic at boot due to root FS not found

That initramfs is fubar. There's no libc or loader (or any libraries at all for that matter). init is found, but there's no way for the kernel to execute it because there's no way to load busybox. You'll need to chroot to your install (make sure to bind mount /proc, /sys and /dev), and regenerate the image:

mkinitcpio -v -p linux

Post the output here.

Last edited by falconindy (2011-08-09 13:40:02)

blog | ±github

Offline

#21 2011-08-09 18:43:31

pzdmrd
Member
From: Dublin
Registered: 2010-03-12
Posts: 9

Re: [SOLVED] Kernel panic at boot due to root FS not found

Hi
I had a similar problem after upgrading to ARCH-3.0 for an external usb HD.
The initramdisk resulted in missing usb kernel modules so that the external HD could not be probed for root filesystem.

To fix the problem i followed these steps

- booted the recovery system from CD and mounted my filesystems:

   mount /dev/sdc4 /mnt/
   mount /dev/sdc3 /mnt/boot

- bound the special filsystems:

   mount -o bind /dev /mnt/dev
   mount -o bind /dev/pts /mnt/dev/pts
   mount -o bind /proc /mnt/proc
   mount -o bind /sys /mnt/sys

- chroot /mnt

- added usb hook in /etc/mkinitcpio.conf :

   HOOKS="base udev usb autodetect pata scsi sata filesystems usbinput"

- regenerate the initramdisk:

   mkinicpio -v -p linux
  (or uninstall and re-install linux package via pacman)

- verify the initramdisk image is correctly generated

- exit and reboot

That fixed the problem

Offline

#22 2011-08-09 21:44:19

dcecile
Member
From: Canada
Registered: 2011-08-08
Posts: 14
Website

Re: [SOLVED] Kernel panic at boot due to root FS not found

falconindy wrote:

That initramfs is fubar. There's no libc or loader (or any libraries at all for that matter). init is found, but there's no way for the kernel to execute it because there's no way to load busybox. You'll need to chroot to your install (make sure to bind mount /proc, /sys and /dev), and regenerate the image:

mkinitcpio -v -p linux

Post the output here.

big_smile Thanks a lot, that solved my problem. Running mkinitcpio while in a chroot (from a live CD) generated a good initramfs, and now I'm able to boot using the newer kernel.

Here's the log from mkinitcpio:

==> Building image from preset: 'default'
  -> -v -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 3.0-ARCH
  -> Parsing hook: [base]
    adding dir: /proc
    adding dir: /sys
    adding dir: /dev
    adding dir: /run
    adding dir: //usr/bin
    adding dir: //usr/sbin
    adding file: /bin/busybox
    adding dir: /lib
    adding symlink: /lib/libc-2.14.so -> /lib/libc.so.6
    adding file: /lib/libc-2.14.so
    adding symlink: /lib/ld-2.14.so -> /lib/ld-linux-x86-64.so.2
    adding file: /lib/ld-2.14.so
    adding file: /sbin/modprobe
    adding file: /sbin/blkid
    adding symlink: /lib/libblkid.so.1.1.0 -> /lib/libblkid.so.1
    adding file: /lib/libblkid.so.1.1.0
    adding symlink: /lib/libuuid.so.1.3.0 -> /lib/libuuid.so.1
    adding file: /lib/libuuid.so.1.3.0
    adding file: /init_functions
    adding file: /init
    adding file: /etc/modprobe.d/usb-load-ehci-first.conf
  -> Parsing hook: [udev]
    adding file: /sbin/udevd
    adding symlink: /lib/librt-2.14.so -> /lib/librt.so.1
    adding file: /lib/librt-2.14.so
    adding symlink: /lib/libpthread-2.14.so -> /lib/libpthread.so.0
    adding file: /lib/libpthread-2.14.so
    adding file: /sbin/udevadm
    adding file: /lib/udev/rules.d/50-firmware.rules
    adding file: /lib/udev/rules.d/50-udev-default.rules
    adding file: /lib/udev/rules.d/60-persistent-storage.rules
    adding file: /lib/udev/rules.d/80-drivers.rules
    adding file: /lib/udev/firmware
    adding file: /lib/udev/ata_id
    adding file: /lib/udev/path_id
    adding file: /lib/udev/scsi_id
    adding file: /lib/udev/usb_id
    adding file: /etc/udev/udev.conf
    adding file: /hooks/udev
  -> Parsing hook: [autodetect]
  -> Parsing hook: [pata]
  -> Parsing hook: [scsi]
  -> Parsing hook: [sata]
  -> Parsing hook: [filesystems]
  -> Parsing hook: [usbinput]
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux.img
==> Image generation successful
==> Building image from preset: 'fallback'
  -> -v -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 3.0-ARCH
  -> Parsing hook: [base]
    adding dir: /proc
    adding dir: /sys
    adding dir: /dev
    adding dir: /run
    adding dir: //usr/bin
    adding dir: //usr/sbin
    adding file: /bin/busybox
    adding dir: /lib
    adding symlink: /lib/libc-2.14.so -> /lib/libc.so.6
    adding file: /lib/libc-2.14.so
    adding symlink: /lib/ld-2.14.so -> /lib/ld-linux-x86-64.so.2
    adding file: /lib/ld-2.14.so
    adding file: /sbin/modprobe
    adding file: /sbin/blkid
    adding symlink: /lib/libblkid.so.1.1.0 -> /lib/libblkid.so.1
    adding file: /lib/libblkid.so.1.1.0
    adding symlink: /lib/libuuid.so.1.3.0 -> /lib/libuuid.so.1
    adding file: /lib/libuuid.so.1.3.0
    adding file: /init_functions
    adding file: /init
    adding file: /etc/modprobe.d/usb-load-ehci-first.conf
  -> Parsing hook: [udev]
    adding file: /sbin/udevd
    adding symlink: /lib/librt-2.14.so -> /lib/librt.so.1
    adding file: /lib/librt-2.14.so
    adding symlink: /lib/libpthread-2.14.so -> /lib/libpthread.so.0
    adding file: /lib/libpthread-2.14.so
    adding file: /sbin/udevadm
    adding file: /lib/udev/rules.d/50-firmware.rules
    adding file: /lib/udev/rules.d/50-udev-default.rules
    adding file: /lib/udev/rules.d/60-persistent-storage.rules
    adding file: /lib/udev/rules.d/80-drivers.rules
    adding file: /lib/udev/firmware
    adding file: /lib/udev/ata_id
    adding file: /lib/udev/path_id
    adding file: /lib/udev/scsi_id
    adding file: /lib/udev/usb_id
    adding file: /etc/udev/udev.conf
    adding file: /hooks/udev
  -> Parsing hook: [pata]
  -> Parsing hook: [scsi]
    adding file: /lib/firmware/cxgb4/t4fw.bin
    adding file: /lib/firmware/cxgb3/ael2020_twx_edc.bin
    adding file: /lib/firmware/cxgb3/ael2005_twx_edc.bin
    adding file: /lib/firmware/cxgb3/ael2005_opt_edc.bin
    adding file: /lib/firmware/cxgb3/t3c_psram-1.1.0.bin
    adding file: /lib/firmware/cxgb3/t3b_psram-1.1.0.bin
    adding file: /lib/firmware/cxgb3/t3fw-7.10.0.bin
    adding file: /lib/firmware/ql2500_fw.bin
    adding file: /lib/firmware/ql2400_fw.bin
    adding file: /lib/firmware/ql2322_fw.bin
    adding file: /lib/firmware/ql2300_fw.bin
    adding file: /lib/firmware/ql2200_fw.bin
    adding file: /lib/firmware/ql2100_fw.bin
    adding file: /lib/firmware/advansys/38C1600.bin
    adding file: /lib/firmware/advansys/38C0800.bin
    adding file: /lib/firmware/advansys/3550.bin
    adding file: /lib/firmware/advansys/mcode.bin
    adding file: /lib/firmware/qlogic/12160.bin
    adding file: /lib/firmware/qlogic/1280.bin
    adding file: /lib/firmware/qlogic/1040.bin
  -> Parsing hook: [sata]
  -> Parsing hook: [filesystems]
  -> Parsing hook: [usbinput]
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful

Again, thanks for all your help, everyone.

Offline

#23 2011-08-09 23:00:11

Inxsible
Forum Fellow
From: Chicago
Registered: 2008-06-09
Posts: 9,183

Re: [SOLVED] Kernel panic at boot due to root FS not found

please mark the thread as solved by editing first post and prepending [SOLVED] to the title

Forum Rules

There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !

Offline

Pages: 1

Board footer

Powered by FluxBB