https://bugzilla.novell.com/show_bug.cgi?id=765198
https://bugzilla.novell.com/show_bug.cgi?id=765198#c12
--- Comment #12 from Neil Rickert 2012-06-22 14:12:24 UTC ---
Hi, Michael.
I have since done another install of Beta2 on a different computer (from the 32
bit DVD - the installs mentioned in #9 were all from the 64bit DVD). If you
want logs, I can provide from the tarball that I saved with the 2nd install
mentioned in #9, or from the 32 bit install that I have done more recently.
The grub2 install also failed on the older 32bit system. It's slower hardware,
so I had a bit more time to look at the missing file mentioned. I still didn't
get the full name. However, it is clear that the file had a path relative to
"/boot". It was either "/grub2/x.y" or "/grub/x.y" where the x and y are the
parts that went past too fast to see.
It looks to me as if this is a file that should have been created in the grub2
install. A test for the existence of that file presumably detected that the
install had failed, and reported that as an error message.
I now have an hypothesis as to what is going wrong.
For most of the failures, the first error message seen has reported an error in
"mkinitrd". When I backup to using grub1, I see the same "mkinitrd" message.
However, the grub1 install works nevertheless.
My hypothesis is that the script that controls the grub2 install is too
sensitive to errors reported from "mkinitrd". Maybe it should ignore errors,
and simply test for the existence of the needed "mkinitrd" file. With
plymouth, a lot more is being put into "initrd", and that may lead to some
errors that have no important consequences. It seems that the grub1 install
ignores such errors, but maybe it is causing the grub2 install to abort
prematurely.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.