UNSOLVED
660f LS module error
I have recently purchased (E-Bay) a fully populated (14 18gig drives) 660f, plus a Qlogic 2200 HBA. I have everything working using Sansurfer and array manager 3.6.0 connected to a PE1650 running Win2k server (no switch). The final configuration (after a few more purchases) is a 3-5 server cluster all connected to the SAN via a switch.
I ended up getting an additional drive (ST373307fc) (Sun labeled) that I have tried installing into the array. The drive is recognized and works fine, but it causes array manager to declare an error, saying that the LS modules are missing or not properly seated. The LED's on the LS modules never report an error.
This is currently not much of an issue, but had considered at some point getting a set of larger drives to install in this system, and would like it to be error free. The purpose of the system is educational. Speed is not so much a concern as is learning how SAN's work and are configured. Any suggestions are appreciated.
Message Edited by Sodhammer on 07-05-2007 06:55 PM
I ended up getting an additional drive (ST373307fc) (Sun labeled) that I have tried installing into the array. The drive is recognized and works fine, but it causes array manager to declare an error, saying that the LS modules are missing or not properly seated. The LED's on the LS modules never report an error.
This is currently not much of an issue, but had considered at some point getting a set of larger drives to install in this system, and would like it to be error free. The purpose of the system is educational. Speed is not so much a concern as is learning how SAN's work and are configured. Any suggestions are appreciated.
Message Edited by Sodhammer on 07-05-2007 06:55 PM
- If I remove the drive, the error goes away. The error occurred with me trying the drive in several different slots. I think (did this awhile ago) that the system would not recognize the SUN drive if it was the only drive in the array. But if there were other drives, it worked.
This drive is not listed on the supported drive list. I am assuming it is some kind of compatibility issue.
rthomp8363
38 Posts
157
0
Posted July 31st, 2007 01:00