Adaptec 39320 stuck?

[JASTECH]

I am in the process of switching from SATA II to U320. My MB GA-X38-DQ6 does not have a PCI-X slot so I have to use the card in a PCI slot. After I insert the card and boot up the card reads Ch1 and hangs there then has error that no drive was found. So then I installed an old Seagate 15k drive in port "A". During boot the adapter found the drive on port "A" then went to port "B" and again it hung. Is there a way around this? I wanted to just install the card and then drivers then start messing with the SCSI drives and formatting them for another PC as I have new 147GB U320 drives for this system. But with the card in the PCI slot it will only use 32bit not 64 bit and my new board (coming soon) is the GA-EX58-UD5 so what card should I use on it to get the 64bit?

Edit: Should the system be able to boot to OS with a SCSI card installed and no SCSI drives attached?

Thanks, JASTECH

 

[nenforcer]

Well I have only used SCSI very little myself but in the old days you had to have a terminator on the SCSI device chain in order for it to work properly. I had thought they had removed this limitation in newer SCSI devices but maybe not.

 

[JASTECH]

nenforcer, They still use the termination block at the end of the cable or you can terminate via the drive. But this is all setup properly as I had it on my wifes computer. It has to be something in the Hub or BIOS that can be changed and I read the manual and still can't find the answer. When the system boots it finds the 39320, then the Hub tries to locate SCSI drives on port "A" and there are no drives attached and then it tries port "B" and hangs then shows a message that no drives were found and keeps trying. It is set for Auto Termination. More ideas please.

Thanks, JASTECH

 

[JASTECH]

I went ahead and installed 3x U320 15k 147GB drives on port "A" then booted the system. The Hub sees the 3 147's on port "A" then goes to port "B" and hangs for a bit then retries over and over. After this I went ahead and installed a Seagate U320 15k on port "B" and thought this will do the trick. Low and behold it did not, so I thought ok the drive is some how bad even though it was working fine a couple days ago. I then removed the Seagate and installed a IBM 15k drive and teh same thing accured. My only other thought was the U320 flat cable was bad so I opened a new one and tried again to only be at teh same result. The Hub was working fine when I pulled it from my wifes computer and installed SATA II drives. Is there a SCSI Guru on this forum that can help? as I need the system up and running by the end of next week at the latest.

Thanks, JASTECH

 

[Big Lar]

OK, I don't have that particular card, but have run a few others. You need to get into the SCSI Cards Bios and configure the setup. You need to setup your parameters. Scsi Disks each have there own identity, ie; disk1 has a jumper set to ID2, or whatever, the disks must have all different ID's. Most SCSI drives will run ID 0 with no jumper for the ID, again, "no 2 drives can have the same ID on the same channel". Check the drive manufacturer website for jumper settings, ie; seagate,fujitsu,etc.

Shoot me a PM if you have direct questions. Been on SCSI for quite awhile now and may be able to give a few pointers, or just post here...

Larry

 

[JASTECH]

Big Lar, That is what you posted a ways back. I know how to configure SCSI devices and set all their "ID" via JP4 and end of drive for Hitachi's and end of drive for Seagate's ect. This hub will not post past port "B" for some reason even when I installed a drive on that port "B". I don't remember if the Hub needs to have "anything" on the ports to post then boot into the OS. I may try and disable port "B", I contacted SCSI4ME and they had no idea and emails were in broken English. That is why I need help here. I am still booting to my OS on the SATA II 250GB drive.

Thanks, JASTECH

 

[Big Lar]

Well, first thing I would do then is to swap cables around and see if that helps, not to mention checking in the mobo bios to be sure its set to boot from the scsi card. I'd also be doing this all with the sata drives disconnected from the setup.

Not sure if you have checked in the mobo bios for something called Interupt 19, if its in there try it enabled. Sometimes a scsi card will dominate so to speak and if there are other drives set to boot, it will completely mess up the boot process.

Yet another idea may be to check the date of the firmware on the card and see if a new 1 is available.

Larry

 

[JASTECH]

Big Lar,

"I went ahead and installed 3x U320 15k 147GB drives on port "A" then booted the system. The Hub sees the 3 147's on port "A" then goes to port "B" and hangs for a bit then retries over and over. After this I went ahead and installed a Seagate U320 15k on port "B" and thought this will do the trick. Low and behold it did not, so I thought ok the drive is some how bad even though it was working fine a couple days ago. I then removed the Seagate and installed a IBM 15k drive and teh same thing accured. My only other thought was the U320 flat cable was bad so I opened a new one and tried again to only be at teh same result. The Hub was working fine when I pulled it from my wifes computer and installed SATA II drives. Is there a SCSI Guru on this forum that can help? as I need the system up and running by the end of next week at the latest. "

This has already been done, I guess you missed what I posted in the thread? Well I located a new driver and installed it, this created a BSOD. I have now removed the 39320-R Hub and new flat SCSI cable. I will remove the new SCSI 147GB 15k U320 drives as there is not a Vista 64 bit driver I can locate to run these. I guess maybe just sell them for 500.00 + s/h and take the loss.

Thanks to everyone who tried to help, this saddens me not having my SCSI system as I have run SCSI for many years.

Thanks, JASTECH

 

[Big Lar]

Actually, I did not miss what you typed in the OP, I have had bad cables before that were brand new. That is why I suggested swapping the cable. Try a driver for Win Server 2003 for the Vista64 setup and see if it works, it will need to be WHQL for it to accept it, may work tho. I had to use the 2003 driver for Win7 to boot with the controller I have.

Larry

 

[JASTECH]

Well, So now I have to figure out what SCSI Hub will work on this MB GA-X38-DQ6 with Vista 64 bit and Linux then into the new EX58-UD5 also with Vista 64 Bit and Linux. Or maybe see what as the same Life, Durability and Speed(LDS) as my SCSI U360 15k's.
Anybody have any ideas? I hate selling what I have but if I need to then I will see what Linux drivers there are.

Opinions welcome, so please do reply with your thoughts.

Thanks, JASTECH