On Tuesday 24 of July 2012 17:21:46 BOYPT wrote: > On Tue, Jul 24, 2012 at 5:02 PM, Herbert J. Skuhra <hskuhra@xxxxxxxx> wrote: > > On 24.07.2012 10:51, BOYPT wrote: > >> On Tue, Jul 24, 2012 at 4:40 PM, Herbert J. Skuhra <hskuhra@xxxxxxxx> > >> > >> wrote: > >> Hi, > >> > >>> after upgrading to linux 3.5-1 yesterday my computer no longer boots. :( > >>> The following error is displayed: No volume groups found > >>> > >>> I have to run "lvm vgchange -a y" before I can continue booting. > >> > >> What do you get running "lvm vgchange -a y" ? > >> > >> If this still fail to load the mapper, it's not likely to boot. > > > > If I enter this command and then quit/exit the system boots normally. > > I have no idea why the vg is not activated automatically. > > > > After downgrading to linux 3.4.6-1 everything is OK. > > > > I encounter the same situation. > > The forum users also report the same: > https://bbs.archlinux.org/viewtopic.php?id=145714 > > I don't know what exactly changed in the new kernel(seems like things going > with udev,device mapper,kernel ...etc), adding the kernel parameters like > the post said helps. Hi, I'm the OP in the forum thread you are referring to. I was wrong. The kernel parameters help, but it's only due to the one sec. delay induced by misuse of the lvmwait parameter :) David
