Bug 868664

Please attach /var/log/anaconda/storage.log and /var/log/anaconda/program.log.  We default to using the first disk, unless you tell us otherwise.

Created attachment 631714 [details]
anaconda.storage.log

Created attachment 631715 [details]
anaconda.program.log

>Please attach /var/log/anaconda/storage.log and /var/log/anaconda/program.log.
done

> We default to using the first disk, unless you tell us otherwise.
There was no warnig or information that MBR would be writen to /dev/sdc which was not selected.  There was only /dev/sda which was selected to use fore insatation.  MBR is writen to /dev/sdc.

I would like to propose this as Final NTH.

It seems to me the user should have some control over
where -- or if -- a bootloader should be installed.

I used to install mine in sector-zero of the Fedora
partition, using the old anaconda UI, but I don't see
that possibility being offered in the new UI.

Nor do I see any option like "install no bootloader."

As the moment (Beta TC8) my main bootloader is in the
MBR of my first disk (sda) and luckily for me anaconda
is always installing its bootloader into the MBR of sdc
(my third disk, which is where I am installing F18).
So mine isn't being destroyed.

It seems to me it certainly violates the spirit, if not
the letter, of: "The installer must be able to create and
install to any workable partition layout using any file
system offered in a default installer configuration, LVM,
software, hardware or BIOS RAID, or combination of the above."

I don't see any release criteria talking about bootloaders,
directly, only in passing.  Perhaps it should be considered.

Thanks.

Reproduced with anaconda 18.29.2 and two disks:
Selecting Disk 1 in the BIOS results in Disk 2 being booted.
Selecting Disk 2 in the BIOS results in a hang with:
"Booting from Hard Disk..."

Detailed procedure:

Create two disc images with slightly different sizes so they can be unambiguously distinguished in the installer:
$ qemu-img create f18-test-1.img 11G
$ qemu-img create f18-test-2.img 12G

Start the installer with both disc images:
$ qemu-kvm -m 2048 -hda f18-test-1.img -hdb f18-test-2.img -cdrom ~/xfr/fedora/F18/F18-Beta/Final/Fedora-18-Beta-x86_64-DVD.iso -usb -vga qxl -boot menu=on -usbdevice mouse

Install to f18-test-1.img:
1.  Boot from the installer disc.
2.  Set timezone to America/Los_Angeles.
3.  Select a minimal install.
4.  Click on Installation Destination.
5.  Click on the 11G disc image.
6.  Click Done.
7.  Click Begin Installation, set a root password.
8.  After installation is complete, reboot, select Disk 1 from the BIOS, login, and verify that the timezone is Pacific (PXT) by running "date".

Install to f18-test-2.img:
1.  Reboot from the installer disc.
2.  Set timezone to America/Denver.
3.  Select a minimal install.
4.  Click on Installation Destination.
5.  Click on the 12G disc image.
6.  Click Done.
7.  Click Begin Installation, set a root password.
8.  After installation is complete, reboot, select Disk 1 from the BIOS, login, and verify that the timezone is Mountain (MXT) by running "date".

Actual results:
It is not possible to boot from f18-test-1.img. Attempting to boot from Disk 2 in the BIOS results in a hang.

Expected results:
It is possible to boot from f18-test-1.img or f18-test-2.img by selecting one or the other in the BIOS.

Created attachment 653119 [details]
[18.29.2] anaconda.log

Created attachment 653122 [details]
[18.29.2] anaconda.packaging.log

Created attachment 653123 [details]
[18.29.2] anaconda.program.log

Created attachment 653124 [details]
[18.29.2] anaconda.storage.log

Created attachment 653126 [details]
[18.29.2] syslog

Created attachment 653127 [details]
[18.29.2] anaconda-ks.cfg

[snippet from attached anaconda.storage.log]
...
13:23:51,662 INFO storage: bootloader stage1 target device is sda
13:23:51,663 INFO storage: bootloader stage2 target device is sdb1
13:23:51,665 DEBUG storage: new default image: <pyanaconda.bootloader.LinuxBootLoaderImage object at 0x7f2e6e5477d0>
13:23:55,385 INFO storage: bootloader.py: used boot args: rd.lvm.lv=fedora/swap rd.lvm.lv=fedora00/root rd.dm=0 rd.lvm.lv=fedora00/swap $([ -x /usr/sbin/rhcrashkernel-param ] && /usr/sbin/rhcrashkernel-param || :) rd.md=0 rd.luks=0 rhgb quiet

Flóki: I agree with Paul[1] that this bug should be an F18 blocker. If you agree, you can propose this bug as an F18 blocker by adding the F18Blocker bug alias[2] to the blocks list for this bug.

Release criteria that could apply:

F18 Final:[3]
8. The installer must be able to create and install to any workable partition layout using any file system offered in a default installer configuration, LVM, software, hardware or BIOS RAID, or combination of the above 
https://fedoraproject.org/wiki/Fedora_18_Final_Release_Criteria

F18 Beta:
9. The installer must be able to complete an installation using automatic partitioning to a validly-formatted disk with sufficient empty space, using the empty space and installing a bootloader but leaving the pre-existing partitions and data untouched 
https://fedoraproject.org/wiki/Fedora_18_Beta_Release_Criteria

F18 Alpha:
19. When booting a system installed without a graphical environment, or when using a correct configuration setting to cause an installed system to boot in non-graphical mode, the system should boot to a state where it is possible to log in through at least one of the default virtual consoles 
https://fedoraproject.org/wiki/Fedora_18_Alpha_Release_Criteria

[1] Comment 5.
[2] http://fedoraproject.org/wiki/BugZappers/HouseKeeping/Trackers
[3] Thanks, Paul -- Comment 5.

(In reply to comment #5)
...
> It seems to me the user should have some control over
> where -- or if -- a bootloader should be installed.
...

Bug 867469 - f18b tc4 anaconda (graphical) there is no option to not to install a boot loader

Created attachment 653250 [details]
screenshot showing grub "error: no such device" message and grub prompt

If you reinstall to Disk 2, booting from Disk 1 fails with a grub error message:
error: no such device: <device UUID not transcribed>
Entering rescue mode...
grub rescue> _

Booting from Disk 2 succeeds, and the reinstalled system is booted.

Tip: When reinstalling, set the timezone to one not already used, so that the reinstalled system can be identified after it is booted.

Created attachment 653257 [details]
[18.29.2] anaconda.storage-1.log after reinstalling to Disk 2

[snippet from attached anaconda.storage-1.log]
...
22:06:53,243 INFO storage: bootloader stage1 target device is sdb
22:06:53,243 INFO storage: bootloader stage2 target device is sdb1
22:06:53,245 DEBUG storage: new default image: <pyanaconda.bootloader.LinuxBootLoaderImage object at 0x7f49b98a3f10>
22:06:56,389 INFO storage: bootloader.py: used boot args: rd.lvm.lv=fedora00/root rd.dm=0 rd.lvm.lv=fedora00/swap $([ -x /usr/sbin/rhcrashkernel-param ] && /usr/sbin/rhcrashkernel-param || :) rd.md=0 rd.luks=0 rhgb quiet

I cannot reproduce this with the F18 Beta DVD plus an updates image containing everything done since beta.  Can you please retest with the next DVD image made and verify?  Thanks.

(In reply to comment #18)
> I cannot reproduce this with the F18 Beta DVD plus an updates image
> containing everything done since beta.  Can you please retest with the next
> DVD image made and verify?  Thanks.

Ok now.
Tried 
Fedora-18-TC1-x86_64-Live-Desktop.iso
Fedora-18-TC1-x86_64-DVD.iso

Great, thanks for retesting.