dynamox is right. A situation like this is very likely caused by misconfiguration with persistent binding. If you can show the disk device names (cXtYdZ) that should show whether leadville driver or non-leadville driver is in use (the latter requires persistent binding).
If it is non-leadville driver / persistent binding, in this case most likely by adding a few entries in sd.conf followed by a reconfiguration reboot should fix the issue.
If this is leadville driver then it's a different story but I don't recall seeing anything like it.
dynamox
11 Legend
•
20419 Posts
•
87439 Points
310
0
Posted July 20th, 2012 16:00
sd.conf and lpfc.conf/qla.conf configured correctly ?