Created attachment 649446 [details] anaconda-tb-s8slmO Description of problem: Attempting to install to a dual boot system with Windows XP. The installer appears to be putting "/" on the unpartitioned, "hidden" 8 MB disk space after the extended partition. Version-Release number of selected component (if applicable): anaconda-18.29.2-1.fc18.i686 F18-Beta-RC1 Live CD on a USB stick How reproducible: Reproduced three times by removing the partition with gparted and rebooting between tests. Steps to Reproduce: 1. Install Windows XP and then Linux for a dual-boot configuration. From previous experiments, the Win XP installer leaves an unpartitioned, 8 MB space after the extended partition. 2. Start the Fedora installer. 3. Select Standard Partitions. 4. Click "+" to create a new "/" mount point. Leave the capacity empty. NB: The disk has ~8 GB free in a separate space. 5. Begin Installation. Actual results: Almost immediately after installing software starts, the install fails with: PayloadInstallError: rsync exited with code 12 See Bug 868755, Comment 72. Expected results: Install succeeds. Additional info: The partition is sda3.
$ cat disk-info-1.txt [root@localhost xfr]# parted /dev/sda print free Model: ATA TOSHIBA MK6026GA (scsi) Disk /dev/sda: 60.0GB Sector size (logical/physical): 512B/512B Partition Table: msdos Disk Flags: Number Start End Size Type File system Flags 1 32.3kB 19.9GB 19.9GB primary ntfs 19.9GB 19.9GB 31.2kB Free Space 2 19.9GB 60.0GB 40.1GB extended lba 5 19.9GB 21.0GB 1045MB logical fat32 6 21.0GB 51.9GB 31.0GB logical ext3 51.9GB 59.5GB 7526MB Free Space 7 59.5GB 60.0GB 535MB logical linux-swap(v1) 60.0GB 60.0GB 295kB Free Space 3 60.0GB 60.0GB 7340kB primary ext4 boot 60.0GB 60.0GB 590kB Free Space [root@localhost xfr]# fdisk -l /dev/sda Disk /dev/sda: 60.0 GB, 60011642880 bytes, 117210240 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: 0x00051344 Device Boot Start End Blocks Id System /dev/sda1 63 38909429 19454683+ 7 HPFS/NTFS/exFAT /dev/sda2 38909491 117194174 39142342 f W95 Ext'd (LBA) /dev/sda3 * 117194752 117209087 7168 83 Linux /dev/sda5 38909493 40949684 1020096 b W95 FAT32 /dev/sda6 40949748 101450474 30250363+ 83 Linux /dev/sda7 116150013 117194174 522081 82 Linux swap / Solaris
Created attachment 649548 [details] screenshot showing partitioning with gparted Here is a reproducer using gparted and a VM disc image: Create an 11 GB disc image: $ qemu-img create f18-test-2.img 11G Partition it this way: 1. 1 GB ext4 primary partition. 2. 10 GB extended partition that ends 8 MB before the end of the disc image. 5. 1 GB ext4 logical partition located at the end of the extended partition. See attached screenshot. Boot the Live CD and start the installer. In Installation Options, select Standard Partition for the partition scheme. In Manual Partitioning, create "/", but do not specify a capacity. The installer puts "/" on a new primary partition created from the 8 MB space after the extended partition. Further, the installer allows installation to begin. Tested with: $ qemu-kvm -m 2048 -hda f18-test-1.img -hdb f18-test-2.img -cdrom ~/xfr/fedora/F18/F18-Beta/RC1/Fedora-18-Beta-x86_64-Live-Desktop.iso -usb -vga qxl -boot menu=on -usbdevice mouse f18-test-1.img has F18 and gparted installed. (gparted is not on the Live CD.) f18-test-2.img is the install target.
For the record, I was able to install by first using gparted to create a partition in the 8 GB free space.
Please try again with F18 and let us know if this is still broken. Thanks.
Created attachment 694152 [details] [18.37.11] anaconda-tb-all.log Reproduced with anaconda 18.37.11. The installer puts root on the 8 MiB unallocated space after the extended partition by creating sdb3. Installation cannot be started, because the Begin Installation button is not sensitive, although no error triangle is displayed. The attached log file was captured with the Installation Summary displayed using: # pkill -USR2 -o anaconda Tested with: $ qemu-img create f18-test-3.img 11G $ qemu-kvm -m 2048 -hda f18-test-1.img -hdb f18-test-3.img -cdrom ~/xfr/fedora/F18/Fedora-18-x86_64-Live-Desktop.iso -vga qxl -boot menu=on -usbdevice mouse NB: The install target is hdb (f18-test-3.img).
Created attachment 694153 [details] screenshot showing Installation Summary with no error triangles, but Begin Installation button insensitive
Created attachment 694155 [details] screenshot showing Manual Partitioning with root on 8 MiB partition sdb3 The capacity field for the new root partition was left blank, so that the maximum available space would be allocated.
(In reply to comment #6) > Created attachment 694153 [details] > screenshot showing Installation Summary with no error triangles, but Begin > Installation button insensitive Did you not see the error text at the bottom of the screen?
Is the GUI going to be consistent about displaying the error triangle, or is it going to force the user to infer which spoke needs to be reentered? NB: The reproducer from Comment 2 leaves ~9 GiB free space, so regardless of whether the error triangle is displayed or not, the message at the bottom of the screen is severely misleading, if not actually wrong, when it refers to "filesystems" and not free space. Please see the screenshot in Attachment 649548 [details]: screenshot showing partitioning with gparted
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.
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.