Please attach /tmp/anaconda.log, all of /tmp/storage.log, and /tmp/program.log.  Thanks.

Also, in the future, please open new bugs using the "New" link near the top left of the bugzilla page instead of cloning existing bugs unless there is a good reason to be cloning the bug.

Created attachment 501160 [details]
storage.log (booting with nodmraid)

Created attachment 501161 [details]
/tmp/program.log (booting with nodmraid)

Created attachment 501162 [details]
/tmp/anaconda.log (Boot with nodmraid)

(In reply to comment #2)
> Also, in the future, please open new bugs using the "New" link near the top
> left of the bugzilla page instead of cloning existing bugs unless there is a
> good reason to be cloning the bug.

Ok, I will take it in account!

What does the output of parted -l look like? And could you attach /var/log/messages as well.

(In reply to comment #3)
> Created attachment 501160 [details]
> storage.log (booting with nodmraid)

17:34:33,939 DEBUG storage: removed disk sda (id 3) from device tree
17:34:33,939 DEBUG storage: lvm filter: adding sda to the reject list
17:34:33,939 DEBUG storage: device 'sda' in ignoredDisks

It never says why, but it examined sda and didn't like it.

(In reply to comment #9)

> Disposit. Inicio    Comienzo      Fin      Bloques  Id  Sistema
> /dev/sda1   *           1        3824    30716248+   7  HPFS/NTFS
> /dev/sda2            3825       10438    53126955   83  Linux
> /dev/sda3           14226       19324    40957717+   b  W95 FAT32
> /dev/sda4           10439       19452    72404955    5  Extendida
> /dev/sda5           10439       13009    20651526   83  Linux
> /dev/sda6           13010       14225     9767488+  83  Linux
> /dev/sda7           19325       19452     1028128+  82  Linux swap / Solaris
> 
> Las entradas de la tabla de particiones no están en el orden del disco
> 

"The entries in the partition table are not in disk order."

Logical partition sda3 is inside of extended partition sda4, I think that's the first time I've seen anything like that. Usually out-of-order partitions are all primary or extended.

It looks like storage can't figure out what kind of disklabel is on sda. The output from parted -l should show this. The output from blkid might also be useful. Please attach that info to this bug.

I have this same problem with Fedora 16.

Created attachment 576211 [details]
The anaconda log from Fedora 16

[liveuser@localhost ~]$ parted -l
/dev/mapper/control: open failed: Permission denied
Failure to communicate with kernel device-mapper driver.
Warning: Unable to open /dev/sr0 read-write (Read-only file system).  /dev/sr0
has been opened read-only.
Error: Invalid partition table - recursive partition on /dev/sr0.         
Ignore/Cancel?

Created attachment 576212 [details]
Screenshot of Anaconda vs Diskutility

(In reply to comment #12)
> Created attachment 576211 [details]
> The anaconda log from Fedora 16

Please attach the following log files individually:

 storage.log
 program.log
 
Along with the output of dmesg.

Thanks.

You also need to run parted -l and blkid as root. su - will get you there from a live install.

[root@localhost ~]# parted -l
                                                                         Warning: /dev/sda contains GPT signatures, indicating that it has a GPT table.
However, it does not have a valid fake msdos partition table, as it should.
Perhaps it was corrupted -- possibly by a program that doesn't understand GPT
partition tables.  Or perhaps you deleted the GPT table, and are now using an
msdos partition table.  Is this a GPT partition table?
                                                                         Yes/No? Yes
Model: ATA WDC WD3200BEVT-6 (scsi)
Disk /dev/sda: 320GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number  Start  End  Size  File system  Name  Flags


Model: Linux device-mapper (snapshot) (dm)
Disk /dev/mapper/live-osimg-min: 4295MB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number  Start  End     Size    File system  Flags
 1      0.00B  4295MB  4295MB  ext4


Model: Linux device-mapper (snapshot) (dm)
Disk /dev/mapper/live-rw: 4295MB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number  Start  End     Size    File system  Flags
 1      0.00B  4295MB  4295MB  ext4


                                                                         Warning: Unable to open /dev/sr0 read-write (Read-only file system).
/dev/sr0 has been opened read-only.
                                                                         Error: Invalid partition table - recursive partition on /dev/sr0.

[root@localhost ~]# blkid 
/dev/loop0: TYPE="squashfs" 
/dev/loop1: TYPE="DM_snapshot_cow" 
/dev/loop2: TYPE="squashfs" 
/dev/loop3: LABEL="_Fedora-16-i686-" UUID="c99f1bac-dc78-4182-9b0d-09a37acb9075" TYPE="ext4" 
/dev/loop4: TYPE="DM_snapshot_cow" 
/dev/sda1: LABEL="System Reserved" UUID="668E59BA8E598409" TYPE="ntfs" 
/dev/sda2: UUID="A6705F93705F6957" TYPE="ntfs" 
/dev/mapper/live-rw: LABEL="_Fedora-16-i686-" UUID="c99f1bac-dc78-4182-9b0d-09a37acb9075" TYPE="ext4" 
/dev/mapper/live-osimg-min: LABEL="_Fedora-16-i686-" UUID="c99f1bac-dc78-4182-9b0d-09a37acb9075" TYPE="ext4"

Created attachment 576371 [details]
Program.log

Created attachment 576372 [details]
storage.log

The current partitions were straight from Windows7, I did a clean install and then tried to install Fedora on top of it.

I think the issue is Fedora16 uses GPT and I had Fedora16 on this disk by itself... so then when I formatted and installed windows7, windows didn't wipe out all the GPT information, so now that I'm trying to put F16 back on its confused about the mix of GPT and MBR

That's what it looks like. If you're not trying to dual boot you can use wipefs -a /dev/sda to remove the gpt information from it and try a clean install again.

Yeah, I ended up to doing parted and running mklabel msdos on it and then re-installing and everything worked.

This will not be a problem in the next release, parted now requires a valid PMBR partition so it will default to msdos in this scenario.