Bug 460481

after installing suse 11.1 final and changing boot options in grub, the system wasnt able to start win xp or suse 11.1, after installing the old 10.3 it works (win xp and 10.3

Created attachment 261700 [details]
YsST2 logs GRUB failed to install, logs, create while installation still in progress

GNOME LiveCD, 32-bit (i686) Final

This installation used a pre-existing partition set on a dual-boot HP-2133 Mininote computer (i686).

sda1 "/Windows/C"
sda2 "Extended"
sda5 "swap"
sda6 "/"
sda7 "/usr"
sda8 "/home"

As I post this, I am trying to decide whether to abort the installation immediately after I post this, or try to continue.

Created attachment 261702 [details]
YaST2 logs after aborting installation

I decided to abort installation of GRUB without re-trying.  The whole installer quit at that point.  This set of logs might not show anything more than the earlier set, but it is a bit larger, so there is a chance that there might be a bit more usable information.

The following were the visible error reports during the installation:

Problem was at "Saving bootloader configuration..."

[In Popup dialog window:]

Error occurred while installing GRUB

GNU GRUB version 0.97 (640K lower / 3072K upper memory)

[Minimal BASH-like line editing is supported. For the first wor, TAB
 lists possible command completions. Anywhere else TAB lists the possible
 completions of a device/filename.]
grub> setup --stage2=/boot/grub/stage2 --force-lba (hd0,1)(hd0,5)
 Checking if "/boot/grub/stage1" exists... yes
 Checking if "/boot/grub/stage2" exists... yes
 Checking if "/boot/grub/efs_stage1_5" exists... yes
 Running "embed /boot/grub/e2fs_stage1_5 (hd0,1)"... failed (this is not fatal)
 Running "embed /boot/grub/e2fs_stage1_5 (hd0,5)"... failed (this is not fatal)
 Running "install --force-lba --stage2=/boot/grub/stage2 /boot/grub/stage1 (hd0,1) /boot/grub/stage2 p /boot/grub/menu.lst "... failed

Error 22: No such partition
grub> quit"

By the way, If you have any advice on what I might try to get this installation to work, that would be appreciated.  I think that I can recover Vista this time.

Joerg:

I think it might be a while before the support team gets to this bug, but I think, if you can post YaST2 logs like I have done, it will help get things moving when they get to this one.  I think it is worth the effort because there is a possibility that the problem might be a bit different on a 64-bit machine than a 32-bit machine.

If you have not does this before, after you are finished trying to install, open a terminal and enter:

"sudo /sbin/save_y2logs logs.tgz"

Then upload the resulting file as an attachment here.

"Severity" is always a bit debatable, but I think this is higher than "Normal", so I am changing that.

I had exactly the same bug. If it may help I can give you my hardwareconfig.
My 'solution' was openSuSE 11.0-64. I'm *not* amused.

Hans, I do not think this is the place to discuss this installation.  There have been a number of discussions in the forums.  I will give a quick summary of what I know and direct you to the most important forum topic.

What Works Better:

1.  The NET Installers.

Apparently, the "GNOME LiveCD" in both 32-bit and 64-bit have the same problem(s) regarding the Partitioner and the Grub Installer.  I have successfully installed a 32-bit GNOME setup on an HP-2133 Mini laptop using the 32-bit NET installer disc.  I re-used existing partitions to avoid the partitioner, but Grub installed without problems.  I have also successfully installed a 64-bit GNOME setup on a Compaq V2570CA.  Again, I used the pre-existing partitions, but there were no "warnings" and the Grub installer was not a problem.

2.  The "KDE4 Live CDs"

The "KDE4 LiveCD" is not perfect either, but is generally "better" than the GNOME version.  I have made a successful load on an Acer Aspire One using the "KDE4 LiveCD."  NOTE:  Ironically, I cannot advice people use that particular CD specifically for the Acer Aspire One, nor for any Netbooks with 1024 x 600, or smaller screens, because there are windows in the installation that are not usable because they are too big.  I was only able to complete the load  because I could use some "default" settings which might not be acceptable to others, and I was able to make the "panel" disappear from the bottom of the screen (not hard, but not easily figured out by beginners).

3.  The DVD

The DVD, again has some problems, but seems to be better than the GNOME CDs.  I have never tried the DVD, so I cannot give any personal confirmation.

The following is the main discussion for this set of problems.  NOTE:  If you study this, and some other forum discussions, you probably could have fixed the resulting inability to boot.  But it was not a free lunch.  I read the information and it is quite a lot of information:

http://forums.opensuse.org/install-boot-login/386603-fixing-vista-multiboot-opensuse.html

Sorry I did not post this sooner. . . .

In Comment #7 I forgot a few important details:

1.  Both the NET installations were done to create "dual-boot" systems with Vista 32-bit already installed.  The results were fully operational with Windows and OpenSuSE selectable at boot.

2.  The Acer Aspire One had "Linpus Lite" already installed.  Although Linpus Lite is a Linux system, the resulting installation was not completely operational.  The link to boot "Linpus Lite" failed and had to be corrected manually in '/boot/grub/menu.lst'.

To Sebastian Henrich:
 - your problem is also described in bug #464485 -> it is bug same for SLE11 I will add you to CC of bug. From your description seems to be specific problem of thinkpad, but without yast logs I am not able write it exactly

To Joerg Wuennenberg:
 - your problem is described in bug #461613 the fix is in yast2-bootloader 2.17.50 for 11.1 will be maintenance update -> the bug is solved

To Jim Omura:
 - to comment #4 there are 2 problems: 
   * one is in tool parted it is describe in some bug for it
   * next there is problem with your partitioning of disk. please look at supported scenarios http://en.opensuse.org/Bootloader/Scenarios

I hope that my short comment helps you. The "original" bugreport is duplicate of bug #464485. if Sebastian disagree he can return it back like normal bug. Comments from other people describe other problems which are also describe in other bugs.

*** This bug has been marked as a duplicate of bug 464485 ***