|Summary:||genkernel.conf isn't updated - server doesn't recognize a lvm2-root-volume|
|Product:||Gentoo Hosted Projects||Reporter:||Arne Babenhauserheide <arne_bab>|
|Component:||genkernel||Assignee:||Gentoo Genkernel Maintainers <genkernel>|
|Package list:||Runtime testing required:||---|
Description Arne Babenhauserheide 2006-09-08 11:37:37 UTC
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.5; Linux; de, eo, es) KHTML/3.5.4 (like Gecko) Build Identifier: I just got my lvm2-root-volume running again wit new kernels. It failed as it said it couldn't find the LVM2-volumes, directly after starting mdev. I updated the following parts of the genkernel.conf, and now it works again: ----------------------------- MODULE_INIT_TOOLS_VER="3.2.2-r1" MODUTILS_VER="2.4.27-r1" DIETLIBC_VER="0.30-r1" UDEV_VER="099" DEVICE_MAPPER_VER="1.02.09" LVM2_VER="2.02.09" ----------------------------- I assume that you also have to update the dmraid part and some other parts to get those features working again. Reproducible: Always Steps to Reproduce: 1.use an old system, on which you are using genkernel for a long time now and have a LVM2 based root partition 2.update genkernel (and maybe udev) 3.build a new kernel 4.reboot Actual Results: didn't find teh LVM2 root partition. I rebooted in my old kernel. Expected Results: The genkernel-update should have updated the genkernel.conf to use the recent versions of LVM, udev, ... ----- MODULE_INIT_TOOLS_VER="3.2.2-r1" MODUTILS_VER="2.4.27-r1" DIETLIBC_VER="0.30-r1" UDEV_VER="099" DEVICE_MAPPER_VER="1.02.09" LVM2_VER="2.02.09" ----- After updating the genkernel.conf the problem disappeared.
Comment 1 Arne Babenhauserheide 2006-09-08 11:38:49 UTC
Forgot to add: Genkernel Versions: 3.3.10, 3.3.11d, 3.4.0-r1
Comment 2 Chris Gianelloni (RETIRED) 2006-09-08 12:09:04 UTC
We are not responsible for making sure that your configuration files match you system. It's nearly impossible for us to do. What we can do is ensure that the versions match what we're expecting when we ship genkernel. Upgrades that you do on your own must be maintained by you.
Comment 3 Arne Babenhauserheide 2006-09-08 18:13:21 UTC
I am not able to track all the config files I might have to update on every new emerge, so this should happen automatically some way. One way I can think of would be, that an udev update automatically updates the file. Or that genkernel updates its config to the most recent versions I have installed (the info should be avaible via portage). I don't blame you for not having predicted this. It's just that it took me a good 10 hours to fix it, because I didn't even know here to look, and I think it would be nice if others wouldn't have to go through that hassle. I only managed to find the problem in te end, because of a tip from _XaX_ in IRC, and I think there may well be others who stop updating their kernels, because they don't manage to build a working new one. And one thing you did was updating busybox. That's why I found out that the config file exists... But before this sounds like only complaining: I did build my kernels on my own till a few months ago, and I'm really glad to have genkernel now, because it saves me a hell of a lot of work! And so I just want to say a big "Thank you!"
Comment 4 Chris Gianelloni (RETIRED) 2006-12-27 10:01:06 UTC
Well, as I said, we cannot track changes you've made on your own (including via portage). The design of genkernel is so it'll function on its own. It uses its own internal versions of certain applications. If you don't want to use the versions we've supplied, that's fine, but we don't have to support it. ;]