I have a working SuSE 10.1 system running kernel version 2.6.16.21-0.13. Updating the kernel to 2.6.16.21-0.21 renders the system unbootable. My /boot is /dev/hda1, a resierfs file system on /dev/hda My / is /dev/system/system, a resiferfs file system on top of LVM. The above layout works fine when I boot the machine into the 2.6.16.21-0.13 kernel. However, booting into the 2.6.16.21-0.21 system makes the system complain about not finding device /dev/system/system, and then drops me to a shell prompt without / being mounted. The messages that come across are to the effect of "/dev/system/system does not exist" and "device-mapper: device does not appear to be in the device hash table". With my little knowledge of Linux, I gather this to be an issue with the initrd. I noticed that while booting with the new broken (broken at least for me) kernel, module dm_mod loaded successfully. I understand this to be something needed for lvm. My question at this point is how do I get kernel 2.6.16.21-0.21 to boot and run on this machine on which kernel 2.6.16.21-0.13 runs fine? Thanks in advance for any help, -- --Moby
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2006-09-18 at 01:00 -0500, Moby wrote:
However, booting into the 2.6.16.21-0.21 system makes the system complain about not finding device /dev/system/system, and then drops me to a shell prompt without / being mounted.
The last kernel update should have updated udev to version udev-085-30.13. Perhaps it failed in your case: try to install it again (the udev rpm). You could try also running mkinird. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFDufAtTMYHG2NR9URAizGAJ9LuetWFgjxL5EfTixHiQBYxxoWVwCeLdln NIg99M/KAb0/29WhyT0iYPc= =vDCh -----END PGP SIGNATURE-----
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Monday 2006-09-18 at 01:00 -0500, Moby wrote:
However, booting into the 2.6.16.21-0.21 system makes the system complain about not finding device /dev/system/system, and then drops me to a shell prompt without / being mounted.
The last kernel update should have updated udev to version udev-085-30.13. Perhaps it failed in your case: try to install it again (the udev rpm). You could try also running mkinird.
- -- Cheers, Carlos E. R.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76
iD8DBQFFDufAtTMYHG2NR9URAizGAJ9LuetWFgjxL5EfTixHiQBYxxoWVwCeLdln NIg99M/KAb0/29WhyT0iYPc= =vDCh -----END PGP SIGNATURE-----
Thank you for your reply Carlos. I verified that udev is indeed version 085-30.13. After more investigation, it looks like the current mkinitrd (version 1.2-106.18) is the culprit. I opened the initrd the system is using for kernel 2.6.16.13-4 and also the initrd generated for kernel 2.6.16.21-0.21. I saw that the working initrd had all the lvm stuff in it, but the newer one had material for evms and not lvm. My thoughts are that the current mkinitrd (1.2-106.18) has a flaw and fails to include the appropriate lvm material. Going through the changelog of the current mkinitrd's RPM I see lots of changes mention evms and lvm. However, that still does not bring me closer to getting the latest kernel to work on this machine :( Would it be possible to go with the current kernel but just back rev the mkinitrd RPM, or is that big no no? -- --Moby
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2006-09-18 at 15:07 -0500, Moby wrote:
I verified that udev is indeed version 085-30.13.
After more investigation, it looks like the current mkinitrd (version 1.2-106.18) is the culprit. I opened the initrd the system is using for kernel 2.6.16.13-4 and also the initrd generated for kernel 2.6.16.21-0.21. I saw that the working initrd had all the lvm stuff in it, but the newer one had material for evms and not lvm. My thoughts are that the current mkinitrd (1.2-106.18) has a flaw and fails to include the appropriate lvm material. Going through the changelog of the current mkinitrd's RPM I see lots of changes mention evms and lvm. However, that still does not bring me closer to getting the latest kernel to work on this machine :(
Ufff.
Would it be possible to go with the current kernel but just back rev the mkinitrd RPM, or is that big no no?
It's a big I have no idea :-P Sorry. And... did you try running the new mkinird? Either that or keep using the old one, but running mkinird to recreate the correct ram disk image. And I think you should report this in bugzilla. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFDxQYtTMYHG2NR9URAgdGAJ9yjSuOYqewLtSTYk+UJn9vJldClQCgmLmJ sIDxQc3jjREpYpRbMot7fiM= =Pifb -----END PGP SIGNATURE-----
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Monday 2006-09-18 at 15:07 -0500, Moby wrote:
I verified that udev is indeed version 085-30.13.
After more investigation, it looks like the current mkinitrd (version 1.2-106.18) is the culprit. I opened the initrd the system is using for kernel 2.6.16.13-4 and also the initrd generated for kernel 2.6.16.21-0.21. I saw that the working initrd had all the lvm stuff in it, but the newer one had material for evms and not lvm. My thoughts are that the current mkinitrd (1.2-106.18) has a flaw and fails to include the appropriate lvm material. Going through the changelog of the current mkinitrd's RPM I see lots of changes mention evms and lvm. However, that still does not bring me closer to getting the latest kernel to work on this machine :(
Ufff.
Would it be possible to go with the current kernel but just back rev the mkinitrd RPM, or is that big no no?
It's a big I have no idea :-P
Sorry. And... did you try running the new mkinird?
Either that or keep using the old one, but running mkinird to recreate the correct ram disk image.
And I think you should report this in bugzilla.
- -- Cheers, Carlos E. R.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76
iD8DBQFFDxQYtTMYHG2NR9URAgdGAJ9yjSuOYqewLtSTYk+UJn9vJldClQCgmLmJ sIDxQc3jjREpYpRbMot7fiM= =Pifb -----END PGP SIGNATURE-----
Ok, I just verified that mkinitrd 1.2-106.18 is the real culprit. Using the previous version of mkinitrd (1.2-106.15) with the latest kernel works fine. For some reason, mkinitrd 1.2-106.18 includes evms material in the initrd instead of lvm material for machines that have / on lvm. I shall now venture to fill out a bug report. -- --Moby They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -- Benjamin Franklin First they came for the Jews and I did not speak out because I was not a Jew. Then they came for the Communists and I did not speak out because I was not a Communist. Then they came for the trade unionists and I did not speak out because I was not a trade unionist. Then they came for me and there was no one left to speak out for me. -- Pastor Martin Niemöller
participants (2)
-
Carlos E. R.
-
Moby