http://bugzilla.novell.com/show_bug.cgi?id=610971 http://bugzilla.novell.com/show_bug.cgi?id=610971#c1 --- Comment #1 from Per Jessen 2010-06-02 16:47:56 UTC --- Looks like jfsutils was not automagically selected for installation although I was using a JFS filesystem during installation. Let me know if you really need the logs. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=610971 http://bugzilla.novell.com/show_bug.cgi?id=610971#c Miklos Szeredi changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Basesystem |Installation AssignedTo|mszeredi@novell.com |bnc-team-screening@forge.pr | |ovo.novell.com QAContact|qa@suse.de |jsrain@novell.com -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=610971 http://bugzilla.novell.com/show_bug.cgi?id=610971#c2 Michal Marek changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|mmarek@novell.com |bnc-team-screening@forge.pr | |ovo.novell.com --- Comment #2 from Michal Marek 2010-06-04 06:22:59 UTC --- Dear screening team, that something has "initrd" in the subject doesn't automatically mean it's a mkinitrd bug. Per: jfsutils.spec has Supplements: filesystem(jfs) so in theory it should be automatically installed when you use the jfs filesystem. It could be a problem with the solver or with the partitioner, I don't know. Better attach the y2logs so the yast / zypp people can tell for sure. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=610971 http://bugzilla.novell.com/show_bug.cgi?id=610971#c4 --- Comment #4 from Per Jessen 2010-06-04 09:29:30 UTC --- Created an attachment (id=367027) --> (http://bugzilla.novell.com/attachment.cgi?id=367027) logs as saved by save_y2logs -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=610971 http://bugzilla.novell.com/show_bug.cgi?id=610971#c5 Miklos Szeredi changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mszeredi@novell.com AssignedTo|mszeredi@novell.com |jreidinger@novell.com --- Comment #5 from Miklos Szeredi 2010-06-10 09:42:00 UTC --- According to the logs jfsutils is installed:

grep jfsutils rpm-qa jfsutils-1.1.14-2.8 (openSUSE) openSUSE Factory

and it provides /sbin/fsck.jfs. I don't think that this is the cause of the failure, even though there's a warning about this in YaST2/y2logmkinitrd, which is curious given that the package is installed. It rather looks like the cause of the failure is LILO: Perl-Bootloader: 2010-06-02 15:33:03 ERROR: Command '/sbin/lilo -P ignore -v -v

/var/log/YaST2/y2log_bootloader 2>&1' failed with code 256 and output: LILO version 22.8, Copyright (C) 1992-1998 Werner Almesberger

Reassigning to Perl-Bootloader maintainer. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=610971 http://bugzilla.novell.com/show_bug.cgi?id=610971#c7 Josef Reidinger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #7 from Josef Reidinger 2010-06-23 07:15:55 UTC --- Hi, lilo is deprecated bootloader. This mean that now new developement is made for such bootloader in perl-Bootloader and yast2-bootloader. Problem in your case is that your compiled modules needed during boot is too big. Lilo by default due to old systems doesn't place modules above 15M. So you have three ways how to avoid this problem: 1) supported one: Use grub as bootloader ( I think that it works in all case and if not we fix it) 2) easy one: add option to lilo.conf 'large-memory' as virtualbox does have BIOS problems for which is this limit designed. 3) hard one: reduce number of modules and recreate initrd if you have any questions feel free to ask -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.