Re: LVM2 volume groups not found during boot
On Fri, 03 Mar 2006 14:00:17 +0100, Ian East <ian.east@gmail.com>
wrote:
>I'm having a problem where my LVM volume groups are not found during
>boot. I have to manually scan and mount them after the OS boots.
>
>Debian Sarge/2.6.11-1
>Volume is on a 3ware 9500S-8
>
>Here's a snipped from the boot sequence:
>
>-----------------------------------------------------------------------------------
>Loading modules...
> ide-cd
> ide-detect
>FATAL: Module ide_detect not fouCapability LSM initialized
>nd.
> sd_mod
>All modules loaded.
>device-mapper: 4.4.0-ioctl (2005-01-12) initialised:
>dm-devel@redhat.com
>Creating device-mapper devices...done.
>Creating device-mapper devices...done.
>Setting up LVM Volume Groups...
> Reading all physical volumes. This may take a while...
> No volume groups found
> No volume groups found
> No volume groups found
>Checking all file systems...
>fsck 1.35 (28-Feb-2004)
>/dev/hda3: clean, 11/13959168 files, 446255/27906913 blocks
>fsck.ext3: No such file or directory while trying to open /dev/vg0/lv0
>/dev/vg0/lv0:
>The superblock could not be read or does not describe a correct ext2
>filesystem. If the device is valid and it really contains an ext2
>filesystem (and not swap or ufs or something else), then the
>superblock
>is corrupt, and you might try running e2fsck with an alternate
>superblock:
> e2fsck -b 8193 <device>
>
>
>fsck failed. Please repair manually.
>
>CONTROL-D will exit from this shell and continue system startup.
>
>Give root password for maintenance
>(or type Control-D to continue):
>--------------------------------------------------------------------------------------
>
>After I boot into the OS I have to manually vgscan and mount the
>volume:
>
>--------------------------------------------------------------------------------------
>dbrimg:~# vgdisplay
> No volume groups found
>dbrimg:~# vgscan
> Reading all physical volumes. This may take a while...
> Found volume group "vg0" using metadata type lvm2
>dbrimg:~# vgdisplay
> --- Volume group ---
> VG Name vg0
> System ID
> Format lvm2
> Metadata Areas 1
> Metadata Sequence No 2
> VG Access read/write
> VG Status resizable
> MAX LV 0
> Cur LV 1
> Open LV 0
> Max PV 0
> Cur PV 1
> Act PV 1
> VG Size 1.46 TB
> PE Size 4.00 MB
> Total PE 381458
> Alloc PE / Size 369458 / 1.41 TB
> Free PE / Size 12000 / 46.88 GB
> VG UUID zYTx8k-xcFI-N6Vd-WAPm-HaPI-rmiL-BmfYo7
>
>dbrimg:~# lvdisplay /dev/vg0/lv0
> --- Logical volume ---
> LV Name /dev/vg0/lv0
> VG Name vg0
> LV UUID 4lzxIP-o96s-Sp1I-BRWA-WD8h-40H1-HBqi8f
> LV Write Access read/write
> LV Status NOT available
> LV Size 1.41 TB
> Current LE 369458
> Segments 1
> Allocation inherit
> Read ahead sectors 0
>
>dbrimg:~# lvchange -ay /dev/vg0/lv0
>dbrimg:~# mount /data/mysql
>kjournald starting. Commit interval 5 seconds
>EXT3 FS on dm-0, internal journal
>EXT3-fs: mounted filesystem with ordered data mode.
>dbrimg:~# df
>Filesystem 1K-blocks Used Available Use% Mounted on
>/dev/hda1 20169236 1175704 17968988 7% /
>tmpfs 2029844 0 2029844 0% /dev/shm
>/dev/mapper/vg0-lv0 1489554400 32828 1413856576 1% /data/mysql
>----------------------------------------------------------------------------------
>
>Any ideas on what's going wrong?
>
>Thanks for any help.
Never mind... Fixed it. I needed to add the 3ware driver to
/etc/modules
Reply to: