Bug 895644 - BootLoaderError: bootloader install failed
Summary: BootLoaderError: bootloader install failed
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 18
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:3cd15f7ea4e32dfc1076c026350...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-15 17:36 UTC by mterry
Modified: 2014-02-05 14:52 UTC (History)
56 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-05 14:52:38 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: anaconda.log (18.09 KB, text/plain)
2013-01-15 17:37 UTC, mterry
no flags Details
File: environ (872 bytes, text/plain)
2013-01-15 17:37 UTC, mterry
no flags Details
File: ifcfg.log (1.04 KB, text/plain)
2013-01-15 17:37 UTC, mterry
no flags Details
File: messages (325.00 KB, text/plain)
2013-01-15 17:37 UTC, mterry
no flags Details
File: packaging.log (144 bytes, text/plain)
2013-01-15 17:37 UTC, mterry
no flags Details
File: program.log (178.75 KB, text/plain)
2013-01-15 17:37 UTC, mterry
no flags Details
File: storage.log (494.10 KB, text/plain)
2013-01-15 17:37 UTC, mterry
no flags Details
File: anaconda-tb (1.05 MB, application/octet-stream)
2013-01-15 17:37 UTC, mterry
no flags Details

Description mterry 2013-01-15 17:36:57 UTC
Description of problem:
Trying to install to USB flash disk from official 18 release.
The following was filed automatically by anaconda:
anaconda 18.37.11 exception report
Traceback (most recent call first):
  File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1540, in install
    raise BootLoaderError("bootloader install failed")
  File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1554, in write
    self.install()
  File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 2312, in writeBootLoader
    storage.bootloader.write()
  File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 135, in doInstall
    writeBootLoader(storage, payload, instClass, ksdata)
  File "/usr/lib64/python2.7/threading.py", line 504, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 91, in run
    threading.Thread.run(self, *args, **kwargs)
BootLoaderError: bootloader install failed

Additional info:
cmdline:        /usr/bin/python  /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-osimg-min --lang en_US.UTF-8
cmdline_file:   initrd=initrd0.img root=live:CDLABEL=Fedora-18-x86_64-Live-Desktop.is rootfstype=auto ro rd.live.image quiet  rhgb rd.luks=0 rd.md=0 rd.dm=0  BOOT_IMAGE=vmlinuz0 
executable:     /sbin/anaconda
hashmarkername: anaconda
kernel:         3.6.10-4.fc18.x86_64
other involved packages: python-libs-2.7.3-13.fc18.x86_64
package:        anaconda-18.37.11-1.fc18.x86_64
product:        Fedora
release:        Fedora release 18 (Spherical Cow)
type:           libreport
version:        18

Comment 1 mterry 2013-01-15 17:37:00 UTC
Created attachment 678920 [details]
File: anaconda.log

Comment 2 mterry 2013-01-15 17:37:02 UTC
Created attachment 678921 [details]
File: environ

Comment 3 mterry 2013-01-15 17:37:04 UTC
Created attachment 678922 [details]
File: ifcfg.log

Comment 4 mterry 2013-01-15 17:37:07 UTC
Created attachment 678923 [details]
File: messages

Comment 5 mterry 2013-01-15 17:37:08 UTC
Created attachment 678924 [details]
File: packaging.log

Comment 6 mterry 2013-01-15 17:37:10 UTC
Created attachment 678925 [details]
File: program.log

Comment 7 mterry 2013-01-15 17:37:13 UTC
Created attachment 678926 [details]
File: storage.log

Comment 8 mterry 2013-01-15 17:37:18 UTC
Created attachment 678927 [details]
File: anaconda-tb

Comment 9 Chris Lumens 2013-01-16 20:34:15 UTC
07:22:37,725 ERR program: /usr/sbin/grub2-bios-setup: warning: Attempting to install GRUB to a disk with multiple partition labels.  This is not supported yet..
07:22:37,730 ERR program: /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..
07:22:37,731 ERR program: /usr/sbin/grub2-bios-setup: error: will not proceed with blocklists.

Comment 10 Martin Božič 2013-01-18 14:25:04 UTC
I tried to install Fedora 18 on my PC. The new Anaconda installer went well until it began to install bootloader.

Package: anaconda-18.37.11-1.fc18.x86_64
OS Release: Fedora release 18

Comment 11 Yupeng Chang 2013-01-20 18:40:01 UTC
Install on SSD, failed to install bootloader

Package: anaconda-18.37.11
OS Release: Fedora release 18

