[Bug 910947] New: Upgrade from 12.3 to 13.2 GRUB didn't start on a windows linux system
http://bugzilla.opensuse.org/show_bug.cgi?id=910947 Bug ID: 910947 Summary: Upgrade from 12.3 to 13.2 GRUB didn't start on a windows linux system Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain@suse.com Reporter: gemsa@netcologne.de QA Contact: jsrain@suse.com Found By: --- Blocker: --- Created attachment 618085 --> http://bugzilla.opensuse.org/attachment.cgi?id=618085&action=edit Details of the error Dear Ladies and Gentleman, i use Windows 7 on sda and OpenSuse 12.3 on sdb. GRUB has to use the Master-Boot-Record from sda. After the installation of OpenSuse 13.2, from DVD 1, the Bootmanager can' find a Device!! This was the GRUB message: GRUB loading... Error: No such Device: e9e6225d-cd31-4d2d-abb7-1e0d5d4eec2 I tryed to reinstall the bootmanger again but got the same error. Afterwards i installed 12.3 again and GRUB worked vary well. What is the reason of version 13.2 to stop with this error? How can i solve this problem? Best Regards Dietmar Gemsa -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=910947 --- Comment #2 from Dietmar Gemsa <gemsa@netcologne.de> --- Created attachment 620061 --> http://bugzilla.opensuse.org/attachment.cgi?id=620061&action=edit details of bootloader 12.3 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=910947 --- Comment #3 from Dietmar Gemsa <gemsa@netcologne.de> --- Dear Jiri, excuse my about my delay. I was busy with an project in my company. When i bought my PC i installed Windows-7 on the first disk and afterwards OPENSUSE on the second disk. During the OPENSUSE installation GRUB was able to manipulate the MBR (on the first disk) and give my the change to decide which OS i would like to start. Before i start the upgrade to 13.2 i don't change my BIOS (boot order, fist DVD second sda) or other system parameters. Why can't use 13.2 the right disk sequece? I can't see an error in my configuration. Have a look to my new attachments please. Best Regards Dietmar -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=910947 --- Comment #4 from Dietmar Gemsa <gemsa@netcologne.de> --- Created attachment 620065 --> http://bugzilla.opensuse.org/attachment.cgi?id=620065&action=edit bootloader new -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=910947 --- Comment #5 from Jiri Srain <jsrain@suse.com> --- Getting the right sequence from the BIOS is always tricky - different BIOSes have different behavior and in any case YaST can only guess. Please, attach the logs (as I added the link to openSUSE wiki in my last comment), that will help much more than screenshots - we will be able to check exactly which configuration was written to the system. If you can add the bootloader configuration files (/boot/grub2/*), it could help even more. Thanks, Jiri -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=910947 --- Comment #6 from Dietmar Gemsa <gemsa@netcologne.de> --- Dear Jiri, i checked your link to the find out how i can save the YAST-Installer logs. I have never done this before and would like to know which chapter is the right one. Can you explain this for me? Regards Dietmar -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=910947 --- Comment #7 from Jiri Srain <jsrain@suse.com> --- Please, see the information just from the top of the page! The first paragraph's title just says: I reported a YaST2 bug, and now I am asked to "attach y2logs" (for package installation also "libzypp logging"). What does that mean, and how do I do that? and it is a good starting point. If you have any specific question, try to find it in the document, it has existed since years and most of the situations are covered there. The document contains all needed information and its purpose is not to have to explain how to get the logs again for each bugreport, unless your situation is very specific. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=910947 --- Comment #8 from Dietmar Gemsa <gemsa@netcologne.de> --- Dear Jiri, today i started a new attempt to install 13.2. After the selection of language and keyboard the install process showed the volumes to work with them: Format Partition /dev/sdb2 (20.00GiB) with btrfs Create subvolume boot/grub2/i386-pc on device /dev/sdb2 Create subvolume boot/grub2/x86_64 on device /dev/sdb2 Create subvolume opt on device /dev/sdb2 Create subvolume srv on device /dev/sdb2 Create subvolume tmp on device /dev/sdb2 Create subvolume usr/local on device /dev/sdb2 Create subvolume var/crash on device /dev/sdb2 Create subvolume var/lib/mailman on device /dev/sdb2 Create subvolume var/lib/named on device /dev/sdb2 Create subvolume var/lib/pgsql on device /dev/sdb2 Create subvolume var/log on device /dev/sdb2 Create subvolume var/opt on device /dev/sdb2 Create subvolume var/spool on device /dev/sdb2 Create subvolume var/tmp on device /dev/sdb2 Use /dev/sdb1 as swap Set mount point of /dev/sdb3 to home Is this the source of error? GRUB2 has to use the master boot record of the first phy. disk called sda. Only on this disk is the mbr and two NTFS-Windows partitions. Regards Dietmar -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=910947 Dietmar Gemsa <gemsa@netcologne.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #9 from Dietmar Gemsa <gemsa@netcologne.de> --- It was simple the wrong choice "Installation" instead of "Upgrade" during the update. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com