[SOLVED] Kernel panic after installing Arch, using LVM

siaco · 2009-04-05 19:26:39

Hi,

I'm having some trouble when I try to install Arch with LVM on a computer. I have followed the LVM wiki, but after rebooting I get this:

To me, it seems like LVM is okay, and volume group is up and running. Some of the text from the image above:

[...]
3 Logical volume(s) in volume group "VolGroupBase" now active
:: Running Hook [filesystem]
:: Loading root filesystem module...
Attempting to create root device '/dev/sda3'
[...]

I have no idea why it tries to create dev/sda3 - my comupter doesn't even have one :-)

I would be really glad if someone please can help me with this. I'm kinda lost atm

I don't know if the following info might help:

[root@archiso mnt]# fdisk -l
Disk /dev/sda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x193f8911

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1          12       96358+  83  Linux
/dev/sda2              13        9729    78051802+  8e  Linux LVM

[root@archiso mnt]# lvdisplay 
  --- Logical volume ---
  LV Name                /dev/VolGroupBase/swap
  VG Name                VolGroupBase
  LV UUID                OnTeBP-bGk5-v0of-2F2w-Jc8m-mIdf-rlLDkT
  LV Write Access        read/write
  LV Status              available
  # open                 0
  LV Size                1.00 GB
  Current LE             256
  Segments               1
  Allocation             contiguous
  Read ahead sectors     auto
  - currently set to     256
  Block device           254:0
   
  --- Logical volume ---
  LV Name                /dev/VolGroupBase/root
  VG Name                VolGroupBase
  LV UUID                9zs23K-i3c8-OX1a-r1by-CNhE-7pvq-YwE2bJ
  LV Write Access        read/write
  LV Status              available
  # open                 1
  LV Size                5.00 GB
  Current LE             1280
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           254:1
   
  --- Logical volume ---
  LV Name                /dev/VolGroupBase/home
  VG Name                VolGroupBase
  LV UUID                ooKq9d-Mych-QYt7-765r-MCgd-ED7X-3JfjXh
  LV Write Access        read/write
  LV Status              available
  # open                 0
  LV Size                60.00 GB
  Current LE             15360
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           254:2

[root@archiso mnt]# cat /mnt/boot/grub/menu.lst 
# 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   5
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.
#
#-*

# (0) Arch Linux
title  Arch Linux
root   (hd0,0)
kernel /vmlinuz26 root=/dev/mapper/VolGroupBase-root ro
initrd /kernel26.img

# (1) Arch Linux
title  Arch Linux Fallback
root   (hd0,0)
kernel /vmlinuz26 root=/dev/mapper/VolGroupBase-root ro
initrd /kernel26-fallback.img

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

[root@archiso mnt]# cat /mnt/root/etc/fstab
# 
# /etc/fstab: static file system information
#
# <file system>        <dir>         <type>    <options>          <dump> <pass>
none                   /dev/pts      devpts    defaults            0      0
none                   /dev/shm      tmpfs     defaults            0      0

#/dev/cdrom             /media/cd   auto    ro,user,noauto,unhide   0      0
#/dev/dvd               /media/dvd  auto    ro,user,noauto,unhide   0      0
#/dev/fd0               /media/fl   auto    user,noauto             0      0

/dev/mapper/VolGroupBase-swap swap swap defaults 0 0
/dev/mapper/VolGroupBase-root / xfs defaults 0 1
/dev/mapper/VolGroupBase-home /home xfs defaults 0 1
UUID=7a0f62c0-3af3-4ab6-8626-86eb5e968ed0 /boot ext2 defaults 0 1

[root@archiso mnt]# cat /mnt/root/etc/mkinitcpio.conf

# vim:set ft=sh
# 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=""

# 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 name>' 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, lvm2, 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 pata scsi sata filesystems"
#
#    This is identical to the above, except the old ide subsystem is
#    used for IDE devices instead of the new pata subsystem.
#    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 pata scsi sata usb filesystems"
#
#    This setup assembles an pata raid array with an encrypted root FS.
#    Note: See 'mkinitcpio -H raid' for more information on raid devices.
#    HOOKS="base udev pata raid encrypt filesystems"
#
#    This setup loads an lvm2 volume group on a usb device.
#    HOOKS="base udev usb lvm2 filesystems"
HOOKS="base udev autodetect pata scsi sata lvm2 filesystems"

Last edited by siaco (2009-04-06 04:03:28)

Dieter@be · 2009-04-05 19:31:09

can you share your mkinitcpio.conf ?
are you sure an mkinitcpio has run after you configured it? (the installer does an mkinitcpio during package installation and once after "configure system", so unless you fixed mkinitcpio.conf way too late you should be fine)

siaco · 2009-04-05 19:35:12

Updated the first post with mkinitcpio.conf. I'm pretty sure that the mkinitcpio ran after I added the "lvm2" right before filesystems. I did this in the installer, and after I was finished editing config files I think it ran. Also, seems to me that it is starting lvm during boot, as seen in the image are the logical volumes found (or at least I think so :-) )

siaco · 2009-04-05 19:37:19

Oh, I might add that I installed Arch on the same computer earlier today without problems. But, when I figured that I wanted to set it up with lvm I removed everything and started from scratch.

Zariel · 2009-04-05 21:11:53

Does the fallback image work?

siaco · 2009-04-06 04:03:07

Hmmm. For some reason, I had to go into the BIOS and disable boot-from-cd option before I was allowed to open the tray and take the CD out after the install (yes, it sounds kinda wired hehe). Therefor, I booted from the CD and selected this in the menu: More options -> Boot existing Linux install. I though that this would boot the Linux installment just like it would have done without it, but it turns out that that was not the case

After disabling boot-from-cd in BIOS, i took the CD out and booted from my harddrive and everything was fine so I gues "Boot existing Linux install" isn't exactly the same as booting just from my harddrive. I thought that that option would just "pass the control" on to the installment on hard drive.

Thanks for all the help everyone! :-) It now works hehe.

(btw, what does the Boot existing Linux really install do? :-p)

Dieter@be · 2009-04-06 07:03:28

Hmm.. maybe because when you boot from cd first grub detects your devices in an other order

Arch Linux

#1 2009-04-05 19:26:39

[SOLVED] Kernel panic after installing Arch, using LVM

#2 2009-04-05 19:31:09

Re: [SOLVED] Kernel panic after installing Arch, using LVM

#3 2009-04-05 19:35:12

Re: [SOLVED] Kernel panic after installing Arch, using LVM

#4 2009-04-05 19:37:19

Re: [SOLVED] Kernel panic after installing Arch, using LVM

#5 2009-04-05 21:11:53

Re: [SOLVED] Kernel panic after installing Arch, using LVM

#6 2009-04-06 04:03:07

Re: [SOLVED] Kernel panic after installing Arch, using LVM

#7 2009-04-06 07:03:28

Re: [SOLVED] Kernel panic after installing Arch, using LVM

Board footer