Description of problem: In GNOME Disk utility two identical PATA drives on the same bus is bundled as only one of them is available for manipulation. This makes it impossible to do anything with both drives (apparently). Version-Release number of selected component (if applicable): How reproducible: It appears when two identical disks are added to the same bus (one master and one slave). I have not tested with different models or size of drives. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: I expect both drives to be visible in the list of drives as separate entries. Additional info:
Please attach the output of 'udisksctl dump' and 'udevadm info --export-db'
Created attachment 597260 [details] udevadm info --export-db dump
Created attachment 597261 [details] udisksctl dump
(In reply to comment #2) > Created attachment 597260 [details] > udevadm info --export-db dump Two interesting fragments: P: /devices/pci0000:00/0000:00:14.1/ata6/host5/target5:0:0/5:0:0:0/block/sdd [...] E: ID_MODEL=SAMSUNG_SP1604N E: ID_MODEL_ENC=SAMSUNG\x20SP1604N\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20 E: ID_PART_TABLE_TYPE=dos E: ID_REVISION=TM100-42 E: ID_SERIAL=SAMSUNG_SP1604N_S013J10X206306 E: ID_SERIAL_SHORT=S013J10X206306 E: ID_TYPE=disk E: ID_WWN=0x50f0000000000000 E: ID_WWN_WITH_EXTENSION=0x50f0000000000000 and P: /devices/pci0000:00/0000:00:14.1/ata6/host5/target5:0:1/5:0:1:0/block/sde [...] E: ID_MODEL=SAMSUNG_SP1604N E: ID_MODEL_ENC=SAMSUNG\x20SP1604N\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20 E: ID_PART_TABLE_TYPE=dos E: ID_REVISION=TM100-42 E: ID_SERIAL=SAMSUNG_SP1604N_0731J1FX106872 E: ID_SERIAL_SHORT=0731J1FX106872 E: ID_TYPE=disk E: ID_WWN=0x50f0000000000000 E: ID_WWN_WITH_EXTENSION=0x50f0000000000000 The interesting thing to observe here is that the WWNs are identical (and looks like they are blank) and since udisks prefers WWN to serial, we end up thinking sdd and sde belongs to the same disk....
Reassign to udisks as the bug is there
Please try these packages http://people.freedesktop.org/~david/rhbz838691/a/ You will need to run # systemctl restart udisks2.service after installing the packages. If this fix works I will commit the fix upstream and build an update for f17. Thanks.
(In reply to comment #6) > Please try these packages > > http://people.freedesktop.org/~david/rhbz838691/a/ > > You will need to run > > # systemctl restart udisks2.service > > after installing the packages. > > If this fix works I will commit the fix upstream and build an update for f17. > > Thanks. Seems to work fine. No problems detected and they fixed the issue.
udisks2-1.94.0-8.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/udisks2-1.94.0-8.fc17
Package udisks2-1.94.0-8.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing udisks2-1.94.0-8.fc17' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-10552/udisks2-1.94.0-8.fc17 then log in and leave karma (feedback).
udisks2-1.94.0-8.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.