You are not logged in.

#1 2012-09-21 06:34:51

srnty
Member
Registered: 2012-09-21
Posts: 23

LVM not detecting one of my drives on boot

Hi there. Right now when I try to boot in to linux  I get an error from lvm saying that it is able to detect two of my drives, but not the third which is plugged in via USB. I've tried booting in to an Ubuntu livecd, and, once booted, the volume group works fine, but, because my /boot partition is in that group, I cannot boot in to arch right now. How do I fix this?

Couldn't find device with uuid bla bla bla.
Refusing activation of partial LV data. Use --partial to override.
2 logical volume(s) in volume group "VolGroup" now active

The boot process just stops at this point.

Last edited by srnty (2012-09-21 06:35:06)

Offline

#2 2012-09-21 06:41:20

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,424
Website

Re: LVM not detecting one of my drives on boot

Have you included the relevant hook in your mkinitcpio.conf?


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#3 2012-09-21 06:41:55

srnty
Member
Registered: 2012-09-21
Posts: 23

Re: LVM not detecting one of my drives on boot

Yes.

Actually, that depends on what the relevant hook is. I know it includes lvm, and I've tried adding usb to no avail.

Last edited by srnty (2012-09-21 06:43:14)

Offline

#4 2012-09-21 06:45:49

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,424
Website

Re: LVM not detecting one of my drives on boot

Sounds like it. Please paste your mkinitcpio.conf. Also, what is the filesystem on the external drive?


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#5 2012-09-21 06:52:30

srnty
Member
Registered: 2012-09-21
Posts: 23

Re: LVM not detecting one of my drives on boot

# 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 any additional binaries a given user may
# wish into the CPIO image.  This is run first, so it may be used to
# override the actual binaries used in a given hook.
# (Existing files are NOT overwritten if already added)
# BINARIES are dependency 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 any way.  This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options
# like so:
#    FILES="/etc/modprobe.d/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
# '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 a pata mdadm array with an encrypted root FS.
##   Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
#    HOOKS="base udev pata mdadm encrypt filesystems"
#
##   This setup loads an lvm2 volume group on a usb device.
#    HOOKS="base udev usb lvm2 filesystems"
HOOKS="base udev autodetect usb sata lvm2 filesystems usbinput"

# COMPRESSION
# Use this to compress the initramfs image. With kernels earlier than
# 2.6.30, only gzip is supported, which is also the default. Newer kernels
# support gzip, bzip2 and lzma. Kernels 2.6.38 and later support xz
# compression.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"

# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=""

The external drive is formatted to be part of the lvm. The lvm includes an ext2 volume and a bunch of xfs volumes.

When I run "vgchange -ay" on ubuntu, all three drives load fine.

Last edited by srnty (2012-09-21 07:02:21)

Offline

#6 2012-09-21 07:06:48

srnty
Member
Registered: 2012-09-21
Posts: 23

Re: LVM not detecting one of my drives on boot

I guess all I really need to know for now is how to add the --partial flag to whatever command arch is running while it boots.

Offline

#7 2012-09-21 11:54:39

Lone_Wolf
Forum Moderator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 11,969

Re: LVM not detecting one of my drives on boot

systemd or initscripts ?

There have been several threads lately about problems with lvm and systemd on boot.


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

Board footer

Powered by FluxBB