Bug 962244

Summary: USB Mass Storage Device (INSTALLATION MEDIA created with DD) is available as a disk and even if not selected, it shows up in custom partitioning with a 0b iso9660 entry
Product: [Fedora] Fedora Reporter: Reartes Guillermo <rtguille>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 19CC: anaconda-maint-list, dshea, g.kaviyarasu, jonathan, mkolman, sbueno, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-09-05 21:02:01 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screenshot F19b TC4
none
screenshot F19b TC4, custom partitioning
none
anaconda.log
none
program.log
none
storage.log
none
syslog
none
wind u100 screenshot
none
anaconda.log
none
program.log
none
storage.log
none
syslog none

Description Reartes Guillermo 2013-05-12 23:30:39 UTC
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.

Comment 1 Reartes Guillermo 2013-05-12 23:32:05 UTC
Created attachment 747022 [details]
screenshot F19b TC4, custom partitioning

only sda was selected, but sdb has that 0b entry (iso9660).

Comment 2 Brian Lane 2013-05-15 00:57:06 UTC
logs please.

Comment 3 Reartes Guillermo 2013-05-15 02:06:37 UTC
Created attachment 748024 [details]
anaconda.log

Comment 4 Reartes Guillermo 2013-05-15 02:07:06 UTC
Created attachment 748025 [details]
program.log

Comment 5 Reartes Guillermo 2013-05-15 02:07:30 UTC
Created attachment 748026 [details]
storage.log

Comment 6 Reartes Guillermo 2013-05-15 02:08:41 UTC
Created attachment 748027 [details]
syslog

These logs are from another affected netbook, wind u100. (the screenshots are from an eee 701).

Comment 7 Reartes Guillermo 2013-05-15 02:12:30 UTC
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.

Comment 8 Reartes Guillermo 2013-05-15 02:36:11 UTC
Created attachment 748032 [details]
anaconda.log

Comment 9 Reartes Guillermo 2013-05-15 02:36:35 UTC
Created attachment 748033 [details]
program.log

Comment 10 Reartes Guillermo 2013-05-15 02:37:04 UTC
Created attachment 748034 [details]
storage.log

Comment 11 Reartes Guillermo 2013-05-15 02:37:29 UTC
Created attachment 748035 [details]
syslog

Comment 12 Reartes Guillermo 2013-05-15 02:43:14 UTC
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.

Comment 13 David Shea 2014-09-05 21:02:01 UTC
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 ***