Comment 12 dev 2013-01-20 22:52:16 UTC
hy guys!
I am also facing a similar problem. I am trying to install fedora 18 and the installer freezes when bootloader is to be installed. The progress bar shows no reaction, other things work fine apart from response from the installer. Installation freezes in installing the boot loader stage. During installation of the software no problem is found whatsoever.

My laptop config is :
lenovo g460
360gb hard disk
2gb RAM
core i3 processor 1st generation.
h20 BIOS.


Package: anaconda-18.37.11-1.fc18.i686
Architecture: i686
OS Release: Fedora release 18

Comment 13 fidgonco 2013-01-20 23:23:21 UTC
La instalci'on corre sin ningun problema llega a 100% y al iniciar la configuracion del gestor de arranque aparece el error. Lo mismo ocurria con la version 17

Package: anaconda-18.37.11-1.fc18.x86_64
OS Release: Fedora release 18

Comment 14 Manish 2013-01-24 09:26:01 UTC
Installing every version of Fedora like 17 i386 or X86_64 or Fedora 18 X86_64...Bootloader is unable to install.May be because My linux parition was formated by Windows disk management program by mistake.Is there any solution.

Package: anaconda-18.37.11
OS Release: Fedora release 18

Comment 15 Alfredo 2013-01-25 19:58:50 UTC
No clue how this happened. First time trying to use Fedora and it won't install. I tried in Spanish first but it had a problem with the ASCII unicode, so I tried in English and it has this bootloader problem. Now I can't enter my Windows partition either, even though I haven't touched the configuration of that partition. I downloaded Fedora from the official website and burned it with K3B on Ubuntu 10.04. Would be thankfull of your help.

Package: anaconda-18.37.11-1.fc18.x86_64
OS Release: Fedora release 18

Comment 16 Mateusz 2013-01-29 00:06:43 UTC
error occured during bootloader instalation. instalation faild

Package: anaconda-18.37.11-1.fc18.i686
Architecture: i686
OS Release: Fedora release 18

Comment 17 meher.tanmay3 2013-01-29 10:56:25 UTC
I am also not able to figure out how this is happening.

I have windows7 and fedora 16 (side by side) previously installed on my system and fedora was set the default to open if any key was not pressed.
then i tried to install fedora 18.
but it showed the same error for bootloader.
The bootloader was on MBR.

Then i thought this might be a problem and as i have installed both os side by side may be the bootloader is not able to recognise.

so, i backed up my data and completely format my system (deleting every drive i have created) and installed fedora 18. this was only solution i got, though destructive.

it is working fine now.
i have not tried yet to install windows 7 side by side though.

:-)

Comment 18 gregjo 2013-01-29 21:58:56 UTC
I'm trying to figure out if I should piggyback this bug report. The description says "Trying to install to USB flash disk from official 18 release." I'm not trying to install to an external device. I'm attempting to install the i386 F18 image to the HD of a netbook, which is partitioned like this:
1 200MB EFI
2 60GB	ntfs (Win7)
3 168GB	empty
4 100GB hfs+
5 60GB  ext4 /
6 60GB  hfs+
7 15GB  fat32
8 15GB	fat32
9 15GB	fat32
10 4GB	swap

Yeah, I'm triple booting (Win/Mac/Linux). I had it working fine with F17. But no joy with F18.

I selected partition 1 as the BIOS_BOOT partition. I put "/" on partition 5. I selected partition 10 as swap. The installer proceeded and was near the end. Eventually I got the same error. (Well, at least I saw the line 1540 in bootloader.py.)

Comment 19 Ciprian Khlud 2013-01-30 08:40:21 UTC
It happened in both installers (DVD and Gnome 64 bit spin). Other Linuxes (mostly Linux Mint & Suse) do install. This DVD installed in a VBox session too.

The installation of Grub2 fails


Package: anaconda-18.37.11-1.fc18.x86_64
OS Release: Fedora release 18

Comment 20 rabindranath 2013-01-31 01:24:34 UTC
Attempted to install F18 from DVD. Installing bootloader failed

Package: anaconda-18.37.11
OS Release: Fedora release 18

Comment 21 Jose Mauro de Rezende 2013-01-31 01:56:19 UTC
Installing FC 18 in an HP notebook  Probook 6360b.
I tried several times with several combinations.
Fedora Core 15 does install very fine. Could not install eather FC 16 and 17. Fedora Core 8 install but the graphic window do not work.
Ubuntu 11.10 does works.
It fails during the bootloader installation. 
No ideia why it happens.
In case you have some clue, let me know. I will install FC-15 in the meantime.
JMauro.


