Siduction Forum

Siduction Forum => Upgrade Warnings => Topic started by: dlalias2k1 on 2013/03/01, 05:03:05

Title: Kernel 3.8.0 can't find LVM (solved)
Post by: dlalias2k1 on 2013/03/01, 05:03:05
Weird. Just did a dist-upgrade from 3.7.1 to 3.8.0, 3.8.0 Won't boot normally, It attempts to. Says it can't find my Volume group, then says that it's skipping it. Then says it cant find my home LVM volume either, Alerts me that /dev/mapper/VOLUME-home does not exist, then gives up and drops me to intramfs shell.

I am still able to boot 3.7.1

Thoughts?
Title: Kernel 3.8.0 can
Post by: devil on 2013/03/01, 15:06:11
Known problem. Towo is working on it, without a real solution for LVM as of yet. Also Iso-Images will not boot with 3.8, but that is solved for us already.

greetz
devil
Title: Kernel 3.8.0 can
Post by: Smon on 2013/03/01, 15:54:13
Does this problem only occur with /-Partition in a LVM or generally with LVM?
Title: Kernel 3.8.0 can
Post by: bluelupo on 2013/03/01, 18:56:42
Hello,
I also have an Acer laptop which I run with the LVM and there can be no more since the last update of the package grub boot (where I'm only in the initramfs). As a workaround I have set on the laptop all grub packages to HOLD.

In another mini-PC (from notebook components assembled), I have no problem with LVM and grub.

I suspect that this is more a problem of grub as the LVM.
Title: RE: Kernel 3.8.0 can
Post by: towo on 2013/03/02, 13:21:50
At all with this problem, try
RUB_CMDLINE_LINUX="rootdelay=1"
in /etc/default/grub
Title: I upgraded to 3.80 and LVM was OK - Can I upgrade further?
Post by: bad_aptitude on 2013/03/09, 06:57:35
I have an encrypted installation of Riders on the Storm using LVM. I did a dist upgrade shortly after 3.8 was available. My installation worked and has continued to work just fine. I am concerned that if I do another dist upgrade that I may lose access to my encrypted installation.
Is it too soon  to do a dist upgrade if you ave an LV?
Title: Kernel 3.8.0 can't find LVM (solved)
Post by: Bequimão on 2013/03/09, 18:27:14
I had this problem before with kernel 3.5.x. Since then I have "rootdelay=5" as a kernel parameter. No problems with kernel 3.8 so far.

http://forum.siduction.org/index.php?topic=2663 (http://forum.siduction.org/index.php?topic=2663)
Bequimão