[Bug 413135] New: openSUSE 11. 0 cannot be booted using Grub when installed on second hard disk
https://bugzilla.novell.com/show_bug.cgi?id=413135 Summary: openSUSE 11.0 cannot be booted using Grub when installed on second hard disk Product: openSUSE 11.0 Version: Final Platform: i686 OS/Version: SuSE Linux 10.0 Status: NEW Severity: Normal Priority: P5 - None Component: Booting AssignedTo: jsrain@novell.com ReportedBy: tobysubs@gmx.com QAContact: jsrain@novell.com Found By: Customer The computer is booted from SATA disk sda which contains sda1: Windows 2000 sda2: Swap sda3: SuSE Linux 10.0 A second SATA disk has been added sdb and the computer rebooted using the openSUSE 11.0 live CD and the installation on sdb completed using YaST. Following this the computer does not reboot and produces a Grub error 25. This can be repaired by adding '(hd1) /dev/sdb' to /boot/grub/device.map on sda and 'setup (hd0)' from grub but nothing can be done to boot the openSUSE 11.0 installation on sdb. There is a long discussion on linuxquestions.org http://www.linuxquestions.org/questions/susenovell-60/grub-problems-after-in... and on opensuse forums http://forums.opensuse.org/install-boot-login/390323-grub-load-fail.html and this constellation of disks has never been used successfully with Grub and I conclude this must be a bug somewhere in the way openSUSE is installed. -- 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#c1 Jiri Srain <jsrain@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |tobysubs@gmx.com --- Comment #1 from Jiri Srain <jsrain@novell.com> 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 tobysubs@gmx.com added comment https://bugzilla.novell.com/show_bug.cgi?id=413135#c2 Toby Martin <tobysubs@gmx.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|tobysubs@gmx.com | --- Comment #2 from Toby Martin <tobysubs@gmx.com> 2008-08-06 14:57:21 MDT --- Hi Jiri, Your understanding is correct, I added /dev/sdb to device.map on sda3, the SUSE Linux 10.0 partition where Grub is installed. I can not upload the installation logs as I can not boot the openSUSE 11.0 installation on sdb - or can you let me know where they would be and I will try to find them. Thanks for your attention. Toby -- 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 <jsrain@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |tobysubs@gmx.com --- Comment #3 from Jiri Srain <jsrain@novell.com> 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#c4 --- Comment #4 from Toby Martin <tobysubs@gmx.com> 2008-08-23 03:15:47 MDT --- Created an attachment (id=235098) --> (https://bugzilla.novell.com/attachment.cgi?id=235098) Contents of /var/log/YaST2 from sdb1 after installation from live CD -- 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 <tobysubs@gmx.com> 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#c6 Toby Martin <tobysubs@gmx.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|tobysubs@gmx.com | --- Comment #6 from Toby Martin <tobysubs@gmx.com> 2008-08-23 03:32:05 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 tobysubs@gmx.com added comment https://bugzilla.novell.com/show_bug.cgi?id=413135#c7 --- Comment #7 from Toby Martin <tobysubs@gmx.com> 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 tobysubs@gmx.com added comment https://bugzilla.novell.com/show_bug.cgi?id=413135#c8 --- Comment #8 from Toby Martin <tobysubs@gmx.com> 2008-08-23 04:01:32 MDT --- .. and as stated above the computer can be booted again to SuSE 10.0 by adding the following fix, as stated above: This can be repaired by adding '(hd1) /dev/sdb' to /boot/grub/device.map on sda However nothing can be done to bring the sdb based openSUSE 11.0 installation to life. -- 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 <jsrain@novell.com> 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 Jiri Srain <jsrain@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |tobysubs@gmx.com -- 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 <tobysubs@gmx.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|tobysubs@gmx.com | --- Comment #10 from Toby Martin <tobysubs@gmx.com> 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#c11 --- Comment #11 from Toby Martin <tobysubs@gmx.com> 2008-09-02 00:37:39 MDT --- Created an attachment (id=236643) --> (https://bugzilla.novell.com/attachment.cgi?id=236643) /mnt/opensuse11/boot/grub/menu.lst -- 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 <tobysubs@gmx.com> 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#c13 --- Comment #13 from Toby Martin <tobysubs@gmx.com> 2008-09-02 00:40:47 MDT --- Thanks for your comment but I hope something is wrong as it is not possible to boot this system and adding a new disk for a clean install doesn't strike me as an unusual thing to do. This issue has also defeated the communities of both the openSUSE support forum and linuxquestions.org, as listed above. In any case it is not expressly forbidden in the install notes, perhaps it should be and at least the supported installations better documented. Attached are the files you request. -- 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 <tobysubs@gmx.com> 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 jsrain@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=413135#c15 Jiri Srain <jsrain@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|jsrain@novell.com |duwe@novell.com --- Comment #15 from Jiri Srain <jsrain@novell.com> 2008-09-02 03:08:25 MDT --- All the configuration files look well to me, the output of GRUB's installation looks also OK. Torsten, is there any way you could figure out why GRUB failed? -- 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 <duwe@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|duwe@novell.com |jsrain@novell.com Severity|Normal |Enhancement Component|Bootloader |Installation --- Comment #16 from Torsten Duwe <duwe@novell.com> 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 jsrain@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=413135#c17 Jiri Srain <jsrain@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |duwe@novell.com --- Comment #17 from Jiri Srain <jsrain@novell.com> 2008-10-30 09:26:09 MDT --- That's right, however, the question is why Linux installed on 2nd disk with GRUB Stage1 in MBR of the first disk fails. If GRUB was booted properly after the installation, it could load both 11.0 and 10.0. The only idea I have is that there may be an issue with GRUB having 1st stage on different disk than 2nd stage, otherwise I have no idea. I don't think that what you suggest is a good idea - this approach would lead into problems when 10.0 on sda would get reinstalled/removed. openSUSE always tries to find other operating systems and add them to the bootloader menu - as you can see in attached menu.lst from 11.0, it did so (and even found a Linux installation on /dev/sdb2 - which is kind of strange to me). -- 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 <duwe@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW CC| |duwe@novell.com Info Provider|duwe@novell.com | --- Comment #18 from Torsten Duwe <duwe@novell.com> 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.
https://bugzilla.novell.com/show_bug.cgi?id=413135 User jsrain@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=413135#c19 Jiri Srain <jsrain@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #19 from Jiri Srain <jsrain@novell.com> 2009-03-17 03:17:11 MST --- Thanks! Toby, the best way would be to have the /boot partition of the 2nd Linux installation on the first disk as well. Otherwise, you seem to need to (manually) set the sda's GRUB to boot GRUB from sdb and configure sdb's GRUB not to touch sda at all. The device map on sdb needs to be in sync with whether or not you do remapping of BIOS IDs in the chainloader for sdb. Optionally, you can copy-paste the GRUB section from sdb to menu.lst on sda, but this will break during kernel update, you will need to update it after each. Sorry for not helping much, but your setup is pretty unusual, I cannot help more here. -- 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.
participants (1)
-
bugzilla_noreply＠novell.com