Package: anaconda-18.37.11
Architecture: i686
OS Release: Fedora release 18

Comment 22 jkchavarrom2015 2013-02-01 06:33:53 UTC
El error se presenta en la instalacion de Fedora 18.

Luego de finalizar la instalacion de archivos, en el momento en el que esta "Instalando gestor de arranque" se presenta el error.


Package: anaconda-18.37.11-1.fc18.x86_64
OS Release: Fedora release 18

Comment 23 rabindranath 2013-02-02 00:14:12 UTC
After reading a few posts on Google and the Fedora 18 install guide pages they pointed to I retried the install. This time I changed the filesystem type to BTRFS as suggested and everything worked. My box is up and running.

Comment 24 baju.ravi 2013-02-03 14:55:07 UTC
Failing to install a proper boot while installing Fedora 18 alongside Windows 7.

 (Similarities appear after installing Ubuntu alongside Windows 7, as 'error disk reading' while trying to load Windows partition from GRUB2. Boot-loader fails to solve anything as MBR perturbates GRUB2, and vice versa)



Package: anaconda-18.37.11-1.fc18.x86_64
OS Release: Fedora release 18

Comment 25 Jose Mauro de Rezende 2013-02-04 12:11:29 UTC
I read the comment #23 from rabindranath and changed the filesystem type to BTRFS but did not work too.
Jose Mauro de Rezende


Package: anaconda-18.37.11
OS Release: Fedora release 18

Comment 26 Nitikesh Bhavsar 2013-02-06 18:51:23 UTC
I happened while installtion of boot loader. I dont know the details

Package: anaconda-18.37.11-1.fc18.x86_64
OS Release: Fedora release 18

Comment 27 Nitikesh Bhavsar 2013-02-06 18:53:31 UTC
I happened during boot loader installtion.

Package: anaconda-18.37.11-1.fc18.x86_64
OS Release: Fedora release 18

Comment 28 Vinju K G 2013-02-08 18:54:12 UTC
error duuring installing bootloader in HP envy 4 laptop

Package: anaconda-18.37.11-1.fc18.x86_64
OS Release: Fedora release 18

Comment 29 Chris Murphy 2013-02-09 10:45:24 UTC
I triggered this same error with md raid1 with two GPT disks. Only one BIOS Boot partition is created in Manual Partitioning, but anaconda calls grub2-install for each drive. It succeeds with one, fails on the other, then crashes.

I think at some point the logic of various BIOS Boot and EFI System partitions, can be sorted out and dealt with behind the scene even with Manual Partitioning. I don't think even Manual Partitioning users should have to deal with these things, they aren't user domain. They should simply be created automatically as needed.

Comment 30 setare_2970 2013-02-14 06:17:41 UTC
I use 64bit windows 7 in hp laptop. I have just two partion one for win and another for linux. also a systemfile partion and hptools partition.
I keep recieving the boot loader problem while installing fedora18.
I have tried a lots of way to prevent this error.
I am using F15 and i tried installation but this error occured.
Also, I deleted Fedora partition on my windows and again i have this error.
Also, I deleted boot partion on windows and again this error.
I don't know what else should i do. I have searched but no answer!
Please help as soon as possible.


Package: anaconda-18.37.11
OS Release: Fedora release 18

Comment 31 Rich 2013-02-15 20:22:34 UTC
<editorial note> Anaconda really has gone downhill, and I don't appreciate the removal of detailed information and choices that used to be available during install. In particular, the lack of choices about bootloader installation and lack of information about partitions during repartitioning -- such as device nodes for BTRFS partitions, the lack of ability to resize and move partitions, the inability to install from multiple package sources, and the lack of a repair capability (which would have been useful for my failed booloader install -- what, I have to install all over again to retry?) to be particularly egregioius.<\editorial note>

I installed F18 from DVD, and during installation of the bootloader (apparently, based on the progress bar), it barfed.

Details of interest: I was installing F18 to a MacBook Pro with OSX on it. During partition setup I reformatted the EFI partition to BIOS_Boot. I did not have a network connection setup during this install. I have reFind (fork of reFit) installed on the OSX partition to initate the boot. 


Package: anaconda-18.37.11
OS Release: Fedora release 18

