new kernel (2.6.17.13-1.1) won't boot [Solved]

mouse256 · 2006-09-11 09:12:07

Hi,
I can't get my system booting with the new kernel from current.
The output:

:: Initramfs Completed - control passing to kinit
md: Will configure md0 (super-block) from /dev/sda1,/dev/sdb1, below
EXT2-fs: ubable to read superblock
EXT3-fs: unable to read superblock
kinit: unable to mount root fs on device md0(9,0)
kinit: init not found!
kernel panic - not syncing: Attemted to kill init

I use software raid (/ is on /dev/md0 (ext3), /boot is on /dev/sda3 (ext2))
The previous kernel has no problems, I did not change my configfiles in the meantime.
Part of Grub:

# (0) Arch Linux
title  Arch Linux
root   (hd0,2)
kernel /vmlinuz26 root=/dev/md0 ro vga=795 noapic md=0,/dev/sda1,/dev/sdb1
initrd /kernel26.img

/etc/mkinitcpio.conf

# MODULES
# The following modules are loaded before any boot hooks are
# run.  Advanced users may wish to specify all system modules
# in this array.  For instance:
#     MODULES="piix ide_disk reiserfs"
MODULES="raid0 ext3"

# BINARIES
# This setting includes, into the CPIO image, and additional
# binaries a given user may wish.  This is run first, so may
# be used to override the actual binaries used in a given hook.
# (Existing files are NOT overwritten is already added)
# BINARIES are dependancy parsed, so you may safely ignore libraries
BINARIES=""

# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in anyway.  This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options,
# like so:
#    FILES="/etc/modprobe.conf"
FILES=""

# HOOKS
# This is the most important setting in this file.  The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added.  Run 'mkinitcpio -H <hook>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'modload' may be used in place of 'udev', but is not recommended
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
#    This setup specifies all modules in the MODULES setting above.
#    No raid, lvm, or encrypted root is needed.
#    HOOKS="base"
#
#    This setup will autodetect all modules for your system and should
#    work as a sane default
#    HOOKS="base udev autodetect ide scsi sata filesystems"
#
#    This setup will generate a 'full' image which supports most systems.
#    No autodetection is done.
#    HOOKS="base udev ide scsi sata usb filesystems"
#
#    This setup assembles an ide raid array with an encrypted root FS.
#    Note: See 'mkinitcpio -H raid' for more information on raid devices.
#    HOOKS="base udev ide filesystems raid encrypt"
#
#    This setup loads an LVM volume group on a usb device.
#    HOOKS="base udev usb filesystems lvm"
HOOKS="base udev autodetect sata ide keymap"

Who can help me here?

chrismortimore · 2006-09-11 09:14:59

http://wiki.archlinux.org/index.php/Mki … Using_raid
This will help you.

mouse256 · 2006-09-11 09:27:20

OK, what a shame on me :oops:
It seems I did modify the mkinitcpio.conf file and removed the raid hook. readding the hook solved my problem...

chrismortimore · 2006-09-11 12:04:40

mouse256 wrote:

OK, what a shame on me :oops:

Happens to the best of us

Arch Linux

#1 2006-09-11 09:12:07

new kernel (2.6.17.13-1.1) won't boot [Solved]

#2 2006-09-11 09:14:59

Re: new kernel (2.6.17.13-1.1) won't boot [Solved]

#3 2006-09-11 09:27:20

Re: new kernel (2.6.17.13-1.1) won't boot [Solved]

#4 2006-09-11 12:04:40

Re: new kernel (2.6.17.13-1.1) won't boot [Solved]

Board footer