Bug#496923: linux-image-2.6.26-1-686: Linux-image-2.6.26-1-686 : fail to load LVM2 volume groupe
On Thu, Aug 28, 2008 at 05:13:45PM +0200, Cyril Mertens wrote:
> Package: linux-image-2.6.26-1-686
> Version: 2.6.26-3
> Severity: grave
> Justification: renders package unusable
>
>
> Hello,
>
> Since the installation of the 2.6.26-1-686, my system cannot boot with this kernel as my LVM2 volume groups are not found.
> This error occurs at the start of the boot sequence with this message :
> << Volume group "Jupiter" not found. >>
> Of course, the boot stops and the maintenance terminal is called.
>
> This error does not append when booting with 2.6.24 and 2.6.25 i686-kernels
>
> My hardware for information :
> D201GLY2 mainboard with soldered Intel Celeron 220
> 1 Crucial DDR2 PC2-5300 stick 1 gb
> 1 Hitachi SATA hard drive P7K500 320 gb
>
> Some fdisk infomation :
>
> Device Boot Start End Blocks Id System
> /dev/sda1 * 1 31 248976 83 Linux
> /dev/sda2 32 38913 312319665 8e Linux LVM
>
> vgdisplay report
> --- Volume group ---
> VG Name Jupiter
> System ID
> Format lvm2
> Metadata Areas 1
> Metadata Sequence No 4
> VG Access read/write
> VG Status resizable
> MAX LV 0
> Cur LV 3
> Open LV 3
> Max PV 0
> Cur PV 1
> Act PV 1
> VG Size 297,85 GB
> PE Size 4,00 MB
> Total PE 76249
> Alloc PE / Size 76249 / 297,85 GB
> Free PE / Size 0 / 0
> VG UUID jLvVjg-l0KZ-ytzG-e2Wq-AtMD-8j4B-RCuXK2
>
> lvdisplay report
> --- Logical volume ---
> LV Name /dev/Jupiter/root
> VG Name Jupiter
> LV UUID jhaaO4-T6ji-ki4J-T1Cg-whOq-ns4l-k2uHJF
> LV Write Access read/write
> LV Status available
> # open 1
> LV Size 6,68 GB
> Current LE 1709
> Segments 1
> Allocation inherit
> Read ahead sectors auto
> - currently set to 256
> Block device 254:0
>
> --- Logical volume ---
> LV Name /dev/Jupiter/swap_1
> VG Name Jupiter
> LV UUID QUZgqH-t7NI-CoMx-r7Yu-yiQM-o55V-S6hdXv
> LV Write Access read/write
> LV Status available
> # open 2
> LV Size 2,59 GB
> Current LE 664
> Segments 1
> Allocation inherit
> Read ahead sectors auto
> - currently set to 256
> Block device 254:1
>
> --- Logical volume ---
> LV Name /dev/Jupiter/home
> VG Name Jupiter
> LV UUID mMklwr-oED0-ymYP-xxs3-XmC8-Rz1P-NxYZdV
> LV Write Access read/write
> LV Status available
> # open 1
> LV Size 288,58 GB
> Current LE 73876
> Segments 1
> Allocation inherit
> Read ahead sectors auto
> - currently set to 256
> Block device 254:2
>
> pvdisplay report
> --- Physical volume ---
> PV Name /dev/sda2
> VG Name Jupiter
> PV Size 297,85 GB / not usable 3,67 MB
> Allocatable yes (but full)
> PE Size (KByte) 4096
> Total PE 76249
> Free PE 0
> Allocated PE 76249
> PV UUID oYPct7-TLQb-BcT8-nAUJ-st2q-TWkr-Xj0VMZ
>
> I hope I correctly described my problem
first you choose wrong severity
second your report misses any relevant info.
how about adding dmesg of working+non-working kernel!?
--
maks
Reply to: