You are not logged in.

#1 2012-09-09 10:31:33

musiKk
Member
Registered: 2011-05-21
Posts: 12

[solved] Boot issues after update caused by LVM

Hi,

I know that there are some threads regarding boot issues but I haven't been able to find a solution for my problem.

I have the following partitions:

$ lsblk
NAME                       MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda                          8:0    0  74.5G  0 disk 
├─sda1                       8:1    0   128M  0 part /boot
├─sda2                       8:2    0     2G  0 part [SWAP]
└─sda3                       8:3    0  72.4G  0 part 
  ├─vg_trinity-root (dm-0) 254:0    0    10G  0 lvm  /
  └─vg_trinity-home (dm-1) 254:1    0    25G  0 lvm  /home

I have

USELVM="yes"

in my rc.conf and the following im mkinitcpio.conf:

HOOKS="base udev autodetect pata scsi sata lvm2 filesystems"

Still, when booting the volume group does not get activated. The following message appears:

:: running hook [lvm2]
Activating logical volumes...
  No volume groups found
Waiting 10 seconds for device /dev/mapper/vg_trinity-root ...
ERROR: Unable to find root device '/dev/mapper/vg_trinity-root'.
You are being dropped to a recovery shell
    Type 'exit' to try and continue booting
sh: can't access tty: job control turned off
[rootfs /]#

At that point I just run

lvm vgchange -ay

exit the shell and booting continues. So somehow activation of the volume group does not occur early enough. I reinstalled udev, mkinitcpio, linux and generated a new boot image as proposed in https://bbs.archlinux.org/viewtopic.php … 4#p1059124 but to no avail. Is there anything else that might be wrong with my configuration?

Thanks for any help.
mK

Last edited by musiKk (2012-09-09 16:23:17)

Offline

#2 2012-09-09 11:10:52

Ashren
Member
From: Denmark
Registered: 2007-06-13
Posts: 1,221
Website

Offline

#3 2012-09-09 16:22:58

musiKk
Member
Registered: 2011-05-21
Posts: 12

Re: [solved] Boot issues after update caused by LVM

My apologies. Usually I'm quite good at searching but this one slipped right past me. Marking as solved (even though the root cause is still WIP).

Offline

Board footer

Powered by FluxBB