Created attachment 747021 [details] screenshot F19b TC4 Description of problem: USB Mass Storage Device (F19b TC4 Installation Media) is available as a disk in INSTALLATION DESTINATION and it is the first item show. Selecting only 'sda' in INSTALLATION DESTINATION results in a 0b entry corresponding to sdb shown in CUSTOM PARTITIONING. Disk 'sdb' was not selected so it should not appear there. Version-Release number of selected component (if applicable): F19b TC4 How reproducible: always Steps to Reproduce: 1. DD Fedora is to an USB Mass Storage Device 2. Reach Storage Installation Destination 3. Select only sda 4. Do CUSTOM PARTITIONING, partition scheme 'standard partition' Actual results: 0b entry in custom partitioning, and the device appears even if it should not. Expected results: Only selected disks should be available to use as a INSTALLATION DESTINATION.
Created attachment 747022 [details] screenshot F19b TC4, custom partitioning only sda was selected, but sdb has that 0b entry (iso9660).
logs please.
Created attachment 748024 [details] anaconda.log
Created attachment 748025 [details] program.log
Created attachment 748026 [details] storage.log
Created attachment 748027 [details] syslog These logs are from another affected netbook, wind u100. (the screenshots are from an eee 701).
Created attachment 748028 [details] wind u100 screenshot please discard previously attached logfiles, as the screenshots shows, it is a different issue. My mistake. I will attach the correct ones in a momment.
Created attachment 748032 [details] anaconda.log
Created attachment 748033 [details] program.log
Created attachment 748034 [details] storage.log
Created attachment 748035 [details] syslog
I could not reproduce it in the original netbook, i got the same results that with the wind u100. I believe that the difference is made by the sdcard slot being non populated. The first time (when i reported it) the netbook ssd was empty (it was trashed by another issue). I current case, there is a detected F19 instance being shown in custom partitioning. The 0b iso9960 entry is now unknown.
The 0b /dev/sdb1 device that is appearing is also appearing with no media, so this is fixed by the fix for bug 960794 *** This bug has been marked as a duplicate of bug 960794 ***