OpenSuSE 11.1 and new kernel up-date.

Hi,

I have an old OpenSuSE 11.1 box and I made that last up-date.
It happens that my partitions are encrypted with Luks
Applying this up-date (or one that is on the list and up-dates mkinitrd) stops the pc from booting.
Because of this bug in the new version of mkinitrd:
https://bugzilla.novell.com/show_bug.cgi?id=631464

the solution is simple and was made availabel by Michal Marek in the link mentioned on the thread:
Commit in mkinitrd in openSUSE - Gitorious

I did like this:
Googled for the problem, found the solution on the improved double quote kernel command line detection.
and then:

Boot the pc with the DVD in rescue mode.
Change the /boot/grub/menu.lst in order to make only / available in the boot.

So all the /dev/mapper/swap and /dev/mapper/home will be errased (in my case)
so the the kernel command line
‘luks=“root swap home”’ shoudl be only:
luks=root

Therefore the machine boots and one get to acccess the all important / :slight_smile:

After that reboot the machine and it goes into recover mode (or something like that) …
Edit /lib/mkinitrd/scripts/boot-start.sh as mentioned on the patch (use vi …yuck!).
go back to /boot/grub/menu.lst and restore the initial setup of Luks with all partitions (in my case root swap and home).

Reboot normally … that’s it!

You could also change the the mentioned /lib/mkinitrd/scripts script by booting and mounting the partition with luksOpen … anyway … it worked.

Regards,
Pedro

Hi,

Of course … now that you know about this, make the up-grade normally and check the mentioned script in case you use luks.
While the system is running and before the required update reboot make the changed proposed in the above link.
An also always check /boot/grub/menu.lst to see if everything is ok … just in case.

Regards,
Pedro

Thanks for the heads up. I do have 11.1 on two PCs: (1) my wife’s Fujitsu-Siemens Amilo 7400M laptop, and (2) my mothers Dell Dimension-2100 desktop. Fortunately neither of those two PCs have encrypted partitions.

But its good to know there is a work around for this problem you encountered.