Archive for the ‘Troubleshooting’ Category

Upgrading All Firmware on your Iomega IX2 or IX4 NAS Device

VMware

I’ve been running an Iomega IX4 in my home vSphere lab 24×7 for the past two years and have found it to be a nice reliable NAS device.  Though like with anything regular maintenance is required whether this be removing the dust or fluff from the fan at the back or keeping the firmware up-to-date.  The latter being the topic of this blog post.

The Iomega IX2 or IX4 NAS has two parts to it than can have firmware revisions applying to it.  The first is the most obvious and is for the actual IX4 unit itself.    You can check to see the current firmware revision of your IX2 or IX4 by clicking on the Dashboard tab of the IX’s web based management interface, see below. 

Iomega Firmware Version[5]

UPDATE THE IX DEVICE FIRMWARE

To check to see if your IX NAS device is running the latest firmware version you have a couple of options. Either visit the ‘Support’ section of the Iomega web site here and select your model of Iomega NAS device or click on the ‘Settings’ tab and then on the ‘Update’ icon (below).

 

Iomega IX Firmware Update

 

After clicking on the ‘Update’ icon you’ll be presented with a screen that shows the current firmware revision and a link to the ‘Iomega Software Update Web Site’.  By clicking this link you’ll be taken through to the Iomega site where you can then navigate to the ‘Support’ section and download any required firmware revision.

 

Iomega IX Firmware Update[6]

The following is a list of the recent firmware updates available along with a description of the main enhancements and fixes for each.

Version 2.1.38 (ix4-200d)
* Improves read-write speeds to NTFS-formatted external USB drives
* Allows writes to HFS-formatted external USB drives
* Fixes issue with device-to-device replication
* Resolves issues with iSCSI, including fixing a bug with capacity reporting and problems caused by improper dismount of shares
* Modifies default drive spin down behavior
* Provides capability to update local hard disk drive
Version 2.1.38 (ix2-200)
* Improves manufacturing process – This update only affects how the ix2-200 devices are manufactured, and has no new functionality
Version 2.1.35.19973
* Improves read-write speeds to NTFS-formatted external USB drives
* Allows writes to HFS-formatted external USB drives
* Fixes issue with device-to-device replication
* Resolves issues with iSCSI, including fixing a bug with capacity reporting and resolving problems caused by improper dismount of shares
* Modifies default drive spin down behavior
Version 2.1.30.8298
-Improved folder permissions, including AFP
-Fixed iSCSI segment length
-Improved Video Surveillance integration
-Fixed minor security issue with external USB devices
-Improved Active Directory integration
-Improved content indexing performance
-Fixed an issue with RAID arrays
-Improved performance when discovering multiple devices on network
-Restricts thumbnails to files less than 15 megapixels

 

Generally firmware revisions to the device itself isn’t data destructive meaning that you can upgrade your IX device without fear of losing any data to it.  That said, it is always a good idea to make a copy of your data to another device or similar before applying any firmware update – just in case…

Once you’ve download the firmware file from the Iomega site you are then all set to update it to the Iomega IX device.  To do this simply check/tick the ‘Copy Update File’ box, click the ‘Browse’ button and select the firmware file you just downloaded and click the ‘Next’ button to start updating the firmware.

 

Iomega IX4 Firmware Update

UPDATE THE DISK FIRMWARE

The second part to upgrading the firmware on your Iomega is no doubt the most overlooked,  the firmware of the hard disks.  It pays to keep the firmware of your hard disks updated semi-regularly especially if your IX device shows symptoms such as hard disks powering down frequently or loud clicking noises on a new device.

But before we go on any further and even start thinking about updating the firmware of the hard disks – BACK UP YOUR IOMEGA DEVICE FIRST!!!  Updating the firmware on the hard disks whether it be in an Iomega or any other device can be a risky business. 

To check out what revision of firmware your hard disks are running click on the ‘Settings’ tab and then the ‘Disks’ icon (below).

 

Iomega IX Disk Drives

From this view of the disks you can see the four disks of model ST31000520AS (Seagate Barracuda LP SATA Disk) which are running the CC32 firmware revision.  From the release notes for the Iomega IX disk upgrade the latest (at the time of writing this post) firmware revision is CC38.  So as you can see the disks in my IX4 are rather out of date, also you’ll notice that I have a failed disk in the device which I plan to swap out shortly under warrantee.

 

Iomega IX Disk Firmware Update

To download the latest drive firmware access the link below to the Iomega support site:

https://iomega-na-en.custhelp.com/app/answers/detail/a_id/24661/kw/Firmware%20Update

The steps below are how to upgrade the drives of your Iomega IX though I would recommend always checking the Iomega site first just in case the procedure changes:

Power off your ix2-200 or ix4-200d

Unplug any external USB devices you may have plugged into your ix2-200 or ix4-200d

Insert the updated USB flash drive into a USB port on your ix2-200 or ix4-200d

Iomega IX Drive FW Upgrade

Press and hold the reset button on the rear panel of the unit

