Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
LVM2 doesn't bind voulme groups automatically
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Documentation, Tips & Tricks
View previous topic :: View next topic  
Author Message
sys64738
n00b
n00b


Joined: 17 Mar 2005
Posts: 7
Location: Germany

PostPosted: Thu Mar 17, 2005 7:27 pm    Post subject: LVM2 doesn't bind voulme groups automatically Reply with quote

Hi, this is my first post on this forum. I encountered a problem a few days ago with using lvm2 and switching my mainboard:

Before switching, I used a mainboard with a Promise RAID Controller (IDE, software) onboard and could use the driver compiled into the kernel. Now, on my new mainboard, there is no such controller, but I still have 4 IDE disks I use via LVM2 as two volume groups, so I use a DAWIControl 133 card now. Unfortunatilly, this card can't be hard-compiled into the kernel, because it overwrites my onboard IDE, so I use the Silicon Image (siimage.ko) as a module now.

This brought up another problem: With the combination of udev and the use of the Silicon Image as a module, vgscan didn't find my volume groups at boot anymore. As long, as the system was fully booted up, vgscan reported both groups correctly and I was able to use them with the following command:

vgchange $VG_NAME -a y

where $VG_NAME is the name of the group (i.e. "vg") and "-a y" says: "activation: yes". I asked about this matter in the IRC channel "#lvm" and got the answer to try a "sleep" command between the module binding and vgscan at startup. The problem was I didn't know where the vgscan is done. The answer is:

Alter "/etc/init.d/checkfs" with your favorite text editor, search "sbin/vgscan >/dev/null" (this should be line 36) and type in "sleep 5" a line before. Next boot, everything should be going smoothly, although there is a short delay now.

Maybe udev doesn't create the device nodes quick enough so vgscan can scan them for devices. This delay (maybe it can be shorter than 5 seconds) should help to make sure every device node is in place.

I hope, this little HowTo can help anyone who has a similar problem and prevent this kind of frustation I had with it. Many Thanx to the people of #lvm who tried to help me with this.

So long,
sys
_________________
Whatever they say about me: I decline! :)
Back to top
View user's profile Send private message
smasher
Tux's lil' helper
Tux's lil' helper


Joined: 15 Nov 2003
Posts: 95

PostPosted: Fri Mar 18, 2005 12:55 am    Post subject: Reply with quote

To make your onboard IDE first have you tried this option the "Boot off-board chipsets first support " in your kernel?
Code:
    -> Device Drivers
         -> ATA/ATAPI/MFM/RLL support
           -> ATA/ATAPI/MFM/RLL support (IDE [=y])
             -> Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support (BLK_D
               -> PCI IDE chipset support (BLK_DEV_IDEPCI [=y])

or maybe the kernel boot option
Code:
ide=reverse

Also, are you using the libata drivers in the scsi section of the kernel config? I believe these come up as sdX instead of hdX.
Back to top
View user's profile Send private message
sys64738
n00b
n00b


Joined: 17 Mar 2005
Posts: 7
Location: Germany

PostPosted: Fri Mar 18, 2005 3:46 pm    Post subject: Reply with quote

smasher wrote:
To make your onboard IDE first have you tried this option the "Boot off-board chipsets first support " in your kernel?
Code:
    -> Device Drivers
         -> ATA/ATAPI/MFM/RLL support
           -> ATA/ATAPI/MFM/RLL support (IDE [=y])
             -> Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support (BLK_D
               -> PCI IDE chipset support (BLK_DEV_IDEPCI [=y])


I didn't try this before, but did now: It worked! Thank you, now I can use the LVM and the siiamge support fully compiled into the kernel.

smasher wrote:
or maybe the kernel boot option
Code:
ide=reverse


It only works correctly when I leave out this point. Maybe the controller BIOS itself already does this reverse? I don't know. At least, it works now fine for me. :)

smasher wrote:

Also, are you using the libata drivers in the scsi section of the kernel config? I believe these come up as sdX instead of hdX.


Nope, I don't have any SATA- harddisks yet, so I deactivated the onboard SATA-controller anyway to prevent any trouble with a non-used device. Maybe a shiny new SATA-hdd will be next reason I'll post here. ;)

Best regards,
sys
_________________
Whatever they say about me: I decline! :)
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Documentation, Tips & Tricks All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum