Mailinglist Archive: opensuse-bugs (4172 mails)

< Previous Next >
[Bug 513004] yast2 bootloader doesn't represent the REAL boot conditions
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Mon, 15 Jun 2009 03:41:46 -0600
  • Message-id: <20090615094147.00ED2CC74F@xxxxxxxxxxxxxxxxxxxxxx>
http://bugzilla.novell.com/show_bug.cgi?id=513004

User juhliarik@xxxxxxxxxx added comment
http://bugzilla.novell.com/show_bug.cgi?id=513004#c1


Jozef Uhliarik <juhliarik@xxxxxxxxxx> changed:

What |Removed |Added
----------------------------------------------------------------------------
Priority|P5 - None |P3 - Medium
Status|NEW |NEEDINFO
Info Provider| |suse@xxxxxxxxx




--- Comment #1 from Jozef Uhliarik <juhliarik@xxxxxxxxxx> 2009-06-15 03:41:46
MDT ---
I read your story and it is really interesting problem. What I didn't see there
are yast logs from your playing with yast2-bootloader. I am not able decide
what really happened. Please attach yast logs from machine where you tried to
install xen kernel.

Next it seems (from you description) that yast2-bootloader didn't update boot
settings: change boot flag or content of MBR. I don't know your previous
settings of booting and I am not able decide what was necessary to change after
your changes (change boot partition from sda2 to sda8)

Finally if you start yast2-bootloader and after that change partitionig of disk
by hand yast2-bootloader still works with old partitioning of disk. It would be
the cause of your problem but it is only hypotesis without yast logs...

Please attach yast logs and I will write you more details. Maybe it is not bug
of yast2-bootloader but please attach yast 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.

< Previous Next >
References