[Bug 765198] New: grub2 did not install on "/dev/sda1" from the live KDE version. It worked from the DVD
https://bugzilla.novell.com/show_bug.cgi?id=765198 https://bugzilla.novell.com/show_bug.cgi?id=765198#c0 Summary: grub2 did not install on "/dev/sda1" from the live KDE version. It worked from the DVD Classification: openSUSE Product: openSUSE 12.2 Version: Beta 1 Platform: i686 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: nrickert@ameritech.net QAContact: jsrain@suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20100101 Firefox/12.0 During install, grub2 failed to install. The message advised against installing on a partition. Perhaps install to MBR would have worked, but I prefer to avoid that. The installer default was to install on "/boot" which is "/dev/sda1" on the system where I was installing. I had to switch to grub1 to get a good install. A later try with installing from the DVD, but disabling "install from images", grub2 installed just fine on "/boot" (or /dev/sda1), same computer. This was all with the 32 bit version. The same problem happened on a second install attempt. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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=765198
https://bugzilla.novell.com/show_bug.cgi?id=765198#c1
Michael Chang
https://bugzilla.novell.com/show_bug.cgi?id=765198
https://bugzilla.novell.com/show_bug.cgi?id=765198#c2
--- Comment #2 from Neil Rickert
https://bugzilla.novell.com/show_bug.cgi?id=765198
https://bugzilla.novell.com/show_bug.cgi?id=765198#c3
Michael Chang
https://bugzilla.novell.com/show_bug.cgi?id=765198
https://bugzilla.novell.com/show_bug.cgi?id=765198#c4
Neil Rickert
https://bugzilla.novell.com/show_bug.cgi?id=765198
https://bugzilla.novell.com/show_bug.cgi?id=765198#c5
--- Comment #5 from Neil Rickert
https://bugzilla.novell.com/show_bug.cgi?id=765198
https://bugzilla.novell.com/show_bug.cgi?id=765198#c6
--- Comment #6 from Michael Chang
https://bugzilla.novell.com/show_bug.cgi?id=765198
https://bugzilla.novell.com/show_bug.cgi?id=765198#c7
--- Comment #7 from Neil Rickert
In general you shouldn't check "Boot from /boot" when /boot is logical partition, as the generic mbr boot code couldn't bootstrap it directly.
Here are some general principles: 1: If you have more than one operating system installed, then only one of them can be booted directly. The others must be booted indirectly. 2: People who do beta testing are likely to have more than one operating system installed. 3: There is only one extended partition, so only one operating system can boot from the extended partition. 4: The active flag is only relevant to the one system (or boot manager) that is booted directly. Any installed system that is booted via another boot manager should not need an active flag (though some operating systems do seem to need that flag before they will boot). In my case, I have a booting arrangement that has worked and that I am happy with. So when I install a system for testing, I don't want it to mess up a booting arrangement that works well. In the case of my "computer 2" (a Dell laptop), I also have Windows 7 and opensuse 12.1 installed. I have an entry in the boot loader for opensuse 12.1 which chain loads to boot whatever is in "/dev/sda5". The best for me is to install Beta1 to boot from "/dev/sda5" and not set the active flag, so that I can boot it the way I am already set up for booting test systems. If I allow it to install grub some other way, then I have to change the active flag to what I want with "fdisk" and I have to use "dd" to write the boot sector to "/dev/sda5". I seem to recall that I had to go through those steps with the M3 release, because the grub install did not have enough options for what I need. -- 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=765198
https://bugzilla.novell.com/show_bug.cgi?id=765198#c8
--- Comment #8 from Michael Chang
https://bugzilla.novell.com/show_bug.cgi?id=765198
https://bugzilla.novell.com/show_bug.cgi?id=765198#c
Andreas Jaeger
https://bugzilla.novell.com/show_bug.cgi?id=765198
https://bugzilla.novell.com/show_bug.cgi?id=765198#c9
--- Comment #9 from Neil Rickert
https://bugzilla.novell.com/show_bug.cgi?id=765198
https://bugzilla.novell.com/show_bug.cgi?id=765198#c10
--- Comment #10 from Michael Chang
https://bugzilla.novell.com/show_bug.cgi?id=765198
https://bugzilla.novell.com/show_bug.cgi?id=765198#c11
--- Comment #11 from Michael Chang
2nd install - I installed only KDE. The grub2 install failed, with a message that it's a bad idea to install on a partition.
That warning is fine IMHO, because upstream not recommend installing to partition.
There was also an error message about a missing file, though that went past a bit too fast for me to be sure what file.
Yes. It should be. That's the real reason to the failure (missing device.map or grub2-mkconfig). -- 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=765198
https://bugzilla.novell.com/show_bug.cgi?id=765198#c12
--- Comment #12 from Neil Rickert
https://bugzilla.novell.com/show_bug.cgi?id=765198
https://bugzilla.novell.com/show_bug.cgi?id=765198#c13
--- Comment #13 from Michael Chang
https://bugzilla.novell.com/show_bug.cgi?id=765198
https://bugzilla.novell.com/show_bug.cgi?id=765198#c14
--- Comment #14 from Neil Rickert
https://bugzilla.novell.com/show_bug.cgi?id=765198
https://bugzilla.novell.com/show_bug.cgi?id=765198#c15
--- Comment #15 from Michael Chang
https://bugzilla.novell.com/show_bug.cgi?id=765198
https://bugzilla.novell.com/show_bug.cgi?id=765198#c16
--- Comment #16 from Michael Chang
https://bugzilla.novell.com/show_bug.cgi?id=765198
https://bugzilla.novell.com/show_bug.cgi?id=765198#c17
--- Comment #17 from Michael Chang
https://bugzilla.novell.com/show_bug.cgi?id=765198
https://bugzilla.novell.com/show_bug.cgi?id=765198#c18
--- Comment #18 from Michael Chang
https://bugzilla.novell.com/show_bug.cgi?id=765198
https://bugzilla.novell.com/show_bug.cgi?id=765198#c19
--- Comment #19 from Michael Chang
https://bugzilla.novell.com/show_bug.cgi?id=765198
https://bugzilla.novell.com/show_bug.cgi?id=765198#c20
--- Comment #20 from Neil Rickert
https://bugzilla.novell.com/show_bug.cgi?id=765198
https://bugzilla.novell.com/show_bug.cgi?id=765198#c21
--- Comment #21 from Michael Chang
I'm not entirely clear on the steps.
Do I need to setup a local server for the url? No.
Or can I store the file in a different disk partition, Yes.
and use something like dud=disk:/dev/sda1/filename Use dud=disk:/filename, for example use "dud=disk:/bug-765198_new-grub2.dud" Linuxrc would try every disk and partition in turn to locate the file in specified path.
If succeed, you could switch to console 1 via Ctrl/ALT + F1 and see the message Reading driver update: disk:/bug-765198_new-grub2.dud Loading file:/mounts/mp_0000/bug-765198_new-grub2.dud (7122kB) - 100% Driver Update: Update with grub2/grub2-efi support beta2 Driver Update added: Update with grub2/grub2-efi support beta 2
I'm assuming that this is entered on the boot options line.
Yes. And don't forget insecure=1 as the dud is not signed.
Do I then need to do a new install, or is an update install (update booting) sufficient)?
It's up to you, whatever steps you tool to reproduce your problem.
If either works, then I would probably test both - a reinstall on my faster system and an update install on an older slower system.
Go ahead. :) -- 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=765198
https://bugzilla.novell.com/show_bug.cgi?id=765198#c22
--- Comment #22 from Michael Chang
https://bugzilla.novell.com/show_bug.cgi?id=765198
https://bugzilla.novell.com/show_bug.cgi?id=765198#c23
--- Comment #23 from Michael Chang
https://bugzilla.novell.com/show_bug.cgi?id=765198
https://bugzilla.novell.com/show_bug.cgi?id=765198#c24
--- Comment #24 from Neil Rickert
https://bugzilla.novell.com/show_bug.cgi?id=765198
https://bugzilla.novell.com/show_bug.cgi?id=765198#c25
--- Comment #25 from Neil Rickert
https://bugzilla.novell.com/show_bug.cgi?id=765198
https://bugzilla.novell.com/show_bug.cgi?id=765198#c26
--- Comment #26 from Michael Chang
https://bugzilla.novell.com/show_bug.cgi?id=765198
https://bugzilla.novell.com/show_bug.cgi?id=765198#c27
--- Comment #27 from Neil Rickert
https://bugzilla.novell.com/show_bug.cgi?id=765198
https://bugzilla.novell.com/show_bug.cgi?id=765198#c28
--- Comment #28 from Michael Chang
https://bugzilla.novell.com/show_bug.cgi?id=765198
https://bugzilla.novell.com/show_bug.cgi?id=765198#c29
--- Comment #29 from Michael Chang
Btw . I'm planning to make some change to it and hopefully that we could get thing done right this time.
OH . please see my last comment in bnc#757683. Thanks. -- 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=765198
https://bugzilla.novell.com/show_bug.cgi?id=765198#c30
Michael Chang
https://bugzilla.novell.com/show_bug.cgi?id=765198
https://bugzilla.novell.com/show_bug.cgi?id=765198#c31
--- Comment #31 from Neil Rickert
https://bugzilla.novell.com/show_bug.cgi?id=765198
https://bugzilla.novell.com/show_bug.cgi?id=765198#c32
Neil Rickert
https://bugzilla.novell.com/show_bug.cgi?id=765198
https://bugzilla.novell.com/show_bug.cgi?id=765198#c33
--- Comment #33 from Michael Chang
RC1 installed in three systems. The grub2 install was without incident in all of those systems. The 1440x900 problem (from comment 27) did not show up.
Thanks. Good to know.
One thing I noticed that I did not expect - running "mkinitrd" apparently causes grub2 to be reinstalled in the boot sector. I would have expected that only "grub.cfg" would be updated.
You're right. I tried to fix that, but unfortunately lead to a disaster which renders system unbootable after updating grub2 package. Then I reverted the changes. The fix has to be thoroughly reviewed, now the process is dumb, like what we did in old days using lilo, but at lease it ensures full resistance to potential file relocation, afaics, update-bootloader has to be extend with a new interface that would just do config updating and tools like mkinitrd could use it instead of update-bootloader --refersh, which also reinstalls to bootsector. -- 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=765198
https://bugzilla.novell.com/show_bug.cgi?id=765198#c34
Michael Chang
participants (1)
-
bugzilla_noreply@novell.com