LSI ADAPTER SAS 3000 SERIES 8-PORT WITH 1068E STORPORT DRIVER
I edited the original post to include a screenshot of the device manager. The server is an HP Z If it’s a server buy from a major brand, like dell, hp or ibm in example, a model number can tell us the exact controller model too, as system build are documented. Sign up using Facebook. So I’ve reworded the question. I guess you are running this on Win Server with HyperV, but you need to make this clear.
|Date Added:||26 January 2010|
|File Size:||16.37 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
Home Questions Tags Users Unanswered. I would have assumed the model would start with a 3, being a ” series”? LSI model numbers never made much sense to me – I found the quickspecs and added that to the answer above. Scott Beeson 1 Zac67 3, 2 4 This caught my eye only on second reading: It was an attempt to show that the LSI device was not virtual, but it was a poor attempt.
What other information can I provide?
LSI Adapter, SAS 3000 series, 8-port with 1068E -StorPort
This is a VM host with multiple company VMs, so I don’t want to shut it down just to get the exact model of the adapger if ztorport even visible. If it’s a server buy from a major brand, like dell, hp or ibm in example, a model number can tell us the exact controller model too, as system build are documented.
How can I find out the exact model of the controller without physical access? Email Required, but never shown. Sign up using Facebook.
To continue using , please upgrade your browser.
Sign up using Email and Password. I initially installed the Intel RST software, but it shows no attached drives.
I added a Windows tag, but I don’t think the fact that it’s a hyper-v host is really syorport to the question itself so I didn’t add that. Since the LSI Adapter, SAS series, 8-port with is also a common, generic virtual adapter you have to make sure that you’re doing this on the hypervisor, not inside a guest. Sorry I didn’t think to include that originally, seems obvious: I edited the original post to include a screenshot of the device manager.
No, HyperV in itself is not importantthe Windows part is: Well, the model devices chosen for virtual hardware are those that are quite common, have mature drivers and are well-documented.
That’s weird, this is definitely the physical host unless there are VMs on a VM I have added the server model to the post.
Please add information about your environment. I’m having trouble finding documentation on this RAID controller.
Sign up or log in Sign up using Google. The Windows system details aren’t very specific.