Hello All,
I am trying to do a clean install of Fedora 19 x86_64 to a disc which has Fedora 17 installed. I alternate between two 500 GB discs for each release.
I chose to repeat the fc17 partitioning scheme, 524MB /boot, 442GB /home, 47GB /, and swap.
The install goes OK until it reports "installing bootloader", which never ends...or for 30-40 mins, I haven't waited longer before forcing a poweroff.
The Fedora 19 iso checksums OK.
I see a bug reporting this behaviour, but the fix appears to require much more than ordinary user knowledge, and wasn't explained.
Can someone please detail, for an ordinary user, how to solve this?

Cheers,
Terry

Let's see a link to the bug report.
Some time back Fedora required the /boot to be (much) larger for the installer to use as a work-space. Make it a Gig - might work, might not.
Cycling through the virtual terminal should show you any relevant messages - or allow you to get at the logs (as per the install guide).

OK, here is the bug report I found https://bugzilla.redhat.com/show_bug.cgi?id=981358
There is some discussion there about how some got past the problem, but appears to be doing things that are not in the realm of an ordinary user.

I also used the partitioning I reported with fc18, so 500MB has been OK here thus far.
When installing I don't see any virtual terminal, just the installer screen.
I'll have another try, use 1Gb for /boot, and see if I can get anything from the logs.

Thanks for the response.

Cheers,
Terry

Well I've tried a number of times, all without success.
I used gparted to reformat the drive and set up a /boot of 1GB. Install hung at "installing bootloader".
I let the installer decide on the partitioning (it chose 500 MB for /boot), and again it hung at "installing bootloader".
After one of the unsuccessful attempts was terminated, I booted into fc18 (on other disc) and checked out what had been installed, and /boot was empty.
I saw some advice (fc19 release notes I think) re using rescue mode to run /sbin/grub-install /dev/sdx, to install grub if the install didn't boot, but that probably doesn't apply here as there is nothing in /boot! Also, I noted that there is no /sbin/grub-install, only /sbin/grub2-install.
This has worn me down a bit. Not sure what to do. It does seem to me that the release iso needs an update, as one has to be able to get a bit further than this to be able to get things started. Is a fixed/updated release iso likely to be available?
Any other options available that will get me to a bootable system?

Cheers,
Terry

With the re-write of the installer and the enforced changes to grub in F18, I too have remained at F17 everywhere.
Your problem appears related to those. I'll try an install of F19 (i386 only as that is my only "don't care" system at the moment) sometime - non efi/gpt thought too, so may not be relevant.

I'm getting to the point where I may give up on them (Fedora) again.

Edit: sorry, I was watching the footy (rugby league) while (slowly) typing - our posts crossed. I'll try an install maybe tomorrow.

I'm not still on F17...I had no trouble installing F18, and have used it since its release. I swap between 2 discs every release, to preserve my existing setup at least until I am happy with the new version.

OK, thanks.

Cheers,
Terry

Found a AMD64 laptop I no longer use, so trashed that. Told the installer to delete the current disk and use it all - never liked Win7 Home anyway ...
I was expecting it to create the disk as gpt, but it didn't - a 500MB /boot (so you were right about that) and the rest to btrfs (single partition). All installed o.k. and re-booted fine. This was from the liveCD though.

I can now report similar success.
I decided to give it a couple more tries. The first via the shell, and that led to a text mode install which was painful, but it too resulted in an interminable time "installing bootloader", so I quit. The next attempt was to using the graphical installer again, and letting it make it's own decisions, except for me deciding I wanted "standard partitioning", which meant ext4, and I walked away and left it...and it eventually completed the install.
So, the problem may have been a lack of patience on my part, although I do think all the previous attempts had run quite a bit longer than this final attempt did.

Thanks for your efforts to help with this.

Cheers,
Terry