Comment 32 Chris Murphy 2013-02-15 23:17:49 UTC
(In reply to comment #30)
(In reply to comment #31)
Bug reports aren't for tech support. They're to document new information to isolate the cause, and fix, for the bug. Neither of these comments contribute to that end. I suggest taking this to fedoraforum.org.

(In reply to comment #31)
Wow, I find this to be particularly obnoxious and useless. Nevertheless, feel free to publicly post your observations on forum, then PM me the URL. Macs have special considerations on Fedora due to their unique (non-standard) EFI. Reformatting the ESP to be BIOS Boot is definitely incorrect.

Comment 33 Rich 2013-02-16 05:34:35 UTC
I am not requesting tech support, I am a) providing feedback to developers on what I consider to be design regressions, and b) providing as much contextual detail as possible for my bug report, which I am filing because anaconda failed to finish.

I am sorry you find this offensive, but it is certainly not useless.

The forum is not for providing feedback to developers or documenting design or code defects. That's what bugzilla is for.

If my system didn't boot after setup because of user error, then I stand corrected, and certainly appreciate your advice (but I was not soliciting it). However, good code handles user errors gracefully, and gives users an opportunity to correct them. My 2 cents.

Comment 34 Chris Murphy 2013-02-16 15:32:53 UTC
(In reply to comment #33)
Fully 80% of your complaints in #31 have nothing to do with *this* bug, but are broad anaconda complaints. You haven't documented any specific design or code defects. It's not so much offensive as it is as useful as a used baby diaper.

I've done ~20 installs to two MacbookPro models, not one of those installs had an outcome similar to your vague description. Useful reports include things like describing storage pre-install state and providing a step by step such that others can reproduce your results, and attaching install logs. That's what bugzilla is for, not posting editorializations.

Conversations on design aesthetic, not bugs, goes on the anaconda@ list. But as you're clearly confused on how to actually install this on a Mac, I still think this goes on a forum.

Comment 35 Rich 2013-02-16 20:45:56 UTC
I made no mention of aesthetics. I made mention of regressions. Features that for many, many users are necessary for a successful install, but are no longer available because the functionality was removed for the sake of aesthetics (since you bring it up).

I submitted my crash report using anaconda. If anaconda lost my the crash data, that's not my problem. I submitted it, you're welcome.

Forget about the fact that my Mac install was unsuccessful, or that I don't know how to install it on my Mac (true) -- I'll figure that out, thank you. Focus on the fact that I successfully installed F17 on the same Mac, using anaconda and not only did anaconda not crash, the computer booted fine afterwards. Focus on the fact that anaconda CRASHED. Not on whether I should or should not have reformatted the ESP. I didn't submit the bug looking for advice on where I screwed up, I did it so you would be aware that anaconda crashed.

I submitted a full crash report, and added my general comments about my anaconda experience, clearly marked as editorial, in the comments tab, along with what I did to create the crash (as instructed by anaconda). If anaconda lost the crash data, not my problem. If bugzilla lost the crash data, not my problem. If anaconda collected the wrong information for you, not my problem. Geez! If you wanted my pre-install storage state, you should have asked for it instead of attacking me. I'll note that I am not the only one who experienced anaconda crashing during installation of the bootloader, many of whom have multiboot configurations, and several of which are Macs. Rich OUT.

Comment 36 vinod.bhabal 2013-02-19 12:29:00 UTC
I was installing Fedora 18 on my notebook

I have Acer Aspire 4738 
Core i3-380M
2 GB DDR3 Memory
500 GB HDD
No other OS was installed when I was performing this installation

I came across this error while "installing bootloader" during the installation


Package: anaconda-18.37.11-1.fc18.x86_64
OS Release: Fedora release 18

Comment 37 Piotr 2013-02-23 09:57:23 UTC
MBP 8.1
=======================


Package: anaconda-18.37.11
OS Release: Fedora release 18

Comment 38 92antwilliams 2013-02-23 12:46:42 UTC
Tried installing live disc to hard drive
After selecting enlgish with english keyboard
Selected to remove and replace old fedora 16 installation
Attempted to install
Bug was reported


Package: anaconda-18.37.11-1.fc18.x86_64
OS Release: Fedora release 18

Comment 39 David Jansen 2013-02-28 11:10:51 UTC
Installation of Fedora 18 on a system which previously had Fedora 16 running. During setup, I chose to reformat / and /var (and keep the /data1 and /data2 partitions). All other options are from the kickstart file that we use for all installations here at the department.

Package: anaconda-18.37.11
OS Release: Fedora release 18

Comment 40 Irwin 2013-03-01 07:44:19 UTC
Planning a Dual booting, but finishing Fedora 18 failed. 

Package: anaconda-18.37.11-1.fc18.i686
Architecture: i686
OS Release: Fedora release 18

Comment 41 David Jansen 2013-03-01 15:14:26 UTC
After my failed install yesterday, I reinstalled Fedora 16, which worked fine. Then I tried Fedora 18 again, which failed in the same way as before.

We have other computers of the same type (HP xw4600) here. The main difference, as far as I could see, is that the computer where it keeps failing, has no cd/dvd drive and no other removable media (except through usb). That may be a coincidence, but I'll build in a dvd drive and give it another try. if that makes any difference, I'll report back here.

Comment 42 Chris Murphy 2013-03-01 17:09:30 UTC
This bug has more than one cause. You need to check the anaconda-tb, or program.log to find out where the installer failed and hints as to why. Or post them.

Comment 43 ademilson 2013-03-02 02:13:10 UTC
the bootloader dont installer interrupt.

Package: anaconda-18.37.11-1.fc18.i686
Architecture: i686
OS Release: Fedora release 18

Comment 44 Jan Jaarsma 2013-03-02 08:11:16 UTC
Installing Fedora 18 X64 live CD on my Laptop HP Pavilion DV6.
Installing software goes well. But trying to install the bootlader results in this error.
Partitioning is chosen automatic (LVM) It chooses a root partition, a home partition and a swap partition. There is sufficient room (90 Gb).
There a still to 3 partitions (SDA1, 2 and 3) on the disk for windows 8.


Package: anaconda-18.37.11-1.fc18.x86_64
OS Release: Fedora release 18

Comment 45 Adilson Favero 2013-03-05 22:49:24 UTC
Error on installing Fedora 18

Package: anaconda-18.37.11-1.fc18.x86_64
OS Release: Fedora release 18

Comment 46 Jay Arnold 2013-03-09 17:02:27 UTC
Attempting a Fedora 18 installation to 16GB USB flash drive, encountered this error at the bootloader install stage.

Package: anaconda-18.37.11-1.fc18.x86_64
OS Release: Fedora release 18

Comment 47 tarik.rifai 2013-03-13 18:58:52 UTC
This happens everytime I try to install Fedora 18 using a bootable USB with Fedora Live Desktop

Package: anaconda-18.37.11-1.fc18.x86_64
OS Release: Fedora release 18

Comment 48 ktr1024 2013-03-15 17:23:15 UTC
Over the past two days I have tried to install Fedora 18 on my laptop (hp dm3-1030us) from a live USB. Windows 7 is already on the hard drive and I am trying to dual boot, not do a clean install. 
So, I left about 25 gb of unallocated space and told anaconda to partition as it would and install. It installs fine until it gets to the "Installing bootloader" step when it freezes for a second and then returns an error. I have tried to install several times after completely deleting the partitions and reflashing the Fedora 18 iso to my flash drive. Every single time it fails to install the bootloader. 
I've searched quite extensively on the internet and no one seems to have found a solution. This problem has existed since Fedora 16 at least, according to the plethora of complaints on the linux forums I have seen. It seems that this problem only rears its ugly head when one is trying to dual boot a recent version of Fedora and either Windows 7 or Windows 8 (with the Windows distro already installed). 
I think that Fedora is on my computer (minus GRUB) and that if I can edit the MBR in Windows or manually install GRUB/GRUB 2, then I can get this dual boot a bootloader to recognize the partition. 


Package: anaconda-18.37.11-1.fc18.x86_64
OS Release: Fedora release 18

Comment 49 Chris Murphy 2013-03-15 20:04:23 UTC
(In reply to comment #48)
Multiple failures lead to this error. You need to look at the logs, in particular program.log to find out the exact grub-install related error. Your explanation doesn't make sense because this very bug lists entries from people not using Windows. If you don't want to look at the installer logs, you can probably induce the error by booting from Netinst or DVD in rescue mode, let it find and mount your system, chroot /mnt/sysimage and then 'grub2-install /dev/sdX' for the target hard drive. If the message complains of blocklists, I'll bet $1 that 'fdisk -l' shows the 1st partition start LBA on the target disk is something other than 2048, and there simply isn't enough room to embed GRUB in such a small MBR gap.

Comment 50 cloudedsoul13linux 2013-03-21 11:54:23 UTC
I installed Fedora 18 from a live media DVD onto my laptop that already had Windows 7 pre-installed. Linux installed fine up until the point it was installing the bootloader. It errored out and now neither Windows nor Linux will boot. I can't recover from the recovery partition because it cannot access it. I tried reinstalling windows from an installation disc, but Windows doesn't recognize ANY hard drives on the computer. I tried redoing the Linux installation (Linux does see the hard drive and partitions on it) but get the same problem once it gets to the bootloader portion. Help please; my laptop is a shell.

Package: anaconda-18.37.11-1.fc18.x86_64
OS Release: Fedora release 18

Comment 51 VJ 2013-03-25 13:25:10 UTC
Bootloader installer bug in Fedora 18 default distro as well as KDE desktop version.

Package: anaconda-18.37.11-1.fc18.i686
Architecture: i686
OS Release: Fedora release 18

Comment 52 v753 2013-03-25 18:51:49 UTC
just wait until end of fedora install

Package: anaconda-18.37.11-1.fc18.x86_64
OS Release: Fedora release 18

Comment 53 jeremy_millsaps 2013-03-26 06:11:58 UTC
Attempting to install Fedora 18 on a HP ProBook 4730s laptop.  This computer originally had a dual boot with Fedora 16 and Windows 7.  Downloaded a live image on a seperate computer using Fedora 17 and created a LiveUSB.  Inserted LiveUSB in this computer and turned on power.  Selected LiveUSB as boot device and allowed to complete Boot.  As Live System User selected Install to Harddrive.  Leave language as default English.  Leave timezone as default USA eastern time.  Leave keyboard as default English.  Selected hardrive and found to be default boot device and left as default.  Due to prior attempts there currently is not enough room to install.  Selected previous attempted Fedora 18 partition and set to delete.  Clicked continue.  Anaconda installed software and started post installation processes.  Fails every time at Install Boot loader.  Attempted later with a new copy of the Live Image and a new USB stick with same results.  Just for curiosity attemted to boot without the LiveUSB.  Fedora 18 appears to boot correctly all the way up to the sign on screen then crashes.  Booting this way does not recognize the Windows 7 partition or ask to boot Windows.  

Package: anaconda-18.37.11-1.fc18.i686
Architecture: i686
OS Release: Fedora release 18

Comment 54 ZISHAN MOHSIN 2013-04-06 17:39:37 UTC
This problem arises when i was installing fedora 18.

Package: anaconda-18.37.11-1.fc18.x86_64
OS Release: Fedora release 18

Comment 55 Joachim Schröder 2013-04-08 07:08:41 UTC
Using 2 disks and putting /boot on a RAID mirror probably  produced this error. 

Background:
For data safety and quick recover without reconfiguration on disk fail in a cheap home server setup (without a HW raid), I want to use mirror RAID for /boot and an encrypted mirror RAID partition holding LVM with /, /home etc.
That way the system can be rebooted from the surviving disk after removal of the failed disk without going through any manual bootloader restore actions.


Package: anaconda-18.37.11
OS Release: Fedora release 18

Comment 56 Elias Reyes 2013-04-22 07:23:41 UTC
sucedio a mitad de proceso de instalacion del sistema

Package: anaconda-18.37.11-1.fc18.x86_64
OS Release: Fedora release 18

Comment 57 Bob 2013-04-23 09:48:12 UTC
Installed Win XP on 50GB partition

Tried to install Fedora 18 on remainder of 240GB disk

Failed.


Package: anaconda-18.37.11-1.fc18.i686
Architecture: i686
OS Release: Fedora release 18

Comment 58 Szőke Károly 2013-05-03 17:51:51 UTC
post setup, while install boot loader

Package: anaconda-18.37.11-1.fc18.x86_64
OS Release: Fedora release 18

Comment 59 Wanderley Junior 2013-05-11 18:40:45 UTC
This problem has occurred only in gnome instal, on kde no haves problem...

<b>Notebook HP dm4-1075br <\b>


Package: anaconda-18.37.11-1.fc18.x86_64
OS Release: Fedora release 18

Comment 60 Maaris 2013-05-19 10:28:45 UTC
Instaling fedora 18, with dual boot (winxp), used LVM automatic part.



Package: anaconda-18.37.11-1.fc18.x86_64
OS Release: Fedora release 18

Comment 61 Fedora End Of Life 2013-12-21 10:23:47 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 62 Fedora End Of Life 2014-02-05 14:52:45 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.