Find the answer to your Linux question:
Results 1 to 3 of 3
I compiled a Xen kernel and upon reboot into the new kernel I'm getting this: Code: Loading dm-log.ko module Loading dm-region_hash.ko module Loading dm-message.ko module Loading rm-raid45.ko module Device-mapper: dm-raid45: ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Dec 2008
    Posts
    3

    Kernel error upon boot up


    I compiled a Xen kernel and upon reboot into the new kernel I'm getting this:
    Code:
    Loading dm-log.ko module
    Loading dm-region_hash.ko module
    Loading dm-message.ko module
    Loading rm-raid45.ko module
    Device-mapper: dm-raid45: initialized v0.25941
    Waiting for driver initialization.
    Scanning and configuring dmraid supported devices
    Creating root device.
    Mounting root filesystem.
    mount: could not find filesystem "/dev/root"
    Setting up other filesystems.
    Setting up new root fs
    setuproot: moving /dev failed: No such file or directory
    no fstab.sys, mounting internal defaults
    setuproot: error mounting /proc: No such file or directory
    setuproot: error mounting /sys: No such file or directory
    Switching to new root and running init.
    unmounting old /dev
    unmounting old /proc
    unmounting old /sys
    switchroot: mount failed: No such file or directory
    Kernel panic - not syncing: Attempted to kill init!
    Do you guys have any ideas as to why this is happening? I do have a raid controller card on the server. I'm running Centos 5.5.

  2. #2
    Linux Engineer Segfault's Avatar
    Join Date
    Jun 2008
    Location
    Acadiana
    Posts
    877
    mount: could not find filesystem "/dev/root"
    Where this /dev/root comes from? Grub? fstab?

    If you have RAID controller why dmraid? dmraid is software RAID designed for fakeraid.

  3. #3
    Just Joined!
    Join Date
    Dec 2008
    Posts
    3
    Here is what I got in grub.conf:

    # grub.conf generated by anaconda
    #
    # Note that you do not have to rerun grub after making changes to this file
    # NOTICE: You do not have a /boot partition. This means that
    # all kernel and initrd paths are relative to /, eg.
    # root (hd0,0)
    # kernel /boot/vmlinuz-version ro root=/dev/sda1
    # initrd /boot/initrd-version.img
    #boot=/dev/sda
    default=0
    timeout=5
    splashimage=(hd0,0)/boot/grub/splash.xpm.gz
    hiddenmenu
    title CentOS (2.6.18-194.11.1.el5xen)
    root (hd0,0)
    kernel /boot/xen.gz-2.6.18-194.11.1.el5 dom0_mem=2048m
    module /boot/vmlinuz-2.6.18-194.11.1.el5xen ro root=LABEL=/
    module /boot/initrd-2.6.18-194.11.1.el5xen.img
    title CentOS (2.6.18-194.el5)
    root (hd0,0)
    kernel /boot/vmlinuz-2.6.18-194.el5 ro root=LABEL=/ rhgb quiet
    initrd /boot/initrd-2.6.18-194.el5.img
    How do I check to see whether the second kernel (the working one) is using dmraid or not? I believe Xen HVM has issues with using soft raid.

  4. $spacer_open
    $spacer_close

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •