You are not logged in.

#1 2009-03-27 17:45:40

McEnroe
Member
Registered: 2009-03-27
Posts: 6

Boot failure (can't find rootfs) with .29

Since the time I switched to .29 my arch system refuses to boot saying it can't find my root filesys. My / is on a logical volume on a raid1 array (xfs). During boot arch finds the raid array and activates it, but apparently lvm2 fails at this point for unknown reasons. I'm dropped to recovery shell.

rootdelay did not help.

I check my array, volume group, and actual filesystems but I can't find any errors.

Any idea what is going on and how to avoid it?

Offline

#2 2009-03-28 23:17:35

hank863
Member
Registered: 2008-08-23
Posts: 77

Re: Boot failure (can't find rootfs) with .29

I'm having the same problem and have yet to find a solution.  I'm working on it too.  I'll let you know if I find anything.  Have you used a Live CD to put your system back in a usable state yet?

Last edited by hank863 (2009-03-28 23:18:22)

Offline

#3 2009-03-29 10:18:26

McEnroe
Member
Registered: 2009-03-27
Posts: 6

Re: Boot failure (can't find rootfs) with .29

Not quite I used the livecd to update all packages, including the kernel, hoping the problem would solve itself -- it didn't. I played a bit with mkinit*.conf and it even booted -- twice. I'm about to downgrade the kernel for I don't see any other solution.

Offline

#4 2009-03-29 17:07:59

hank863
Member
Registered: 2008-08-23
Posts: 77

Re: Boot failure (can't find rootfs) with .29

I fixed my problem, but you already said you played around with your mkinit*.conf, so this may not be of any help to you.  I'm not sure why this is the first Kernel upgrade I've had to do this, but I had to remove "raid-partitions" from the "HOOKS" line of my mkinit*.conf.  I guess it's because I don't have any raid-partitions and that caused the image generation process to fail.  Good luck on your search!  If you find out anything else, I can try to help you, but I'm no Linux master.  If it helps, here's my 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="pata_acpi pata_atiixp ata_generic scsi_mod ahci"

# 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 usb pcmcia net usbinput keymap encrypt lvm2 filesystems"

Offline

#5 2009-03-31 10:51:13

Deeno9
Member
From: Kleinfischlingen, Germany
Registered: 2008-03-26
Posts: 7
Website

Re: Boot failure (can't find rootfs) with .29

i've got the same problems over here. arch says, it can't find

/lib/modules/2.9.29-ARCH/modules.dep

but it's there,
and it says

Failed to parse block device name for /dev/sda1

removing "raid-partitions" from the "HOOKS" line of /etc/mkinitcpio.conf didn't help.

here's the mkinitcpio.conf:

# MODULES
MODULES="pata_acpi pata_amd ata_generic sata_nv sata_sil24"

# BINARIES
BINARIES=""

# FILES
FILES=""

# HOOKS
HOOKS="base udev autodetect pata scsi sata usb fw pcmcia net keymap encrypt lvm2 filesystems"

i don't know how to downgrade the kernel via a life-cd, so i'd be happy, if someone would explain it to me, so i can at least use .28

thank for the help

btw: i'm using i686 and / is ext3

Last edited by Deeno9 (2009-03-31 11:15:01)

Offline

#6 2009-03-31 11:41:53

McEnroe
Member
Registered: 2009-03-27
Posts: 6

Re: Boot failure (can't find rootfs) with .29

i don't know how to downgrade the kernel via a life-cd, so i'd be happy, if someone would explain it to me, so i can at least use .28

1. mdadm -A /dev/mdX /dev/sd{X1,X2,...}
2. modprobe dm-mod
3. vgchange -ay
4. cd /mnt
5. mkdir arch
6. mount /dev/arrayX/$root arch
7. same thing for all other partitions
8. mount -t proc proc arch/proc
9. mount -o bind /dev arch/dev
10. mount -o bind /sys arch/sys
11. ifconfig eth0 up
12. dhcpcd eth0
13. chroot arch /bin/bash
14. pacman -S core/kernel26
15. exit
16. reboot

Offline

#7 2009-03-31 11:52:24

bangkok_manouel
Member
From: indicates a starting point
Registered: 2005-02-07
Posts: 1,554

Re: Boot failure (can't find rootfs) with .29

McEnroe wrote:

i don't know how to downgrade the kernel via a life-cd, so i'd be happy, if someone would explain it to me, so i can at least use .28

1. mdadm -A /dev/mdX /dev/sd{X1,X2,...}
2. modprobe dm-mod
3. vgchange -ay
4. cd /mnt
5. mkdir arch
6. mount /dev/arrayX/$root arch
7. same thing for all other partitions
8. mount -t proc proc arch/proc
9. mount -o bind /dev arch/dev
10. mount -o bind /sys arch/sys
11. ifconfig eth0 up
12. dhcpcd eth0
13. chroot arch /bin/bash
14. pacman -S core/kernel26
15. exit
16. reboot

Before (and I guess/hope it's still possible), you could boot into your existing system with Arch install disk so you didnt have to do all those steps.


All design goals must be phrased in such a way that it is hard to use them as slogans to justify stupidity.

Offline

#8 2009-03-31 16:33:57

Deeno9
Member
From: Kleinfischlingen, Germany
Registered: 2008-03-26
Posts: 7
Website

Re: Boot failure (can't find rootfs) with .29

thank you, it worked smile i had no idea how to boot into my existing system, because i didn't see any options like that in the livecd grub. but following McEnroe's steps helped me, step #1 didn't work, so i skipped it, but without getting any problems.

thank you again smile

Offline

Board footer

Powered by FluxBB