https://bugzilla.novell.com/show_bug.cgi?id=413135 User jsrain@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=413135#c1 Jiri Srain changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |tobysubs@gmx.com --- Comment #1 from Jiri Srain 2008-08-04 00:41:16 MDT --- Please, attach the installation logs. Did I get correctly that /dev/sdb was not present in device map at all? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=413135 User jsrain@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=413135#c3 Jiri Srain changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |tobysubs@gmx.com --- Comment #3 from Jiri Srain 2008-08-07 23:48:10 MDT --- You can boot the installation, switch to 2nd console, mount the partition and copy the logs somewhere you can reach them. If you other Linux on /dev/sda3 boots fine, just boot it and mount 11.0's partition(s). Anyway, my guess is that all that's wrong is the disks order which you need to review, but I'd like to see the log first so that I can tell what exactly was wrong and how to set it up properly. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=413135 User tobysubs@gmx.com added comment https://bugzilla.novell.com/show_bug.cgi?id=413135#c5 --- Comment #5 from Toby Martin 2008-08-23 03:19:44 MDT --- (In reply to comment #4 from Toby Martin)

Created an attachment (id=235098) --> (https://bugzilla.novell.com/attachment.cgi?id=235098) [details] Contents of /var/log/YaST2 from sdb1 after installation from live CD

To reproduce the problem I set the contents of the SUSE Linux 10.0 installation on sda back to their 'original' state before I first tried the sdb installation using the live CD. I repeated the installation from live CD, allowing Yast to do what it felt best, the settings all look sensible enough to me. After a reboot the following is the computer's only response: Grub loading stage 1.5. Grub loading, please wait Error 25 And that's it. Now the computer can only be booted using an alternative boot source, like the super grub disk. I have uploaded the YaST2 logs as above and will leave the computer in its invalid state in case you need further information. Thanks for your attention. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=413135 User tobysubs@gmx.com added comment https://bugzilla.novell.com/show_bug.cgi?id=413135#c7 --- Comment #7 from Toby Martin 2008-08-23 03:33:18 MDT --- Requested information provided. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=413135 User jsrain@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=413135#c9 --- Comment #9 from Jiri Srain 2008-08-27 04:57:53 MDT --- Looking at the logs, I found everything correct. Would it be possible to also attach /etc/grub.conf, /boot/grub/device.map and /boot/grub/menu.lst from the 11.0 system? How do you intend to boot the 11.0 system? You installed its bootloader to MBR of /dev/sda - this is where you have the 10.0 loader as well (according to your repair step). This obviously cannot work, you need to install those bootloaders to separate locations (and as long as the one of 10.0 is primary, you need to link the 11.0 from it). The original error 25 points to something incorrect in the created files (unrecognized command) - having a look at them could help, anyway from the experience I have so far I don't think that I will find something wrong. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=413135 User tobysubs@gmx.com added comment https://bugzilla.novell.com/show_bug.cgi?id=413135#c10 Toby Martin changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|tobysubs@gmx.com | --- Comment #10 from Toby Martin 2008-09-02 00:37:04 MDT --- Created an attachment (id=236642) --> (https://bugzilla.novell.com/attachment.cgi?id=236642) /mnt/opensuse11/etc/grub.conf -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=413135 User tobysubs@gmx.com added comment https://bugzilla.novell.com/show_bug.cgi?id=413135#c12 --- Comment #12 from Toby Martin 2008-09-02 00:38:03 MDT --- Created an attachment (id=236644) --> (https://bugzilla.novell.com/attachment.cgi?id=236644) /mnt/opensuse11/boot/grub/device.map -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=413135 User tobysubs@gmx.com added comment https://bugzilla.novell.com/show_bug.cgi?id=413135#c14 --- Comment #14 from Toby Martin 2008-09-02 00:49:26 MDT --- In answer to your specific points above - I'm far from an expert in booting Linux, honestly I don't have any interest in becoming one, so my answers come with some caveats. The MBR of /dev/sda was, as far as I know, installed with the Suse 10.0 system. This loads grub which presents the grub boot menu when the computer boots. I would like to preserve the 10.0 installation. On /dev/sdb is a cleanly formatted disk, with a full install Suse 11.0 done how Yast saw best from the live CD. I would expect Yast to perform the necessary changes to all files on both disks to allow the new 11.0 installation to boot, even if this is chainloading the 11.0 installation on /dev/sdb. Yast has not correctly added the entries to configuration files on both disks to allow this system to boot. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=413135 User duwe@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=413135#c16 Torsten Duwe changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|duwe@novell.com |jsrain@novell.com Severity|Normal |Enhancement Component|Bootloader |Installation --- Comment #16 from Torsten Duwe 2008-10-15 04:33:39 MDT --- The two installations appear to fight about the MBR, you're attempting the impossible here. An installation on the second disk requires the boot path to somehow get there (Windoze BTW plays especially poor on disks 2 and beyond). To be sure, Yast uses the MBR in this case by default. I'm not sure whether a "setup (hd0)" is correct here, or if not better a detailed "install" command should be used instead. The best way in such a scenario, when a free OS is detected on the first disk, is to ask the user to add a chainloader entry to its menu to point to the second disk, or even better, do it automatically if it can be determined how. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=413135 User duwe@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=413135#c18 Torsten Duwe changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW CC| |duwe@novell.com Info Provider|duwe@novell.com | --- Comment #18 from Torsten Duwe 2009-03-16 06:43:15 MST --- You have to install some sort of boot selector that _stays_ on the first disk, if you want to be sure. There simply is no magic bullet to kill this problem. -- 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.