[Bug 809798] New: Grub2 fails to install properly during NEW system installation
https://bugzilla.novell.com/show_bug.cgi?id=809798 https://bugzilla.novell.com/show_bug.cgi?id=809798#c0 Summary: Grub2 fails to install properly during NEW system installation Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: m407@mail.ru QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20100101 Firefox/19.0 12.3 installation fails to install bootloader with the message like "initrd image creation failure". Reproducible: Always Steps to Reproduce: 1. install system from openSUSE DVD 12.3 x64_86 2. don't set any options 3. in partitioning format your root Actual Results: Installation fails. Some messages from /var/log/zypp/history # 2013-03-14 22:49:01 grub2-2.00-19.5.2.x86_64.rpm installed ok # Additional rpm output: # warning: /etc/default/grub created as /etc/default/grub.rpmnew # Perl-Bootloader: 2013-03-14 18:49:01 <3> pbl-0767.2 Core::RunCommand.1642: Error: Command '/usr/sbin/grub2-install --target=i386-pc --force --skip-fs-probe "(hd0,2)" >/var/log/YaST2/y2log_bootloader 2>&1' failed with code 256 and output: /usr/sbin/grub2-bios-setup: warning: File system `ext2' doesn't support embedding. # /usr/sbin/grub2-bios-setup: warning: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and their use is discouraged.. # /usr/sbin/grub2-bios-setup: error: blocklists are invalid. Expected Results: Successful intallation I've got no UEFI, GPT or other obsticals. Used standard options for installation with automatic configuration except partitioning. It was an upgrade with formatted root. Got the same results on 2 my computers. Solved by launching upgrade from distribution DVD and reinstalling kernel and grub. PS. Installation on KVM works fine. -- 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=809798 https://bugzilla.novell.com/show_bug.cgi?id=809798#c FeiXiang Zhang <fxzhang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fxzhang@suse.com AssignedTo|bnc-team-screening@forge.pr |mchang@suse.com |ovo.novell.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=809798 https://bugzilla.novell.com/show_bug.cgi?id=809798#c1 --- Comment #1 from Winfrid Tschiedel <Winfrid.Tschiedel@t-online.de> 2013-03-22 14:01:40 UTC --- Created an attachment (id=531220) --> (http://bugzilla.novell.com/attachment.cgi?id=531220) my installation logs I am not sure if my failed installation has the same reason as in this incident. My installation hangs after approximate 94% of the installation - after this I can boot the system, but login failed, because /etc/passwd and /etc/shadow have not set up in a proper way. After fixing this and setting up the network everything seems to be correct. It seems to be a problem when I install grub2 boot-loader installation with grub did not show this trouble. -- 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=809798 https://bugzilla.novell.com/show_bug.cgi?id=809798#c2 --- Comment #2 from Андрей Кувшинов <m407@mail.ru> 2013-03-22 20:50:45 UTC --- I also reproduced this bug while upgrading my ThinkPad T420. Root was formated (it is on LVM) and boot is on primary partition formated to ext4. -- 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=809798 https://bugzilla.novell.com/show_bug.cgi?id=809798#c3 --- Comment #3 from Michael Chang <mchang@suse.com> 2013-04-18 08:14:24 UTC --- This is my understanding from reading the grub2-bios-setup utility. That "blocklists are invalid" error originated from the checking right after the blocklists of core.img are determined by ioctl(). The checking is to read the file (core.img) thru firmware read (biosdisk INT#13) according to the blocklist and compare with the result of fread from standard library. If they don't match the above error will emit and program aborts. Upstream has suggested install to MBR to get rid of the blocklist mess, if it doesn't work well for you. -- 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=809798 https://bugzilla.novell.com/show_bug.cgi?id=809798#c4 --- Comment #4 from Michael Chang <mchang@suse.com> 2013-04-18 08:57:22 UTC --- (In reply to comment #3)
This is my understanding from reading the grub2-bios-setup utility.
That "blocklists are invalid" error originated from the checking right after the blocklists of core.img are determined by ioctl(). The checking is to read the file (core.img) thru firmware read (biosdisk INT#13) according to the
Sorry, above is wrong (I thought it could be LRMI to do that but no) It's not the biosdisk but the hostdisk which set lower level block read (with ioctl) so there's no bios call involves 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.
https://bugzilla.novell.com/show_bug.cgi?id=809798 https://bugzilla.novell.com/show_bug.cgi?id=809798#c5 --- Comment #5 from Андрей Кувшинов <m407@mail.ru> 2013-04-18 13:01:33 UTC --- There is some meaningful point in comment #3. Installation into to MBR only does solve the problem. But if you want to boot also from boot partition or root you are in trouble. -- 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