Arch Linux

Kamu

Member

Registered: 2006-12-28

Posts: 3

No longer boots since update [kinit & call trace troubles]

Hi all,

Recently I did a full system upgrade on a completely working system (running I assume was a 2.6.28 kernel26) that upgraded it to 2.6.29. It then stopped booting correctly. I left this for a while since I didn't have the time for messing around with it. Today I got back to it, used live cd, chrooted and did a full system update (to a 2.6.30 kernel) hoping it may have fixed it. No such luck.

Here is the error portion of the boot up/init:

Waiting 10 seconds for device /dev/sda3 ...

Root device '/dev/sda3' doesn't exist, attempting to create it
/bin/mknod /dev/root b 8 3
:: Initramfs Completed - control passing to kinit
IP-Config: no devices to configure
Waiting 0 s before mouting root device...
kinit: Cannot open root device dev(8,3)
kinit: init not found!
Kernel panic - not syncing: Attempted to kill init!
Pid: 1, comm: kinit Not tainted 2.6.30-ARCH #1
Call Trace:
[<c03cebcd>] ? panic+0x5b/0xff
[<c013f624>] ? do_exit+0x614/0x6f0
[<c02dce40>] ? redirected_tty_write+0x0/0xe0
[<c013f810>] ? complete_and_exit+0x0/0x30
[<c0103d74>] ? syscall_call+0x7/0xb

My mkinitcpio.conf is untouched, as are the files in mkinitcpio.d.

My FS is as follows:

/dev/sda1 - ext2 - /boot
/dev/sda2 - swap
/dev/sda3 - ext3 - /
/dev/sda4 - ext3 - /home

My menu.1st for grub is:

# (0) Arch Linux
title Arch Linux
root   (hd0,0)
kernel /vmlinuz26 rootfstype=ext3 root=/dev/sda3 vga=791 ro
initrd /kernel26.img

The bizare thing is, if I change to root=/dev/sda4, I don't get 'root device doesn't exist etc etc etc' and it mounts it fine with no errors and then kinit drops to a recovery console instead of panicing.

I am not sure what to do now. Basically, what has changed since 2.6.28 that caused this in the first place?

Thanks in advance for any help!

Last edited by Kamu (2009-08-03 11:26:13)

djszapi

Member

From: Cambridge, United Kingdom

Registered: 2009-06-14

Posts: 1,439

Website

Re: No longer boots since update [kinit & call trace troubles]

Hello!

What can you see in recovery console ? Do you see your filesystem ?

---

http://lpapp.blogspot.com

maturin

Member

Registered: 2009-08-27

Posts: 9

Re: No longer boots since update [kinit & call trace troubles]

kamu: I am having a similar problem on an install.  I noticed root (hd0,0) points to /boot and root=/dev/sda3 points to /.  In this discussion,

http://bbs.archlinux.org/viewtopic.php?id=56251

a boot problem was solved with root=/ (UUID pointing to /boot not / ).  see post 3. I'm a noob, so I hope this applies. good luck.

steve_v

Member

Registered: 2006-02-11

Posts: 80

Re: No longer boots since update [kinit & call trace troubles]

This may sound like a silly question, but you did have /boot mounted within the chroot when the kernel installed right?
--Does the arch-fallback initrd help?
--Boot into your recovery console and take a look at dmesg & /proc/partitions. Make sure your drives are being detected & what drives/partitions are where.
--More than one disk? ls /sys/block/[sh]d[a-z]/ should show you what partitions are on which disks.
-- Be sure root entry in /etc/fstab and on kernel command line are the same.
--More than one disk controller? Put the module in mkinitcpio.conf so the controller with your / on it gets loaded first  (I had fun and games with this during the ide -> pata switch)
+1 for the referencing partitions by UUID, you can also do it by filesystem label (root=/dev/disk/by-[label,uuid]/XXXX)

Steve.