-
-
Save h4rm0n1c/a1b96b4f6e4a3f6b7728e3cc8d644a40 to your computer and use it in GitHub Desktop.
| I've tried the following configuration on ESXi up to 6.5.0 Update 2 (Build 10719125) | |
| Beware the Adaptec, you can trick their support software into working | |
| with older cards by torturing your whitebox with various old vibs... | |
| But you will NEVER get Maxview Storage Manager to work! NEVER! | |
| Be grateful for ARCCONF, it's all you're getting, Adaptec sucks. | |
| I personally have a ASR-51245, running the latest BIOS available, 18948. | |
| The 5805, 5405, 6405, 6805, etc... should all in theory work with this combo, but if you have a 6 series card, you will have working maxview anyway. | |
| So the trick here is using just the right versions of the drivers, cim providers and arcconf to get this to work, bear with me. | |
| In theory, this should work all the way up to the latest version of 6.7, however in my testing I was not able to verify this. | |
| I know it will work on at least 6.7.0 Release. | |
| Driver | |
| URL: https://my.vmware.com/web/vmware/details?downloadGroup=DT-ESXI60-PMC-AACRAID-62141024&productId=491 | |
| Filename: aacraid-6.0.6.2.1.41024-2915492.zip | |
| Release Date: 23 July 2015 | |
| This is the last driver to support 5 Series cards in any way that could be considered proper. | |
| CIM Provider | |
| URL: https://storage.microsemi.com/en-us/speed/raid/storage_manager/msm_vmware_v2_02_22404_zip.php | |
| Filename: msm_vmware_v2_02_22404.zip | |
| Release Date: 20 Oct 2016 | |
| This is the ONLY cim provider I can find that works. | |
| Arcconf | |
| URL http://download.adaptec.com/raid/storage_manager/arcconf_v2_06_23167.zip | |
| Filename arcconf_v2_06_23167.zip | |
| Release Date 05 Jul 2018 | |
| All the recent versions from 2.06.23167 onwards should work. | |
| Maxview will log in and may work intermittently in terms of monitoring, but it is definitely unreliable. | |
| It's best to slipstream the vibs into a ESXi 6.5 ISO or wait until everything in this gist is set up before you create your raid volumes. | |
| If you have issues with dissapearing data stores, you may have to reattach them from the direct management console or SSH, check the vmware support site for for info. |
Hi! Sorry for necroposting like this but I'm in the middle of trying to make this exact thing working, and I've hit a bit of a wall there. Unfortunately both VMWare and Adaptec sites are pretty much gone now and aren't exactly very well preserved, I only managed to grab the correct version of arcconf from the Web Archive. I'm still missing both the driver and the CIM Provider for this combo - do you by any chance still have them and if you do, could you please upload them somewhere?
Hi! Sorry for necroposting like this but I'm in the middle of trying to make this exact thing working, and I've hit a bit of a wall there. Unfortunately both VMWare and Adaptec sites are pretty much gone now and aren't exactly very well preserved, I only managed to grab the correct version of arcconf from the Web Archive. I'm still missing both the driver and the CIM Provider for this combo - do you by any chance still have them and if you do, could you please upload them somewhere?
I've noticed a discrepancy between the documentation and the screenshot. the drivers on the screenshot are versioned differently from the archive names, and clearly it's working on the screenshot, so here's what I'm gonna do...
I do have copies of what's listed in the screenshot, In a folder.
Here you go
https://github.com/h4rm0n1c/old_adaptec_stuff/
There's a lot of stuff there, check out releases for the bigger archive files since I had to put those into blob/object storage instead of the repo.
I suspect the filenames I put in the first document are either wrong or I ended up updating it later and forgot to update details, I opened a few vib files in 7zip and checked the versioning in the xml metadata and they matched the screenshot.
if you manage to get it working, let me know and I'll update the gist so someone else doesn't go through that, sorry!
the files were all dated around 2018 on my drive, a.k.a when I wrote this gist so I assume the versioning plus match with the screenshot over the text file is what you're really needing.
some of these may be extraneous, at least you've got some things to try!
I'm going to proxmox for my next maintenance and upgrade pass, I am running out my 6.7u3 until the pain of not replacing it is greater than the process of migrating all my VMXs to proxmox.
VMWare and then Broadcom's extaordinarlity greedy and toxic mindsets killed everything cool about this ecosystem and microsemi is just a walking corpse.
I'm so tired of corporations ruining good things because profit.
Watch as the kids learn proxmox instead because it's free and open and you don't need to give a figurative blood and urine sample to get an ISO file, and then broadcom wonders why nobody wants to use esxi anymore in about a decade it'll be dead I bet, proxmox will eat broadcom's lunch just because they screwed small guys and hobbyists, truely boneheaded.
what's worse is some lawyer dink from one of those places is likely to get all salty about this and the repo, so make sure you pull down everything and spread it if you can.
they figuratively attack everybody who's technically tried to help them when you think about it.
like I'm broke on disability with a dual xeon server from a decade ago I managed to scrape together with old parts and threw in a second hand 3080 for ai stuff (someone needed to get rid of it, I benefited in a lull in pricing about a year or two ago), they just don't get it, most of us are fkin broke and they wanna keep folding in support for old stuff that is all we can afford. it's just stupid.
also, don't worry about necroposting, as far as I'm concerned, I put this information out there to help people, if it's no longer helpful, it needs to be fixed, hopefully what I've done here tonight fixes it.
I've also got to do a lot of work on DMD2 for the Arduino, that's my responsibility and sadly poor health has taken me away from coding until recently, I'm gettting warmed up with some personal projects before I touch a repo that gets referenced against the Arduino IDE.
Thanks, you're a saviour! I've got a bit confused myself in the process but I believe I tried 2.06 first and the system became unstable, going into the kernel panic after every 10 minutes after the reboot or so. After a reinstall I've tried 1.08 and that one worked perfectly. So I guess the option that definitely works are 1.08 versions of CIM and arcconf. Though please leave the other versions up as well, otherwise I believe they're most likely lost media. I think I might go on a web archive scraping spree for whatever I'll manage to find and post all that stuff on the Internet Archive later. Thanks again!
no worries, you're welcome! I'm glad to be of assistance, adaptec cards are cool!
Quick and Dirty proof Screenshots, I have actually had ESXi change status when a disk just so happened to drop (had a bad SFF8087 to SATA cable), so I know for a fact that it can correctly detect status.
I wonder how adaptec would feel about a generic webui that interacts with the arcconf executable... something tells me they'd get upset that maxview had a competitor...