Re: shuttle sd37p2 eSATA driver?


hi john-paul:

i tried a couple of variation of echo "scsi add-single-device [2-6] 0
0 0" >> /proc/scsi/scsi, but none had an effect. rescan-scsi-bus also
has some mild errors in output these days (no wonder for a hardware
script from 1998!).

# sh rescan-scsi-bus.sh
Host adapter ? (*) found.
Scanning for device ? 0 1 0 ...
Scanning for device ? 0 2 0 ...1: echo: write error: Invalid argument
Scanning for device ? 0 3 0 ...1: echo: write error: Invalid argument
Scanning for device ? 0 4 0 ...1: echo: write error: Invalid argument
Scanning for device ? 0 5 0 ...1: echo: write error: Invalid argument
Scanning for device ? 0 6 0 ...1: echo: write error: Invalid argument
Scanning for device ? 0 7 0 ...1: echo: write error: Invalid argument
0 new device(s) found. o: write error: Invalid argument

but I did take your other advice, and this seemed to help a lot---a
cold reboot.

# lsscsi
[0:0:0:0] disk ATA SAMSUNG HD400LJ ZZ10 /dev/sda
[1:0:0:0] disk ATA WDC WD3200KS-00P 21.0 /dev/sdb
[1:0:1:0] disk ATA Sans Digital V.36 /dev/sdc

so, I needed to tell /proc/scsi/scsi to scan the ID on hostadapter #1.
interesting, isn't it? anyway, thanks a lot for your advice.
hopefully, the next sd37p2 linux user will see this thread.

regards,

/iaw


John-Paul Stewart wrote:
ivowel@xxxxxxxxx wrote:


thanks, john-paul, but I think its deeper than this. I only see my two
internal SATA drives:

# lsscsi
[0:0:0:0] disk ATA SAMSUNG HD400LJ ZZ10 /dev/sda
[1:0:0:0] disk ATA WDC WD3200KS-00P 21.0 /dev/sdb

Those numbers surprise me. I would have thought that the SATA driver
mapped everything onto a single SCSI bus number, but instead it maps
onto multiple busses.

Since the rescan-scsi-bus.sh script didn't work, it's unlikely that
echoing directly to /proc/scsi/scsi will help, but it would appear that
the right command would be 'echo "scsi-add-single-device 2 0 0 0"
>/proc/scsi/scsi' instead of the numbers I suggested in my earlier
post. (They were just a guess, and apparently not a good one!) What
numbers did you try? (Note that if there are additional unused internal
SATA ports, those could be 2, 3, ... whatever. Try everything until you
get at least one beyond the number of internal SATA ports you have.)

.