Power on your ix2-200 or x4-200d

Continue holding the reset button while powering on the device

  • After about 1 minute, a picture of a USB flash drive will show on the front LCD display. At this point release the reset button.

Iomega IX firmware update USB

  • The ix2-200 or ix4-200d unit will now execute the utility loaded on the flash drive to update the drives in the system. After all drives are updated the unit will automatically shut-down. This should take less than 1 additional minute.

After your ix2-200 or ix4-200d powers off, remove the USB flash drive

Power up your ix2-200 or ix4-200d

  • If your device drives are 500GB (2TB total capacity), verify that the drives are updated to version CC37 by logging in to the ix2-200 or ix4-200d and checking under Settings -> Disks
  • If your device drives are 1TB or 2TB drives (4TB or 8TB total capacity), verify that the drives are updated to version CC38 by logging in to the ix2-200 or ix4-200d and checking under Settings -> Disks

Now, when you go back into the ‘Settings’ –> ‘Disks’ tab you should see that the disks firmware revisions have increased from CC32 to CC38.  As mentioned earlier in this post there is a possibility that the updating of the firmware of the drives is data destructive so double check that your data is still intact else restore it from your backup.  You did take a back right?

Iomega IX4 FW Update[6]

 

So there we have it, updating the firmware of both your Iomega IX device and it’s disks is a straight forward process and well worth keeping on top of.  Smile

 

VMware vSphere Error – Initializer for VirtualInfrastructure.Utils.HttpWebRequestProxy’ threw an exception

VMware

Hey TechHeads!  Here’s an important vSphere issue that may potentially impact the management of your production or lab vSphere environment.  The ‘issue’ is caused by a recent Microsoft .NET patch update which can cause your pre-Update 1 vSphere Client to give the error message: “ Error parsing the server "<servername>" "clients.xml" file.  The type initializer for VirtualInfrastructure.Utils.HttpWebRequestProxy’ threw an exception. “

VMware have released a Knowledge Base article which describes the error in a little more detail and provides the resolution of….  Update your vSphere Client.  So to head this error off you may want to consider upgrading your vSphere Client, if your haven’t already done so.

 The type initializer for VirtualInfrastructure.Utils.HttpWebRequestProxy' threw an exception

VMware ESXi Purple Screen of Death on HP Proliant ML110 or ML115

Hewlett Packard (HP) VMware

A common occurrence discovered by HP Proliant ML110 and ML115 owners when having installed the HP version of VMware ESXi  containing the management agents is a Purple Screen of Death (PSoD) after about 2 minutes of the ESXi host being up and running.  The following video demonstrates this:

 

 

The reason this occurs is that ESXi loads the HP CIM (Common Information Model) agents which then subsequently crashes ESXi if particular hardware is not found.  Needless to say the hardware the CIM agents are looking for are not present in the Proliant 100 series of servers which includes the ML110 and ML115 models.

With the introduction of VMware vSphere you are now able to view the majority of hardware in your ESX(i) host and its current status via the use of the common interfaces standard, Intelligent Platform Management Interface (IPMI).  Though you will notice that this doesn’t quite extend to the onboard disk controller of the Proliant ML115 (or ML110).  Similar specification entry level servers from the likes of Dell do show the full disk and onboard controller details, so what’s the catch?  From what I can make out HP uses their own minor variation of IPMI which talks to the BMC which then in turn talks to the ILO to gain some of the additional component information.

 

VMware ESX Health Status - HP Proliant

 

Herein lies part of the problem – the HP Proliant 100 series of servers don’t come with the full version of the ILO.  They can have the Lights Out 100 card installed though this is the equivalent of the low fat/no frills version of the full ILO which doesn’t provide the same level of hardware detection and monitoring information.

So how do you know if one of your hard disks connected to the onboard controller is having issues?  Well, the answer is – you won’t.  The official line is that these servers aren’t on VMware’s hardware compatibility list (HCL) so you may want to consider is using a PCIe based array controller such as the HP Smart Array E200 or a Dell DRAC if you want this level of hardware monitoring.  Both of these array controllers can often be found at a semi-reasonable price on EBay.

Unfortunately your disk controller and drive monitoring issues don’t go away if you buy an HP E200 as you will still need to load the HP Management Agents on to your ESX(i) host for the E200 to be detected and presented in the ‘Health Status’ window of ESX(i).  At this point you are then back to square one as once the HP Management Agents are loaded ESX(i) will PSoD again.

To overcome this PSoD issue you will need to install the HP Management Agents and then stop all but the Smart Array controller agents from loading.  Once this is complete and the ESX(i) host rebooted you should now see the HP Smart Array E200 controller and attached hard disks in the ‘Health Status’.  I only have one E200 controller in my lab though have used this method since ESX 3.5 without any issues.  I will put together a step by step guide if anyone is would like to see how this is done.

 

StarWind Software
TrainSignal - vSphere Pro
AppAssure
PHD Virtual - esXpress
Trilead
Veeam #1