Red Hat Bugzilla – Bug 789216
/dev/disk/by-path loses a harddrive
Last modified: 2015-01-04 21:49:06 EST
Created attachment 560775 [details]
ls -lR /dev/disk
Description of problem: /dev/disk/by-path shows only 3 harddrives, but in fact there are four.
Version-Release number of selected component (if applicable):
How reproducible: every time
Steps to Reproduce:
1. boot; inspect /dev/disk/by-path
Actual results: only 3 harddrives are listed:
pci-0000:00:06.0-scsi-0:0:0:0 -> ../../sda
pci-0000:00:06.0-scsi-0:0:1:0 -> ../../sdb
pci-0000:00:07.0-scsi-0:0:0:0 -> ../../sde
Note that ../../sdd is missing. [../../sdc is an empty ZIP-100 drive attached to IDE Secondary slave.]
This shows up in graphical table of drives during anaconda installation of Fedora 17 Alpha TC2 as:
ATA MAXTOR STM332062 305245 MB pci:0000:00:06.0-scsi-0:0:1:0 (EIDE)
ATA ST3320620AS 305245 MB pci:0000:00:07.0-scsi-0:0:0:0 (EIDE)
ATA WDC WDC3200AAJB-0 305245 MB pci:0000:00:06.0-scsi-0:0:0:0 (SATA)
ATA WDC WDC5000AAKS-0 476940 MB pci:0000:00:07.0-scsi-0:0:0:0 (SATA)
Note that the "pci:..." of line 4 is the same as line 2.
Expected results: all 4 harddrives appear
Additional info: Actual hardware configuration is:
IDE Primary master: ATA MAXTOR STM332062 sda
IDE Primary slave: ATA ST3320620AS sdb
IDE Secondary master: SONY DVD RW AW-G170A sr0
IDE Secondary slave: IOMEGA ZIP 100 sdc [drive is empty]
SATA1: ATA ST3320620AS sdd
SATA2: ATA WDC WD5000AAKS-0 sde
Sorry, SATA1 is ATA WDC WDC3200AAJB-0.
Created attachment 560776 [details]
lspci; lspci -n; lspci -v
The main chipset is nVidia Corporation CK804.
Created attachment 560777 [details]
syslog during boot of anaconda installer
udev creates /dev/disk/by-path/ entries as far as I know. The other listings you have show the kernel found the device, so I don't see this as a kernel problem.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.
(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)
More information and reason for this action is here:
This appears to be a FEdora 17 bug. If this is still an issue on a current, supported version of Fedora, please reopen.