Bug 1940

Did you install grub2 record to MBR? It may not work installed in partition.

To provide a better output, you should boot system in live mode, start draklive-install from konsole and when installer fails to install bootloader, copy output from konsole and paste it here.

This looks very similar to bug #1239.

(In reply to comment #1)
> Did you install grub2 record to MBR? It may not work installed in partition.
I don't remember any choice about MBR, I installed in "default" mode.


(In reply to comment #3)
> This looks very similar to bug #1239.
May be, not sure because I can't read anything in the photo.


(In reply to comment #2)
> To provide a better output, you should boot system in live mode, start
> draklive-install from konsole and when installer fails to install
> bootloader, copy output from konsole and paste it here.
As soon as I'll have back the computer I'll try.

I confirm the bug with friend's AMD computer and Fresh R1 586

(In reply to comment #1)
> Did you install grub2 record to MBR? It may not work installed in partition.
Can't select "mbr" in interface

(In reply to comment #2)
> To provide a better output, you should boot system in live mode, start
> draklive-install from konsole and when installer fails to install
> bootloader, copy output from konsole and paste it here.
In live mode draklive-install fail before grub2 setup

Install in MBR = install in sdX (like sda, sdb, etc). If you has gpt system install in automate mode not possible.

What fail? Before grub install there is similar coping file in HDD.

(In reply to comment #8)
> Install in MBR = install in sdX (like sda, sdb, etc). If you has gpt system
> install in automate mode not possible.
only sda in case.

I had same issue while installing GNOME edition recently. I have two hard disks, /sda and /sdb. On /sdb I have WindowsXP and ROSA KDE so I was installing the GNOME ed to /sda but I thought it would be better to have GRUB installed on /sdb. So installing GNOME ed to some partitions on /sda I indicated /dev/sdb for the bootloader to be installed. So I got the same error, it could not install GRUB2 there.

maybe the problem is with incorrect exit from windows, when NTFS parition was not correctly "closed" ?

Cannot say exactly but at that moment I haven't touched Windows for some months already, wine works fine in ROSA. But it seems to be closely related to the Windows installation on destination drive, since everybody affected by the bug have Windows on destination drives. Cannot say also if NTFS partition has to do something with it since I have ROSA KDE on that drive, too, and some file-store on reiserfs also. It makes 3 partitions in total on /dev/sdb.

(In reply to comment #12)
> maybe the problem is with incorrect exit from windows, when NTFS parition
> was not correctly "closed" ?
No. I correct exit from windows. Marathon's grub setup without errors.

Marathon has grub1, legacy grub. What may be ok for legacy grub is not ok for grub2.

Btw, after this error the ROSA KDE installation on /dev/sdb was broken. I reinstalled GNOME with GRUB on /dev/sda and after that it could nicely boot into Windows but could not boot into KDE. The problem resulted to be that UUID of the KDE partition specified in GRUB2 config was correct, so GRUB was working fine but after that the img of KDE system was searching for wrong UUID. I ran dracut from chroot on that partition and after that it was able to boot but with lots of errors from systemctl, which I could not defeat and fix. Hope this info helps. somehow.

Same problem at this config while installing ROSA Fresh R1:

Mainboard: ASUS P8H61Pro with EFI and two harddisks with 500 Gb and 1 Tb capacity.

ROSA was installed at first 500 Gb HDD with preinstalled Windows 7 Home Premium.

Disks configuration:

[root@localhost ~]# fdisk -l

Disk /dev/sda: 500.1 GB, 500107862016 bytes, 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x06b94949

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *        2048      206847      102400    7  HPFS/NTFS/exFAT
/dev/sda2          206848   204799999   102296576    7  HPFS/NTFS/exFAT
/dev/sda3       204800000   831641599   313420800    7  HPFS/NTFS/exFAT
/dev/sda4       831643596   976768064    72562234+   5  Extended
Partition 4 does not start on physical sector boundary.
/dev/sda5       831643648   856826774    12591563+  83  Linux
/dev/sda6       856829952   865003859     4086954   82  Linux swap / Solaris
/dev/sda7       865007616   976768064    55880224+  83  Linux

Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes, 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xc3145809

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1        88148656  1953520064   932685704+   7  HPFS/NTFS/exFAT
/dev/sdc2   *          63    78156224    39078081    7  HPFS/NTFS/exFAT

Drive /dev/sdb this is installation flashdrive with ROSA.

After succesful installing of ROSa Grub2 not installed with ioctl error. Manual install of Grub2 using ROSA Wiki not help for me. Any ideas?

If you boot in EFI mode, try this guide
http://wiki.rosalab.ru/ru/index.php/%D0%A3%D1%81%D1%82%D0%B0%D0%BD%D0%BE%D0%B2%D0%BA%D0%B0_ROSA_%D0%BD%D0%B0_EFI/UEFI

*** Bug 1239 has been marked as a duplicate of this bug. ***

*** Bug 1709 has been marked as a duplicate of this bug. ***

*** Bug 2621 has been marked as a duplicate of this bug. ***

Please check the problem for new release
http://mirror.rosalab.ru/rosa/rosa2014.1/iso/ROSA.Fresh.R4/

We believe that this issue is fixed since ROSA Desktop Fresh R4. At least the same problem on Asus Zenbook mentioned in bug #1239 has disappeared with modern ROSA releases.

If you still experience some problems with ROSA installation, feel free to reopen this bug or create a new one.