- LSI MEGARAID STORAGE MANAGER FOR VMWARE ESXI 5.5 SERVERS INSTALL
- LSI MEGARAID STORAGE MANAGER FOR VMWARE ESXI 5.5 SERVERS UPDATE
- LSI MEGARAID STORAGE MANAGER FOR VMWARE ESXI 5.5 SERVERS DRIVER
- LSI MEGARAID STORAGE MANAGER FOR VMWARE ESXI 5.5 SERVERS VERIFICATION
- LSI MEGARAID STORAGE MANAGER FOR VMWARE ESXI 5.5 SERVERS SOFTWARE
There has been no updates for the LSI 2108 based cards from the vendor since Avago took over LSI, which was the reason I was attempting to go to the VMware Native driver - so I did not have a newer VIB to import into VUM. The big question: What is the proper method to remove a vendor supplied driver and start using the VMware inbox driver?
LSI MEGARAID STORAGE MANAGER FOR VMWARE ESXI 5.5 SERVERS UPDATE
Question 4: When you make a Host change does it only update that specific value in storage or does the entire file get overwritten with the Host configuration running in RAM? There is no writing of the config that is running in RAM to persistent storage when you issue a reboot command. Question 3: My understanding of the way ESXi does the configuration is that the configuration file is only updated at the time of the change being made. I rebooted and verified that the system was fixed - at least that it was functioning properly, though still using the Legacy driver. I also did restart of all the services using services.sh. The module load command gave a module busy error but the enable module command was accepted. esxcli system module load -module=megaraid_sasĮsxcli system module set -enabled=true -module=megaraid_sas I loaded the megaraid_sas module and enabled it, checked that the storage adapter and datastores showed up and then repeated the commands. I finally realized that I should make the module changes twice before the last ditch solution of wiping the volume and doing a fresh install. It did not and why would it? This was a configuration change I made not some corrupt driver.
LSI MEGARAID STORAGE MANAGER FOR VMWARE ESXI 5.5 SERVERS INSTALL
Tried to install 5.5 U3b over my existing system thinking it would repair the driver. This failed since I had not installed a VIB so there was no previous state to return to. Tried to do a system recovery using Shift R. I went through a bunch of wasted effort trying to fix what I though was a unrecoverable situation, I realized that I had an issue where the Host change was not being written to system volume since it could not see the volume when the change was made. It went back to the same failed state - no storage adapter recognized and the megaraid_sas module is disabled. I then rebooted the Host to make sure everything was working properly. I reversed that change and enabled the megaraid_sas module and luckily the storage adapter was recognized and the datastores appeared. I tried to load and enable the lsi_mr3 module manually but this failed to get ESXi to see the storage adapter. At this point I think I am really screwed. I rebooted again it does not fix itself and I see no local storage. The same issue as the first attempt - no storage adapter is seen and no datastores. esxcli system module set -enabled=false -module=megaraid_sas I decided to force the issue and removed the Host from vCenter, removed the megaraid_sas driver again from the CLI, disabled the driver using esxcli and rebooted. Question 2: Why did it not revert to using the Native lsi_mr3 driver? Can anyone verify that this is the case and get me a link to anything that discusses this in detail.
LSI MEGARAID STORAGE MANAGER FOR VMWARE ESXI 5.5 SERVERS VERIFICATION
Question 1: I assume that vCenter saw the issue when it booted and during the second reboot reverted to the previous driver, similar to the network verification mechanism when you make changes to a vmk interface. When it finally booted I saw that the megaraid_sas VIB was still installed and it was being used as the scsi driver. I rebooted the Host again and the Host booted normally. The Host is still attached to the vCenter Server. In our environment this ESXi Host boots off of a volume behind the same RAID card that the VMs have their datastores on and everything is Direct Attached Storage on this Host. After it booted fully the storage controller was not available and none of the datastores showed.
Once after 'vfc loaded successfully' and once after 'nfs client loaded successfully'. It stalled at a few places during the reboot which was the first hint that there was a driver problem now.
LSI MEGARAID STORAGE MANAGER FOR VMWARE ESXI 5.5 SERVERS SOFTWARE
esxcli software vib remove -n megaraid_sas I used the esxcli command to remove the megaraid_sas version 6.603.55.00.1vmw driver and rebooted the Host. You can read about the ESXi 5.5 Native driver introduction from William Lam if you were not aware of them here, Īfter upgrading the Host to 5.5 U3b (build 3343343) using VUM, I decided it was time to remove the LSI provided VIB since it was getting old and was unneeded - the VMware Native VIB LSI_mr3 fully supports the 9260 series cards as they are 6 Gb\s and not 12 Gb/s RAID cards. This is a legacy ESXi driver that still uses the vmklinux shim. In this case I have been using the LSI provided megaraid_sas VIB for an ESXi 5.5 Host using a LSI 9260-8i RAID card. I have an issue where I do not understand the proper procedure for removing a vendor supplied VIB and making ESXi use the Native driver that is part of the ISO (VMware inbox).
0 kommentar(er)
