Between TC1 and release of F16 Alpha, something must have changed to the worse with regard to installing GRUB to a partition's primary sector. Partitioning hasn't changed. TC1 managed to install GRUB to /dev/sda3. Anaconda now reports failure to install, and I've found this on virtual console:
/usr/sbin/grub2-setup: warn: Attempting to install GRUB to a partitionless disk or to a partitionj. This is a BAD idea..
/usr/sbin/grub2-setup: warn: Embedding is not possible. GRUB can only be installed in this setup using blocklists. However, blocklists are UNRELIABLE and their use is discouraged..
/usr/sbin/grub2-setup: error: will not proceed with blocklists.
Bug or feature?
On Thu, 2011-08-25 at 22:56 +0200, Michael Schwendt wrote:
Between TC1 and release of F16 Alpha, something must have changed to the worse with regard to installing GRUB to a partition's primary sector. Partitioning hasn't changed. TC1 managed to install GRUB to /dev/sda3. Anaconda now reports failure to install, and I've found this on virtual console:
/usr/sbin/grub2-setup: warn: Attempting to install GRUB to a partitionless disk or to a partitionj. This is a BAD idea..
/usr/sbin/grub2-setup: warn: Embedding is not possible. GRUB can only be installed in this setup using blocklists. However, blocklists are UNRELIABLE and their use is discouraged..
/usr/sbin/grub2-setup: error: will not proceed with blocklists.
Bug or feature?
On Thu, 2011-08-25 at 15:59 -0500, David Lehman wrote:
On Thu, 2011-08-25 at 22:56 +0200, Michael Schwendt wrote:
Between TC1 and release of F16 Alpha, something must have changed to the worse with regard to installing GRUB to a partition's primary sector. Partitioning hasn't changed. TC1 managed to install GRUB to /dev/sda3. Anaconda now reports failure to install, and I've found this on virtual console:
/usr/sbin/grub2-setup: warn: Attempting to install GRUB to a partitionless disk or to a partitionj. This is a BAD idea..
/usr/sbin/grub2-setup: warn: Embedding is not possible. GRUB can only be installed in this setup using blocklists. However, blocklists are UNRELIABLE and their use is discouraged..
/usr/sbin/grub2-setup: error: will not proceed with blocklists.
Bug or feature?
Also see:
https://fedoraproject.org/wiki/Common_F16_bugs#grub2-partition-fail
On Thu, 25 Aug 2011 15:20:54 -0700, AW (Adam) wrote:
On Thu, 2011-08-25 at 15:59 -0500, David Lehman wrote:
On Thu, 2011-08-25 at 22:56 +0200, Michael Schwendt wrote:
Between TC1 and release of F16 Alpha, something must have changed to the worse with regard to installing GRUB to a partition's primary sector. Partitioning hasn't changed. TC1 managed to install GRUB to /dev/sda3. Anaconda now reports failure to install, and I've found this on virtual console:
/usr/sbin/grub2-setup: warn: Attempting to install GRUB to a partitionless disk or to a partitionj. This is a BAD idea..
/usr/sbin/grub2-setup: warn: Embedding is not possible. GRUB can only be installed in this setup using blocklists. However, blocklists are UNRELIABLE and their use is discouraged..
/usr/sbin/grub2-setup: error: will not proceed with blocklists.
Bug or feature?
:) One step forward, two steps back ...
Also see:
https://fedoraproject.org/wiki/Common_F16_bugs#grub2-partition-fail
Doesn't work for me.
1st, quotes are missing:
# grub2-install --force (hd0,3) -bash: syntax error near unexpected token `('
2nd, it still refuses to install:
# grub2-install --force '(hd0,3)' /usr/sbin/grub2-setup: warn: Attempting to install GRUB to a partitionless disk or to a partition. This is a BAD idea.. /usr/sbin/grub2-setup: warn: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and their use is discouraged.. Installation finished. No error reported.
3rd, GRUB 2 %doc NEWS file mentions the partition numbering scheme has changed to count from 1 instead of 0. The Wiki should mention that or recommend normal /dev/sdXY notation, which also fails, however (and which is the reason why I don't try to edit the Wiki myself):
# grub2-install --force /dev/sda3 /usr/sbin/grub2-setup: warn: Attempting to install GRUB to a partitionless disk or to a partition. This is a BAD idea.. /usr/sbin/grub2-setup: warn: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and their use is discouraged.. Installation finished. No error reported.
On Fri, 26 Aug 2011 17:18:56 +0200, me wrote:
Doesn't work for me.
# grub2-install --grub-setup=/bin/true /dev/sda3 Installation finished. No error reported.
# grub2-install --grub-setup=/bin/true '(hd0,3)' Installation finished. No error reported.
On Fri, Aug 26, 2011 at 11:37 AM, Michael Schwendt mschwendt@gmail.com wrote:
On Fri, 26 Aug 2011 17:18:56 +0200, me wrote:
Doesn't work for me.
# grub2-install --grub-setup=/bin/true /dev/sda3 Installation finished. No error reported.
# grub2-install --grub-setup=/bin/true '(hd0,3)' Installation finished. No error reported.
AFAIK, this won't be bootable, unless grub-install has run successfully before, because that all that the above commands are doing is populating "/boot/grub2/".
It's grub2-setup that does the heavy lifting of embedding boot.img in the PBR and pointing at core.img from boot.img.
On Fri, 26 Aug 2011 11:47:15 -0400, TH (Tom) wrote:
# grub2-install --grub-setup=/bin/true '(hd0,3)' Installation finished. No error reported.
AFAIK, this won't be bootable, unless grub-install has run successfully before, because that all that the above commands are doing is populating "/boot/grub2/".
it's from a comment in bz 728742
With warnings telling me something "is not possible", I stopped reading them again and missed the "Installation finished. No error reported." at the end. It simply got lost in the noise. No line prefix for the final status message. When using --force it is too late to warn about something that is "UNRELIABLE" and "discouraged".
On Fri, Aug 26, 2011 at 12:52 PM, Michael Schwendt mschwendt@gmail.com wrote:
On Fri, 26 Aug 2011 11:47:15 -0400, TH (Tom) wrote:
# grub2-install --grub-setup=/bin/true '(hd0,3)' Installation finished. No error reported.
AFAIK, this won't be bootable, unless grub-install has run successfully before, because that all that the above commands are doing is populating "/boot/grub2/".
it's from a comment in bz 728742
With warnings telling me something "is not possible", I stopped reading them again and missed the "Installation finished. No error reported." at the end. It simply got lost in the noise. No line prefix for the final status message. When using --force it is too late to warn about something that is "UNRELIABLE" and "discouraged".
As I said in my earlier email, unless grub-install has run successfully (which it has in your case because you used "--force"), using "...--grub-setup=/bin/true..." will not install grub.
On Sat, 27 Aug 2011 07:50:39 -0400, TH (Tom) wrote:
On Fri, 26 Aug 2011 11:47:15 -0400, TH (Tom) wrote:
# grub2-install --grub-setup=/bin/true '(hd0,3)' Installation finished. No error reported.
AFAIK, this won't be bootable, unless grub-install has run successfully before, because that all that the above commands are doing is populating "/boot/grub2/".
it's from a comment in bz 728742
With warnings telling me something "is not possible", I stopped reading them again and missed the "Installation finished. No error reported." at the end. It simply got lost in the noise. No line prefix for the final status message. When using --force it is too late to warn about something that is "UNRELIABLE" and "discouraged".
As I said in my earlier email, unless grub-install has run successfully (which it has in your case because you used "--force"), using "...--grub-setup=/bin/true..." will not install grub.
I didn't mean to disagree.
On Sat, Aug 27, 2011 at 10:47 AM, Michael Schwendt mschwendt@gmail.com wrote:
On Sat, 27 Aug 2011 07:50:39 -0400, TH (Tom) wrote:
On Fri, 26 Aug 2011 11:47:15 -0400, TH (Tom) wrote:
# grub2-install --grub-setup=/bin/true '(hd0,3)' Installation finished. No error reported.
AFAIK, this won't be bootable, unless grub-install has run successfully before, because that all that the above commands are doing is populating "/boot/grub2/".
it's from a comment in bz 728742
With warnings telling me something "is not possible", I stopped reading them again and missed the "Installation finished. No error reported." at the end. It simply got lost in the noise. No line prefix for the final status message. When using --force it is too late to warn about something that is "UNRELIABLE" and "discouraged".
As I said in my earlier email, unless grub-install has run successfully (which it has in your case because you used "--force"), using "...--grub-setup=/bin/true..." will not install grub.
I didn't mean to disagree.
Sorry, misunderstood you.
On Fri, 2011-08-26 at 17:18 +0200, Michael Schwendt wrote:
On Thu, 25 Aug 2011 15:20:54 -0700, AW (Adam) wrote:
On Thu, 2011-08-25 at 15:59 -0500, David Lehman wrote:
On Thu, 2011-08-25 at 22:56 +0200, Michael Schwendt wrote:
Between TC1 and release of F16 Alpha, something must have changed to the worse with regard to installing GRUB to a partition's primary sector. Partitioning hasn't changed. TC1 managed to install GRUB to /dev/sda3. Anaconda now reports failure to install, and I've found this on virtual console:
/usr/sbin/grub2-setup: warn: Attempting to install GRUB to a partitionless disk or to a partitionj. This is a BAD idea..
/usr/sbin/grub2-setup: warn: Embedding is not possible. GRUB can only be installed in this setup using blocklists. However, blocklists are UNRELIABLE and their use is discouraged..
/usr/sbin/grub2-setup: error: will not proceed with blocklists.
Bug or feature?
:) One step forward, two steps back ...
Also see:
https://fedoraproject.org/wiki/Common_F16_bugs#grub2-partition-fail
Doesn't work for me.
1st, quotes are missing:
# grub2-install --force (hd0,3) -bash: syntax error near unexpected token `('
2nd, it still refuses to install:
# grub2-install --force '(hd0,3)' /usr/sbin/grub2-setup: warn: Attempting to install GRUB to a partitionless disk or to a partition. This is a BAD idea.. /usr/sbin/grub2-setup: warn: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and their use is discouraged.. Installation finished. No error reported.
It is not refusing to install. It's just warning you that it thinks what you are telling it to do is a bad idea. Notice that it says at the end "No error reported"?
3rd, GRUB 2 %doc NEWS file mentions the partition numbering scheme has changed to count from 1 instead of 0. The Wiki should mention that
Good idea.
or recommend normal /dev/sdXY notation, which also fails, however (and which is the reason why I don't try to edit the Wiki myself):
# grub2-install --force /dev/sda3 /usr/sbin/grub2-setup: warn: Attempting to install GRUB to a partitionless disk or to a partition. This is a BAD idea.. /usr/sbin/grub2-setup: warn: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and their use is discouraged.. Installation finished. No error reported.
Again, this is not a failure.
On Fri, Aug 26, 2011 at 12:20 AM, Adam Williamson awilliam@redhat.com wrote:
On Thu, 2011-08-25 at 15:59 -0500, David Lehman wrote:
On Thu, 2011-08-25 at 22:56 +0200, Michael Schwendt wrote:
Between TC1 and release of F16 Alpha, something must have changed to the worse with regard to installing GRUB to a partition's primary sector. Partitioning hasn't changed. TC1 managed to install GRUB to /dev/sda3. Anaconda now reports failure to install, and I've found this on virtual console:
/usr/sbin/grub2-setup: warn: Attempting to install GRUB to a partitionless disk or to a partitionj. This is a BAD idea..
/usr/sbin/grub2-setup: warn: Embedding is not possible. GRUB can only be installed in this setup using blocklists. However, blocklists are UNRELIABLE and their use is discouraged..
/usr/sbin/grub2-setup: error: will not proceed with blocklists.
Bug or feature?
Also see:
https://fedoraproject.org/wiki/Common_F16_bugs#grub2-partition-fail
Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net
This is a really mayor but and I don't understand it why it fails when I tried grub2-install --force then grub installs without issues :( This should have been a blocker Fedora bug.
On Mon, 2012-02-13 at 17:21 +0100, valent.turkovic@gmail.com wrote:
This is a really mayor but and I don't understand it why it fails when I tried grub2-install --force then grub installs without issues :( This should have been a blocker Fedora bug.
anaconda already uses grub2-install --force, and installation to a partition does not *generally* fail - it's failing in your specific case for some reason I don't know, but it's not the case that *any* attempt to install grub2 to a partition with F16 fails.
On Thu, Aug 25, 2011 at 10:59 PM, David Lehman dlehman@redhat.com wrote:
On Thu, 2011-08-25 at 22:56 +0200, Michael Schwendt wrote:
Between TC1 and release of F16 Alpha, something must have changed to the worse with regard to installing GRUB to a partition's primary sector. Partitioning hasn't changed. TC1 managed to install GRUB to /dev/sda3. Anaconda now reports failure to install, and I've found this on virtual console:
/usr/sbin/grub2-setup: warn: Attempting to install GRUB to a partitionless disk or to a partitionj. This is a BAD idea..
/usr/sbin/grub2-setup: warn: Embedding is not possible. GRUB can only be installed in this setup using blocklists. However, blocklists are UNRELIABLE and their use is discouraged..
/usr/sbin/grub2-setup: error: will not proceed with blocklists.
Bug or feature?
I did Fedora 16 Respin iso install with all latest packages, including latest Anaconda package, and still had this issue.
There were two ntfs partitions (Windows 7 + data partition) and 30 GB of free space.
From 30GB free space I created
/root # 200 MB, ext4 /swap # 2.5 GB, swap / # 8.0 GB, ext4 /home # 19 GB, btrfs
grub2 install fails miserably :(
Are there any updates regarding this bug?
-
Adam Williamson -
David Lehman -
Michael Schwendt -
Tom H -
Tom Horsley -
Valent Turkovic