burdsounds
Technical User
I have a G3 Beige 266Mhz still trucking along with an ATTO ULD2 card that has been great thus far.
My issue is my 2 SCA Seagate Barracuda 50 LC drives I recently bought and put on using SanMax 160LVD 80pin-68pin adapters are appearing with incorrect ID's.
The first drive in the chain (Seagate LC), which regardless of the configuration of jumpers on the drive or adapter, boots as ID 1 [My current setting is ID 0 on both drive and adapter]. The next drive is another Seagate LC that will only appear to the OS [as ID 3] when set drive and adapter to ID 1. The third and final drive is a Seagate Elite 23 ST423451W (yes, a brick) set to ID 4 and appears correctly and has the drive powered SE terminator enabled.
The symptoms are the first SCA drive works fine even though the ID is incorrect but the second drive is not ready for driver install according to ATTO ExpressTools. It remains useless to the system and I suspect that it's due to wrong ID assumed or seen by the HBA on boot (possibly a second ID 1 on the bus that's unformatted and thus ignored?)
At the moment I am not running a twisted pair cable and would be more than happy to purchase an LVD terminator and lose the older Seagate if it solve or improve the chances of fixing the ID issues.
Any recommendations?
My issue is my 2 SCA Seagate Barracuda 50 LC drives I recently bought and put on using SanMax 160LVD 80pin-68pin adapters are appearing with incorrect ID's.
The first drive in the chain (Seagate LC), which regardless of the configuration of jumpers on the drive or adapter, boots as ID 1 [My current setting is ID 0 on both drive and adapter]. The next drive is another Seagate LC that will only appear to the OS [as ID 3] when set drive and adapter to ID 1. The third and final drive is a Seagate Elite 23 ST423451W (yes, a brick) set to ID 4 and appears correctly and has the drive powered SE terminator enabled.
The symptoms are the first SCA drive works fine even though the ID is incorrect but the second drive is not ready for driver install according to ATTO ExpressTools. It remains useless to the system and I suspect that it's due to wrong ID assumed or seen by the HBA on boot (possibly a second ID 1 on the bus that's unformatted and thus ignored?)
At the moment I am not running a twisted pair cable and would be more than happy to purchase an LVD terminator and lose the older Seagate if it solve or improve the chances of fixing the ID issues.
Any recommendations?