Skip to contentSkip to conversation

vg availability during boot

linux-lvm Till Wimmer 3 participants 3 messages Sep 15, 2009

lore
Share & tools
lore
#0 lore raw
Quoted 2 lines

Did you rebuild initrd? During boot, initrd uses staticly linked modules to load what otherwise would be kernel modules. It does, if LVM is enabled, do a vgchange -y a as part of that process. Since LVM is part of the default initrd, it may be the drivers for your SAN that you need to get in place - remember to include the high-end Ethernet drivers too that your NAS (I presume?) uses.

Hi,

i have a quite similar problem with my server. But in my case, it occurs from time to time only.
Before i had another issue with mounting the root partition because of swapped SCSI IDs (sda becomes sdb, sdc, becomes sda, and so on). But i could solve this with ext2fs labels.

I'm using Debian Lenny.

Is the vgchange -ay in initrd executed for every volume group or is this hard coded by update-initrd?

Could the swapping of SCSI-IDs be the reason for this issue, too?

Thank you,
TW

#1 lore raw

I spent four days messing with this before I found
this procedure for rebuilding initrd, which worked for me. This howto talks specifically about switching to RAID, but it also worked for me switching to LVM on RAID:
http://www.howtoforge.com/software-raid1-grub-boot-fedora-8
--
Ray Morris
[email protected]

Strongbox - The next generation in site security:
http://www.bettercgi.com/strongbox/

Throttlebox - Intelligent Bandwidth Control
http://www.bettercgi.com/throttlebox/

Strongbox / Throttlebox affiliate program:
http://www.bettercgi.com/affiliates/user/register.php

Quoted 37 lines · Till Wimmer
Quoted 1 line

Did you rebuild initrd? During boot, initrd uses staticly linked

modules to load what otherwise would be kernel modules. It does, if LVM is enabled, do a vgchange -y a as part of that process. Since LVM is part of the default initrd, it may be the drivers for your SAN that
you need to get in place - remember to include the high-end Ethernet drivers too that your NAS (I presume?) uses.

Quoted 1 line

Hi,

i have a quite similar problem with my server. But in my case, it occurs from time to time only.
Before i had another issue with mounting the root partition because of
swapped SCSI IDs (sda becomes sdb, sdc, becomes sda, and so on). But i
could solve this with ext2fs labels.

I'm using Debian Lenny.

Is the vgchange -ay in initrd executed for every volume group or is this hard coded by update-initrd?

Could the swapping of SCSI-IDs be the reason for this issue, too?

Thank you,
TW

_______________________________________________
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
In reply to Till Wimmer

That's another good reason to rely on UUID instead of the /dev device name. If you see how MD does things, and LVM internally, you'll find all device references are by UUID. Why not use that more foolproof method? As long as the device is online, it doesn't matter what bus id it gets.

Signature · 1 line
   Peter H. Larsen

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Till Wimmer
Sent: Tuesday, September 15, 2009 1:35 PM
To: LVM general discussion and development
Subject: Re: RE: [linux-lvm] vg availability during boot

Quoted 2 lines

Did you rebuild initrd? During boot, initrd uses staticly linked modules to load what otherwise would be kernel modules. It does, if LVM is enabled, do a vgchange -y a as part of that process. Since LVM is part of the default initrd, it may be the drivers for your SAN that you need to get in place - remember to include the high-end Ethernet drivers too that your NAS (I presume?) uses.

Hi,

i have a quite similar problem with my server. But in my case, it occurs from time to time only.
Before i had another issue with mounting the root partition because of swapped SCSI IDs (sda becomes sdb, sdc, becomes sda, and so on). But i could solve this with ext2fs labels.

I'm using Debian Lenny.

Is the vgchange -ay in initrd executed for every volume group or is this hard coded by update-initrd?

Could the swapping of SCSI-IDs be the reason for this issue, too?

Thank you,
TW

_______________________________________________
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/