kernel panic after pkgs upgrade

eduac · 2006-10-06 20:43:09

Hi all,

I do a global update today (pacman -Syu) and after a reboot he freezes on the boot with this error message:

No filesystem could mount root, tried:
Kernel panic - no syncing: VFS: Unable to mount fs on unknown-block (3,1)

before the complete reboot, i see that cant umount / partition...

anyone can help me please?

phrakture · 2006-10-06 20:45:26

Moved to the kernel forum.

Please try using the kernel26-fallback.img initrd image. Further more, I recommend checking out the mkinitcpio wiki:
http://wiki.archlinux.org/index.php/Mkinitcpio

eduac · 2006-10-08 14:41:27

phrakture wrote:

Moved to the kernel forum.
Please try using the kernel26-fallback.img initrd image. Further more, I recommend checking out the mkinitcpio wiki:
http://wiki.archlinux.org/index.php/Mkinitcpio

why i should have to check the mkinitcpio wiki?

toxic · 2006-10-08 15:52:49

By the looks of it, your latest sys upgrade upgraded mkinitcpio and rewrote it's config file. So likely you can just fix this problem by adding filesystems hook in mkinitcpio.conf.

eduac · 2006-10-08 15:56:20

toxic wrote:

By the looks of it, your latest sys upgrade upgraded mkinitcpio and rewrote it's config file. So likely you can just fix this problem by adding filesystems hook in mkinitcpio.conf.

HOOKS="base udev autodetect ide scsi sata filesystems"

fk · 2006-10-08 16:10:10

Add the Module for the Filesystem and the controller in the modules Array, its the first in mkinitcpio.conf

e.g MODULES="piix ext3"

then you must rebuild the mkinitcpio

eduac · 2006-10-08 16:13:11

fk wrote:

Add the Module for the Filesystem and the controller in the modules Array, its the first in mkinitcpio.conf
e.g MODULES="piix ext3"

then you must rebuild the mkinitcpio

After that i must do: mkinitcpio -g /boot/kernel26.img ????

fk · 2006-10-08 16:14:39

eduac wrote:

fk wrote:
Add the Module for the Filesystem and the controller in the modules Array, its the first in mkinitcpio.conf
e.g MODULES="piix ext3"

then you must rebuild the mkinitcpio
After that i must do: mkinitcpio -g /boot/kernel26.img ????

if you are do this from the live cd or so, you must

mkinitcpio -g /boot/kernel26.img -k 2.6.18-ARCH

eduac · 2006-10-08 16:17:39

nops...im not on live cd, im in the my arch desktop

eduac · 2006-10-08 18:18:45

I have another doubt... where I must put this line? (disablemodules=foo,foo1) which file?

toxic · 2006-10-08 18:37:57

eduac wrote:

I have another doubt... where I must put this line? (disablemodules=foo,foo1) which file?

To the kernel commandline. You can edit this permanently in /boot/grub/menu.lst or you can add it during boot time by pressing 'e' when the grub-boot screen appears. Then you can just type disablemodules... on the kernel commandline.

Convergence · 2006-10-09 07:51:59

Eduac: Please let me know if this worked for you. I've had the same problem. I'm actually using a different distro temporarily.

tarellel · 2006-10-13 16:09:07

I have been experiencing this problem as well with the newest full update. I ended up retrying about 100 different techniques over 2 days. And the one thing I never though of doing was changing my kernel after the patch.
If your using GRUB you can change it in /boot/grub/menu.lst
I changed it from initrd26.img to kernel26.img and now it works as perfect as before.
*shakes head* It helps to pay attention to the messages when updating, this time I learned my lesson.

martti1 · 2006-10-14 20:31:51

I installed Arch-0.7.2-base today, did sysupgrade and I'm getting the "Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block (0,0)".
I'm using grub.
What I did:
Before rebooting I edited /etc/fstab to use /dev/discs/..
After I got the error I did what was written in this thread:
1. Edited mkinitcpio.conf and added piix and ext3 to MODULES. HOOKS was already looking fine.
2. mkinitcpio -g /boot/kernel26.img -k 2.6.18-ARCH

Still the same error, have I missed something?

edit: Read mkinitcpio wiki, edited grub.conf to use kernel26.img instead of initrd26.img. When I booted arch it told me to specify the rootfstype kernel parameter, so i did. Now i get this: image

edit2: I modified mkinitcpio.conf again and removed autodetect from HOOKS and created a new kernel26.img, now the system boots fine and everything seems to work. Just one question. In /dev, i still see devices like hda1 hdb1 etc. I thought it was /dev/discs/disc1 and such in udev? I mean I changed fstab for udev and I had to change it back to normal, cause it didn't boot.

byte · 2006-10-15 08:13:15

martti1 wrote:

Just one question. In /dev, i still see devices like hda1 hdb1 etc. I thought it was /dev/discs/disc1 and such in udev? I mean I changed fstab for udev and I had to change it back to normal, cause it didn't boot.

/dev/discs/... was the deprecated and now extinct devfs, not udev. udev could be made compatible with devfs, though.

By the way, don't fiddle with MODULES in mkinitcpio.conf unless you know exactly what you need. In that case it's even best to just include the 'base' hook, as that makes for the simplest and smallest image.
If unsure, go with the default config.

byte · 2006-10-15 16:26:07

Try running jfs_fsck on that partition. It won't mount after a forced shutdown or something similar usually to be avoided with filesystems.

erosa · 2006-10-17 21:21:58

I'm running Arch 0.7.1 within QEMU and after an upgrade suffered from the same problem described.

To fix it, using the LiveCD I removed support for raid, scsi, and sata from my mkinitcpio confic as recommended by the Arch Wiki (http://wiki.archlinux.org/index.php/Mkinitcpio). I then recreated the mkinitcpio image and rebooted to a working system.

In trying to determing the cause of the problem, I believe to have discovered a possible issue. When pacman upgraded the kernel, it must have replaced the existing kernel image with the new one. If this is the case, I think that is a bad idea since you can be left with an unbootable system.

So, if I may ask a question, is it a recommended practice to create a backup kernel image prior to updating the kernel package?

Arch Linux

#1 2006-10-06 20:43:09

kernel panic after pkgs upgrade

#2 2006-10-06 20:45:26

Re: kernel panic after pkgs upgrade

#3 2006-10-08 14:41:27

Re: kernel panic after pkgs upgrade

#4 2006-10-08 15:52:49

Re: kernel panic after pkgs upgrade

#5 2006-10-08 15:56:20

Re: kernel panic after pkgs upgrade

#6 2006-10-08 16:10:10

Re: kernel panic after pkgs upgrade

#7 2006-10-08 16:13:11

Re: kernel panic after pkgs upgrade

#8 2006-10-08 16:14:39

Re: kernel panic after pkgs upgrade

#9 2006-10-08 16:17:39

Re: kernel panic after pkgs upgrade

#10 2006-10-08 18:18:45

Re: kernel panic after pkgs upgrade

#11 2006-10-08 18:37:57

Re: kernel panic after pkgs upgrade

#12 2006-10-09 07:51:59

Re: kernel panic after pkgs upgrade

#13 2006-10-13 16:09:07

Re: kernel panic after pkgs upgrade

#14 2006-10-14 20:31:51

Re: kernel panic after pkgs upgrade

#15 2006-10-15 08:13:15

Re: kernel panic after pkgs upgrade

#16 2006-10-15 16:26:07

Re: kernel panic after pkgs upgrade

#17 2006-10-17 21:21:58

Re: kernel panic after pkgs upgrade

Board footer