HP IO Accelerator Driver and Management
Software Version 2.2.2
Release Notes
Abstract
This document describes details about the 2.2.2 HP IO Accelerator driver release, including significant issues resolved with this release and issues
resolved since the 2.2.0 release. This document also covers issues that might arise using this release.
Part Number: 607716-005
February 2011
Edition: 5
© Copyright 2010, 2011 Hewlett-Packard Development Company, L.P.
The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express
warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall
not be liable for technical or editorial errors or omissions contained herein.
Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212,
Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government
under vendor’s standard commercial license.
Microsoft, Windows, and Windows Server are U.S. registered trademarks of Microsoft Corporation.
Contents
About this guide ........................................................................................................................... 5
Description ............................................................................................................................................... 5
Product models ......................................................................................................................................... 5
Operating systems ..................................................................................................................................... 5
Supported firmware version ........................................................................................................................ 6
Download location .................................................................................................................................... 7
Upgrade information ..................................................................................................................... 8
Upgrading from Version 1.2.3 and earlier ................................................................................................... 8
Upgrading from Version 1.2.4 to 1.2.7 ....................................................................................................... 8
Change log .................................................................................................................................. 9
Version 2.2.2 change log .......................................................................................................................... 9
Changes for Version 2.2.1 ......................................................................................................................... 9
Changes for Version 2.2.2 ......................................................................................................................... 9
Management ............................................................................................................................................ 9
Bug fixes .................................................................................................................................................. 9
Ports ...................................................................................................................................................... 10
New features .......................................................................................................................................... 10
Trim support ........................................................................................................................................... 10
Discard (Trim) on Linux ................................................................................................................... 10
Trim on Windows .......................................................................................................................... 11
Errata ........................................................................................................................................ 12
Errata overview ....................................................................................................................................... 12
General issues ........................................................................................................................................ 12
Avoid unmanaged shutdown........................................................................................................... 12
IO Accelerator uses host memory to operate ..................................................................................... 12
Periodic latency bump .................................................................................................................... 12
IO Accelerator is not bootable ........................................................................................................ 13
Compiler Cache (ccache) causes driver src.rpm rebuild failures on some distributions ............................ 13
fio-update-iodrive shows strange version number ............................................................................... 13
Reported power usage from fio-status might be incorrect for IO Accelerator Monos ................................ 13
LED indicators do not operate properly ............................................................................................. 13
fio-update-iodrive shows wrong version number ................................................................................. 14
Linux-specific issues ................................................................................................................................. 14
Linux MD RAID5 performs poorly and is not supported ....................................................................... 14
Drivers not installed after updating kernel ......................................................................................... 14
Rare error on driver unload using kernels older than 2.6.24 ............................................................... 14
ext4 in Kernel.org 2.6.33 or earlier might silently corrupt data when discard (trim) is enabled ................ 14
Driver might not autoload in some distributions .................................................................................. 15
RHEL4 2.6.9-22 kernel does not work with 320GB IO Accelerators ..................................................... 15
Driver not auto-loaded on RHEL4 releases u6 and earlier .................................................................... 15
Modinfo module parameters not reported under RHEL4 ...................................................................... 16
Source rpm build fails in Chaos 4.3 with ccache enabled ................................................................... 16
Kernels 2.6.34/35 don't handle switching interrupt types................................................................... 16
RHEL6 udevd warning .................................................................................................................... 16
Contents
3
RHEL6 gives a warn_slowpath message during device attach .............................................................. 16
Windows-specific issues ........................................................................................................................... 17
Conversion to GPT or Dynamic disk terminates Logical Disk Manager Administrative Service .................. 17
Windows Installer (DLL) errors ......................................................................................................... 17
VMWare ESX-specific issues ..................................................................................................................... 18
ESXi not supported ........................................................................................................................ 18
The IO Accelerator VSL driver is unsigned ........................................................................................ 18
HP IO Accelerator Management Tool-specific issues .................................................................................... 18
IO Accelerator Management Tool in Linux enables preallocate (for swap support) in wrong file ............... 18
Acronyms and abbreviations ........................................................................................................ 19
Contents
4
About this guide
Description
This document describes information about the 2.2.2 release of the IO Accelerator driver, including a list of
changes, firmware compatibility, download location, and notes.
Version: 2.2.2
Update recommendation: Routine
Languages: International English
CAUTION: IO Accelerator driver Version 2.2.x is not backward compatible. HP does not
support downgrading from Version 2.2.x to Version 1.2.x. All IO Accelerators in the system must
run the same revision of the IO Accelerator driver. Version 2.1 and later of the driver software,
including VSL, are not compatible with any driver version earlier than 2.1.
Product models
The following HP IO Accelerator models are included in this document:
•
HP 160GB SLC PCIe ioDrive for ProLiant Servers
•
HP 320GB MLC PCIe ioDrive for ProLiant Servers
•
HP 320GB SLC PCIe ioDrive Duo for ProLiant Servers
•
HP 640GB MLC PCIe ioDrive Duo for ProLiant Servers
•
HP 1.28TB MLC PCIe ioDrive Duo for ProLiant Servers
•
HP StorageWorks 80 GB IO Accelerator for BladeSystems c-Class
•
HP StorageWorks 160 GB IO Accelerator for BladeSystems c-Class
•
HP StorageWorks 320 GB IO Accelerator for BladeSystems c-Class
•
HP StorageWorks 640 GB IO Accelerator for BladeSystems c-Class
Operating systems
The IO Accelerator driver works with many Linux kernels and has been verified using the operating systems
and kernel versions listed in the following table. Kernels similar to those listed also work.
Operating
system
Kernels
Red Hat Enterprise 2.6.9-22.ELsmp
2.6.9_34.ELlargesmp
Linux 4
2.6.9_34.ELsmp
2.6.9-42.ELlargesmp
2.6.9-42.ELsmp
About this guide
5
Operating
system
Kernels
2.6.9-55.ELlargesmp
2.6.9-55.ELsmp
2.6.9-67.ELlargesmp
2.6.9-67.ELsmp
2.6.9_78.0.8.ELlargesmp
2.6.9_78.0.8.ELsmp
2.6.9_78.ELlargesmp
2.6.9_78.ELsmp
2.6.9_89.ELlargesmp
2.6.9_89.ELsmp
Red Hat Enterprise 2.6.18_120.el5
2.6.18_128.el5
Linux 5
2.6.18_128.el5xen
2.6.18_164.el5
2.6.18_164.el5xen
2.6.18_53.el5
2.6.18_53.el5xen
2.6.18_8.el5
2.6.18_8.el5xen
2.6.18_92.1.22.el5
2.6.18_92.1.22.el5xen
2.6.18_92.el5
2.6.18_92.el5xen
SLES 10
2.6.16.46-0.12-smp
2.6.16.60-0.21-smp
SLES 11
2.6.27.19_5_default
2.6.27.19_5_xen
2.6.27.21_0.1_default
Operating
system
Supported operating system
Windows
Windows Server 2003 x64
Windows Server 2008 x64
VMWare ESX
VMware ESX 4.0 Update 1
VMware ESX 4.1
Supported firmware version
HP recommends using the latest firmware version provided with the software release package for all IO
Accelerators. For HP IO Accelerator Versions 2.2.2 and later, the firmware version is firmware package
ioaccelerator_101583_6.fff.
NOTE: Microsoft® Windows® operating systems might also display a file named
iodrive_101583.fff. Use the ioaccelerator_101583_6.fff firmware file.
About this guide
6
Download location
Drivers, utilities, and related documentation for this version can be found at the HP website
(http://www.hp.com/support).
About this guide
7
Upgrade information
Upgrading from Version 1.2.3 and earlier
Before you upgrade the HP IO Accelerator driver to Version 2.2.2 from Version 1.2.4 or earlier, you must
upgrade to Version 1.2.7 or higher.
Upgrading from Version 1.2.4 to 1.2.7
Upgrading the driver from Versions 1.2.4 or 1.2.7 requires that the previous version be completely
uninstalled. You must also upgrade the firmware after installing the 2.2.x software. Ensure that all data is
backed up before beginning the installation process.
To uninstall the software using Linux:
1.
Log in to the system as root or use the su command to gain root access.
2.
Ensure that there are no file systems or RAID volumes mounted to the IO Accelerator.
3.
Detach each IO Accelerator:
# fio-detach /dev/fctx where x = 0, 1, 2
For example:
# fio-detach /dev/fct0
4.
Remove the driver from kernel:
/dev/fct1
# modprobe -r fio-driver fio-port
NOTE: This command might fail if you have not unmounted the file systems or RAID volumes.
5.
Run the following commands, in order, to uninstall the 1.2.x package:
rpm -e iodrive-snmp
rpm -e iodrive-ini
rpm -e iodrive-firmware
rpm -e iodrive-util
rpm -e iodrive-driver
To uninstall the software by using Windows® operating systems:
1.
Open the Control Panel.
2.
Select Add/Remove Programs, and remove the HP IO Accelerator software.
Upgrade information 8
Change log
Version 2.2.2 change log
This change log documents the changes made from Version 2.1.0 to Version 2.2.0, as well as the additional
changes made for two maintenance releases (2.2.1 and this release, 2.2.2). The first two sections include the
changes made with this release. All other sections include the changes made from 2.1.0 to 2.2.0.
Changes for Version 2.2.1
•
Added support for the HP 5.2TB MLC PCIe ioOctal.
•
Fixed various minor bugs.
•
New firmware, version 101583.
Changes for Version 2.2.2
•
Added support for two new HP mezzanine cards:
o
AJ878B: HP StorageWorks 320 GB IO Accelerator for BladeSystems c-Class
o
BK836A: HP StorageWorks 640 GB IO Accelerator for BladeSystems c-Class
•
Fixed bug where ambient temperature gets stuck at zero
•
Fixed other minor bugs
Management
•
The fio-status command displays bandwidth and power requirements.
•
Added RAM usage statistics to SDK and fio-status.
•
Improved fio-status speed in Linux when driver is loaded.
•
The fio-status command no longer displays unknown if slot number is invalid, and it does not
display the slot: tag at all.
Bug fixes
•
Improvements have been made in shutdown handling.
•
The HP IO Accelerator Management Tool and the fio-config command update the correct
modprobe.d/ file in Linux.
•
Linux works on systems with IOMMUs.
•
Memory constraint fixes have been placed in ESX. There is no longer a five card limit.
•
Improved memory management for Windows operating systems.
Change log 9
•
There are faster detach times for Windows operating systems.
•
The utils segfault command is fixed when run on box with greater than 256 PCI devices.
•
Fixed fio-status induced lockup.
Ports
Linux
•
General availability
•
Support newer Linux kernels
Windows® operating systems
•
General availability
ESX
•
General availability
New features
•
Trim/Discard is enabled by default. For more information, see "Trim support (on page 10)."
•
The fio-bugreport utility is improved for Windows® operating systems.
•
The handling of timeout in the kfio_config.sh driver build script for Linux is improved. Builds are
less likely to fail on heavily loaded systems.
•
Fine tuning options for preallocate mode are included.
•
The default fio_dev_wait_timeout_secs is changed from 3 to 30 for Linux. The driver now waits
longer for /dev/fio* devices to display. This can be bad for systems not using udev (embedded).
These systems might need to set back to a smaller value.
Trim support
With driver Version 2.2.0 and later, Trim (also known as Discard) is enabled by default on Linux and
Windows operating systems. Trim addresses an issue unique to solid-state storage. When a user deletes a
file, the device does not recognize that it can reclaim the space. Instead the device assumes the data is valid.
Trim is a feature on newer filesystem releases. It informs the device of logical sectors that no longer contain
valid user data. This feature enables the wear-leveling software to reclaim that space as reserve to handle
future write operations.
NOTE: Only Linux and Windows® operating systems currently support Trim/Discard.
Discard (Trim) on Linux
Discard is enabled by default in the Linux IO Accelerator driver Version 2.2.0 and later. However, for
discard to be implemented, the Linux distribution must support this feature and discard must be turned on. If
Change log 10
your Linux distribution supports discard, and discard is enabled on the system, then discard is implemented
on your IO Accelerator device.
Under Linux, discards are not limited to being created by the filesystem. Discard requests can also be
generated directly from userspace applications using the kernels discard ioctl.
CAUTION: HP does not support the use of ext4 in Kernel.org 2.6.33 or earlier. Ext4 in
Kernel.org 2.6.33 or earlier might silently corrupt data when discard is enabled. This has been
fixed in many kernels provided by distribution vendors. Verify with your kernel provider that your
kernel supports discard. For more information, see "Linux-specific issues (on page 14)."
NOTE: On Linux, MD and LVM do not currently pass discards to underlying devices. Therefore,
any IO Accelerator device that is part of an MD or LVM array do not receive discards sent by the
filesystem.
Trim on Windows
Trim is enabled by default in the Windows® IO Accelerator driver Version 2.2.0 and later. For a complete
description of Trim support on Windows®, see the "Trim support" section of the HP IO Accelerator version
2.2.1 for Windows User Guide.
NOTE: Windows® operating systems do not support Trim with a RAID 5 configuration.
Trim on Windows Server 2008 R2
Windows Server® 2008 R2 has built-in Trim support. IO Accelerator devices work with Windows® Trim
commands by default.
Trim on Windows Server 2003 and Windows Server 2008 R1
Windows® Trim is not built into Windows Server® 2003 or Windows Server 2008 R1. However, the HP IO
Accelerator Trim service is installed with the Windows® ioMemory VSL, and it provides the necessary Trim
operations.
The HP IO Accelerator Trim service is enabled by default unless it detects an operating system that supports
Trim (such as Windows Server® 2008 R2). You can disable the HP IO Accelerator Trim service by using the
fio-trim-config utility. For more details, see the HP IO Accelerator Version 2.2.1 for Windows User
Guide.
Change log 11
Errata
Errata overview
This section describes issues you might encounter when using the 2.2.2 IO Accelerator driver release.
General issues
The following issues might occur regardless of which operating system you use.
Avoid unmanaged shutdown
If the IO Accelerator experiences an unmanaged shutdown (for example, power loss or system crash), the
driver takes longer to load during the next reboot, up to several minutes. When this issue occurs, the driver
reports that it needs several minutes to rebuild management data and not to shut down or restart the system.
If you have more than one IO Accelerator, each device rebuilds the management data in parallel, rather than
serially as with previous versions.
IO Accelerator uses host memory to operate
Depending on how the IO Accelerator is configured, it uses varying amounts of host memory per 80GB of
storage capacity, as shown in the following table for 2.x systems.
Average block
size (bytes)
RAM usage (megabytes)
8192
225
4096 (most
common)
425
2048
825
1024
1600
512 (default)
3175
Periodic latency bump
A latency bump every 30 seconds might be observed under some workloads, or a higher than expected
average latency might be observed. This issue occurs because of normal maintenance.
Under Linux, this bump can be safely changed to happen every minute instead of every 30 seconds. To set
a one minute interval, enter the following command every time you load the driver:
$ echo 60000 > /proc/fusion/fio/fiox/data/groomer/groom-oldest-lebinterval
where x is the letter of the device you are modifying.
This issue will be resolved in a future release.
Errata
12
IO Accelerator is not bootable
The IO Accelerator cannot currently be used as a boot device.
Compiler Cache (ccache) causes driver src.rpm rebuild failures on
some distributions
If the ccache package is installed, rebuilding the fio-driver src.rpm might fail with an error similar to
the following:
CC [M] /root/fio/fio-driver-2.0.0.113/root/usr/src/fio-driver/driver_init.o
/root/fio/fio-driver-2.0.0.113/root/usr/src/fio-driver/driver_init.c:116:
error: initializer element is not constant
[...]
To allow the driver to rebuild, remove the ccache package or disable ccache.
fio-update-iodrive shows strange version number
Using the fio-update-iodrive utility shows firmware reporting and updated from 41936 to 5. This
report occurs because the firmware is moving to a new versioning system. However, the firmware update is
successful and the device is operating with the updated firmware (version 42527).
Reported power usage from fio-status might be incorrect for IO
Accelerator Monos
The value reported by the fio-status utility for PCIe Bus power is incorrect for IO Accelerator Monos
(IO Accelerators without a separate carrier adapter) and must not be used for any health monitoring. The IO
Accelerator Mono cannot draw more power than what is provided by the base PCIe specification for the
minimum slot. Therefore, tracking this value accurately is unnecessary. The device and driver operate
normally in all other aspects. Only the reporting function is affected. Other IO Accelerator models that
support power usage monitoring are not affected.
Sample errant fio-status output: PCIE Bus power:
PCIE Bus power: avg 6.86W, max -16.89W
LED indicators do not operate properly
The LED lights might not light up according to expected behavior. After the driver is loaded, the amber and
green LED lights might remain constantly lit and fail to blink to indicate device activity.
This behavior is only experienced on newer IO Accelerator devices that have a part number that begins with
FS1-003-XXX-XX. Older IO Accelerator devices that are not affected by this behavior have a part number that
begins with FS1-001-XXX-XX.
This issue does not affect IO Accelerator Duo devices or HP IO Accelerators for BladeSystem c-Class.
Errata
13
fio-update-iodrive shows wrong version number
When upgrading the firmware version on driver Version 1.2.7 or earlier, the fio-update-iodrive utility
reports an incorrect new version number. For example, when updating from firmware version 41936 to
42527, the utility displays the following message:
****************************************************************************
# ./fio-update-iodrive -f -s 05:00.0 /home/fio/firmware/iodrive_42527.fff
Device ID 0 (05:00.0) Updating device firmware from 41936 to 5
****************************************************************************
However, the firmware update is successful and the device operates with the updated firmware version
42527.
Linux-specific issues
The following issues apply only to systems running Linux operating systems.
Linux MD RAID5 performs poorly and is not supported
HP does not recommend or support using a RAID5 configuration. The Linux kernel RAID5 implementation
performs poorly at high data rates. This issue must be fixed in the Linux kernel and is not controlled by HP.
Alternatives include using RAID10 or possibly a third-party RAID stack. The cause of the issue might be that
the RAID5 parity calculation is handled by a single kernel thread, which does not match the performance of
an array of IO Accelerators.
Drivers not installed after updating kernel
When the driver is installed for a specific kernel version and the kernel version is changed for any reason, the
IO Accelerator driver must be reinstalled to work with the new kernel version. RHEL5 has some processes that
minimize the need to reinstall the driver after a kernel upgrade.
Rare error on driver unload using kernels older than 2.6.24
A bug in Linux kernels prior to 2.6.24 can cause a general protection fault or other kernel error when the IO
Accelerator driver is unloaded. This bug also affects non-HP drivers. The bug has been resolved in newer
kernels. See the kernel 2.6.24 change log
(http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.24) for more information. Search for
commit 5a622f2d0f86b316b07b55a4866ecb5518dd1cf7.
Because this is a bug in the Linux kernel, HP cannot resolve this issue for older kernels.
ext4 in Kernel.org 2.6.33 or earlier might silently corrupt data
when discard (trim) is enabled
CAUTION: HP does not support the use of ext4 in Kernel.org 2.6.33 or earlier. Ext4 in
Kernel.org 2.6.33 or earlier might silently corrupt data when discard is enabled.
Errata
14
The ext4 filesystem in the Kernel.org kernel 2.6.33 and earlier contains a bug where the data in a portion of
a file might be improperly discarded (set to all 0x00) under some workloads. Use Version 2.6.34 or newer
to avoid this issue. For more information, see the patch
(http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=b90f687018e6d6 ) and
bug report (https://bugzilla.kernel.org/show_bug.cgi?id=15579).
The fix is included in RHEL6 pre-release kernel kernel-2.6.32-23.el6. The eventual release RHEL6 kernel is not
affected by this issue.
Discard support was added to the kernel.org mainline ext4 in Version 2.6.28 and was enabled by default.
For fear of damaging some devices, discard was set to default to disabled in Version 2.6.33-rc1 and was
back ported to 2.6.31.8 and 2.6.32.1. For more information, see the kernel patch
(http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=5328e635315734d).
Driver might not autoload in some distributions
When using certain Linux operating systems, the driver installation package might not properly configure
itself to be automatically loaded in all run level boot sequences. To verify whether the driver is properly
configured, after you have installed the driver, run the following command at a shell prompt:
$ chkconfig –list | grep iodrive
The following appears:
$ iodrive 0:off 1:on 2:on 3:on 4:on 5:on 6:off
The results inform you that the driver loads if the server is booted at run levels 1-5. At a minimum, the run
levels at which you use or maintain the IO Accelerator must be enabled. If those run levels are not enabled,
run the following commands at a shell prompt (with root privilege):
$ chkconfig --del iodrive
$ chkconfig --add iodrive
$ chkconfig --list | grep iodrive
The previous results appear:
$ iodrive 0:off 1:on 2:on 3:on 4:on 5:on 6:off
If you need further assistance, contact HP Customer Support (http://www.hp.com/support).
RHEL4 2.6.9-22 kernel does not work with 320GB IO
Accelerators
Because of limitations in the 2.6.9-22 kernel shipped with early versions of RHEL4, the 320GB IO
Accelerator and 640GB IO Accelerator Duo cards do not work when running this kernel.
Newer RHEL4 kernels support the larger devices.
Driver not auto-loaded on RHEL4 releases u6 and earlier
In RHEL4 release 6 and earlier, the udev script does not auto-load the driver. Use the init script to load the
driver instead.
Errata
15
Modinfo module parameters not reported under RHEL4
The IO Accelerator driver does not properly report the load-time parameters when the modinfo command
is run. Obtain the list of supported parameters from the User Guide that came with your IO Accelerator or by
running the modinfo command on a newer system. The module parameters are identical between Linux
distributions when using the same driver version.
Source rpm build fails in Chaos 4.3 with ccache enabled
By default, Chaos has the ccache package installed. If an attempt is made to build the RPM from source with
ccache enabled, the result is an error message.
Remove or disable ccache before building the driver.
Kernels 2.6.34/35 don't handle switching interrupt types
Linux kernels around 2.6.34/35 might have problems processing interrupts if the driver is loaded using one
interrupt type, unloaded, and then loaded again using a different interrupt type. The primary symptom is that
the IO Accelerator device is unusable and the kernel logs have errors containing doIRQ. For example, the
following sequence on an affected system would likely result in errors:
1.
Load the driver with a default of disable_msi=1 which selects APIC interrupts:
$ modprobe iomemory-vsl
$ modprobe -r iomemory-vsl
2.
Load the driver and enable MSI interrupts:
$ modprobe iomemory-vsl disable_msi=0
To work around this issue, if you see the error, reboot the system. Also, always load with the same interrupt
type selected. To change between interrupt types, reboot the system first.
RHEL6 udevd warning
When using an IO Accelerator under RHEL6 (or any Linux distribution with udev script version 147 or later),
udevd might emit the following messages:
udevd[154]: worker [19174] unexpectedly returned with status 0x0100
udevd[154]: worker [19174] failed while handling
'/devices/virtual/block/fioa'
These messages are innocuous, and you can ignore them.
RHEL6 gives a warn_slowpath message during device attach
When attaching an IO Accelerator device under RHEL6, you might see log messages similar to the following:
kernel: ------------[ cut here ]-----------kernel: WARNING: at fs/fs-writeback.c:967 __mark_inode_dirty+0x108/0x160()
(Tainted: P ---------------- )
.
.
Errata
16
.
[<ffffffff8106b857>] warn_slowpath_common+0x87/0xc0
[<ffffffff8106b8aa>] warn_slowpath_null+0x1a/0x20
.
.
.
This is due to a bug in the 2.6.32 kernel, and the messages can safely be ignored.
Windows-specific issues
The following issues apply only to systems running Windows® operating systems.
Conversion to GPT or Dynamic disk terminates Logical Disk
Manager Administrative Service
This issue appears when:
•
Converting a Basic partition to GPT
•
Converting a Basic partition to Dynamic Volume
•
Switching between GPT and Dynamic Volume or vice versa
When an issue occurs, the following message appears: The Logical Disk Manager Administrative
Service terminated unexpectedly. Restart the Virtual Disk service.
This issue occurs only with Windows Server® 2003 and Windows® XP x64.
If the IO Accelerators are used in GPT or Dynamic mode, the following process must be performed during the
initial setup. This process also recovers drives that have had a failed conversion attempt.
CAUTION: This procedure destroys any existing data on your drives. If you already have data
on a drive, be sure to back it up before proceeding.
For IO Accelerators used in GPT or Dynamic mode:
1.
For each IO Accelerator in the system to be converted, use the HP IO Accelerator Management Tool to
a. Detach the drive.
b. Perform a low-level format.
For more information, see the User Guide that came with your IO Accelerator.
2.
Restart the computer.
3.
Navigate to Disk Management and select Initialize Disk.
4.
Right-click and select Convert to GPT or Convert to Dynamic Disk.
Windows Installer (DLL) errors
If you receive an error related to a .dll during the installation of the Windows® driver, follow these steps:
1.
Abort the installation process.
2.
Run the Uninstaller program for any previous installations.
Errata
17
3.
Stop any running Windows® services related to ioMemory VSL products (for example, the fio-agent
utility):
a. Open Device Manger.
b. Navigate to the Services menu.
c.
Select Stop on these running services.
4.
Reboot the system.
5.
After the system has rebooted, navigate to the installation directory of the driver and remove any files
that were left over from the previous installation (at a minimum, any leftover .dll files). If you receive an
access denied error when attempting to remove these files, be sure you have Administrator
privileges.
6.
Remove the fio.dll file from the Windows\System32 directory.
NOTE: If the fio.dll file does not exist in this directory, proceed to step 7.
7.
You are now able to run the new installer without error. If you still encounter errors, contact HP Customer
Support (http://www.hp.com/support).
VMWare ESX-specific issues
The following issues apply only to systems running ESX operating systems.
ESXi not supported
There is a known limitation that ESXi is not yet supported.
The IO Accelerator VSL driver is unsigned
The driver is not signed until a future release of ESX.
HP IO Accelerator Management Tool-specific issues
The following issues apply specifically to the HP IO Accelerator Management Tool.
IO Accelerator Management Tool in Linux enables preallocate (for
swap support) in wrong file
The IO Accelerator Management Tool writes the preallocate_memory parameter to the
/etc/modprobe.d/fio-driver.conf file, but it should be writing the option to the
/etc/modprobe.d/iomemory-vsl.conf file. Preallocate is still enabled properly.
Errata
18
Acronyms and abbreviations
DLL
dynamic link library
GPT
GUID partition table
GUID
globally unique identifier
IOMMU
input/output memory management unit
LED
light-emitting diode
LVM
Logical Volume Manager
MLC
multi-level cell
PCIe
peripheral component interconnect express
RAID
redundant array of inexpensive (or independent) disks
RAM
random access memory
RHEL
Red Hat Enterprise Linux
RPM
Red Hat Package Manager
Acronyms and abbreviations 19
SLC
single-level cell
SLES
SUSE Linux Enterprise Server
VSL
virtual storage layer
Acronyms and abbreviations 20