Description of problem: Yesterday I was helping a student with F21 installation. He had a completely full disk (Windows installation, 4 partitions, allegedly as provided by manufacturer and untouched), but anaconda displayed it a completely empty! That means the partition spoke overview, and also custom partition spoke - no existing partitions were shown. That's a serious problem, because not only it would not be able to install alongside Windows, it would probably erase the disk contents completely, destroying all previous data. I collected all the logs and hope it will help you debug the issue. I looked at the disk contents in several applications. gnome-disks showed the disk contents without any problems. gparted worked as well, but reported some warnings and errors (but honestly, I always see some warnings from gparted, so that doesn't need to mean much). Version-Release number of selected component (if applicable): F21 Alpha Workstation x86_64 Live anaconda-21.48.6-1.fc21.x86_64 python-blivet-0.62-1.fc21.noarch How reproducible: always, for *that particular disk* Steps to Reproduce: 1. check existing boot contents - boot windows (ok), display partitions in gnome-disks (ok) 2. run installer 3. see that anaconda reports roughly 590GB disk with 590GB free space, i.e. completely empty disk Actual results: the disk is reported as empty Expected results: the disk should be reported as full Additional info: F20 anaconda exhibited the same problem. Originally I wanted to install F20, then tried F21, the same problem.
Created attachment 942620 [details] anaconda.log
Created attachment 942621 [details] program.log
Created attachment 942622 [details] storage.log
Created attachment 942623 [details] system journal
Created attachment 942624 [details] rpm -qa output
Created attachment 942625 [details] fdisk output on that disk
Created attachment 942626 [details] gdisk output on that disk
For some reason parted is refusing to instantiate a parted.Disk on sda. We sure don't give much information in these circumstances.
Can you run parted -s /dev/sda u s p on it? Since libparted is what is used that's the most useful output to see. If there's a bug in parted it should also show up when using the cmdline tool.
I'm not really sure what state this disk is in, hopefully you haven't let gdisk 'repair' it yet. I'd like to see the start and end of the disk: dd if=/dev/sda of=first.64.sda.bin bs=512 count=64 dd if=/dev/sda of=last.128.sda.bin bs=512 skip=1250263600
I'm sorry, I don't have access to that machine anymore. I hoped that those gathered logs and output would be enough. I forgot about parted, sorry. If we can't find the source of the problem from these logs, we will need to close this bug.
python-blivet-0.61.4-1 will raise an exception if it finds a partition on a disk that parted says does not contain a disklabel.