Red Hat Bugzilla – Bug 122203
i2o Device Nodes not created/recognized when i2o_block is used
Last modified: 2014-03-16 22:44:44 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7b)
Description of problem:
When installing Test3, the i2o device nodes are not created or
recognized by Anaconda, resulting in "No Hard Drives Found".
However, the i2o subsystem _is_ functional. For example, if I create
the device nodes in /tmp:
mknod /tmp/i2o/hda b 80 0
mknod /tmp/i2o/hda1 b 80 1
mknod /tmp/i2o/hda2 b 80 2
mknod /tmp/i2o/hda8 b 80 8
I am able to mount my partitions with no problems. Hence, it appears
that the i2o block drivers are fully functional, however Anaconda is
not creating the correct device entries or is not recognizing the i2o
To be sure, I also tried manual hardware configuration (noprobe) to
ensure that it wasn't a conflict involving Anaconda seeing my other
SCSI controllers. Sure enough, same problem even when the other SCSI
drivers are not loaded.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot Test3 Installer CD
2. Select standard install
3. Hard drives will not be found
i2o drivers seem to be working great... The i2o_block drivers
definately seem to have some performance improvements over dpt_i2o.
Unfortunately, Anaconda won't isntall to them yet!
This is because kudzu can't probe i2o disks.
Created attachment 100058 [details]
Markus Lidel wrote this patch. I am testing it now.