[SLE] module missing in the upgraded kernel
Hi, 10.0 x86_64 here. I upgraded/updated the kernel to 2.6.13-15.10 (official). It misses the dm-mod module compiled, so I'm really screwed. Non of my LVM volumes can be mounted. And my /usr and /var are on logical volumes :( The previous kernel I used - 2.6.13-15.8 worked OK. Can someone confirm that this is the case? Where from I can get the previous version, so I can recover? -- -- Svetoslav Milenov (Sunny) Windows is a 32-bit extension to a 16-bit graphical shell for an 8-bit operating system originally coded for a 4-bit microprocessor by a 2-bit company that can't stand 1 bit of competition. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Sunday 16 July 2006 18:06, Sunny wrote:
Hi, 10.0 x86_64 here.
I upgraded/updated the kernel to 2.6.13-15.10 (official).
It misses the dm-mod module compiled,
Not at all # rpm -qpl kernel-default-2.6.13-15.10.x86_64.rpm |grep dm-mod /lib/modules/2.6.13-15.10-default/kernel/drivers/md/dm-mod.ko It's there, so it must be something else that's wrong -- Ut supra post festum sunt obscura -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Sunny wrote:
Hi, 10.0 x86_64 here.
I upgraded/updated the kernel to 2.6.13-15.10 (official).
It misses the dm-mod module compiled, so I'm really screwed. Non of my LVM volumes can be mounted. And my /usr and /var are on logical volumes :(
The previous kernel I used - 2.6.13-15.8 worked OK.
Can someone confirm that this is the case?
Where from I can get the previous version, so I can recover?
Hi Sunny, have you checked that you have the dm-mod.ko file, I think it should be found under /lib/modules/2.6.13-15.10/kernel/drivers/md/ If so, it may be that the installation procedure didn't create your initrd with all the required drivers. If this is the case, you'll need to run mkinitrd, I don't remember the proper syntax off the top of my head so check out the man page. There is also a variable in /etc/sysconfig/kernel called INITRD_MODULES which determines which modules go into the initrd image, check this before using mkinitrd. HTH, James. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Monday 17 July 2006 15:12, James Watkins wrote:
Sunny wrote:
Hi, 10.0 x86_64 here.
I upgraded/updated the kernel to 2.6.13-15.10 (official).
It misses the dm-mod module compiled, so I'm really screwed. Non of my LVM volumes can be mounted. And my /usr and /var are on logical volumes :(
The previous kernel I used - 2.6.13-15.8 worked OK.
Can someone confirm that this is the case?
Where from I can get the previous version, so I can recover?
Hi Sunny, have you checked that you have the dm-mod.ko file, I think it should be found under /lib/modules/2.6.13-15.10/kernel/drivers/md/ If so, it may be that the installation procedure didn't create your initrd with all the required drivers. If this is the case, you'll need to run mkinitrd, I don't remember the proper syntax off the top of my head so check out the man page. There is also a variable in /etc/sysconfig/kernel called INITRD_MODULES which determines which modules go into the initrd image, check this before using mkinitrd.
He said he had /usr and /var on logical volumes, and you don't need initrd for those, you only need to use initrd to mount /, since the point of initrd is to be able to access /lib/modules (which isn't allowed to be on a separate partition) so all the other drivers can be loaded The problem must be something else, but until Sunny replies with more details we can't know -- Ut supra post festum sunt obscura -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Anders Johansson wrote:
He said he had /usr and /var on logical volumes, and you don't need initrd for those, you only need to use initrd to mount /, since the point of initrd is to be able to access /lib/modules (which isn't allowed to be on a separate partition) so all the other drivers can be loaded
The problem must be something else, but until Sunny replies with more details we can't know
Of course, you're quite right. Unless he has / on a logical volume the initrd is irrelevant. I guess we just have to wait and see. Cheers, James. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On 7/17/06, Anders Johansson wrote:
He said he had /usr and /var on logical volumes, and you don't need initrd for those, you only need to use initrd to mount /, since the point of initrd is to be able to access /lib/modules (which isn't allowed to be on a separate partition) so all the other drivers can be loaded
Anders, just curious - saying "isn't allowed" means is not a good idea, or I'll get an error if I try to use a separate partition for /lib? -- -- Svetoslav Milenov (Sunny) Windows is a 32-bit extension to a 16-bit graphical shell for an 8-bit operating system originally coded for a 4-bit microprocessor by a 2-bit company that can't stand 1 bit of competition. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Monday 17 July 2006 16:44, Sunny wrote:
Anders, just curious - saying "isn't allowed" means is not a good idea, or I'll get an error if I try to use a separate partition for /lib?
It's very much not a good idea, because /lib and a few other directories need to be accessible if things fail. They need to be part of the base system. I'm not sure if you'll actually get an error message, because it's one of those things I've never been suicidal enough to try Have a look at the FHS for a more comprehensive description -- Ut supra post festum sunt obscura -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On 7/17/06, James Watkins wrote:
Sunny wrote:
Hi, 10.0 x86_64 here.
I upgraded/updated the kernel to 2.6.13-15.10 (official).
It misses the dm-mod module compiled, so I'm really screwed. Non of my LVM volumes can be mounted. And my /usr and /var are on logical volumes :(
The previous kernel I used - 2.6.13-15.8 worked OK.
Can someone confirm that this is the case?
Where from I can get the previous version, so I can recover?
Hi Sunny, have you checked that you have the dm-mod.ko file, I think it should be found under /lib/modules/2.6.13-15.10/kernel/drivers/md/ If so, it may be that the installation procedure didn't create your initrd with all the required drivers. If this is the case, you'll need to run mkinitrd, I don't remember the proper syntax off the top of my head so check out the man page. There is also a variable in /etc/sysconfig/kernel called INITRD_MODULES which determines which modules go into the initrd image, check this before using mkinitrd.
The problem was, that the dm-mod.ko file was missing with that kernel. I do not recall any problems during the update. But it was not there. Anyway, I booted to rescue with the CD, then mounted the filesystems, chroot, and downgraded to 2.6.13-15.8 and now everything is OK. I did not had time to experiment and to update again to confirm if the install is broken, or something else have been wrong the previous time. Anyway, thanks to all for the suggestions. I'll try later today or tomorrow to update the kernel again and will post my findings. Cheers -- -- Svetoslav Milenov (Sunny) Windows is a 32-bit extension to a 16-bit graphical shell for an 8-bit operating system originally coded for a 4-bit microprocessor by a 2-bit company that can't stand 1 bit of competition. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On 7/17/06, Sunny wrote:
The problem was, that the dm-mod.ko file was missing with that kernel. I do not recall any problems during the update. But it was not there.
Anyway, I booted to rescue with the CD, then mounted the filesystems, chroot, and downgraded to 2.6.13-15.8 and now everything is OK.
I did not had time to experiment and to update again to confirm if the install is broken, or something else have been wrong the previous time.
Anyway, thanks to all for the suggestions.
I'll try later today or tomorrow to update the kernel again and will post my findings.
Cheers
Ok, I tried the update again. I'm using smart for that. The strange thing was, that smart decided to install first the nongpls rpm, then the sources, and then the kernel itself. It reported some problem with the post-install script of the nongpl rpm, not finding the System...map file in /boot, but everything else went OK. I checked after that that I have dm-mod.ko is present, and reinstalled the nongpl rpm. It reinstalled OK, without any error. The reboot went OK and my system is up and running. So, maybe something went very wrong last time I did the update, and the modules were not written. Thank you all for the help. Cheers -- -- Svetoslav Milenov (Sunny) Windows is a 32-bit extension to a 16-bit graphical shell for an 8-bit operating system originally coded for a 4-bit microprocessor by a 2-bit company that can't stand 1 bit of competition. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
participants (3)
-
Anders Johansson -
James Watkins -
Sunny