Skip to contentSkip to conversation

VGs not detected at startup

linux-lvm Markus Wiedmer - FHBB 3 participants 5 messages Nov 8, 2004

lore
Share & tools
lore
#0 lore raw

hi all,

I'm running lvm2.00.25 on kernel 2.6.9, but I have problems with detecting the VGs.Immediately after bootup, vgscan returns: no volume groups found, same for lvscan and pvscan. I have my root partition on my Primary IDE-Drive (hda) and the VGs lie on the serial-ATA-Drive (sda).

Now after I run fdisk on /dev/sda (just run it an quit again). all my VGs mysteriously appear on the next vgscan.

I guess I'm missing something, but I can't see what. Does anyone know this problem?

Thanks in advance

markus

Signature · 2 lines
Mit freundlichen Grüssen
Markus Wiedmer - FHBB
#1 lore raw
Quoted 7 lines

I'm running lvm2.00.25 on kernel 2.6.9, but I have problems with detecting the VGs.Immediately after bootup, vgscan returns: no volume groups found, same for lvscan and pvscan. I have my root partition on my Primary IDE-Drive (hda) and the VGs lie on the serial-ATA-Drive (sda).

Quoted 5 lines

Now after I run fdisk on /dev/sda (just run it an quit again). all my VGs mysteriously appear on the next vgscan.

I guess I'm missing something, but I can't see what. Does anyone know this problem?

Yes, I certainly know this problem. I'm running LVM2 2.00.15 and device mapper 1.00.17 on a 2.6.9 (x86) kernel. 'Vgscan' fails to find an vloumes running from the system initialization script, but works fine a few seconds (I'm guessing) later run from 'rc.local'. I've tried a few things to "fix" this, all to no effect.

David S.

Quoted 18 lines

Thanks in advance

markus

Signature · 11 lines
Mit freundlichen Gr?ssen
Markus Wiedmer - FHBB




_______________________________________________
linux-lvm mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
#2 lore raw

I'd be happy if this would work with me. Unfortunately a few seconds (even an hour) will do nothing with my system. the VGs are still unavailable.

I now found a work-around that seems to work so far. In the LVM-Start-Script I just put "mount /dev/sda5 || true" before the vgscan. it looks like after a mount-command the system suddenly finds the VG. strange...

markus

DS> Yes, I certainly know this problem. I'm running LVM2 2.00.15 and device DS> mapper 1.00.17 on a 2.6.9 (x86) kernel. 'Vgscan' fails to find an vloumes DS> running from the system initialization script, but works fine a few seconds DS> (I'm guessing) later run from 'rc.local'. I've tried a few things to "fix" DS> this, all to no effect.

DS> David S.

#3 lore raw
Quoted 4 lines · Markus Wiedmer - FHBB

I now found a work-around that seems to work so far. In the LVM-Start-Script I just put "mount /dev/sda5 || true" before the vgscan. it looks like after a mount-command the system suddenly finds the VG. strange...

Apologies if this is something that's already been discussed (if so I missed it), and also for saying something that you've almost definitely covered but......

Check to see if there's any autoloading of modules, or anything, going on as a result of the mount/fdisk?

Also (instead of the mount) does a 'dd' work? E.g. dd if=/dev/sda of=/dev/null bs=512 count=1?

That's going to be faster & probably less intrusive.

Graham

#4 lore raw
Quoted 4 lines · Markus Wiedmer - FHBB
Quoted 4 lines

I now found a work-around that seems to work so far. In the LVM-Start-Script I just put "mount /dev/sda5 || true" before the vgscan. it looks like after a mount-command the system suddenly finds the VG. strange...

llsdo> Apologies if this is something that's already been llsdo> discussed (if so I missed it), and also
llsdo> for saying something that you've almost definitely covered but......

llsdo> Check to see if there's any autoloading of modules, or llsdo> anything, going on as a result of the
llsdo> mount/fdisk?

llsdo> Also (instead of the mount) does a 'dd' work? E.g. dd llsdo> if=/dev/sda of=/dev/null bs=512
llsdo> count=1?

llsdo> That's going to be faster & probably less intrusive.

llsdo> Graham

thanks a lot for your hint. it really was a module (sd_mod) that was not loaded at boottime. everything works now like a charm

thanks

markus

Signature · 3 lines
Mit freundlichen Grüssen
Markus Wiedmer - FHBB
mailto:[email protected]