No LVM with 2.6.14.3

kleptophobiac · 2005-12-17 13:10:02

I have uselvm=yes in rc.conf, and I'm loading the dm-mod module in the modules= line, but lvm no longer functions with the new kernel. I'm reverting back to the previous stock kernel26.

Any idea why?

BTW, the new kernel loads about six million (or 97) modules for my server. That's crazy!

apeiro · 2005-12-17 18:48:48

You'll have to unset the REMOVE_DM=1 line in /etc/mkinitrd.conf and regenerate your init ramdisk. LVM and RAID support are disabled by default because most users don't need them.

See this page about initrd customization. You can tweak your initrd down to only the modules you need. The default is safe, but bulky.

http://wiki.archlinux.org/index.php/Initrd

apeiro · 2005-12-17 18:57:02

As an example, here is the mkinitrd.conf from one of my machines. It has a RAID1 root filesystem, with /usr and /home on LVM/RAID.

REMOVE_IDE=
REMOVE_SCSI=1
REMOVE_SATA=1
REMOVE_CDROM=
REMOVE_USB=1
REMOVE_FW=1
REMOVE_RAID=
REMOVE_DM=
REMOVE_FS=

AUTODETECT=1
 
# Define which modules are needed by adding "moduleX moduleY"
# If left empty, all modules are included if they are not disabled above
HOSTCONTROLLER_IDE=
HOSTCONTROLLER_SCSI=
HOSTCONTROLLER_SATA=
HOSTCONTROLLER_USB=
FILESYSTEMS=

# If you have an encrypted root filesystem, set it here
CRYPT_DEVICE=

# If you use software RAID for your root device then list all the devices
# that belong to your root array here.  If your root RAID device is
# something other than md0, then change the RAID_ROOT_ARRAY setting.
#    eg, RAID_ROOT_DEVICES="/dev/hda3 /dev/hdc3"
RAID_ROOT_ARRAY="md0"
RAID_ROOT_DEVICES="/dev/hda2 /dev/hdc2"

# Define additional modules here
ADD_MODULE=
REMOVE_MODULE=

apeiro · 2005-12-17 19:10:16

If you're also using RAID:

http://wiki.archlinux.org/index.php/Ini … RAID_users

kleptophobiac · 2005-12-17 22:30:24

I ended up figuring out that the initrd was the problem and remade it by specifically including the necessary module.

...but your solution is much cleaner and more comprehensive. So thank you!

But I don't like the new stock kernel, so I'm using archck now.

dmartinsca · 2006-04-13 21:42:36

I probably should not have posted this here, i didn't realize the thread was so old! sorry

With the stock kernel setup, is it necessesary to edit mkinitrd.conf if my root filesystem is not LVM? I am getting an error when the boot process gets to the LVM2 section saying it cannot communicate with the device mapper. I have set the dm-mod module to load in rc.conf. Surely the modules from rc.conf should be read very early!

brain0 · 2006-04-14 22:08:48

dmartinsca wrote:

I probably should not have posted this here, i didn't realize the thread was so old! sorry
With the stock kernel setup, is it necessesary to edit mkinitrd.conf if my root filesystem is not LVM? I am getting an error when the boot process gets to the LVM2 section saying it cannot communicate with the device mapper. I have set the dm-mod module to load in rc.conf. Surely the modules from rc.conf should be read very early!

As you found out yourself, this thread is pretty old. WIth up-to-date initscripts, modules are loaded in the very beginning, so you don't need a modified initrd anymore. Instead, adding the dm-mod module to MODULES=() in rc.conf should load it before lvm setup.
If it doesn't, your initscripts are most likely quite old.

Arch Linux

#1 2005-12-17 13:10:02

No LVM with 2.6.14.3

#2 2005-12-17 18:48:48

Re: No LVM with 2.6.14.3

#3 2005-12-17 18:57:02

Re: No LVM with 2.6.14.3

#4 2005-12-17 19:10:16

Re: No LVM with 2.6.14.3

#5 2005-12-17 22:30:24

Re: No LVM with 2.6.14.3

#6 2006-04-13 21:42:36

Re: No LVM with 2.6.14.3

#7 2006-04-14 22:08:48

Re: No LVM with 2.6.14.3

Board footer