You did not mention the kernel version you are working with, but I will
assume that it is 2.4 based (2.5 supports report_luns and should avoid
The failure looks like you need to set a sparse lun flag for this
storage device. Add an entry with the BLIST_SPARSELUN flag set to the
device_list array in scsi_scan.c for this storage device.
If the scanning is happening post boot you could turn on some scan
logging to verify this issue.
echo "scsi log scan 4" > /proc/scsi/scsi
You can set logging during boot, but you can only control all logging or
none and it sometimes generates to much output.
-- Michael Anderson email@example.com
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to firstname.lastname@example.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/