hp-firmware-smartarray-14ef73e580-6.64-2 >
D H ` x Uw'ݍd'^ƻn8z\T>g %ZU|dNxK39&gfRfp
nXVfAה9}/]b&L-ΝlԯR_ )REIc'7ZQ
~ l[`[;22?^#r+L&^}MWXQyR
$g}\w&Ԫ'Wjtnvx_}e}yqJT6d1c4bb1c5dfc66276acbaec7297fbefa18b813e ep Uwݍd'^0&QJP$-ࢭvI@8'-]%2iZ:R[uHqxI@a7y(`.N#% VĜzؼ^ZAyaܜ@$mOoYL)Fr7&yK$`eJ5l3(V}\]^iPv5F}e/7)T| C,wtR {U.- ndEYx뚴fi Uw&ݍd'^٪nk.C &<
n,_%Lo2`Y0%`5`҆^HdujH?v19Em(5C狒s(p\+Ewc~*q]'cjٞ/6!I\F8Ξi5ޠ%zgf].WkU2'bFs4W LD~[\V2Xmd-y1+!Þ:S]CrVFKQKc-V4KY9/~=af٫R~ 0 > 7
?
r d $ ) + p / G [ ~ F nX n n
n n p4
p@ pp p p q qL v w y| ( y 8 y A 9 z A : " A >
@
G
H
I
X
Y
x \
]
^
b
D d
c e
h f
m l
o
~
j C hp-firmware-smartarray-14ef73e580 6.64 2 Smart Array P212, P410, P410i, P411, P711m, P712m, and P812 firmware This package contains the Smart Array P212, P410, P410i, P411, P711m, P712m, and P812 firmware Uwbldeb6u3x64004 Hewlett-Packard Company 2012 Hewlett-Packard Development Company, L.P. Hewlett-Packard Company Applications/System http://www.hp.com/go/proliantlinux linux i386
# create marker files so that we only run hp-fm once per transaction
mkdir -p /var/lib/rpm-state/hp-firmware/
touch /var/lib/rpm-state/hp-firmware/hp-firmware-smartarray-14ef73e580-6.64-2 # clean up our directory
if [ -d "/usr/lib/i386-linux-gnu/hp-firmware-smartarray-14ef73e580-6.64-2" ] ; then
rm -rf "/usr/lib/i386-linux-gnu/hp-firmware-smartarray-14ef73e580-6.64-2"
fi
if [ -d /etc/hp-firmware/postrm.d ]; then
for i in /etc/hp-firmware/postrm.d/*.sh; do
if [ -r $i ]; then
sh $i
fi
done
unset i
fi
# surface XML so hpsum doesn't need to extract the package
cat<<__ENDCPXML__>>/dev/null
CP027483.scexe
存储设备
Storage
ストレージ
스토리지
儲存裝置
服务器
Server
サーバ
서버
伺服器
Microsoft Windows Server 2008 W32
SUSE LINUX Enterprise Server 10 (x86)
SUSE LINUX Enterprise Server 10 (AMD64/EM64T)
Red Hat Enterprise Linux 5 Server (x86)
Red Hat Enterprise Linux 5 Server (x86-64)
Microsoft Windows Server 2008 R2
VMware ESX/ESXi 4.0
SUSE LINUX Enterprise Server 11 (x86)
Red Hat Enterprise Linux 6 Server (x86-64)
Red Hat Enterprise Linux 6 Server (x86)
VMware ESX/ESXi 4.1
Cross Operating System
VMware vSphere 5.1
VMware ESXi 5.0
Red Hat Enterprise Linux 7 Server
SUSE Linux Enterprise Server 12
固件 - 存储控制器
Firmware - Speichercontroller
Firmware - Storage Controller
Firmware - Controlador de almacenamiento
Micrologiciel - Contrôleur de stockage
Firmware - Controller di memorizzazione
ファームウェア - ストレージ コントローラ
펌웨어 - 스토리지 컨트롤러
韌體 ─ 儲存裝置控制器
补充更新/面向 Linux 的在线 ROM Flash 组件 - 智能阵列 P212、P410、P410i、P411、P711m、P712m 和 P812
Supplemental Update / Online ROM Flash Component for Linux - Smart Array P212, P410, P410i, P411, P711m, P712m, and P812
Supplemental Update / Online ROM Flash Component for Linux - Smart Array P212, P410, P410i, P411, P711m, P712m, and P812
Supplemental Update / Online ROM Flash Component for Linux - Smart Array P212, P410, P410i, P411, P711m, P712m, and P812
Supplemental Update / Online ROM Flash Component for Linux - Smart Array P212, P410, P410i, P411, P711m, P712m, and P812
Supplemental Update / Online ROM Flash Component for Linux - Smart Array P212, P410, P410i, P411, P711m, P712m, and P812
サプリメンタルアップデート / オンラインROMフラッシュコンポーネント for Linux - SmartアレイP212、P410、P410i、P411、P711m、P712m、およびP812
Linux용 추가 업데이트 / 온라인 ROM 플래시 구성 요소 - 스마트 어레이 P212, P410, P410i, P411, P711m, P712m, 및 P812
適用於 Linux 的補充程式更新/線上 ROM 更新元件 - Smart Array P212、P410、P410i、P411、P711m、P712m 與 P812
智能阵列 P212、P410、P410i、P411、P711m、P712m 和 P812
Smart Array P212, P410, P410i, P411, P711m, P712m, and P812
Smart Array P212, P410, P410i, P411, P711m, P712m, and P812
Smart Array P212, P410, P410i, P411, P711m, P712m, and P812
Smart Array P212, P410, P410i, P411, P711m, P712m, and P812
Smart Array P212, P410, P410i, P411, P711m, P712m, and P812
SmartアレイP212、P410、P410i、P411、P711m、P712m、およびP812
스마트 어레이 P212, P410, P410i, P411, P711m, P712m, 및 P812
Smart Array P212、P410、P410i、P411、P711m、P712m 與 P812
Hewlett-Packard Development Company, L.P.
Hewlett-Packard Development Company, L.P.
Hewlett-Packard Development Company, L.P.
Hewlett-Packard Development Company, L.P.
Hewlett-Packard Development Company, L.P.
English (US), Japanese, German, French, Italian, Spanish
Anglais, Japonais, Allemand, Français, Italien, Espagnol
Englisch, Japanisch, Deutsch, Französisch, Italienisch, Spanisch
Inglese, Giapponese, Tedesco, Francese, Italiano, Spagnolo
英語(US), 日本語, ドイツ語, フランス語, イタリア語, スペイン語
Inglés, Japonés, Alemán, Francés, Italiano, Español
영어(미국), 일본어, 독일어, 프랑스어, 이탈리아어, 스페인어
英语(美国), 日语, 德语, 法语, 意大利语, 西班牙语
美式英文, 日文, 德文, 法文, 義大利文, 西班牙文
To update firmware from Linux operating system on target server:
Updating firmware with rpm installed:
- Install the firmware rpm using the command: rpm -ivh <rpm_filename>. This extracts the contents of the rpm to the '/usr/lib/i386-linux-gnu' location
- The CP027483.scexe script is located in the 'hp-scexe-compat' folder. The actual name of the 'hp-firmware-smartarray-14ef73e580-*' folder is based on the version of the rpm installed in the first step above
- To install firmware, you can execute ONE of the following commands:
# ./CP027483.scexe in the '/usr/lib/i386-linux-gnu/hp-scexe-compat' location (OR)
# ./hpsetup in the '/usr/lib/i386-linux-gnu/hp-firmware-smartarray-14ef73e580-*' location
- The results of the firmware upgrade are saved to the Component.log file, located in the /var/cpq/ directory
- To uninstall the rpm, run the command: rpm -e <rpm_package_name>, which is the rpm filename without the '.rpm' extension
Updating firmware without installing the rpm:
- Extract the contents of the rpm using the command: rpm2cpio <rpm_filename>.rpm | cpio -id. This extracts the contents of the rpm to 'usr' folder in the current directory
- Navigate to the 'usr/lib/i386-linux-gnu/hp-firmware-smartarray-14ef73e580-*' location and run ./hpsetup to update the firmware. The actual name of the 'hp-firmware-smartarray-14ef73e580-*' folder is based on the version of the rpm installed in the step above
- The results of the firmware upgrade are saved to the Component.log file, located in the /var/cpq/ directory
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps
To use HP Smart Update Manager from the HP Service Pack for ProLiant:
Offline:
- Place the HP Service Pack for ProLiant on a USB key using the HP USB Key Creator Utility
- Place the desired firmware to be updated in the directory, /hp/swpackages on the USB key
- Boot from the newly created HP Service Pack for Proliant USB key
- Follow HP Smart Update Manager steps to complete firmware update
Online:
- Login as root. (You must be root in order to apply the ROM update.)
- Place the desired firmware to be updated in the directory, /hp/swpackages
- Locate Start.html which is found in the root of the ISO
- Open the html file in a supported browser
- Follow the instructions on the screen
]]>
To update firmware from Linux operating system on target server:
Updating firmware with rpm installed:
- Install the firmware rpm using the command: rpm -ivh <rpm_filename>. This extracts the contents of the rpm to the '/usr/lib/i386-linux-gnu' location
- The CP027483.scexe script is located in the 'hp-scexe-compat' folder. The actual name of the 'hp-firmware-smartarray-14ef73e580-*' folder is based on the version of the rpm installed in the first step above
- To install firmware, you can execute ONE of the following commands:
# ./CP027483.scexe in the '/usr/lib/i386-linux-gnu/hp-scexe-compat' location (OR)
# ./hpsetup in the '/usr/lib/i386-linux-gnu/hp-firmware-smartarray-14ef73e580-*' location
- The results of the firmware upgrade are saved to the Component.log file, located in the /var/cpq/ directory
- To uninstall the rpm, run the command: rpm -e <rpm_package_name>, which is the rpm filename without the '.rpm' extension
Updating firmware without installing the rpm:
- Extract the contents of the rpm using the command: rpm2cpio <rpm_filename>.rpm | cpio -id. This extracts the contents of the rpm to 'usr' folder in the current directory
- Navigate to the 'usr/lib/i386-linux-gnu/hp-firmware-smartarray-14ef73e580-*' location and run ./hpsetup to update the firmware. The actual name of the 'hp-firmware-smartarray-14ef73e580-*' folder is based on the version of the rpm installed in the step above
- The results of the firmware upgrade are saved to the Component.log file, located in the /var/cpq/ directory
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps
To use HP Smart Update Manager from the HP Service Pack for ProLiant:
Offline:
- Place the HP Service Pack for ProLiant on a USB key using the HP USB Key Creator Utility
- Place the desired firmware to be updated in the directory, /hp/swpackages on the USB key
- Boot from the newly created HP Service Pack for Proliant USB key
- Follow HP Smart Update Manager steps to complete firmware update
Online:
- Login as root. (You must be root in order to apply the ROM update.)
- Place the desired firmware to be updated in the directory, /hp/swpackages
- Locate Start.html which is found in the root of the ISO
- Open the html file in a supported browser
- Follow the instructions on the screen
]]>
To update firmware from Linux operating system on target server:
Updating firmware with rpm installed:
- Install the firmware rpm using the command: rpm -ivh <rpm_filename>. This extracts the contents of the rpm to the '/usr/lib/i386-linux-gnu' location
- The CP027483.scexe script is located in the 'hp-scexe-compat' folder. The actual name of the 'hp-firmware-smartarray-14ef73e580-*' folder is based on the version of the rpm installed in the first step above
- To install firmware, you can execute ONE of the following commands:
# ./CP027483.scexe in the '/usr/lib/i386-linux-gnu/hp-scexe-compat' location (OR)
# ./hpsetup in the '/usr/lib/i386-linux-gnu/hp-firmware-smartarray-14ef73e580-*' location
- The results of the firmware upgrade are saved to the Component.log file, located in the /var/cpq/ directory
- To uninstall the rpm, run the command: rpm -e <rpm_package_name>, which is the rpm filename without the '.rpm' extension
Updating firmware without installing the rpm:
- Extract the contents of the rpm using the command: rpm2cpio <rpm_filename>.rpm | cpio -id. This extracts the contents of the rpm to 'usr' folder in the current directory
- Navigate to the 'usr/lib/i386-linux-gnu/hp-firmware-smartarray-14ef73e580-*' location and run ./hpsetup to update the firmware. The actual name of the 'hp-firmware-smartarray-14ef73e580-*' folder is based on the version of the rpm installed in the step above
- The results of the firmware upgrade are saved to the Component.log file, located in the /var/cpq/ directory
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps
To use HP Smart Update Manager from the HP Service Pack for ProLiant:
Offline:
- Place the HP Service Pack for ProLiant on a USB key using the HP USB Key Creator Utility
- Place the desired firmware to be updated in the directory, /hp/swpackages on the USB key
- Boot from the newly created HP Service Pack for Proliant USB key
- Follow HP Smart Update Manager steps to complete firmware update
Online:
- Login as root. (You must be root in order to apply the ROM update.)
- Place the desired firmware to be updated in the directory, /hp/swpackages
- Locate Start.html which is found in the root of the ISO
- Open the html file in a supported browser
- Follow the instructions on the screen
]]>
To update firmware from Linux operating system on target server:
Updating firmware with rpm installed:
- Install the firmware rpm using the command: rpm -ivh <rpm_filename>. This extracts the contents of the rpm to the '/usr/lib/i386-linux-gnu' location
- The CP027483.scexe script is located in the 'hp-scexe-compat' folder. The actual name of the 'hp-firmware-smartarray-14ef73e580-*' folder is based on the version of the rpm installed in the first step above
- To install firmware, you can execute ONE of the following commands:
# ./CP027483.scexe in the '/usr/lib/i386-linux-gnu/hp-scexe-compat' location (OR)
# ./hpsetup in the '/usr/lib/i386-linux-gnu/hp-firmware-smartarray-14ef73e580-*' location
- The results of the firmware upgrade are saved to the Component.log file, located in the /var/cpq/ directory
- To uninstall the rpm, run the command: rpm -e <rpm_package_name>, which is the rpm filename without the '.rpm' extension
Updating firmware without installing the rpm:
- Extract the contents of the rpm using the command: rpm2cpio <rpm_filename>.rpm | cpio -id. This extracts the contents of the rpm to 'usr' folder in the current directory
- Navigate to the 'usr/lib/i386-linux-gnu/hp-firmware-smartarray-14ef73e580-*' location and run ./hpsetup to update the firmware. The actual name of the 'hp-firmware-smartarray-14ef73e580-*' folder is based on the version of the rpm installed in the step above
- The results of the firmware upgrade are saved to the Component.log file, located in the /var/cpq/ directory
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps
To use HP Smart Update Manager from the HP Service Pack for ProLiant:
Offline:
- Place the HP Service Pack for ProLiant on a USB key using the HP USB Key Creator Utility
- Place the desired firmware to be updated in the directory, /hp/swpackages on the USB key
- Boot from the newly created HP Service Pack for Proliant USB key
- Follow HP Smart Update Manager steps to complete firmware update
Online:
- Login as root. (You must be root in order to apply the ROM update.)
- Place the desired firmware to be updated in the directory, /hp/swpackages
- Locate Start.html which is found in the root of the ISO
- Open the html file in a supported browser
- Follow the instructions on the screen
]]>
To update firmware from Linux operating system on target server:
Updating firmware with rpm installed:
- Install the firmware rpm using the command: rpm -ivh <rpm_filename>. This extracts the contents of the rpm to the '/usr/lib/i386-linux-gnu' location
- The CP027483.scexe script is located in the 'hp-scexe-compat' folder. The actual name of the 'hp-firmware-smartarray-14ef73e580-*' folder is based on the version of the rpm installed in the first step above
- To install firmware, you can execute ONE of the following commands:
# ./CP027483.scexe in the '/usr/lib/i386-linux-gnu/hp-scexe-compat' location (OR)
# ./hpsetup in the '/usr/lib/i386-linux-gnu/hp-firmware-smartarray-14ef73e580-*' location
- The results of the firmware upgrade are saved to the Component.log file, located in the /var/cpq/ directory
- To uninstall the rpm, run the command: rpm -e <rpm_package_name>, which is the rpm filename without the '.rpm' extension
Updating firmware without installing the rpm:
- Extract the contents of the rpm using the command: rpm2cpio <rpm_filename>.rpm | cpio -id. This extracts the contents of the rpm to 'usr' folder in the current directory
- Navigate to the 'usr/lib/i386-linux-gnu/hp-firmware-smartarray-14ef73e580-*' location and run ./hpsetup to update the firmware. The actual name of the 'hp-firmware-smartarray-14ef73e580-*' folder is based on the version of the rpm installed in the step above
- The results of the firmware upgrade are saved to the Component.log file, located in the /var/cpq/ directory
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps
To use HP Smart Update Manager from the HP Service Pack for ProLiant:
Offline:
- Place the HP Service Pack for ProLiant on a USB key using the HP USB Key Creator Utility
- Place the desired firmware to be updated in the directory, /hp/swpackages on the USB key
- Boot from the newly created HP Service Pack for Proliant USB key
- Follow HP Smart Update Manager steps to complete firmware update
Online:
- Login as root. (You must be root in order to apply the ROM update.)
- Place the desired firmware to be updated in the directory, /hp/swpackages
- Locate Start.html which is found in the root of the ISO
- Open the html file in a supported browser
- Follow the instructions on the screen
]]>
To update firmware from Linux operating system on target server:
Updating firmware with rpm installed:
- Install the firmware rpm using the command: rpm -ivh <rpm_filename>. This extracts the contents of the rpm to the '/usr/lib/i386-linux-gnu' location
- The CP027483.scexe script is located in the 'hp-scexe-compat' folder. The actual name of the 'hp-firmware-smartarray-14ef73e580-*' folder is based on the version of the rpm installed in the first step above
- To install firmware, you can execute ONE of the following commands:
# ./CP027483.scexe in the '/usr/lib/i386-linux-gnu/hp-scexe-compat' location (OR)
# ./hpsetup in the '/usr/lib/i386-linux-gnu/hp-firmware-smartarray-14ef73e580-*' location
- The results of the firmware upgrade are saved to the Component.log file, located in the /var/cpq/ directory
- To uninstall the rpm, run the command: rpm -e <rpm_package_name>, which is the rpm filename without the '.rpm' extension
Updating firmware without installing the rpm:
- Extract the contents of the rpm using the command: rpm2cpio <rpm_filename>.rpm | cpio -id. This extracts the contents of the rpm to 'usr' folder in the current directory
- Navigate to the 'usr/lib/i386-linux-gnu/hp-firmware-smartarray-14ef73e580-*' location and run ./hpsetup to update the firmware. The actual name of the 'hp-firmware-smartarray-14ef73e580-*' folder is based on the version of the rpm installed in the step above
- The results of the firmware upgrade are saved to the Component.log file, located in the /var/cpq/ directory
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps
To use HP Smart Update Manager from the HP Service Pack for ProLiant:
Offline:
- Place the HP Service Pack for ProLiant on a USB key using the HP USB Key Creator Utility
- Place the desired firmware to be updated in the directory, /hp/swpackages on the USB key
- Boot from the newly created HP Service Pack for Proliant USB key
- Follow HP Smart Update Manager steps to complete firmware update
Online:
- Login as root. (You must be root in order to apply the ROM update.)
- Place the desired firmware to be updated in the directory, /hp/swpackages
- Locate Start.html which is found in the root of the ISO
- Open the html file in a supported browser
- Follow the instructions on the screen
]]>
To update firmware from Linux operating system on target server:
Updating firmware with rpm installed:
- Install the firmware rpm using the command: rpm -ivh <rpm_filename>. This extracts the contents of the rpm to the '/usr/lib/i386-linux-gnu' location
- The CP027483.scexe script is located in the 'hp-scexe-compat' folder. The actual name of the 'hp-firmware-smartarray-14ef73e580-*' folder is based on the version of the rpm installed in the first step above
- To install firmware, you can execute ONE of the following commands:
# ./CP027483.scexe in the '/usr/lib/i386-linux-gnu/hp-scexe-compat' location (OR)
# ./hpsetup in the '/usr/lib/i386-linux-gnu/hp-firmware-smartarray-14ef73e580-*' location
- The results of the firmware upgrade are saved to the Component.log file, located in the /var/cpq/ directory
- To uninstall the rpm, run the command: rpm -e <rpm_package_name>, which is the rpm filename without the '.rpm' extension
Updating firmware without installing the rpm:
- Extract the contents of the rpm using the command: rpm2cpio <rpm_filename>.rpm | cpio -id. This extracts the contents of the rpm to 'usr' folder in the current directory
- Navigate to the 'usr/lib/i386-linux-gnu/hp-firmware-smartarray-14ef73e580-*' location and run ./hpsetup to update the firmware. The actual name of the 'hp-firmware-smartarray-14ef73e580-*' folder is based on the version of the rpm installed in the step above
- The results of the firmware upgrade are saved to the Component.log file, located in the /var/cpq/ directory
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps
To use HP Smart Update Manager from the HP Service Pack for ProLiant:
Offline:
- Place the HP Service Pack for ProLiant on a USB key using the HP USB Key Creator Utility
- Place the desired firmware to be updated in the directory, /hp/swpackages on the USB key
- Boot from the newly created HP Service Pack for Proliant USB key
- Follow HP Smart Update Manager steps to complete firmware update
Online:
- Login as root. (You must be root in order to apply the ROM update.)
- Place the desired firmware to be updated in the directory, /hp/swpackages
- Locate Start.html which is found in the root of the ISO
- Open the html file in a supported browser
- Follow the instructions on the screen
]]>
To update firmware from Linux operating system on target server:
Updating firmware with rpm installed:
- Install the firmware rpm using the command: rpm -ivh <rpm_filename>. This extracts the contents of the rpm to the '/usr/lib/i386-linux-gnu' location
- The CP027483.scexe script is located in the 'hp-scexe-compat' folder. The actual name of the 'hp-firmware-smartarray-14ef73e580-*' folder is based on the version of the rpm installed in the first step above
- To install firmware, you can execute ONE of the following commands:
# ./CP027483.scexe in the '/usr/lib/i386-linux-gnu/hp-scexe-compat' location (OR)
# ./hpsetup in the '/usr/lib/i386-linux-gnu/hp-firmware-smartarray-14ef73e580-*' location
- The results of the firmware upgrade are saved to the Component.log file, located in the /var/cpq/ directory
- To uninstall the rpm, run the command: rpm -e <rpm_package_name>, which is the rpm filename without the '.rpm' extension
Updating firmware without installing the rpm:
- Extract the contents of the rpm using the command: rpm2cpio <rpm_filename>.rpm | cpio -id. This extracts the contents of the rpm to 'usr' folder in the current directory
- Navigate to the 'usr/lib/i386-linux-gnu/hp-firmware-smartarray-14ef73e580-*' location and run ./hpsetup to update the firmware. The actual name of the 'hp-firmware-smartarray-14ef73e580-*' folder is based on the version of the rpm installed in the step above
- The results of the firmware upgrade are saved to the Component.log file, located in the /var/cpq/ directory
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps
To use HP Smart Update Manager from the HP Service Pack for ProLiant:
Offline:
- Place the HP Service Pack for ProLiant on a USB key using the HP USB Key Creator Utility
- Place the desired firmware to be updated in the directory, /hp/swpackages on the USB key
- Boot from the newly created HP Service Pack for Proliant USB key
- Follow HP Smart Update Manager steps to complete firmware update
Online:
- Login as root. (You must be root in order to apply the ROM update.)
- Place the desired firmware to be updated in the directory, /hp/swpackages
- Locate Start.html which is found in the root of the ISO
- Open the html file in a supported browser
- Follow the instructions on the screen
]]>
To update firmware from Linux operating system on target server:
Updating firmware with rpm installed:
- Install the firmware rpm using the command: rpm -ivh <rpm_filename>. This extracts the contents of the rpm to the '/usr/lib/i386-linux-gnu' location
- The CP027483.scexe script is located in the 'hp-scexe-compat' folder. The actual name of the 'hp-firmware-smartarray-14ef73e580-*' folder is based on the version of the rpm installed in the first step above
- To install firmware, you can execute ONE of the following commands:
# ./CP027483.scexe in the '/usr/lib/i386-linux-gnu/hp-scexe-compat' location (OR)
# ./hpsetup in the '/usr/lib/i386-linux-gnu/hp-firmware-smartarray-14ef73e580-*' location
- The results of the firmware upgrade are saved to the Component.log file, located in the /var/cpq/ directory
- To uninstall the rpm, run the command: rpm -e <rpm_package_name>, which is the rpm filename without the '.rpm' extension
Updating firmware without installing the rpm:
- Extract the contents of the rpm using the command: rpm2cpio <rpm_filename>.rpm | cpio -id. This extracts the contents of the rpm to 'usr' folder in the current directory
- Navigate to the 'usr/lib/i386-linux-gnu/hp-firmware-smartarray-14ef73e580-*' location and run ./hpsetup to update the firmware. The actual name of the 'hp-firmware-smartarray-14ef73e580-*' folder is based on the version of the rpm installed in the step above
- The results of the firmware upgrade are saved to the Component.log file, located in the /var/cpq/ directory
Additional Information:
Installing the firmware rpm package (rpm -ivh) does not update the firmware. It merely extracts the rpm content to the local system. Updating the firmware on the local system requires following the above outlined steps
To use HP Smart Update Manager from the HP Service Pack for ProLiant:
Offline:
- Place the HP Service Pack for ProLiant on a USB key using the HP USB Key Creator Utility
- Place the desired firmware to be updated in the directory, /hp/swpackages on the USB key
- Boot from the newly created HP Service Pack for Proliant USB key
- Follow HP Smart Update Manager steps to complete firmware update
Online:
- Login as root. (You must be root in order to apply the ROM update.)
- Place the desired firmware to be updated in the directory, /hp/swpackages
- Locate Start.html which is found in the root of the ISO
- Open the html file in a supported browser
- Follow the instructions on the screen
]]>
Deliverable Name:
Supplemental Update / Online ROM Flash Component for Linux - Smart Array P212, P410, P410i, P411, P711m, P712m, and P812
Release Version and/or Date:
6.64 (B)
Last Recommended or Critical Version:
6.64 (B)
Previous Version of Firmware:
6.64
Firmware Dependency:
None
Enhancements/New Features:
None
Problems Fixed:
- Running SMARTCTL (smartmontools) on HP Proliant G6/G7 (Px1x) Smart Array controllers that have firmware version 5.70 to 6.62 installed with SATA drives attached may result in system not responding or reboot. Wehn reboot occurred, a reboot 1719 POST error message with lockup 0x15 displayed.
Known Issues:
None
]]>
Deliverable Name:
Supplemental Update / Online ROM Flash Component for Linux - Smart Array P212, P410, P410i, P411, P711m, P712m, and P812
Release Version and/or Date:
6.64 (B)
Last Recommended or Critical Version:
6.64 (B)
Previous Version of Firmware:
6.64
Firmware Dependency:
None
Enhancements/New Features:
None
Problems Fixed:
- Running SMARTCTL (smartmontools) on HP Proliant G6/G7 (Px1x) Smart Array controllers that have firmware version 5.70 to 6.62 installed with SATA drives attached may result in system not responding or reboot. Wehn reboot occurred, a reboot 1719 POST error message with lockup 0x15 displayed.
Known Issues:
None
]]>
Deliverable Name:
Supplemental Update / Online ROM Flash Component for Linux - Smart Array P212, P410, P410i, P411, P711m, P712m, and P812
Release Version and/or Date:
6.64 (B)
Last Recommended or Critical Version:
6.64 (B)
Previous Version of Firmware:
6.64
Firmware Dependency:
None
Enhancements/New Features:
None
Problems Fixed:
- Running SMARTCTL (smartmontools) on HP Proliant G6/G7 (Px1x) Smart Array controllers that have firmware version 5.70 to 6.62 installed with SATA drives attached may result in system not responding or reboot. Wehn reboot occurred, a reboot 1719 POST error message with lockup 0x15 displayed.
Known Issues:
None
]]>
Deliverable Name:
Supplemental Update / Online ROM Flash Component for Linux - Smart Array P212, P410, P410i, P411, P711m, P712m, and P812
Release Version and/or Date:
6.64 (B)
Last Recommended or Critical Version:
6.64 (B)
Previous Version of Firmware:
6.64
Firmware Dependency:
None
Enhancements/New Features:
None
Problems Fixed:
- Running SMARTCTL (smartmontools) on HP Proliant G6/G7 (Px1x) Smart Array controllers that have firmware version 5.70 to 6.62 installed with SATA drives attached may result in system not responding or reboot. Wehn reboot occurred, a reboot 1719 POST error message with lockup 0x15 displayed.
Known Issues:
None
]]>
Deliverable Name:
Supplemental Update / Online ROM Flash Component for Linux - Smart Array P212, P410, P410i, P411, P711m, P712m, and P812
Release Version and/or Date:
6.64 (B)
Last Recommended or Critical Version:
6.64 (B)
Previous Version of Firmware:
6.64
Firmware Dependency:
None
Enhancements/New Features:
None
Problems Fixed:
- Running SMARTCTL (smartmontools) on HP Proliant G6/G7 (Px1x) Smart Array controllers that have firmware version 5.70 to 6.62 installed with SATA drives attached may result in system not responding or reboot. Wehn reboot occurred, a reboot 1719 POST error message with lockup 0x15 displayed.
Known Issues:
None
]]>
Deliverable Name:
Supplemental Update / Online ROM Flash Component for Linux - Smart Array P212, P410, P410i, P411, P711m, P712m, and P812
Release Version and/or Date:
6.64 (B)
Last Recommended or Critical Version:
6.64 (B)
Previous Version of Firmware:
6.64
Firmware Dependency:
None
Enhancements/New Features:
None
Problems Fixed:
- Running SMARTCTL (smartmontools) on HP Proliant G6/G7 (Px1x) Smart Array controllers that have firmware version 5.70 to 6.62 installed with SATA drives attached may result in system not responding or reboot. Wehn reboot occurred, a reboot 1719 POST error message with lockup 0x15 displayed.
Known Issues:
None
]]>
Deliverable Name:
Supplemental Update / Online ROM Flash Component for Linux - Smart Array P212, P410, P410i, P411, P711m, P712m, and P812
Release Version and/or Date:
6.64 (B)
Last Recommended or Critical Version:
6.64 (B)
Previous Version of Firmware:
6.64
Firmware Dependency:
None
Enhancements/New Features:
None
Problems Fixed:
- Running SMARTCTL (smartmontools) on HP Proliant G6/G7 (Px1x) Smart Array controllers that have firmware version 5.70 to 6.62 installed with SATA drives attached may result in system not responding or reboot. Wehn reboot occurred, a reboot 1719 POST error message with lockup 0x15 displayed.
Known Issues:
None
]]>
Deliverable Name:
Supplemental Update / Online ROM Flash Component for Linux - Smart Array P212, P410, P410i, P411, P711m, P712m, and P812
Release Version and/or Date:
6.64 (B)
Last Recommended or Critical Version:
6.64 (B)
Previous Version of Firmware:
6.64
Firmware Dependency:
None
Enhancements/New Features:
None
Problems Fixed:
- Running SMARTCTL (smartmontools) on HP Proliant G6/G7 (Px1x) Smart Array controllers that have firmware version 5.70 to 6.62 installed with SATA drives attached may result in system not responding or reboot. Wehn reboot occurred, a reboot 1719 POST error message with lockup 0x15 displayed.
Known Issues:
None
]]>
Deliverable Name:
Supplemental Update / Online ROM Flash Component for Linux - Smart Array P212, P410, P410i, P411, P711m, P712m, and P812
Release Version and/or Date:
6.64 (B)
Last Recommended or Critical Version:
6.64 (B)
Previous Version of Firmware:
6.64
Firmware Dependency:
None
Enhancements/New Features:
None
Problems Fixed:
- Running SMARTCTL (smartmontools) on HP Proliant G6/G7 (Px1x) Smart Array controllers that have firmware version 5.70 to 6.62 installed with SATA drives attached may result in system not responding or reboot. Wehn reboot occurred, a reboot 1719 POST error message with lockup 0x15 displayed.
Known Issues:
None
]]>
在固件版本为5.70到6.62且连接SATA硬盘的HP Proliant G6/G7 (Px1x)智能阵列控制器上运行SMARTCTL (smartmontools)可能会导致系统不响应或重新启动。发生重启时,显示重启1719加电自检错误消息且锁定0x15。
]]>
Running SMARTCTL (smartmontools) on HP Proliant G6/G7 (Px1x) Smart Array controllers that have firmware version 5.70 to 6.62 installed with SATA drives attached may result in system not responding or reboot. When reboot occurred, a reboot 1719 POST error message with lockup 0x15 displayed.
]]>
Running SMARTCTL (smartmontools) on HP Proliant G6/G7 (Px1x) Smart Array controllers that have firmware version 5.70 to 6.62 installed with SATA drives attached may result in system not responding or reboot. When reboot occurred, a reboot 1719 POST error message with lockup 0x15 displayed.
]]>
Running SMARTCTL (smartmontools) on HP Proliant G6/G7 (Px1x) Smart Array controllers that have firmware version 5.70 to 6.62 installed with SATA drives attached may result in system not responding or reboot. When reboot occurred, a reboot 1719 POST error message with lockup 0x15 displayed.
]]>
Running SMARTCTL (smartmontools) on HP Proliant G6/G7 (Px1x) Smart Array controllers that have firmware version 5.70 to 6.62 installed with SATA drives attached may result in system not responding or reboot. When reboot occurred, a reboot 1719 POST error message with lockup 0x15 displayed.
]]>
Running SMARTCTL (smartmontools) on HP Proliant G6/G7 (Px1x) Smart Array controllers that have firmware version 5.70 to 6.62 installed with SATA drives attached may result in system not responding or reboot. When reboot occurred, a reboot 1719 POST error message with lockup 0x15 displayed.
]]>
SATAドライブが接続された、ファームウェアバージョン5.70から6.62のHP ProLiant G6/G7 (Px1x) Smartアレイコントローラー上で実行しているSMARTCTL (smartmontools)は、システムが応答しなくなるまたはリブートすることがあります。 リブートが起こった場合、lockup 0x15でリブート1719 POSTエラーメッセージが表示されます。
]]>
펌웨어 버전 5.70부터 6.62까지 설치되어 있고 SATA 드라이브가 장착된 HP Proliant G6/G7 (Px1x) 스마트 어레이 컨트롤러에서 SMARTCTL(smartmontools)를 실행할 경우 시스템이 응답하지 않거나 재부팅될 수 있습니다. 재부팅이 발생하는 경우 재부팅 1719 POST 오류 메시지가 록업 0x15와 함께 표시됩니다.
]]>
在安裝了韌體版本 5.70 至 6.62 並連接了 SATA 磁碟機的 HP Proliant G6/G7 (Px1x) Smart Array 控制器上執行 SMARTCTL (smartmontools) 可能會導致系統沒有回應或重新開機。當發生重新開機,會顯示重新啟動 1719 POST 錯誤訊息與 lockup 0x15。
]]>
在固件版本为5.70到6.62且连接SATA硬盘的HP Proliant G6/G7 (Px1x)智能阵列控制器上运行SMARTCTL (smartmontools)可能会导致系统不响应或重新启动。发生重启时,显示重启1719加电自检错误消息且锁定0x15。
]]>
Running SMARTCTL (smartmontools) on HP Proliant G6/G7 (Px1x) Smart Array controllers that have firmware version 5.70 to 6.62 installed with SATA drives attached may result in system not responding or reboot. When reboot occurred, a reboot 1719 POST error message with lockup 0x15 displayed.
]]>
Running SMARTCTL (smartmontools) on HP Proliant G6/G7 (Px1x) Smart Array controllers that have firmware version 5.70 to 6.62 installed with SATA drives attached may result in system not responding or reboot. When reboot occurred, a reboot 1719 POST error message with lockup 0x15 displayed.
]]>
Running SMARTCTL (smartmontools) on HP Proliant G6/G7 (Px1x) Smart Array controllers that have firmware version 5.70 to 6.62 installed with SATA drives attached may result in system not responding or reboot. When reboot occurred, a reboot 1719 POST error message with lockup 0x15 displayed.
]]>
Running SMARTCTL (smartmontools) on HP Proliant G6/G7 (Px1x) Smart Array controllers that have firmware version 5.70 to 6.62 installed with SATA drives attached may result in system not responding or reboot. When reboot occurred, a reboot 1719 POST error message with lockup 0x15 displayed.
]]>
Running SMARTCTL (smartmontools) on HP Proliant G6/G7 (Px1x) Smart Array controllers that have firmware version 5.70 to 6.62 installed with SATA drives attached may result in system not responding or reboot. When reboot occurred, a reboot 1719 POST error message with lockup 0x15 displayed.
]]>
SATAドライブが接続された、ファームウェアバージョン5.70から6.62のHP ProLiant G6/G7 (Px1x) Smartアレイコントローラー上で実行しているSMARTCTL (smartmontools)は、システムが応答しなくなるまたはリブートすることがあります。 リブートが起こった場合、lockup 0x15でリブート1719 POSTエラーメッセージが表示されます。
]]>
펌웨어 버전 5.70부터 6.62까지 설치되어 있고 SATA 드라이브가 장착된 HP Proliant G6/G7 (Px1x) 스마트 어레이 컨트롤러에서 SMARTCTL(smartmontools)를 실행할 경우 시스템이 응답하지 않거나 재부팅될 수 있습니다. 재부팅이 발생하는 경우 재부팅 1719 POST 오류 메시지가 록업 0x15와 함께 표시됩니다.
]]>
在安裝了韌體版本 5.70 至 6.62 並連接了 SATA 磁碟機的 HP Proliant G6/G7 (Px1x) Smart Array 控制器上執行 SMARTCTL (smartmontools) 可能會導致系統沒有回應或重新開機。當發生重新開機,會顯示重新啟動 1719 POST 錯誤訊息與 lockup 0x15。
]]>
增强功能/新功能:
- 当驱动器因过多恢复介质错误开始下降时,增强此时的性能。
]]>
Enhancements/New Features:
-
Performance enhancement when a drive starts to degrade due to excessive recovered media errors.
]]>
Enhancements/New Features:
-
Performance enhancement when a drive starts to degrade due to excessive recovered media errors.
]]>
Enhancements/New Features:
-
Performance enhancement when a drive starts to degrade due to excessive recovered media errors.
]]>
Enhancements/New Features:
-
Performance enhancement when a drive starts to degrade due to excessive recovered media errors.
]]>
Enhancements/New Features:
-
Performance enhancement when a drive starts to degrade due to excessive recovered media errors.
]]>
改善点/新しい機能:
-
ドライブが過剰な回復されたメディアエラーのために劣化が始まるときのパフォーマンスの向上。
]]>
향상된 기능/새로운 기능:
- 복구된 미디어 오류가 과도하여 드라이브의 기능이 저하되기 시작하더라도 성능이 향상됩니다.
]]>
增強或新增功能:
- 當磁碟機歸因於過多的還原媒體錯誤而開始降級時的效能增強。
]]>
已解决的问题:
- 在具有连接到在HP P2000 G3 SAS存储阵列上的逻辑卷的HP智能阵列P711m控制器的系统上,在安装VMware vSphere 5.5 Update 2期间,智能阵列设备驱动程序‘hpsa’将停止工作。
- 当在HP P2000 G3存储系统或HP MSA 2040 SAS存储阵列上的配置了逻辑卷的服务器上的Red Hat Enterprise Linux 6 Update 4或Update 5上的智能阵列设备驱动程序‘hpsa’升级到3.4.6-165版后,系统将停止工作并且在重启后报告一个HP智能阵列P712m控制器被锁定。(POST Error(加电自检错误):1719 - A controller failure event occurred prior to this power-up(此次上电前曾出现控制器故障).(Previous lock up code(上次锁定代码) = 0x13))
]]>
Problems Fixed:
-
On systems configured with HP Smart Array P711m controllers connected to logical volumes on HP P2000 G3 SAS storage arrays, the Smart Array device driver ‘hpsa’ would cease to function during installation of VMware vSphere 5.5 Update 2.
-
After the Smart Array device driver 'hpsa' was upgraded to version 3.4.6-165 on Red Hat Enterprise Linux 6 Update 4 or Update 5 on a server configured with logical volumes on HP P2000 G3 Storage Systems or HP MSA 2040 SAS Storage Arrays, the system would cease to function and an HP Smart Array P712m controller lockup would be reported after reboot. (POST Error: 1719 - A controller failure event occurred prior to this power-up. (Previous lock up code = 0x13))
]]>
Problems Fixed:
-
On systems configured with HP Smart Array P711m controllers connected to logical volumes on HP P2000 G3 SAS storage arrays, the Smart Array device driver ‘hpsa’ would cease to function during installation of VMware vSphere 5.5 Update 2.
-
After the Smart Array device driver 'hpsa' was upgraded to version 3.4.6-165 on Red Hat Enterprise Linux 6 Update 4 or Update 5 on a server configured with logical volumes on HP P2000 G3 Storage Systems or HP MSA 2040 SAS Storage Arrays, the system would cease to function and an HP Smart Array P712m controller lockup would be reported after reboot. (POST Error: 1719 - A controller failure event occurred prior to this power-up. (Previous lock up code = 0x13))
]]>
Problems Fixed:
-
On systems configured with HP Smart Array P711m controllers connected to logical volumes on HP P2000 G3 SAS storage arrays, the Smart Array device driver ‘hpsa’ would cease to function during installation of VMware vSphere 5.5 Update 2.
-
After the Smart Array device driver 'hpsa' was upgraded to version 3.4.6-165 on Red Hat Enterprise Linux 6 Update 4 or Update 5 on a server configured with logical volumes on HP P2000 G3 Storage Systems or HP MSA 2040 SAS Storage Arrays, the system would cease to function and an HP Smart Array P712m controller lockup would be reported after reboot. (POST Error: 1719 - A controller failure event occurred prior to this power-up. (Previous lock up code = 0x13))
]]>
Problems Fixed:
-
On systems configured with HP Smart Array P711m controllers connected to logical volumes on HP P2000 G3 SAS storage arrays, the Smart Array device driver ‘hpsa’ would cease to function during installation of VMware vSphere 5.5 Update 2.
-
After the Smart Array device driver 'hpsa' was upgraded to version 3.4.6-165 on Red Hat Enterprise Linux 6 Update 4 or Update 5 on a server configured with logical volumes on HP P2000 G3 Storage Systems or HP MSA 2040 SAS Storage Arrays, the system would cease to function and an HP Smart Array P712m controller lockup would be reported after reboot. (POST Error: 1719 - A controller failure event occurred prior to this power-up. (Previous lock up code = 0x13))
]]>
Problems Fixed:
-
On systems configured with HP Smart Array P711m controllers connected to logical volumes on HP P2000 G3 SAS storage arrays, the Smart Array device driver ‘hpsa’ would cease to function during installation of VMware vSphere 5.5 Update 2.
-
After the Smart Array device driver 'hpsa' was upgraded to version 3.4.6-165 on Red Hat Enterprise Linux 6 Update 4 or Update 5 on a server configured with logical volumes on HP P2000 G3 Storage Systems or HP MSA 2040 SAS Storage Arrays, the system would cease to function and an HP Smart Array P712m controller lockup would be reported after reboot. (POST Error: 1719 - A controller failure event occurred prior to this power-up. (Previous lock up code = 0x13))
]]>
修正された問題点:
-
HP P2000 G3 SASストレージアレイ上の論理ボリュームに接続されたHP SmartアレイP711mコントローラーで構成されたシステムでは、Smartアレイデバイスドライバー ‘hpsa’ は、VMware vSphere 5.5 Update 2のインストール中に機能しなくなります。
-
HP P2000 G3ストレージシステムまたはHP MSA 2040 SASストレージアレイ上の論理ボリュームで構成されたサーバー上のRed Hat Enterprise Linux 6 Update 4またはUpdate 5でSmartアレイデバイスドライバー 'hpsa'が、バージョン3.4.6-165にアップグレードされた後、システムが機能しなくなり、HP SmartアレイP712mコントローラーのロックアップがリブート後に報告されます。 (POST Error: 1719 - A controller failure event occurred prior to this power-up. (Previous lock up code = 0x13))
]]>
해결된 문제:
- HP P2000 G3 SAS 스토리지 어레이의 논리 볼륨과 연결된 HP 스마트 어레이 P711m 컨트롤러로 구성된 시스템에서 VMware vSphere 5.5 Update 2를 설치하는 동안 스마트 어레이 장치 드라이버 ‘hpsa’가 작동을 중지합니다.
- 스마트 어레이 장치 드라이버 'hpsa'가 HP P2000 G3 스토리지 시스템 또는 HP MSA 2040 SAS 스토리지 어레이에 있는 논리 볼륨으로 구성된 서버에서 Red Hat Enterprise Linux 6 Update 4 또는 Update 5의 3.4.6-165로 업그레이드되면 시스템이 작동을 멈추고 다시 부팅된 후 HP 스마트 어레이 P712m 컨트롤러 잠금이 보고됩니다. (POST 오류: 1719- - A Controller failure event occurred prior to this power-up. (Previous lock up code = 0x13))
]]>
修正的問題:
- 在設定使用連線至 HP P2000 G3 SAS 儲存陣列邏輯磁碟區的 HP Smart Array P711m 控制器上,安裝 VMware vSphere 5.5 更新 2.期間,Smart Array 裝置驅動程式「hpsa」會停止運作。
- 在設定使用 HP P2000 G3 儲存系統邏輯磁碟區或 HP MSA 2040 SAS 儲存陣列邏輯磁碟區的的伺服器上, Smart Array 裝置驅動程式「hpsa」升級至 Red Hat Enterprise Linux 6 更新 4 或更新 5 版本 3.4.6-165 後,系統會停止運作且重新開機後會報告 HP Smart Array P712m 控制器鎖定。(POST Error:1719 - A controller failure event occurred prior to this power-up.(Previous lock up code = 0x13). (核心錯誤:1719 - 開機前發生控制器故障事件. (先前鎖定碼 = 0x13))
]]>
增强功能/新功能:
- 增强了控制器SAS的发现逻辑,以允许可能重置的设备。
- 增加了一条新的POST消息1813,以便电池充电在电路出现故障或无法充电时进行提示。
]]>
Enhancements/New Features:
-
Enhanced the controller SAS discovery logic to tolerate devices that may be resetting.
-
Added a new POST message 1813 to indicate bad or failed battery charge circuit.
]]>
Enhancements/New Features:
-
Enhanced the controller SAS discovery logic to tolerate devices that may be resetting.
-
Added a new POST message 1813 to indicate bad or failed battery charge circuit.
]]>
Enhancements/New Features:
-
Enhanced the controller SAS discovery logic to tolerate devices that may be resetting.
-
Added a new POST message 1813 to indicate bad or failed battery charge circuit.
]]>
Enhancements/New Features:
-
Enhanced the controller SAS discovery logic to tolerate devices that may be resetting.
-
Added a new POST message 1813 to indicate bad or failed battery charge circuit.
]]>
Enhancements/New Features:
-
Enhanced the controller SAS discovery logic to tolerate devices that may be resetting.
-
Added a new POST message 1813 to indicate bad or failed battery charge circuit.
]]>
改善点/新しい機能:
-
リセットしているかもしれないデバイスを許容するためにコントローラーSAS検出ロジックを強化しました。
-
不良またはバッテリ充電回路の障害を示すために、新しいPOSTメッセージ1813を追加しました。
]]>
:
- 재설정 중일 수도 있는 장치를 허용할 수 있도록 SAS 검색 논리를 개선했습니다.
- 불량이거나 오류가 있는 배터리 충전 회로를 표시하기 위해 새 POST 메시지 1813을 추가하였습니다.
]]>
增強或新增功能:
- 已增強控制器 SAS 探索邏輯,可容許裝置重設。
- 已新增新 POST 訊息 1813,指出損壞或故障的電池充電電路。
]]>
6.60 版本修复的问题:
该版固件解决了以下问题:
- 在EFI ORCA执行模式切换后,运行以下命令后将不会显示控制器名称: “reconnect –r”。
- 当配置控制器以便在没有超级电容的情况下工作时,控制器显示POST错误消息1805“未安装高速缓存模块超级电容(Cache Module Super–Cap is not installed)”。
- 改进HDD的耐热表现。
- 配有一个或多个SATA备用驱动器和6.40(或更低版本)固件的控制器可能在64、128、或256天后停止并出现"Lockup Code = 0xAB"。
- HP智能阵列P812控制器板载扩展器固件更新至3.12版,以加强3Gbps SATA连接速度,这是HP智能阵列 P212、P410、P410i、P411、P711m、P712m和P812控制器支持的最大SATA数据速率。
]]>
Problems Fixed in version 6.60:
This firmware release resolved the following issues:
-
After a mode toggle at EFI ORCA was performed, the controller name would not be displayed when running the command: “reconnect –r”.
-
Controller displayed a POST error message 1805 “Cache Module Super–Cap is not installed” when the controller was configured to work without super-capacitors.
-
Corrected thermal behavior with HDDs.
-
Controllers configured with one or more SATA spare drives and firmware version 6.40 (or earlier) may halt with "Lockup Code = 0xAB" after 64, 128, or 256 days.
-
HP Smart Array P812 controller onboard expander firmware was updated to version 3.12 to enforce 3Gbps SATA connection speeds which is the maximum supported SATA data rate on HP Smart Array P212, P410, P410i, P411, P711m, P712m, and P812 controllers.
]]>
Problems Fixed in version 6.60:
This firmware release resolved the following issues:
-
After a mode toggle at EFI ORCA was performed, the controller name would not be displayed when running the command: “reconnect –r”.
-
Controller displayed a POST error message 1805 “Cache Module Super–Cap is not installed” when the controller was configured to work without super-capacitors.
-
Corrected thermal behavior with HDDs.
-
Controllers configured with one or more SATA spare drives and firmware version 6.40 (or earlier) may halt with "Lockup Code = 0xAB" after 64, 128, or 256 days.
-
HP Smart Array P812 controller onboard expander firmware was updated to version 3.12 to enforce 3Gbps SATA connection speeds which is the maximum supported SATA data rate on HP Smart Array P212, P410, P410i, P411, P711m, P712m, and P812 controllers.
]]>
Problems Fixed in version 6.60:
This firmware release resolved the following issues:
-
After a mode toggle at EFI ORCA was performed, the controller name would not be displayed when running the command: “reconnect –r”.
-
Controller displayed a POST error message 1805 “Cache Module Super–Cap is not installed” when the controller was configured to work without super-capacitors.
-
Corrected thermal behavior with HDDs.
-
Controllers configured with one or more SATA spare drives and firmware version 6.40 (or earlier) may halt with "Lockup Code = 0xAB" after 64, 128, or 256 days.
-
HP Smart Array P812 controller onboard expander firmware was updated to version 3.12 to enforce 3Gbps SATA connection speeds which is the maximum supported SATA data rate on HP Smart Array P212, P410, P410i, P411, P711m, P712m, and P812 controllers.
]]>
Problems Fixed in version 6.60:
This firmware release resolved the following issues:
-
After a mode toggle at EFI ORCA was performed, the controller name would not be displayed when running the command: “reconnect –r”.
-
Controller displayed a POST error message 1805 “Cache Module Super–Cap is not installed” when the controller was configured to work without super-capacitors.
-
Corrected thermal behavior with HDDs.
-
Controllers configured with one or more SATA spare drives and firmware version 6.40 (or earlier) may halt with "Lockup Code = 0xAB" after 64, 128, or 256 days.
-
HP Smart Array P812 controller onboard expander firmware was updated to version 3.12 to enforce 3Gbps SATA connection speeds which is the maximum supported SATA data rate on HP Smart Array P212, P410, P410i, P411, P711m, P712m, and P812 controllers.
]]>
Problems Fixed in version 6.60:
This firmware release resolved the following issues:
-
After a mode toggle at EFI ORCA was performed, the controller name would not be displayed when running the command: “reconnect –r”.
-
Controller displayed a POST error message 1805 “Cache Module Super–Cap is not installed” when the controller was configured to work without super-capacitors.
-
Corrected thermal behavior with HDDs.
-
Controllers configured with one or more SATA spare drives and firmware version 6.40 (or earlier) may halt with "Lockup Code = 0xAB" after 64, 128, or 256 days.
-
HP Smart Array P812 controller onboard expander firmware was updated to version 3.12 to enforce 3Gbps SATA connection speeds which is the maximum supported SATA data rate on HP Smart Array P212, P410, P410i, P411, P711m, P712m, and P812 controllers.
]]>
バージョン6.60で修正された問題:
このファームウェアリリースは、次の問題を解決しました。
-
EFI ORCAでモードの切り替えを行った後に、コマンド “reconnect -r” を実行すると、コントローラー名が表示されませんでした。
-
コントローラーがスーパーキャパシターなしで動作するように構成された場合、コントローラーがPOSTエラーメッセージ1805 “Cache Module Super-Cap is not installed” を表示しました。
-
HDDでの温度動作を修正しました。
-
1つ以上のSATAスペアドライブおよびファームウェアバージョンが6.40(またはそれ以前)で構成されたコントローラーが、64、128および256日経過後に"Lockup Code = 0xAB"により停止することがあります。
-
HP SmartアレイP212, P410, P410i, P411, P711m, P712mおよびP812コントローラーでサポートされる最大のSATAデータレートである3GbpsのSATA接続速度を実行するために、HP SmartアレイP812コントローラーのオンボードエキスパンダーファームウェアが、バージョン3.12にアップデートされました。
]]>
버전 6.60에서 해결된 문제:
이 펌웨어 릴리스에서 다음과 같은 문제가 해결되었습니다.
- EFI ORCA에서 모드 전환을 수행한 후, 다음 명령을 실행하면 컨트롤러 이름이 표시되지 않습니다. “reconnect –r”.
- 컨트롤러가 슈퍼 커패시터가 없는 상태로 작동하도록 구성된 경우 POST 오류 메시지 1805 "캐시 모듈 슈퍼 커패시터가 설치되지 않음"을 표시했습니다.
- HDD의 열 동작이 교정되었습니다.
- 하나 이상의 SATA 여분 드라이브 및 펌웨어 버전 6.40(또는 이전)으로 구성된 컨트롤러는 64, 128 또는 256일 후 "록업 코드 = 0xAB"와 함께 정지될 수 있습니다.
- HP 스마트 어레이 P812 컨트롤러 온보드 익스팬더 펌웨어는 HP 스마트 어레이 P212, P410, P410i, P411, P711m, P712m 및 P812 컨트롤러에서 지원되는 최대 SATA 데이터 속도인 3Gbps SATA 연결 속도를 강제 적용하도록 버전 3.12로 업데이트되었습니다.
]]>
6.60 版中修正的問題:
此韌體版本已解決下列問題:
- 在 EFI ORCA 執行模式切換後,執行命令 「reconnect –r」時不會顯示控制器名稱。
- 當設定控制器在無超級電容器情況中運作時,控制器顯示 POST 錯誤訊息 1805「Cache Module Super–Cap is not installed (未安裝快取模組超級電容器)」。
- 已修正 HDD 的熱活動問題。
- 控制器設定為具有一或多個 SATA 備用磁碟機且使用韌體版本 6.40 (或更早版本) 時,64、128,或 256 天後控制器可能會中止且「鎖定代碼 = 0xAB」。
- HP Smart Array P812 控制器的內建擴充卡韌體已更新至 3.12 版本,會強制採用 3Gbps SATA 連線速度,此為的 HP Smart Array P212、P410、P410i、P411、P711m、P712m 與 P812 控制器上支援的最大 SATA 資料速率。
]]>
增强功能/新功能:
]]>
Enhancements/New Features:
-
Enhanced the firmware to enable discovery of HDD.
]]>
Enhancements/New Features:
-
Enhanced the firmware to enable discovery of HDD.
]]>
Enhancements/New Features:
-
Enhanced the firmware to enable discovery of HDD.
]]>
Enhancements/New Features:
-
Enhanced the firmware to enable discovery of HDD.
]]>
Enhancements/New Features:
-
Enhanced the firmware to enable discovery of HDD.
]]>
改善点/新しい機能:
-
HDDの検出を可能にするためにファームウェアを改善しました。
]]>
향상된 기능/새로운 기능:
- HDD의 검색을 활성화하도록 펌웨어가 향상되었습니다.
]]>
增強或新增功能:
]]>
已解决的问题:
- SATA驱动器配置为备用的60天或更多时间,存储控制器可能会锁定,报告为0xAB错误。
- 改进HDD的耐热表现。
]]>
Problems Fixed:
-
When SATA drives are configured as spares for a period of 60 days or more, the storage controller would lockup, reporting as 0xAB error.
-
Corrected Thermal behavior with HDDs.
]]>
Problems Fixed:
-
When SATA drives are configured as spares for a period of 60 days or more, the storage controller would lockup, reporting as 0xAB error.
-
Corrected Thermal behavior with HDDs.
]]>
Problems Fixed:
-
When SATA drives are configured as spares for a period of 60 days or more, the storage controller would lockup, reporting as 0xAB error.
-
Corrected Thermal behavior with HDDs.
]]>
Problems Fixed:
-
When SATA drives are configured as spares for a period of 60 days or more, the storage controller would lockup, reporting as 0xAB error.
-
Corrected Thermal behavior with HDDs.
]]>
Problems Fixed:
-
When SATA drives are configured as spares for a period of 60 days or more, the storage controller would lockup, reporting as 0xAB error.
-
Corrected Thermal behavior with HDDs.
]]>
修正された問題点:
-
SATAドライブが60日以上の期間、スペアとして構成されている場合、ストレージコントローラーがロックアップし、0xABエラーとして報告されます。
-
HDDでの温度動作を修正しました。
]]>
해결된 문제:
- SATA 드라이브가 60일 이상 동안 예비 부품으로 구성되면 스토리지 컨트롤러가 잠기고 0xAB 오류가 보고됩니다.
- HDD의 열 동작이 교정되었습니다.
]]>
修正的問題:
- SATA 磁碟機設定為備援磁碟機且期限為 60 天或以上時,儲存控制器會鎖定,報告為 0xAB 錯誤。
- 已修正 HDD 的熱活動問題。
]]>
已解决的问题:
]]>
Problems Fixed:
-
Corrected Thermal behavior with HDDs
]]>
Problems Fixed:
-
Corrected Thermal behavior with HDDs
]]>
Problems Fixed:
-
Corrected Thermal behavior with HDDs
]]>
Problems Fixed:
-
Corrected Thermal behavior with HDDs
]]>
Problems Fixed:
-
Corrected Thermal behavior with HDDs
]]>
修正された問題点:
]]>
해결된 문제:
]]>
修正的問題:
]]>
增强功能/新功能:
- 当存储驱动程序发出请求时,允许 Windows Server 2012 驱动程序利用命令对高于较低的 4GB 内存区域进行寻址。
]]>
Enhancements/New Features:
-
Allow Windows Server 2012 drivers to utilize command addressing above the lower 4GB memory region when requested by the storage driver.
]]>
Enhancements/New Features:
-
Allow Windows Server 2012 drivers to utilize command addressing above the lower 4GB memory region when requested by the storage driver.
]]>
Enhancements/New Features:
-
Allow Windows Server 2012 drivers to utilize command addressing above the lower 4GB memory region when requested by the storage driver.
]]>
Enhancements/New Features:
-
Allow Windows Server 2012 drivers to utilize command addressing above the lower 4GB memory region when requested by the storage driver.
]]>
Enhancements/New Features:
-
Allow Windows Server 2012 drivers to utilize command addressing above the lower 4GB memory region when requested by the storage driver.
]]>
改善点/新しい機能:
-
ストレージドライバーによって要求されたときに、Windows Server 2012ドライバーは4GB以下のメモリ領域上でコマンドアドレッシングを利用することができます。
]]>
:
- 저장소 드라이버의 요청 시 Windows Server 2012 드라이버는 4GB의 낮은 메모리 영역 위로 주소 지정 명령을 이용할 수 있습니다.
]]>
:
- 當儲存驅動程式請求時,允許 Windows Server 2012 驅動程式在較低的 4GB 記憶體區域上方使用命令定址。
]]>
6.40(B)版本解决的问题:
- 安装用于智能阵列P410i控制器的6.40版在线智能阵列工具智能组件时,有时会用错误的固件更新HP D2200sb存储刀片中的SAS扩展器,导致智能阵列P410i控制器无法与安装在HP D2200sb存储刀片中的硬盘通讯,此版本已解决了该问题。该问题的其他重要信息,请参考客户顾问文档c03964262。
6.40 版本解决的问题:
- 使用 HP 智能阵列 P410i 控制器固件版本 5.76 或更高版本的 HP BL465c G7 或 HP BL685c G7 刀片系统上通报假的 POST 1705 消息。POST 指示超级电容出现故障,依次禁用写缓存。
- 在极少数情况下,POST 期间控制器停止响应。
- 有时,JBOD 中的 SATA 备份驱动器被标记为热删除并重新出现。
- 用户无法通过命令行界面调用 ORCA,通过 BIOS 串行控制台按 escape 组合键 “Esc+6” 或 “F6”,或 “Esc+8” 或“F8”。
注意: HP支持中心不再提供6.40版的下载,但6.40(B)版也提供了以下修复。
]]>
Problems Fixed in version 6.40(B):
-
Fixed an installation issue where version 6.40 of the Online Smart Array firmware smart components for the Smart Array P410i Controller would in some cases update the SAS expander in the HP D2200sb Storage Blade with incorrect firmware causing the Smart Array P410i Controller to be unable to communicate with the hard drives installed in the HP D2200sb Storage Blade. Reference Customer Advisory c03964262 for additional important information about this issue.
Problems Fixed in version 6.40:
-
False POST 1705 messages were being posted on the HP BL465c G7 or HP BL685c G7 Blade systems that used HP Smart Array P410i controller firmware version 5.76 or greater. The POST was indicateding a bad Super-Cap, which in turn disabled write caching.
-
On rare occasions the controller would become unresponsive during POST.
-
On intermittent occasions, SATA spare drives in a JBOD were being marked as hot removed and then rediscovered.
-
Customers could not invoke ORCA via command line interface, by pressing the escape key-strokes “Esc+6” or "F6" or “Esc+8” or "F8" via the BIOS Serial Console.
Note: Version 6.40 is no longer available for download from HP Support Center, but the following fixes are also provided in version 6.40(B).
]]>
Problems Fixed in version 6.40(B):
-
Fixed an installation issue where version 6.40 of the Online Smart Array firmware smart components for the Smart Array P410i Controller would in some cases update the SAS expander in the HP D2200sb Storage Blade with incorrect firmware causing the Smart Array P410i Controller to be unable to communicate with the hard drives installed in the HP D2200sb Storage Blade. Reference Customer Advisory c03964262 for additional important information about this issue.
Problems Fixed in version 6.40:
-
False POST 1705 messages were being posted on the HP BL465c G7 or HP BL685c G7 Blade systems that used HP Smart Array P410i controller firmware version 5.76 or greater. The POST was indicateding a bad Super-Cap, which in turn disabled write caching.
-
On rare occasions the controller would become unresponsive during POST.
-
On intermittent occasions, SATA spare drives in a JBOD were being marked as hot removed and then rediscovered.
-
Customers could not invoke ORCA via command line interface, by pressing the escape key-strokes “Esc+6” or "F6" or “Esc+8” or "F8" via the BIOS Serial Console.
Note: Version 6.40 is no longer available for download from HP Support Center, but the following fixes are also provided in version 6.40(B).
]]>
Problems Fixed in version 6.40(B):
-
Fixed an installation issue where version 6.40 of the Online Smart Array firmware smart components for the Smart Array P410i Controller would in some cases update the SAS expander in the HP D2200sb Storage Blade with incorrect firmware causing the Smart Array P410i Controller to be unable to communicate with the hard drives installed in the HP D2200sb Storage Blade. Reference Customer Advisory c03964262 for additional important information about this issue.
Problems Fixed in version 6.40:
-
False POST 1705 messages were being posted on the HP BL465c G7 or HP BL685c G7 Blade systems that used HP Smart Array P410i controller firmware version 5.76 or greater. The POST was indicateding a bad Super-Cap, which in turn disabled write caching.
-
On rare occasions the controller would become unresponsive during POST.
-
On intermittent occasions, SATA spare drives in a JBOD were being marked as hot removed and then rediscovered.
-
Customers could not invoke ORCA via command line interface, by pressing the escape key-strokes “Esc+6” or "F6" or “Esc+8” or "F8" via the BIOS Serial Console.
Note: Version 6.40 is no longer available for download from HP Support Center, but the following fixes are also provided in version 6.40(B).
]]>
Problems Fixed in version 6.40(B):
-
Fixed an installation issue where version 6.40 of the Online Smart Array firmware smart components for the Smart Array P410i Controller would in some cases update the SAS expander in the HP D2200sb Storage Blade with incorrect firmware causing the Smart Array P410i Controller to be unable to communicate with the hard drives installed in the HP D2200sb Storage Blade. Reference Customer Advisory c03964262 for additional important information about this issue.
Problems Fixed in version 6.40:
-
False POST 1705 messages were being posted on the HP BL465c G7 or HP BL685c G7 Blade systems that used HP Smart Array P410i controller firmware version 5.76 or greater. The POST was indicateding a bad Super-Cap, which in turn disabled write caching.
-
On rare occasions the controller would become unresponsive during POST.
-
On intermittent occasions, SATA spare drives in a JBOD were being marked as hot removed and then rediscovered.
-
Customers could not invoke ORCA via command line interface, by pressing the escape key-strokes “Esc+6” or "F6" or “Esc+8” or "F8" via the BIOS Serial Console.
Note: Version 6.40 is no longer available for download from HP Support Center, but the following fixes are also provided in version 6.40(B).
]]>
Problems Fixed in version 6.40(B):
-
Fixed an installation issue where version 6.40 of the Online Smart Array firmware smart components for the Smart Array P410i Controller would in some cases update the SAS expander in the HP D2200sb Storage Blade with incorrect firmware causing the Smart Array P410i Controller to be unable to communicate with the hard drives installed in the HP D2200sb Storage Blade. Reference Customer Advisory c03964262 for additional important information about this issue.
Problems Fixed in version 6.40:
-
False POST 1705 messages were being posted on the HP BL465c G7 or HP BL685c G7 Blade systems that used HP Smart Array P410i controller firmware version 5.76 or greater. The POST was indicateding a bad Super-Cap, which in turn disabled write caching.
-
On rare occasions the controller would become unresponsive during POST.
-
On intermittent occasions, SATA spare drives in a JBOD were being marked as hot removed and then rediscovered.
-
Customers could not invoke ORCA via command line interface, by pressing the escape key-strokes “Esc+6” or "F6" or “Esc+8” or "F8" via the BIOS Serial Console.
Note: Version 6.40 is no longer available for download from HP Support Center, but the following fixes are also provided in version 6.40(B).
]]>
バージョン6.40(B)で修正された問題:
-
SmartアレイP410iコントローラー用のオンラインSmartアレイファームウェアのSmartコンポーネントのバージョン6.40が、いくつかのケースで、SmartアレイP410iコントローラーがHP D2200sbストレージブレードにインストールされたハードディスクドライブと通信することができなくなることが発生する誤ったファームウェアでHP D2200sbストレージブレードのSASエキスパンダーをアップデートするインストールの問題を修正しました。 この問題に関する追加の重要な情報については、カスタマーアドバイザリc03964262を参照してください。
バージョン6.40で修正された問題:
-
HP SmartアレイP410iコントローラーのファームウェアバージョン5.76以降を使用したHP BL465c G7またはHP BL685c G7ブレードシステム上で誤ったPOST1705メッセージがポストされていました。 POSTは不良Super-Capを示し、次に書き込みキャッシングを無効にします。
-
まれに、コントローラーがPOST中に応答しなくなります。
-
断続的に、JBODのSATAスペアドライブがホットリムーブとマークされ、再検出されていました。
-
お客様は、BIOSシリアルコンソールを通してエスケープキーストローク"Esc+6"または"F6"または"Esc+8"または"F8" を押すことで、コマンドラインインターフェイスによりORCAを起動することができませんでした。
注: バージョン6.40はHPサポートセンターからダウンロードできなくなりましたが、以下の修正はバージョン6.40(B)で提供されています。
]]>
버전 6.40(B)에서 해결된 문제:
- 스마트 어레이 P410i 컨트롤러용 온라인 스마트 어레이 펌웨어 스마트 구성 요소 버전 6.40이 일부 경우에 HP D2200sb 스토리지 블레이드의 SAS 익스팬더를 잘못된 펌웨어로 업데이트하여 스마트 어레이 P410i 컨트롤러가 HP D2200sb 스토리지 블레이드에 설치된 하드 드라이브와 통신할 수 없게 되는 설치 문제가 해결되었습니다. 이 문제에 대한 다른 중요한 내용은 고객 권고 사항 c03964262를 참조하십시오.
버전 6.40에서 해결된 문제:
- 잘못된 POST 1705 메시지가 HP 스마트 어레이 P410i 컨트롤러 펌웨어 버전 5.76 이상을 사용하는 HP BL465c G7 또는 HP BL685c G7 블레이드 시스템에 게시되었습니다. 이 POST는 불량 Super-Cap을 표시했으며, 그 후 쓰기 캐시도 비활성화했습니다.
- 드문 경우지만 컨트롤러가 POST 중에 응답하지 않을 수 있습니다.
- 간헐적으로 JBOD에 있는 SATA 여분 드라이브는 핫 제거되고 이후 재검색되는 것으로 표시되었습니다.
- 고객은 BIOS 시리얼 콘솔을 통해 Esc 키 스트로크 “Esc+6” 또는 "F6", “Esc+8” 또는 "F8"을 눌러 명령줄 인터페이스를 통해 ORCA를 호출할 수 없었습니다.
주: 버전 6.40은 HP 지원 센터에서 더 이상 다운로드할 수 없지만, 다음 수정 사항은 버전 6.40(B)에서도 제공됩니다.
]]>
6.40(B) 版中修正的問題:
- 修正以下安裝問題:在一些情況中,適用於 Smart Array P410i 控制器的 6.40 版 Online Smart Array 韌體智慧元件會用不正確的韌體來更新 HP D2200sb 儲存刀鋒中的 SAS 擴充器,導致 Smart Array P410i 控制器無法與 HP D2200sb 儲存刀鋒中安裝的硬碟通訊。若需關於此問題的其他重要資訊,請參閱客戶諮詢文件 c03964262。
6.40 版中修正的問題:
- 在使用 HP Smart Array P410i 控制器韌體 5.76 版或更高版本的 HP BL465c G7 或 HP BL685c G7 刀鋒型伺服器系統上發佈的假 POST 1705 訊息。POST 指出超級電容損壞,因而導致停用寫入快取。
- 在極少數狀況下,控制器會在 POST 期間無回應。
- 在間歇狀況下,JBOD 中的 SATA 備用磁碟機正被標記為熱移除,然後重新探索。
- 客戶透過命令列介面按 Esc 鍵組合「Esc+6」或「F6」或透過 BIOS 序列主控台按 Esc 鍵組合「Esc+8」或「F8」,無法叫用 ORCA。
附註: 無法使用 6.40 版自 HP 支援中心進行下載,但是在 6.40(B) 版中亦提供以下修正:
]]>
Problems Fixed:
-
On rare occasions during power-up the controller would become unresponsive during POST.
]]>
Problems Fixed:
-
On rare occasions during power-up the controller would become unresponsive during POST.
]]>
Problems Fixed:
-
On rare occasions during power-up the controller would become unresponsive during POST.
]]>
Problems Fixed:
-
On rare occasions during power-up the controller would become unresponsive during POST.
]]>
Problems Fixed:
-
On rare occasions during power-up the controller would become unresponsive during POST.
]]>
Problems Fixed:
-
On rare occasions during power-up the controller would become unresponsive during POST.
]]>
修正された問題点:
-
まれに、電源投入時にコントローラーがPOST中に応答しなくなります。
]]>
Problems Fixed:
-
On rare occasions during power-up the controller would become unresponsive during POST.
]]>
Problems Fixed:
-
On rare occasions during power-up the controller would become unresponsive during POST.
]]>
Problems Fixed:
The following problems are addressed in version 6.00 of Online ROM Flash Component for Linux - Smart Array P212, P410, P410i, P411, P711m, P712m, and P812:
-
On rare occasions during power-up of an HP DS2200sb the expander backplane would be unresponsive. When the expander backplane was unresponsive, the attached Smart Array Controller was not allowed to discover drives that were attached.
-
On an HP P812 controller, executing several sequential Write operations to more than 75 hard drives would result in a controller lockup.
-
Modified the FBWC module code to improve the training of the DDR2 DIMMs in order to prevent the rare occasions when 1783 POST error messages displays followed by an unresponsive controller.
-
Protection has been added to prevent potential Smart Array controller hangs under rare conditions when hot-adding hard drives.
-
When running in a Solaris environment, Smart Array firmware version 6.00 works around an issue where the driver would not handle asynchronous events from the Smart Array controller properly.
-
An interaction issue occurred between the Smart Array Controller and HP SAS Expander card in which the Hard Drives attached to the HP SAS Expander were not being discovered occasionally upon boot up or hot plug.
-
On rare occasions, the Smart Array controller would reset the same SATA drive several times when a PHY is stuck longer than four seconds.
-
The Smart Array P711m and P712m would report false link errors.
-
The Open Connection timeout was reduced to 900 microseconds so that SAS connections terminate gracefully and data transfer stalls are prevented.
-
The Smart Array controller would not connect to hard drives within 20ms under heavy stress.
-
Upon power up, a Post message will now be displayed to the user to indicate that a cache module is needed for the P711m controller.
-
When running heavy I/O in RAID 5, while an HP P410 controller was connected to more than 17 SAS drives in an HP DL180 G6 server with a 25SFF backplane, a lockup issue (error code 0xAB or 0xEA) could occur.
-
During heavy I/O when the HP P711m controller is connected to a HP P2000sa G3 MSA Array System via a HP 6Gb SAS Switch, a lockup issue (error code 0x15) could occur.
-
After a system with (2) or more empty SAS storage boxes, Box 1, 2, 3 …, attached to an HP SAS Expander card is powered up and then a drive is hot plugged into Box 2 or above, ACU and ORCA would incorrectly display the drive in Box 1.
]]>
Problems Fixed:
The following problems are addressed in version 6.00 of Online ROM Flash Component for Linux - Smart Array P212, P410, P410i, P411, P711m, P712m, and P812:
-
On rare occasions during power-up of an HP DS2200sb the expander backplane would be unresponsive. When the expander backplane was unresponsive, the attached Smart Array Controller was not allowed to discover drives that were attached.
-
On an HP P812 controller, executing several sequential Write operations to more than 75 hard drives would result in a controller lockup.
-
Modified the FBWC module code to improve the training of the DDR2 DIMMs in order to prevent the rare occasions when 1783 POST error messages displays followed by an unresponsive controller.
-
Protection has been added to prevent potential Smart Array controller hangs under rare conditions when hot-adding hard drives.
-
When running in a Solaris environment, Smart Array firmware version 6.00 works around an issue where the driver would not handle asynchronous events from the Smart Array controller properly.
-
An interaction issue occurred between the Smart Array Controller and HP SAS Expander card in which the Hard Drives attached to the HP SAS Expander were not being discovered occasionally upon boot up or hot plug.
-
On rare occasions, the Smart Array controller would reset the same SATA drive several times when a PHY is stuck longer than four seconds.
-
The Smart Array P711m and P712m would report false link errors.
-
The Open Connection timeout was reduced to 900 microseconds so that SAS connections terminate gracefully and data transfer stalls are prevented.
-
The Smart Array controller would not connect to hard drives within 20ms under heavy stress.
-
Upon power up, a Post message will now be displayed to the user to indicate that a cache module is needed for the P711m controller.
-
When running heavy I/O in RAID 5, while an HP P410 controller was connected to more than 17 SAS drives in an HP DL180 G6 server with a 25SFF backplane, a lockup issue (error code 0xAB or 0xEA) could occur.
-
During heavy I/O when the HP P711m controller is connected to a HP P2000sa G3 MSA Array System via a HP 6Gb SAS Switch, a lockup issue (error code 0x15) could occur.
-
After a system with (2) or more empty SAS storage boxes, Box 1, 2, 3 …, attached to an HP SAS Expander card is powered up and then a drive is hot plugged into Box 2 or above, ACU and ORCA would incorrectly display the drive in Box 1.
]]>
Problems Fixed:
The following problems are addressed in version 6.00 of Online ROM Flash Component for Linux - Smart Array P212, P410, P410i, P411, P711m, P712m, and P812:
-
On rare occasions during power-up of an HP DS2200sb the expander backplane would be unresponsive. When the expander backplane was unresponsive, the attached Smart Array Controller was not allowed to discover drives that were attached.
-
On an HP P812 controller, executing several sequential Write operations to more than 75 hard drives would result in a controller lockup.
-
Modified the FBWC module code to improve the training of the DDR2 DIMMs in order to prevent the rare occasions when 1783 POST error messages displays followed by an unresponsive controller.
-
Protection has been added to prevent potential Smart Array controller hangs under rare conditions when hot-adding hard drives.
-
When running in a Solaris environment, Smart Array firmware version 6.00 works around an issue where the driver would not handle asynchronous events from the Smart Array controller properly.
-
An interaction issue occurred between the Smart Array Controller and HP SAS Expander card in which the Hard Drives attached to the HP SAS Expander were not being discovered occasionally upon boot up or hot plug.
-
On rare occasions, the Smart Array controller would reset the same SATA drive several times when a PHY is stuck longer than four seconds.
-
The Smart Array P711m and P712m would report false link errors.
-
The Open Connection timeout was reduced to 900 microseconds so that SAS connections terminate gracefully and data transfer stalls are prevented.
-
The Smart Array controller would not connect to hard drives within 20ms under heavy stress.
-
Upon power up, a Post message will now be displayed to the user to indicate that a cache module is needed for the P711m controller.
-
When running heavy I/O in RAID 5, while an HP P410 controller was connected to more than 17 SAS drives in an HP DL180 G6 server with a 25SFF backplane, a lockup issue (error code 0xAB or 0xEA) could occur.
-
During heavy I/O when the HP P711m controller is connected to a HP P2000sa G3 MSA Array System via a HP 6Gb SAS Switch, a lockup issue (error code 0x15) could occur.
-
After a system with (2) or more empty SAS storage boxes, Box 1, 2, 3 …, attached to an HP SAS Expander card is powered up and then a drive is hot plugged into Box 2 or above, ACU and ORCA would incorrectly display the drive in Box 1.
]]>
Problems Fixed:
The following problems are addressed in version 6.00 of Online ROM Flash Component for Linux - Smart Array P212, P410, P410i, P411, P711m, P712m, and P812:
-
On rare occasions during power-up of an HP DS2200sb the expander backplane would be unresponsive. When the expander backplane was unresponsive, the attached Smart Array Controller was not allowed to discover drives that were attached.
-
On an HP P812 controller, executing several sequential Write operations to more than 75 hard drives would result in a controller lockup.
-
Modified the FBWC module code to improve the training of the DDR2 DIMMs in order to prevent the rare occasions when 1783 POST error messages displays followed by an unresponsive controller.
-
Protection has been added to prevent potential Smart Array controller hangs under rare conditions when hot-adding hard drives.
-
When running in a Solaris environment, Smart Array firmware version 6.00 works around an issue where the driver would not handle asynchronous events from the Smart Array controller properly.
-
An interaction issue occurred between the Smart Array Controller and HP SAS Expander card in which the Hard Drives attached to the HP SAS Expander were not being discovered occasionally upon boot up or hot plug.
-
On rare occasions, the Smart Array controller would reset the same SATA drive several times when a PHY is stuck longer than four seconds.
-
The Smart Array P711m and P712m would report false link errors.
-
The Open Connection timeout was reduced to 900 microseconds so that SAS connections terminate gracefully and data transfer stalls are prevented.
-
The Smart Array controller would not connect to hard drives within 20ms under heavy stress.
-
Upon power up, a Post message will now be displayed to the user to indicate that a cache module is needed for the P711m controller.
-
When running heavy I/O in RAID 5, while an HP P410 controller was connected to more than 17 SAS drives in an HP DL180 G6 server with a 25SFF backplane, a lockup issue (error code 0xAB or 0xEA) could occur.
-
During heavy I/O when the HP P711m controller is connected to a HP P2000sa G3 MSA Array System via a HP 6Gb SAS Switch, a lockup issue (error code 0x15) could occur.
-
After a system with (2) or more empty SAS storage boxes, Box 1, 2, 3 …, attached to an HP SAS Expander card is powered up and then a drive is hot plugged into Box 2 or above, ACU and ORCA would incorrectly display the drive in Box 1.
]]>
Problems Fixed:
The following problems are addressed in version 6.00 of Online ROM Flash Component for Linux - Smart Array P212, P410, P410i, P411, P711m, P712m, and P812:
-
On rare occasions during power-up of an HP DS2200sb the expander backplane would be unresponsive. When the expander backplane was unresponsive, the attached Smart Array Controller was not allowed to discover drives that were attached.
-
On an HP P812 controller, executing several sequential Write operations to more than 75 hard drives would result in a controller lockup.
-
Modified the FBWC module code to improve the training of the DDR2 DIMMs in order to prevent the rare occasions when 1783 POST error messages displays followed by an unresponsive controller.
-
Protection has been added to prevent potential Smart Array controller hangs under rare conditions when hot-adding hard drives.
-
When running in a Solaris environment, Smart Array firmware version 6.00 works around an issue where the driver would not handle asynchronous events from the Smart Array controller properly.
-
An interaction issue occurred between the Smart Array Controller and HP SAS Expander card in which the Hard Drives attached to the HP SAS Expander were not being discovered occasionally upon boot up or hot plug.
-
On rare occasions, the Smart Array controller would reset the same SATA drive several times when a PHY is stuck longer than four seconds.
-
The Smart Array P711m and P712m would report false link errors.
-
The Open Connection timeout was reduced to 900 microseconds so that SAS connections terminate gracefully and data transfer stalls are prevented.
-
The Smart Array controller would not connect to hard drives within 20ms under heavy stress.
-
Upon power up, a Post message will now be displayed to the user to indicate that a cache module is needed for the P711m controller.
-
When running heavy I/O in RAID 5, while an HP P410 controller was connected to more than 17 SAS drives in an HP DL180 G6 server with a 25SFF backplane, a lockup issue (error code 0xAB or 0xEA) could occur.
-
During heavy I/O when the HP P711m controller is connected to a HP P2000sa G3 MSA Array System via a HP 6Gb SAS Switch, a lockup issue (error code 0x15) could occur.
-
After a system with (2) or more empty SAS storage boxes, Box 1, 2, 3 …, attached to an HP SAS Expander card is powered up and then a drive is hot plugged into Box 2 or above, ACU and ORCA would incorrectly display the drive in Box 1.
]]>
Problems Fixed:
The following problems are addressed in version 6.00 of Online ROM Flash Component for Linux - Smart Array P212, P410, P410i, P411, P711m, P712m, and P812:
-
On rare occasions during power-up of an HP DS2200sb the expander backplane would be unresponsive. When the expander backplane was unresponsive, the attached Smart Array Controller was not allowed to discover drives that were attached.
-
On an HP P812 controller, executing several sequential Write operations to more than 75 hard drives would result in a controller lockup.
-
Modified the FBWC module code to improve the training of the DDR2 DIMMs in order to prevent the rare occasions when 1783 POST error messages displays followed by an unresponsive controller.
-
Protection has been added to prevent potential Smart Array controller hangs under rare conditions when hot-adding hard drives.
-
When running in a Solaris environment, Smart Array firmware version 6.00 works around an issue where the driver would not handle asynchronous events from the Smart Array controller properly.
-
An interaction issue occurred between the Smart Array Controller and HP SAS Expander card in which the Hard Drives attached to the HP SAS Expander were not being discovered occasionally upon boot up or hot plug.
-
On rare occasions, the Smart Array controller would reset the same SATA drive several times when a PHY is stuck longer than four seconds.
-
The Smart Array P711m and P712m would report false link errors.
-
The Open Connection timeout was reduced to 900 microseconds so that SAS connections terminate gracefully and data transfer stalls are prevented.
-
The Smart Array controller would not connect to hard drives within 20ms under heavy stress.
-
Upon power up, a Post message will now be displayed to the user to indicate that a cache module is needed for the P711m controller.
-
When running heavy I/O in RAID 5, while an HP P410 controller was connected to more than 17 SAS drives in an HP DL180 G6 server with a 25SFF backplane, a lockup issue (error code 0xAB or 0xEA) could occur.
-
During heavy I/O when the HP P711m controller is connected to a HP P2000sa G3 MSA Array System via a HP 6Gb SAS Switch, a lockup issue (error code 0x15) could occur.
-
After a system with (2) or more empty SAS storage boxes, Box 1, 2, 3 …, attached to an HP SAS Expander card is powered up and then a drive is hot plugged into Box 2 or above, ACU and ORCA would incorrectly display the drive in Box 1.
]]>
修正された問題点:
バージョン6.00のオンラインROMフラッシュコンポーネント for Linux - SmartアレイP212、P410、P410i、P411、P711m、P712m、およびP812で、以下の問題に対応しました。
-
まれにHP DS2200sbの起動時に、エキスパンダーバックプレーンが応答しなくなります。 エキスパンダーバックプレーンが応答しない時、接続されたSmartアレイコントローラーは接続されたドライブを検出することができませんでした。
-
HP P812コントローラーで、75台以上のハードディスクドライブに複数のシーケンシャルライト操作を実行すると、コントローラーのロックアップを引き起こす可能性があります。
-
まれに1783 POSTエラーメッセージが表示された後にコントローラーが応答しないことを防止するために、DDR2 DIMMのトレーニングを改善するFBWCモジュールのコードを変更しました。
-
ハードディスクドライブをホット追加した場合、まれな条件下で潜在的なSmartアレイコントローラーのハングアップを防ぐために保護を追加しました。
-
Solaris環境で実行する場合、Smartアレイファームウェアバージョン6.00は、ドライバーが正しくSmartアレイコントローラーからの非同期イベントを処理しない問題を回避します。
-
SmartアレイコントローラーおよびHP SASエキスパンダーカードの間で、HP SASエキスパンダーに接続されたハードディスクドライブが、ブートアップまたはホットプラグ時に時々検出されない問題が発生します。
-
ごくまれに、PHYが4秒以上スタックした場合、Smartアレイコントローラーが同一のSATAドライブを複数回リセットすることがあります。
-
SmartアレイP711mおよびP712mは、誤ったリンクエラーを報告することがあります。
-
Open Connectionのタイムアウトが900マイクロ秒に削減されたので、SAS接続は安全に終了し、データ転送の停止は回避されます。
-
Smartアレイコントローラーは、負荷が重い場合、20ms以内にハードディスクドライブに接続しないことがあります。
-
起動時に、P711mコントローラーにキャッシュモジュールが必要なことを知らせるために、POSTメッセージが表示されます。
-
RAID 5でI/O負荷が重い場合、25SFFバックプレーンのHP DL180 G6サーバーでHP P410コントローラーが17台以上のSASドライブに接続している間、ロックアップの問題(エラーコード0xABまたは0xEA)が発生する可能性があります。
-
I/Oの負荷が重い状態で、HP P711mコントローラーがHP 6Gb SASスイッチ経由でHP P2000 G3 MSA SASに接続されている場合、ロックアップの問題(エラーコード0x15)が発生する可能性があります。
-
2つ以上の空いているSASストレージボックス(ボックス1、2、3...)が、HP SASエキスパンダーカードに接続されているシステムの電源が入った後、ボックス2以上にドライブをホットプラグすると、ACUおよびORCAは誤ってドライブがボックス1にあると表示します。
]]>
Problems Fixed:
The following problems are addressed in version 6.00 of Online ROM Flash Component for Linux - Smart Array P212, P410, P410i, P411, P711m, P712m, and P812:
-
On rare occasions during power-up of an HP DS2200sb the expander backplane would be unresponsive. When the expander backplane was unresponsive, the attached Smart Array Controller was not allowed to discover drives that were attached.
-
On an HP P812 controller, executing several sequential Write operations to more than 75 hard drives would result in a controller lockup.
-
Modified the FBWC module code to improve the training of the DDR2 DIMMs in order to prevent the rare occasions when 1783 POST error messages displays followed by an unresponsive controller.
-
Protection has been added to prevent potential Smart Array controller hangs under rare conditions when hot-adding hard drives.
-
When running in a Solaris environment, Smart Array firmware version 6.00 works around an issue where the driver would not handle asynchronous events from the Smart Array controller properly.
-
An interaction issue occurred between the Smart Array Controller and HP SAS Expander card in which the Hard Drives attached to the HP SAS Expander were not being discovered occasionally upon boot up or hot plug.
-
On rare occasions, the Smart Array controller would reset the same SATA drive several times when a PHY is stuck longer than four seconds.
-
The Smart Array P711m and P712m would report false link errors.
-
The Open Connection timeout was reduced to 900 microseconds so that SAS connections terminate gracefully and data transfer stalls are prevented.
-
The Smart Array controller would not connect to hard drives within 20ms under heavy stress.
-
Upon power up, a Post message will now be displayed to the user to indicate that a cache module is needed for the P711m controller.
-
When running heavy I/O in RAID 5, while an HP P410 controller was connected to more than 17 SAS drives in an HP DL180 G6 server with a 25SFF backplane, a lockup issue (error code 0xAB or 0xEA) could occur.
-
During heavy I/O when the HP P711m controller is connected to a HP P2000sa G3 MSA Array System via a HP 6Gb SAS Switch, a lockup issue (error code 0x15) could occur.
-
After a system with (2) or more empty SAS storage boxes, Box 1, 2, 3 …, attached to an HP SAS Expander card is powered up and then a drive is hot plugged into Box 2 or above, ACU and ORCA would incorrectly display the drive in Box 1.
]]>
Problems Fixed:
The following problems are addressed in version 6.00 of Online ROM Flash Component for Linux - Smart Array P212, P410, P410i, P411, P711m, P712m, and P812:
-
On rare occasions during power-up of an HP DS2200sb the expander backplane would be unresponsive. When the expander backplane was unresponsive, the attached Smart Array Controller was not allowed to discover drives that were attached.
-
On an HP P812 controller, executing several sequential Write operations to more than 75 hard drives would result in a controller lockup.
-
Modified the FBWC module code to improve the training of the DDR2 DIMMs in order to prevent the rare occasions when 1783 POST error messages displays followed by an unresponsive controller.
-
Protection has been added to prevent potential Smart Array controller hangs under rare conditions when hot-adding hard drives.
-
When running in a Solaris environment, Smart Array firmware version 6.00 works around an issue where the driver would not handle asynchronous events from the Smart Array controller properly.
-
An interaction issue occurred between the Smart Array Controller and HP SAS Expander card in which the Hard Drives attached to the HP SAS Expander were not being discovered occasionally upon boot up or hot plug.
-
On rare occasions, the Smart Array controller would reset the same SATA drive several times when a PHY is stuck longer than four seconds.
-
The Smart Array P711m and P712m would report false link errors.
-
The Open Connection timeout was reduced to 900 microseconds so that SAS connections terminate gracefully and data transfer stalls are prevented.
-
The Smart Array controller would not connect to hard drives within 20ms under heavy stress.
-
Upon power up, a Post message will now be displayed to the user to indicate that a cache module is needed for the P711m controller.
-
When running heavy I/O in RAID 5, while an HP P410 controller was connected to more than 17 SAS drives in an HP DL180 G6 server with a 25SFF backplane, a lockup issue (error code 0xAB or 0xEA) could occur.
-
During heavy I/O when the HP P711m controller is connected to a HP P2000sa G3 MSA Array System via a HP 6Gb SAS Switch, a lockup issue (error code 0x15) could occur.
-
After a system with (2) or more empty SAS storage boxes, Box 1, 2, 3 …, attached to an HP SAS Expander card is powered up and then a drive is hot plugged into Box 2 or above, ACU and ORCA would incorrectly display the drive in Box 1.
]]>
已解决的问题:
- SATA驱动器配置为备用的60天或更多时间,存储控制器可能会锁定,报告为0xAB错误。
]]>
Problems Fixed:
-
When SATA drives are configured as spares for a period of 60 days or more, the storage controller would lockup, reporting as 0xAB error.
]]>
Problems Fixed:
-
When SATA drives are configured as spares for a period of 60 days or more, the storage controller would lockup, reporting as 0xAB error.
]]>
Problems Fixed:
-
When SATA drives are configured as spares for a period of 60 days or more, the storage controller would lockup, reporting as 0xAB error.
]]>
Problems Fixed:
-
When SATA drives are configured as spares for a period of 60 days or more, the storage controller would lockup, reporting as 0xAB error.
]]>
Problems Fixed:
-
When SATA drives are configured as spares for a period of 60 days or more, the storage controller would lockup, reporting as 0xAB error.
]]>
修正された問題点:
-
SATAドライブが60日以上の期間、スペアとして構成されている場合、ストレージコントローラーがロックアップし、0xABエラーとして報告されます。
]]>
해결된 문제:
- SATA 드라이브가 60일 이상 동안 예비 부품으로 구성되면 스토리지 컨트롤러가 잠기고 0xAB 오류가 보고됩니다.
]]>
修正的問題:
- 當 SATA 磁碟機設定為備援且期限為 60 天或以上時,儲存控制器會鎖定,報告為 0xAB 錯誤。
]]>
已修复的问题:
- 修复了 HP P812 控制器中在重新启动时会出现极其少见的锁定(代码 0xD4)的问题。
- 修复了在置了 HP SAS 扩展卡的 HP DL580 G5 中错误地报告磁盘位置信息的问题
- 修复了在某些配置中进行卷转换后,RAID 6 卷在最后一个条带中的奇偶数据不一致的问题。
- 修复了移除 HP P2000saG3 控制器模块可能会导致控制器锁定(代码 0xAB)的问题。
- 修复了向 HP DL180G6 12 驱动器背板中热添加一个 3TB 的驱动器会导致控制器锁定(代码 0x15)的问题。
- 修复了由于错误地将主机数据放入具有内存错误的写高速缓存中从而会导致控制器锁定(代码 0xBC)的问题。
- 修复了将控制器配置为 100% 读高速缓存可能会导致 ACU 的“高速缓存状态详情 (Cache Status Details)” 栏中显示“检测到高速缓存错误。请运行诊断报告获取更多信息 (A cache error was detected.Run a diagnostic report for more information)”错误的问题。
- 修复了向 MSA-60、MSA-70 或 HP DL180-G6 12 驱动器背板中热添加 SATA 磁盘后,存储控制器可能会停止响应的问题。请参阅客户顾问文档 c03011608。
- 修复了在 I/O 繁重的情况下处理热移除事件时,控制器可能会停止响应的问题。
- 修复了在卷转换过程中可能会发生的问题。在阵列中将原始卷配置为偏移位置时,如果发生逻辑性的不可恢复读取错误,可能会使得坏块迁移至所转换卷的错误位置。
- 修复了在支持原生命令队列的 SATA 磁盘上处理大量不可恢复的读取错误时可能会导致锁定(代码 0x15)的问题。
- 修复了磁盘容量大于 2TB 时可能会错误地标记为失败的问题。
- 修复了在 SSD RAID 10 阵列处于繁重的 I/O 负载下会导致锁定(代码 0x13)的问题。
- 修复了控制器上未安装高速缓存模块时,在启动过程中 SATA 磁盘可能会偶尔被标记为失败或丢失的问题。
- 修复了控制器在无高速缓存模块且连接至 SATA 磁盘的情况下运行时可能会在运行 HP Insight Diagnostics 软件或离线硬盘固件刷新实用程序时出现锁定(代码 0x15)的问题。
- 修复了在控制器和机柜 IO 模块之间连接电缆可能会导致 Open VMS / Solaris 系统中发生锁定(代码 0x13)的问题。
- 修复了导致控制器在启动时停止响应的几个问题。请参考客户顾问文档 C03161926。
- 修复了控制器固件在启动时正常运行 F1 和 F2 键的问题。请参考客户顾问文档 c03127437。
- 修复了无法将 3TB 驱动器作为备件管理的问题。
- 修复了服务器序列号、产品 ID 和其它配置被清除或者设置错误的问题。请参阅客户顾问文档 c03083515
]]>
Problems Fixed:
-
Fixed an issue with the HP P812 controller in which a rare lockup (code 0xD4) could occur upon reboot.
-
Fixed an issue where disk location information was reported incorrectly in the HP DL580 G5 with the HP SAS Expander card
-
Fixed an issue where a RAID 6 volume could have inconsistent parity data in the last stripe in certain configurations after a volume transformation operation had occurred.
-
Fixed an issue where removal of a HP P2000saG3 controller module could cause a controller lockup (code 0xAB).
-
Fixed an issue where the hot-add of a 3TB drive to HP DL180G6 12 drive backplane could cause the controller to lock up (code 0x15).
-
Fixed an issue where the controller would lock up (code 0xBC) due to incorrectly placing host data into a write-cache line that had a memory error.
-
Fixed an issue where a controller configured for 100% read cache could cause a false "A cache error was detected. Run a diagnostic report for more information" error to be displayed in the 'Cache Status Details' column in ACU.
-
Fixed an issue where after hot-adding a SATA disk to an MSA-60, MSA-70, or HP DL180-G6 12-drive backplane, the storage controller could become unresponsive. Reference Customer Advisory c03011608.
-
Fixed an issue where the controller could become unresponsive while handling a hot-removal event when experiencing heavy I/O.
-
Fixed an issue that could be experienced during a volume transformation operation. If a logical Unrecovered Read Error occurred, it could cause the bad block(s) to be moved to the incorrect location in the transformed volume if the original volume was configured at an offset in the array.
-
Fixed an issue where simultaneous handling of many Unrecoverable Read Errors on SATA disks supporting Native Command Queuing could result in a lockup (code 0x15).
-
Fixed an issue where a disk of size >2TB could be incorrectly marked as failed.
-
Fixed an issue that caused a lockup (code 0x13) with a SSD RAID 10 array under heavy I/O load.
-
Fixed an issue where SATA disks could occasionally be marked as failed or missing during boot when no cache module is installed on the controller.
-
Fixed an issue where a controller running with no cache module, attached to SATA disks, could encounter a lockup (code 0x15) when running HP Insight Diagnostics software or offline HDD firmware flash utility.
-
Fixed an issue with cable pull between the controller and an enclosure IO module that would cause a lockup (code 0x13) in Open VMS / Solaris systems.
-
Fixed several issues that caused the controller to become unresponsive at boot up time. Reference CA C03161926.
-
Fixed the controller firmware to properly process F1 and F2 keys at startup. Reference CA c03127437.
-
Fixed an issue in which 3TB drives were not managed as spares.
-
Fixed an issue in which the Server Serial Number, Product ID, and Other Configurations were cleared or set to default. Reference Customer Advisory c03083515
]]>
Problems Fixed:
-
Fixed an issue with the HP P812 controller in which a rare lockup (code 0xD4) could occur upon reboot.
-
Fixed an issue where disk location information was reported incorrectly in the HP DL580 G5 with the HP SAS Expander card
-
Fixed an issue where a RAID 6 volume could have inconsistent parity data in the last stripe in certain configurations after a volume transformation operation had occurred.
-
Fixed an issue where removal of a HP P2000saG3 controller module could cause a controller lockup (code 0xAB).
-
Fixed an issue where the hot-add of a 3TB drive to HP DL180G6 12 drive backplane could cause the controller to lock up (code 0x15).
-
Fixed an issue where the controller would lock up (code 0xBC) due to incorrectly placing host data into a write-cache line that had a memory error.
-
Fixed an issue where a controller configured for 100% read cache could cause a false "A cache error was detected. Run a diagnostic report for more information" error to be displayed in the 'Cache Status Details' column in ACU.
-
Fixed an issue where after hot-adding a SATA disk to an MSA-60, MSA-70, or HP DL180-G6 12-drive backplane, the storage controller could become unresponsive. Reference Customer Advisory c03011608.
-
Fixed an issue where the controller could become unresponsive while handling a hot-removal event when experiencing heavy I/O.
-
Fixed an issue that could be experienced during a volume transformation operation. If a logical Unrecovered Read Error occurred, it could cause the bad block(s) to be moved to the incorrect location in the transformed volume if the original volume was configured at an offset in the array.
-
Fixed an issue where simultaneous handling of many Unrecoverable Read Errors on SATA disks supporting Native Command Queuing could result in a lockup (code 0x15).
-
Fixed an issue where a disk of size >2TB could be incorrectly marked as failed.
-
Fixed an issue that caused a lockup (code 0x13) with a SSD RAID 10 array under heavy I/O load.
-
Fixed an issue where SATA disks could occasionally be marked as failed or missing during boot when no cache module is installed on the controller.
-
Fixed an issue where a controller running with no cache module, attached to SATA disks, could encounter a lockup (code 0x15) when running HP Insight Diagnostics software or offline HDD firmware flash utility.
-
Fixed an issue with cable pull between the controller and an enclosure IO module that would cause a lockup (code 0x13) in Open VMS / Solaris systems.
-
Fixed several issues that caused the controller to become unresponsive at boot up time. Reference CA C03161926.
-
Fixed the controller firmware to properly process F1 and F2 keys at startup. Reference CA c03127437.
-
Fixed an issue in which 3TB drives were not managed as spares.
-
Fixed an issue in which the Server Serial Number, Product ID, and Other Configurations were cleared or set to default. Reference Customer Advisory c03083515
]]>
Problems Fixed:
-
Fixed an issue with the HP P812 controller in which a rare lockup (code 0xD4) could occur upon reboot.
-
Fixed an issue where disk location information was reported incorrectly in the HP DL580 G5 with the HP SAS Expander card
-
Fixed an issue where a RAID 6 volume could have inconsistent parity data in the last stripe in certain configurations after a volume transformation operation had occurred.
-
Fixed an issue where removal of a HP P2000saG3 controller module could cause a controller lockup (code 0xAB).
-
Fixed an issue where the hot-add of a 3TB drive to HP DL180G6 12 drive backplane could cause the controller to lock up (code 0x15).
-
Fixed an issue where the controller would lock up (code 0xBC) due to incorrectly placing host data into a write-cache line that had a memory error.
-
Fixed an issue where a controller configured for 100% read cache could cause a false "A cache error was detected. Run a diagnostic report for more information" error to be displayed in the 'Cache Status Details' column in ACU.
-
Fixed an issue where after hot-adding a SATA disk to an MSA-60, MSA-70, or HP DL180-G6 12-drive backplane, the storage controller could become unresponsive. Reference Customer Advisory c03011608.
-
Fixed an issue where the controller could become unresponsive while handling a hot-removal event when experiencing heavy I/O.
-
Fixed an issue that could be experienced during a volume transformation operation. If a logical Unrecovered Read Error occurred, it could cause the bad block(s) to be moved to the incorrect location in the transformed volume if the original volume was configured at an offset in the array.
-
Fixed an issue where simultaneous handling of many Unrecoverable Read Errors on SATA disks supporting Native Command Queuing could result in a lockup (code 0x15).
-
Fixed an issue where a disk of size >2TB could be incorrectly marked as failed.
-
Fixed an issue that caused a lockup (code 0x13) with a SSD RAID 10 array under heavy I/O load.
-
Fixed an issue where SATA disks could occasionally be marked as failed or missing during boot when no cache module is installed on the controller.
-
Fixed an issue where a controller running with no cache module, attached to SATA disks, could encounter a lockup (code 0x15) when running HP Insight Diagnostics software or offline HDD firmware flash utility.
-
Fixed an issue with cable pull between the controller and an enclosure IO module that would cause a lockup (code 0x13) in Open VMS / Solaris systems.
-
Fixed several issues that caused the controller to become unresponsive at boot up time. Reference CA C03161926.
-
Fixed the controller firmware to properly process F1 and F2 keys at startup. Reference CA c03127437.
-
Fixed an issue in which 3TB drives were not managed as spares.
-
Fixed an issue in which the Server Serial Number, Product ID, and Other Configurations were cleared or set to default. Reference Customer Advisory c03083515
]]>
Problems Fixed:
-
Fixed an issue with the HP P812 controller in which a rare lockup (code 0xD4) could occur upon reboot.
-
Fixed an issue where disk location information was reported incorrectly in the HP DL580 G5 with the HP SAS Expander card
-
Fixed an issue where a RAID 6 volume could have inconsistent parity data in the last stripe in certain configurations after a volume transformation operation had occurred.
-
Fixed an issue where removal of a HP P2000saG3 controller module could cause a controller lockup (code 0xAB).
-
Fixed an issue where the hot-add of a 3TB drive to HP DL180G6 12 drive backplane could cause the controller to lock up (code 0x15).
-
Fixed an issue where the controller would lock up (code 0xBC) due to incorrectly placing host data into a write-cache line that had a memory error.
-
Fixed an issue where a controller configured for 100% read cache could cause a false "A cache error was detected. Run a diagnostic report for more information" error to be displayed in the 'Cache Status Details' column in ACU.
-
Fixed an issue where after hot-adding a SATA disk to an MSA-60, MSA-70, or HP DL180-G6 12-drive backplane, the storage controller could become unresponsive. Reference Customer Advisory c03011608.
-
Fixed an issue where the controller could become unresponsive while handling a hot-removal event when experiencing heavy I/O.
-
Fixed an issue that could be experienced during a volume transformation operation. If a logical Unrecovered Read Error occurred, it could cause the bad block(s) to be moved to the incorrect location in the transformed volume if the original volume was configured at an offset in the array.
-
Fixed an issue where simultaneous handling of many Unrecoverable Read Errors on SATA disks supporting Native Command Queuing could result in a lockup (code 0x15).
-
Fixed an issue where a disk of size >2TB could be incorrectly marked as failed.
-
Fixed an issue that caused a lockup (code 0x13) with a SSD RAID 10 array under heavy I/O load.
-
Fixed an issue where SATA disks could occasionally be marked as failed or missing during boot when no cache module is installed on the controller.
-
Fixed an issue where a controller running with no cache module, attached to SATA disks, could encounter a lockup (code 0x15) when running HP Insight Diagnostics software or offline HDD firmware flash utility.
-
Fixed an issue with cable pull between the controller and an enclosure IO module that would cause a lockup (code 0x13) in Open VMS / Solaris systems.
-
Fixed several issues that caused the controller to become unresponsive at boot up time. Reference CA C03161926.
-
Fixed the controller firmware to properly process F1 and F2 keys at startup. Reference CA c03127437.
-
Fixed an issue in which 3TB drives were not managed as spares.
-
Fixed an issue in which the Server Serial Number, Product ID, and Other Configurations were cleared or set to default. Reference Customer Advisory c03083515
]]>
Problems Fixed:
-
Fixed an issue with the HP P812 controller in which a rare lockup (code 0xD4) could occur upon reboot.
-
Fixed an issue where disk location information was reported incorrectly in the HP DL580 G5 with the HP SAS Expander card
-
Fixed an issue where a RAID 6 volume could have inconsistent parity data in the last stripe in certain configurations after a volume transformation operation had occurred.
-
Fixed an issue where removal of a HP P2000saG3 controller module could cause a controller lockup (code 0xAB).
-
Fixed an issue where the hot-add of a 3TB drive to HP DL180G6 12 drive backplane could cause the controller to lock up (code 0x15).
-
Fixed an issue where the controller would lock up (code 0xBC) due to incorrectly placing host data into a write-cache line that had a memory error.
-
Fixed an issue where a controller configured for 100% read cache could cause a false "A cache error was detected. Run a diagnostic report for more information" error to be displayed in the 'Cache Status Details' column in ACU.
-
Fixed an issue where after hot-adding a SATA disk to an MSA-60, MSA-70, or HP DL180-G6 12-drive backplane, the storage controller could become unresponsive. Reference Customer Advisory c03011608.
-
Fixed an issue where the controller could become unresponsive while handling a hot-removal event when experiencing heavy I/O.
-
Fixed an issue that could be experienced during a volume transformation operation. If a logical Unrecovered Read Error occurred, it could cause the bad block(s) to be moved to the incorrect location in the transformed volume if the original volume was configured at an offset in the array.
-
Fixed an issue where simultaneous handling of many Unrecoverable Read Errors on SATA disks supporting Native Command Queuing could result in a lockup (code 0x15).
-
Fixed an issue where a disk of size >2TB could be incorrectly marked as failed.
-
Fixed an issue that caused a lockup (code 0x13) with a SSD RAID 10 array under heavy I/O load.
-
Fixed an issue where SATA disks could occasionally be marked as failed or missing during boot when no cache module is installed on the controller.
-
Fixed an issue where a controller running with no cache module, attached to SATA disks, could encounter a lockup (code 0x15) when running HP Insight Diagnostics software or offline HDD firmware flash utility.
-
Fixed an issue with cable pull between the controller and an enclosure IO module that would cause a lockup (code 0x13) in Open VMS / Solaris systems.
-
Fixed several issues that caused the controller to become unresponsive at boot up time. Reference CA C03161926.
-
Fixed the controller firmware to properly process F1 and F2 keys at startup. Reference CA c03127437.
-
Fixed an issue in which 3TB drives were not managed as spares.
-
Fixed an issue in which the Server Serial Number, Product ID, and Other Configurations were cleared or set to default. Reference Customer Advisory c03083515
]]>
修正された問題点:
-
再起動時にまれにロックアップ(コード0xD4)が発生するHP P812コントローラーの問題を修正しました。
-
HP SAS拡張カードを搭載するHP DL580 G5で、ディスク位置情報が誤って報告される問題を修正しました。
-
RAID 6ボリュームでボリューム変換処理が発生した後、特定の構成の最後のストライプのパリティデータが一致しない問題を修正しました。
-
HP P2000saG3コントローラーモジュールを取り外すとコントローラーがロックアップ(コード0xAB)する問題を修正しました。
-
3TBのドライブをHP DL180G6 12ドライブバックプレーンにホットアドするとコントローラーがロックアップ(コード0x15)する問題を修正しました。
-
メモリエラーを持つ書き込みキャッシュラインにホストデータを誤って書き込んだため、コントローラーがロックアップ(コード0xBC)する問題を修正しました。
-
リードキャッシュを100%に設定されたコントローラーが、ACUの[Cache Status Details]に「A cache error was detected. Run a diagnostic report for more information」エラーが表示される問題を修正しました。
-
SATAディスクをMSA-60、MSA-70、またはHP DL180-G6 12ドライブバックプレーンにホットアドするとストレージコントローラーが応答しなくなる問題を修正しました。 カスタマーアドバイザリ c03011608を参照してください。
-
大量のI/Oが発生しているときにホットリムーブイベントを処理していると、コントローラーが応答しなくなる問題を修正しました。
-
ボリューム変換処理中に発生する問題を修正しました。 論理的な回復不能読み込みエラーが発生した場合、元のボリュームがアレイ内のオフセットで構成されていると、不良ブロックが変換されたボリューム内の誤った場所に移動する可能性があります。
-
Native Command QueuingをサポートするSATAディスク上で同時に多くの回復不能な読み取りエラーを処理するとロックアップ(コード0x15の)が発生する問題を修正しました。
-
2TBを超えるサイズのディスクが誤って障害と記録される問題を修正しました。
-
大量のI/O負荷によりSSD RAID 10アレイでロックアップ(コード0x13)が発生する問題を修正しました。
-
コントローラーにキャッシュモジュールが装着されていないと、起動中にSATAディスクが時々障害または消失と記録される問題を修正しました。
-
HP Insight DiagnosticsソフトウェアまたはオフラインHDDファームウェアフラッシュユーティリティを実行する際に、コントローラーがキャッシュモジュールなしでSATAディスクを接続して実行されていると、ロックアップ(コード0x15の)する問題を修正しました。
-
Open VMS/Solarisシステムのロックアップ(コード0x13を)引き起こすコントローラーおよびエンクロージャーのIOモジュール間のケーブルの問題を修正しました。
-
起動時にコントローラーが応答しなくなるいくつかの問題を修正しました。 カスタマーアドバイザリ C03161926を参照してください。
-
起動時に[F1]および[F2]キーを正しく処理するようコントローラーファームウェアを修正しました。 カスタマーアドバイザリ c03127437を参照してください。
-
3TBのドライブがスペアとして管理できない問題を修正しました。
-
サーバーのシリアル番号、製品ID、およびその他の構成がクリアまたはデフォルトに設定される問題を修正しました。 カスタマーアドバイザリ c03083515を参照してください。
]]>
해결된 문제:
- 재부팅 시 HP P812 컨트롤러에 발생하는 록업 (code 0xD4) 문제를 해결하였습니다.
- HP SAS 익스팬더 카드가 장착되어 있는 HP DL580 G5에서 디스크 위치 정보가 잘못 보고되는 문제를 해결하였습니다
- 일부 구성에서 볼륨이 변화되면 마지막 스트라이프의 RAID 6 볼륨이 패리티 데이터와 일치하지 않는 문제를 해결하였습니다.
- HP P2000saG3 컨트롤러를 제거하면 컨트롤러 록업 (code 0xAB)이 발생하는 문제를 해결하였습니다.
- HP DL180G6 12 드라이브 백플레인에 3TB 드라이브를 강제 추가하면 컨트롤러가 록업(code 0x15)되는 문제를 해결하였습니다.
- 호스트 데이터를 메모리 오류가 발생한 읽기-캐시 라인에 잘못 저장함으로 인해 컨트롤러가 록업되는 문제 (code 0xBC)를 해결하였습니다.
- 컨트롤러가 100% 읽기 캐시로 구성되면 ACU의 "캐시 상태 세부정보" 컬럼에 "A cache error was detected. Run a diagnostic report for more information" 오류 메시지가 표시되는 문제를 해결하였습니다.
- MSA-60, MSA-70 또는 HP DL180-G6 12 드라이브 백플레인에 SATA 디스크를 강제 추가하면 스토리지 컨트롤러가 응답하지 않는 문제를 해결하였습니다. 고객 권고사항 c03011608을 참고하십시오.
- I/O에 과부하가 걸린 경우 강제 제거(hot-removal) 이벤트를 처리하는 과정에 컨트롤러가 응답하지 않는 문제를 해결하였습니다.
- 볼륨이 변화되는 과정에 발생할 수 있는 문제를 해결하였습니다. 논리적인, 발견되지 않은 읽기 오류가 발생하면 기본 볼륨이 어레이의 오프셋에서 구성된 경우 해당되지 않는 블록이 변화된 볼륨의 잘못된 위치로 이동할 수 있습니다.
- Native Command Queuing을 지원하는 SATA 디스크에서 동시에 많은 양의 "발견되지 않은 읽기 오류"를 처리하면 록업(code 0x15)이 발생할 수 있는 문제를 해결하였습니다.
- 디스크 크기가 2TB 이상이면 "고장됨"으로 잘못 표기되는 문제를 해결하였습니다.
- I/O에 과부하가 걸리면 SSD RAID 10 어레이에 록업(code 0x13)이 발생하는 문제를 해결하였습니다.
- 컨트롤러에 캐시 모듈이 설치되어 있지 않으면 부팅 과정에 가끔씩 SATA 디스크가 "고장남" 또는 "사라짐"으로 표기되는 문제를 해결하였습니다.
- 캐기 모듈이 설치되어 있지 않고 SATA 디스크에 장착된 컨트롤러에서 HP Insight Diagnostics 소프트웨어 또는 오프라인 HDD 펌웨어 업데이트 유틸리티를 실행하면 록업(code 0x15)이 발생하는 문제를 해결하였습니다.
- 컨트롤러와 인클로저 IO 모듈 사이의 연결선이 끊김으로 인해 Open VMS / Solaris 시스템에 록업(code 0x13)이 발생하는 문제를 해결하였습니다.
- 부팅과정에 컨트롤러가 응답하지 않는 여러가지 문제를 해결하였습니다. CA C03161926을 참고하십시오.
- 실행과정에 F1와 F2 키가 정확히 실행될 수 있도록 컨트롤러 펌웨어를 수정하였습니다. CA c03127437을 참고하십시오.
- 3TB 드라이브가 예비 부품으로 처리되지 않은 문제를 해결하였습니다.
- 서버 일련 번호, 제품 ID 및 기타 구성이 삭제되거나 기본값으로 재설정되는 문제를 해결하였습니다. 고객 권고사항 c03083515을 참고하십시오
]]>
修正的問題:
- 修復了 HP P812 控制器發生的一個問題: 重啟時會出現罕見的鎖定(編碼 0xD4)問題。
- 修復了如下問題, 含 HP SAS Expander 卡的 HP DL580 G5 錯誤報告磁碟位置資訊。
- 修復了如下問題, 在發生捲改造作業後, 某些組態中 RAID 6 捲在最後一個條帶中有不一致的同位資料。
- 修復了如下問題: 移除一個 HP P2000saG3 控制器模組會導致控制器鎖定(編碼 0xAB)。
- 修復了如下問題: 熱新增一個 3TB 磁碟機至 HP DL180G6 12 磁碟機背板會導致控制器鎖定(編碼 0x15)。
- 修復了如下問題: 將主機資料錯誤放置到一個有記憶體錯誤的寫入快取行中會導致控制器鎖定(編碼 0xBC)。
- 修復了如下問題: 設定為 100% 讀取快取的控制器會導致虛假的"偵測到一個快取錯誤。抓取一份診斷報告獲得更多資訊" 錯誤顯示在 ACU '快取狀態明細'欄中。
- 修復了如下問題: 熱新增一個 SATA 磁碟至 MSA-60, MSA-70 或 HP DL180-G6 12 磁碟機背板後存儲控制器會變得無響應。參閱顧客顧問文檔c03011608。
- 修復了如下問題: 在面臨繁重的 I/O 時處理熱移除事件會變得無響應。
- 修復了一個在捲改造作業中可能遇到的問題。如果發生邏輯"不可恢復的讀取錯誤", 如果原有的捲是在陣列中設定為抵償, 會導致壞區移動至改造後的捲。
- 修復了如下問題:同時處理多個支援"本機命令列隊"的不可恢復讀取錯誤會導致鎖定(編碼 0x15)。
- 修復了如下問題: 磁碟大小超過 2TB 會錯誤標記為故障。
- 修復了如下問題: 在繁重的 I/O 負載下會導致 SSD RAID 10 陣列鎖定(編碼 0x13)。
- 修復了如下問題: 啟動期間, 控制器上沒有安裝任何快取模組時 SATA 磁碟機會偶爾標記為故障或丟失。
- 修復了如下問題: 連接至 SATA 磁碟機, 未執行任何快取模組的控制器,在執行 HP Insight Diagnostics 軟體或離線 HDD 韌體刷新公用程式時遭遇鎖定(編碼 0x15)。
- 修復了如下問題: Open VMS / Solaris 系統下控制器與機櫃 IO 模組之間的纜線拉力問題可導致鎖定(編碼 0x13)。
- 修復了導致控制器在啟動時變得無響應的好幾個問題。參閱 CA C03161926。
- 修復了啟動時控制器韌體無法正常處理 F1 與 F2 鍵的問題。參閱 CA c03127437。
- 修復了如下問題: 3TB 磁碟機無法作為備件來管理。
- 修復了如下問題: 伺服器序號, 產品 ID 與其他組態都被清除或設定為預設。參閱顧客顧問文檔c03083515。
]]>
已修复的问题:
- 修复了 HP P812 控制器中在重新启动时会出现极其少见的锁定(代码 0xD4)的问题。
- 修复了在置了 HP SAS 扩展卡的 HP DL580 G5 中错误地报告磁盘位置信息的问题
- 修复了在某些配置中进行卷转换后,RAID 6 卷在最后一个条带中的奇偶数据不一致的问题。
- 修复了移除 HP P2000saG3 控制器模块可能会导致控制器锁定(代码 0xAB)的问题。
- 修复了向 HP DL180G6 12 驱动器背板中热添加一个 3TB 的驱动器会导致控制器锁定(代码 0x15)的问题。
- 修复了由于错误地将主机数据放入具有内存错误的写高速缓存中从而会导致控制器锁定(代码 0xBC)的问题。
- 修复了将控制器配置为 100% 读高速缓存可能会导致 ACU 的“高速缓存状态详情 (Cache Status Details)” 栏中显示“检测到高速缓存错误。请运行诊断报告获取更多信息 (A cache error was detected.Run a diagnostic report for more information)”错误的问题。
- 修复了向 MSA-60、MSA-70 或 HP DL180-G6 12 驱动器背板中热添加 SATA 磁盘后,存储控制器可能会停止响应的问题。请参阅客户顾问文档 c03011608。
- 修复了在 I/O 繁重的情况下处理热移除事件时,控制器可能会停止响应的问题。
- 修复了在卷转换过程中可能会发生的问题。在阵列中将原始卷配置为偏移位置时,如果发生逻辑性的不可恢复读取错误,可能会使得坏块迁移至所转换卷的错误位置。
- 修复了在支持原生命令队列的 SATA 磁盘上处理大量不可恢复的读取错误时可能会导致锁定(代码 0x15)的问题。
- 修复了磁盘容量大于 2TB 时可能会错误地标记为失败的问题。
- 修复了在 SSD RAID 10 阵列处于繁重的 I/O 负载下会导致锁定(代码 0x13)的问题。
- 修复了控制器上未安装高速缓存模块时,在启动过程中 SATA 磁盘可能会偶尔被标记为失败或丢失的问题。
- 修复了控制器在无高速缓存模块且连接至 SATA 磁盘的情况下运行时可能会在运行 HP Insight Diagnostics 软件或离线硬盘固件刷新实用程序时出现锁定(代码 0x15)的问题。
- 修复了在控制器和机柜 IO 模块之间连接电缆可能会导致 Open VMS / Solaris 系统中发生锁定(代码 0x13)的问题。
- 修复了导致控制器在启动时停止响应的几个问题。请参考客户顾问文档 C03161926。
- 修复了控制器固件在启动时正常运行 F1 和 F2 键的问题。请参考客户顾问文档 c03127437。
- 修复了无法将 3TB 驱动器作为备件管理的问题。
- 修复了服务器序列号、产品 ID 和其它配置被清除或者设置错误的问题。请参阅客户顾问文档 c03083515
]]>
Problems Fixed:
-
Fixed an issue with the HP P812 controller in which a rare lockup (code 0xD4) could occur upon reboot.
-
Fixed an issue where disk location information was reported incorrectly in the HP DL580 G5 with the HP SAS Expander card
-
Fixed an issue where a RAID 6 volume could have inconsistent parity data in the last stripe in certain configurations after a volume transformation operation had occurred.
-
Fixed an issue where removal of a HP P2000saG3 controller module could cause a controller lockup (code 0xAB).
-
Fixed an issue where the hot-add of a 3TB drive to HP DL180G6 12 drive backplane could cause the controller to lock up (code 0x15).
-
Fixed an issue where the controller would lock up (code 0xBC) due to incorrectly placing host data into a write-cache line that had a memory error.
-
Fixed an issue where a controller configured for 100% read cache could cause a false "A cache error was detected. Run a diagnostic report for more information" error to be displayed in the 'Cache Status Details' column in ACU.
-
Fixed an issue where after hot-adding a SATA disk to an MSA-60, MSA-70, or HP DL180-G6 12-drive backplane, the storage controller could become unresponsive. Reference Customer Advisory c03011608.
-
Fixed an issue where the controller could become unresponsive while handling a hot-removal event when experiencing heavy I/O.
-
Fixed an issue that could be experienced during a volume transformation operation. If a logical Unrecovered Read Error occurred, it could cause the bad block(s) to be moved to the incorrect location in the transformed volume if the original volume was configured at an offset in the array.
-
Fixed an issue where simultaneous handling of many Unrecoverable Read Errors on SATA disks supporting Native Command Queuing could result in a lockup (code 0x15).
-
Fixed an issue where a disk of size >2TB could be incorrectly marked as failed.
-
Fixed an issue that caused a lockup (code 0x13) with a SSD RAID 10 array under heavy I/O load.
-
Fixed an issue where SATA disks could occasionally be marked as failed or missing during boot when no cache module is installed on the controller.
-
Fixed an issue where a controller running with no cache module, attached to SATA disks, could encounter a lockup (code 0x15) when running HP Insight Diagnostics software or offline HDD firmware flash utility.
-
Fixed an issue with cable pull between the controller and an enclosure IO module that would cause a lockup (code 0x13) in Open VMS / Solaris systems.
-
Fixed several issues that caused the controller to become unresponsive at boot up time. Reference CA C03161926.
-
Fixed the controller firmware to properly process F1 and F2 keys at startup. Reference CA c03127437.
-
Fixed an issue in which 3TB drives were not managed as spares.
-
Fixed an issue in which the Server Serial Number, Product ID, and Other Configurations were cleared or set to default. Reference Customer Advisory c03083515
]]>
Problems Fixed:
-
Fixed an issue with the HP P812 controller in which a rare lockup (code 0xD4) could occur upon reboot.
-
Fixed an issue where disk location information was reported incorrectly in the HP DL580 G5 with the HP SAS Expander card
-
Fixed an issue where a RAID 6 volume could have inconsistent parity data in the last stripe in certain configurations after a volume transformation operation had occurred.
-
Fixed an issue where removal of a HP P2000saG3 controller module could cause a controller lockup (code 0xAB).
-
Fixed an issue where the hot-add of a 3TB drive to HP DL180G6 12 drive backplane could cause the controller to lock up (code 0x15).
-
Fixed an issue where the controller would lock up (code 0xBC) due to incorrectly placing host data into a write-cache line that had a memory error.
-
Fixed an issue where a controller configured for 100% read cache could cause a false "A cache error was detected. Run a diagnostic report for more information" error to be displayed in the 'Cache Status Details' column in ACU.
-
Fixed an issue where after hot-adding a SATA disk to an MSA-60, MSA-70, or HP DL180-G6 12-drive backplane, the storage controller could become unresponsive. Reference Customer Advisory c03011608.
-
Fixed an issue where the controller could become unresponsive while handling a hot-removal event when experiencing heavy I/O.
-
Fixed an issue that could be experienced during a volume transformation operation. If a logical Unrecovered Read Error occurred, it could cause the bad block(s) to be moved to the incorrect location in the transformed volume if the original volume was configured at an offset in the array.
-
Fixed an issue where simultaneous handling of many Unrecoverable Read Errors on SATA disks supporting Native Command Queuing could result in a lockup (code 0x15).
-
Fixed an issue where a disk of size >2TB could be incorrectly marked as failed.
-
Fixed an issue that caused a lockup (code 0x13) with a SSD RAID 10 array under heavy I/O load.
-
Fixed an issue where SATA disks could occasionally be marked as failed or missing during boot when no cache module is installed on the controller.
-
Fixed an issue where a controller running with no cache module, attached to SATA disks, could encounter a lockup (code 0x15) when running HP Insight Diagnostics software or offline HDD firmware flash utility.
-
Fixed an issue with cable pull between the controller and an enclosure IO module that would cause a lockup (code 0x13) in Open VMS / Solaris systems.
-
Fixed several issues that caused the controller to become unresponsive at boot up time. Reference CA C03161926.
-
Fixed the controller firmware to properly process F1 and F2 keys at startup. Reference CA c03127437.
-
Fixed an issue in which 3TB drives were not managed as spares.
-
Fixed an issue in which the Server Serial Number, Product ID, and Other Configurations were cleared or set to default. Reference Customer Advisory c03083515
]]>
Problems Fixed:
-
Fixed an issue with the HP P812 controller in which a rare lockup (code 0xD4) could occur upon reboot.
-
Fixed an issue where disk location information was reported incorrectly in the HP DL580 G5 with the HP SAS Expander card
-
Fixed an issue where a RAID 6 volume could have inconsistent parity data in the last stripe in certain configurations after a volume transformation operation had occurred.
-
Fixed an issue where removal of a HP P2000saG3 controller module could cause a controller lockup (code 0xAB).
-
Fixed an issue where the hot-add of a 3TB drive to HP DL180G6 12 drive backplane could cause the controller to lock up (code 0x15).
-
Fixed an issue where the controller would lock up (code 0xBC) due to incorrectly placing host data into a write-cache line that had a memory error.
-
Fixed an issue where a controller configured for 100% read cache could cause a false "A cache error was detected. Run a diagnostic report for more information" error to be displayed in the 'Cache Status Details' column in ACU.
-
Fixed an issue where after hot-adding a SATA disk to an MSA-60, MSA-70, or HP DL180-G6 12-drive backplane, the storage controller could become unresponsive. Reference Customer Advisory c03011608.
-
Fixed an issue where the controller could become unresponsive while handling a hot-removal event when experiencing heavy I/O.
-
Fixed an issue that could be experienced during a volume transformation operation. If a logical Unrecovered Read Error occurred, it could cause the bad block(s) to be moved to the incorrect location in the transformed volume if the original volume was configured at an offset in the array.
-
Fixed an issue where simultaneous handling of many Unrecoverable Read Errors on SATA disks supporting Native Command Queuing could result in a lockup (code 0x15).
-
Fixed an issue where a disk of size >2TB could be incorrectly marked as failed.
-
Fixed an issue that caused a lockup (code 0x13) with a SSD RAID 10 array under heavy I/O load.
-
Fixed an issue where SATA disks could occasionally be marked as failed or missing during boot when no cache module is installed on the controller.
-
Fixed an issue where a controller running with no cache module, attached to SATA disks, could encounter a lockup (code 0x15) when running HP Insight Diagnostics software or offline HDD firmware flash utility.
-
Fixed an issue with cable pull between the controller and an enclosure IO module that would cause a lockup (code 0x13) in Open VMS / Solaris systems.
-
Fixed several issues that caused the controller to become unresponsive at boot up time. Reference CA C03161926.
-
Fixed the controller firmware to properly process F1 and F2 keys at startup. Reference CA c03127437.
-
Fixed an issue in which 3TB drives were not managed as spares.
-
Fixed an issue in which the Server Serial Number, Product ID, and Other Configurations were cleared or set to default. Reference Customer Advisory c03083515
]]>
Problems Fixed:
-
Fixed an issue with the HP P812 controller in which a rare lockup (code 0xD4) could occur upon reboot.
-
Fixed an issue where disk location information was reported incorrectly in the HP DL580 G5 with the HP SAS Expander card
-
Fixed an issue where a RAID 6 volume could have inconsistent parity data in the last stripe in certain configurations after a volume transformation operation had occurred.
-
Fixed an issue where removal of a HP P2000saG3 controller module could cause a controller lockup (code 0xAB).
-
Fixed an issue where the hot-add of a 3TB drive to HP DL180G6 12 drive backplane could cause the controller to lock up (code 0x15).
-
Fixed an issue where the controller would lock up (code 0xBC) due to incorrectly placing host data into a write-cache line that had a memory error.
-
Fixed an issue where a controller configured for 100% read cache could cause a false "A cache error was detected. Run a diagnostic report for more information" error to be displayed in the 'Cache Status Details' column in ACU.
-
Fixed an issue where after hot-adding a SATA disk to an MSA-60, MSA-70, or HP DL180-G6 12-drive backplane, the storage controller could become unresponsive. Reference Customer Advisory c03011608.
-
Fixed an issue where the controller could become unresponsive while handling a hot-removal event when experiencing heavy I/O.
-
Fixed an issue that could be experienced during a volume transformation operation. If a logical Unrecovered Read Error occurred, it could cause the bad block(s) to be moved to the incorrect location in the transformed volume if the original volume was configured at an offset in the array.
-
Fixed an issue where simultaneous handling of many Unrecoverable Read Errors on SATA disks supporting Native Command Queuing could result in a lockup (code 0x15).
-
Fixed an issue where a disk of size >2TB could be incorrectly marked as failed.
-
Fixed an issue that caused a lockup (code 0x13) with a SSD RAID 10 array under heavy I/O load.
-
Fixed an issue where SATA disks could occasionally be marked as failed or missing during boot when no cache module is installed on the controller.
-
Fixed an issue where a controller running with no cache module, attached to SATA disks, could encounter a lockup (code 0x15) when running HP Insight Diagnostics software or offline HDD firmware flash utility.
-
Fixed an issue with cable pull between the controller and an enclosure IO module that would cause a lockup (code 0x13) in Open VMS / Solaris systems.
-
Fixed several issues that caused the controller to become unresponsive at boot up time. Reference CA C03161926.
-
Fixed the controller firmware to properly process F1 and F2 keys at startup. Reference CA c03127437.
-
Fixed an issue in which 3TB drives were not managed as spares.
-
Fixed an issue in which the Server Serial Number, Product ID, and Other Configurations were cleared or set to default. Reference Customer Advisory c03083515
]]>
Problems Fixed:
-
Fixed an issue with the HP P812 controller in which a rare lockup (code 0xD4) could occur upon reboot.
-
Fixed an issue where disk location information was reported incorrectly in the HP DL580 G5 with the HP SAS Expander card
-
Fixed an issue where a RAID 6 volume could have inconsistent parity data in the last stripe in certain configurations after a volume transformation operation had occurred.
-
Fixed an issue where removal of a HP P2000saG3 controller module could cause a controller lockup (code 0xAB).
-
Fixed an issue where the hot-add of a 3TB drive to HP DL180G6 12 drive backplane could cause the controller to lock up (code 0x15).
-
Fixed an issue where the controller would lock up (code 0xBC) due to incorrectly placing host data into a write-cache line that had a memory error.
-
Fixed an issue where a controller configured for 100% read cache could cause a false "A cache error was detected. Run a diagnostic report for more information" error to be displayed in the 'Cache Status Details' column in ACU.
-
Fixed an issue where after hot-adding a SATA disk to an MSA-60, MSA-70, or HP DL180-G6 12-drive backplane, the storage controller could become unresponsive. Reference Customer Advisory c03011608.
-
Fixed an issue where the controller could become unresponsive while handling a hot-removal event when experiencing heavy I/O.
-
Fixed an issue that could be experienced during a volume transformation operation. If a logical Unrecovered Read Error occurred, it could cause the bad block(s) to be moved to the incorrect location in the transformed volume if the original volume was configured at an offset in the array.
-
Fixed an issue where simultaneous handling of many Unrecoverable Read Errors on SATA disks supporting Native Command Queuing could result in a lockup (code 0x15).
-
Fixed an issue where a disk of size >2TB could be incorrectly marked as failed.
-
Fixed an issue that caused a lockup (code 0x13) with a SSD RAID 10 array under heavy I/O load.
-
Fixed an issue where SATA disks could occasionally be marked as failed or missing during boot when no cache module is installed on the controller.
-
Fixed an issue where a controller running with no cache module, attached to SATA disks, could encounter a lockup (code 0x15) when running HP Insight Diagnostics software or offline HDD firmware flash utility.
-
Fixed an issue with cable pull between the controller and an enclosure IO module that would cause a lockup (code 0x13) in Open VMS / Solaris systems.
-
Fixed several issues that caused the controller to become unresponsive at boot up time. Reference CA C03161926.
-
Fixed the controller firmware to properly process F1 and F2 keys at startup. Reference CA c03127437.
-
Fixed an issue in which 3TB drives were not managed as spares.
-
Fixed an issue in which the Server Serial Number, Product ID, and Other Configurations were cleared or set to default. Reference Customer Advisory c03083515
]]>
Problems Fixed:
-
Fixed an issue with the HP P812 controller in which a rare lockup (code 0xD4) could occur upon reboot.
-
Fixed an issue where disk location information was reported incorrectly in the HP DL580 G5 with the HP SAS Expander card
-
Fixed an issue where a RAID 6 volume could have inconsistent parity data in the last stripe in certain configurations after a volume transformation operation had occurred.
-
Fixed an issue where removal of a HP P2000saG3 controller module could cause a controller lockup (code 0xAB).
-
Fixed an issue where the hot-add of a 3TB drive to HP DL180G6 12 drive backplane could cause the controller to lock up (code 0x15).
-
Fixed an issue where the controller would lock up (code 0xBC) due to incorrectly placing host data into a write-cache line that had a memory error.
-
Fixed an issue where a controller configured for 100% read cache could cause a false "A cache error was detected. Run a diagnostic report for more information" error to be displayed in the 'Cache Status Details' column in ACU.
-
Fixed an issue where after hot-adding a SATA disk to an MSA-60, MSA-70, or HP DL180-G6 12-drive backplane, the storage controller could become unresponsive. Reference Customer Advisory c03011608.
-
Fixed an issue where the controller could become unresponsive while handling a hot-removal event when experiencing heavy I/O.
-
Fixed an issue that could be experienced during a volume transformation operation. If a logical Unrecovered Read Error occurred, it could cause the bad block(s) to be moved to the incorrect location in the transformed volume if the original volume was configured at an offset in the array.
-
Fixed an issue where simultaneous handling of many Unrecoverable Read Errors on SATA disks supporting Native Command Queuing could result in a lockup (code 0x15).
-
Fixed an issue where a disk of size >2TB could be incorrectly marked as failed.
-
Fixed an issue that caused a lockup (code 0x13) with a SSD RAID 10 array under heavy I/O load.
-
Fixed an issue where SATA disks could occasionally be marked as failed or missing during boot when no cache module is installed on the controller.
-
Fixed an issue where a controller running with no cache module, attached to SATA disks, could encounter a lockup (code 0x15) when running HP Insight Diagnostics software or offline HDD firmware flash utility.
-
Fixed an issue with cable pull between the controller and an enclosure IO module that would cause a lockup (code 0x13) in Open VMS / Solaris systems.
-
Fixed several issues that caused the controller to become unresponsive at boot up time. Reference CA C03161926.
-
Fixed the controller firmware to properly process F1 and F2 keys at startup. Reference CA c03127437.
-
Fixed an issue in which 3TB drives were not managed as spares.
-
Fixed an issue in which the Server Serial Number, Product ID, and Other Configurations were cleared or set to default. Reference Customer Advisory c03083515
]]>
해결된 문제:
- 재부팅 시 HP P812 컨트롤러에 발생하는 록업 (code 0xD4) 문제를 해결하였습니다.
- HP SAS 익스팬더 카드가 장착되어 있는 HP DL580 G5에서 디스크 위치 정보가 잘못 보고되는 문제를 해결하였습니다
- 일부 구성에서 볼륨이 변화되면 마지막 스트라이프의 RAID 6 볼륨이 패리티 데이터와 일치하지 않는 문제를 해결하였습니다.
- HP P2000saG3 컨트롤러를 제거하면 컨트롤러 록업 (code 0xAB)이 발생하는 문제를 해결하였습니다.
- HP DL180G6 12 드라이브 백플레인에 3TB 드라이브를 강제 추가하면 컨트롤러가 록업(code 0x15)되는 문제를 해결하였습니다.
- 호스트 데이터를 메모리 오류가 발생한 읽기-캐시 라인에 잘못 저장함으로 인해 컨트롤러가 록업되는 문제 (code 0xBC)를 해결하였습니다.
- 컨트롤러가 100% 읽기 캐시로 구성되면 ACU의 "캐시 상태 세부정보" 컬럼에 "A cache error was detected. Run a diagnostic report for more information" 오류 메시지가 표시되는 문제를 해결하였습니다.
- MSA-60, MSA-70 또는 HP DL180-G6 12 드라이브 백플레인에 SATA 디스크를 강제 추가하면 스토리지 컨트롤러가 응답하지 않는 문제를 해결하였습니다. 고객 권고사항 c03011608을 참고하십시오.
- I/O에 과부하가 걸린 경우 강제 제거(hot-removal) 이벤트를 처리하는 과정에 컨트롤러가 응답하지 않는 문제를 해결하였습니다.
- 볼륨이 변화되는 과정에 발생할 수 있는 문제를 해결하였습니다. 논리적인, 발견되지 않은 읽기 오류가 발생하면 기본 볼륨이 어레이의 오프셋에서 구성된 경우 해당되지 않는 블록이 변화된 볼륨의 잘못된 위치로 이동할 수 있습니다.
- Native Command Queuing을 지원하는 SATA 디스크에서 동시에 많은 양의 "발견되지 않은 읽기 오류"를 처리하면 록업(code 0x15)이 발생할 수 있는 문제를 해결하였습니다.
- 디스크 크기가 2TB 이상이면 "고장됨"으로 잘못 표기되는 문제를 해결하였습니다.
- I/O에 과부하가 걸리면 SSD RAID 10 어레이에 록업(code 0x13)이 발생하는 문제를 해결하였습니다.
- 컨트롤러에 캐시 모듈이 설치되어 있지 않으면 부팅 과정에 가끔씩 SATA 디스크가 "고장남" 또는 "사라짐"으로 표기되는 문제를 해결하였습니다.
- 캐기 모듈이 설치되어 있지 않고 SATA 디스크에 장착된 컨트롤러에서 HP Insight Diagnostics 소프트웨어 또는 오프라인 HDD 펌웨어 업데이트 유틸리티를 실행하면 록업(code 0x15)이 발생하는 문제를 해결하였습니다.
- 컨트롤러와 인클로저 IO 모듈 사이의 연결선이 끊김으로 인해 Open VMS / Solaris 시스템에 록업(code 0x13)이 발생하는 문제를 해결하였습니다.
- 부팅과정에 컨트롤러가 응답하지 않는 여러가지 문제를 해결하였습니다. CA C03161926을 참고하십시오.
- 실행과정에 F1와 F2 키가 정확히 실행될 수 있도록 컨트롤러 펌웨어를 수정하였습니다. CA c03127437을 참고하십시오.
- 3TB 드라이브가 예비 부품으로 처리되지 않은 문제를 해결하였습니다.
- 서버 일련 번호, 제품 ID 및 기타 구성이 삭제되거나 기본값으로 재설정되는 문제를 해결하였습니다. 고객 권고사항 c03083515을 참고하십시오
]]>
修正的問題:
- 修復了 HP P812 控制器發生的一個問題: 重啟時會出現罕見的鎖定(編碼 0xD4)問題。
- 修復了如下問題, 含 HP SAS Expander 卡的 HP DL580 G5 錯誤報告磁碟位置資訊。
- 修復了如下問題, 在發生捲改造作業後, 某些組態中 RAID 6 捲在最後一個條帶中有不一致的同位資料。
- 修復了如下問題: 移除一個 HP P2000saG3 控制器模組會導致控制器鎖定(編碼 0xAB)。
- 修復了如下問題: 熱新增一個 3TB 磁碟機至 HP DL180G6 12 磁碟機背板會導致控制器鎖定(編碼 0x15)。
- 修復了如下問題: 將主機資料錯誤放置到一個有記憶體錯誤的寫入快取行中會導致控制器鎖定(編碼 0xBC)。
- 修復了如下問題: 設定為 100% 讀取快取的控制器會導致虛假的"偵測到一個快取錯誤。抓取一份診斷報告獲得更多資訊" 錯誤顯示在 ACU '快取狀態明細'欄中。
- 修復了如下問題: 熱新增一個 SATA 磁碟至 MSA-60, MSA-70 或 HP DL180-G6 12 磁碟機背板後存儲控制器會變得無響應。參閱顧客顧問文檔c03011608。
- 修復了如下問題: 在面臨繁重的 I/O 時處理熱移除事件會變得無響應。
- 修復了一個在捲改造作業中可能遇到的問題。如果發生邏輯"不可恢復的讀取錯誤", 如果原有的捲是在陣列中設定為抵償, 會導致壞區移動至改造後的捲。
- 修復了如下問題:同時處理多個支援"本機命令列隊"的不可恢復讀取錯誤會導致鎖定(編碼 0x15)。
- 修復了如下問題: 磁碟大小超過 2TB 會錯誤標記為故障。
- 修復了如下問題: 在繁重的 I/O 負載下會導致 SSD RAID 10 陣列鎖定(編碼 0x13)。
- 修復了如下問題: 啟動期間, 控制器上沒有安裝任何快取模組時 SATA 磁碟機會偶爾標記為故障或丟失。
- 修復了如下問題: 連接至 SATA 磁碟機, 未執行任何快取模組的控制器,在執行 HP Insight Diagnostics 軟體或離線 HDD 韌體刷新公用程式時遭遇鎖定(編碼 0x15)。
- 修復了如下問題: Open VMS / Solaris 系統下控制器與機櫃 IO 模組之間的纜線拉力問題可導致鎖定(編碼 0x13)。
- 修復了導致控制器在啟動時變得無響應的好幾個問題。參閱 CA C03161926。
- 修復了啟動時控制器韌體無法正常處理 F1 與 F2 鍵的問題。參閱 CA c03127437。
- 修復了如下問題: 3TB 磁碟機無法作為備件來管理。
- 修復了如下問題: 伺服器序號, 產品 ID 與其他組態都被清除或設定為預設。參閱顧客顧問文檔c03083515。
]]>
已修复的问题:
]]>
Problems Fixed:
-
Resolved an issue where the server’s serial number, product ID, and/or BIOS Configuration options may be cleared if the server’s HP Smart Array RAID configuration was created by first using the Smart Array’s Option ROM Configuration for Arrays (ORCA) utility or Smart Array Auto-Configuration and then later deleting the configured volume. This may impact all HP ProLiant G6 and G7 BladeSystem servers using the Smart Array Controllers P711m or P712m installed with firmware version 5.32. For more details, please review the customer advisory located here: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03083515
]]>
Problems Fixed:
-
Resolved an issue where the server’s serial number, product ID, and/or BIOS Configuration options may be cleared if the server’s HP Smart Array RAID configuration was created by first using the Smart Array’s Option ROM Configuration for Arrays (ORCA) utility or Smart Array Auto-Configuration and then later deleting the configured volume. This may impact all HP ProLiant G6 and G7 BladeSystem servers using the Smart Array Controllers P711m or P712m installed with firmware version 5.32. For more details, please review the customer advisory located here: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03083515
]]>
Problems Fixed:
-
Resolved an issue where the server’s serial number, product ID, and/or BIOS Configuration options may be cleared if the server’s HP Smart Array RAID configuration was created by first using the Smart Array’s Option ROM Configuration for Arrays (ORCA) utility or Smart Array Auto-Configuration and then later deleting the configured volume. This may impact all HP ProLiant G6 and G7 BladeSystem servers using the Smart Array Controllers P711m or P712m installed with firmware version 5.32. For more details, please review the customer advisory located here: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03083515
]]>
Problems Fixed:
-
Resolved an issue where the server’s serial number, product ID, and/or BIOS Configuration options may be cleared if the server’s HP Smart Array RAID configuration was created by first using the Smart Array’s Option ROM Configuration for Arrays (ORCA) utility or Smart Array Auto-Configuration and then later deleting the configured volume. This may impact all HP ProLiant G6 and G7 BladeSystem servers using the Smart Array Controllers P711m or P712m installed with firmware version 5.32. For more details, please review the customer advisory located here: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03083515
]]>
Problems Fixed:
-
Resolved an issue where the server’s serial number, product ID, and/or BIOS Configuration options may be cleared if the server’s HP Smart Array RAID configuration was created by first using the Smart Array’s Option ROM Configuration for Arrays (ORCA) utility or Smart Array Auto-Configuration and then later deleting the configured volume. This may impact all HP ProLiant G6 and G7 BladeSystem servers using the Smart Array Controllers P711m or P712m installed with firmware version 5.32. For more details, please review the customer advisory located here: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03083515
]]>
修正された問題点:
-
HP SmartアレイRAID構成が最初にSmartアレイのOption ROM Configuration for Arrays(ORCA)ユーティリティまたはSmart Array Auto-Configurationを使用して作成して、その後構成したボリュームを削除した場合、に、シリアル番号、製品ID、および/またはBIOS構成オプションがクリアされる問題を解決しました。 これは、ファームウェアバージョン5.32でインストールされているHP SmartアレイコントローラーP711mあるいはP712mを使用しているすべてのHP ProLiant G6およびG7 BladeSystemサーバーに影響を与える可能性があります。 詳しくは、カスタマーアドバイザリhttp://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03083515(英語)を参照してください。
]]>
해결된 문제:
]]>
修正的問題:
]]>
增强功能/新功能:
新增对以下服务器的支持:
- HP D2600 和 HP D2700 磁盘机柜
- HP 600 模块化磁盘系统
- 大小超过 2.2 TB 的 HDD
- 用于选定单级单元 (SLC) 和多级单元 (MLC) SSD 的 HP Smart SSD Gas Gauge
]]>
Enhancements/New Features:
Added support for:
-
HP D2600 and the HP D2700 Disk Enclosures
-
HP 600 Modular Disk System
-
HDDs that exceed 2.2 TB in size
-
HP Smart SSD Gas Gauge for select Single Level Cell (SLC) and Multi-Level Cell (MLC) SSD's
]]>
Enhancements/New Features:
Added support for:
-
HP D2600 and the HP D2700 Disk Enclosures
-
HP 600 Modular Disk System
-
HDDs that exceed 2.2 TB in size
-
HP Smart SSD Gas Gauge for select Single Level Cell (SLC) and Multi-Level Cell (MLC) SSD's
]]>
Enhancements/New Features:
Added support for:
-
HP D2600 and the HP D2700 Disk Enclosures
-
HP 600 Modular Disk System
-
HDDs that exceed 2.2 TB in size
-
HP Smart SSD Gas Gauge for select Single Level Cell (SLC) and Multi-Level Cell (MLC) SSD's
]]>
Enhancements/New Features:
Added support for:
-
HP D2600 and the HP D2700 Disk Enclosures
-
HP 600 Modular Disk System
-
HDDs that exceed 2.2 TB in size
-
HP Smart SSD Gas Gauge for select Single Level Cell (SLC) and Multi-Level Cell (MLC) SSD's
]]>
Enhancements/New Features:
Added support for:
-
HP D2600 and the HP D2700 Disk Enclosures
-
HP 600 Modular Disk System
-
HDDs that exceed 2.2 TB in size
-
HP Smart SSD Gas Gauge for select Single Level Cell (SLC) and Multi-Level Cell (MLC) SSD's
]]>
改善点/新しい機能:
以下のサポートを追加しました。
-
HP D2600およびHP D2700ディスクエンクロージャー
-
HP 600 Modular Disk System
-
2.2TBを超えるHDD
-
特定のSingle Level Cell(SLC)およびMulti-Level Cell(MLC)SSD用のHP Smart SSD Gas Gauge
]]>
개선 사항/새로운 기능:
다음 시스템에 대한 지원을 추가하였습니다:
- HP D2600 및 HP D2700 디스크 인클로저
- HP 600 모듈러식 디스크 시스템
- 크기가 2.2TB를 초과하는 HDD
- SLC(Single Level Cell) 및 MLC(Multi-Level Cell) SSD 선택을 위한 HP Smart SSD 가스 게이지
]]>
增強或新增功能:
針對下列項目新增支援:
- HP D2600 和 HP D2700 磁碟機櫃
- HP 600 模組式磁碟系統
- 大小超過 2.2 TB 的 HDD
- HP Smart SSD Gas Gauge (適用於特定單層單元 (SLC) 與多層單元 (MLC) SSD)
]]>
固件依赖条件:
下列设备对用于 HP Smart Array FW 5.32 版的 FW 可交付物有最低要求:
设备 最低版本
- HP D2060 磁盘机柜 1.34
- HP D2070 磁盘机柜 1.34
- HP 600 模块化磁盘系统 3.44
- HP P2000 模块化智能阵列 TS230P06
- Virtual Storage Manager 2.0.1.0
修复的问题:
· 1783-Slot # Drive Array Controller Failure
· 1719-Slot [x] Drive Array - A controller failure event occurred prior to this power-up (previous lock-up code = 0x11) [or other lock-up codes] (RESUME = "F1" KEY)
]]>
Firmware Dependency:
The devices listed below require minimum FW deliverables with HP Smart Array FW version 5.32:
Device Minimum Version
-
HP D2060 Disk Enclosure 1.34
-
HP D2070 Disk Enclosure 1.34
-
HP 600 Modular Disk System 3.44
-
HP P2000 Modular Smart Array TS230P06
-
Virtual Storage Manager 2.0.1.0
Problems Fixed:
-
For additional information, reference Customer Advisory c03012502 at the following URL: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03012502
There is a potential data transfer issue if the following Smart Array controllers P212, P410, P410i, P411, or P812 are attached to certain models of the SATA hard drives. SAS hard drives are not affected by this issue. For additional information and a list of affected SATA hard drives models, reference Customer Advisory c03011446 at the following URL: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03011446
-
SATA hard drives may not be discovered during Power-On Self-Test (POST) when attached to Smart Array P212, P410, or P410i Controllers that are configured for Zero Memory RAID (ZMR).
-
RAID 6/60 surface analysis could result in background parity scans that stop responding while doing excessive fault tolerance calculations.
-
When a Smart Array controller is configured without a cache module the server intermittently will not respond during the boot process.
-
The server PXE was prevented from successfully booting.
-
An IO request that is never completed after outstanding read and write requests overlapped the same block range. This issue can potentially cause the controller to stop responding without displaying a lockup code as a result.
-
An apparent hot-swap of a disk drive is reported even though the drive was not physically hot-plugged.
-
Flash-based cache modules caused a controller failure at POST, displaying one of the following error messages:
· 1783-Slot # Drive Array Controller Failure
· 1719-Slot [x] Drive Array - A controller failure event occurred prior to this power-up (previous lock-up code = 0x11) [or other lock-up codes] (RESUME = "F1" KEY)
]]>
Firmware Dependency:
The devices listed below require minimum FW deliverables with HP Smart Array FW version 5.32:
Device Minimum Version
-
HP D2060 Disk Enclosure 1.34
-
HP D2070 Disk Enclosure 1.34
-
HP 600 Modular Disk System 3.44
-
HP P2000 Modular Smart Array TS230P06
-
Virtual Storage Manager 2.0.1.0
Problems Fixed:
-
For additional information, reference Customer Advisory c03012502 at the following URL: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03012502
There is a potential data transfer issue if the following Smart Array controllers P212, P410, P410i, P411, or P812 are attached to certain models of the SATA hard drives. SAS hard drives are not affected by this issue. For additional information and a list of affected SATA hard drives models, reference Customer Advisory c03011446 at the following URL: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03011446
-
SATA hard drives may not be discovered during Power-On Self-Test (POST) when attached to Smart Array P212, P410, or P410i Controllers that are configured for Zero Memory RAID (ZMR).
-
RAID 6/60 surface analysis could result in background parity scans that stop responding while doing excessive fault tolerance calculations.
-
When a Smart Array controller is configured without a cache module the server intermittently will not respond during the boot process.
-
The server PXE was prevented from successfully booting.
-
An IO request that is never completed after outstanding read and write requests overlapped the same block range. This issue can potentially cause the controller to stop responding without displaying a lockup code as a result.
-
An apparent hot-swap of a disk drive is reported even though the drive was not physically hot-plugged.
-
Flash-based cache modules caused a controller failure at POST, displaying one of the following error messages:
· 1783-Slot # Drive Array Controller Failure
· 1719-Slot [x] Drive Array - A controller failure event occurred prior to this power-up (previous lock-up code = 0x11) [or other lock-up codes] (RESUME = "F1" KEY)
]]>
Firmware Dependency:
The devices listed below require minimum FW deliverables with HP Smart Array FW version 5.32:
Device Minimum Version
-
HP D2060 Disk Enclosure 1.34
-
HP D2070 Disk Enclosure 1.34
-
HP 600 Modular Disk System 3.44
-
HP P2000 Modular Smart Array TS230P06
-
Virtual Storage Manager 2.0.1.0
Problems Fixed:
-
For additional information, reference Customer Advisory c03012502 at the following URL: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03012502
There is a potential data transfer issue if the following Smart Array controllers P212, P410, P410i, P411, or P812 are attached to certain models of the SATA hard drives. SAS hard drives are not affected by this issue. For additional information and a list of affected SATA hard drives models, reference Customer Advisory c03011446 at the following URL: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03011446
-
SATA hard drives may not be discovered during Power-On Self-Test (POST) when attached to Smart Array P212, P410, or P410i Controllers that are configured for Zero Memory RAID (ZMR).
-
RAID 6/60 surface analysis could result in background parity scans that stop responding while doing excessive fault tolerance calculations.
-
When a Smart Array controller is configured without a cache module the server intermittently will not respond during the boot process.
-
The server PXE was prevented from successfully booting.
-
An IO request that is never completed after outstanding read and write requests overlapped the same block range. This issue can potentially cause the controller to stop responding without displaying a lockup code as a result.
-
An apparent hot-swap of a disk drive is reported even though the drive was not physically hot-plugged.
-
Flash-based cache modules caused a controller failure at POST, displaying one of the following error messages:
· 1783-Slot # Drive Array Controller Failure
· 1719-Slot [x] Drive Array - A controller failure event occurred prior to this power-up (previous lock-up code = 0x11) [or other lock-up codes] (RESUME = "F1" KEY)
]]>
Firmware Dependency:
The devices listed below require minimum FW deliverables with HP Smart Array FW version 5.32:
Device Minimum Version
-
HP D2060 Disk Enclosure 1.34
-
HP D2070 Disk Enclosure 1.34
-
HP 600 Modular Disk System 3.44
-
HP P2000 Modular Smart Array TS230P06
-
Virtual Storage Manager 2.0.1.0
Problems Fixed:
-
For additional information, reference Customer Advisory c03012502 at the following URL: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03012502
There is a potential data transfer issue if the following Smart Array controllers P212, P410, P410i, P411, or P812 are attached to certain models of the SATA hard drives. SAS hard drives are not affected by this issue. For additional information and a list of affected SATA hard drives models, reference Customer Advisory c03011446 at the following URL: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03011446
-
SATA hard drives may not be discovered during Power-On Self-Test (POST) when attached to Smart Array P212, P410, or P410i Controllers that are configured for Zero Memory RAID (ZMR).
-
RAID 6/60 surface analysis could result in background parity scans that stop responding while doing excessive fault tolerance calculations.
-
When a Smart Array controller is configured without a cache module the server intermittently will not respond during the boot process.
-
The server PXE was prevented from successfully booting.
-
An IO request that is never completed after outstanding read and write requests overlapped the same block range. This issue can potentially cause the controller to stop responding without displaying a lockup code as a result.
-
An apparent hot-swap of a disk drive is reported even though the drive was not physically hot-plugged.
-
Flash-based cache modules caused a controller failure at POST, displaying one of the following error messages:
· 1783-Slot # Drive Array Controller Failure
· 1719-Slot [x] Drive Array - A controller failure event occurred prior to this power-up (previous lock-up code = 0x11) [or other lock-up codes] (RESUME = "F1" KEY)
]]>
Firmware Dependency:
The devices listed below require minimum FW deliverables with HP Smart Array FW version 5.32:
Device Minimum Version
-
HP D2060 Disk Enclosure 1.34
-
HP D2070 Disk Enclosure 1.34
-
HP 600 Modular Disk System 3.44
-
HP P2000 Modular Smart Array TS230P06
-
Virtual Storage Manager 2.0.1.0
Problems Fixed:
-
For additional information, reference Customer Advisory c03012502 at the following URL: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03012502
There is a potential data transfer issue if the following Smart Array controllers P212, P410, P410i, P411, or P812 are attached to certain models of the SATA hard drives. SAS hard drives are not affected by this issue. For additional information and a list of affected SATA hard drives models, reference Customer Advisory c03011446 at the following URL: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03011446
-
SATA hard drives may not be discovered during Power-On Self-Test (POST) when attached to Smart Array P212, P410, or P410i Controllers that are configured for Zero Memory RAID (ZMR).
-
RAID 6/60 surface analysis could result in background parity scans that stop responding while doing excessive fault tolerance calculations.
-
When a Smart Array controller is configured without a cache module the server intermittently will not respond during the boot process.
-
The server PXE was prevented from successfully booting.
-
An IO request that is never completed after outstanding read and write requests overlapped the same block range. This issue can potentially cause the controller to stop responding without displaying a lockup code as a result.
-
An apparent hot-swap of a disk drive is reported even though the drive was not physically hot-plugged.
-
Flash-based cache modules caused a controller failure at POST, displaying one of the following error messages:
· 1783-Slot # Drive Array Controller Failure
· 1719-Slot [x] Drive Array - A controller failure event occurred prior to this power-up (previous lock-up code = 0x11) [or other lock-up codes] (RESUME = "F1" KEY)
]]>
ファームウェアの関連性:
以下に記載されているデバイスは、HP SmartアレイのFWバージョン5.32に含まれる最小FWが必要です。
デバイス 最小バージョン
-
HP D2060ディスクエンクロージャー 1.34
-
HP D2070ディスクエンクロージャー 1.34
-
HP 600 Modular Disk System 3.44
-
HP P2000 Modular Smart Array TS230P006
-
Virtual Storage Manager 2.0.1.0
修正された問題点:
· 1783-Slot # Drive Array Controller Failure
· 1719-Slot [x] Drive Array - A controller failure event occurred prior to this power-up (previous lock-up code = 0x11) [or other lock-up codes] (RESUME = "F1" KEY)
]]>
펌웨어 종속성:
아래에 나열되어 있는 장치에는 HP Smart Array FW 5.32 이상 버전의 펌웨어가 설치되어 있어야 합니다:
장치 최소 버전
- HP D2060 Disk Enclosure 1.34
- HP D2070 Disk Enclosure 1.34
- HP 600 Modular Disk System 3.44
- HP P2000 Modular Smart Array TS230P06
- Virtual Storage Manager 2.0.1.0
해결된 문제:
-
자세한 정보는 다음 URL을 통해 제공되는 고객 권고사항 c03012502을 참조하십시오: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03012502
아래의 스마트 어레이 컨트롤러 P212, P410, P410i, P411 또는 P812가 SATA 하드 드라이브의 특정 모델과 연결되어 있는 경우 잠재적으로 데이터 전송 오류가 발생할 수 있습니다. SAS 하드 드라이브는 이 문제의 영향을 받지 않습니다. 더욱 자세한 정보와 영향받는 SATA 하드 드라이브 모델 목록을 보시려면 다음 URL을 통해 제공되는 고객 권고사항 c03011446을 참조하십시오: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03011446
- Zero Memory RAID (ZMR)로 구성된 스마트 어레이 P212, P410 또는 P410i 컨트롤러로 연결된 경우 POST 과정에 SATA 하드 드라이브가 인식되지 않을 수 있습니다 .
- RAID 6/60 표면 분석을 진행하면 배후 패리티(background parity)가 스캔되면서 과부하 고장 진단 계산을 진행하는 과정에 응답을 멈출 수 있습니다.
- 캐시 모듈이 없이 스마트 어레이 컨트롤러가 구성된 경우 부팅 과정에 서버가 간헐적으로 응답을 멈출 수 있습니다.
- 서버 PXE가 성공적으로 부팅되지 못합니다.
- 대기중 읽기 및 쓰기 요청이 동일한 블록 범위를 초과하면 IO 요청이 완료되지 않습니다. 이 문제로 인해 컨트롤러가 록업 코드 표시없이 중단될 수 있습니다.
- 드라이브가 물리적으로 핫플러그되어 있지 않음에도 디스크의 명백한 핫스왑이 보고됩니다.
- 플래시 기반 캐시 모듈로 인해 POST에서 컨트롤러 오류가 발생하여 다음과 같은 오류 메시지 중 하나가 표시됩니다.
· 1783-Slot # Drive Array Controller Failure
· 1719-Slot [x] Drive Array - A controller failure event occurred prior to this power-up (previous lock-up code = 0x11) [or other lock-up codes] (RESUME = "F1" KEY)
]]>
韌體相依性:
使用 HP 智慧型陣列韌體 5.32 版時,各裝置所需要的最低韌體交付項目版本如下:
裝置 最低版本
- HP D2060 磁碟機櫃 1.34
- HP D2070 磁碟機櫃 1.34
- HP 600 模組式磁碟系統 3.44
- HP P2000 模組式智慧型陣列 TS230P06
- 虛擬儲存管理員 2.0.1.0
修正的問題:
· 1783-Slot # Drive Array Controller Failure (1783-插槽 # 磁碟陣列控制器故障)
· 1719-Slot [x] Drive Array - A controller failure event occurred prior to this power-up (previous lock-up code = 0x11) [or other lock-up codes] (RESUME = "F1" KEY) (1719-插槽 [x] 磁碟陣列 ─ 在此次開啟電源之前,發生控制器故障事件 (先前鎖定代碼 = 0x11) [或其他鎖定代碼] (恢復 = F1 鍵))
]]>
已修复的问题:
]]>
Problems Fixed:
-
Resolved an issue where the server’s serial number, product ID, and/or BIOS Configuration options may be cleared if the server’s HP Smart Array RAID configuration was created by first using the Smart Array’s Option ROM Configuration for Arrays (ORCA) utility or Smart Array Auto-Configuration and then later by deleting the configured volume. This may impact all HP ProLiant G6 and G7 servers, except the 100 series, using the Smart Array Controllers P212, P410i, P410, P411, or P812 installed with either firmware version 5.06 or 5.12. For more details, please review the customer advisory located here: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03083515
]]>
Problems Fixed:
-
Resolved an issue where the server’s serial number, product ID, and/or BIOS Configuration options may be cleared if the server’s HP Smart Array RAID configuration was created by first using the Smart Array’s Option ROM Configuration for Arrays (ORCA) utility or Smart Array Auto-Configuration and then later by deleting the configured volume. This may impact all HP ProLiant G6 and G7 servers, except the 100 series, using the Smart Array Controllers P212, P410i, P410, P411, or P812 installed with either firmware version 5.06 or 5.12. For more details, please review the customer advisory located here: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03083515
]]>
Problems Fixed:
-
Resolved an issue where the server’s serial number, product ID, and/or BIOS Configuration options may be cleared if the server’s HP Smart Array RAID configuration was created by first using the Smart Array’s Option ROM Configuration for Arrays (ORCA) utility or Smart Array Auto-Configuration and then later by deleting the configured volume. This may impact all HP ProLiant G6 and G7 servers, except the 100 series, using the Smart Array Controllers P212, P410i, P410, P411, or P812 installed with either firmware version 5.06 or 5.12. For more details, please review the customer advisory located here: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03083515
]]>
Problems Fixed:
-
Resolved an issue where the server’s serial number, product ID, and/or BIOS Configuration options may be cleared if the server’s HP Smart Array RAID configuration was created by first using the Smart Array’s Option ROM Configuration for Arrays (ORCA) utility or Smart Array Auto-Configuration and then later by deleting the configured volume. This may impact all HP ProLiant G6 and G7 servers, except the 100 series, using the Smart Array Controllers P212, P410i, P410, P411, or P812 installed with either firmware version 5.06 or 5.12. For more details, please review the customer advisory located here: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03083515
]]>
Problems Fixed:
-
Resolved an issue where the server’s serial number, product ID, and/or BIOS Configuration options may be cleared if the server’s HP Smart Array RAID configuration was created by first using the Smart Array’s Option ROM Configuration for Arrays (ORCA) utility or Smart Array Auto-Configuration and then later by deleting the configured volume. This may impact all HP ProLiant G6 and G7 servers, except the 100 series, using the Smart Array Controllers P212, P410i, P410, P411, or P812 installed with either firmware version 5.06 or 5.12. For more details, please review the customer advisory located here: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03083515
]]>
修正された問題点::
-
HP SmartアレイRAID構成が最初にSmartアレイのOption ROM Configuration for Arrays(ORCA)ユーティリティまたはSmart Array Auto-Configurationを使用して作成して、その後構成したボリュームを削除した場合、に、シリアル番号、製品ID、および/またはBIOS構成オプションがクリアされる問題を解決しました。 これは、ファームウェアバージョン5.06または5.12でインストールされているHP SmartアレイコントローラーP212、P410i、P410、P411あるいはP812を使用している100シリーズを除くすべてのHP ProLiant G6およびG7サーバーに影響を与える可能性があります。 詳しくは、カスタマーアドバイザリhttp://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03083515(英語)を参照してください。
]]>
해결된 문제:
- 서버의 HP 스마트 어레이 RAID 구성이 스마트 어레이의 ORCA 유틸리티 옵션 또는 스마트 어레이 자동 구성을 통해 맨 처음 생성된 다음 해당 구성 값을 삭제하면 서버의 일련 번호,제품 ID 또는 BIOS 구성 옵션이 삭제될 수도 있는 문제를 해결하였습니다. 해당 문제는 펌웨어 5.06 또는 5.12 버전이 설치되어 있는 스마트 어레이 컨트롤러 P212, P410i, P410, P411 또는 P812를 실행하는, 100 시리즈를 제외한 모든 HP 프로라이언트 G6 및 G7 서버에 영향을 미칩니다.더욱 자세한 정보는 다음 주소를 통해 제공되는 고객 권고 문서를 참조하십시오: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03083515
]]>
修正的問題:
]]>
重要提示:
已解决的问题:
如欲了解更多信息,请参考客户顾问文档 c03012502,网址为: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03012502
已知问题:
]]>
Important Notes:
-
This firmware is Optional for customers using SAS drives.
Problems Fixed:
-
There is a potential data transfer issue if the following Smart Array controllers P212, P410, P410i, P411, or P812 are attached to certain models of the SATA hard drives. SAS hard drives are not affected by this issue. For additional information and a list of affected SATA hard drives models, reference Customer Advisory c03011446 at the following URL: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03011446
-
SATA hard drives may not be discovered during Power-On Self-Test (POST) when attached to Smart Array P212, P410, or P410i Controllers that are configured for Zero Memory RAID (ZMR).
For additional information, reference Customer Advisory c03012502 at the following URL: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03012502
Known Issues:
]]>
Important Notes:
-
This firmware is Optional for customers using SAS drives.
Problems Fixed:
-
There is a potential data transfer issue if the following Smart Array controllers P212, P410, P410i, P411, or P812 are attached to certain models of the SATA hard drives. SAS hard drives are not affected by this issue. For additional information and a list of affected SATA hard drives models, reference Customer Advisory c03011446 at the following URL: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03011446
-
SATA hard drives may not be discovered during Power-On Self-Test (POST) when attached to Smart Array P212, P410, or P410i Controllers that are configured for Zero Memory RAID (ZMR).
For additional information, reference Customer Advisory c03012502 at the following URL: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03012502
Known Issues:
]]>
Important Notes:
-
This firmware is Optional for customers using SAS drives.
Problems Fixed:
-
There is a potential data transfer issue if the following Smart Array controllers P212, P410, P410i, P411, or P812 are attached to certain models of the SATA hard drives. SAS hard drives are not affected by this issue. For additional information and a list of affected SATA hard drives models, reference Customer Advisory c03011446 at the following URL: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03011446
-
SATA hard drives may not be discovered during Power-On Self-Test (POST) when attached to Smart Array P212, P410, or P410i Controllers that are configured for Zero Memory RAID (ZMR).
For additional information, reference Customer Advisory c03012502 at the following URL: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03012502
Known Issues:
]]>
Important Notes:
-
This firmware is Optional for customers using SAS drives.
Problems Fixed:
-
There is a potential data transfer issue if the following Smart Array controllers P212, P410, P410i, P411, or P812 are attached to certain models of the SATA hard drives. SAS hard drives are not affected by this issue. For additional information and a list of affected SATA hard drives models, reference Customer Advisory c03011446 at the following URL: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03011446
-
SATA hard drives may not be discovered during Power-On Self-Test (POST) when attached to Smart Array P212, P410, or P410i Controllers that are configured for Zero Memory RAID (ZMR).
For additional information, reference Customer Advisory c03012502 at the following URL: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03012502
Known Issues:
]]>
Important Notes:
-
This firmware is Optional for customers using SAS drives.
Problems Fixed:
-
There is a potential data transfer issue if the following Smart Array controllers P212, P410, P410i, P411, or P812 are attached to certain models of the SATA hard drives. SAS hard drives are not affected by this issue. For additional information and a list of affected SATA hard drives models, reference Customer Advisory c03011446 at the following URL: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03011446
-
SATA hard drives may not be discovered during Power-On Self-Test (POST) when attached to Smart Array P212, P410, or P410i Controllers that are configured for Zero Memory RAID (ZMR).
For additional information, reference Customer Advisory c03012502 at the following URL: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03012502
Known Issues:
]]>
重要な注意:
-
このファームウェアは、SASドライブを使用するためのオプションです。
修正された問題点:
詳しくは、以下のURLのカスタマーアドバイザリc03012502を参照してください。 http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03012502(英語)
既知の問題点:
]]>
중요 알림:
- SAS 드라이브 사용 시 선택적으로 펌웨어를 사용할 수 있습니다.
해결된 문제:
- 아래의 스마트 어레이 컨트롤러 P212, P410, P410i, P411 또는 P812가 SATA 하드 드라이브의 특정 모델과 연결되어 있는 경우 잠재적으로 데이터 전송 오류가 발생할 수 있습니다. SAS 하드 드라이브는 이 문제의 영향을 받지 않습니다. 더욱 자세한 정보와 영향받는 SATA 하드 드라이브 모델 목록을 보시려면 다음 URL을 통해 제공되는 고객 권고사항 c03011446을 참조하십시오: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03011446
- Zero Memory RAID (ZMR)로 구성된 스마트 어레이 P212, P410 또는 P410i 컨트롤러로 연결된 경우 POST 과정에 SATA 하드 드라이브가 인식되지 않을 수 있습니다 .
자세한 정보는 다음 URL을 통해 제공되는 고객 권고사항 c03012502을 참조하십시오: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03012502
알려진 문제:
]]>
重要注意事項:
- 此韌體對於使用 SAS 磁碟機的客戶而言是選購配備。
修正的問題:
若需相關資訊,請參閱 Customer Advisory c03012502,網址為: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03012502
已知問題:
]]>
增强功能/新功能:
增加了对以下功能的支持:
- 大小超过 2.2 TB 的 HDD
- 连接到 HP D2200sb 存储刀片的 SATA 固态驱动器 (SSD)
- 用于选定单级单元 (SLC) 和多级单元 (MLC) SSD 的 HP Smart SSD Gas Gauge
]]>
Enhancements/New Features:
Added support for the following features:
- HDDs that exceed 2.2 TB in size
- SATA Solid State Drives (SSD) connected to the HP D2200sb Storage Blade
- HP Smart SSD Gas Gauge for select Single Level Cell (SLC) and Multi-Level Cell (MLC) SSD's
]]>
Enhancements/New Features:
Added support for the following features:
- HDDs that exceed 2.2 TB in size
- SATA Solid State Drives (SSD) connected to the HP D2200sb Storage Blade
- HP Smart SSD Gas Gauge for select Single Level Cell (SLC) and Multi-Level Cell (MLC) SSD's
]]>
Enhancements/New Features:
Added support for the following features:
- HDDs that exceed 2.2 TB in size
- SATA Solid State Drives (SSD) connected to the HP D2200sb Storage Blade
- HP Smart SSD Gas Gauge for select Single Level Cell (SLC) and Multi-Level Cell (MLC) SSD's
]]>
Enhancements/New Features:
Added support for the following features:
- HDDs that exceed 2.2 TB in size
- SATA Solid State Drives (SSD) connected to the HP D2200sb Storage Blade
- HP Smart SSD Gas Gauge for select Single Level Cell (SLC) and Multi-Level Cell (MLC) SSD's
]]>
Enhancements/New Features:
Added support for the following features:
- HDDs that exceed 2.2 TB in size
- SATA Solid State Drives (SSD) connected to the HP D2200sb Storage Blade
- HP Smart SSD Gas Gauge for select Single Level Cell (SLC) and Multi-Level Cell (MLC) SSD's
]]>
改善点/新しい機能:
以下の機能のサポートを追加しました。
- 2.2TBを超えるHDD
- HP D2200sb Storage Bladeに接続されたSATA Solid State Drive(SSD)
- Single Level Cell(SLC)およびMulti-Level Cell(MLC)SSDを選択するためのHP Smart SSD Gas Gauge
]]>
향상된/새로운 기능:
다음 기능에 대한 지원이 추가되었습니다:
- 크기가 2.2TB를 초과하는 HDD
- HP D2200sb 스토리지 블레이드에 연결된 SATA 솔리드 스테이트 드라이브(SSD)
- SLC(Single Level Cell) 및 MLC(Multi-Level Cell) SSD 선택을 위한 HP Smart SSD 가스 게이지
]]>
Enhancements/New Features:
Added support for the following features:
- HDDs that exceed 2.2 TB in size
- SATA Solid State Drives (SSD) connected to the HP D2200sb Storage Blade
- HP Smart SSD Gas Gauge for select Single Level Cell (SLC) and Multi-Level Cell (MLC) SSD's
]]>
修复的问题:
解决了以下问题:
· 1783-Slot # Drive Array Controller Failure
· 1719-Slot [x] Drive Array - A controller failure event occurred prior to this power-up (previous lock-up code = 0x11) [or other lock-up codes] (RESUME = "F1" KEY)
- HP Smart Array 固件版本 3.52 的发布导致了零内存 RAID 模式下重建性能的回归。
- Smart Array P812 控制器连接至多个 MSA 60 存储系统后,可能会在处理大量 I/O 工作负载时遇到锁定情况(锁定代码 0XAB)。
- 修复了在进入 HP DL165 G7 和 HP DL170e G6 上 Online Raid Configuration Utility 后,导致系统重置或挂起的问题。
]]>
Problems Fixed:
Resolved the following issues:
-
An issue resulting in a server hang during the boot process when a Smart Array controller is configured without a cache module.
-
An issue that prevented a successful server PXE boot.
-
An issue that resulted in never completing an IO request after outstanding read and write requests overlapped the same block range. This issue can potentially cause controller hang with no lockup code as a result.
-
An apparent hot-swap of a disk drive is reported even though the drive was not physically hot-plugged.
-
Flash-based cache modules caused a controller failure at POST, displaying one of the following error messages:
· 1783-Slot # Drive Array Controller Failure
· 1719-Slot [x] Drive Array - A controller failure event occurred prior to this power-up (previous lock-up code = 0x11) [or other lock-up codes] (RESUME = "F1" KEY)
-
The release of HP Smart Array firmware version 3.52 caused a regression in rebuild performance while in Zero Memory Raid mode.
-
A Smart Array P812 controller attached to multiple MSA 60 storage systems may encounter a lockup condition (lockup code 0XAB) during heavy I/O workload.
-
Fixed a BIOS interaction issue that causes a system reset or hang after entering the Online Raid Configuration Utility on the HP DL165 G7 and the HP DL170e G6.
]]>
Problems Fixed:
Resolved the following issues:
-
An issue resulting in a server hang during the boot process when a Smart Array controller is configured without a cache module.
-
An issue that prevented a successful server PXE boot.
-
An issue that resulted in never completing an IO request after outstanding read and write requests overlapped the same block range. This issue can potentially cause controller hang with no lockup code as a result.
-
An apparent hot-swap of a disk drive is reported even though the drive was not physically hot-plugged.
-
Flash-based cache modules caused a controller failure at POST, displaying one of the following error messages:
· 1783-Slot # Drive Array Controller Failure
· 1719-Slot [x] Drive Array - A controller failure event occurred prior to this power-up (previous lock-up code = 0x11) [or other lock-up codes] (RESUME = "F1" KEY)
-
The release of HP Smart Array firmware version 3.52 caused a regression in rebuild performance while in Zero Memory Raid mode.
-
A Smart Array P812 controller attached to multiple MSA 60 storage systems may encounter a lockup condition (lockup code 0XAB) during heavy I/O workload.
-
Fixed a BIOS interaction issue that causes a system reset or hang after entering the Online Raid Configuration Utility on the HP DL165 G7 and the HP DL170e G6.
]]>
Problems Fixed:
Resolved the following issues:
-
An issue resulting in a server hang during the boot process when a Smart Array controller is configured without a cache module.
-
An issue that prevented a successful server PXE boot.
-
An issue that resulted in never completing an IO request after outstanding read and write requests overlapped the same block range. This issue can potentially cause controller hang with no lockup code as a result.
-
An apparent hot-swap of a disk drive is reported even though the drive was not physically hot-plugged.
-
Flash-based cache modules caused a controller failure at POST, displaying one of the following error messages:
· 1783-Slot # Drive Array Controller Failure
· 1719-Slot [x] Drive Array - A controller failure event occurred prior to this power-up (previous lock-up code = 0x11) [or other lock-up codes] (RESUME = "F1" KEY)
-
The release of HP Smart Array firmware version 3.52 caused a regression in rebuild performance while in Zero Memory Raid mode.
-
A Smart Array P812 controller attached to multiple MSA 60 storage systems may encounter a lockup condition (lockup code 0XAB) during heavy I/O workload.
-
Fixed a BIOS interaction issue that causes a system reset or hang after entering the Online Raid Configuration Utility on the HP DL165 G7 and the HP DL170e G6.
]]>
Problems Fixed:
Resolved the following issues:
-
An issue resulting in a server hang during the boot process when a Smart Array controller is configured without a cache module.
-
An issue that prevented a successful server PXE boot.
-
An issue that resulted in never completing an IO request after outstanding read and write requests overlapped the same block range. This issue can potentially cause controller hang with no lockup code as a result.
-
An apparent hot-swap of a disk drive is reported even though the drive was not physically hot-plugged.
-
Flash-based cache modules caused a controller failure at POST, displaying one of the following error messages:
· 1783-Slot # Drive Array Controller Failure
· 1719-Slot [x] Drive Array - A controller failure event occurred prior to this power-up (previous lock-up code = 0x11) [or other lock-up codes] (RESUME = "F1" KEY)
-
The release of HP Smart Array firmware version 3.52 caused a regression in rebuild performance while in Zero Memory Raid mode.
-
A Smart Array P812 controller attached to multiple MSA 60 storage systems may encounter a lockup condition (lockup code 0XAB) during heavy I/O workload.
-
Fixed a BIOS interaction issue that causes a system reset or hang after entering the Online Raid Configuration Utility on the HP DL165 G7 and the HP DL170e G6.
]]>
Problems Fixed:
Resolved the following issues:
-
An issue resulting in a server hang during the boot process when a Smart Array controller is configured without a cache module.
-
An issue that prevented a successful server PXE boot.
-
An issue that resulted in never completing an IO request after outstanding read and write requests overlapped the same block range. This issue can potentially cause controller hang with no lockup code as a result.
-
An apparent hot-swap of a disk drive is reported even though the drive was not physically hot-plugged.
-
Flash-based cache modules caused a controller failure at POST, displaying one of the following error messages:
· 1783-Slot # Drive Array Controller Failure
· 1719-Slot [x] Drive Array - A controller failure event occurred prior to this power-up (previous lock-up code = 0x11) [or other lock-up codes] (RESUME = "F1" KEY)
-
The release of HP Smart Array firmware version 3.52 caused a regression in rebuild performance while in Zero Memory Raid mode.
-
A Smart Array P812 controller attached to multiple MSA 60 storage systems may encounter a lockup condition (lockup code 0XAB) during heavy I/O workload.
-
Fixed a BIOS interaction issue that causes a system reset or hang after entering the Online Raid Configuration Utility on the HP DL165 G7 and the HP DL170e G6.
]]>
修正された問題点:
以下の問題が解決されました。
· 1783-Slot # Drive Array Controller Failure
· 1719-Slot [x] Drive Array - A controller failure event occurred prior to this power-up (previous lock-up code = 0x11) [or other lock-up codes] (RESUME = "F1" KEY)
-
HP Smartアレイファームウェアバージョン3.52のリリースは、Zero Memory Raidモードの間、再構築のパフォーマンスの劣化を引き起こします。
-
複数のMSA60 Storage Systemに接続されたSmartアレイP812コントローラーが、I/O負荷が高い間、ロックアップ状態(ロックアップコード 0xAB)になる場合があります。
-
HP DL165 G7およびHP DL170e G6でOnline Raid Configuration Utilityを実行するとシステムリセットまたはハングアップとなるBIOS インタラクションの問題を修正しました。
]]>
해결된 문제:
다음과 같은 문제가 해결되었습니다.
· 1783-Slot # Drive Array Controller Failure(1783-슬롯 # 드라이브 어레이 컨트롤러 오류)
· 1719-Slot [x] Drive Array - A controller failure event occurred prior to this power-up (previous lock-up code = 0x11) [or other lock-up codes] (RESUME = "F1" KEY)(1719-슬롯 [x] 드라이브 어레이 - 이 시동 전에 컨트롤러 오류가 발생했습니다. (이전 록업 코드 = 0x11) [또는 다른 록업 코드] (다시 시작 = "F1" 키))
- HP 스마트 어레이 펌웨어 버전 3.52 릴리스는 제로 메모리 Raid 모드 상태의 재구축 성능을 저하시켰습니다.
- 과도한 I/O 작업 부하 중에 다중 MSA 60 스토리지 시스템에 연결된 스마트 어레이 P812 컨트롤러에서 록업 조건(록업 코드 0XAB)이 발생할 수 있습니다.
- HP DL165 G7 및 HP DL170e G6에서 온라인 Raid 구성 유틸리티를 시작한 후 시스템 리셋이나 중단의 원인이 되는 BIOS 상호 작용 문제를 해결하였습니다.
]]>
Problems Fixed:
Resolved the following issues:
-
An issue resulting in a server hang during the boot process when a Smart Array controller is configured without a cache module.
-
An issue that prevented a successful server PXE boot.
-
An issue that resulted in never completing an IO request after outstanding read and write requests overlapped the same block range. This issue can potentially cause controller hang with no lockup code as a result.
-
An apparent hot-swap of a disk drive is reported even though the drive was not physically hot-plugged.
-
Flash-based cache modules caused a controller failure at POST, displaying one of the following error messages:
· 1783-Slot # Drive Array Controller Failure
· 1719-Slot [x] Drive Array - A controller failure event occurred prior to this power-up (previous lock-up code = 0x11) [or other lock-up codes] (RESUME = "F1" KEY)
-
The release of HP Smart Array firmware version 3.52 caused a regression in rebuild performance while in Zero Memory Raid mode.
-
A Smart Array P812 controller attached to multiple MSA 60 storage systems may encounter a lockup condition (lockup code 0XAB) during heavy I/O workload.
-
Fixed a BIOS interaction issue that causes a system reset or hang after entering the Online Raid Configuration Utility on the HP DL165 G7 and the HP DL170e G6.
]]>
增强功能/新功能:
增加了对以下功能的支持:
- 大小超过 2.2 TB 的 HDD
- 连接到 HP D2200sb 存储刀片的 SATA 固态驱动器 (SSD)
- 用于选定单级单元 (SLC) 和多级单元 (MLC) SSD 的 HP Smart SSD Gas Gauge
]]>
Enhancements/New Features:
Added support for the following features:
- HDDs that exceed 2.2 TB in size
- SATA Solid State Drives (SSD) connected to the HP D2200sb Storage Blade
- HP Smart SSD Gas Gauge for select Single Level Cell (SLC) and Multi-Level Cell (MLC) SSD's
]]>
Enhancements/New Features:
Added support for the following features:
- HDDs that exceed 2.2 TB in size
- SATA Solid State Drives (SSD) connected to the HP D2200sb Storage Blade
- HP Smart SSD Gas Gauge for select Single Level Cell (SLC) and Multi-Level Cell (MLC) SSD's
]]>
Enhancements/New Features:
Added support for the following features:
- HDDs that exceed 2.2 TB in size
- SATA Solid State Drives (SSD) connected to the HP D2200sb Storage Blade
- HP Smart SSD Gas Gauge for select Single Level Cell (SLC) and Multi-Level Cell (MLC) SSD's
]]>
Enhancements/New Features:
Added support for the following features:
- HDDs that exceed 2.2 TB in size
- SATA Solid State Drives (SSD) connected to the HP D2200sb Storage Blade
- HP Smart SSD Gas Gauge for select Single Level Cell (SLC) and Multi-Level Cell (MLC) SSD's
]]>
Enhancements/New Features:
Added support for the following features:
- HDDs that exceed 2.2 TB in size
- SATA Solid State Drives (SSD) connected to the HP D2200sb Storage Blade
- HP Smart SSD Gas Gauge for select Single Level Cell (SLC) and Multi-Level Cell (MLC) SSD's
]]>
改善点/新しい機能:
以下の機能のサポートを追加しました。
- 2.2TBを超えるHDD
- HP D2200sb Storage Bladeに接続されたSATA Solid State Drive(SSD)
- Single Level Cell(SLC)およびMulti-Level Cell(MLC)SSDを選択するためのHP Smart SSD Gas Gauge
]]>
개선 사항/새로운 기능:
다음 기능에 대한 지원이 추가되었습니다:
- 크기가 2.2TB를 초과하는 HDD
- HP D2200sb 스토리지 블레이드에 연결된 SATA 솔리드 스테이트 드라이브(SSD)
- SLC(Single Level Cell) 및 MLC(Multi-Level Cell) SSD 선택을 위한 HP Smart SSD 가스 게이지
]]>
增強或新增功能:
已新增對下列功能的支援:
- 大小超過 2.2 TB 的 HDD
- 連接至 HP D2200sb 刀鋒型儲存裝置的 SATA 固態磁碟機 (SSD)
- 用於選擇 Single Level Cell (SLC) 與 Multi-Level Cell (MLC) SSD 的 HP Smart SSD Gas Gauge
]]>
修复的问题:
解决了以下问题:
· 1783-Slot # Drive Array Controller Failure
· 1719-Slot [x] Drive Array - A controller failure event occurred prior to this power-up (previous lock-up code = 0x11) [or other lock-up codes] (RESUME = "F1" KEY)
- HP Smart Array 固件版本 3.52 的发布导致了零内存 RAID 模式下重建性能的回归。
- Smart Array P812 控制器连接至多个 MSA 60 存储系统后,可能会在处理大量 I/O 工作负载时遇到锁定情况(锁定代码 0XAB)。
已知问题:
- HP Smart Array 固件 5.06 版不应安装在 HP DL165 G7 上,因为 BIOS 会产生干扰问题,从而导致进入 Online Raid Configuration Utility 之后系统重置或停止响应。为修复此问题而开发的最新 BIOS 将于 2011 年 9 月发布。使用 HP DL165 G7 服务器的客户仍然继续使用 HP Smart Array 固件版本 3.66。
]]>
Problems Fixed:
Resolved the following issues:
- An issue resulting in a server hang during the boot process when a Smart Array controller is configured without a cache module.
- An issue that prevented a successful server PXE boot.
- An issue that resulted in never completing an IO request after outstanding read and write requests overlapped the same block range. This issue can potentially cause controller hang with no lockup code as a result.
-
An apparent hot-swap of a disk drive is reported even though the drive was not physically hot-plugged.
-
Flash-based cache modules caused a controller failure at POST, displaying one of the following error messages:
· 1783-Slot # Drive Array Controller Failure
· 1719-Slot [x] Drive Array - A controller failure event occurred prior to this power-up (previous lock-up code = 0x11) [or other lock-up codes] (RESUME = "F1" KEY)
- The release of HP Smart Array firmware version 3.52 caused a regression in rebuild performance while in Zero Memory Raid mode.
- A Smart Array P812 controller attached to multiple MSA 60 storage systems may encounter a lockup condition (lockup code 0XAB) during heavy I/O workload.
Known Issues:
- HP Smart Array FW version 5.06 should not be installed on the HP DL165 G7 due to a BIOS interaction issue that causes a system reset or hang after entering the Online Raid Configuration Utility. A new BIOS to fix this issue is scheduled to be released September of 2011. Customers with the HP DL165 G7 server should remain at HP Smart Array FW version 3.66.
]]>
Problems Fixed:
Resolved the following issues:
- An issue resulting in a server hang during the boot process when a Smart Array controller is configured without a cache module.
- An issue that prevented a successful server PXE boot.
- An issue that resulted in never completing an IO request after outstanding read and write requests overlapped the same block range. This issue can potentially cause controller hang with no lockup code as a result.
-
An apparent hot-swap of a disk drive is reported even though the drive was not physically hot-plugged.
-
Flash-based cache modules caused a controller failure at POST, displaying one of the following error messages:
· 1783-Slot # Drive Array Controller Failure
· 1719-Slot [x] Drive Array - A controller failure event occurred prior to this power-up (previous lock-up code = 0x11) [or other lock-up codes] (RESUME = "F1" KEY)
- The release of HP Smart Array firmware version 3.52 caused a regression in rebuild performance while in Zero Memory Raid mode.
- A Smart Array P812 controller attached to multiple MSA 60 storage systems may encounter a lockup condition (lockup code 0XAB) during heavy I/O workload.
Known Issues:
- HP Smart Array FW version 5.06 should not be installed on the HP DL165 G7 due to a BIOS interaction issue that causes a system reset or hang after entering the Online Raid Configuration Utility. A new BIOS to fix this issue is scheduled to be released September of 2011. Customers with the HP DL165 G7 server should remain at HP Smart Array FW version 3.66.
]]>
Problems Fixed:
Resolved the following issues:
- An issue resulting in a server hang during the boot process when a Smart Array controller is configured without a cache module.
- An issue that prevented a successful server PXE boot.
- An issue that resulted in never completing an IO request after outstanding read and write requests overlapped the same block range. This issue can potentially cause controller hang with no lockup code as a result.
-
An apparent hot-swap of a disk drive is reported even though the drive was not physically hot-plugged.
-
Flash-based cache modules caused a controller failure at POST, displaying one of the following error messages:
· 1783-Slot # Drive Array Controller Failure
· 1719-Slot [x] Drive Array - A controller failure event occurred prior to this power-up (previous lock-up code = 0x11) [or other lock-up codes] (RESUME = "F1" KEY)
- The release of HP Smart Array firmware version 3.52 caused a regression in rebuild performance while in Zero Memory Raid mode.
- A Smart Array P812 controller attached to multiple MSA 60 storage systems may encounter a lockup condition (lockup code 0XAB) during heavy I/O workload.
Known Issues:
- HP Smart Array FW version 5.06 should not be installed on the HP DL165 G7 due to a BIOS interaction issue that causes a system reset or hang after entering the Online Raid Configuration Utility. A new BIOS to fix this issue is scheduled to be released September of 2011. Customers with the HP DL165 G7 server should remain at HP Smart Array FW version 3.66.
]]>
Problems Fixed:
Resolved the following issues:
- An issue resulting in a server hang during the boot process when a Smart Array controller is configured without a cache module.
- An issue that prevented a successful server PXE boot.
- An issue that resulted in never completing an IO request after outstanding read and write requests overlapped the same block range. This issue can potentially cause controller hang with no lockup code as a result.
-
An apparent hot-swap of a disk drive is reported even though the drive was not physically hot-plugged.
-
Flash-based cache modules caused a controller failure at POST, displaying one of the following error messages:
· 1783-Slot # Drive Array Controller Failure
· 1719-Slot [x] Drive Array - A controller failure event occurred prior to this power-up (previous lock-up code = 0x11) [or other lock-up codes] (RESUME = "F1" KEY)
- The release of HP Smart Array firmware version 3.52 caused a regression in rebuild performance while in Zero Memory Raid mode.
- A Smart Array P812 controller attached to multiple MSA 60 storage systems may encounter a lockup condition (lockup code 0XAB) during heavy I/O workload.
Known Issues:
- HP Smart Array FW version 5.06 should not be installed on the HP DL165 G7 due to a BIOS interaction issue that causes a system reset or hang after entering the Online Raid Configuration Utility. A new BIOS to fix this issue is scheduled to be released September of 2011. Customers with the HP DL165 G7 server should remain at HP Smart Array FW version 3.66.
]]>
Problems Fixed:
Resolved the following issues:
- An issue resulting in a server hang during the boot process when a Smart Array controller is configured without a cache module.
- An issue that prevented a successful server PXE boot.
- An issue that resulted in never completing an IO request after outstanding read and write requests overlapped the same block range. This issue can potentially cause controller hang with no lockup code as a result.
-
An apparent hot-swap of a disk drive is reported even though the drive was not physically hot-plugged.
-
Flash-based cache modules caused a controller failure at POST, displaying one of the following error messages:
· 1783-Slot # Drive Array Controller Failure
· 1719-Slot [x] Drive Array - A controller failure event occurred prior to this power-up (previous lock-up code = 0x11) [or other lock-up codes] (RESUME = "F1" KEY)
- The release of HP Smart Array firmware version 3.52 caused a regression in rebuild performance while in Zero Memory Raid mode.
- A Smart Array P812 controller attached to multiple MSA 60 storage systems may encounter a lockup condition (lockup code 0XAB) during heavy I/O workload.
Known Issues:
- HP Smart Array FW version 5.06 should not be installed on the HP DL165 G7 due to a BIOS interaction issue that causes a system reset or hang after entering the Online Raid Configuration Utility. A new BIOS to fix this issue is scheduled to be released September of 2011. Customers with the HP DL165 G7 server should remain at HP Smart Array FW version 3.66.
]]>
修正された問題点:
以下の問題が解決されました。
■ 1783-Slot # Drive Array Controller Failure
■ 1719-Slot [x] Drive Array - A controller failure event occurred prior to this power-up (previous lock-up code = 0x11) [or other lock-up codes] (RESUME = "F1" KEY)
- HP Smartアレイファームウェアバージョン3.52のリリースは、Zero Memory Raidモードの間、再構築のパフォーマンスの劣化を引き起こします。
- 複数のMSA60 Storage Systemに接続されたSmartアレイP812コントローラーが、I/O負荷が高い間、ロックアップ状態(ロックアップコード 0xAB)になる場合があります。
既知の問題点:
- Online Raid Configuration Utilityに入った後、システムのリセットまたはハングアップを引き起こすBIOSの相互作用の問題のために、HP Smartアレイファームウェアバージョン5.06は、HP DL165 G7にインストールしないでください。 この問題を修正するために新しいBIOSは、2011年9月にリリースが予定されています。 HP DL165 G7サーバーは、HP Smartアレイファームウェアバージョン3.66のままにしておいてください。
]]>
해결된 문제:
다음과 같은 문제가 해결되었습니다.
· 1783-Slot # Drive Array Controller Failure(1783-슬롯 # 드라이브 어레이 컨트롤러 오류)
· 1719-Slot [x] Drive Array - A controller failure event occurred prior to this power-up (previous lock-up code = 0x11) [or other lock-up codes] (RESUME = "F1" KEY)(1719-슬롯 [x] 드라이브 어레이 - 이 시동 전에 컨트롤러 오류가 발생했습니다. (이전 록업 코드 = 0x11) [또는 다른 록업 코드] (다시 시작 = "F1" 키))
- HP 스마트 어레이 펌웨어 버전 3.52 릴리스는 제로 메모리 Raid 모드 상태의 재구축 성능을 저하시켰습니다.
- 과도한 I/O 작업 부하 중에 다중 MSA 60 스토리지 시스템에 연결된 스마트 어레이 P812 컨트롤러에서 록업 조건(록업 코드 0XAB)이 발생할 수 있습니다.
알려진 문제:
- HP DL165 G7에 HP 스마트 어레이 FW 버전 5.06을 설치해서는 안 됩니다. 이 버전을 설치할 경우 온라인 Raid 구성 유틸리티를 시작하면 시스템이 다시 설정되거나 중단되는 BIOS 상호 작용 문제가 발생할 수 있습니다. 이 문제를 해결하기 위한 새 BIOS는 2011년 9월에 릴리스될 예정입니다. HP DL165 G7 서버를 사용하는 고객은 HP 스마트 어레이 FW 버전 3.66을 계속 유지해야 합니다.
]]>
修正的問題:
已解決下列問題:
· 1783-Slot # Drive Array Controller Failure(1783-插槽編號磁碟機控制器故障)
· 1719-Slot [x] Drive Array - A controller failure event occurred prior to this power-up (previous lock-up code = 0x11) [or other lock-up codes] (RESUME = "F1" KEY)(1719-插槽 [x] 磁碟機陣列 -在此次開啟電源之前,發生控制器故障事件(先前鎖定代碼 = 0x11)[或其他鎖定代碼](繼續 =「F1」鍵))
- HP Smart Array 韌體版本 3.52 的發行在零記憶體 RAID 模式中造成重建效能退化。
- 連接至多套 MSA 60 儲存系統的 Smart Array P812 控制器在繁重的 I/O 工作負載期間可能發生鎖定狀況(鎖定代碼 0XAB)。
已知問題:
- HP Smart Array 韌體版本 5.06 不應安裝於 HP DL165 G7 上,因為一項 BIOS 互動 問題會在進入 Online Raid Configuration Utility 之後,造成系統重設或當機。解決此問題的新 BIOS 預計在 2011 年 9 月發佈。HP DL165 G7 伺服器的客戶應繼續使用 HP Smart Array FW 版本 3.66。
]]>
增强功能/新功能:
- 增加了对 HP Smart Array P711m 的支持
- HP Smart Array P712m 上已启用的外部端口使控制器上只需安装 256MB 缓存。
- 增加了对 HP 6Gb SAS BL Switch 的支持
- 增加了对 HP StorageWorks P2000 G3 MSA 的支持
]]>
Enhancements/New Features:
- Added support for the HP Smart Array P711m
- Enabled external ports on HP Smart Array P712m with a minimum of 256MB cache installed on the controller.
- Added support for HP 6Gb SAS BL Switch
- Added support for HP StorageWorks P2000 G3 MSA
]]>
Enhancements/New Features:
- Added support for the HP Smart Array P711m
- Enabled external ports on HP Smart Array P712m with a minimum of 256MB cache installed on the controller.
- Added support for HP 6Gb SAS BL Switch
- Added support for HP StorageWorks P2000 G3 MSA
]]>
Enhancements/New Features:
- Added support for the HP Smart Array P711m
- Enabled external ports on HP Smart Array P712m with a minimum of 256MB cache installed on the controller.
- Added support for HP 6Gb SAS BL Switch
- Added support for HP StorageWorks P2000 G3 MSA
]]>
Enhancements/New Features:
- Added support for the HP Smart Array P711m
- Enabled external ports on HP Smart Array P712m with a minimum of 256MB cache installed on the controller.
- Added support for HP 6Gb SAS BL Switch
- Added support for HP StorageWorks P2000 G3 MSA
]]>
Enhancements/New Features:
- Added support for the HP Smart Array P711m
- Enabled external ports on HP Smart Array P712m with a minimum of 256MB cache installed on the controller.
- Added support for HP 6Gb SAS BL Switch
- Added support for HP StorageWorks P2000 G3 MSA
]]>
改善点/新しい機能:
- HP SmartアレイP711mのサポートを追加しました。
- コントローラーに最低256MBのキャッシュを搭載したHP SmartアレイP712mの外部ポートを有効にしました。
- HP 6Gb SAS BLスイッチ用のサポートを追加しました。
- HP StorageWorks P2000 G3 MSA のサポートを追加しました。
]]>
개선 사항/새로운 기능:
- HP 스마트 어레이 P711m에 대한 지원이 추가되었습니다.
- 컨트롤러에 256MB 이상의 캐시가 설치되어 있는 HP 스마트 어레이 P712m의 외부 포트가 활성화되었습니다.
- HP 6Gb SAS BL 스위치에 대한 지원이 추가되었습니다.
- HP StorageWorks P2000 G3 MSA에 대한 지원이 추가되었습니다.
]]>
增強或新增功能:
- 已新增對 HP Smart Array P711m 的支援
- 已在 HP Smart Array P712m(控制器上至少安裝 256MB 的快取)上啟用外部連接埠。
- 已新增對 HP 6Gb SAS BL 交換機的支援
- 已新增對 HP StorageWorks P2000 G3 MSA 的支援
]]>
Enhancements/New Features:
- Added support for the HP Smart Array P711m
- Enabled external ports on HP Smart Array P712m with a minimum of 256MB cache installed on the controller.
- Added support for HP 6Gb SAS BL Switch
- Added support for HP StorageWorks P2000 G3 MSA
]]>
Enhancements/New Features:
- Added support for the HP Smart Array P711m
- Enabled external ports on HP Smart Array P712m with a minimum of 256MB cache installed on the controller.
- Added support for HP 6Gb SAS BL Switch
- Added support for HP StorageWorks P2000 G3 MSA
]]>
Enhancements/New Features:
- Added support for the HP Smart Array P711m
- Enabled external ports on HP Smart Array P712m with a minimum of 256MB cache installed on the controller.
- Added support for HP 6Gb SAS BL Switch
- Added support for HP StorageWorks P2000 G3 MSA
]]>
Enhancements/New Features:
- Added support for the HP Smart Array P711m
- Enabled external ports on HP Smart Array P712m with a minimum of 256MB cache installed on the controller.
- Added support for HP 6Gb SAS BL Switch
- Added support for HP StorageWorks P2000 G3 MSA
]]>
Enhancements/New Features:
- Added support for the HP Smart Array P711m
- Enabled external ports on HP Smart Array P712m with a minimum of 256MB cache installed on the controller.
- Added support for HP 6Gb SAS BL Switch
- Added support for HP StorageWorks P2000 G3 MSA
]]>
Enhancements/New Features:
- Added support for the HP Smart Array P711m
- Enabled external ports on HP Smart Array P712m with a minimum of 256MB cache installed on the controller.
- Added support for HP 6Gb SAS BL Switch
- Added support for HP StorageWorks P2000 G3 MSA
]]>
改善点/新しい機能:
- HP SmartアレイP711mのサポートを追加しました。
- コントローラーに最低256MBのキャッシュを搭載したHP SmartアレイP712mの外部ポートを有効にしました。
- HP 6Gb SAS BLスイッチ用のサポートを追加しました。
- HP StorageWorks P2000 G3 MSA のサポートを追加しました。
]]>
Enhancements/New Features:
- Added support for the HP Smart Array P711m
- Enabled external ports on HP Smart Array P712m with a minimum of 256MB cache installed on the controller.
- Added support for HP 6Gb SAS BL Switch
- Added support for HP StorageWorks P2000 G3 MSA
]]>
Enhancements/New Features:
- Added support for the HP Smart Array P711m
- Enabled external ports on HP Smart Array P712m with a minimum of 256MB cache installed on the controller.
- Added support for HP 6Gb SAS BL Switch
- Added support for HP StorageWorks P2000 G3 MSA
]]>
Enhancements/New Features:
- Added support for HP SATA SSD's connected to the HP StorageWorks D2600 and the HP StorageWorks D2700.
]]>
Enhancements/New Features:
- Added support for HP SATA SSD's connected to the HP StorageWorks D2600 and the HP StorageWorks D2700.
]]>
Enhancements/New Features:
- Added support for HP SATA SSD's connected to the HP StorageWorks D2600 and the HP StorageWorks D2700.
]]>
Enhancements/New Features:
- Added support for HP SATA SSD's connected to the HP StorageWorks D2600 and the HP StorageWorks D2700.
]]>
Enhancements/New Features:
- Added support for HP SATA SSD's connected to the HP StorageWorks D2600 and the HP StorageWorks D2700.
]]>
Enhancements/New Features:
- Added support for HP SATA SSD's connected to the HP StorageWorks D2600 and the HP StorageWorks D2700.
]]>
改善点/新しい機能:
- HP StorageWorks D2600およびHP StorageWorks D2700に接続されたHP SATA SSDのサポートを追加しました。
]]>
Enhancements/New Features:
- Added support for HP SATA SSD's connected to the HP StorageWorks D2600 and the HP StorageWorks D2700.
]]>
Enhancements/New Features:
- Added support for HP SATA SSD's connected to the HP StorageWorks D2600 and the HP StorageWorks D2700.
]]>
固件依赖条件:
希望支持与 HP StorageWorks 600 Modular Disk System (MDS600) 连接的 HP Smart Array P812 的客户必须确认硬件满足以下最低固件版本(或更高版本)。
- 将 MDS600 连接至 HP Smart Array P812 之前,必须先将 HP Smart Array P812 更新至固件版本 3.50 或更高版本。
- 将 HP Smart Array P812 固件更新至 3.50 或更高版本后, 请执行以下步骤将 MDS600 与 HP Smart Array P812 控制器连接并开始运行 MSD600。
- 若 MDS600 的固件版本为 2.60,则可以连接至 HP Smart Array P812 控制器。
- 然而,运行与 HP Smart Array P812 连接的 MDS600,必须先将后者固件升级至版本 2.66。
- 若 MDS600 运行的固件版本为 2.54,则必须将其连接至以下智能阵列控制器并将固件版本升级至版本 2.66:
- 智能阵列 P700m 控制器
- 智能阵列 P411 控制器
- 智能阵列 P212 控制器
注释: 通过备选控制器方式将 MDS600 固件升级至版本 2.66 后,则可将 MDS600 与固件版本为 3.50 的 HP Smart Array P812 连接并开始运行。
如欲了解更多信息,请参考以下网址的客户顾问文档:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02437391
如需支持 HP StorageWorks D2000 机柜的双域功能,则 D2000 必须安装固件版本 0067 或更高版本。
存储子系统(例如,磁盘、控制器和服务器背板)的组件应以相同的数据传输速率或者系统带宽运行,并可向下浏览至素有组件的可接受层级。
连接至 HP Smart Array P410 或者 HP Smart Array P410i 的 HP SAS Expander Card 要求使用 SAS Expander Card 固件版本 2.06 或者更改版本以支持 6Gb SAS 和 3Gb SATA 驱动器。
运行 VMware ESX/ESXi 时,仅固件维护光盘中的 HP Smart Update Manager 才支持离线更新功能。
修复的问题:
- 对 HP 智能阵列硬盘驱动器进行热更换之后,其所在的扩展卡上连接的所有驱动器均报告位于仓位 0。此问题发生在 HP StorageWorks MSA60、HP StorageWorks MSA70 以及配备 12 仓位和 25 仓位背板的 HP ProLiant DL180 G6 上。
- 备用驱动器连接到 HP ProLiant ML150 G6 服务器上的非热插拔背板时没有加速转动。
- 电池供电写高速缓存 (BBWC) 处于耗尽状态时没有显示“无数据丢失”开机自检消息。电池耗尽时不当地永久禁用了 BBWC。
- 解决了智能阵列与导致智能阵列锁定的卡巴斯基反病毒工具之间的不兼容性问题。
- 修改了存储器接口参数,以便修复导致使用闪存支持的写高速缓存 (FBWC) 时控制器锁定的问题。
]]>
Firmware Dependency:
Customers who wish to support the HP Smart Array P812 connected to the HP StorageWorks 600 Modular Disk System (MDS600) must ensure that the hardware is at the minimum firmware versions (or later) as defined below.
- Before connecting the MDS600 to the HP Smart Array P812, you must first flash the HP Smart Array P812 to firmware version 3.50 or greater.
- After the HP Smart Array P812 firmware is flashed to 3.50 or greater, then the following steps need to be followed to connect the MDS600 with the HP Smart Array P812 controller and begin operating the MSD600.
- If the MDS600 has version 2.60 firmware, then it can be connected to the HP Smart Array P812 controller.
- However, to operate the MDS600 connected to HP Smart Array P812, the MDS600 must be upgraded to firmware version 2.66.
- If an MDS600 is running firmware version 2.54, it must be attached to one of the following Smart Array Controllers to perform the upgrade to firmware version 2.66:
- Smart Array P700m Controller
- Smart Array P411 Controller
- Smart Array P212 Controller
NOTE: Once the MDS600 firmware is upgraded to 2.66 using this alternate controller method, then the MDS600 can be connected to the HP Smart Array P812, which has firmware version 3.50, and begin operation.
For additional information, reference the Customer Advisory available at the following URL:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02437391
To support Dual Domain on HP StorageWorks D2000 enclosures, the D2000 must be at a minimum firmware version of 0067 or later.
The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card firmware version 2.06 or higher, to support 6Gb SAS and 3Gb SATA drives.
When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD.
Problems Fixed:
- After hot-replacement of an HP Smart Array HDD, all drives, which were attached to the expander where the HDD was replaced, report as being in Bay 0. Issue occurs on the HP StorageWorks MSA60, HP StorageWorks MSA70, and HP ProLiant DL180 G6 with 12 bay and 25 bay backplanes.
- Spare drives were not spinning up when attached to a non-hot plug backplane on the HP ProLiant ML150 G6 server.
- A No-Data Loss post message was not being displayed when the Battery Backed Write Cache (BBWC) was in a depleted state. The BBWC was improperly disabled permanently when the battery became depleted.
- Resolved an incompatibility between Smart Array and the Kaspersky Anti-Virus tool that resulted in a Smart Array lockup.
- Modified memory interface parameters to fix an issue resulting in controller lock-ups when utilizing a Flash-Backed Write Cache (FBWC).
]]>
Firmware Dependency:
Customers who wish to support the HP Smart Array P812 connected to the HP StorageWorks 600 Modular Disk System (MDS600) must ensure that the hardware is at the minimum firmware versions (or later) as defined below.
- Before connecting the MDS600 to the HP Smart Array P812, you must first flash the HP Smart Array P812 to firmware version 3.50 or greater.
- After the HP Smart Array P812 firmware is flashed to 3.50 or greater, then the following steps need to be followed to connect the MDS600 with the HP Smart Array P812 controller and begin operating the MSD600.
- If the MDS600 has version 2.60 firmware, then it can be connected to the HP Smart Array P812 controller.
- However, to operate the MDS600 connected to HP Smart Array P812, the MDS600 must be upgraded to firmware version 2.66.
- If an MDS600 is running firmware version 2.54, it must be attached to one of the following Smart Array Controllers to perform the upgrade to firmware version 2.66:
- Smart Array P700m Controller
- Smart Array P411 Controller
- Smart Array P212 Controller
NOTE: Once the MDS600 firmware is upgraded to 2.66 using this alternate controller method, then the MDS600 can be connected to the HP Smart Array P812, which has firmware version 3.50, and begin operation.
For additional information, reference the Customer Advisory available at the following URL:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02437391
To support Dual Domain on HP StorageWorks D2000 enclosures, the D2000 must be at a minimum firmware version of 0067 or later.
The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card firmware version 2.06 or higher, to support 6Gb SAS and 3Gb SATA drives.
When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD.
Problems Fixed:
- After hot-replacement of an HP Smart Array HDD, all drives, which were attached to the expander where the HDD was replaced, report as being in Bay 0. Issue occurs on the HP StorageWorks MSA60, HP StorageWorks MSA70, and HP ProLiant DL180 G6 with 12 bay and 25 bay backplanes.
- Spare drives were not spinning up when attached to a non-hot plug backplane on the HP ProLiant ML150 G6 server.
- A No-Data Loss post message was not being displayed when the Battery Backed Write Cache (BBWC) was in a depleted state. The BBWC was improperly disabled permanently when the battery became depleted.
- Resolved an incompatibility between Smart Array and the Kaspersky Anti-Virus tool that resulted in a Smart Array lockup.
- Modified memory interface parameters to fix an issue resulting in controller lock-ups when utilizing a Flash-Backed Write Cache (FBWC).
]]>
Firmware Dependency:
Customers who wish to support the HP Smart Array P812 connected to the HP StorageWorks 600 Modular Disk System (MDS600) must ensure that the hardware is at the minimum firmware versions (or later) as defined below.
- Before connecting the MDS600 to the HP Smart Array P812, you must first flash the HP Smart Array P812 to firmware version 3.50 or greater.
- After the HP Smart Array P812 firmware is flashed to 3.50 or greater, then the following steps need to be followed to connect the MDS600 with the HP Smart Array P812 controller and begin operating the MSD600.
- If the MDS600 has version 2.60 firmware, then it can be connected to the HP Smart Array P812 controller.
- However, to operate the MDS600 connected to HP Smart Array P812, the MDS600 must be upgraded to firmware version 2.66.
- If an MDS600 is running firmware version 2.54, it must be attached to one of the following Smart Array Controllers to perform the upgrade to firmware version 2.66:
- Smart Array P700m Controller
- Smart Array P411 Controller
- Smart Array P212 Controller
NOTE: Once the MDS600 firmware is upgraded to 2.66 using this alternate controller method, then the MDS600 can be connected to the HP Smart Array P812, which has firmware version 3.50, and begin operation.
For additional information, reference the Customer Advisory available at the following URL:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02437391
To support Dual Domain on HP StorageWorks D2000 enclosures, the D2000 must be at a minimum firmware version of 0067 or later.
The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card firmware version 2.06 or higher, to support 6Gb SAS and 3Gb SATA drives.
When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD.
Problems Fixed:
- After hot-replacement of an HP Smart Array HDD, all drives, which were attached to the expander where the HDD was replaced, report as being in Bay 0. Issue occurs on the HP StorageWorks MSA60, HP StorageWorks MSA70, and HP ProLiant DL180 G6 with 12 bay and 25 bay backplanes.
- Spare drives were not spinning up when attached to a non-hot plug backplane on the HP ProLiant ML150 G6 server.
- A No-Data Loss post message was not being displayed when the Battery Backed Write Cache (BBWC) was in a depleted state. The BBWC was improperly disabled permanently when the battery became depleted.
- Resolved an incompatibility between Smart Array and the Kaspersky Anti-Virus tool that resulted in a Smart Array lockup.
- Modified memory interface parameters to fix an issue resulting in controller lock-ups when utilizing a Flash-Backed Write Cache (FBWC).
]]>
Firmware Dependency:
Customers who wish to support the HP Smart Array P812 connected to the HP StorageWorks 600 Modular Disk System (MDS600) must ensure that the hardware is at the minimum firmware versions (or later) as defined below.
- Before connecting the MDS600 to the HP Smart Array P812, you must first flash the HP Smart Array P812 to firmware version 3.50 or greater.
- After the HP Smart Array P812 firmware is flashed to 3.50 or greater, then the following steps need to be followed to connect the MDS600 with the HP Smart Array P812 controller and begin operating the MSD600.
- If the MDS600 has version 2.60 firmware, then it can be connected to the HP Smart Array P812 controller.
- However, to operate the MDS600 connected to HP Smart Array P812, the MDS600 must be upgraded to firmware version 2.66.
- If an MDS600 is running firmware version 2.54, it must be attached to one of the following Smart Array Controllers to perform the upgrade to firmware version 2.66:
- Smart Array P700m Controller
- Smart Array P411 Controller
- Smart Array P212 Controller
NOTE: Once the MDS600 firmware is upgraded to 2.66 using this alternate controller method, then the MDS600 can be connected to the HP Smart Array P812, which has firmware version 3.50, and begin operation.
For additional information, reference the Customer Advisory available at the following URL:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02437391
To support Dual Domain on HP StorageWorks D2000 enclosures, the D2000 must be at a minimum firmware version of 0067 or later.
The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card firmware version 2.06 or higher, to support 6Gb SAS and 3Gb SATA drives.
When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD.
Problems Fixed:
- After hot-replacement of an HP Smart Array HDD, all drives, which were attached to the expander where the HDD was replaced, report as being in Bay 0. Issue occurs on the HP StorageWorks MSA60, HP StorageWorks MSA70, and HP ProLiant DL180 G6 with 12 bay and 25 bay backplanes.
- Spare drives were not spinning up when attached to a non-hot plug backplane on the HP ProLiant ML150 G6 server.
- A No-Data Loss post message was not being displayed when the Battery Backed Write Cache (BBWC) was in a depleted state. The BBWC was improperly disabled permanently when the battery became depleted.
- Resolved an incompatibility between Smart Array and the Kaspersky Anti-Virus tool that resulted in a Smart Array lockup.
- Modified memory interface parameters to fix an issue resulting in controller lock-ups when utilizing a Flash-Backed Write Cache (FBWC).
]]>
Firmware Dependency:
Customers who wish to support the HP Smart Array P812 connected to the HP StorageWorks 600 Modular Disk System (MDS600) must ensure that the hardware is at the minimum firmware versions (or later) as defined below.
- Before connecting the MDS600 to the HP Smart Array P812, you must first flash the HP Smart Array P812 to firmware version 3.50 or greater.
- After the HP Smart Array P812 firmware is flashed to 3.50 or greater, then the following steps need to be followed to connect the MDS600 with the HP Smart Array P812 controller and begin operating the MSD600.
- If the MDS600 has version 2.60 firmware, then it can be connected to the HP Smart Array P812 controller.
- However, to operate the MDS600 connected to HP Smart Array P812, the MDS600 must be upgraded to firmware version 2.66.
- If an MDS600 is running firmware version 2.54, it must be attached to one of the following Smart Array Controllers to perform the upgrade to firmware version 2.66:
- Smart Array P700m Controller
- Smart Array P411 Controller
- Smart Array P212 Controller
NOTE: Once the MDS600 firmware is upgraded to 2.66 using this alternate controller method, then the MDS600 can be connected to the HP Smart Array P812, which has firmware version 3.50, and begin operation.
For additional information, reference the Customer Advisory available at the following URL:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02437391
To support Dual Domain on HP StorageWorks D2000 enclosures, the D2000 must be at a minimum firmware version of 0067 or later.
The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card firmware version 2.06 or higher, to support 6Gb SAS and 3Gb SATA drives.
When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD.
Problems Fixed:
- After hot-replacement of an HP Smart Array HDD, all drives, which were attached to the expander where the HDD was replaced, report as being in Bay 0. Issue occurs on the HP StorageWorks MSA60, HP StorageWorks MSA70, and HP ProLiant DL180 G6 with 12 bay and 25 bay backplanes.
- Spare drives were not spinning up when attached to a non-hot plug backplane on the HP ProLiant ML150 G6 server.
- A No-Data Loss post message was not being displayed when the Battery Backed Write Cache (BBWC) was in a depleted state. The BBWC was improperly disabled permanently when the battery became depleted.
- Resolved an incompatibility between Smart Array and the Kaspersky Anti-Virus tool that resulted in a Smart Array lockup.
- Modified memory interface parameters to fix an issue resulting in controller lock-ups when utilizing a Flash-Backed Write Cache (FBWC).
]]>
ファームウェアの関連性:
HP StorageWorks Modular Disk System 600(MDS600)に接続されたHP Smartアレイ P812のサポートが必要な場合、ハードウェアが以下のバージョン以降のファームウェアの最小要件を満たしている必要があります。
- MDS600をHP Smartアレイ P812に接続する前に、HP Smartアレイ P812のファームウェアをバージョン3.50以降にフラッシュする必要があります。
- HP Smartアレイ P812のファームウェアを3.50以降にフラッシュした後、MDS600をHP Smartアレイ P812コントローラーに接続して、MDS600の動作を開始するためには、以下の手順に従う必要があります。
- MDS600がバージョン2.60のファームウェアの場合、HP Smartアレイ P812コントローラーに接続することができます。
- しかし、HP Smartアレイ P812に接続したMDS600を動作させるためには、MDS600は、ファームウェア バージョン2.66へのアップグレードが必要です。
- MDS600がバージョン2.54のファームウェアの場合、ファームウェア バージョン2.66へのアップグレードを実行するために以下のSmartアレイ コントローラーの一つと接続する必要があります。
- Smartアレイ P700mコントローラー
- Smartアレイ P411コントローラー
- Smartアレイ P212コントローラー
注: このコントローラーの代替方法を使ってMDS600のファームウェアを2.66にアップデートが行われたら、MDS600をファームウェア バージョン3.50のHP Smartアレイ P812に接続して、動作を開始することができます。
詳しくは、以下のURLのCustomer Advisoryを参照してください。
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02437391(英語)
HP StorageWorks D2000エンクロージャーでデュアル ドメインをサポートするには、D2000のファームウェア バージョンを0067以降にする必要があります。
ストレージ サブシステムのコンポーネント(例、ドライブ、コントローラー、およびサーバー バックプレーン)は、同じデータ転送レートで動作しなければなりません。そうでない場合はシステム バンド幅はすべてのコンポーネントが受け入れ可能なレベルにネゴシエートされます。
HP Smartアレイ P410またはHP Smartアレイ P410iに接続されたHP SASエキスパンダー カードは、6Gb SASおよび3Gb SATAドライブをサポートするために、SASエキスパンダー カード ファームウェア バージョン2.06以降が必要です。
VMware ESX/ESXiを実行している場合、Firmware Maintenance CD上のHP Smart Update Managerを使用したオフライン アップデートのみサポートされます。
修正された問題点:
- 1台のHP SmartアレイHDDをホット リプレースした後、交換したHDDがあるエキスパンダーに接続されている全てのドライブは、ベイ0にあると報告されました。 HP StorageWorks MSA60、HP StorageWorks MSA70、および12ベイおよび25ベイのバックプレーンのHP ProLiant DL180 G6上で、この問題は発生します。
- HP ProLiant ML150 G6サーバーのノンホット プラグ バックプレーンに接続された場合、スペア ドライブはスピンアップしませんでした。
- バッテリ バックアップ付きライト キャッシュ(BBWC)が劣化した状態の場合、No-Data LossのPOSTメッセージが表示されませんでした。 バッテリが空になった場合、BBWCは間違って無効にされました。
- SmartアレイとSmartアレイをロックアップさせるKaspersky Anti-Virusツールとの間の互換性の問題を解決しました。
- フラッシュバック式ライトキャッシュ(FBWC)を利用した場合、コントローラーのロックアップを引き起こす問題を修正するために、メモリ インターフェイスのパラメーターを変更しました。
]]>
펌웨어 종속성:
HP StorageWorks 600 Modular Disk System (MDS600) 과 연결되어 있는 HP 스마트 어레이 P812의 지원을 원하는 고객들은 반드시 다음과 같은 최소한의 펌웨어 버전(또는 이상)이 하드웨어에 설치되어 있는지를 확인해야 합니다.
- MDS600을 HP 스마트 어레이 P812로 연결하기 전 HP 스마트 어레이 P812를 3.50 이상 펌웨어 버전으로 업데이트해야 합니다.
- HP 스마트 어레이 P812 펌웨어가 3.50 이상 버전으로 업데이트되면 HP 스마트 어레이 P812 컨트롤러에 MSD600을 연결한 다음 이를 실행하기 위해서는 다음 절차를 진행해야 합니다.
- MDS600에 펌웨어 2.60 버전이 설치되어 있는 경우 HP 스마트 어레이 P812 컨트롤러와 연결가능합니다.
- 하지만 HP 스마트 어레이 P812와 연결되어 있는 MDS600을 실행하려면 MDS600의 펌웨어를 2.66 이상 버전으로 업그레이드해야 합니다.
- MDS600에 펌웨어 2.54 버전이 설치되어 있는 경우 다음 중 하나의 스마트 어레이 컨트롤러에 장착되어 펌웨어 2.66 버전으로 업그레이드하여야 합니다:
- 스마트 어레이 P700m 컨트롤러
- 스마트 어레이 P411 컨트롤러
- 스마트 어레이 P212 컨트롤러
주: 해당 컨트롤러를 통해 MDS600 펌웨어를 2.66 버전으로 업그레이드하면 펌웨어 3.50 버전이 설치되어 있는 HP 스마트 어레이 P812로 MDS600을 연결하여 이를 실행할 수 있습니다.
자세한 정보는 다음 URL을 통해 제공되는 고객 권고사항을 참조하십시오:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02437391
HP StorageWorks D2000 인클로저에서 이중 도메인을 지원하려면 D2000에 0067 이상 버전의 펌웨어가 설치되어야 합니다.
스토리지 하위 시스템의 구성 요소들(예: 드라이버, 컨트롤러 및 서버 백플레인)이 동일한 데이터 전송 속도로 작동하거나 시스템 대역폭이 모든 구성 요소에 적용될 수 있도록 조정됩니다.
HP Smart Array P410 또는 HP Smart Array P410i에 연결되어 있는 HP SAS 익스팬더 카드는 6Gb SAS와 3Gb SATA 드라이브 지원을 위해 2.06 이상 버전의 SAS 익스팬더 카드 펌웨어를 필요로 하고 있습니다.
VMware ESX/ESXi 실행 시 펌웨어 유지관리 CD의 HP Smart Update Manager를 통해 업데이트하려는 경우 오프라인 업데이트만 지원됩니다.
해결된 문제:
- HP 스마트 어레이 HDD를 강제 교체하면 HDD가 교체된 익스팬더에 장착되어 있는 모든 드라이버가 Bay 0에 있는 것으로 보고됩니다. 해당 문제는 HP StorageWorks MSA60, HP StorageWorks MSA70 및 HP ProLiant DL180 G6(12 베이와 25 베이 백플레인 장착)에서 발생합니다.
- HP ProLiant ML150 G6 서버의 non-hot 플러그 백플레인에 장착되면 예비 드라이브는 스핀업이 되지 않습니다.
- Battery Backed Write Cache (BBWC)가 고갈 상태에 처했어도 No-Data Loss post 메시지가 표시되지 않습니다. 배터리가 고갈되면 BBWC는 부적절하게 영구적으로 비활성화될 수 있습니다.
- 스마트 어레이 록업 문제를 유발하는 스마트 어레이와 Kaspersky 백신 툴 사이의 비호환성 문제를 해결하였습니다.
- 메모리 인터페이스 파라미터를 수정하여 Flash-Backed Write Cache (FBWC) 사용 시 컨트롤러가 록업되는 문제를 해결하였습니다.
]]>
韌體相依性:
想要支援連接至 HP StorageWorks 600 模組化磁盤系統 (MDS600) 的 HP Smart Array P812 客戶必須確保硬體的最低韌體版本為如下所示(或更高版本)。
- 在連接 MDS600 至 HP Smart Array P812 之前,必須將 HP Smart Array P812 刷新至韌體版本 3.50 或更高版本。
- 在 HP Smart Array P812 韌體刷新至 3.50 或更高版本後,需要採取如下步驟來連接 MDS600 與 HP Smart Array P812 控制器,然後開始操作 MSD600。
- 如果 MDS600 的韌體版本為 2.60, 則可以連接至 HP Smart Array P812 控制器。
- 但是,要運行連接至 HP Smart Array P812 的 MDS600,MDS600 必須升級至韌體版本 2.66。
- 如果 MDS600 執行的韌體版本為 2.54,則必須連接如下之一的 Smart Array 控制器來執行韌體升級至 2.66:
- Smart Array P700m 控制器
- Smart Array P411 控制器
- Smart Array P212 控制器
附註: 當使用此備用控制器方法將 MDS600 韌體升級至 2.66 後,MDS600 即可連接至韌體版本為 3.50 的 HP Smart Array P812,然後開始操作。
有關更多資訊,請參考如下 URL 的可用客戶諮詢文件:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02437391
要支援 HP StorageWorks D2000 機櫃上的雙域,D2000 的最低韌體版本要為 0067 或更高版本。
此儲存子系統的元件(例如磁碟機、控制器與伺服器背板)應當在同樣的資料傳輸速率與系統頻寬上運行,從而所有元件都處於一個可接受的水準上。
連接至 HP Smart Array P410 或 HP Smart Array P410i 的 HP SAS Expander 卡必須要有 SAS Expander 卡韌體版本 2.06 或更高版本來支援 6Gb SAS 與 3Gb SATA 磁碟機。
在執行 VMware ESX/ESXi 時,使用韌體維護 CD 上的 HP Smart Update Manager 僅支援離線更新。
已解決的問題:
- 在熱更換 HP Smart Array HDD 後,所有連接至擴充卡(HDD 更換處)的磁碟機均報告為位於機槽 0。此問題發生在 HP StorageWorks MSA60、HP StorageWorks MSA70 與 HP ProLiant DL180 G6,含 12 個機槽與 25 個機槽背板。
- 備用磁碟機連接至 HP ProLiant ML150 G6 伺服器上的非熱拔插背板後無法運轉。
- 當電池備援寫入快取 (BBWC) 處於耗盡狀態時,無法顯示「No-Data Loss」(無資料遺失)POST 訊息。當電池耗盡時 BBWC 會永久不正常停用。
- 解決了導致 Smart Array 鎖定之 Smart Array 與 Kaspersky Anti-Virus 工具間的不相容性。
- 已修改記憶記憶體介面參數,以解決在使用 Flash-Backed Write Cache (FBWC) 導致控制器鎖定的問題。
]]>
Firmware Dependency:
Customers who wish to support the HP Smart Array P812 connected to the HP StorageWorks 600 Modular Disk System (MDS600) must ensure that the hardware is at the minimum firmware versions (or later) as defined below.
- Before connecting the MDS600 to the HP Smart Array P812, you must first flash the HP Smart Array P812 to firmware version 3.50 or greater.
- After the HP Smart Array P812 firmware is flashed to 3.50 or greater, then the following steps need to be followed to connect the MDS600 with the HP Smart Array P812 controller and begin operating the MSD600.
- If the MDS600 has version 2.60 firmware, then it can be connected to the HP Smart Array P812 controller.
- However, to operate the MDS600 connected to HP Smart Array P812, the MDS600 must be upgraded to firmware version 2.66.
- If an MDS600 is running firmware version 2.54, it must be attached to one of the following Smart Array Controllers to perform the upgrade to firmware version 2.66:
- Smart Array P700m Controller
- Smart Array P411 Controller
- Smart Array P212 Controller
NOTE: Once the MDS600 firmware is upgraded to 2.66 using this alternate controller method, then the MDS600 can be connected to the HP Smart Array P812, which has firmware version 3.50, and begin operation.
For additional information, reference the Customer Advisory available at the following URL:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02437391
To support Dual Domain on HP StorageWorks D2000 enclosures, the D2000 must be at a minimum firmware version of 0067 or later.
The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card firmware version 2.06 or higher, to support 6Gb SAS and 3Gb SATA drives.
When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD.
Problems Fixed:
- Fix for an incomplete or problematic data transfer issue on RAID 0 or RAID 1 volumes, which may occur under heavy I/O workloads. This issue may happen when array accelerator cache-bypassed write operations take place on a common small Logical Block Addressing (LBA) region on the drive, following multiple discontinuous non-overlapping cached writes.
For additional information, reference the Customer Advisory available at the following URL:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02547655
- Fix to resolve the rare potential for a data transfer from an incorrect host memory address. This issue is associated with read or write operations that span 8 GB (or higher) address boundaries in non-Windows OS using Physical Address Extensions.
For additional information, reference the Customer Advisory available at the following URL:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02547670
]]>
Firmware Dependency:
Customers who wish to support the HP Smart Array P812 connected to the HP StorageWorks 600 Modular Disk System (MDS600) must ensure that the hardware is at the minimum firmware versions (or later) as defined below.
- Before connecting the MDS600 to the HP Smart Array P812, you must first flash the HP Smart Array P812 to firmware version 3.50 or greater.
- After the HP Smart Array P812 firmware is flashed to 3.50 or greater, then the following steps need to be followed to connect the MDS600 with the HP Smart Array P812 controller and begin operating the MSD600.
- If the MDS600 has version 2.60 firmware, then it can be connected to the HP Smart Array P812 controller.
- However, to operate the MDS600 connected to HP Smart Array P812, the MDS600 must be upgraded to firmware version 2.66.
- If an MDS600 is running firmware version 2.54, it must be attached to one of the following Smart Array Controllers to perform the upgrade to firmware version 2.66:
- Smart Array P700m Controller
- Smart Array P411 Controller
- Smart Array P212 Controller
NOTE: Once the MDS600 firmware is upgraded to 2.66 using this alternate controller method, then the MDS600 can be connected to the HP Smart Array P812, which has firmware version 3.50, and begin operation.
For additional information, reference the Customer Advisory available at the following URL:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02437391
To support Dual Domain on HP StorageWorks D2000 enclosures, the D2000 must be at a minimum firmware version of 0067 or later.
The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card firmware version 2.06 or higher, to support 6Gb SAS and 3Gb SATA drives.
When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD.
Problems Fixed:
- Fix for an incomplete or problematic data transfer issue on RAID 0 or RAID 1 volumes, which may occur under heavy I/O workloads. This issue may happen when array accelerator cache-bypassed write operations take place on a common small Logical Block Addressing (LBA) region on the drive, following multiple discontinuous non-overlapping cached writes.
For additional information, reference the Customer Advisory available at the following URL:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02547655
- Fix to resolve the rare potential for a data transfer from an incorrect host memory address. This issue is associated with read or write operations that span 8 GB (or higher) address boundaries in non-Windows OS using Physical Address Extensions.
For additional information, reference the Customer Advisory available at the following URL:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02547670
]]>
Firmware Dependency:
Customers who wish to support the HP Smart Array P812 connected to the HP StorageWorks 600 Modular Disk System (MDS600) must ensure that the hardware is at the minimum firmware versions (or later) as defined below.
- Before connecting the MDS600 to the HP Smart Array P812, you must first flash the HP Smart Array P812 to firmware version 3.50 or greater.
- After the HP Smart Array P812 firmware is flashed to 3.50 or greater, then the following steps need to be followed to connect the MDS600 with the HP Smart Array P812 controller and begin operating the MSD600.
- If the MDS600 has version 2.60 firmware, then it can be connected to the HP Smart Array P812 controller.
- However, to operate the MDS600 connected to HP Smart Array P812, the MDS600 must be upgraded to firmware version 2.66.
- If an MDS600 is running firmware version 2.54, it must be attached to one of the following Smart Array Controllers to perform the upgrade to firmware version 2.66:
- Smart Array P700m Controller
- Smart Array P411 Controller
- Smart Array P212 Controller
NOTE: Once the MDS600 firmware is upgraded to 2.66 using this alternate controller method, then the MDS600 can be connected to the HP Smart Array P812, which has firmware version 3.50, and begin operation.
For additional information, reference the Customer Advisory available at the following URL:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02437391
To support Dual Domain on HP StorageWorks D2000 enclosures, the D2000 must be at a minimum firmware version of 0067 or later.
The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card firmware version 2.06 or higher, to support 6Gb SAS and 3Gb SATA drives.
When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD.
Problems Fixed:
- Fix for an incomplete or problematic data transfer issue on RAID 0 or RAID 1 volumes, which may occur under heavy I/O workloads. This issue may happen when array accelerator cache-bypassed write operations take place on a common small Logical Block Addressing (LBA) region on the drive, following multiple discontinuous non-overlapping cached writes.
For additional information, reference the Customer Advisory available at the following URL:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02547655
- Fix to resolve the rare potential for a data transfer from an incorrect host memory address. This issue is associated with read or write operations that span 8 GB (or higher) address boundaries in non-Windows OS using Physical Address Extensions.
For additional information, reference the Customer Advisory available at the following URL:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02547670
]]>
Firmware Dependency:
Customers who wish to support the HP Smart Array P812 connected to the HP StorageWorks 600 Modular Disk System (MDS600) must ensure that the hardware is at the minimum firmware versions (or later) as defined below.
- Before connecting the MDS600 to the HP Smart Array P812, you must first flash the HP Smart Array P812 to firmware version 3.50 or greater.
- After the HP Smart Array P812 firmware is flashed to 3.50 or greater, then the following steps need to be followed to connect the MDS600 with the HP Smart Array P812 controller and begin operating the MSD600.
- If the MDS600 has version 2.60 firmware, then it can be connected to the HP Smart Array P812 controller.
- However, to operate the MDS600 connected to HP Smart Array P812, the MDS600 must be upgraded to firmware version 2.66.
- If an MDS600 is running firmware version 2.54, it must be attached to one of the following Smart Array Controllers to perform the upgrade to firmware version 2.66:
- Smart Array P700m Controller
- Smart Array P411 Controller
- Smart Array P212 Controller
NOTE: Once the MDS600 firmware is upgraded to 2.66 using this alternate controller method, then the MDS600 can be connected to the HP Smart Array P812, which has firmware version 3.50, and begin operation.
For additional information, reference the Customer Advisory available at the following URL:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02437391
To support Dual Domain on HP StorageWorks D2000 enclosures, the D2000 must be at a minimum firmware version of 0067 or later.
The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card firmware version 2.06 or higher, to support 6Gb SAS and 3Gb SATA drives.
When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD.
Problems Fixed:
- Fix for an incomplete or problematic data transfer issue on RAID 0 or RAID 1 volumes, which may occur under heavy I/O workloads. This issue may happen when array accelerator cache-bypassed write operations take place on a common small Logical Block Addressing (LBA) region on the drive, following multiple discontinuous non-overlapping cached writes.
For additional information, reference the Customer Advisory available at the following URL:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02547655
- Fix to resolve the rare potential for a data transfer from an incorrect host memory address. This issue is associated with read or write operations that span 8 GB (or higher) address boundaries in non-Windows OS using Physical Address Extensions.
For additional information, reference the Customer Advisory available at the following URL:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02547670
]]>
Firmware Dependency:
Customers who wish to support the HP Smart Array P812 connected to the HP StorageWorks 600 Modular Disk System (MDS600) must ensure that the hardware is at the minimum firmware versions (or later) as defined below.
- Before connecting the MDS600 to the HP Smart Array P812, you must first flash the HP Smart Array P812 to firmware version 3.50 or greater.
- After the HP Smart Array P812 firmware is flashed to 3.50 or greater, then the following steps need to be followed to connect the MDS600 with the HP Smart Array P812 controller and begin operating the MSD600.
- If the MDS600 has version 2.60 firmware, then it can be connected to the HP Smart Array P812 controller.
- However, to operate the MDS600 connected to HP Smart Array P812, the MDS600 must be upgraded to firmware version 2.66.
- If an MDS600 is running firmware version 2.54, it must be attached to one of the following Smart Array Controllers to perform the upgrade to firmware version 2.66:
- Smart Array P700m Controller
- Smart Array P411 Controller
- Smart Array P212 Controller
NOTE: Once the MDS600 firmware is upgraded to 2.66 using this alternate controller method, then the MDS600 can be connected to the HP Smart Array P812, which has firmware version 3.50, and begin operation.
For additional information, reference the Customer Advisory available at the following URL:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02437391
To support Dual Domain on HP StorageWorks D2000 enclosures, the D2000 must be at a minimum firmware version of 0067 or later.
The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card firmware version 2.06 or higher, to support 6Gb SAS and 3Gb SATA drives.
When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD.
Problems Fixed:
- Fix for an incomplete or problematic data transfer issue on RAID 0 or RAID 1 volumes, which may occur under heavy I/O workloads. This issue may happen when array accelerator cache-bypassed write operations take place on a common small Logical Block Addressing (LBA) region on the drive, following multiple discontinuous non-overlapping cached writes.
For additional information, reference the Customer Advisory available at the following URL:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02547655
- Fix to resolve the rare potential for a data transfer from an incorrect host memory address. This issue is associated with read or write operations that span 8 GB (or higher) address boundaries in non-Windows OS using Physical Address Extensions.
For additional information, reference the Customer Advisory available at the following URL:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02547670
]]>
Firmware Dependency:
Customers who wish to support the HP Smart Array P812 connected to the HP StorageWorks 600 Modular Disk System (MDS600) must ensure that the hardware is at the minimum firmware versions (or later) as defined below.
- Before connecting the MDS600 to the HP Smart Array P812, you must first flash the HP Smart Array P812 to firmware version 3.50 or greater.
- After the HP Smart Array P812 firmware is flashed to 3.50 or greater, then the following steps need to be followed to connect the MDS600 with the HP Smart Array P812 controller and begin operating the MSD600.
- If the MDS600 has version 2.60 firmware, then it can be connected to the HP Smart Array P812 controller.
- However, to operate the MDS600 connected to HP Smart Array P812, the MDS600 must be upgraded to firmware version 2.66.
- If an MDS600 is running firmware version 2.54, it must be attached to one of the following Smart Array Controllers to perform the upgrade to firmware version 2.66:
- Smart Array P700m Controller
- Smart Array P411 Controller
- Smart Array P212 Controller
NOTE: Once the MDS600 firmware is upgraded to 2.66 using this alternate controller method, then the MDS600 can be connected to the HP Smart Array P812, which has firmware version 3.50, and begin operation.
For additional information, reference the Customer Advisory available at the following URL:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02437391
To support Dual Domain on HP StorageWorks D2000 enclosures, the D2000 must be at a minimum firmware version of 0067 or later.
The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card firmware version 2.06 or higher, to support 6Gb SAS and 3Gb SATA drives.
When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD.
Problems Fixed:
- Fix for an incomplete or problematic data transfer issue on RAID 0 or RAID 1 volumes, which may occur under heavy I/O workloads. This issue may happen when array accelerator cache-bypassed write operations take place on a common small Logical Block Addressing (LBA) region on the drive, following multiple discontinuous non-overlapping cached writes.
For additional information, reference the Customer Advisory available at the following URL:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02547655
- Fix to resolve the rare potential for a data transfer from an incorrect host memory address. This issue is associated with read or write operations that span 8 GB (or higher) address boundaries in non-Windows OS using Physical Address Extensions.
For additional information, reference the Customer Advisory available at the following URL:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02547670
]]>
ファームウェアの関連性:
HP StorageWorks Modular Disk System 600(MDS600)に接続されたHP Smartアレイ P812のサポートが必要な場合、ハードウェアが以下のバージョン以降のファームウェアの最小要件を満たしている必要があります。
- MDS600をHP Smartアレイ P812に接続する前に、HP Smartアレイ P812のファームウェアをバージョン3.50以降にフラッシュする必要があります。
- HP Smartアレイ P812のファームウェアを3.50以降にフラッシュした後、MDS600をHP Smartアレイ P812コントローラーに接続して、MDS600の動作を開始するためには、以下の手順に従う必要があります。
- MDS600がバージョン2.60のファームウェアの場合、HP Smartアレイ P812コントローラーに接続することができます。
- しかし、HP Smartアレイ P812に接続したMDS600を動作させるためには、MDS600は、ファームウェア バージョン2.66へのアップグレードが必要です。
- MDS600がバージョン2.54のファームウェアの場合、ファームウェア バージョン2.66へのアップグレードが実行された以下のSmartアレイ コントローラーの一つと接続する必要があります。
- Smartアレイ P700mコントローラー
- Smartアレイ P411コントローラー
- Smartアレイ P212コントローラー
注: このコントローラーの代替方法を使ってMDS600のファームウェアを2.66にアップデートが行われたら、MDS600をファームウェア バージョン3.50のHP Smartアレイ P812に接続して、動作を開始することができます。
詳しくは、以下のURLのCustomer Advisoryを参照してください。
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02437391(英語)
HP StorageWorks D2000エンクロージャーでデュアル ドメインをサポートするには、D2000のファームウェア バージョンを0067以降にする必要があります。
ストレージ サブシステムのコンポーネント(例、ドライブ、コントローラー、およびサーバー バックプレーン)は、同じデータ転送レートで動作しなければなりません。そうでない場合はシステム バンド幅はすべてのコンポーネントが受け入れ可能なレベルにネゴシエートされます。
HP Smartアレイ P410またはHP Smartアレイ P410iに接続されたHP SASエキスパンダー カードは、6Gb SASおよび3Gb SATAドライブをサポートするために、SASエキスパンダー カード ファームウェア バージョン2.06以降が必要です。
VMware ESX/ESXiを実行している場合、Firmware Maintenance CD上のHP Smart Update Managerを使用したオフライン アップデートのみサポートされます。
修正された問題点:
- RAID 0あるいはRAID 1のボリュームでI/O負荷が高い状態で発生する、不完全なまたは問題を含むデータ転送の問題を修正しました。 アレイアクセラレータのキャッシュバイパス書き込み動作が、ドライブ上の共通の小さいLogical Block Addressing (LBA) 領域で、複数の不連続な重ならないキャッシュ書き込みが起こる場合、この問題が発生することがあります。
詳しくは、以下のURLのCustomer Advisoryを参照してください。
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02547655(英語)
- 間違ったホスト メモリアドレスからのデータ転送がまれに起こる可能性を解決するために修正しました。 この問題は、Physical Address Extensionsを使っている非Windows OSで8GB(以上)のアドレス境界の範囲での読み込みあるいは書き込み操作と関係しています。
詳しくは、以下のURLのCustomer Advisoryを参照してください。
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02547670(英語)
]]>
Firmware Dependency:
Customers who wish to support the HP Smart Array P812 connected to the HP StorageWorks 600 Modular Disk System (MDS600) must ensure that the hardware is at the minimum firmware versions (or later) as defined below.
- Before connecting the MDS600 to the HP Smart Array P812, you must first flash the HP Smart Array P812 to firmware version 3.50 or greater.
- After the HP Smart Array P812 firmware is flashed to 3.50 or greater, then the following steps need to be followed to connect the MDS600 with the HP Smart Array P812 controller and begin operating the MSD600.
- If the MDS600 has version 2.60 firmware, then it can be connected to the HP Smart Array P812 controller.
- However, to operate the MDS600 connected to HP Smart Array P812, the MDS600 must be upgraded to firmware version 2.66.
- If an MDS600 is running firmware version 2.54, it must be attached to one of the following Smart Array Controllers to perform the upgrade to firmware version 2.66:
- Smart Array P700m Controller
- Smart Array P411 Controller
- Smart Array P212 Controller
NOTE: Once the MDS600 firmware is upgraded to 2.66 using this alternate controller method, then the MDS600 can be connected to the HP Smart Array P812, which has firmware version 3.50, and begin operation.
For additional information, reference the Customer Advisory available at the following URL:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02437391
To support Dual Domain on HP StorageWorks D2000 enclosures, the D2000 must be at a minimum firmware version of 0067 or later.
The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card firmware version 2.06 or higher, to support 6Gb SAS and 3Gb SATA drives.
When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD.
Problems Fixed:
- Fix for an incomplete or problematic data transfer issue on RAID 0 or RAID 1 volumes, which may occur under heavy I/O workloads. This issue may happen when array accelerator cache-bypassed write operations take place on a common small Logical Block Addressing (LBA) region on the drive, following multiple discontinuous non-overlapping cached writes.
For additional information, reference the Customer Advisory available at the following URL:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02547655
- Fix to resolve the rare potential for a data transfer from an incorrect host memory address. This issue is associated with read or write operations that span 8 GB (or higher) address boundaries in non-Windows OS using Physical Address Extensions.
For additional information, reference the Customer Advisory available at the following URL:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02547670
]]>
Firmware Dependency:
Customers who wish to support the HP Smart Array P812 connected to the HP StorageWorks 600 Modular Disk System (MDS600) must ensure that the hardware is at the minimum firmware versions (or later) as defined below.
- Before connecting the MDS600 to the HP Smart Array P812, you must first flash the HP Smart Array P812 to firmware version 3.50 or greater.
- After the HP Smart Array P812 firmware is flashed to 3.50 or greater, then the following steps need to be followed to connect the MDS600 with the HP Smart Array P812 controller and begin operating the MSD600.
- If the MDS600 has version 2.60 firmware, then it can be connected to the HP Smart Array P812 controller.
- However, to operate the MDS600 connected to HP Smart Array P812, the MDS600 must be upgraded to firmware version 2.66.
- If an MDS600 is running firmware version 2.54, it must be attached to one of the following Smart Array Controllers to perform the upgrade to firmware version 2.66:
- Smart Array P700m Controller
- Smart Array P411 Controller
- Smart Array P212 Controller
NOTE: Once the MDS600 firmware is upgraded to 2.66 using this alternate controller method, then the MDS600 can be connected to the HP Smart Array P812, which has firmware version 3.50, and begin operation.
For additional information, reference the Customer Advisory available at the following URL:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02437391
To support Dual Domain on HP StorageWorks D2000 enclosures, the D2000 must be at a minimum firmware version of 0067 or later.
The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card firmware version 2.06 or higher, to support 6Gb SAS and 3Gb SATA drives.
When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD.
Problems Fixed:
- Fix for an incomplete or problematic data transfer issue on RAID 0 or RAID 1 volumes, which may occur under heavy I/O workloads. This issue may happen when array accelerator cache-bypassed write operations take place on a common small Logical Block Addressing (LBA) region on the drive, following multiple discontinuous non-overlapping cached writes.
For additional information, reference the Customer Advisory available at the following URL:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02547655
- Fix to resolve the rare potential for a data transfer from an incorrect host memory address. This issue is associated with read or write operations that span 8 GB (or higher) address boundaries in non-Windows OS using Physical Address Extensions.
For additional information, reference the Customer Advisory available at the following URL:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02547670
]]>
Enhancements/New Features:
]]>
Enhancements/New Features:
]]>
Enhancements/New Features:
]]>
Enhancements/New Features:
]]>
Enhancements/New Features:
]]>
Enhancements/New Features:
]]>
改善点/新しい機能:
]]>
Enhancements/New Features:
]]>
Enhancements/New Features:
]]>
Firmware Dependency:
Customers who wish to support the HP Smart Array P812 connected to the HP StorageWorks 600 Modular Disk System (MDS600) must ensure that the hardware is at the minimum firmware versions (or later) as defined below.
- Before connecting the MDS600 to the HP Smart Array P812, you must first flash the HP Smart Array P812 to firmware version 3.50 or greater.
- After the HP Smart Array P812 firmware is flashed to 3.50 or greater, then the following steps need to be followed to connect the MDS600 with the HP Smart Array P812 controller and begin operating the MSD600.
- If the MDS600 has version 2.60 firmware, then it can be connected to the HP Smart Array P812 controller.
- However, to operate the MDS600 connected to HP Smart Array P812, the MDS600 must be upgraded to firmware version 2.66.
- If an MDS600 is running firmware version 2.54, it must be attached to one of the following Smart Array Controllers to perform the upgrade to firmware version 2.66:
- Smart Array P700m Controller
- Smart Array P411 Controller
- Smart Array P212 Controller
NOTE: Once the MDS600 firmware is upgraded to 2.66 using this alternate controller method, then the MDS600 can be connected to the HP Smart Array P812, which has firmware version 3.50, and begin operation.
To support Dual Domain on HP StorageWorks D2000 enclosures, the D2000 must be at a minimum firmware version of 0067 or later.
The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card firmware version 2.06 or higher, to support 6Gb SAS and 3Gb SATA drives.
When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD.
Problems Fixed:
- Fixed an issue where spare drives were not being seen at post on an HP SAS Expander card when connected to an HP Smart Array P410.
- Fixed an issue on the HP ProLiant DL180G6 that occurred when a drive was hot-added in Bay 12 the LED was illuminating in Bay 11.
- Fixed an issue where false hot-drive removal of drives is being reported.
- Fixed an issue where an OS would hang during heavy IO loads and drive rebuilds.
- Fixed an issue where a bad block in a RAID 60 configuration could lead to potential data-miscompare. This has only been observed in a lab environment under extensive write/verify testing involving bad blocks in a RAID 60 volume.
- Fixed an issue where a bad block write operation would result in a controller lockup when running in a Dual Domain configuration connected to an HP Smart Array P812 controller.
- Fixed an issue that existed in Smart Array FW 3.30 where SATA hard drives behind an expander were being incorrectly flagged as "Failed" . This issue did not affect SAS drives.
For additional information, reference the Customer Advisory available at the following URL:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?locale=en_US&objectID=c02457119
]]>
Firmware Dependency:
Customers who wish to support the HP Smart Array P812 connected to the HP StorageWorks 600 Modular Disk System (MDS600) must ensure that the hardware is at the minimum firmware versions (or later) as defined below.
- Before connecting the MDS600 to the HP Smart Array P812, you must first flash the HP Smart Array P812 to firmware version 3.50 or greater.
- After the HP Smart Array P812 firmware is flashed to 3.50 or greater, then the following steps need to be followed to connect the MDS600 with the HP Smart Array P812 controller and begin operating the MSD600.
- If the MDS600 has version 2.60 firmware, then it can be connected to the HP Smart Array P812 controller.
- However, to operate the MDS600 connected to HP Smart Array P812, the MDS600 must be upgraded to firmware version 2.66.
- If an MDS600 is running firmware version 2.54, it must be attached to one of the following Smart Array Controllers to perform the upgrade to firmware version 2.66:
- Smart Array P700m Controller
- Smart Array P411 Controller
- Smart Array P212 Controller
NOTE: Once the MDS600 firmware is upgraded to 2.66 using this alternate controller method, then the MDS600 can be connected to the HP Smart Array P812, which has firmware version 3.50, and begin operation.
To support Dual Domain on HP StorageWorks D2000 enclosures, the D2000 must be at a minimum firmware version of 0067 or later.
The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card firmware version 2.06 or higher, to support 6Gb SAS and 3Gb SATA drives.
When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD.
Problems Fixed:
- Fixed an issue where spare drives were not being seen at post on an HP SAS Expander card when connected to an HP Smart Array P410.
- Fixed an issue on the HP ProLiant DL180G6 that occurred when a drive was hot-added in Bay 12 the LED was illuminating in Bay 11.
- Fixed an issue where false hot-drive removal of drives is being reported.
- Fixed an issue where an OS would hang during heavy IO loads and drive rebuilds.
- Fixed an issue where a bad block in a RAID 60 configuration could lead to potential data-miscompare. This has only been observed in a lab environment under extensive write/verify testing involving bad blocks in a RAID 60 volume.
- Fixed an issue where a bad block write operation would result in a controller lockup when running in a Dual Domain configuration connected to an HP Smart Array P812 controller.
- Fixed an issue that existed in Smart Array FW 3.30 where SATA hard drives behind an expander were being incorrectly flagged as "Failed" . This issue did not affect SAS drives.
For additional information, reference the Customer Advisory available at the following URL:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?locale=en_US&objectID=c02457119
]]>
Firmware Dependency:
Customers who wish to support the HP Smart Array P812 connected to the HP StorageWorks 600 Modular Disk System (MDS600) must ensure that the hardware is at the minimum firmware versions (or later) as defined below.
- Before connecting the MDS600 to the HP Smart Array P812, you must first flash the HP Smart Array P812 to firmware version 3.50 or greater.
- After the HP Smart Array P812 firmware is flashed to 3.50 or greater, then the following steps need to be followed to connect the MDS600 with the HP Smart Array P812 controller and begin operating the MSD600.
- If the MDS600 has version 2.60 firmware, then it can be connected to the HP Smart Array P812 controller.
- However, to operate the MDS600 connected to HP Smart Array P812, the MDS600 must be upgraded to firmware version 2.66.
- If an MDS600 is running firmware version 2.54, it must be attached to one of the following Smart Array Controllers to perform the upgrade to firmware version 2.66:
- Smart Array P700m Controller
- Smart Array P411 Controller
- Smart Array P212 Controller
NOTE: Once the MDS600 firmware is upgraded to 2.66 using this alternate controller method, then the MDS600 can be connected to the HP Smart Array P812, which has firmware version 3.50, and begin operation.
To support Dual Domain on HP StorageWorks D2000 enclosures, the D2000 must be at a minimum firmware version of 0067 or later.
The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card firmware version 2.06 or higher, to support 6Gb SAS and 3Gb SATA drives.
When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD.
Problems Fixed:
- Fixed an issue where spare drives were not being seen at post on an HP SAS Expander card when connected to an HP Smart Array P410.
- Fixed an issue on the HP ProLiant DL180G6 that occurred when a drive was hot-added in Bay 12 the LED was illuminating in Bay 11.
- Fixed an issue where false hot-drive removal of drives is being reported.
- Fixed an issue where an OS would hang during heavy IO loads and drive rebuilds.
- Fixed an issue where a bad block in a RAID 60 configuration could lead to potential data-miscompare. This has only been observed in a lab environment under extensive write/verify testing involving bad blocks in a RAID 60 volume.
- Fixed an issue where a bad block write operation would result in a controller lockup when running in a Dual Domain configuration connected to an HP Smart Array P812 controller.
- Fixed an issue that existed in Smart Array FW 3.30 where SATA hard drives behind an expander were being incorrectly flagged as "Failed" . This issue did not affect SAS drives.
For additional information, reference the Customer Advisory available at the following URL:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?locale=en_US&objectID=c02457119
]]>
Firmware Dependency:
Customers who wish to support the HP Smart Array P812 connected to the HP StorageWorks 600 Modular Disk System (MDS600) must ensure that the hardware is at the minimum firmware versions (or later) as defined below.
- Before connecting the MDS600 to the HP Smart Array P812, you must first flash the HP Smart Array P812 to firmware version 3.50 or greater.
- After the HP Smart Array P812 firmware is flashed to 3.50 or greater, then the following steps need to be followed to connect the MDS600 with the HP Smart Array P812 controller and begin operating the MSD600.
- If the MDS600 has version 2.60 firmware, then it can be connected to the HP Smart Array P812 controller.
- However, to operate the MDS600 connected to HP Smart Array P812, the MDS600 must be upgraded to firmware version 2.66.
- If an MDS600 is running firmware version 2.54, it must be attached to one of the following Smart Array Controllers to perform the upgrade to firmware version 2.66:
- Smart Array P700m Controller
- Smart Array P411 Controller
- Smart Array P212 Controller
NOTE: Once the MDS600 firmware is upgraded to 2.66 using this alternate controller method, then the MDS600 can be connected to the HP Smart Array P812, which has firmware version 3.50, and begin operation.
To support Dual Domain on HP StorageWorks D2000 enclosures, the D2000 must be at a minimum firmware version of 0067 or later.
The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card firmware version 2.06 or higher, to support 6Gb SAS and 3Gb SATA drives.
When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD.
Problems Fixed:
- Fixed an issue where spare drives were not being seen at post on an HP SAS Expander card when connected to an HP Smart Array P410.
- Fixed an issue on the HP ProLiant DL180G6 that occurred when a drive was hot-added in Bay 12 the LED was illuminating in Bay 11.
- Fixed an issue where false hot-drive removal of drives is being reported.
- Fixed an issue where an OS would hang during heavy IO loads and drive rebuilds.
- Fixed an issue where a bad block in a RAID 60 configuration could lead to potential data-miscompare. This has only been observed in a lab environment under extensive write/verify testing involving bad blocks in a RAID 60 volume.
- Fixed an issue where a bad block write operation would result in a controller lockup when running in a Dual Domain configuration connected to an HP Smart Array P812 controller.
- Fixed an issue that existed in Smart Array FW 3.30 where SATA hard drives behind an expander were being incorrectly flagged as "Failed" . This issue did not affect SAS drives.
For additional information, reference the Customer Advisory available at the following URL:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?locale=en_US&objectID=c02457119
]]>
Firmware Dependency:
Customers who wish to support the HP Smart Array P812 connected to the HP StorageWorks 600 Modular Disk System (MDS600) must ensure that the hardware is at the minimum firmware versions (or later) as defined below.
- Before connecting the MDS600 to the HP Smart Array P812, you must first flash the HP Smart Array P812 to firmware version 3.50 or greater.
- After the HP Smart Array P812 firmware is flashed to 3.50 or greater, then the following steps need to be followed to connect the MDS600 with the HP Smart Array P812 controller and begin operating the MSD600.
- If the MDS600 has version 2.60 firmware, then it can be connected to the HP Smart Array P812 controller.
- However, to operate the MDS600 connected to HP Smart Array P812, the MDS600 must be upgraded to firmware version 2.66.
- If an MDS600 is running firmware version 2.54, it must be attached to one of the following Smart Array Controllers to perform the upgrade to firmware version 2.66:
- Smart Array P700m Controller
- Smart Array P411 Controller
- Smart Array P212 Controller
NOTE: Once the MDS600 firmware is upgraded to 2.66 using this alternate controller method, then the MDS600 can be connected to the HP Smart Array P812, which has firmware version 3.50, and begin operation.
To support Dual Domain on HP StorageWorks D2000 enclosures, the D2000 must be at a minimum firmware version of 0067 or later.
The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card firmware version 2.06 or higher, to support 6Gb SAS and 3Gb SATA drives.
When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD.
Problems Fixed:
- Fixed an issue where spare drives were not being seen at post on an HP SAS Expander card when connected to an HP Smart Array P410.
- Fixed an issue on the HP ProLiant DL180G6 that occurred when a drive was hot-added in Bay 12 the LED was illuminating in Bay 11.
- Fixed an issue where false hot-drive removal of drives is being reported.
- Fixed an issue where an OS would hang during heavy IO loads and drive rebuilds.
- Fixed an issue where a bad block in a RAID 60 configuration could lead to potential data-miscompare. This has only been observed in a lab environment under extensive write/verify testing involving bad blocks in a RAID 60 volume.
- Fixed an issue where a bad block write operation would result in a controller lockup when running in a Dual Domain configuration connected to an HP Smart Array P812 controller.
- Fixed an issue that existed in Smart Array FW 3.30 where SATA hard drives behind an expander were being incorrectly flagged as "Failed" . This issue did not affect SAS drives.
For additional information, reference the Customer Advisory available at the following URL:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?locale=en_US&objectID=c02457119
]]>
Firmware Dependency:
Customers who wish to support the HP Smart Array P812 connected to the HP StorageWorks 600 Modular Disk System (MDS600) must ensure that the hardware is at the minimum firmware versions (or later) as defined below.
- Before connecting the MDS600 to the HP Smart Array P812, you must first flash the HP Smart Array P812 to firmware version 3.50 or greater.
- After the HP Smart Array P812 firmware is flashed to 3.50 or greater, then the following steps need to be followed to connect the MDS600 with the HP Smart Array P812 controller and begin operating the MSD600.
- If the MDS600 has version 2.60 firmware, then it can be connected to the HP Smart Array P812 controller.
- However, to operate the MDS600 connected to HP Smart Array P812, the MDS600 must be upgraded to firmware version 2.66.
- If an MDS600 is running firmware version 2.54, it must be attached to one of the following Smart Array Controllers to perform the upgrade to firmware version 2.66:
- Smart Array P700m Controller
- Smart Array P411 Controller
- Smart Array P212 Controller
NOTE: Once the MDS600 firmware is upgraded to 2.66 using this alternate controller method, then the MDS600 can be connected to the HP Smart Array P812, which has firmware version 3.50, and begin operation.
To support Dual Domain on HP StorageWorks D2000 enclosures, the D2000 must be at a minimum firmware version of 0067 or later.
The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card firmware version 2.06 or higher, to support 6Gb SAS and 3Gb SATA drives.
When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD.
Problems Fixed:
- Fixed an issue where spare drives were not being seen at post on an HP SAS Expander card when connected to an HP Smart Array P410.
- Fixed an issue on the HP ProLiant DL180G6 that occurred when a drive was hot-added in Bay 12 the LED was illuminating in Bay 11.
- Fixed an issue where false hot-drive removal of drives is being reported.
- Fixed an issue where an OS would hang during heavy IO loads and drive rebuilds.
- Fixed an issue where a bad block in a RAID 60 configuration could lead to potential data-miscompare. This has only been observed in a lab environment under extensive write/verify testing involving bad blocks in a RAID 60 volume.
- Fixed an issue where a bad block write operation would result in a controller lockup when running in a Dual Domain configuration connected to an HP Smart Array P812 controller.
- Fixed an issue that existed in Smart Array FW 3.30 where SATA hard drives behind an expander were being incorrectly flagged as "Failed" . This issue did not affect SAS drives.
For additional information, reference the Customer Advisory available at the following URL:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?locale=en_US&objectID=c02457119
]]>
ファームウェアの関連性:
HP StorageWorks Modular Disk System 600(MDS600)に接続されたHP Smartアレイ P812のサポートが必要な場合、ハードウェアが以下のバージョン以降のファームウェアの最小要件を満たしている必要があります。
- MDS600をHP Smartアレイ P812に接続する前に、HP Smartアレイ P812のファームウェアをバージョン3.50以降にフラッシュする必要があります。
- HP Smartアレイ P812のファームウェアを3.50以降にフラッシュした後、MDS600をHP Smartアレイ P812コントローラーに接続して、MDS600の動作を開始するためには、以下の手順に従う必要があります。
- MDS600がバージョン2.60のファームウェアの場合、HP Smartアレイ P812コントローラーに接続することができます。
- しかし、HP Smartアレイ P812に接続したMDS600を動作させるためには、MDS600は、ファームウェア バージョン2.66へのアップグレードが必要です。
- MDS600がバージョン2.54のファームウェアの場合、ファームウェア バージョン2.66へのアップグレードが実行された以下のSmartアレイ コントローラーの一つと接続する必要があります。
- Smartアレイ P700mコントローラー
- Smartアレイ P411コントローラー
- Smartアレイ P212コントローラー
注: このコントローラーの代替方法を使ってMDS600のファームウェアを2.66にアップデートしたら、MDS600をファームウェア バージョン3.50のHP Smartアレイ P812に接続して、動作を開始することができます。
HP StorageWorks D2000エンクロージャーでデュアル ドメインをサポートするには、D2000のファームウェア バージョンを0067以降にする必要があります。
ストレージ サブシステムのコンポーネント(例、ドライブ、コントローラー、およびサーバー バックプレーン)は、同じデータ転送レートで動作しなければなりません。そうでない場合はシステム バンド幅はすべてのコンポーネントが受け入れ可能なレベルにネゴシエートされます。
HP Smartアレイ P410またはHP Smartアレイ P410iに接続されたHP SASエキスパンダー カードは、6Gb SASおよび3Gb SATAドライブをサポートするために、SASエキスパンダー カード ファームウェア バージョン2.06以降が必要です。
VMware ESX/ESXiを実行している場合、Firmware Maintenance CD上のHP Smart Update Managerを使用したオフライン アップデートのみサポートされます。
修正された問題点:
- HP Smartアレイ P410に接続されているHP SASエキスパンダー カード上でPOST中にスペア ドライブが確認できない問題を修正しました。
- ドライブをベイ12に動的追加した場合、ベイ11のLEDが点灯してしまうHP ProLiant DL180G6で起こる問題を修正しました。
- 誤ってドライブのホット リムーバルが報告される問題を修正しました。
- IO負荷が重く、ドライブの再構築の間、OSがハングアップする問題を修正しました。
- RAID 60構成で不良ブロックが潜在的なデータ不整合を引き起こす問題を修正しました。 この現象は、不良ブロックを含むRAID 60ボリュームに対して詳細な書き込み/確認テストを行ったラボの環境でのみ確認されました。
- HP Smartアレイ P812コントローラーに接続したデュアル ドメイン構成の場合、不良ブロック書き込みの操作が、コントローラーのロックアップを引き起こす問題を修正しました。
- エキスパンダーのSATAハードディスク ドライブが[Failed]とマークされるSmartアレイFW 3.30内の問題を修正しました。 この問題はSASドライブでは発生しません。
詳しくは、以下のURLのCustomer Advisoryを参照してください。
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?locale=en_US&objectID=c02457119(英語)
]]>
Firmware Dependency:
Customers who wish to support the HP Smart Array P812 connected to the HP StorageWorks 600 Modular Disk System (MDS600) must ensure that the hardware is at the minimum firmware versions (or later) as defined below.
- Before connecting the MDS600 to the HP Smart Array P812, you must first flash the HP Smart Array P812 to firmware version 3.50 or greater.
- After the HP Smart Array P812 firmware is flashed to 3.50 or greater, then the following steps need to be followed to connect the MDS600 with the HP Smart Array P812 controller and begin operating the MSD600.
- If the MDS600 has version 2.60 firmware, then it can be connected to the HP Smart Array P812 controller.
- However, to operate the MDS600 connected to HP Smart Array P812, the MDS600 must be upgraded to firmware version 2.66.
- If an MDS600 is running firmware version 2.54, it must be attached to one of the following Smart Array Controllers to perform the upgrade to firmware version 2.66:
- Smart Array P700m Controller
- Smart Array P411 Controller
- Smart Array P212 Controller
NOTE: Once the MDS600 firmware is upgraded to 2.66 using this alternate controller method, then the MDS600 can be connected to the HP Smart Array P812, which has firmware version 3.50, and begin operation.
To support Dual Domain on HP StorageWorks D2000 enclosures, the D2000 must be at a minimum firmware version of 0067 or later.
The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card firmware version 2.06 or higher, to support 6Gb SAS and 3Gb SATA drives.
When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD.
Problems Fixed:
- Fixed an issue where spare drives were not being seen at post on an HP SAS Expander card when connected to an HP Smart Array P410.
- Fixed an issue on the HP ProLiant DL180G6 that occurred when a drive was hot-added in Bay 12 the LED was illuminating in Bay 11.
- Fixed an issue where false hot-drive removal of drives is being reported.
- Fixed an issue where an OS would hang during heavy IO loads and drive rebuilds.
- Fixed an issue where a bad block in a RAID 60 configuration could lead to potential data-miscompare. This has only been observed in a lab environment under extensive write/verify testing involving bad blocks in a RAID 60 volume.
- Fixed an issue where a bad block write operation would result in a controller lockup when running in a Dual Domain configuration connected to an HP Smart Array P812 controller.
- Fixed an issue that existed in Smart Array FW 3.30 where SATA hard drives behind an expander were being incorrectly flagged as "Failed" . This issue did not affect SAS drives.
For additional information, reference the Customer Advisory available at the following URL:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?locale=en_US&objectID=c02457119
]]>
Firmware Dependency:
Customers who wish to support the HP Smart Array P812 connected to the HP StorageWorks 600 Modular Disk System (MDS600) must ensure that the hardware is at the minimum firmware versions (or later) as defined below.
- Before connecting the MDS600 to the HP Smart Array P812, you must first flash the HP Smart Array P812 to firmware version 3.50 or greater.
- After the HP Smart Array P812 firmware is flashed to 3.50 or greater, then the following steps need to be followed to connect the MDS600 with the HP Smart Array P812 controller and begin operating the MSD600.
- If the MDS600 has version 2.60 firmware, then it can be connected to the HP Smart Array P812 controller.
- However, to operate the MDS600 connected to HP Smart Array P812, the MDS600 must be upgraded to firmware version 2.66.
- If an MDS600 is running firmware version 2.54, it must be attached to one of the following Smart Array Controllers to perform the upgrade to firmware version 2.66:
- Smart Array P700m Controller
- Smart Array P411 Controller
- Smart Array P212 Controller
NOTE: Once the MDS600 firmware is upgraded to 2.66 using this alternate controller method, then the MDS600 can be connected to the HP Smart Array P812, which has firmware version 3.50, and begin operation.
To support Dual Domain on HP StorageWorks D2000 enclosures, the D2000 must be at a minimum firmware version of 0067 or later.
The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card firmware version 2.06 or higher, to support 6Gb SAS and 3Gb SATA drives.
When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD.
Problems Fixed:
- Fixed an issue where spare drives were not being seen at post on an HP SAS Expander card when connected to an HP Smart Array P410.
- Fixed an issue on the HP ProLiant DL180G6 that occurred when a drive was hot-added in Bay 12 the LED was illuminating in Bay 11.
- Fixed an issue where false hot-drive removal of drives is being reported.
- Fixed an issue where an OS would hang during heavy IO loads and drive rebuilds.
- Fixed an issue where a bad block in a RAID 60 configuration could lead to potential data-miscompare. This has only been observed in a lab environment under extensive write/verify testing involving bad blocks in a RAID 60 volume.
- Fixed an issue where a bad block write operation would result in a controller lockup when running in a Dual Domain configuration connected to an HP Smart Array P812 controller.
- Fixed an issue that existed in Smart Array FW 3.30 where SATA hard drives behind an expander were being incorrectly flagged as "Failed" . This issue did not affect SAS drives.
For additional information, reference the Customer Advisory available at the following URL:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?locale=en_US&objectID=c02457119
]]>
重要说明:
- 存储子系统(例如,磁盘、控制器和服务器背板)的组件应以相同的数据传输速率或者系统带宽运行,并可向下浏览至素有组件的可接受层级。
- 运行 VMware ESX/ESXi 时,仅固件维护光盘中的 HP Smart Update Manager 才支持离线更新功能。
惠普建议远程部署通过最新版本 Firmware Maintenance CD 获取的软件包,步骤如下:
- 使用 USB Key Creator 实用工具将 Firmware Maintenance CD 置于 U 盘上。
- 将更新使用的必需固件放在 U 盘上的 /compaq/swpackages 目录中。
- 通过系统中的 USB 密钥从 Firmware Maintenance CD 中的 \_autorunutorun_win.exe 运行 Autorun。
- 选择 "Firmware Update" 选项卡。
- 点击 "Install Firmware" 链接启动 HP Smart Update Manager。
- 遵循 GUI 在远程服务器上安装固件
固件依赖条件:
连接至 HP Smart Array P410 或者 HP Smart Array P410i 的 HP SAS Expander Card 要求使用 SAS Expander Card 固件版本 1.52 或者更改版本以支持 6Gb SAS 和 3Gb SATA 驱动器。
修复的问题:
- 解决了服务器配置多于 1 个 HP Smart Array P212、P411 或者 P410 控制器时,HP ProLiant 100 系列服务器 BIOS 无法指定启动控制器的问题。
- 解决了升级 HDD FW 时控制器无法响应的问题。
- 解决了 Storage Management Homepage 中的 CPU 使用率错误报告为 100% 的问题。
]]>
Important Notes:
- The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
- When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD
HP recommends for remote deployment of this package that you obtain the most recent version of the Firmware Maintenance CD and follow these steps:
- Place the Firmware Maintenance CD on a USB key using the HP USB Key Creator Utility.
- Place the firmware to be updated in the directory, /compaq/swpackages on the USB key.
- Run Autorun from \_autorunutorun_win.exe on the Firmware Maintenance CD from the USB key on a system
- Select the Firmware Update tab
- Click on the Install Firmware link to launch the HP Smart Update Manager
- Follow the GUI to install the firmware on remote servers
Firmware Dependency:
HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card Firmware version 1.52 or higher, to support 6Gb SAS and 3Gb SATA drives.
Problems Fixed:
- Fixed an issue where Bios on HP ProLiant 100 series servers could not designate a boot controller when more than 1 HP Smart Array P212, P411, or P410 controller are in the server.
- Fixed an issue where the controller became unresponsive while upgrading HDD FW.
- Fixed an issue where CPU usage in the Storage Management Hompage was being incorrectly reported as 100%.
]]>
Important Notes:
- The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
- When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD
HP recommends for remote deployment of this package that you obtain the most recent version of the Firmware Maintenance CD and follow these steps:
- Place the Firmware Maintenance CD on a USB key using the HP USB Key Creator Utility.
- Place the firmware to be updated in the directory, /compaq/swpackages on the USB key.
- Run Autorun from \_autorunutorun_win.exe on the Firmware Maintenance CD from the USB key on a system
- Select the Firmware Update tab
- Click on the Install Firmware link to launch the HP Smart Update Manager
- Follow the GUI to install the firmware on remote servers
Firmware Dependency:
HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card Firmware version 1.52 or higher, to support 6Gb SAS and 3Gb SATA drives.
Problems Fixed:
- Fixed an issue where Bios on HP ProLiant 100 series servers could not designate a boot controller when more than 1 HP Smart Array P212, P411, or P410 controller are in the server.
- Fixed an issue where the controller became unresponsive while upgrading HDD FW.
- Fixed an issue where CPU usage in the Storage Management Hompage was being incorrectly reported as 100%.
]]>
Important Notes:
- The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
- When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD
HP recommends for remote deployment of this package that you obtain the most recent version of the Firmware Maintenance CD and follow these steps:
- Place the Firmware Maintenance CD on a USB key using the HP USB Key Creator Utility.
- Place the firmware to be updated in the directory, /compaq/swpackages on the USB key.
- Run Autorun from \_autorunutorun_win.exe on the Firmware Maintenance CD from the USB key on a system
- Select the Firmware Update tab
- Click on the Install Firmware link to launch the HP Smart Update Manager
- Follow the GUI to install the firmware on remote servers
Firmware Dependency:
HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card Firmware version 1.52 or higher, to support 6Gb SAS and 3Gb SATA drives.
Problems Fixed:
- Fixed an issue where Bios on HP ProLiant 100 series servers could not designate a boot controller when more than 1 HP Smart Array P212, P411, or P410 controller are in the server.
- Fixed an issue where the controller became unresponsive while upgrading HDD FW.
- Fixed an issue where CPU usage in the Storage Management Hompage was being incorrectly reported as 100%.
]]>
Important Notes:
- The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
- When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD
HP recommends for remote deployment of this package that you obtain the most recent version of the Firmware Maintenance CD and follow these steps:
- Place the Firmware Maintenance CD on a USB key using the HP USB Key Creator Utility.
- Place the firmware to be updated in the directory, /compaq/swpackages on the USB key.
- Run Autorun from \_autorunutorun_win.exe on the Firmware Maintenance CD from the USB key on a system
- Select the Firmware Update tab
- Click on the Install Firmware link to launch the HP Smart Update Manager
- Follow the GUI to install the firmware on remote servers
Firmware Dependency:
HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card Firmware version 1.52 or higher, to support 6Gb SAS and 3Gb SATA drives.
Problems Fixed:
- Fixed an issue where Bios on HP ProLiant 100 series servers could not designate a boot controller when more than 1 HP Smart Array P212, P411, or P410 controller are in the server.
- Fixed an issue where the controller became unresponsive while upgrading HDD FW.
- Fixed an issue where CPU usage in the Storage Management Hompage was being incorrectly reported as 100%.
]]>
Important Notes:
- The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
- When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD
HP recommends for remote deployment of this package that you obtain the most recent version of the Firmware Maintenance CD and follow these steps:
- Place the Firmware Maintenance CD on a USB key using the HP USB Key Creator Utility.
- Place the firmware to be updated in the directory, /compaq/swpackages on the USB key.
- Run Autorun from \_autorunutorun_win.exe on the Firmware Maintenance CD from the USB key on a system
- Select the Firmware Update tab
- Click on the Install Firmware link to launch the HP Smart Update Manager
- Follow the GUI to install the firmware on remote servers
Firmware Dependency:
HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card Firmware version 1.52 or higher, to support 6Gb SAS and 3Gb SATA drives.
Problems Fixed:
- Fixed an issue where Bios on HP ProLiant 100 series servers could not designate a boot controller when more than 1 HP Smart Array P212, P411, or P410 controller are in the server.
- Fixed an issue where the controller became unresponsive while upgrading HDD FW.
- Fixed an issue where CPU usage in the Storage Management Hompage was being incorrectly reported as 100%.
]]>
重要な注意:
- ストレージ サブシステム(例、ドライブ、コントローラー、およびサーバー バックプレーン)は、同じデータ転送レートで動作しなければなりません。そうでない場合はシステム バンド幅はすべてのコンポーネントが受け入れ可能なレベルにネゴシエートされます。
- VMware ESX/ESXiを実行している場合、Firmware Maintenance CD上のHP Smart Update Managerを使用したオフライン アップデートのみサポートされます。
このパッケージのリモート デプロイメントには、最新のバージョンのFirmware Maintenance CDを入手して、以下の手順を実行することをおすすめします。
- HP USB Key Creator Utilityを使用して、Firmware Maintenance CDをUSBキーにコピーします。
- アップデートするファームウェアをUSBキーの/compaq/swpackagesディレクトリにコピーします。
- システムのUSBキーのFirmware Maintenance CDの\_autorunutorun_win.exeからAutorunを実行します。
- ファームウェア アップデート タブを選択します。
- [ファームウェアのインストール]リンクをクリックしてHP Smart Update Managerを実行します。
- GUIに従ってリモート サーバーにファームウェアをインストールします。
ファームウェアの関連性:
HP SmartアレイP410またはHP SmartアレイP410iに接続されたHP SASエキスパンダー カードは、6Gb SASおよび3Gb SATAドライブをサポートするために、SASエキスパンダー カード ファームウェア バージョン1.52以降が必要です。
修正された問題点:
- HP ProLiant 100シリーズ サーバー上のBIOSが2つ以上のHP SmartアレイP212、P411あるいはP410コントローラーを指定することができない問題を修正しました。
- HDD FWのアップグレード中にコントローラーが応答しなくなる問題を修正しました。
- Storage Management HompageでCPU使用率が誤って100%で報告される問題を修正しました。
]]>
중요 알림:
- 스토리지 하위 시스템의 구성 요소들(예: 드라이버, 컨트롤러 및 서버 백플레인)이 동일한 데이터 전송 속도로 작동하거나 시스템 대역폭이 모든 구성 요소에 적용될 수 있도록 조정됩니다.
- VMware ESX/ESXi 실행 시 펌웨어 유지관리 CD의 HP Smart Update Manager를 통해 업데이트하려는 경우 오프라인 업데이트만 지원됩니다.
사용자들이 최신 버전의 펌웨어 유지관리 CD를 제공받아 다음의 절차를 진행할 수 있도록 HP는 이 패키지의 원격 배포를 권장합니다:
- HP USB 키 생성 유틸리티를 통해 펌웨어 유지관리 CD를 USB 키에 저장합니다.
- 업데이트하려는 펌웨어를 USB키의 /compaq/swpackages 디렉터리에 저장합니다.
- 시스템에서 USB 키를 통해 펌웨어 유지관리 CD에 있는 \_autorunutorun_win.exe를 실행함으로써 자동실행(Autorun)을 진행합니다
- Firmware Update(펌웨어 업데이트) 탭을 선택합니다
- "펌웨어 설치" 링크를 클릭하여 HP Smart Update Manager를 실행합니다
- GUI의 설명에 따라 원격 서버에 펌웨어를 설치합니다
펌웨어 종속성:
HP Smart Array P410 또는 HP Smart Array P410i에 연결되어 있는 HP SAS 익스팬더 카드는 6Gb SAS와 3Gb SATA 드라이브 지원을 위해 1.52 이상 버전의 SAS 익스팬더 카드 펌웨어를 필요로 하고 있습니다.
해결된 문제:
- 한개 이상의 HP 스마트 어레이 P212, P411 또는 P410 컨트롤러가 서버에 설치되어 있는 경우 HP 프로라이언트 100 시리즈 서버의 BIOS가 부팅 컨트롤러를 지정하지 못하는 문제를 해결하였습니다.
- HDD FW의 업그레이드 과정에 컨트롤러가 응답을 멈추는 문제를 해결하였습니다.
- 스토리지 관리 홈페이지에서 CPU 사용률이 100%로 잘못 보고되는 문제를 해결하였습니다.
]]>
重要說明:
- 此存儲子系統的元件(例如磁碟機、控制器與伺服器背板)應當在同樣的資料傳輸速率與系統帶寬上運行,從而所有元件都處在一個可接受的水平上。
- 在執行 VMware ESX/ESXi 時,使用韌體維護 CD 上的 HP Smart Update Manager 僅支援離線更新。
惠普建議遠端部署此套件,你可以按照如下步驟操作獲取最新版本的韌體維護 CD:
- 使用HP USB 鍵創建公用程式將韌體維護 CD放入一個 USB 鍵上。
- 將想要更新的韌體放入目錄,即 USB 鍵上的 /compaq/swpackages。
- 從系統 USB 鍵的執行韌體維護 CD 上的 \_autorunutorun_win.exe 中的 Autorun
- 選擇 "韌體更新" 選項卡。
- 點選"安裝韌體"連結啟動 HP Smart Update Manager
- 根據 GUI 安裝遠端伺服器韌體
韌體相依性:
連接至 HP Smart Array P410 或 HP Smart Array P410i 的 HP SAS Expander 卡必須要有 SAS Expander 卡韌體版本 1.52 或更高版本來支援 6Gb SAS 與 3Gb SATA 磁碟機。
已解決的問題:
- 解決了 HP ProLiant 100 系列伺服器 BIOS 無法指定引導控制器的問題(伺服器上配置了不只一個 HP Smart Array P212, P411, P410 或 P410 控制器)。
- 解決了升級 HDD FW 時控制器變得無響應的問題。
- 解決了 Storage Management Homepage 的 CPU 使用率被錯誤報告為 100% 的問題。
]]>
Update Requirements:
Optional: Users should update to this firmware version if their system is affected by one of the documented fixes or if there is a desire to utilize any of the enhanced functionality provided by this version.
Important Notes:
- The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
- When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD
HP recommends for remote deployment of this package that you obtain the most recent version of the Firmware Maintenance CD and follow these steps:
- Place the Firmware Maintenance CD on a USB key using the HP USB Key Creator Utility.
- Place the firmware to be updated in the directory, /compaq/swpackages on the USB key.
- Run Autorun from \_autorunutorun_win.exe on the Firmware Maintenance CD from the USB key on a system
- Select the Firmware Update tab
- Click on the Install Firmware link to launch the HP Smart Update Manager
- Follow the GUI to install the firmware on remote servers
Firmware Dependency:
HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card Firmware version 1.52 or higher, to support 6Gb SAS and 3Gb SATA drives.
Problems Fixed:
Fixes a controller lockup at post that occurs when new unconfigured HDD’s are installed. FW version 2.76 is similar to version 2.74 except for an updated ORCA version 8.30.04.00, that contains the fix for the lockup.
]]>
Update Requirements:
Optional: Users should update to this firmware version if their system is affected by one of the documented fixes or if there is a desire to utilize any of the enhanced functionality provided by this version.
Important Notes:
- The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
- When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD
HP recommends for remote deployment of this package that you obtain the most recent version of the Firmware Maintenance CD and follow these steps:
- Place the Firmware Maintenance CD on a USB key using the HP USB Key Creator Utility.
- Place the firmware to be updated in the directory, /compaq/swpackages on the USB key.
- Run Autorun from \_autorunutorun_win.exe on the Firmware Maintenance CD from the USB key on a system
- Select the Firmware Update tab
- Click on the Install Firmware link to launch the HP Smart Update Manager
- Follow the GUI to install the firmware on remote servers
Firmware Dependency:
HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card Firmware version 1.52 or higher, to support 6Gb SAS and 3Gb SATA drives.
Problems Fixed:
Fixes a controller lockup at post that occurs when new unconfigured HDD’s are installed. FW version 2.76 is similar to version 2.74 except for an updated ORCA version 8.30.04.00, that contains the fix for the lockup.
]]>
Update Requirements:
Optional: Users should update to this firmware version if their system is affected by one of the documented fixes or if there is a desire to utilize any of the enhanced functionality provided by this version.
Important Notes:
- The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
- When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD
HP recommends for remote deployment of this package that you obtain the most recent version of the Firmware Maintenance CD and follow these steps:
- Place the Firmware Maintenance CD on a USB key using the HP USB Key Creator Utility.
- Place the firmware to be updated in the directory, /compaq/swpackages on the USB key.
- Run Autorun from \_autorunutorun_win.exe on the Firmware Maintenance CD from the USB key on a system
- Select the Firmware Update tab
- Click on the Install Firmware link to launch the HP Smart Update Manager
- Follow the GUI to install the firmware on remote servers
Firmware Dependency:
HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card Firmware version 1.52 or higher, to support 6Gb SAS and 3Gb SATA drives.
Problems Fixed:
Fixes a controller lockup at post that occurs when new unconfigured HDD’s are installed. FW version 2.76 is similar to version 2.74 except for an updated ORCA version 8.30.04.00, that contains the fix for the lockup.
]]>
Update Requirements:
Optional: Users should update to this firmware version if their system is affected by one of the documented fixes or if there is a desire to utilize any of the enhanced functionality provided by this version.
Important Notes:
- The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
- When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD
HP recommends for remote deployment of this package that you obtain the most recent version of the Firmware Maintenance CD and follow these steps:
- Place the Firmware Maintenance CD on a USB key using the HP USB Key Creator Utility.
- Place the firmware to be updated in the directory, /compaq/swpackages on the USB key.
- Run Autorun from \_autorunutorun_win.exe on the Firmware Maintenance CD from the USB key on a system
- Select the Firmware Update tab
- Click on the Install Firmware link to launch the HP Smart Update Manager
- Follow the GUI to install the firmware on remote servers
Firmware Dependency:
HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card Firmware version 1.52 or higher, to support 6Gb SAS and 3Gb SATA drives.
Problems Fixed:
Fixes a controller lockup at post that occurs when new unconfigured HDD’s are installed. FW version 2.76 is similar to version 2.74 except for an updated ORCA version 8.30.04.00, that contains the fix for the lockup.
]]>
Update Requirements:
Optional: Users should update to this firmware version if their system is affected by one of the documented fixes or if there is a desire to utilize any of the enhanced functionality provided by this version.
Important Notes:
- The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
- When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD
HP recommends for remote deployment of this package that you obtain the most recent version of the Firmware Maintenance CD and follow these steps:
- Place the Firmware Maintenance CD on a USB key using the HP USB Key Creator Utility.
- Place the firmware to be updated in the directory, /compaq/swpackages on the USB key.
- Run Autorun from \_autorunutorun_win.exe on the Firmware Maintenance CD from the USB key on a system
- Select the Firmware Update tab
- Click on the Install Firmware link to launch the HP Smart Update Manager
- Follow the GUI to install the firmware on remote servers
Firmware Dependency:
HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card Firmware version 1.52 or higher, to support 6Gb SAS and 3Gb SATA drives.
Problems Fixed:
Fixes a controller lockup at post that occurs when new unconfigured HDD’s are installed. FW version 2.76 is similar to version 2.74 except for an updated ORCA version 8.30.04.00, that contains the fix for the lockup.
]]>
Update Requirements:
Optional: Users should update to this firmware version if their system is affected by one of the documented fixes or if there is a desire to utilize any of the enhanced functionality provided by this version.
Important Notes:
- The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
- When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD
HP recommends for remote deployment of this package that you obtain the most recent version of the Firmware Maintenance CD and follow these steps:
- Place the Firmware Maintenance CD on a USB key using the HP USB Key Creator Utility.
- Place the firmware to be updated in the directory, /compaq/swpackages on the USB key.
- Run Autorun from \_autorunutorun_win.exe on the Firmware Maintenance CD from the USB key on a system
- Select the Firmware Update tab
- Click on the Install Firmware link to launch the HP Smart Update Manager
- Follow the GUI to install the firmware on remote servers
Firmware Dependency:
HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card Firmware version 1.52 or higher, to support 6Gb SAS and 3Gb SATA drives.
Problems Fixed:
Fixes a controller lockup at post that occurs when new unconfigured HDD’s are installed. FW version 2.76 is similar to version 2.74 except for an updated ORCA version 8.30.04.00, that contains the fix for the lockup.
]]>
アップデート要件:
オプション: ご使用のシステムが記載された修正に影響する場合、またはこのバージョンで提供される拡張機能を使用する場合、このファームウェア バージョンにアップデートする必要があります。
重要な注意:
- ストレージ サブシステム(例、ドライブ、コントローラー、およびサーバー バックプレーン)は、同じデータ転送レートで動作しなければなりません。そうでない場合はシステム バンド幅はすべてのコンポーネントが受け入れ可能なレベルにネゴシエートされます。
- VMware ESX/ESXiを実行している場合、Firmware Maintenance CD上のHP Smart Update Managerを使用したオフライン アップデートのみサポートされます。
このパッケージのリモート デプロイメントには、最新のバージョンのFirmware Maintenance CDを入手して、以下の手順を実行することをおすすめします。
- HP USB Key Creator Utilityを使用して、Firmware Maintenance CDをUSBキーにコピーします。
- アップデートするファームウェアをUSBキーの/compaq/swpackagesディレクトリにコピーします。
- システムのUSBキーのFirmware Maintenance CDの\_autorunutorun_win.exeからAutorunを実行します。
- ファームウェア アップデート タブを選択します。
- [ファームウェアのインストール]リンクをクリックしてHP Smart Update Managerを実行します。
- GUIに従ってリモート サーバーにファームウェアをインストールします。
ファームウェアの関連性:
HP SmartアレイP410またはHP SmartアレイP410iに接続されたHP SAS Expanderカードは、6Gb SASおよび3Gb SATAドライブをサポートするために、SAS Expanderカード ファームウェア バージョン1.52以降が必要です。
修正された問題点:
新しく設定されていないHDDfsがインストールされた場合、POST時にコントローラーのロックアップが発生する問題を修正しました。 ロックアップの修正を含んだ、ORCAバージョン8.30.04.00のアップデートを除いて、FWバージョン2.76は、バージョン2.74と同等です。
]]>
Update Requirements:
Optional: Users should update to this firmware version if their system is affected by one of the documented fixes or if there is a desire to utilize any of the enhanced functionality provided by this version.
Important Notes:
- The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
- When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD
HP recommends for remote deployment of this package that you obtain the most recent version of the Firmware Maintenance CD and follow these steps:
- Place the Firmware Maintenance CD on a USB key using the HP USB Key Creator Utility.
- Place the firmware to be updated in the directory, /compaq/swpackages on the USB key.
- Run Autorun from \_autorunutorun_win.exe on the Firmware Maintenance CD from the USB key on a system
- Select the Firmware Update tab
- Click on the Install Firmware link to launch the HP Smart Update Manager
- Follow the GUI to install the firmware on remote servers
Firmware Dependency:
HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card Firmware version 1.52 or higher, to support 6Gb SAS and 3Gb SATA drives.
Problems Fixed:
Fixes a controller lockup at post that occurs when new unconfigured HDD’s are installed. FW version 2.76 is similar to version 2.74 except for an updated ORCA version 8.30.04.00, that contains the fix for the lockup.
]]>
Update Requirements:
Optional: Users should update to this firmware version if their system is affected by one of the documented fixes or if there is a desire to utilize any of the enhanced functionality provided by this version.
Important Notes:
- The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
- When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD
HP recommends for remote deployment of this package that you obtain the most recent version of the Firmware Maintenance CD and follow these steps:
- Place the Firmware Maintenance CD on a USB key using the HP USB Key Creator Utility.
- Place the firmware to be updated in the directory, /compaq/swpackages on the USB key.
- Run Autorun from \_autorunutorun_win.exe on the Firmware Maintenance CD from the USB key on a system
- Select the Firmware Update tab
- Click on the Install Firmware link to launch the HP Smart Update Manager
- Follow the GUI to install the firmware on remote servers
Firmware Dependency:
HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card Firmware version 1.52 or higher, to support 6Gb SAS and 3Gb SATA drives.
Problems Fixed:
Fixes a controller lockup at post that occurs when new unconfigured HDD’s are installed. FW version 2.76 is similar to version 2.74 except for an updated ORCA version 8.30.04.00, that contains the fix for the lockup.
]]>
重要说明 -
- 存储子系统(例如,磁盘、控制器和服务器背板)的组件应以相同的数据传输速率或者系统带宽运行,并可向下浏览至素有组件的可接受层级。
- 运行 VMware ESX/ESXi 时,仅固件维护光盘中的 HP Smart Update Manager 才支持离线更新功能。
惠普建议远程部署通过最新版本 Firmware Maintenance CD 获取的软件包,步骤如下:
- 使用 USB Key Creator 实用工具将 Firmware Maintenance CD 置于 U 盘上。
- 将更新使用的必需固件放在 U 盘上的 /compaq/swpackages 目录中。
- 通过系统中的 USB 密钥从 Firmware Maintenance CD 中的 \_autorunutorun_win.exe 运行 Autorun。
- 选择 "Firmware Update" 选项卡。
- 点击 "Install Firmware" 链接启动 HP Smart Update Manager。
- 遵循 GUI 在远程服务器上安装固件
固件依赖条件:
连接至 HP Smart Array P410 或者 HP Smart Array P410i 的 HP SAS Expander Card 要求使用 SAS Expander Card 固件版本 1.52 或者更高版本以支持 6Gb SAS 和 3Gb SATA 驱动器。
增强功能/新功能:
新增对仅连接至 HP Smart Array P410i 的 512MB 和 1G Flash Backed Write Cache (FBWC) 的支持。
]]>
Important Notes -
- The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
- When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD
HP recommends for remote deployment of this package that you obtain the most recent version of the Firmware Maintenance CD and follow these steps:
- Place the Firmware Maintenance CD on a USB key using the HP USB Key Creator Utility.
- Place the firmware to be updated in the directory, /compaq/swpackages on the USB key.
- Run Autorun from \_autorunutorun_win.exe on the Firmware Maintenance CD from the USB key on a system
- Select the Firmware Update tab
- Click on the Install Firmware link to launch the HP Smart Update Manager
- Follow the GUI to install the firmware on remote servers
Firmware Dependency:
HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card Firmware version 1.52 or higher, to support 6Gb SAS and 3Gb SATA drives.
Enhancements/New Features:
Added support for 512MB and 1G Flash Backed Write Cache (FBWC) attached to the HP Smart Array P410i only.
]]>
Important Notes -
- The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
- When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD
HP recommends for remote deployment of this package that you obtain the most recent version of the Firmware Maintenance CD and follow these steps:
- Place the Firmware Maintenance CD on a USB key using the HP USB Key Creator Utility.
- Place the firmware to be updated in the directory, /compaq/swpackages on the USB key.
- Run Autorun from \_autorunutorun_win.exe on the Firmware Maintenance CD from the USB key on a system
- Select the Firmware Update tab
- Click on the Install Firmware link to launch the HP Smart Update Manager
- Follow the GUI to install the firmware on remote servers
Firmware Dependency:
HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card Firmware version 1.52 or higher, to support 6Gb SAS and 3Gb SATA drives.
Enhancements/New Features:
Added support for 512MB and 1G Flash Backed Write Cache (FBWC) attached to the HP Smart Array P410i only.
]]>
Important Notes -
- The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
- When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD
HP recommends for remote deployment of this package that you obtain the most recent version of the Firmware Maintenance CD and follow these steps:
- Place the Firmware Maintenance CD on a USB key using the HP USB Key Creator Utility.
- Place the firmware to be updated in the directory, /compaq/swpackages on the USB key.
- Run Autorun from \_autorunutorun_win.exe on the Firmware Maintenance CD from the USB key on a system
- Select the Firmware Update tab
- Click on the Install Firmware link to launch the HP Smart Update Manager
- Follow the GUI to install the firmware on remote servers
Firmware Dependency:
HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card Firmware version 1.52 or higher, to support 6Gb SAS and 3Gb SATA drives.
Enhancements/New Features:
Added support for 512MB and 1G Flash Backed Write Cache (FBWC) attached to the HP Smart Array P410i only.
]]>
Important Notes -
- The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
- When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD
HP recommends for remote deployment of this package that you obtain the most recent version of the Firmware Maintenance CD and follow these steps:
- Place the Firmware Maintenance CD on a USB key using the HP USB Key Creator Utility.
- Place the firmware to be updated in the directory, /compaq/swpackages on the USB key.
- Run Autorun from \_autorunutorun_win.exe on the Firmware Maintenance CD from the USB key on a system
- Select the Firmware Update tab
- Click on the Install Firmware link to launch the HP Smart Update Manager
- Follow the GUI to install the firmware on remote servers
Firmware Dependency:
HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card Firmware version 1.52 or higher, to support 6Gb SAS and 3Gb SATA drives.
Enhancements/New Features:
Added support for 512MB and 1G Flash Backed Write Cache (FBWC) attached to the HP Smart Array P410i only.
]]>
Important Notes -
- The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
- When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD
HP recommends for remote deployment of this package that you obtain the most recent version of the Firmware Maintenance CD and follow these steps:
- Place the Firmware Maintenance CD on a USB key using the HP USB Key Creator Utility.
- Place the firmware to be updated in the directory, /compaq/swpackages on the USB key.
- Run Autorun from \_autorunutorun_win.exe on the Firmware Maintenance CD from the USB key on a system
- Select the Firmware Update tab
- Click on the Install Firmware link to launch the HP Smart Update Manager
- Follow the GUI to install the firmware on remote servers
Firmware Dependency:
HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card Firmware version 1.52 or higher, to support 6Gb SAS and 3Gb SATA drives.
Enhancements/New Features:
Added support for 512MB and 1G Flash Backed Write Cache (FBWC) attached to the HP Smart Array P410i only.
]]>
重要な注意
- ストレージ サブシステム(例、ドライブ、コントローラー、およびサーバー バックプレーン)は、同じデータ転送レートで動作しなければなりません。そうでない場合はシステム バンド幅はすべてのコンポーネントが受け入れ可能なレベルにネゴシエートされます。
- VMware ESX/ESXiを実行している場合、Firmware Maintenance CD上のHP Smart Update Managerを使用したオフライン アップデートのみサポートされます。
このパッケージのリモート デプロイメントには、最新のバージョンのFirmware Maintenance CDを入手して、以下の手順を実行することをおすすめします。
- HP USB Key Utility(英語)を使用して、Firmware Maintenance CD(英語)をUSBキーにコピーします。
- アップデートするファームウェアをUSBキーの/compaq/swpackagesディレクトリにコピーします。
- システムのUSBキーのFirmware Maintenance CDの\_autorunutorun_win.exeからAutorunを実行します。
- ファームウェア アップデート タブを選択します。
- [ファームウェアのインストール]リンクをクリックしてHP Smart Update Managerを実行します。
- GUIに従ってリモート サーバーにファームウェアをインストールします。
ファームウェアの関連性:
HP SmartアレイP410またはHP SmartアレイP410iに接続されたHP SAS Expanderカードは、6Gb SASおよび3Gb SATAドライブをサポートするために、SAS Expanderカード ファームウェア バージョン1.52以降が必要です。
改善点/新しい機能:
HP SmartアレイP410iに搭載する、512MBと1GBのフラッシュバック式ライトキャッシュ(FBWC)のサポートを追加しました。
]]>
중요 알림 -
- 스토리지 하위 시스템의 구성 요소들(예: 드라이버, 컨트롤러 및 서버 백플레인)이 동일한 데이터 전송 속도로 작동하거나 시스템 대역폭이 모든 구성 요소에 적용될 수 있도록 조정됩니다.
- VMware ESX/ESXi 실행 시 펌웨어 유지관리 CD의 HP Smart Update Manager를 통해 업데이트하려는 경우 오프라인 업데이트만 지원됩니다.
사용자들이 최신 버전의 펌웨어 유지관리 CD를 제공받아 다음의 절차를 진행할 수 있도록 HP는 이 패키지의 원격 배포를 권장합니다:
- HP USB 키 생성 유틸리티를 통해 펌웨어 유지관리 CD를 USB 키에 저장합니다.
- 업데이트하려는 펌웨어를 USB키의 /compaq/swpackages 디렉터리에 저장합니다.
- 시스템에서 USB 키를 통해 펌웨어 유지관리 CD에 있는 \_autorunutorun_win.exe를 실행함으로써 자동실행(Autorun)을 진행합니다
- Firmware Update(펌웨어 업데이트) 탭을 선택합니다
- "펌웨어 설치" 링크를 클릭하여 HP Smart Update Manager를 실행합니다
- GUI의 설명에 따라 원격 서버에 펌웨어를 설치합니다
펌웨어 종속성:
HP Smart Array P410 또는 HP Smart Array P410i에 연결되어 있는 HP SAS 익스팬더 카드는 6Gb SAS와 3Gb SATA 드라이브 지원을 위해 1.52 이상 버전의 SAS 익스팬더 카드 펌웨어를 필요로 하고 있습니다.
향상된/새로운 기능:
HP Smart Array P410i에만 장착되어 있는 512MB 및 1G Flash Backed Write Cache(FBWC)에 대한 지원을 추가하였습니다.
]]>
重要說明
- 此存儲子系統的元件(例如磁碟機、控制器與伺服器背板)應當在同樣的資料傳輸速率與系統帶寬上運行,從而所有元件都處在一個可接受的水平上。
- 在執行 VMware ESX/ESXi 時,使用韌體維護 CD 上的 HP Smart Update Manager 僅支援離線更新。
惠普建議遠端部署此套件,你可以按照如下步驟操作獲取最新版本的韌體維護 CD:
- 使用HP USB 鍵創建公用程式將韌體維護 CD放入一個 USB 鍵上。
- 將想要更新的韌體放入目錄,即 USB 鍵上的 /compaq/swpackages。
- 從系統 USB 鍵的執行韌體維護 CD 上的 \_autorunutorun_win.exe 中的 Autorun
- 選擇 "韌體更新" 選項卡。
- 點選"安裝韌體"連結啟動 HP Smart Update Manager
- 根據 GUI 安裝遠端伺服器韌體
韌體相依性:
連接至 HP Smart Array P410 或 HP Smart Array P410i 的 HP SAS Expander 卡必須要有 SAS Expander 卡韌體版本 1.52 或更高版本來支援 6Gb SAS 與 3Gb SATA 磁碟機。
改進/新功能:
新增了對連接至 HP Smart Array P410i 的 512MB 與 1G Flash Backed Write Cache (FBWC) 的支援。
]]>
更新要求:
或者: 若系统受上述问题之一影响且需要使用由此版本提供的增强功能,用户则需将固件更新至此版本。
重要说明 -
- 存储子系统(例如,磁盘、控制器和服务器背板)的组件应以相同的数据传输速率或者系统带宽运行,并可向下浏览至素有组件的可接受层级。
- 运行 VMware ESX/ESXi 时,仅固件维护光盘中的 HP Smart Update Manager 才支持离线更新功能。
惠普建议远程部署通过最新版本 Firmware Maintenance CD 获取的软件包,步骤如下:
- 使用 USB Key Creator 实用工具将 Firmware Maintenance CD 置于 U 盘上。
- 将更新使用的必需固件放在 U 盘上的 /compaq/swpackages 目录中。
- 通过系统中的 USB 密钥从 Firmware Maintenance CD 中的 \_autorunutorun_win.exe 运行 Autorun。
- 选择 "Firmware Update" 选项卡。
- 点击 "Install Firmware" 链接启动 HP Smart Update Manager。
- 遵循 GUI 在远程服务器上安装固件
固件依赖条件:
连接至 HP Smart Array P410 或者 HP Smart Array P410i 的 HP SAS Expander Card 要求使用 SAS Expander Card 固件版本 1.52 或者更高版本以支持 6Gb SAS 和 3Gb SATA 驱动器。
增强功能/新功能:
新增对仅连接至 HP Smart Array P410i 的 512MB 和 1G Flash Backed Write Cache (FBWC) 的支持。
]]>
Update Requirements:
Optional: Users should update to this firmware version if their system is affected by one of the documented fixes or if there is a desire to utilize any of the enhanced functionality provided by this version.
Important Notes -
- The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
- When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD
HP recommends for remote deployment of this package that you obtain the most recent version of the Firmware Maintenance CD and follow these steps:
- Place the Firmware Maintenance CD on a USB key using the HP USB Key Creator Utility.
- Place the firmware to be updated in the directory, /compaq/swpackages on the USB key.
- Run Autorun from \_autorunutorun_win.exe on the Firmware Maintenance CD from the USB key on a system
- Select the Firmware Update tab
- Click on the Install Firmware link to launch the HP Smart Update Manager
- Follow the GUI to install the firmware on remote servers
Firmware Dependency:
HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card Firmware version 1.52 or higher, to support 6Gb SAS and 3Gb SATA drives.
Enhancements/New Features:
Added support for 512MB and 1G Flash Backed Write Cache (FBWC) attached to the HP Smart Array P410i only.
]]>
Update Requirements:
Optional: Users should update to this firmware version if their system is affected by one of the documented fixes or if there is a desire to utilize any of the enhanced functionality provided by this version.
Important Notes -
- The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
- When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD
HP recommends for remote deployment of this package that you obtain the most recent version of the Firmware Maintenance CD and follow these steps:
- Place the Firmware Maintenance CD on a USB key using the HP USB Key Creator Utility.
- Place the firmware to be updated in the directory, /compaq/swpackages on the USB key.
- Run Autorun from \_autorunutorun_win.exe on the Firmware Maintenance CD from the USB key on a system
- Select the Firmware Update tab
- Click on the Install Firmware link to launch the HP Smart Update Manager
- Follow the GUI to install the firmware on remote servers
Firmware Dependency:
HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card Firmware version 1.52 or higher, to support 6Gb SAS and 3Gb SATA drives.
Enhancements/New Features:
Added support for 512MB and 1G Flash Backed Write Cache (FBWC) attached to the HP Smart Array P410i only.
]]>
Update Requirements:
Optional: Users should update to this firmware version if their system is affected by one of the documented fixes or if there is a desire to utilize any of the enhanced functionality provided by this version.
Important Notes -
- The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
- When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD
HP recommends for remote deployment of this package that you obtain the most recent version of the Firmware Maintenance CD and follow these steps:
- Place the Firmware Maintenance CD on a USB key using the HP USB Key Creator Utility.
- Place the firmware to be updated in the directory, /compaq/swpackages on the USB key.
- Run Autorun from \_autorunutorun_win.exe on the Firmware Maintenance CD from the USB key on a system
- Select the Firmware Update tab
- Click on the Install Firmware link to launch the HP Smart Update Manager
- Follow the GUI to install the firmware on remote servers
Firmware Dependency:
HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card Firmware version 1.52 or higher, to support 6Gb SAS and 3Gb SATA drives.
Enhancements/New Features:
Added support for 512MB and 1G Flash Backed Write Cache (FBWC) attached to the HP Smart Array P410i only.
]]>
Update Requirements:
Optional: Users should update to this firmware version if their system is affected by one of the documented fixes or if there is a desire to utilize any of the enhanced functionality provided by this version.
Important Notes -
- The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
- When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD
HP recommends for remote deployment of this package that you obtain the most recent version of the Firmware Maintenance CD and follow these steps:
- Place the Firmware Maintenance CD on a USB key using the HP USB Key Creator Utility.
- Place the firmware to be updated in the directory, /compaq/swpackages on the USB key.
- Run Autorun from \_autorunutorun_win.exe on the Firmware Maintenance CD from the USB key on a system
- Select the Firmware Update tab
- Click on the Install Firmware link to launch the HP Smart Update Manager
- Follow the GUI to install the firmware on remote servers
Firmware Dependency:
HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card Firmware version 1.52 or higher, to support 6Gb SAS and 3Gb SATA drives.
Enhancements/New Features:
Added support for 512MB and 1G Flash Backed Write Cache (FBWC) attached to the HP Smart Array P410i only.
]]>
Update Requirements:
Optional: Users should update to this firmware version if their system is affected by one of the documented fixes or if there is a desire to utilize any of the enhanced functionality provided by this version.
Important Notes -
- The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
- When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD
HP recommends for remote deployment of this package that you obtain the most recent version of the Firmware Maintenance CD and follow these steps:
- Place the Firmware Maintenance CD on a USB key using the HP USB Key Creator Utility.
- Place the firmware to be updated in the directory, /compaq/swpackages on the USB key.
- Run Autorun from \_autorunutorun_win.exe on the Firmware Maintenance CD from the USB key on a system
- Select the Firmware Update tab
- Click on the Install Firmware link to launch the HP Smart Update Manager
- Follow the GUI to install the firmware on remote servers
Firmware Dependency:
HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card Firmware version 1.52 or higher, to support 6Gb SAS and 3Gb SATA drives.
Enhancements/New Features:
Added support for 512MB and 1G Flash Backed Write Cache (FBWC) attached to the HP Smart Array P410i only.
]]>
アップデート要件:
オプション: ご使用のシステムが記載された修正に影響する場合、またはこのバージョンで提供される拡張機能を使用する場合、このファームウェア バージョンにアップデートする必要があります。
重要な注意
- ストレージ サブシステム(例、ドライブ、コントローラー、およびサーバー バックプレーン)は、同じデータ転送レートで動作しなければなりません。そうでない場合はシステム バンド幅はすべてのコンポーネントが受け入れ可能なレベルにネゴシエートされます。
- VMware ESX/ESXiを実行している場合、Firmware Maintenance CD上のHP Smart Update Managerを使用したオフライン アップデートのみサポートされます。
このパッケージのリモート デプロイメントには、最新のバージョンのFirmware Maintenance CDを入手して、以下の手順を実行することをおすすめします。
- HP USB Key Creator Utilityを使用して、Firmware Maintenance CDをUSBキーにコピーします。
- アップデートするファームウェアをUSBキーの/compaq/swpackagesディレクトリにコピーします。
- システムのUSBキーのFirmware Maintenance CDの\_autorunutorun_win.exeからAutorunを実行します。
- ファームウェア アップデート タブを選択します。
- [ファームウェアのインストール]リンクをクリックしてHP Smart Update Managerを実行します。
- GUIに従ってリモート サーバーにファームウェアをインストールします。
ファームウェアの関連性:
HP SmartアレイP410またはHP SmartアレイP410iに接続されたHP SAS Expanderカードは、6Gb SASおよび3Gb SATAドライブをサポートするために、SAS Expanderカード ファームウェア バージョン1.52以降が必要です。
改善点/新しい機能:
HP SmartアレイP410iに搭載する、512MBと1GBのフラッシュバック式ライトキャッシュ(FBWC)のサポートを追加しました。
]]>
업데이트 요구 사항:
선택사항: 사용자 시스템이 문서화되어 있는 수정사항의 영향을 받거나 수정 버전에 제공되어 있는 향상된 기능을 적용하고자 하는 경우 펌웨어 버전을 업데이트해야 합니다.
중요 알림 -
- 스토리지 하위 시스템의 구성 요소들(예: 드라이버, 컨트롤러 및 서버 백플레인)이 동일한 데이터 전송 속도로 작동하거나 시스템 대역폭이 모든 구성 요소에 적용될 수 있도록 조정됩니다.
- VMware ESX/ESXi 실행 시 펌웨어 유지관리 CD의 HP Smart Update Manager를 통해 업데이트하려는 경우 오프라인 업데이트만 지원됩니다.
사용자들이 최신 버전의 펌웨어 유지관리 CD를 제공받아 다음의 절차를 진행할 수 있도록 HP는 이 패키지의 원격 배포를 권장합니다:
- HP USB 키 생성 유틸리티를 통해 펌웨어 유지관리 CD를 USB 키에 저장합니다.
- 업데이트하려는 펌웨어를 USB키의 /compaq/swpackages 디렉터리에 저장합니다.
- 시스템에서 USB 키를 통해 펌웨어 유지관리 CD에 있는 \_autorunutorun_win.exe를 실행함으로써 자동실행(Autorun)을 진행합니다
- Firmware Update(펌웨어 업데이트) 탭을 선택합니다
- "펌웨어 설치" 링크를 클릭하여 HP Smart Update Manager를 실행합니다
- GUI의 설명에 따라 원격 서버에 펌웨어를 설치합니다
펌웨어 종속성:
HP Smart Array P410 또는 HP Smart Array P410i에 연결되어 있는 HP SAS 익스팬더 카드는 6Gb SAS와 3Gb SATA 드라이브 지원을 위해 1.52 이상 버전의 SAS 익스팬더 카드 펌웨어를 필요로 하고 있습니다.
향상된/새로운 기능:
HP Smart Array P410i에만 장착되어 있는 512MB 및 1G Flash Backed Write Cache(FBWC)에 대한 지원을 추가하였습니다.
]]>
更新要求:
選用: 如果使用者系統受到本文所述修正程式影響,或者有必要利用此版本提供的增強功能,則使用者應當更新此韌體版本。
重要說明
- 此儲存子系統的元件(例如磁碟機、控制器與伺服器背板)應當在同樣的資料傳輸速率與系統頻寬上運行,從而所有元件都處於一個可接受的水準上。
- 在執行 VMware ESX/ESXi 時,使用韌體維護 CD 上的 HP Smart Update Manager 僅支援離線更新
HP 建議遠端部署此套件,您可以按照如下步驟操作取得最新版本的韌體維護 CD:
- 使用 HP USB 隨身碟建立公用程式將韌體維護 CD 放入 USB 隨身碟上。
- 將想要更新的韌體放入目錄,即 USB 隨身碟上的 /compaq/swpackages。
- 從系統 USB 隨身碟的執行韌體維護 CD 上的 \_autorunutorun_win.exe 中的 Autorun
- 選擇「韌體更新」標籤
- 點選「安裝韌體」連結啟動 HP Smart Update Manager
- 根據 GUI 安裝遠端伺服器韌體
韌體相依性:
連接至 HP Smart Array P410 或 HP Smart Array P410i 的 HP SAS Expander 卡必須要有 SAS Expander 卡韌體版本 1.52 或更高版本來支援 6Gb SAS 與 3Gb SATA 磁碟機。
增強/新功能:
新增了對連接至 HP Smart Array P410i 的 512MB 與 1G Flash Backed Write Cache (FBWC) 的支援。
]]>
Added support for attaching the HP Smart Array P212 and the HP Smart Array P411 to an HP StorageWorks 600 Modular Disk System (MDS600)
Improved performance in SATA Hard drive configurations.
Improved performance during offset non-contiguous writes.]]>
Added support for attaching the HP Smart Array P212 and the HP Smart Array P411 to an HP StorageWorks 600 Modular Disk System (MDS600)
Improved performance in SATA Hard drive configurations.
Improved performance during offset non-contiguous writes.]]>
Added support for attaching the HP Smart Array P212 and the HP Smart Array P411 to an HP StorageWorks 600 Modular Disk System (MDS600)
Improved performance in SATA Hard drive configurations.
Improved performance during offset non-contiguous writes.]]>
Added support for attaching the HP Smart Array P212 and the HP Smart Array P411 to an HP StorageWorks 600 Modular Disk System (MDS600)
Improved performance in SATA Hard drive configurations.
Improved performance during offset non-contiguous writes.]]>
Added support for attaching the HP Smart Array P212 and the HP Smart Array P411 to an HP StorageWorks 600 Modular Disk System (MDS600)
Improved performance in SATA Hard drive configurations.
Improved performance during offset non-contiguous writes.]]>
Added support for attaching the HP Smart Array P212 and the HP Smart Array P411 to an HP StorageWorks 600 Modular Disk System (MDS600)
Improved performance in SATA Hard drive configurations.
Improved performance during offset non-contiguous writes.]]>
HP SmartアレイP212およびHP SmartアレイP411をHP StorageWorks Modular Disk System 600(MDS600)に接続するためのサポートを追加しました。
SATAハードディスク ドライブ構成のパフォーマンスを向上しました。
オフセット非隣接書き込み中のパフォーマンスを改善しました。]]>
Added support for attaching the HP Smart Array P212 and the HP Smart Array P411 to an HP StorageWorks 600 Modular Disk System (MDS600)
Improved performance in SATA Hard drive configurations.
Improved performance during offset non-contiguous writes.]]>
Added support for attaching the HP Smart Array P212 and the HP Smart Array P411 to an HP StorageWorks 600 Modular Disk System (MDS600)
Improved performance in SATA Hard drive configurations.
Improved performance during offset non-contiguous writes.]]>
Update Requirements:
Critical: HP requires users to update to this firmware version immediately.
If you have previously updated to version 2.72, another update is not needed. The changes for 2.72(B) did not affect FW functionality.
Important Notes:
- HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card Firmware version 1.52 or higher, to support 6Gb SAS and 3Gb SATA drives.
- The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
- When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD
HP recommends for remote deployment of this package that you obtain the most recent version of the Firmware Maintenance CD and follow these steps:
- Place the Firmware Maintenance CD on a USB key using the HP USB Key Creator Utility.
- Place the firmware to be updated in the directory, /compaq/swpackages on the USB key.
- Run Autorun from \_autorunutorun_win.exe on the Firmware Maintenance CD from the USB key on a system
- Select the Firmware Update tab
- Click on the Install Firmware link to launch the HP Smart Update Manager
- Follow the GUI to install the firmware on remote servers
Problems Fixed:
- Fixed an issue where 3G SATA drives were not being detected at post on the ProLiant DL180G6 with a 12 drive backplane
- Fixed an issue where erroneous drive hot remove events were being reported causing unnecessary drive rebuilds.
- Fixed an issue where Novell Netware volumes failed to mount with 2.00 HP Smart Array FW.
]]>
Update Requirements:
Critical: HP requires users to update to this firmware version immediately.
If you have previously updated to version 2.72, another update is not needed. The changes for 2.72(B) did not affect FW functionality.
Important Notes:
- HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card Firmware version 1.52 or higher, to support 6Gb SAS and 3Gb SATA drives.
- The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
- When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD
HP recommends for remote deployment of this package that you obtain the most recent version of the Firmware Maintenance CD and follow these steps:
- Place the Firmware Maintenance CD on a USB key using the HP USB Key Creator Utility.
- Place the firmware to be updated in the directory, /compaq/swpackages on the USB key.
- Run Autorun from \_autorunutorun_win.exe on the Firmware Maintenance CD from the USB key on a system
- Select the Firmware Update tab
- Click on the Install Firmware link to launch the HP Smart Update Manager
- Follow the GUI to install the firmware on remote servers
Problems Fixed:
- Fixed an issue where 3G SATA drives were not being detected at post on the ProLiant DL180G6 with a 12 drive backplane
- Fixed an issue where erroneous drive hot remove events were being reported causing unnecessary drive rebuilds.
- Fixed an issue where Novell Netware volumes failed to mount with 2.00 HP Smart Array FW.
]]>
Update Requirements:
Critical: HP requires users to update to this firmware version immediately.
If you have previously updated to version 2.72, another update is not needed. The changes for 2.72(B) did not affect FW functionality.
Important Notes:
- HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card Firmware version 1.52 or higher, to support 6Gb SAS and 3Gb SATA drives.
- The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
- When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD
HP recommends for remote deployment of this package that you obtain the most recent version of the Firmware Maintenance CD and follow these steps:
- Place the Firmware Maintenance CD on a USB key using the HP USB Key Creator Utility.
- Place the firmware to be updated in the directory, /compaq/swpackages on the USB key.
- Run Autorun from \_autorunutorun_win.exe on the Firmware Maintenance CD from the USB key on a system
- Select the Firmware Update tab
- Click on the Install Firmware link to launch the HP Smart Update Manager
- Follow the GUI to install the firmware on remote servers
Problems Fixed:
- Fixed an issue where 3G SATA drives were not being detected at post on the ProLiant DL180G6 with a 12 drive backplane
- Fixed an issue where erroneous drive hot remove events were being reported causing unnecessary drive rebuilds.
- Fixed an issue where Novell Netware volumes failed to mount with 2.00 HP Smart Array FW.
]]>
Update Requirements:
Critical: HP requires users to update to this firmware version immediately.
If you have previously updated to version 2.72, another update is not needed. The changes for 2.72(B) did not affect FW functionality.
Important Notes:
- HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card Firmware version 1.52 or higher, to support 6Gb SAS and 3Gb SATA drives.
- The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
- When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD
HP recommends for remote deployment of this package that you obtain the most recent version of the Firmware Maintenance CD and follow these steps:
- Place the Firmware Maintenance CD on a USB key using the HP USB Key Creator Utility.
- Place the firmware to be updated in the directory, /compaq/swpackages on the USB key.
- Run Autorun from \_autorunutorun_win.exe on the Firmware Maintenance CD from the USB key on a system
- Select the Firmware Update tab
- Click on the Install Firmware link to launch the HP Smart Update Manager
- Follow the GUI to install the firmware on remote servers
Problems Fixed:
- Fixed an issue where 3G SATA drives were not being detected at post on the ProLiant DL180G6 with a 12 drive backplane
- Fixed an issue where erroneous drive hot remove events were being reported causing unnecessary drive rebuilds.
- Fixed an issue where Novell Netware volumes failed to mount with 2.00 HP Smart Array FW.
]]>
Update Requirements:
Critical: HP requires users to update to this firmware version immediately.
If you have previously updated to version 2.72, another update is not needed. The changes for 2.72(B) did not affect FW functionality.
Important Notes:
- HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card Firmware version 1.52 or higher, to support 6Gb SAS and 3Gb SATA drives.
- The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
- When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD
HP recommends for remote deployment of this package that you obtain the most recent version of the Firmware Maintenance CD and follow these steps:
- Place the Firmware Maintenance CD on a USB key using the HP USB Key Creator Utility.
- Place the firmware to be updated in the directory, /compaq/swpackages on the USB key.
- Run Autorun from \_autorunutorun_win.exe on the Firmware Maintenance CD from the USB key on a system
- Select the Firmware Update tab
- Click on the Install Firmware link to launch the HP Smart Update Manager
- Follow the GUI to install the firmware on remote servers
Problems Fixed:
- Fixed an issue where 3G SATA drives were not being detected at post on the ProLiant DL180G6 with a 12 drive backplane
- Fixed an issue where erroneous drive hot remove events were being reported causing unnecessary drive rebuilds.
- Fixed an issue where Novell Netware volumes failed to mount with 2.00 HP Smart Array FW.
]]>
Update Requirements:
Critical: HP requires users to update to this firmware version immediately.
If you have previously updated to version 2.72, another update is not needed. The changes for 2.72(B) did not affect FW functionality.
Important Notes:
- HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card Firmware version 1.52 or higher, to support 6Gb SAS and 3Gb SATA drives.
- The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
- When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD
HP recommends for remote deployment of this package that you obtain the most recent version of the Firmware Maintenance CD and follow these steps:
- Place the Firmware Maintenance CD on a USB key using the HP USB Key Creator Utility.
- Place the firmware to be updated in the directory, /compaq/swpackages on the USB key.
- Run Autorun from \_autorunutorun_win.exe on the Firmware Maintenance CD from the USB key on a system
- Select the Firmware Update tab
- Click on the Install Firmware link to launch the HP Smart Update Manager
- Follow the GUI to install the firmware on remote servers
Problems Fixed:
- Fixed an issue where 3G SATA drives were not being detected at post on the ProLiant DL180G6 with a 12 drive backplane
- Fixed an issue where erroneous drive hot remove events were being reported causing unnecessary drive rebuilds.
- Fixed an issue where Novell Netware volumes failed to mount with 2.00 HP Smart Array FW.
]]>
アップデート要件:
クリティカル: HPではファームウェア バージョンをすぐにアップデートすることを推奨しています。
すでにバージョン2.72にアップデートしている場合、アップデートは必要ありません。 2.72(B) の変更は、FW機能に影響ありません。
重要な注意:
- HP SmartアレイP410またはHP SmartアレイP410iに接続されたHP SAS Expanderカードは、6Gb SASおよび3Gb SATAドライブをサポートするために、SAS Expanderカード ファームウェア バージョン1.52以降が必要です。
- ストレージ サブシステム(例、ドライブ、コントローラー、およびサーバー バックプレーン)は、同じデータ転送レートで動作しなければなりません。そうでない場合はシステム バンド幅はすべてのコンポーネントが受け入れ可能なレベルにネゴシエートされます。
- VMware ESX/ESXiを実行している場合、Firmware Maintenance CD上のHP Smart Update Managerを使用したオフライン アップデートのみサポートされます。
このパッケージのリモート デプロイメントには、最新のバージョンのFirmware Maintenance CDを入手して、以下の手順を実行することをおすすめします。
- HP USB Key Creator Utilityを使用して、Firmware Maintenance CDをUSBキーにコピーします。
- アップデートするファームウェアをUSBキーの/compaq/swpackagesディレクトリにコピーします。
- システムのUSBキーのFirmware Maintenance CDの\_autorunutorun_win.exeからAutorunを実行します。
- ファームウェア アップデート タブを選択します。
- [ファームウェアのインストール]リンクをクリックしてHP Smart Update Managerを実行します。
- GUIに従ってリモート サーバーにファームウェアをインストールします。
修正された問題点:
- 12ドライブ バックプレーンのProLiant DL180G6で3G SATAドライブがPOSTで検出されない問題を修正しました。
- ホット リムーブ イベントが間違って報告されて、必要のないドライブの再構築が発生する問題を修正しました。
- Novell Netwareボリュームが2.00 HP Smartアレイ ファームウェアでマウントに失敗する問題を修正しました。
]]>
Update Requirements:
Critical: HP requires users to update to this firmware version immediately.
If you have previously updated to version 2.72, another update is not needed. The changes for 2.72(B) did not affect FW functionality.
Important Notes:
- HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card Firmware version 1.52 or higher, to support 6Gb SAS and 3Gb SATA drives.
- The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
- When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD
HP recommends for remote deployment of this package that you obtain the most recent version of the Firmware Maintenance CD and follow these steps:
- Place the Firmware Maintenance CD on a USB key using the HP USB Key Creator Utility.
- Place the firmware to be updated in the directory, /compaq/swpackages on the USB key.
- Run Autorun from \_autorunutorun_win.exe on the Firmware Maintenance CD from the USB key on a system
- Select the Firmware Update tab
- Click on the Install Firmware link to launch the HP Smart Update Manager
- Follow the GUI to install the firmware on remote servers
Problems Fixed:
- Fixed an issue where 3G SATA drives were not being detected at post on the ProLiant DL180G6 with a 12 drive backplane
- Fixed an issue where erroneous drive hot remove events were being reported causing unnecessary drive rebuilds.
- Fixed an issue where Novell Netware volumes failed to mount with 2.00 HP Smart Array FW.
]]>
Update Requirements:
Critical: HP requires users to update to this firmware version immediately.
If you have previously updated to version 2.72, another update is not needed. The changes for 2.72(B) did not affect FW functionality.
Important Notes:
- HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card Firmware version 1.52 or higher, to support 6Gb SAS and 3Gb SATA drives.
- The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
- When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD
HP recommends for remote deployment of this package that you obtain the most recent version of the Firmware Maintenance CD and follow these steps:
- Place the Firmware Maintenance CD on a USB key using the HP USB Key Creator Utility.
- Place the firmware to be updated in the directory, /compaq/swpackages on the USB key.
- Run Autorun from \_autorunutorun_win.exe on the Firmware Maintenance CD from the USB key on a system
- Select the Firmware Update tab
- Click on the Install Firmware link to launch the HP Smart Update Manager
- Follow the GUI to install the firmware on remote servers
Problems Fixed:
- Fixed an issue where 3G SATA drives were not being detected at post on the ProLiant DL180G6 with a 12 drive backplane
- Fixed an issue where erroneous drive hot remove events were being reported causing unnecessary drive rebuilds.
- Fixed an issue where Novell Netware volumes failed to mount with 2.00 HP Smart Array FW.
]]>
Added support for attaching the HP Smart Array P212 and the HP Smart Array P411 to an HP StorageWorks 600 Modular Disk System (MDS600)
Improved performance in SATA Hard drive configurations.
Improved performance during offset non-contiguous writes.]]>
Added support for attaching the HP Smart Array P212 and the HP Smart Array P411 to an HP StorageWorks 600 Modular Disk System (MDS600)
Improved performance in SATA Hard drive configurations.
Improved performance during offset non-contiguous writes.]]>
Added support for attaching the HP Smart Array P212 and the HP Smart Array P411 to an HP StorageWorks 600 Modular Disk System (MDS600)
Improved performance in SATA Hard drive configurations.
Improved performance during offset non-contiguous writes.]]>
Added support for attaching the HP Smart Array P212 and the HP Smart Array P411 to an HP StorageWorks 600 Modular Disk System (MDS600)
Improved performance in SATA Hard drive configurations.
Improved performance during offset non-contiguous writes.]]>
Added support for attaching the HP Smart Array P212 and the HP Smart Array P411 to an HP StorageWorks 600 Modular Disk System (MDS600)
Improved performance in SATA Hard drive configurations.
Improved performance during offset non-contiguous writes.]]>
Added support for attaching the HP Smart Array P212 and the HP Smart Array P411 to an HP StorageWorks 600 Modular Disk System (MDS600)
Improved performance in SATA Hard drive configurations.
Improved performance during offset non-contiguous writes.]]>
HP SmartアレイP212およびHP SmartアレイP411をHP StorageWorks Modular Disk System 600(MDS600)に接続するためのサポートを追加しました。
SATAハードディスク ドライブ構成のパフォーマンスを向上しました。
オフセット非隣接書き込み中のパフォーマンスを改善しました。]]>
Added support for attaching the HP Smart Array P212 and the HP Smart Array P411 to an HP StorageWorks 600 Modular Disk System (MDS600)
Improved performance in SATA Hard drive configurations.
Improved performance during offset non-contiguous writes.]]>
Added support for attaching the HP Smart Array P212 and the HP Smart Array P411 to an HP StorageWorks 600 Modular Disk System (MDS600)
Improved performance in SATA Hard drive configurations.
Improved performance during offset non-contiguous writes.]]>
Update Requirements:
Critical: HP requires users to update to this firmware version immediately.
Important Notes:
- HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card Firmware version 1.52 or higher, to support 6Gb SAS and 3Gb SATA drives.
- The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
- When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD
HP recommends for remote deployment of this package that you obtain the most recent version of the Firmware Maintenance CD and follow these steps:
- Place the Firmware Maintenance CD on a USB key using the HP USB Key Creator Utility.
- Place the firmware to be updated in the directory, /compaq/swpackages on the USB key.
- Run Autorun from \_autorunutorun_win.exe on the Firmware Maintenance CD from the USB key on a system
- Select the Firmware Update tab
- Click on the Install Firmware link to launch the HP Smart Update Manager
- Follow the GUI to install the firmware on remote servers
Problems Fixed:
- Fixed an issue where 3G SATA drives were not being detected at post on the ProLiant DL180G6 with a 12 drive backplane
- Fixed an issue where erroneous drive hot remove events were being reported causing unnecessary drive rebuilds.
- Fixed an issue where Novell Netware volumes failed to mount with 2.00 HP Smart Array FW.
]]>
Update Requirements:
Critical: HP requires users to update to this firmware version immediately.
Important Notes:
- HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card Firmware version 1.52 or higher, to support 6Gb SAS and 3Gb SATA drives.
- The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
- When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD
HP recommends for remote deployment of this package that you obtain the most recent version of the Firmware Maintenance CD and follow these steps:
- Place the Firmware Maintenance CD on a USB key using the HP USB Key Creator Utility.
- Place the firmware to be updated in the directory, /compaq/swpackages on the USB key.
- Run Autorun from \_autorunutorun_win.exe on the Firmware Maintenance CD from the USB key on a system
- Select the Firmware Update tab
- Click on the Install Firmware link to launch the HP Smart Update Manager
- Follow the GUI to install the firmware on remote servers
Problems Fixed:
- Fixed an issue where 3G SATA drives were not being detected at post on the ProLiant DL180G6 with a 12 drive backplane
- Fixed an issue where erroneous drive hot remove events were being reported causing unnecessary drive rebuilds.
- Fixed an issue where Novell Netware volumes failed to mount with 2.00 HP Smart Array FW.
]]>
Update Requirements:
Critical: HP requires users to update to this firmware version immediately.
Important Notes:
- HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card Firmware version 1.52 or higher, to support 6Gb SAS and 3Gb SATA drives.
- The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
- When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD
HP recommends for remote deployment of this package that you obtain the most recent version of the Firmware Maintenance CD and follow these steps:
- Place the Firmware Maintenance CD on a USB key using the HP USB Key Creator Utility.
- Place the firmware to be updated in the directory, /compaq/swpackages on the USB key.
- Run Autorun from \_autorunutorun_win.exe on the Firmware Maintenance CD from the USB key on a system
- Select the Firmware Update tab
- Click on the Install Firmware link to launch the HP Smart Update Manager
- Follow the GUI to install the firmware on remote servers
Problems Fixed:
- Fixed an issue where 3G SATA drives were not being detected at post on the ProLiant DL180G6 with a 12 drive backplane
- Fixed an issue where erroneous drive hot remove events were being reported causing unnecessary drive rebuilds.
- Fixed an issue where Novell Netware volumes failed to mount with 2.00 HP Smart Array FW.
]]>
Update Requirements:
Critical: HP requires users to update to this firmware version immediately.
Important Notes:
- HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card Firmware version 1.52 or higher, to support 6Gb SAS and 3Gb SATA drives.
- The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
- When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD
HP recommends for remote deployment of this package that you obtain the most recent version of the Firmware Maintenance CD and follow these steps:
- Place the Firmware Maintenance CD on a USB key using the HP USB Key Creator Utility.
- Place the firmware to be updated in the directory, /compaq/swpackages on the USB key.
- Run Autorun from \_autorunutorun_win.exe on the Firmware Maintenance CD from the USB key on a system
- Select the Firmware Update tab
- Click on the Install Firmware link to launch the HP Smart Update Manager
- Follow the GUI to install the firmware on remote servers
Problems Fixed:
- Fixed an issue where 3G SATA drives were not being detected at post on the ProLiant DL180G6 with a 12 drive backplane
- Fixed an issue where erroneous drive hot remove events were being reported causing unnecessary drive rebuilds.
- Fixed an issue where Novell Netware volumes failed to mount with 2.00 HP Smart Array FW.
]]>
Update Requirements:
Critical: HP requires users to update to this firmware version immediately.
Important Notes:
- HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card Firmware version 1.52 or higher, to support 6Gb SAS and 3Gb SATA drives.
- The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
- When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD
HP recommends for remote deployment of this package that you obtain the most recent version of the Firmware Maintenance CD and follow these steps:
- Place the Firmware Maintenance CD on a USB key using the HP USB Key Creator Utility.
- Place the firmware to be updated in the directory, /compaq/swpackages on the USB key.
- Run Autorun from \_autorunutorun_win.exe on the Firmware Maintenance CD from the USB key on a system
- Select the Firmware Update tab
- Click on the Install Firmware link to launch the HP Smart Update Manager
- Follow the GUI to install the firmware on remote servers
Problems Fixed:
- Fixed an issue where 3G SATA drives were not being detected at post on the ProLiant DL180G6 with a 12 drive backplane
- Fixed an issue where erroneous drive hot remove events were being reported causing unnecessary drive rebuilds.
- Fixed an issue where Novell Netware volumes failed to mount with 2.00 HP Smart Array FW.
]]>
Update Requirements:
Critical: HP requires users to update to this firmware version immediately.
Important Notes:
- HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card Firmware version 1.52 or higher, to support 6Gb SAS and 3Gb SATA drives.
- The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
- When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD
HP recommends for remote deployment of this package that you obtain the most recent version of the Firmware Maintenance CD and follow these steps:
- Place the Firmware Maintenance CD on a USB key using the HP USB Key Creator Utility.
- Place the firmware to be updated in the directory, /compaq/swpackages on the USB key.
- Run Autorun from \_autorunutorun_win.exe on the Firmware Maintenance CD from the USB key on a system
- Select the Firmware Update tab
- Click on the Install Firmware link to launch the HP Smart Update Manager
- Follow the GUI to install the firmware on remote servers
Problems Fixed:
- Fixed an issue where 3G SATA drives were not being detected at post on the ProLiant DL180G6 with a 12 drive backplane
- Fixed an issue where erroneous drive hot remove events were being reported causing unnecessary drive rebuilds.
- Fixed an issue where Novell Netware volumes failed to mount with 2.00 HP Smart Array FW.
]]>
アップデート要件:
クリティカル: HPではファームウェア バージョンをすぐにアップデートすることを推奨しています。
重要な注意:
- HP SmartアレイP410またはHP SmartアレイP410iに接続されたHP SAS Expanderカードは、6Gb SASおよび3Gb SATAドライブをサポートするために、SAS Expanderカード ファームウェア バージョン1.52以降が必要です。
- ストレージ サブシステム(例、ドライブ、コントローラー、およびサーバー バックプレーン)は、同じデータ転送レートで動作しなければなりません。そうでない場合はシステム バンド幅はすべてのコンポーネントが受け入れ可能なレベルにネゴシエートされます。
- VMware ESX/ESXiを実行している場合、Firmware Maintenance CD上のHP Smart Update Managerを使用したオフライン アップデートのみサポートされます。
このパッケージのリモート デプロイメントには、最新のバージョンのFirmware Maintenance CDを入手して、以下の手順を実行することをおすすめします。
- HP USB Key Utility(英語)を使用して、Firmware Maintenance CD(英語)をUSBキーにコピーします。
- アップデートするファームウェアをUSBキーの/compaq/swpackagesディレクトリにコピーします。
- システムのUSBキーのFirmware Maintenance CDの\_autorunutorun_win.exeからAutorunを実行します。
- ファームウェア アップデート タブを選択します。
- [ファームウェアのインストール]リンクをクリックしてHP Smart Update Managerを実行します。
- GUIに従ってリモート サーバーにファームウェアをインストールします。
修正された問題点:
- 12ドライブ バックプレーンのProLiant DL180G6で3G SATAドライブがPOSTで検出されない問題を修正しました。
- ホット リムーブ イベントが間違って報告されて、必要のないドライブの再構築が発生する問題を修正しました。
- Novell Netwareボリュームが2.00 HP Smartアレイ ファームウェアでマウントに失敗する問題を修正しました。
]]>
Update Requirements:
Critical: HP requires users to update to this firmware version immediately.
Important Notes:
- HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card Firmware version 1.52 or higher, to support 6Gb SAS and 3Gb SATA drives.
- The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
- When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD
HP recommends for remote deployment of this package that you obtain the most recent version of the Firmware Maintenance CD and follow these steps:
- Place the Firmware Maintenance CD on a USB key using the HP USB Key Creator Utility.
- Place the firmware to be updated in the directory, /compaq/swpackages on the USB key.
- Run Autorun from \_autorunutorun_win.exe on the Firmware Maintenance CD from the USB key on a system
- Select the Firmware Update tab
- Click on the Install Firmware link to launch the HP Smart Update Manager
- Follow the GUI to install the firmware on remote servers
Problems Fixed:
- Fixed an issue where 3G SATA drives were not being detected at post on the ProLiant DL180G6 with a 12 drive backplane
- Fixed an issue where erroneous drive hot remove events were being reported causing unnecessary drive rebuilds.
- Fixed an issue where Novell Netware volumes failed to mount with 2.00 HP Smart Array FW.
]]>
Update Requirements:
Critical: HP requires users to update to this firmware version immediately.
Important Notes:
- HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card Firmware version 1.52 or higher, to support 6Gb SAS and 3Gb SATA drives.
- The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
- When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD
HP recommends for remote deployment of this package that you obtain the most recent version of the Firmware Maintenance CD and follow these steps:
- Place the Firmware Maintenance CD on a USB key using the HP USB Key Creator Utility.
- Place the firmware to be updated in the directory, /compaq/swpackages on the USB key.
- Run Autorun from \_autorunutorun_win.exe on the Firmware Maintenance CD from the USB key on a system
- Select the Firmware Update tab
- Click on the Install Firmware link to launch the HP Smart Update Manager
- Follow the GUI to install the firmware on remote servers
Problems Fixed:
- Fixed an issue where 3G SATA drives were not being detected at post on the ProLiant DL180G6 with a 12 drive backplane
- Fixed an issue where erroneous drive hot remove events were being reported causing unnecessary drive rebuilds.
- Fixed an issue where Novell Netware volumes failed to mount with 2.00 HP Smart Array FW.
]]>
Support for SATA SSD drives
Support for HP DS2600 JBOD
Additional performance enhancements specific to non-contiguous offset writes]]>
Support for SATA SSD drives
Support for HP DS2600 JBOD
Additional performance enhancements specific to non-contiguous offset writes]]>
Support for SATA SSD drives
Support for HP DS2600 JBOD
Additional performance enhancements specific to non-contiguous offset writes]]>
Support for SATA SSD drives
Support for HP DS2600 JBOD
Additional performance enhancements specific to non-contiguous offset writes]]>
Support for SATA SSD drives
Support for HP DS2600 JBOD
Additional performance enhancements specific to non-contiguous offset writes]]>
Support for SATA SSD drives
Support for HP DS2600 JBOD
Additional performance enhancements specific to non-contiguous offset writes]]>
SATA SSDドライブをサポートします。
HP DS2600 JBODをサポートします
非連続オフセット ライト固有のパフォーマンスの改善を追加します]]>
Support for SATA SSD drives
Support for HP DS2600 JBOD
Additional performance enhancements specific to non-contiguous offset writes]]>
Support for SATA SSD drives
Support for HP DS2600 JBOD
Additional performance enhancements specific to non-contiguous offset writes]]>
Update Requirements – Critical – HP requires users to update to this firmware version immediately.
Important Notes -
- HP ProLiant DL380G6 and HP ProLiant DL385G6 will require 300 series G6 Server SAS Backplane Firmware version 1.16 or higher, to support 6Gb SAS drives. The SAS Backplane Firmware can be obtained at the following link. Click Here
- It is NOT recommended to apply version 2.00 or higher on an HP Proliant 180G6 server configured with the 12 bay drive option and 3Gb SATA drives. On rare occasions, the server may become unresponsive under heavy I/O and a reboot may be required. A future version of the controller firmware will support the HP ProLiant DL180G6 and 12 bay drive expander backplane for 3Gb SATA drives.
- HP SAS Expander Card connected to an HP SA P410 or HP SA P410i will require SAS Expander Card Firmware version 1.52 or higher, to support 6Gb SAS and 3Gb SATA drives.
- The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
HP recommends for remote deployment of this package that you obtain the most recent version of the Firmware Maintenance CD and follow these steps:
- Place the Firmware Maintenance CD on a USB key using the HP USB Key Creator Utility.
- Place the firmware to be updated in the directory, /compaq/swpackages on the USB key.
- Run Autorun from \_autorunutorun_win.exe on the Firmware Maintenance CD from the USB key on a system
- Select the Firmware Update tab
- Click on the Install Firmware link to launch the HP Smart Update Manager
- Follow the GUI to install the firmware on remote servers
Required Fixes :
- Fix for a potential controller hang condition (lockup error code 0XBC) seen during heavy I/O.
- Fix for a server operating system hang condition encountered during IO stress tests, such as SQLIO.
- Fix for a potential controller hang condition (lockup error code 0XAB) seen when controller is configured in Zero Memory Mode (no cache module installed)
- Fix for potential data miscompare condition during error recovery in a RAID50/60 configuration. The error condition was only observed in a lab test environment.
- Fix for an issue where logical erase feature in utilities such as ACU, does not completely erase a volume if write cache is enabled
- Fix for a potential controller hang condition that may be seen when a 2nd SATA drive fails in a RAID 6 configuration.
]]>
Update Requirements – Critical – HP requires users to update to this firmware version immediately.
Important Notes -
- HP ProLiant DL380G6 and HP ProLiant DL385G6 will require 300 series G6 Server SAS Backplane Firmware version 1.16 or higher, to support 6Gb SAS drives. The SAS Backplane Firmware can be obtained at the following link. Click Here
- It is NOT recommended to apply version 2.00 or higher on an HP Proliant 180G6 server configured with the 12 bay drive option and 3Gb SATA drives. On rare occasions, the server may become unresponsive under heavy I/O and a reboot may be required. A future version of the controller firmware will support the HP ProLiant DL180G6 and 12 bay drive expander backplane for 3Gb SATA drives.
- HP SAS Expander Card connected to an HP SA P410 or HP SA P410i will require SAS Expander Card Firmware version 1.52 or higher, to support 6Gb SAS and 3Gb SATA drives.
- The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
HP recommends for remote deployment of this package that you obtain the most recent version of the Firmware Maintenance CD and follow these steps:
- Place the Firmware Maintenance CD on a USB key using the HP USB Key Creator Utility.
- Place the firmware to be updated in the directory, /compaq/swpackages on the USB key.
- Run Autorun from \_autorunutorun_win.exe on the Firmware Maintenance CD from the USB key on a system
- Select the Firmware Update tab
- Click on the Install Firmware link to launch the HP Smart Update Manager
- Follow the GUI to install the firmware on remote servers
Required Fixes :
- Fix for a potential controller hang condition (lockup error code 0XBC) seen during heavy I/O.
- Fix for a server operating system hang condition encountered during IO stress tests, such as SQLIO.
- Fix for a potential controller hang condition (lockup error code 0XAB) seen when controller is configured in Zero Memory Mode (no cache module installed)
- Fix for potential data miscompare condition during error recovery in a RAID50/60 configuration. The error condition was only observed in a lab test environment.
- Fix for an issue where logical erase feature in utilities such as ACU, does not completely erase a volume if write cache is enabled
- Fix for a potential controller hang condition that may be seen when a 2nd SATA drive fails in a RAID 6 configuration.
]]>
Update Requirements – Critical – HP requires users to update to this firmware version immediately.
Important Notes -
- HP ProLiant DL380G6 and HP ProLiant DL385G6 will require 300 series G6 Server SAS Backplane Firmware version 1.16 or higher, to support 6Gb SAS drives. The SAS Backplane Firmware can be obtained at the following link. Click Here
- It is NOT recommended to apply version 2.00 or higher on an HP Proliant 180G6 server configured with the 12 bay drive option and 3Gb SATA drives. On rare occasions, the server may become unresponsive under heavy I/O and a reboot may be required. A future version of the controller firmware will support the HP ProLiant DL180G6 and 12 bay drive expander backplane for 3Gb SATA drives.
- HP SAS Expander Card connected to an HP SA P410 or HP SA P410i will require SAS Expander Card Firmware version 1.52 or higher, to support 6Gb SAS and 3Gb SATA drives.
- The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
HP recommends for remote deployment of this package that you obtain the most recent version of the Firmware Maintenance CD and follow these steps:
- Place the Firmware Maintenance CD on a USB key using the HP USB Key Creator Utility.
- Place the firmware to be updated in the directory, /compaq/swpackages on the USB key.
- Run Autorun from \_autorunutorun_win.exe on the Firmware Maintenance CD from the USB key on a system
- Select the Firmware Update tab
- Click on the Install Firmware link to launch the HP Smart Update Manager
- Follow the GUI to install the firmware on remote servers
Required Fixes :
- Fix for a potential controller hang condition (lockup error code 0XBC) seen during heavy I/O.
- Fix for a server operating system hang condition encountered during IO stress tests, such as SQLIO.
- Fix for a potential controller hang condition (lockup error code 0XAB) seen when controller is configured in Zero Memory Mode (no cache module installed)
- Fix for potential data miscompare condition during error recovery in a RAID50/60 configuration. The error condition was only observed in a lab test environment.
- Fix for an issue where logical erase feature in utilities such as ACU, does not completely erase a volume if write cache is enabled
- Fix for a potential controller hang condition that may be seen when a 2nd SATA drive fails in a RAID 6 configuration.
]]>
Update Requirements – Critical – HP requires users to update to this firmware version immediately.
Important Notes -
- HP ProLiant DL380G6 and HP ProLiant DL385G6 will require 300 series G6 Server SAS Backplane Firmware version 1.16 or higher, to support 6Gb SAS drives. The SAS Backplane Firmware can be obtained at the following link. Click Here
- It is NOT recommended to apply version 2.00 or higher on an HP Proliant 180G6 server configured with the 12 bay drive option and 3Gb SATA drives. On rare occasions, the server may become unresponsive under heavy I/O and a reboot may be required. A future version of the controller firmware will support the HP ProLiant DL180G6 and 12 bay drive expander backplane for 3Gb SATA drives.
- HP SAS Expander Card connected to an HP SA P410 or HP SA P410i will require SAS Expander Card Firmware version 1.52 or higher, to support 6Gb SAS and 3Gb SATA drives.
- The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
HP recommends for remote deployment of this package that you obtain the most recent version of the Firmware Maintenance CD and follow these steps:
- Place the Firmware Maintenance CD on a USB key using the HP USB Key Creator Utility.
- Place the firmware to be updated in the directory, /compaq/swpackages on the USB key.
- Run Autorun from \_autorunutorun_win.exe on the Firmware Maintenance CD from the USB key on a system
- Select the Firmware Update tab
- Click on the Install Firmware link to launch the HP Smart Update Manager
- Follow the GUI to install the firmware on remote servers
Required Fixes :
- Fix for a potential controller hang condition (lockup error code 0XBC) seen during heavy I/O.
- Fix for a server operating system hang condition encountered during IO stress tests, such as SQLIO.
- Fix for a potential controller hang condition (lockup error code 0XAB) seen when controller is configured in Zero Memory Mode (no cache module installed)
- Fix for potential data miscompare condition during error recovery in a RAID50/60 configuration. The error condition was only observed in a lab test environment.
- Fix for an issue where logical erase feature in utilities such as ACU, does not completely erase a volume if write cache is enabled
- Fix for a potential controller hang condition that may be seen when a 2nd SATA drive fails in a RAID 6 configuration.
]]>
Update Requirements – Critical – HP requires users to update to this firmware version immediately.
Important Notes -
- HP ProLiant DL380G6 and HP ProLiant DL385G6 will require 300 series G6 Server SAS Backplane Firmware version 1.16 or higher, to support 6Gb SAS drives. The SAS Backplane Firmware can be obtained at the following link. Click Here
- It is NOT recommended to apply version 2.00 or higher on an HP Proliant 180G6 server configured with the 12 bay drive option and 3Gb SATA drives. On rare occasions, the server may become unresponsive under heavy I/O and a reboot may be required. A future version of the controller firmware will support the HP ProLiant DL180G6 and 12 bay drive expander backplane for 3Gb SATA drives.
- HP SAS Expander Card connected to an HP SA P410 or HP SA P410i will require SAS Expander Card Firmware version 1.52 or higher, to support 6Gb SAS and 3Gb SATA drives.
- The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
HP recommends for remote deployment of this package that you obtain the most recent version of the Firmware Maintenance CD and follow these steps:
- Place the Firmware Maintenance CD on a USB key using the HP USB Key Creator Utility.
- Place the firmware to be updated in the directory, /compaq/swpackages on the USB key.
- Run Autorun from \_autorunutorun_win.exe on the Firmware Maintenance CD from the USB key on a system
- Select the Firmware Update tab
- Click on the Install Firmware link to launch the HP Smart Update Manager
- Follow the GUI to install the firmware on remote servers
Required Fixes :
- Fix for a potential controller hang condition (lockup error code 0XBC) seen during heavy I/O.
- Fix for a server operating system hang condition encountered during IO stress tests, such as SQLIO.
- Fix for a potential controller hang condition (lockup error code 0XAB) seen when controller is configured in Zero Memory Mode (no cache module installed)
- Fix for potential data miscompare condition during error recovery in a RAID50/60 configuration. The error condition was only observed in a lab test environment.
- Fix for an issue where logical erase feature in utilities such as ACU, does not completely erase a volume if write cache is enabled
- Fix for a potential controller hang condition that may be seen when a 2nd SATA drive fails in a RAID 6 configuration.
]]>
Update Requirements – Critical – HP requires users to update to this firmware version immediately.
Important Notes -
- HP ProLiant DL380G6 and HP ProLiant DL385G6 will require 300 series G6 Server SAS Backplane Firmware version 1.16 or higher, to support 6Gb SAS drives. The SAS Backplane Firmware can be obtained at the following link. Click Here
- It is NOT recommended to apply version 2.00 or higher on an HP Proliant 180G6 server configured with the 12 bay drive option and 3Gb SATA drives. On rare occasions, the server may become unresponsive under heavy I/O and a reboot may be required. A future version of the controller firmware will support the HP ProLiant DL180G6 and 12 bay drive expander backplane for 3Gb SATA drives.
- HP SAS Expander Card connected to an HP SA P410 or HP SA P410i will require SAS Expander Card Firmware version 1.52 or higher, to support 6Gb SAS and 3Gb SATA drives.
- The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
HP recommends for remote deployment of this package that you obtain the most recent version of the Firmware Maintenance CD and follow these steps:
- Place the Firmware Maintenance CD on a USB key using the HP USB Key Creator Utility.
- Place the firmware to be updated in the directory, /compaq/swpackages on the USB key.
- Run Autorun from \_autorunutorun_win.exe on the Firmware Maintenance CD from the USB key on a system
- Select the Firmware Update tab
- Click on the Install Firmware link to launch the HP Smart Update Manager
- Follow the GUI to install the firmware on remote servers
Required Fixes :
- Fix for a potential controller hang condition (lockup error code 0XBC) seen during heavy I/O.
- Fix for a server operating system hang condition encountered during IO stress tests, such as SQLIO.
- Fix for a potential controller hang condition (lockup error code 0XAB) seen when controller is configured in Zero Memory Mode (no cache module installed)
- Fix for potential data miscompare condition during error recovery in a RAID50/60 configuration. The error condition was only observed in a lab test environment.
- Fix for an issue where logical erase feature in utilities such as ACU, does not completely erase a volume if write cache is enabled
- Fix for a potential controller hang condition that may be seen when a 2nd SATA drive fails in a RAID 6 configuration.
]]>
アップデート要件 - クリティカル - HPではファームウェア バージョンをすぐにアップデートすることを推奨しています。
重要な注意 -
- HP ProLiant DL380 G6およびHP ProLiant DL385 G6で6Gb SASドライブをサポートするには、300シリーズG6サーバーSASバックプレーン ファームウェア バージョン1.16以降が必要です。 SASバックプレーン ファームウェアは以下のリンクより入手できます。 ここをクリック(英語)
- 12ベイ ドライブ オプションと3Gb SATAドライブ構成のHP ProLiant 180G6サーバーにバージョン2.00以降を適用することはおすすめしません。 ごくまれに、I/Oの負荷が高くサーバーが応答しなくなり、再起動が必要になることがあります。 将来のバージョンのコントローラー ファームウェアは、HP ProLiant DL180G6と3Gb SATAドライブの12ベイ ドライブ拡張バックプレーンをサポートします。
- HP SA P410またはHP SA P410iに接続されたHP SAS Expanderカードは、6Gb SASおよび3Gb SATAドライブをサポートするために、SAS Expanderカード ファームウェア バージョン1.52以降が必要です。
- ストレージ サブシステム(例、ドライブ、コントローラー、およびサーバー バックプレーン)は、同じデータ転送レートで動作しなければなりません。そうでない場合はシステム バンド幅はすべてのコンポーネントが受け入れ可能なレベルにネゴシエートされます。
このパッケージのリモート デプロイメントには、最新のバージョンのFirmware Maintenance CDを入手して、以下の手順を実行することをおすすめします。
- HP USB Key Creator Utilityを使用して、Firmware Maintenance CDをUSBキーにコピーします。
- アップデートするファームウェアをUSBキーの/compaq/swpackagesディレクトリにコピーします。
- システムのUSBキーのFirmware Maintenance CDの\_autorunutorun_win.exeからAutorunを実行します。
- ファームウェア アップデート タブを選択します。
- [ファームウェアのインストール]リンクをクリックしてHP Smart Update Managerを実行します。
- GUIに従ってリモート サーバーにファームウェアをインストールします。
必要な修正:
- I/Oが高負荷の時にコントローラーがハングアップする潜在的な問題(ルックアップ エラー コード 0XBC)を修正します。
- SQLIOなどのIOストレス テスト中にサーバーのオペレーティング システムがハングアップする問題を修正しました。
- コントローラーが[Zero Memory Mode](キャッシュ モジュール非搭載)に設定されていると、コントローラーがハングアップする潜在的な問題(ルックアップ エラー コード0XAB)を修正します。
- RAID50/60構成でエラー復旧中の潜在的なデータ不一致を修正しました。 そのエラーはラボ テスト環境でのみ確認されました。
- ACUなどのユーティリティの論理消去機能は、書き込みキャッシュが有効だとボリュームを完全に消去しません。
- RAID 6構成で二台目のSATAドライブに障害が発生するとコントローラーがハングアップ状態になる可能性がある問題を修正しました。
]]>
Update Requirements – Critical – HP requires users to update to this firmware version immediately.
Important Notes -
- HP ProLiant DL380G6 and HP ProLiant DL385G6 will require 300 series G6 Server SAS Backplane Firmware version 1.16 or higher, to support 6Gb SAS drives. The SAS Backplane Firmware can be obtained at the following link. Click Here
- It is NOT recommended to apply version 2.00 or higher on an HP Proliant 180G6 server configured with the 12 bay drive option and 3Gb SATA drives. On rare occasions, the server may become unresponsive under heavy I/O and a reboot may be required. A future version of the controller firmware will support the HP ProLiant DL180G6 and 12 bay drive expander backplane for 3Gb SATA drives.
- HP SAS Expander Card connected to an HP SA P410 or HP SA P410i will require SAS Expander Card Firmware version 1.52 or higher, to support 6Gb SAS and 3Gb SATA drives.
- The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
HP recommends for remote deployment of this package that you obtain the most recent version of the Firmware Maintenance CD and follow these steps:
- Place the Firmware Maintenance CD on a USB key using the HP USB Key Creator Utility.
- Place the firmware to be updated in the directory, /compaq/swpackages on the USB key.
- Run Autorun from \_autorunutorun_win.exe on the Firmware Maintenance CD from the USB key on a system
- Select the Firmware Update tab
- Click on the Install Firmware link to launch the HP Smart Update Manager
- Follow the GUI to install the firmware on remote servers
Required Fixes :
- Fix for a potential controller hang condition (lockup error code 0XBC) seen during heavy I/O.
- Fix for a server operating system hang condition encountered during IO stress tests, such as SQLIO.
- Fix for a potential controller hang condition (lockup error code 0XAB) seen when controller is configured in Zero Memory Mode (no cache module installed)
- Fix for potential data miscompare condition during error recovery in a RAID50/60 configuration. The error condition was only observed in a lab test environment.
- Fix for an issue where logical erase feature in utilities such as ACU, does not completely erase a volume if write cache is enabled
- Fix for a potential controller hang condition that may be seen when a 2nd SATA drive fails in a RAID 6 configuration.
]]>
Update Requirements – Critical – HP requires users to update to this firmware version immediately.
Important Notes -
- HP ProLiant DL380G6 and HP ProLiant DL385G6 will require 300 series G6 Server SAS Backplane Firmware version 1.16 or higher, to support 6Gb SAS drives. The SAS Backplane Firmware can be obtained at the following link. Click Here
- It is NOT recommended to apply version 2.00 or higher on an HP Proliant 180G6 server configured with the 12 bay drive option and 3Gb SATA drives. On rare occasions, the server may become unresponsive under heavy I/O and a reboot may be required. A future version of the controller firmware will support the HP ProLiant DL180G6 and 12 bay drive expander backplane for 3Gb SATA drives.
- HP SAS Expander Card connected to an HP SA P410 or HP SA P410i will require SAS Expander Card Firmware version 1.52 or higher, to support 6Gb SAS and 3Gb SATA drives.
- The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
HP recommends for remote deployment of this package that you obtain the most recent version of the Firmware Maintenance CD and follow these steps:
- Place the Firmware Maintenance CD on a USB key using the HP USB Key Creator Utility.
- Place the firmware to be updated in the directory, /compaq/swpackages on the USB key.
- Run Autorun from \_autorunutorun_win.exe on the Firmware Maintenance CD from the USB key on a system
- Select the Firmware Update tab
- Click on the Install Firmware link to launch the HP Smart Update Manager
- Follow the GUI to install the firmware on remote servers
Required Fixes :
- Fix for a potential controller hang condition (lockup error code 0XBC) seen during heavy I/O.
- Fix for a server operating system hang condition encountered during IO stress tests, such as SQLIO.
- Fix for a potential controller hang condition (lockup error code 0XAB) seen when controller is configured in Zero Memory Mode (no cache module installed)
- Fix for potential data miscompare condition during error recovery in a RAID50/60 configuration. The error condition was only observed in a lab test environment.
- Fix for an issue where logical erase feature in utilities such as ACU, does not completely erase a volume if write cache is enabled
- Fix for a potential controller hang condition that may be seen when a 2nd SATA drive fails in a RAID 6 configuration.
]]>
• Includes advanced error logging features for controller lockup codes that can be collected via the HP Array Diagnostics Utility.
• Enhancements to support 6Gb SAS / 3Gb SATA hard drives for all HP Proliant G6 Servers.
]]>
• Includes advanced error logging features for controller lockup codes that can be collected via the HP Array Diagnostics Utility.
• Enhancements to support 6Gb SAS / 3Gb SATA hard drives for all HP Proliant G6 Servers.
]]>
• Includes advanced error logging features for controller lockup codes that can be collected via the HP Array Diagnostics Utility.
• Enhancements to support 6Gb SAS / 3Gb SATA hard drives for all HP Proliant G6 Servers.
]]>
• Includes advanced error logging features for controller lockup codes that can be collected via the HP Array Diagnostics Utility.
• Enhancements to support 6Gb SAS / 3Gb SATA hard drives for all HP Proliant G6 Servers.
]]>
• Includes advanced error logging features for controller lockup codes that can be collected via the HP Array Diagnostics Utility.
• Enhancements to support 6Gb SAS / 3Gb SATA hard drives for all HP Proliant G6 Servers.
]]>
• Includes advanced error logging features for controller lockup codes that can be collected via the HP Array Diagnostics Utility.
• Enhancements to support 6Gb SAS / 3Gb SATA hard drives for all HP Proliant G6 Servers.
]]>
- HPアレイ診断ユーティリティで収集できるコントローラー ロックアップ コードのアドバンスト エラー ログ機能を追加します。
- すべてのHP Proliant G6サーバー用の6Gb SAS/3Gb SATAハードディスク ドライブのサポートを改善しました。
]]>
• Includes advanced error logging features for controller lockup codes that can be collected via the HP Array Diagnostics Utility.
• Enhancements to support 6Gb SAS / 3Gb SATA hard drives for all HP Proliant G6 Servers.
]]>
• Includes advanced error logging features for controller lockup codes that can be collected via the HP Array Diagnostics Utility.
• Enhancements to support 6Gb SAS / 3Gb SATA hard drives for all HP Proliant G6 Servers.
]]>
• Fix to address high latency issues seen during heavy I/O conditions involving non-contiguous offset writes and RAID 5/6 write operations.
• Fix for a potential controller lockup condition when a drive is hot removed during a read operation.
• Additional fixes to address rare occurrences of controller unresponsiveness during heavy I/O stress tests in a lab environment.
]]>
• Fix to address high latency issues seen during heavy I/O conditions involving non-contiguous offset writes and RAID 5/6 write operations.
• Fix for a potential controller lockup condition when a drive is hot removed during a read operation.
• Additional fixes to address rare occurrences of controller unresponsiveness during heavy I/O stress tests in a lab environment.
]]>
• Fix to address high latency issues seen during heavy I/O conditions involving non-contiguous offset writes and RAID 5/6 write operations.
• Fix for a potential controller lockup condition when a drive is hot removed during a read operation.
• Additional fixes to address rare occurrences of controller unresponsiveness during heavy I/O stress tests in a lab environment.
]]>
• Fix to address high latency issues seen during heavy I/O conditions involving non-contiguous offset writes and RAID 5/6 write operations.
• Fix for a potential controller lockup condition when a drive is hot removed during a read operation.
• Additional fixes to address rare occurrences of controller unresponsiveness during heavy I/O stress tests in a lab environment.
]]>
• Fix to address high latency issues seen during heavy I/O conditions involving non-contiguous offset writes and RAID 5/6 write operations.
• Fix for a potential controller lockup condition when a drive is hot removed during a read operation.
• Additional fixes to address rare occurrences of controller unresponsiveness during heavy I/O stress tests in a lab environment.
]]>
• Fix to address high latency issues seen during heavy I/O conditions involving non-contiguous offset writes and RAID 5/6 write operations.
• Fix for a potential controller lockup condition when a drive is hot removed during a read operation.
• Additional fixes to address rare occurrences of controller unresponsiveness during heavy I/O stress tests in a lab environment.
]]>
- 非連続的なオフセット書き込みとRAID 5/6書き込み処理に関連するI/Oが高負荷状態のときに待ち時間が長くなる問題に対処するために修正しました。
- 読み込み処理中にドライブをホット リムーブするとコントローラーがロックアップ状態になる問題を修正しました。
- 研究所環境でI/O高ストレス テスト中に、ごくまれにコントローラーが応答しなくなる問題に対処するための修正を追加しました。
]]>
• Fix to address high latency issues seen during heavy I/O conditions involving non-contiguous offset writes and RAID 5/6 write operations.
• Fix for a potential controller lockup condition when a drive is hot removed during a read operation.
• Additional fixes to address rare occurrences of controller unresponsiveness during heavy I/O stress tests in a lab environment.
]]>
• Fix to address high latency issues seen during heavy I/O conditions involving non-contiguous offset writes and RAID 5/6 write operations.
• Fix for a potential controller lockup condition when a drive is hot removed during a read operation.
• Additional fixes to address rare occurrences of controller unresponsiveness during heavy I/O stress tests in a lab environment.
]]>
Fix for an ORCA related issue, where a ProLiant ML150G6 server may stop responding during POST.]]>
Fix for an ORCA related issue, where a ProLiant ML150G6 server may stop responding during POST.]]>
Fix for an ORCA related issue, where a ProLiant ML150G6 server may stop responding during POST.]]>
Fix for an ORCA related issue, where a ProLiant ML150G6 server may stop responding during POST.]]>
Fix for an ORCA related issue, where a ProLiant ML150G6 server may stop responding during POST.]]>
Fix for an ORCA related issue, where a ProLiant ML150G6 server may stop responding during POST.]]>
ProLiant ML150G6サーバーがPOST中に応答しなくなる、ORCAに関連する問題を修正します。]]>
Fix for an ORCA related issue, where a ProLiant ML150G6 server may stop responding during POST.]]>
Fix for an ORCA related issue, where a ProLiant ML150G6 server may stop responding during POST.]]>
Enabled a feature that allows the HP Smart Array P410i, P410, P411, and P212 to run at generation 2 speeds.]]>
Enabled a feature that allows the HP Smart Array P410i, P410, P411, and P212 to run at generation 2 speeds.]]>
Enabled a feature that allows the HP Smart Array P410i, P410, P411, and P212 to run at generation 2 speeds.]]>
Enabled a feature that allows the HP Smart Array P410i, P410, P411, and P212 to run at generation 2 speeds.]]>
Enabled a feature that allows the HP Smart Array P410i, P410, P411, and P212 to run at generation 2 speeds.]]>
Enabled a feature that allows the HP Smart Array P410i, P410, P411, and P212 to run at generation 2 speeds.]]>
HP SmartアレイP410i、P410、P411、およびP212をgeneration 2の速度で動作させるための機能を有効にしました。]]>
Enabled a feature that allows the HP Smart Array P410i, P410, P411, and P212 to run at generation 2 speeds.]]>
Enabled a feature that allows the HP Smart Array P410i, P410, P411, and P212 to run at generation 2 speeds.]]>
Enabled support for the HP Smart Array P410i Controller]]>
Enabled support for the HP Smart Array P410i Controller]]>
Enabled support for the HP Smart Array P410i Controller]]>
Enabled support for the HP Smart Array P410i Controller]]>
Enabled support for the HP Smart Array P410i Controller]]>
Enabled support for the HP Smart Array P410i Controller]]>
HP SmartアレイP410iコントローラのサポートを有効にしました]]>
Enabled support for the HP Smart Array P410i Controller]]>
Enabled support for the HP Smart Array P410i Controller]]>
Fixed an issue on RAID 1 and RAID 1+0 logical drives in which normal operating system-related buffer content changes that occur during write operations are misinterpreted and logged as critical "inconsistent stripe" events.]]>
Fixed an issue on RAID 1 and RAID 1+0 logical drives in which normal operating system-related buffer content changes that occur during write operations are misinterpreted and logged as critical "inconsistent stripe" events.]]>
Fixed an issue on RAID 1 and RAID 1+0 logical drives in which normal operating system-related buffer content changes that occur during write operations are misinterpreted and logged as critical "inconsistent stripe" events.]]>
Fixed an issue on RAID 1 and RAID 1+0 logical drives in which normal operating system-related buffer content changes that occur during write operations are misinterpreted and logged as critical "inconsistent stripe" events.]]>
Fixed an issue on RAID 1 and RAID 1+0 logical drives in which normal operating system-related buffer content changes that occur during write operations are misinterpreted and logged as critical "inconsistent stripe" events.]]>
Fixed an issue on RAID 1 and RAID 1+0 logical drives in which normal operating system-related buffer content changes that occur during write operations are misinterpreted and logged as critical "inconsistent stripe" events.]]>
書き込み動作中に発生する通常のオペレーティング システムに関連するバッファの内容の変更が、誤認識されてクリティカル「inconsistent stripe」イベントと記録される、RAID 1およびRAID 1+0論理ドライブの問題を修正しました。]]>
Fixed an issue on RAID 1 and RAID 1+0 logical drives in which normal operating system-related buffer content changes that occur during write operations are misinterpreted and logged as critical "inconsistent stripe" events.]]>
Fixed an issue on RAID 1 and RAID 1+0 logical drives in which normal operating system-related buffer content changes that occur during write operations are misinterpreted and logged as critical "inconsistent stripe" events.]]>
Fixed an issue on RAID 1 and RAID 1+0 logical drives in which normal operating system-related buffer content changes that occur during write operations are misinterpreted and logged as critical "inconsistent stripe" events.
]]>
Fixed an issue on RAID 1 and RAID 1+0 logical drives in which normal operating system-related buffer content changes that occur during write operations are misinterpreted and logged as critical "inconsistent stripe" events.
]]>
Fixed an issue on RAID 1 and RAID 1+0 logical drives in which normal operating system-related buffer content changes that occur during write operations are misinterpreted and logged as critical "inconsistent stripe" events.
]]>
Fixed an issue on RAID 1 and RAID 1+0 logical drives in which normal operating system-related buffer content changes that occur during write operations are misinterpreted and logged as critical "inconsistent stripe" events.
]]>
Fixed an issue on RAID 1 and RAID 1+0 logical drives in which normal operating system-related buffer content changes that occur during write operations are misinterpreted and logged as critical "inconsistent stripe" events.
]]>
Fixed an issue on RAID 1 and RAID 1+0 logical drives in which normal operating system-related buffer content changes that occur during write operations are misinterpreted and logged as critical "inconsistent stripe" events.
]]>
書き込み動作中に発生する通常のオペレーティング システムに関連するバッファの内容の変更が、誤認識されてクリティカル「inconsistent stripe」イベントと記録される、RAID 1およびRAID 1+0論理ドライブの問題を修正しました。
]]>
Fixed an issue on RAID 1 and RAID 1+0 logical drives in which normal operating system-related buffer content changes that occur during write operations are misinterpreted and logged as critical "inconsistent stripe" events.
]]>
Fixed an issue on RAID 1 and RAID 1+0 logical drives in which normal operating system-related buffer content changes that occur during write operations are misinterpreted and logged as critical "inconsistent stripe" events.
]]>
已解决的问题:
以下问题在面向 Linux 的在线 ROM Flash 组件 5.80 版本中得到解决 - 智能阵列 P212、P410、 P410i、 P411、 P711m、 P712m 和 P812:
- 在 HP P812 控制器上,向超过 75 块硬盘执行几个连续的写入操作会导致控制器锁定。
- 在罕见情况下,热添加硬盘时,已添加了保护以防止出现潜在的智能阵列控制器挂起。
- 在 Solaris 环境中运行时,智能阵列固件版本 5.80 解决了驱动程序无法正确处理智能阵列控制器出现异步事件的问题。
- 智能阵列控制器和 HP SAS 扩展卡之间出现互动问题,即开机或热插拔后,偶尔无法发现与 HP SAS 扩展卡连接的硬盘。
- 在极少数情况下,当 PHY 停留时间超过 4 秒,智能阵列控制器将多次重置相同的 SATA 驱动器。
- 智能阵列 P711m 和 P712m 将报告虚假的链接错误。
- 开放连接超时时间被减少到 900 微秒,以便正常终止 SAS 连接并防止数据传输中断。
- 在沉重负荷下,20 微秒内无法将智能阵列控制器与硬盘连接。
- 启动后,用户将立即看到一条 Post 消息,表示 P711m 控制器需要使用高速缓存模块。
- 当在 RAID 5 中运行繁重的 I/O 时,同时在采用 25SFF 背板的 HP DL180 G6 服务器中,向超过 17 块 SAS 驱动器连接 HP P410 控制器,可能发生锁定问题(错误代码 0xAB 或 0xEA)。
- 在繁重的 I/O 期间,当通过 HP 6Gb SAS 交换机将 HP P711m 控制器连接到 HP P2000sa G3 MSA 阵列系统,可能会发生锁定问题(错误代码 0x15)。
- 启动与 HP SAS 扩展卡连接的系统(配有 2 个或更多的空白 SAS 存储箱,箱 1、2、3 ……),然后将驱动器热插入 箱 2 或更多,ACU 和 ORCA 将错误显示箱 1 中的驱动器。
]]>
Problems Fixed:
The following problems are addressed in version 5.80 of Online ROM Flash Component for Linux - Smart Array P212, P410, P410i, P411, P711m, P712m, and P812:
-
On an HP P812 controller, executing several sequential Write operations to more than 75 hard drives would result in a controller lockup.
-
Protection has been added to prevent potential Smart Array controller hangs under rare conditions when hot-adding hard drives.
-
When running in a Solaris environment, Smart Array firmware version 5.80 works around an issue where the driver would not handle asynchronous events from the Smart Array controller properly.
-
An interaction issue occurred between the Smart Array Controller and HP SAS Expander card in which the Hard Drives attached to the HP SAS Expander were not being discovered occasionally upon boot up or hot plug.
-
On rare occasions, the Smart Array controller would reset the same SATA drive several times when a PHY is stuck longer than four seconds.
-
The Smart Array P711m and P712m would report false link errors.
-
The Open Connection timeout was reduced to 900 microseconds so that SAS connections terminate gracefully and data transfer stalls are prevented.
-
The Smart Array controller would not connect to hard drives within 20ms under heavy stress.
-
Upon power up, a Post message will now be displayed to the user to indicate that a cache module is needed for the P711m controller.
-
When running heavy I/O in RAID 5, while an HP P410 controller was connected to more than 17 SAS drives in an HP DL180 G6 server with a 25SFF backplane, a lockup issue (error code 0xAB or 0xEA) could occur.
-
During heavy I/O when the HP P711m controller is connected to a HP P2000sa G3 MSA Array System via a HP 6Gb SAS Switch, a lockup issue (error code 0x15) could occur.
-
After a system with (2) or more empty SAS storage boxes, Box 1, 2, 3 …, attached to an HP SAS Expander card is powered up and then a drive is hot plugged into Box 2 or above, ACU and ORCA would incorrectly display the drive in Box 1.
]]>
Problems Fixed:
The following problems are addressed in version 5.80 of Online ROM Flash Component for Linux - Smart Array P212, P410, P410i, P411, P711m, P712m, and P812:
-
On an HP P812 controller, executing several sequential Write operations to more than 75 hard drives would result in a controller lockup.
-
Protection has been added to prevent potential Smart Array controller hangs under rare conditions when hot-adding hard drives.
-
When running in a Solaris environment, Smart Array firmware version 5.80 works around an issue where the driver would not handle asynchronous events from the Smart Array controller properly.
-
An interaction issue occurred between the Smart Array Controller and HP SAS Expander card in which the Hard Drives attached to the HP SAS Expander were not being discovered occasionally upon boot up or hot plug.
-
On rare occasions, the Smart Array controller would reset the same SATA drive several times when a PHY is stuck longer than four seconds.
-
The Smart Array P711m and P712m would report false link errors.
-
The Open Connection timeout was reduced to 900 microseconds so that SAS connections terminate gracefully and data transfer stalls are prevented.
-
The Smart Array controller would not connect to hard drives within 20ms under heavy stress.
-
Upon power up, a Post message will now be displayed to the user to indicate that a cache module is needed for the P711m controller.
-
When running heavy I/O in RAID 5, while an HP P410 controller was connected to more than 17 SAS drives in an HP DL180 G6 server with a 25SFF backplane, a lockup issue (error code 0xAB or 0xEA) could occur.
-
During heavy I/O when the HP P711m controller is connected to a HP P2000sa G3 MSA Array System via a HP 6Gb SAS Switch, a lockup issue (error code 0x15) could occur.
-
After a system with (2) or more empty SAS storage boxes, Box 1, 2, 3 …, attached to an HP SAS Expander card is powered up and then a drive is hot plugged into Box 2 or above, ACU and ORCA would incorrectly display the drive in Box 1.
]]>
Problems Fixed:
The following problems are addressed in version 5.80 of Online ROM Flash Component for Linux - Smart Array P212, P410, P410i, P411, P711m, P712m, and P812:
-
On an HP P812 controller, executing several sequential Write operations to more than 75 hard drives would result in a controller lockup.
-
Protection has been added to prevent potential Smart Array controller hangs under rare conditions when hot-adding hard drives.
-
When running in a Solaris environment, Smart Array firmware version 5.80 works around an issue where the driver would not handle asynchronous events from the Smart Array controller properly.
-
An interaction issue occurred between the Smart Array Controller and HP SAS Expander card in which the Hard Drives attached to the HP SAS Expander were not being discovered occasionally upon boot up or hot plug.
-
On rare occasions, the Smart Array controller would reset the same SATA drive several times when a PHY is stuck longer than four seconds.
-
The Smart Array P711m and P712m would report false link errors.
-
The Open Connection timeout was reduced to 900 microseconds so that SAS connections terminate gracefully and data transfer stalls are prevented.
-
The Smart Array controller would not connect to hard drives within 20ms under heavy stress.
-
Upon power up, a Post message will now be displayed to the user to indicate that a cache module is needed for the P711m controller.
-
When running heavy I/O in RAID 5, while an HP P410 controller was connected to more than 17 SAS drives in an HP DL180 G6 server with a 25SFF backplane, a lockup issue (error code 0xAB or 0xEA) could occur.
-
During heavy I/O when the HP P711m controller is connected to a HP P2000sa G3 MSA Array System via a HP 6Gb SAS Switch, a lockup issue (error code 0x15) could occur.
-
After a system with (2) or more empty SAS storage boxes, Box 1, 2, 3 …, attached to an HP SAS Expander card is powered up and then a drive is hot plugged into Box 2 or above, ACU and ORCA would incorrectly display the drive in Box 1.
]]>
Problems Fixed:
The following problems are addressed in version 5.80 of Online ROM Flash Component for Linux - Smart Array P212, P410, P410i, P411, P711m, P712m, and P812:
-
On an HP P812 controller, executing several sequential Write operations to more than 75 hard drives would result in a controller lockup.
-
Protection has been added to prevent potential Smart Array controller hangs under rare conditions when hot-adding hard drives.
-
When running in a Solaris environment, Smart Array firmware version 5.80 works around an issue where the driver would not handle asynchronous events from the Smart Array controller properly.
-
An interaction issue occurred between the Smart Array Controller and HP SAS Expander card in which the Hard Drives attached to the HP SAS Expander were not being discovered occasionally upon boot up or hot plug.
-
On rare occasions, the Smart Array controller would reset the same SATA drive several times when a PHY is stuck longer than four seconds.
-
The Smart Array P711m and P712m would report false link errors.
-
The Open Connection timeout was reduced to 900 microseconds so that SAS connections terminate gracefully and data transfer stalls are prevented.
-
The Smart Array controller would not connect to hard drives within 20ms under heavy stress.
-
Upon power up, a Post message will now be displayed to the user to indicate that a cache module is needed for the P711m controller.
-
When running heavy I/O in RAID 5, while an HP P410 controller was connected to more than 17 SAS drives in an HP DL180 G6 server with a 25SFF backplane, a lockup issue (error code 0xAB or 0xEA) could occur.
-
During heavy I/O when the HP P711m controller is connected to a HP P2000sa G3 MSA Array System via a HP 6Gb SAS Switch, a lockup issue (error code 0x15) could occur.
-
After a system with (2) or more empty SAS storage boxes, Box 1, 2, 3 …, attached to an HP SAS Expander card is powered up and then a drive is hot plugged into Box 2 or above, ACU and ORCA would incorrectly display the drive in Box 1.
]]>
Problems Fixed:
The following problems are addressed in version 5.80 of Online ROM Flash Component for Linux - Smart Array P212, P410, P410i, P411, P711m, P712m, and P812:
-
On an HP P812 controller, executing several sequential Write operations to more than 75 hard drives would result in a controller lockup.
-
Protection has been added to prevent potential Smart Array controller hangs under rare conditions when hot-adding hard drives.
-
When running in a Solaris environment, Smart Array firmware version 5.80 works around an issue where the driver would not handle asynchronous events from the Smart Array controller properly.
-
An interaction issue occurred between the Smart Array Controller and HP SAS Expander card in which the Hard Drives attached to the HP SAS Expander were not being discovered occasionally upon boot up or hot plug.
-
On rare occasions, the Smart Array controller would reset the same SATA drive several times when a PHY is stuck longer than four seconds.
-
The Smart Array P711m and P712m would report false link errors.
-
The Open Connection timeout was reduced to 900 microseconds so that SAS connections terminate gracefully and data transfer stalls are prevented.
-
The Smart Array controller would not connect to hard drives within 20ms under heavy stress.
-
Upon power up, a Post message will now be displayed to the user to indicate that a cache module is needed for the P711m controller.
-
When running heavy I/O in RAID 5, while an HP P410 controller was connected to more than 17 SAS drives in an HP DL180 G6 server with a 25SFF backplane, a lockup issue (error code 0xAB or 0xEA) could occur.
-
During heavy I/O when the HP P711m controller is connected to a HP P2000sa G3 MSA Array System via a HP 6Gb SAS Switch, a lockup issue (error code 0x15) could occur.
-
After a system with (2) or more empty SAS storage boxes, Box 1, 2, 3 …, attached to an HP SAS Expander card is powered up and then a drive is hot plugged into Box 2 or above, ACU and ORCA would incorrectly display the drive in Box 1.
]]>
修正された問題点:
バージョン5.80のオンラインROMフラッシュコンポーネント for Linux - SmartアレイP212、P410、P410i、P411、P711m、P712m、およびP812で、以下の問題に対応しました。
-
HP P812コントローラーで、75台以上のハードディスクドライブに複数のシーケンシャルライト操作を実行すると、コントローラーのロックアップを引き起こす可能性があります。
-
ハードディスクドライブをホット追加した場合、まれな条件下で潜在的なSmartアレイコントローラーのハングアップを防ぐために保護を追加しました。
-
Solaris環境で実行する場合、Smartアレイファームウェアバージョン5.80は、ドライバーが正しくSmartアレイコントローラーからの非同期イベントを処理しない問題を回避します。
-
SmartアレイコントローラーおよびHP SASエキスパンダーカードの間で、HP SASエキスパンダーに接続されたハードディスクドライブが、ブートアップまたはホットプラグ時に時々検出されない問題が発生します。
-
ごくまれに、PHYが4秒以上スタックした場合、Smartアレイコントローラーが同一のSATAドライブを複数回リセットすることがあります。
-
SmartアレイP711mおよびP712mは、誤ったリンクエラーを報告することがあります。
-
Open Connectionのタイムアウトが900マイクロ秒に削減されたので、SAS接続は安全に終了し、データ転送の停止は回避されます。
-
Smartアレイコントローラーは、負荷が重い場合、20ms以内にハードディスクドライブに接続しないことがあります。
-
起動時に、P711mコントローラーにキャッシュモジュールが必要なことを知らせるために、POSTメッセージが表示されます。
-
RAID 5でI/O負荷が重い場合、25SFFバックプレーンのHP DL180 G6サーバーでHP P410コントローラーが17台以上のSASドライブに接続している間、ロックアップの問題(エラーコード0xABまたは0xEA)が発生する可能性があります。
-
I/Oの負荷が重い状態で、HP P711mコントローラーがHP 6Gb SASスイッチ経由でHP P2000 G3 MSA SASに接続されている場合、ロックアップの問題(エラーコード0x15)が発生する可能性があります。
-
2つ以上の空いているSASストレージボックス(ボックス1、2、3...)が、HP SASエキスパンダーカードに接続されているシステムの電源が入った後、ボックス2以上にドライブをホットプラグすると、ACUおよびORCAは誤ってドライブがボックス1にあると表示します。
]]>
해결된 문제:
Linux용 온라인 ROM 플래시 구성 요소(스마트 어레이 P212, P410, P410i, P411, P711m, P712m 및 P812) 버전 5.80에서 다음 문제가 해결되었습니다.
- HP P812 컨트롤러에서 75개 이상의 하드 드라이브에 몇 가지 연속적인 쓰기 작업을 실행하면 컨트롤러에 록업이 발생했습니다.
- 하드 드라이브를 강제 추가할 때 드물게 스마트 어레이 컨트롤러가 정지되는 문제를 방지하기 위한 보호 기능이 추가되었습니다.
- Solaris 환경에서 실행 시, 스마트 어레이 펌웨어 버전 5.80에서 드라이버가 스마트 어레이 컨트롤러의 비동기 이벤트를 적절하게 처리하지 못하는 문제가 있었습니다.
- 스마트 어레이 컨트롤러와 HP SAS 익스팬더 카드 사이에서, 부팅이나 핫 플러그 시 HP SAS 익스팬더 카드에 부착된 하드 드라이브가 가끔 인식되지 않는 상호 작용 문제가 있었습니다.
- 드물긴 하지만, PHY가 4초 이상 움직이지 않으면 스마트 어레이 컨트롤러가 동일한 SATA 드라이브를 몇 번 리셋하는 문제가 발생했습니다.
- 스마트 어레이 P711m 및 P712m이 잘못된 링크 오류를 보고했습니다.
- Open Connection 타임아웃이 900마이크로초로 단축되어 SAS 연결이 깔끔하게 종료되며 데이터 전송 지연이 방지됩니다.
- 과부하를 받으면 스마트 어레이 컨트롤러가 20m/s 안에 하드 드라이브에 연결되지 않았습니다.
- 가동 시, 이제 사용자에게 Post 메시지가 표시되므로 P711m 컨트롤러에 캐시 모듈이 필요하다는 것을 알 수 있습니다.
- 25SFF 백플레인이 있는 HP DL180 G6 서버에서 HP P410 컨트롤러가 17개 이상의 SAS 드라이브에 연결되어 있을 때 RAID 5에서 I/O에 과부하가 걸리면 록업 문제(오류 코드 0xAB or 0xEA)가 발생했습니다.
- HP P711m 컨트롤러가 HP 6Gb SAS 스위치를 통해 HP P2000sa G3 MSA 어레이 시스템에 연결되어 있으면 록업 문제(오류 코드 0x15)가 발생했습니다.
- HP SAS 확장기 카드에 부착되어 있고 (2)개 이상의 비어 있는 SAS 스토리지 박스, 박스 1, 2, 3 …이 있는 시스템이 가동되고 드라이브가 박스 2 이상에 핫 플러그된 후, ACU 및 ORCA가 드라이브를 박스 1로 잘못 표시했습니다.
]]>
修正的問題:
已解決適用於 Linux 的 5.80 版線上 ROM 更新元件 (Smart Array P212、P410、P410i、P411、P711m、P712m 及 P812) 中的以下問題:
- 在 HP P812 控制器上,對超過 75 個硬碟執行數個序列寫入作業會導致控制器鎖定。
- 已新增保護,以防止極少數狀況下在熱新增硬碟時可能出現 Smart Array 控制器當機。
- 在 Solaris 環境中執行時,Smart Array 5.80 版韌體解決了驅動程式無法正確處理 Smart Array 控制器的非同步事件這一問題。
- 在開機或熱插入後,偶爾會無法搜尋連接至 HP SAS 擴充器的硬碟,從而在 Smart Array 控制器與 HP SAS Expander 卡之間出現互動問題。
- 在極少數狀況下,若 PHY 停滯時間超過四秒,Smart Array 控制器將多次重設同一 SATA 磁碟機。
- Smart Array P711m 及 P712m 將報告虛假連結錯誤。
- 開啟連線逾時已縮短為 900 微秒,以便 SAS 連線可以順利終止,並防止資料傳輸停止。
- 在壓力繁重的狀況下,Smart Array 控制器不會在 20ms 內連線至硬碟。
- 開啟電源後,現在會為使用者顯示開機自我測試訊息,指示 P711m 控制器需要快取模組。
- RAID 5 中執行繁重的 I/O 時,若將 HP P410 控制器連線至 HP DL180 G6 伺服器 (含 25SFF 背板) 中超過 17 SAS 磁碟機,則會發生鎖定問題 (錯誤碼為 0xAB 或 0xEA)。
- 在 I/O 繁重時,若透過 HP 6Gb SAS 交換器將 HP P711m 控制器連線至 HP P2000sa G3 MSA 陣列系統,則會發生鎖定問題 (錯誤碼為 0x15)。
- 若系統至少有 (2) 個空 SAS 儲存盒 (盒 1、2、3 …) 連接至 HP SAS 擴充器卡,則在開啟系統電源,然後在盒 2 (或編號更大的盒) 中熱插入磁碟機後,ACU 及 ORCA 會不正確地顯示盒 1 中的磁碟機。
]]>
已解决的问题:
以下问题在面向 Linux 的在线 ROM Flash 组件 5.78 版本中得到解决 - 智能阵列 P212、P410、 P410i、 P411、 P711m、 P712m 和 P812:
- 在 HP P812 控制器上,向超过 75 块硬盘执行几个连续的写入操作会导致控制器锁定。
- 在罕见情况下,热添加硬盘时,已添加了保护以防止出现潜在的智能阵列控制器挂起。
- 在 Solaris 环境中运行时,智能阵列固件版本 5.78 解决了驱动程序无法正确处理智能阵列控制器出现异步事件的问题。
- 智能阵列控制器和 HP SAS 扩展卡之间出现互动问题,即开机或热插拔后,偶尔无法发现与 HP SAS 扩展卡连接的硬盘。
- 在极少数情况下,当 PHY 停留时间超过 4 秒,智能阵列控制器将多次重置相同的 SATA 驱动器。
- 智能阵列 P711m 和 P712m 将报告虚假的链接错误。
- 开放连接超时时间被减少到 900 微秒,以便正常终止 SAS 连接并防止数据传输中断。
- 在沉重负荷下,20 微秒内无法将智能阵列控制器与硬盘连接。
- 启动后,用户将立即看到一条 Post 消息,表示 P711m 控制器需要使用高速缓存模块。
- 当在 RAID 5 中运行繁重的 I/O 时,同时在采用 25SFF 背板的 HP DL180 G6 服务器中,向超过 17 块 SAS 驱动器连接 HP P410 控制器,可能发生锁定问题(错误代码 0xAB 或 0xEA)。
- 在繁重的 I/O 期间,当通过 HP 6Gb SAS 交换机将 HP P711m 控制器连接到 HP P2000sa G3 MSA 阵列系统,可能会发生锁定问题(错误代码 0x15)。
]]>
Problems Fixed:
The following problems are addressed in version 5.78 of Online ROM Flash Component for Linux - Smart Array P212, P410, P410i, P411, P711m, P712m, and P812:
-
On an HP P812 controller, executing several sequential Write operations to more than 75 hard drives would result in a controller lockup.
-
Protection has been added to prevent potential Smart Array controller hangs under rare conditions when hot-adding hard drives.
-
When running in a Solaris environment, Smart Array firmware version 5.78 works around an issue where the driver would not handle asynchronous events from the Smart Array controller properly.
-
An interaction issue occurred between the Smart Array Controller and HP SAS Expander card in which the Hard Drives attached to the HP SAS Expander were not being discovered occasionally upon boot up or hot plug.
-
On rare occasions, the Smart Array controller would reset the same SATA drive several times when a PHY is stuck longer than four seconds.
-
The Smart Array P711m and P712m would report false link errors.
-
The Open Connection timeout was reduced to 900 microseconds so that SAS connections terminate gracefully and data transfer stalls are prevented.
-
The Smart Array controller would not connect to hard drives within 20ms under heavy stress.
-
Upon power up, a Post message will now be displayed to the user to indicate that a cache module is needed for the P711m controller.
-
When running heavy I/O in RAID 5, while an HP P410 controller was connected to more than 17 SAS drives in an HP DL180 G6 server with a 25SFF backplane, a lockup issue (error code 0xAB or 0xEA) could occur.
-
During heavy I/O when the HP P711m controller is connected to a HP P2000sa G3 MSA Array System via a HP 6Gb SAS Switch, a lockup issue (error code 0x15) could occur.
]]>
Problems Fixed:
The following problems are addressed in version 5.78 of Online ROM Flash Component for Linux - Smart Array P212, P410, P410i, P411, P711m, P712m, and P812:
-
On an HP P812 controller, executing several sequential Write operations to more than 75 hard drives would result in a controller lockup.
-
Protection has been added to prevent potential Smart Array controller hangs under rare conditions when hot-adding hard drives.
-
When running in a Solaris environment, Smart Array firmware version 5.78 works around an issue where the driver would not handle asynchronous events from the Smart Array controller properly.
-
An interaction issue occurred between the Smart Array Controller and HP SAS Expander card in which the Hard Drives attached to the HP SAS Expander were not being discovered occasionally upon boot up or hot plug.
-
On rare occasions, the Smart Array controller would reset the same SATA drive several times when a PHY is stuck longer than four seconds.
-
The Smart Array P711m and P712m would report false link errors.
-
The Open Connection timeout was reduced to 900 microseconds so that SAS connections terminate gracefully and data transfer stalls are prevented.
-
The Smart Array controller would not connect to hard drives within 20ms under heavy stress.
-
Upon power up, a Post message will now be displayed to the user to indicate that a cache module is needed for the P711m controller.
-
When running heavy I/O in RAID 5, while an HP P410 controller was connected to more than 17 SAS drives in an HP DL180 G6 server with a 25SFF backplane, a lockup issue (error code 0xAB or 0xEA) could occur.
-
During heavy I/O when the HP P711m controller is connected to a HP P2000sa G3 MSA Array System via a HP 6Gb SAS Switch, a lockup issue (error code 0x15) could occur.
]]>
Problems Fixed:
The following problems are addressed in version 5.78 of Online ROM Flash Component for Linux - Smart Array P212, P410, P410i, P411, P711m, P712m, and P812:
-
On an HP P812 controller, executing several sequential Write operations to more than 75 hard drives would result in a controller lockup.
-
Protection has been added to prevent potential Smart Array controller hangs under rare conditions when hot-adding hard drives.
-
When running in a Solaris environment, Smart Array firmware version 5.78 works around an issue where the driver would not handle asynchronous events from the Smart Array controller properly.
-
An interaction issue occurred between the Smart Array Controller and HP SAS Expander card in which the Hard Drives attached to the HP SAS Expander were not being discovered occasionally upon boot up or hot plug.
-
On rare occasions, the Smart Array controller would reset the same SATA drive several times when a PHY is stuck longer than four seconds.
-
The Smart Array P711m and P712m would report false link errors.
-
The Open Connection timeout was reduced to 900 microseconds so that SAS connections terminate gracefully and data transfer stalls are prevented.
-
The Smart Array controller would not connect to hard drives within 20ms under heavy stress.
-
Upon power up, a Post message will now be displayed to the user to indicate that a cache module is needed for the P711m controller.
-
When running heavy I/O in RAID 5, while an HP P410 controller was connected to more than 17 SAS drives in an HP DL180 G6 server with a 25SFF backplane, a lockup issue (error code 0xAB or 0xEA) could occur.
-
During heavy I/O when the HP P711m controller is connected to a HP P2000sa G3 MSA Array System via a HP 6Gb SAS Switch, a lockup issue (error code 0x15) could occur.
]]>
Problems Fixed:
The following problems are addressed in version 5.78 of Online ROM Flash Component for Linux - Smart Array P212, P410, P410i, P411, P711m, P712m, and P812:
-
On an HP P812 controller, executing several sequential Write operations to more than 75 hard drives would result in a controller lockup.
-
Protection has been added to prevent potential Smart Array controller hangs under rare conditions when hot-adding hard drives.
-
When running in a Solaris environment, Smart Array firmware version 5.78 works around an issue where the driver would not handle asynchronous events from the Smart Array controller properly.
-
An interaction issue occurred between the Smart Array Controller and HP SAS Expander card in which the Hard Drives attached to the HP SAS Expander were not being discovered occasionally upon boot up or hot plug.
-
On rare occasions, the Smart Array controller would reset the same SATA drive several times when a PHY is stuck longer than four seconds.
-
The Smart Array P711m and P712m would report false link errors.
-
The Open Connection timeout was reduced to 900 microseconds so that SAS connections terminate gracefully and data transfer stalls are prevented.
-
The Smart Array controller would not connect to hard drives within 20ms under heavy stress.
-
Upon power up, a Post message will now be displayed to the user to indicate that a cache module is needed for the P711m controller.
-
When running heavy I/O in RAID 5, while an HP P410 controller was connected to more than 17 SAS drives in an HP DL180 G6 server with a 25SFF backplane, a lockup issue (error code 0xAB or 0xEA) could occur.
-
During heavy I/O when the HP P711m controller is connected to a HP P2000sa G3 MSA Array System via a HP 6Gb SAS Switch, a lockup issue (error code 0x15) could occur.
]]>
Problems Fixed:
The following problems are addressed in version 5.78 of Online ROM Flash Component for Linux - Smart Array P212, P410, P410i, P411, P711m, P712m, and P812:
-
On an HP P812 controller, executing several sequential Write operations to more than 75 hard drives would result in a controller lockup.
-
Protection has been added to prevent potential Smart Array controller hangs under rare conditions when hot-adding hard drives.
-
When running in a Solaris environment, Smart Array firmware version 5.78 works around an issue where the driver would not handle asynchronous events from the Smart Array controller properly.
-
An interaction issue occurred between the Smart Array Controller and HP SAS Expander card in which the Hard Drives attached to the HP SAS Expander were not being discovered occasionally upon boot up or hot plug.
-
On rare occasions, the Smart Array controller would reset the same SATA drive several times when a PHY is stuck longer than four seconds.
-
The Smart Array P711m and P712m would report false link errors.
-
The Open Connection timeout was reduced to 900 microseconds so that SAS connections terminate gracefully and data transfer stalls are prevented.
-
The Smart Array controller would not connect to hard drives within 20ms under heavy stress.
-
Upon power up, a Post message will now be displayed to the user to indicate that a cache module is needed for the P711m controller.
-
When running heavy I/O in RAID 5, while an HP P410 controller was connected to more than 17 SAS drives in an HP DL180 G6 server with a 25SFF backplane, a lockup issue (error code 0xAB or 0xEA) could occur.
-
During heavy I/O when the HP P711m controller is connected to a HP P2000sa G3 MSA Array System via a HP 6Gb SAS Switch, a lockup issue (error code 0x15) could occur.
]]>
修正された問題点:
バージョン5.78のオンラインROMフラッシュコンポーネント for Linux - SmartアレイP212、P410、P410i、P411、P711m、P712m、およびP812で、以下の問題に対応しました。
-
HP P812コントローラーで、75台以上のハードディスクドライブに複数のシーケンシャルライト操作を実行すると、コントローラーのロックアップを引き起こす可能性があります。
-
ハードディスクドライブをホット追加した場合、まれな条件下で潜在的なSmartアレイコントローラーのハングアップを防ぐために保護を追加しました。
-
Solaris環境で実行する場合、Smartアレイファームウェアバージョン5.78は、ドライバーが正しくSmartアレイコントローラーからの非同期イベントを処理しない問題を回避します。
-
SmartアレイコントローラーおよびHP SASエキスパンダーカードの間で、HP SASエキスパンダーに接続されたハードディスクドライブが、ブートアップまたはホットプラグ時に時々検出されない問題が発生します。
-
ごくまれに、PHYが4秒以上スタックした場合、Smartアレイコントローラーが同一のSATAドライブを複数回リセットすることがあります。
-
SmartアレイP711mおよびP712mは、誤ったリンクエラーを報告することがあります。
-
Open Connectionのタイムアウトが900マイクロ秒に削減されたので、SAS接続は安全に終了し、データ転送の停止は回避されます。
-
Smartアレイコントローラーは、負荷が重い場合、20ms以内にハードディスクドライブに接続しないことがあります。
-
起動時に、P711mコントローラーにキャッシュモジュールが必要なことを知らせるために、POSTメッセージが表示されます。
-
RAID 5でI/O負荷が重い場合、25SFFバックプレーンのHP DL180 G6サーバーでHP P410コントローラーが17台以上のSASドライブに接続している間、ロックアップの問題(エラーコード0xABまたは0xEA)が発生する可能性があります。
-
I/Oの負荷が重い状態で、HP P711mコントローラーがHP 6Gb SASスイッチ経由でHP P2000 G3 MSA SASに接続されている場合、ロックアップの問題(エラーコード0x15)が発生する可能性があります。
]]>
해결된 문제:
Linux용 온라인 ROM 플래시 구성 요소(스마트 어레이 P212, P410, P410i, P411, P711m, P712m 및 P812) 버전 5.78에서 다음 문제가 해결되었습니다.
- HP P812 컨트롤러에서 75개 이상의 하드 드라이브에 몇 가지 연속적인 쓰기 작업을 실행하면 컨트롤러에 록업이 발생했습니다.
- 하드 드라이브를 강제 추가할 때 드물게 스마트 어레이 컨트롤러가 정지되는 문제를 방지하기 위한 보호 기능이 추가되었습니다.
- Solaris 환경에서 실행 시, 스마트 어레이 펌웨어 버전 5.78에서 드라이버가 스마트 어레이 컨트롤러의 비동기 이벤트를 적절하게 처리하지 못하는 문제가 있었습니다.
- 스마트 어레이 컨트롤러와 HP SAS 익스팬더 카드 사이에서, 부팅이나 핫 플러그 시 HP SAS 익스팬더 카드에 부착된 하드 드라이브가 가끔 인식되지 않는 상호 작용 문제가 있었습니다.
- 드물긴 하지만, PHY가 4초 이상 움직이지 않으면 스마트 어레이 컨트롤러가 동일한 SATA 드라이브를 몇 번 리셋하는 문제가 발생했습니다.
- 스마트 어레이 P711m 및 P712m이 잘못된 링크 오류를 보고했습니다.
- Open Connection 타임아웃이 900마이크로초로 단축되어 SAS 연결이 깔끔하게 종료되며 데이터 전송 지연이 방지됩니다.
- 과부하를 받으면 스마트 어레이 컨트롤러가 20m/s 안에 하드 드라이브에 연결되지 않았습니다.
- 가동 시, 이제 사용자에게 Post 메시지가 표시되므로 P711m 컨트롤러에 캐시 모듈이 필요하다는 것을 알 수 있습니다.
- 25SFF 백플레인이 있는 HP DL180 G6 서버에서 HP P410 컨트롤러가 17개 이상의 SAS 드라이브에 연결되어 있을 때 RAID 5에서 I/O에 과부하가 걸리면 록업 문제(오류 코드 0xAB or 0xEA)가 발생했습니다.
- HP P711m 컨트롤러가 HP 6Gb SAS 스위치를 통해 HP P2000sa G3 MSA 어레이 시스템에 연결되어 있으면 록업 문제(오류 코드 0x15)가 발생했습니다.
]]>
修正的問題:
已解決適用於 Linux 的 5.78 版線上 ROM 更新元件 (Smart Array P212、P410、P410i、P411、P711m、P712m 及 P812) 中的以下問題:
- 在 HP P812 控制器上,對超過 75 個硬碟執行數個序列寫入作業會導致控制器鎖定。
- 已新增保護,以防止極少數狀況下在熱新增硬碟時可能出現 Smart Array 控制器當機。
- 在 Solaris 環境中執行時,Smart Array 5.78 版韌體解決了驅動程式無法正確處理 Smart Array 控制器的非同步事件這一問題。
- 在開機或熱插入後,偶爾會無法搜尋連接至 HP SAS 擴充器的硬碟,從而在 Smart Array 控制器與 HP SAS Expander 卡之間出現互動問題。
- 在極少數狀況下,若 PHY 停滯時間超過四秒,Smart Array 控制器將多次重設同一 SATA 磁碟機。
- Smart Array P711m 及 P712m 將報告虛假連結錯誤。
- 開啟連線逾時已縮短為 900 微秒,以便 SAS 連線可以順利終止,並防止資料傳輸停止。
- 在壓力繁重的狀況下,Smart Array 控制器不會在 20ms 內連線至硬碟。
- 開啟電源後,現在會為使用者顯示開機自我測試訊息,指示 P711m 控制器需要快取模組。
- RAID 5 中執行繁重的 I/O 時,若將 HP P410 控制器連線至 HP DL180 G6 伺服器 (含 25SFF 背板) 中超過 17 SAS 磁碟機,則會發生鎖定問題 (錯誤碼為 0xAB 或 0xEA)。
- 在 I/O 繁重時,若透過 HP 6Gb SAS 交換器將 HP P711m 控制器連線至 HP P2000sa G3 MSA 陣列系統,則會發生鎖定問題 (錯誤碼為 0x15)。
]]>
已修复的问题:
- 通过修改 FBWC 模块代码来改进 DDR2 DIMM,进而避免出现以下罕见情况,即显示“1783 POST 错误”消息后,控制器停止响应。
]]>
Problems Fixed:
-
Modified the FBWC module code to improve the training of the DDR2 DIMMs in order to prevent the rare occasions when 1783 POST error messages displays followed by an unresponsive controller.
]]>
Problems Fixed:
-
Modified the FBWC module code to improve the training of the DDR2 DIMMs in order to prevent the rare occasions when 1783 POST error messages displays followed by an unresponsive controller.
]]>
Problems Fixed:
-
Modified the FBWC module code to improve the training of the DDR2 DIMMs in order to prevent the rare occasions when 1783 POST error messages displays followed by an unresponsive controller.
]]>
Problems Fixed:
-
Modified the FBWC module code to improve the training of the DDR2 DIMMs in order to prevent the rare occasions when 1783 POST error messages displays followed by an unresponsive controller.
]]>
Problems Fixed:
-
Modified the FBWC module code to improve the training of the DDR2 DIMMs in order to prevent the rare occasions when 1783 POST error messages displays followed by an unresponsive controller.
]]>
修正された問題点:
-
まれに1783 POSTエラーメッセージが表示された後にコントローラーが応答しないことを防止するために、DDR2 DIMMのトレーニングを改善するFBWCモジュールのコードを変更しました。
]]>
해결된 문제:
- 드물지만 컨트롤러가 응답하지 않고 1783 POST 오류 메시지가 표시되는 경우를 방지하기 위해 FBWC 모듈 코드를 수정하여 DDR2 DIMM의 교육을 향상시켰습니다.
]]>
修正的問題:
- 已修改 FBWC 模組程式碼,以提升 DDR2 DIMM 的反應,避免顯示 1783 POST 錯誤訊息 (後接無回應控制器) 的罕見情況。
]]>
增强功能/新功能:
- 修改 POST 消息 1798,选择 F2 作为默认超时值,使其恢复至与固件版本 3.66 及其早期版本相同的设置。
]]>
Enhancements/New Features:
-
Modified POST message 1798 behavior to choose F2 as the default on timeout, returning it to the same behavior as firmware version 3.66 and previous releases.
]]>
Enhancements/New Features:
-
Modified POST message 1798 behavior to choose F2 as the default on timeout, returning it to the same behavior as firmware version 3.66 and previous releases.
]]>
Enhancements/New Features:
-
Modified POST message 1798 behavior to choose F2 as the default on timeout, returning it to the same behavior as firmware version 3.66 and previous releases.
]]>
Enhancements/New Features:
-
Modified POST message 1798 behavior to choose F2 as the default on timeout, returning it to the same behavior as firmware version 3.66 and previous releases.
]]>
Enhancements/New Features:
-
Modified POST message 1798 behavior to choose F2 as the default on timeout, returning it to the same behavior as firmware version 3.66 and previous releases.
]]>
改善点/新しい機能:
-
タイムアウトのデフォルトとしてF2を選択したときのPOSTメッセージ1798の動作を、ファームウェアバージョン3.66と以前のリリースと同じ動作になるよう変更しました。
]]>
개선 사항/새로운 기능:
- POST 메세지 1798을 수정하여 타임아웃 시 자동으로 F2를 선택하게 하고 동일한 정보를 펌웨어 3.66 및 이전 버전으로 반환하였습니다.
]]>
增進或新增功能:
- 修訂了 POST 訊息 1798 行為以選擇 F2 作為逾時預設, 將其返回至與韌體版本 3.66 與此前版本相同的行為。
]]>
Problems Fixed:
]]>
Problems Fixed:
]]>
Problems Fixed:
]]>
Problems Fixed:
]]>
Problems Fixed:
]]>
Problems Fixed:
]]>
修正された問題点:
]]>
Problems Fixed:
]]>
Problems Fixed:
]]>
Problems Fixed:
The following issues are resolved with firmware version 3.76:
- An operating system may intermittently hang during initialization after a reboot, when ProLiant server is configured with Smart Array controller in zero cache memory mode.
- The HP Smart Array controller would not boot in a PXE boot configuration.
- Concurrent host write and read commands to an overlapping block range could cause the Smart Array controller to not complete a host request.
]]>
Problems Fixed:
The following issues are resolved with firmware version 3.76:
- An operating system may intermittently hang during initialization after a reboot, when ProLiant server is configured with Smart Array controller in zero cache memory mode.
- The HP Smart Array controller would not boot in a PXE boot configuration.
- Concurrent host write and read commands to an overlapping block range could cause the Smart Array controller to not complete a host request.
]]>
Problems Fixed:
The following issues are resolved with firmware version 3.76:
- An operating system may intermittently hang during initialization after a reboot, when ProLiant server is configured with Smart Array controller in zero cache memory mode.
- The HP Smart Array controller would not boot in a PXE boot configuration.
- Concurrent host write and read commands to an overlapping block range could cause the Smart Array controller to not complete a host request.
]]>
Problems Fixed:
The following issues are resolved with firmware version 3.76:
- An operating system may intermittently hang during initialization after a reboot, when ProLiant server is configured with Smart Array controller in zero cache memory mode.
- The HP Smart Array controller would not boot in a PXE boot configuration.
- Concurrent host write and read commands to an overlapping block range could cause the Smart Array controller to not complete a host request.
]]>
Problems Fixed:
The following issues are resolved with firmware version 3.76:
- An operating system may intermittently hang during initialization after a reboot, when ProLiant server is configured with Smart Array controller in zero cache memory mode.
- The HP Smart Array controller would not boot in a PXE boot configuration.
- Concurrent host write and read commands to an overlapping block range could cause the Smart Array controller to not complete a host request.
]]>
Problems Fixed:
The following issues are resolved with firmware version 3.76:
- An operating system may intermittently hang during initialization after a reboot, when ProLiant server is configured with Smart Array controller in zero cache memory mode.
- The HP Smart Array controller would not boot in a PXE boot configuration.
- Concurrent host write and read commands to an overlapping block range could cause the Smart Array controller to not complete a host request.
]]>
修正された問題点:
ファームウェア バージョン3.76で、以下の問題を解決しました。
- ProLiantサーバーが、zero cache memoryモードのSmartアレイ コントローラーで構成されている場合、オペレーティング システムが再起動後の初期化中に断続的にハングアップすることがあります。
- HP Smartアレイ コントローラーは、PXEブート構成で起動しません。
- 重なるブロック範囲へのホストの同時書き込みおよび読み込み命令は、Smartアレイ コントローラーがホストの要求を完了することができません。
]]>
Problems Fixed:
The following issues are resolved with firmware version 3.76:
- An operating system may intermittently hang during initialization after a reboot, when ProLiant server is configured with Smart Array controller in zero cache memory mode.
- The HP Smart Array controller would not boot in a PXE boot configuration.
- Concurrent host write and read commands to an overlapping block range could cause the Smart Array controller to not complete a host request.
]]>
Problems Fixed:
The following issues are resolved with firmware version 3.76:
- An operating system may intermittently hang during initialization after a reboot, when ProLiant server is configured with Smart Array controller in zero cache memory mode.
- The HP Smart Array controller would not boot in a PXE boot configuration.
- Concurrent host write and read commands to an overlapping block range could cause the Smart Array controller to not complete a host request.
]]>
修复的问题:
- 已解决 Storageworks D2D G2 设备的一个问题:在重新启动后,HP 智能阵列控制器无法识别所连接的 HP StorageWorks MSA60 或 HP StorageWorks D2600 存储机架。
]]>
Problems Fixed:
- Resolved an issue on the Storageworks D2D G2 Appliances where upon reboot the attached HP StorageWorks MSA60 or HP StorageWorks D2600 storage shelves would not be recognized by the HP Smart Array attached controller.
]]>
Problems Fixed:
- Resolved an issue on the Storageworks D2D G2 Appliances where upon reboot the attached HP StorageWorks MSA60 or HP StorageWorks D2600 storage shelves would not be recognized by the HP Smart Array attached controller.
]]>
Problems Fixed:
- Resolved an issue on the Storageworks D2D G2 Appliances where upon reboot the attached HP StorageWorks MSA60 or HP StorageWorks D2600 storage shelves would not be recognized by the HP Smart Array attached controller.
]]>
Problems Fixed:
- Resolved an issue on the Storageworks D2D G2 Appliances where upon reboot the attached HP StorageWorks MSA60 or HP StorageWorks D2600 storage shelves would not be recognized by the HP Smart Array attached controller.
]]>
Problems Fixed:
- Resolved an issue on the Storageworks D2D G2 Appliances where upon reboot the attached HP StorageWorks MSA60 or HP StorageWorks D2600 storage shelves would not be recognized by the HP Smart Array attached controller.
]]>
修正された問題点:
- 付属のHP Smartアレイ コントローラーが、再起動時に接続されているHP StorageWorks MSA60あるいはHP StorageWorks D2600ストレージ シェルフを認識しないStorageWorks D2D G2アプライアンス上の問題を解決しました。
]]>
해결된 문제:
- 다시 부팅할 때 HP 스마트 어레이에 연결된 컨트롤러가 연결된 HP 스토리지웍스 MSA60 또는 HP 스토리지웍스 D2600 스토리지 선반을 인식하지 못하는 스토리지웍스 D2D G2 어플라이언스의 문제를 해결했습니다.
]]>
已解決的問題:
- 解決了 Storageworks D2D G2 裝置的問題,該問題為重新開機後,HP 智慧陣列連接的控制器無法辨識連接的 HP StorageWorks MSA60 或 HP StorageWorks D2600 儲存架。
]]>
增强功能/新功能:
- 增加了对连接到 HP StorageWorks D2600 和 HP StorageWorks D2700 的 HP SATA SSD 的支持。
]]>
Enhancements/New Features:
- Added support for HP SATA SSD's connected to the HP StorageWorks D2600 and the HP StorageWorks D2700.
]]>
Enhancements/New Features:
- Added support for HP SATA SSD's connected to the HP StorageWorks D2600 and the HP StorageWorks D2700.
]]>
Enhancements/New Features:
- Added support for HP SATA SSD's connected to the HP StorageWorks D2600 and the HP StorageWorks D2700.
]]>
Enhancements/New Features:
- Added support for HP SATA SSD's connected to the HP StorageWorks D2600 and the HP StorageWorks D2700.
]]>
Enhancements/New Features:
- Added support for HP SATA SSD's connected to the HP StorageWorks D2600 and the HP StorageWorks D2700.
]]>
改善点/新しい機能:
- HP StorageWorks D2600およびHP StorageWorks D2700に接続されたHP SATA SSDのサポートを追加しました。
]]>
향상된 기능/새로운 기능:
- HP 스토리지웍스 D2600 및 HP 스토리지웍스 D2700에 연결된 HP SATA SSD에 대한 지원을 추가했습니다.
]]>
增強/新功能:
- 新增對於連接至 HP StorageWorks D2600 與 HP StorageWorks D2700 的 HP SATA SSD 的支援。
]]>
固件依赖条件:
希望支持与 HP StorageWorks 600 Modular Disk System (MDS600) 连接的 HP Smart Array P812 的客户必须确认硬件满足以下最低固件版本(或更高版本)。
- 将 MDS600 连接至 HP Smart Array P812 之前,必须先将 HP Smart Array P812 更新至固件版本 3.50 或更高版本。
- 将 HP Smart Array P812 固件更新至 3.50 或更高版本后, 请执行以下步骤将 MDS600 与 HP Smart Array P812 控制器连接并开始运行 MSD600。
- 若 MDS600 的固件版本为 2.60,则可以连接至 HP Smart Array P812 控制器。
- 然而,运行与 HP Smart Array P812 连接的 MDS600,必须先将后者固件升级至版本 2.66。
- 若 MDS600 运行的固件版本为 2.54,则必须将其连接至以下智能阵列控制器并将固件版本升级至版本 2.66:
- 智能阵列 P700m 控制器
- 智能阵列 P411 控制器
- 智能阵列 P212 控制器
注释: 通过备选控制器方式将 MDS600 固件升级至版本 2.66 后,则可将 MDS600 与固件版本为 3.50 的 HP Smart Array P812 连接并开始运行。
如欲了解更多信息,请参考以下网址的客户顾问文档:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02437391
如需支持 HP StorageWorks D2000 机柜的双域功能,则 D2000 必须安装固件版本 0067 或更高版本。
存储子系统(例如,磁盘、控制器和服务器背板)的组件应以相同的数据传输速率或者系统带宽运行,并可向下浏览至素有组件的可接受层级。
连接至 HP Smart Array P410 或者 HP Smart Array P410i 的 HP SAS Expander Card 要求使用 SAS Expander Card 固件版本 2.06 或者更改版本以支持 6Gb SAS 和 3Gb SATA 驱动器。
运行 VMware ESX/ESXi 时,仅固件维护光盘中的 HP Smart Update Manager 才支持离线更新功能。
修复的问题:
- 对 HP 智能阵列硬盘驱动器进行热更换之后,其所在的扩展卡上连接的所有驱动器均报告位于仓位 0。此问题发生在 HP StorageWorks MSA60、HP StorageWorks MSA70 以及配备 12 仓位和 25 仓位背板的 HP ProLiant DL180 G6 上。
- 备用驱动器连接到 HP ProLiant ML150 G6 服务器上的非热插拔背板时没有加速转动。
- 电池供电写高速缓存 (BBWC) 处于耗尽状态时没有显示“无数据丢失”开机自检消息。电池耗尽时不当地永久禁用了 BBWC。
- 解决了智能阵列与导致智能阵列锁定的卡巴斯基反病毒工具之间的不兼容性问题。
- 修改了存储器接口参数,以便修复导致使用闪存支持的写高速缓存 (FBWC) 时控制器锁定的问题。
-
解决了间歇性条件的问题。在间歇性条件下,HP Smart Array P812 控制器在重新启动后无法找到逻辑磁盘,并且会报告以下开机自检时发生的问题之一。
1783- Slot 1 驱动器阵列控制器故障!
[命令故障 (cmd=11h, err=020h)]
或者
Slot 1 HP Smart Array P812 控制器 (512MB, V3.66) 0 逻辑磁盘
1719- Slot 1 驱动器阵列 - 系统加电前,出现控制器故障
(上一锁定代码 = 0xD4)
]]>
Firmware Dependency:
Customers who wish to support the HP Smart Array P812 connected to the HP StorageWorks 600 Modular Disk System (MDS600) must ensure that the hardware is at the minimum firmware versions (or later) as defined below.
- Before connecting the MDS600 to the HP Smart Array P812, you must first flash the HP Smart Array P812 to firmware version 3.50 or greater.
- After the HP Smart Array P812 firmware is flashed to 3.50 or greater, then the following steps need to be followed to connect the MDS600 with the HP Smart Array P812 controller and begin operating the MSD600.
- If the MDS600 has version 2.60 firmware, then it can be connected to the HP Smart Array P812 controller.
- However, to operate the MDS600 connected to HP Smart Array P812, the MDS600 must be upgraded to firmware version 2.66.
- If an MDS600 is running firmware version 2.54, it must be attached to one of the following Smart Array Controllers to perform the upgrade to firmware version 2.66:
- Smart Array P700m Controller
- Smart Array P411 Controller
- Smart Array P212 Controller
NOTE: Once the MDS600 firmware is upgraded to 2.66 using this alternate controller method, then the MDS600 can be connected to the HP Smart Array P812, which has firmware version 3.50, and begin operation.
For additional information, reference the Customer Advisory available at the following URL:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02437391
To support Dual Domain on HP StorageWorks D2000 enclosures, the D2000 must be at a minimum firmware version of 0067 or later.
The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card firmware version 2.06 or higher, to support 6Gb SAS and 3Gb SATA drives.
When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD.
Problems Fixed:
- After hot-replacement of an HP Smart Array HDD, all drives, which were attached to the expander where the HDD was replaced, report as being in Bay 0. Issue occurs on the HP StorageWorks MSA60, HP StorageWorks MSA70, and HP ProLiant DL180 G6 with 12 bay and 25 bay backplanes.
- Spare drives were not spinning up when attached to a non-hot plug backplane on the HP ProLiant ML150 G6 server.
- A No-Data Loss post message was not being displayed when the Battery Backed Write Cache (BBWC) was in a depleted state. The BBWC was improperly disabled permanently when the battery became depleted.
- Resolved an incompatibility between Smart Array and the Kaspersky Anti-Virus tool that resulted in a Smart Array lockup.
- Modified memory interface parameters to fix an issue resulting in controller lock-ups when utilizing a Flash-Backed Write Cache (FBWC).
-
Resolved intermittent condition in which the HP Smart Array P812 Controller may not locate logical drives after a power cycle and will report one of the following errors at post.
1783- Slot 1 Drive Array Controller Failure!
[Command failure (cmd=11h, err=020h)]
OR
Slot 1 HP Smart Array P812 Controller (512MB, V3.66) 0 logical drives
1719- Slot 1 Drive Array - A controllers failure event occurred prior to this
power-up, (Previous lockup code=0xD4)
]]>
Firmware Dependency:
Customers who wish to support the HP Smart Array P812 connected to the HP StorageWorks 600 Modular Disk System (MDS600) must ensure that the hardware is at the minimum firmware versions (or later) as defined below.
- Before connecting the MDS600 to the HP Smart Array P812, you must first flash the HP Smart Array P812 to firmware version 3.50 or greater.
- After the HP Smart Array P812 firmware is flashed to 3.50 or greater, then the following steps need to be followed to connect the MDS600 with the HP Smart Array P812 controller and begin operating the MSD600.
- If the MDS600 has version 2.60 firmware, then it can be connected to the HP Smart Array P812 controller.
- However, to operate the MDS600 connected to HP Smart Array P812, the MDS600 must be upgraded to firmware version 2.66.
- If an MDS600 is running firmware version 2.54, it must be attached to one of the following Smart Array Controllers to perform the upgrade to firmware version 2.66:
- Smart Array P700m Controller
- Smart Array P411 Controller
- Smart Array P212 Controller
NOTE: Once the MDS600 firmware is upgraded to 2.66 using this alternate controller method, then the MDS600 can be connected to the HP Smart Array P812, which has firmware version 3.50, and begin operation.
For additional information, reference the Customer Advisory available at the following URL:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02437391
To support Dual Domain on HP StorageWorks D2000 enclosures, the D2000 must be at a minimum firmware version of 0067 or later.
The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card firmware version 2.06 or higher, to support 6Gb SAS and 3Gb SATA drives.
When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD.
Problems Fixed:
- After hot-replacement of an HP Smart Array HDD, all drives, which were attached to the expander where the HDD was replaced, report as being in Bay 0. Issue occurs on the HP StorageWorks MSA60, HP StorageWorks MSA70, and HP ProLiant DL180 G6 with 12 bay and 25 bay backplanes.
- Spare drives were not spinning up when attached to a non-hot plug backplane on the HP ProLiant ML150 G6 server.
- A No-Data Loss post message was not being displayed when the Battery Backed Write Cache (BBWC) was in a depleted state. The BBWC was improperly disabled permanently when the battery became depleted.
- Resolved an incompatibility between Smart Array and the Kaspersky Anti-Virus tool that resulted in a Smart Array lockup.
- Modified memory interface parameters to fix an issue resulting in controller lock-ups when utilizing a Flash-Backed Write Cache (FBWC).
-
Resolved intermittent condition in which the HP Smart Array P812 Controller may not locate logical drives after a power cycle and will report one of the following errors at post.
1783- Slot 1 Drive Array Controller Failure!
[Command failure (cmd=11h, err=020h)]
OR
Slot 1 HP Smart Array P812 Controller (512MB, V3.66) 0 logical drives
1719- Slot 1 Drive Array - A controllers failure event occurred prior to this
power-up, (Previous lockup code=0xD4)
]]>
Firmware Dependency:
Customers who wish to support the HP Smart Array P812 connected to the HP StorageWorks 600 Modular Disk System (MDS600) must ensure that the hardware is at the minimum firmware versions (or later) as defined below.
- Before connecting the MDS600 to the HP Smart Array P812, you must first flash the HP Smart Array P812 to firmware version 3.50 or greater.
- After the HP Smart Array P812 firmware is flashed to 3.50 or greater, then the following steps need to be followed to connect the MDS600 with the HP Smart Array P812 controller and begin operating the MSD600.
- If the MDS600 has version 2.60 firmware, then it can be connected to the HP Smart Array P812 controller.
- However, to operate the MDS600 connected to HP Smart Array P812, the MDS600 must be upgraded to firmware version 2.66.
- If an MDS600 is running firmware version 2.54, it must be attached to one of the following Smart Array Controllers to perform the upgrade to firmware version 2.66:
- Smart Array P700m Controller
- Smart Array P411 Controller
- Smart Array P212 Controller
NOTE: Once the MDS600 firmware is upgraded to 2.66 using this alternate controller method, then the MDS600 can be connected to the HP Smart Array P812, which has firmware version 3.50, and begin operation.
For additional information, reference the Customer Advisory available at the following URL:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02437391
To support Dual Domain on HP StorageWorks D2000 enclosures, the D2000 must be at a minimum firmware version of 0067 or later.
The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card firmware version 2.06 or higher, to support 6Gb SAS and 3Gb SATA drives.
When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD.
Problems Fixed:
- After hot-replacement of an HP Smart Array HDD, all drives, which were attached to the expander where the HDD was replaced, report as being in Bay 0. Issue occurs on the HP StorageWorks MSA60, HP StorageWorks MSA70, and HP ProLiant DL180 G6 with 12 bay and 25 bay backplanes.
- Spare drives were not spinning up when attached to a non-hot plug backplane on the HP ProLiant ML150 G6 server.
- A No-Data Loss post message was not being displayed when the Battery Backed Write Cache (BBWC) was in a depleted state. The BBWC was improperly disabled permanently when the battery became depleted.
- Resolved an incompatibility between Smart Array and the Kaspersky Anti-Virus tool that resulted in a Smart Array lockup.
- Modified memory interface parameters to fix an issue resulting in controller lock-ups when utilizing a Flash-Backed Write Cache (FBWC).
-
Resolved intermittent condition in which the HP Smart Array P812 Controller may not locate logical drives after a power cycle and will report one of the following errors at post.
1783- Slot 1 Drive Array Controller Failure!
[Command failure (cmd=11h, err=020h)]
OR
Slot 1 HP Smart Array P812 Controller (512MB, V3.66) 0 logical drives
1719- Slot 1 Drive Array - A controllers failure event occurred prior to this
power-up, (Previous lockup code=0xD4)
]]>
Firmware Dependency:
Customers who wish to support the HP Smart Array P812 connected to the HP StorageWorks 600 Modular Disk System (MDS600) must ensure that the hardware is at the minimum firmware versions (or later) as defined below.
- Before connecting the MDS600 to the HP Smart Array P812, you must first flash the HP Smart Array P812 to firmware version 3.50 or greater.
- After the HP Smart Array P812 firmware is flashed to 3.50 or greater, then the following steps need to be followed to connect the MDS600 with the HP Smart Array P812 controller and begin operating the MSD600.
- If the MDS600 has version 2.60 firmware, then it can be connected to the HP Smart Array P812 controller.
- However, to operate the MDS600 connected to HP Smart Array P812, the MDS600 must be upgraded to firmware version 2.66.
- If an MDS600 is running firmware version 2.54, it must be attached to one of the following Smart Array Controllers to perform the upgrade to firmware version 2.66:
- Smart Array P700m Controller
- Smart Array P411 Controller
- Smart Array P212 Controller
NOTE: Once the MDS600 firmware is upgraded to 2.66 using this alternate controller method, then the MDS600 can be connected to the HP Smart Array P812, which has firmware version 3.50, and begin operation.
For additional information, reference the Customer Advisory available at the following URL:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02437391
To support Dual Domain on HP StorageWorks D2000 enclosures, the D2000 must be at a minimum firmware version of 0067 or later.
The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card firmware version 2.06 or higher, to support 6Gb SAS and 3Gb SATA drives.
When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD.
Problems Fixed:
- After hot-replacement of an HP Smart Array HDD, all drives, which were attached to the expander where the HDD was replaced, report as being in Bay 0. Issue occurs on the HP StorageWorks MSA60, HP StorageWorks MSA70, and HP ProLiant DL180 G6 with 12 bay and 25 bay backplanes.
- Spare drives were not spinning up when attached to a non-hot plug backplane on the HP ProLiant ML150 G6 server.
- A No-Data Loss post message was not being displayed when the Battery Backed Write Cache (BBWC) was in a depleted state. The BBWC was improperly disabled permanently when the battery became depleted.
- Resolved an incompatibility between Smart Array and the Kaspersky Anti-Virus tool that resulted in a Smart Array lockup.
- Modified memory interface parameters to fix an issue resulting in controller lock-ups when utilizing a Flash-Backed Write Cache (FBWC).
-
Resolved intermittent condition in which the HP Smart Array P812 Controller may not locate logical drives after a power cycle and will report one of the following errors at post.
1783- Slot 1 Drive Array Controller Failure!
[Command failure (cmd=11h, err=020h)]
OR
Slot 1 HP Smart Array P812 Controller (512MB, V3.66) 0 logical drives
1719- Slot 1 Drive Array - A controllers failure event occurred prior to this
power-up, (Previous lockup code=0xD4)
]]>
Firmware Dependency:
Customers who wish to support the HP Smart Array P812 connected to the HP StorageWorks 600 Modular Disk System (MDS600) must ensure that the hardware is at the minimum firmware versions (or later) as defined below.
- Before connecting the MDS600 to the HP Smart Array P812, you must first flash the HP Smart Array P812 to firmware version 3.50 or greater.
- After the HP Smart Array P812 firmware is flashed to 3.50 or greater, then the following steps need to be followed to connect the MDS600 with the HP Smart Array P812 controller and begin operating the MSD600.
- If the MDS600 has version 2.60 firmware, then it can be connected to the HP Smart Array P812 controller.
- However, to operate the MDS600 connected to HP Smart Array P812, the MDS600 must be upgraded to firmware version 2.66.
- If an MDS600 is running firmware version 2.54, it must be attached to one of the following Smart Array Controllers to perform the upgrade to firmware version 2.66:
- Smart Array P700m Controller
- Smart Array P411 Controller
- Smart Array P212 Controller
NOTE: Once the MDS600 firmware is upgraded to 2.66 using this alternate controller method, then the MDS600 can be connected to the HP Smart Array P812, which has firmware version 3.50, and begin operation.
For additional information, reference the Customer Advisory available at the following URL:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02437391
To support Dual Domain on HP StorageWorks D2000 enclosures, the D2000 must be at a minimum firmware version of 0067 or later.
The components of a storage subsystem (e.g. the drive, the controller, and the server backplane) should operate at the same data transfer rate or the system bandwidth will be negotiated down to an acceptable level for all components.
HP SAS Expander Card connected to an HP Smart Array P410 or HP Smart Array P410i will require SAS Expander Card firmware version 2.06 or higher, to support 6Gb SAS and 3Gb SATA drives.
When running VMware ESX/ESXi only offline updates are supported using the HP Smart Update Manager on the Firmware Maintenance CD.
Problems Fixed:
- After hot-replacement of an HP Smart Array HDD, all drives, which were attached to the expander where the HDD was replaced, report as being in Bay 0. Issue occurs on the HP StorageWorks MSA60, HP StorageWorks MSA70, and HP ProLiant DL180 G6 with 12 bay and 25 bay backplanes.
- Spare drives were not spinning up when attached to a non-hot plug backplane on the HP ProLiant ML150 G6 server.
- A No-Data Loss post message was not being displayed when the Battery Backed Write Cache (BBWC) was in a depleted state. The BBWC was improperly disabled permanently when the battery became depleted.
- Resolved an incompatibility between Smart Array and the Kaspersky Anti-Virus tool that resulted in a Smart Array lockup.
- Modified memory interface parameters to fix an issue resulting in controller lock-ups when utilizing a Flash-Backed Write Cache (FBWC).
-
Resolved intermittent condition in which the HP Smart Array P812 Controller may not locate logical drives after a power cycle and will report one of the following errors at post.
1783- Slot 1 Drive Array Controller Failure!
[Command failure (cmd=11h, err=020h)]
OR
Slot 1 HP Smart Array P812 Controller (512MB, V3.66) 0 logical drives
1719- Slot 1 Drive Array - A controllers failure event occurred prior to this
power-up, (Previous lockup code=0xD4)
]]>
ファームウェアの関連性:
HP StorageWorks Modular Disk System 600(MDS600)に接続されたHP Smartアレイ P812のサポートが必要な場合、ハードウェアが以下のバージョン以降のファームウェアの最小要件を満たしている必要があります。
- MDS600をHP Smartアレイ P812に接続する前に、HP Smartアレイ P812のファームウェアをバージョン3.50以降にフラッシュする必要があります。
- HP Smartアレイ P812のファームウェアを3.50以降にフラッシュした後、MDS600をHP Smartアレイ P812コントローラーに接続して、MDS600の動作を開始するためには、以下の手順に従う必要があります。
- MDS600がバージョン2.60のファームウェアの場合、HP Smartアレイ P812コントローラーに接続することができます。
- しかし、HP Smartアレイ P812に接続したMDS600を動作させるためには、MDS600は、ファームウェア バージョン2.66へのアップグレードが必要です。
- MDS600がバージョン2.54のファームウェアの場合、ファームウェア バージョン2.66へのアップグレードを実行するためには、以下のいずれかのSmartアレイ コントローラーと接続する必要があります。
- Smartアレイ P700mコントローラー
- Smartアレイ P411コントローラー
- Smartアレイ P212コントローラー
注: まず、このコントローラーの代替方法を使ってMDS600のファームウェアを2.66にアップデートし、その後MDS600をファームウェア バージョン3.50のHP Smartアレイ P812に接続して、動作を開始することができます。
詳しくは、以下のURLのCustomer Advisoryを参照してください。
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02437391(英語)
HP StorageWorks D2000エンクロージャーでデュアル ドメインをサポートするには、D2000のファームウェア バージョンを0067以降にする必要があります。
ストレージ サブシステムのコンポーネント(例、ドライブ、コントローラー、およびサーバー バックプレーン)は、同じデータ転送レートで動作しなければなりません。そうでない場合はシステム バンド幅はすべてのコンポーネントが受け入れ可能なレベルにネゴシエートされます。
HP Smartアレイ P410またはHP Smartアレイ P410iに接続されたHP SASエキスパンダー カードは、6Gb SASおよび3Gb SATAドライブをサポートするために、SASエキスパンダー カード ファームウェア バージョン2.06以降が必要です。
VMware ESX/ESXiを実行している場合、Firmware Maintenance CD上のHP Smart Update Managerを使用したオフライン アップデートのみサポートされます。
修正された問題点:
- 1台のHP SmartアレイHDDをホット リプレースした後、交換したHDDがあるエキスパンダーに接続されている全てのドライブは、ベイ0にあると報告されました。 HP StorageWorks MSA60、HP StorageWorks MSA70、および12ベイおよび25ベイのバックプレーンのHP ProLiant DL180 G6上で、この問題は発生します。
- HP ProLiant ML150 G6サーバーのノンホット プラグ バックプレーンに接続された場合、スペア ドライブはスピンアップしませんでした。
- バッテリ バックアップ付きライト キャッシュ(BBWC)が劣化した状態の場合、No-Data LossのPOSTメッセージが表示されませんでした。 バッテリが空になった場合、BBWCは間違って無効にされました。
- SmartアレイとSmartアレイをロックアップさせるKaspersky Anti-Virusツールとの間の互換性の問題を解決しました。
- フラッシュバック式ライトキャッシュ(FBWC)を利用した場合、コントローラーのロックアップを引き起こす問題を修正するために、メモリ インターフェイスのパラメーターを変更しました。
-
HP SmartアレイP812コントローラーが電源投入後、論理ドライブを認識しない、またはPOST時に以下のエラーの一つを報告する、断続的な状態を解決しました。
1783- Slot 1 Drive Array Controller Failure!
[Command failure (cmd=11h, err=020h)]
または
Slot 1 HP Smart Array P812 Controller (512MB, V3.66) 0 logical drives
1719- Slot 1 Drive Array - A controllers failure event occurred prior to this
power-up, (Previous lockup code=0xD4)
]]>
펌웨어 종속성:
HP 스토리지웍스 600 모듈식 디스크 시스템(MDS600)과 연결되어 있는 HP 스마트 어레이 P812의 지원을 원하는 고객들은 반드시 다음과 같은 최소한의 펌웨어 버전(또는 이상)이 하드웨어에 설치되어 있는지를 확인해야 합니다.
- MDS600을 HP 스마트 어레이 P812로 연결하기 전 HP 스마트 어레이 P812를 3.50 이상 펌웨어 버전으로 업데이트해야 합니다.
- HP 스마트 어레이 P812 펌웨어가 3.50 이상 버전으로 업데이트되면 HP 스마트 어레이 P812 컨트롤러에 MSD600을 연결한 다음 이를 실행하기 위해서는 다음 절차를 진행해야 합니다.
- MDS600에 펌웨어 2.60 버전이 설치되어 있는 경우 HP 스마트 어레이 P812 컨트롤러와 연결 가능합니다.
- 하지만 HP 스마트 어레이 P812와 연결되어 있는 MDS600을 실행하려면 MDS600의 펌웨어를 2.66 이상 버전으로 업그레이드해야 합니다.
- MDS600에 펌웨어 2.54 버전이 설치되어 있는 경우 다음 중 하나의 스마트 어레이 컨트롤러에 장착되어 펌웨어 2.66 버전으로 업그레이드해야 합니다.
- 스마트 어레이 P700m 컨트롤러
- 스마트 어레이 P411 컨트롤러
- 스마트 어레이 P212 컨트롤러
주: 해당 컨트롤러를 통해 MDS600 펌웨어를 2.66 버전으로 업그레이드하면 펌웨어 3.50 버전이 설치되어 있는 HP 스마트 어레이 P812로 MDS600을 연결하여 이를 실행할 수 있습니다.
자세한 정보는 다음 URL을 통해 제공되는 고객 권고사항을 참조하십시오.
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02437391
HP 스토리지웍스 D2000 인클로저에서 이중 도메인을 지원하려면 D2000에 0067 이상 버전의 펌웨어가 설치되어야 합니다.
스토리지 하위 시스템의 구성 요소들(예: 드라이버, 컨트롤러 및 서버 백플레인)이 동일한 데이터 전송 속도로 작동하거나 시스템 대역폭이 모든 구성 요소에 적용될 수 있도록 조정됩니다.
HP 스마트 어레이 P410 또는 HP 스마트 어레이 P410i에 연결되어 있는 HP SAS 익스팬더 카드는 6Gb SAS와 3Gb SATA 드라이브 지원을 위해 2.06 이상 버전의 SAS 익스팬더 카드 펌웨어를 필요로 하고 있습니다.
VMware ESX/ESXi 실행 시 펌웨어 유지관리 CD의 HP Smart Update Manager를 통해 업데이트하려는 경우 오프라인 업데이트만 지원됩니다.
해결된 문제:
- HP 스마트 어레이 HDD를 강제 교체하면 HDD가 교체된 익스팬더에 장착되어 있는 모든 드라이버가 Bay 0에 있는 것으로 보고됩니다. 해당 문제는 HP 스토리지웍스 MSA60, HP 스토리지웍스 MSA70 및 HP 프로라이언트 DL180 G6(12 베이와 25 베이 백플레인 장착)에서 발생합니다.
- HP 프로라이언트 ML150 G6 서버의 핫 플러그 미지원 백플레인에 장착되면 예비 드라이브는 스핀업이 되지 않습니다.
- BBWC(Battery Backed Write Cache)가 고갈 상태에 처했어도 No-Data Loss post 메시지가 표시되지 않습니다. 배터리가 고갈되면 BBWC는 부적절하게 영구적으로 비활성화될 수 있습니다.
- 스마트 어레이 록업 문제를 유발하는 스마트 어레이와 Kaspersky 백신 툴 사이의 비호환성 문제를 해결하였습니다.
- 메모리 인터페이스 파라미터를 수정하여 FBWC(Flash-Backed Write Cache) 사용 시 컨트롤러가 록업되는 문제를 해결하였습니다.
-
전원을 껐다 켠 후 HP 스마트 어레이 P812 컨트롤러가 가끔 논리 드라이브를 찾지 못하고 POST 시 다음 오류 중 하나를 보고하는 문제를 해결했습니다.
1783- 슬롯 1 드라이브 어레이 컨트롤러 오류!
[명령 실패(cmd=11h, err=020h)]
또는
슬롯 1 HP 스마트 어레이 P812 컨트롤러(512MB, V3.66) 0 논리 드라이브
1719- 슬롯 1 드라이브 어레이 - 이번에 전원을 켜기 전에 컨트롤러 오류 이벤트가
발생했음(이전 록업 코드=0xD4)
]]>
韌體相依性:
想要支援連接至 HP StorageWorks 600 模組化磁盤系統 (MDS600) 的 HP Smart Array P812 客戶必須確保硬體的最低韌體版本為如下所示(或更高版本)。
- 在連接 MDS600 至 HP Smart Array P812 之前,必須將 HP Smart Array P812 刷新至韌體版本 3.50 或更高版本。
- 在 HP Smart Array P812 韌體刷新至 3.50 或更高版本後,需要採取如下步驟來連接 MDS600 與 HP Smart Array P812 控制器,然後開始操作 MSD600。
- 如果 MDS600 的韌體版本為 2.60, 則可以連接至 HP Smart Array P812 控制器。
- 但是,要運行連接至 HP Smart Array P812 的 MDS600,MDS600 必須升級至韌體版本 2.66。
- 如果 MDS600 執行的韌體版本為 2.54,則必須連接如下之一的 Smart Array 控制器來執行韌體升級至 2.66:
- Smart Array P700m 控制器
- Smart Array P411 控制器
- Smart Array P212 控制器
注意: 當使用此備用控制器方法將 MDS600 韌體升級至 2.66 後,MDS600 即可連接至韌體版本為 3.50 的 HP Smart Array P812,然後開始操作。
有關更多資訊,請參考如下 URL 的可用客戶諮詢文件:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02437391
要支援 HP StorageWorks D2000 機櫃上的雙域,D2000 的最低韌體版本要為 0067 或更高版本。
此儲存子系統的元件(例如磁碟機、控制器與伺服器背板)應當在同樣的資料傳輸速率與系統頻寬上運行,從而所有元件都處於一個可接受的水準上。
連接至 HP Smart Array P410 或 HP Smart Array P410i 的 HP SAS Expander 卡必須要有 SAS Expander 卡韌體版本 2.06 或更高版本來支援 6Gb SAS 與 3Gb SATA 磁碟機。
在執行 VMware ESX/ESXi 時,使用韌體維護 CD 上的 HP Smart Update Manager 僅支援離線更新。
已修正的問題:
- 在熱更換 HP Smart Array HDD 後,所有連接至擴充卡(HDD 更換處)的磁碟機均報告為位於機槽 0。此問題發生在 HP StorageWorks MSA60、HP StorageWorks MSA70 與 HP ProLiant DL180 G6,含 12 個機槽與 25 個機槽背板。
- 備用磁碟機連接至 HP ProLiant ML150 G6 伺服器上的非熱拔插背板後無法運轉。
- 當電池備援寫入快取 (BBWC) 處於耗盡狀態時,無法顯示「No-Data Loss」(無資料遺失)POST 訊息。當電池耗盡時 BBWC 會永久不正常停用。
- 解決了導致 Smart Array 鎖定之 Smart Array 與 Kaspersky Anti-Virus 工具間的不相容性。
- 已修改記憶記憶體介面參數,以解決在使用 Flash-Backed Write Cache (FBWC) 導致控制器鎖定的問題。
-
解決了間歇性情況,該情況為 HP Smart Array P812 控制器無法在重新開啟電源後找到邏輯磁碟機,並在 POST 期間報告下列其中一項錯誤。
1783- Slot 1 Drive Array Controller Failure!
[Command failure (cmd=11h, err=020h)](1783- 插槽 1 磁碟機陣列控制器故障![命令失敗 (cmd=11h,err=020h)])
或
Slot 1 HP Smart Array P812 Controller (512MB, V3.66) 0 logical drives(插槽 1 HP Smart Array P812 控制器 (512MB,V3.66) 0 邏輯磁碟機)
1719- Slot 1 Drive Array - A controllers failure event occurred prior to this
power-up, (Previous lockup code=0xD4)(1719- 插槽 1 磁碟機陣列 - 此次開機前發生控制器故障事件,(原先鎖定代碼=0xD4))
]]>
firmware:smartarray
firmware:smartarray
firmware:smartarray
firmware:smartarray
firmware:smartarray
firmware:smartarray
firmware:smartarray
103C
323A
103C
3241
103C
323A
103C
3245
103C
323A
103C
3247
103c
323a
103c
3249
103C
323A
103C
3243
103C
323A
103C
324A
103C
323A
103C
324B
CP027483.scexe
Fri, 10 Jul 2015 02:40:17
2
1
True
14ef73e580
hp-firmware-smartarray-14ef73e580
14ef73e580
smartcomponent-linux-firmware-array
hp-firmware-smartarray-14ef73e580
hp-firmware-smartarray-14ef73e580
2
__ENDCPXML__ + j~ M } @ O ]A큤m$$$$$mAm UwUwUwUwUwUwUwUwUwUwUwUw c66eaef3ca367e8af92e632d2e51efad e2f3d47eae8cf979e970f40eff0d4e5a 2d363c87e7956842b7912c4795e69e66 339f79de13391135ded7c3064bda060a fb9508cfd1e23c3f26669fb5f1c0187d d76c01031b18b1c685e0c5e0ac1e3242 a6428e3287e6d372336515500129ce83 885f0d12911c2f03c7a0e532cd13826f d1dcc4fd197929d56a266756ab2df71e 3afcfa39bdb2ea99035a00826434a631 root root root root root root root root root root root root root root root root root root root root root root root root hp-firmware-smartarray-14ef73e580-6.64-2.src.rpm firmware(hp:firmware:3241103c) firmware(hp:firmware:3241103c) firmware(hp:firmware:3243103c) firmware(hp:firmware:3243103c) firmware(hp:firmware:3245103c) firmware(hp:firmware:3245103c) firmware(hp:firmware:3247103c) firmware(hp:firmware:3247103c) firmware(hp:firmware:3249103c) firmware(hp:firmware:3249103c) firmware(hp:firmware:324b103c) firmware(hp:firmware:324b103c) firmware(hp:firmware:324a103c) firmware(hp:firmware:324a103c) firmware(pci:v0000103Cd0000323Asv0000103Csd00003241bc*sc*i*) firmware(pci:v0000103Cd0000323Asv0000103Csd00003241bc*sc*i*) firmware(pci:v0000103Cd0000323Asv0000103Csd00003245bc*sc*i*) firmware(pci:v0000103Cd0000323Asv0000103Csd00003245bc*sc*i*) firmware(pci:v0000103Cd0000323Asv0000103Csd00003247bc*sc*i*) firmware(pci:v0000103Cd0000323Asv0000103Csd00003247bc*sc*i*) firmware(pci:v0000103Cd0000323Asv0000103Csd00003249bc*sc*i*) firmware(pci:v0000103Cd0000323Asv0000103Csd00003249bc*sc*i*) firmware(pci:v0000103Cd0000323Asv0000103Csd00003243bc*sc*i*) firmware(pci:v0000103Cd0000323Asv0000103Csd00003243bc*sc*i*) firmware(pci:v0000103Cd0000323Asv0000103Csd0000324Abc*sc*i*) firmware(pci:v0000103Cd0000323Asv0000103Csd0000324Abc*sc*i*) firmware(pci:v0000103Cd0000323Asv0000103Csd0000324Bbc*sc*i*) firmware(pci:v0000103Cd0000323Asv0000103Csd0000324Bbc*sc*i*) hp-firmware-smartarray-14ef73e580 hp-firmware-smartarray-14ef73e580(x86-32)
@ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ rpmlib(VersionedDependencies) /bin/sh /bin/sh /bin/sh rpmlib(PayloadFilesHavePrefix) rpmlib(CompressedFileNames) /bin/sh libc.so.6 libc.so.6(GLIBC_2.0) libc.so.6(GLIBC_2.1) libc.so.6(GLIBC_2.1.3) libc.so.6(GLIBC_2.2) libc.so.6(GLIBC_2.2.3) libc.so.6(GLIBC_2.3) libdl.so.2 libdl.so.2(GLIBC_2.0) libdl.so.2(GLIBC_2.1) libgcc_s.so.1 libgcc_s.so.1(GCC_3.0) libm.so.6 libm.so.6(GLIBC_2.0) libpthread.so.0 libpthread.so.0(GLIBC_2.0) libpthread.so.0(GLIBC_2.1) libpthread.so.0(GLIBC_2.1.1) libpthread.so.0(GLIBC_2.2) libpthread.so.0(GLIBC_2.3.2) libstdc++.so.6 libstdc++.so.6(GLIBCXX_3.4) libstdc++.so.6(GLIBCXX_3.4.5) 3.0.3-1 4.0-1 3.0.4-1 4.8.1 U@U-@T}T,@SϣSR@S@S-SRa"R_@R^Q@Q#i@Q"PP1@O N@NNR@N N@N]N@NJ[NI
@NGN|@N*N@N M@MM\@L@LmLk@K,KbKa|@KG@K*@K(K@K?Jv@J$JmJlE@J'@I@Io@IIm@II@IxI'@II@I2I@II>@HP Linux Development 6.64-2 HP Linux Development 6.64 HP Linux Development 6.62 HP Linux Development 6.62 HP Linux Development 6.60 HP Linux Development 6.60 HP Linux Development 6.50 HP Linux Development 6.48 HP Linux Development 6.46 HP Linux Development 6.40-2 HP Linux Development 6.40-2 HP Linux Development 6.40-2 HP Linux Development 6.10 HP Linux Development 6.00 HP Linux Development 5.90 HP Linux Development 5.70-2 HP Linux Development 5.70-2 HP Linux Development 5.70 HP Linux Development 5.36 HP Linux Development 5.32 HP Linux Development 5.32 HP Linux Development 5.32 HP Linux Development 5.14 HP Linux Development 5.12 HP Linux Development 5.12 HP Linux Development 5.08 HP Linux Development 5.08 HP Linux Development 5.08 HP Linux Development 5.06 HP Linux Development 5.06 HP Linux Development 4.02-2 HP Linux Development 4.02-2 HP Linux Development 4.02 HP Linux Development 3.66 HP Linux Development 3.66 HP Linux Development 3.52 HP Linux Development 3.50 HP Linux Development 3.50 HP Linux Development 3.00 HP Linux Development 2.76 HP Linux Development 2.74-2 HP Linux Development 2.74 HP Linux Development 2.72-2 HP Linux Development 2.72-2 HP Linux Development 2.72 HP Linux Development 2.72 HP Linux Development 2.50 HP Linux Development 2.50 HP Linux Development 2.00 HP Linux Development 2.00 HP Linux Development 1.66 HP Linux Development 1.62 HP Linux Development 1.58-3 HP Linux Development 1.58-3 HP Linux Development 1.58-2 HP Linux Development 5.80 HP Linux Development 5.78 HP Linux Development 5.76 HP Linux Development 5.18 HP Linux Development 3.78 HP Linux Development 3.76 HP Linux Development 3.72 HP Linux Development 3.66-2 HP Linux Development 3.66-2 HP Linux Development 3.66-2 - Running SMARTCTL (smartmontools) on HP Proliant G6/G7 (Px1x) Smart Array controllers that have firmware version 5.70 to 6.62 installed with SATA drives attached may result in system not responding or reboot. When reboot occurred, a reboot 1719 POST error message with lockup 0x15 displayed. - Running SMARTCTL (smartmontools) on HP Proliant G6/G7 (Px1x) Smart Array controllers that have firmware version 5.70 to 6.62 installed with SATA drives attached may result in system not responding or reboot. When reboot occurred, a reboot 1719 POST error message with lockup 0x15 displayed. - *Problems Fixed:**
* On systems configured with HP Smart Array P711m controllers connected to logical volumes on HP P2000 G3 SAS storage arrays, the Smart Array device driver 'hpsa' would cease to function during installation of VMware vSphere 5.5 Update 2.
* After the Smart Array device driver 'hpsa' was upgraded to version 3.4.6-165 on Red Hat Enterprise Linux 6 Update 4 or Update 5 on a server configured with logical volumes on HP P2000 G3 Storage Systems or HP MSA 2040 SAS Storage Arrays, the system would cease to function and an HP Smart Array P712m controller lockup would be reported after reboot. (POST Error: 1719 - A controller failure event occurred prior to this power-up. (Previous lock up code = 0x13)) - *Enhancements/New Features:**
* Performance enhancement when a drive starts to degrade due to excessive recovered media errors. - *Problems Fixed in version 6.60:**
This firmware release resolved the following issues:
* After a mode toggle at EFI ORCA was performed, the controller name would not be displayed when running the command: "reconnect -r".
* Controller displayed a POST error message 1805 "Cache Module Super-Cap is not installed" when the controller was configured to work without super-capacitors.
* Corrected thermal behavior with HDDs.
* Controllers configured with one or more SATA spare drives and firmware version 6.40 (or earlier) may halt with "Lockup Code = 0xAB" after 64, 128, or 256 days.
* HP Smart Array P812 controller onboard expander firmware was updated to version 3.12 to enforce 3Gbps SATA connection speeds which is the maximum supported SATA data rate on HP Smart Array P212, P410, P410i, P411, P711m, P712m, and P812 controllers. - *Enhancements/New Features**:
* Enhanced the controller SAS discovery logic to tolerate devices that may be resetting.
* Added a new POST message 1813 to indicate bad or failed battery charge circuit. - *Enhancements/New Features**:
* Enhanced the firmware to enable discovery of HDD. - ***Problems Fixed:****
* When SATA drives are configured as spares for a period of 60 days or more, the storage controller would lockup, reporting as 0xAB error.
* Corrected Thermal behavior with HDDs. - *Problems Fixed:**
* Corrected Thermal behavior with HDDs - *Problems Fixed in version 6.40(B):**
* Fixed an installation issue where version 6.40 of the Online Smart Array firmware smart components for the Smart Array P410i Controller would in some cases update the SAS expander in the HP D2200sb Storage Blade with incorrect firmware causing the Smart Array P410i Controller to be unable to communicate with the hard drives installed in the HP D2200sb Storage Blade. Reference Customer Advisory c03964262 for additional important information about this issue.
**Problems Fixed in version 6.40:**
* False POST 1705 messages were being posted on the HP BL465c G7 or HP BL685c G7 Blade systems that used HP Smart Array P410i controller firmware version 5.76 or greater. The POST was indicateding a bad Super-Cap, which in turn disabled write caching.
* On rare occasions the controller would become unresponsive during POST.
* On intermittent occasions, SATA spare drives in a JBOD were being marked as hot removed and then rediscovered.
* Customers could not invoke ORCA via command line interface, by pressing the escape key-strokes "Esc+6" or "F6" or "Esc+8" or "F8" via the BIOS Serial Console.
**Note: Version 6.40 is no longer available for download from HP Support Center, but the following fixes are also provided in version 6.40(B).** - *Enhancements/New Features**:
* Allow Windows Server 2012 drivers to utilize command addressing above the lower 4GB memory region when requested by the storage driver. - Customers who already installed firmware version 6.40 do not need to update to 6.40 (B). - *Problems Fixed:**
* On rare occasions during power-up the controller would become unresponsive during POST. - *Problems Fixed:**
The following problems are addressed in version 6.00 of Online ROM Flash
Component for Linux - Smart Array P212, P410, P410i, P411, P711m, P712m, and
P812:
* On rare occasions during power-up of an HP DS2200sb the expander backplane would be unresponsive. When the expander backplane was unresponsive, the attached Smart Array Controller was not allowed to discover drives that were attached.
* On an HP P812 controller, executing several sequential Write operations to more than 75 hard drives would result in a controller lockup.
* Modified the FBWC module code to improve the training of the DDR2 DIMMs in order to prevent the rare occasions when 1783 POST error messages displays followed by an unresponsive controller.
* Protection has been added to prevent potential Smart Array controller hangs under rare conditions when hot-adding hard drives.
* When running in a Solaris environment, Smart Array firmware version 6.00 works around an issue where the driver would not handle asynchronous events from the Smart Array controller properly.
* An interaction issue occurred between the Smart Array Controller and HP SAS Expander card in which the Hard Drives attached to the HP SAS Expander were not being discovered occasionally upon boot up or hot plug.
* On rare occasions, the Smart Array controller would reset the same SATA drive several times when a PHY is stuck longer than four seconds.
* The Smart Array P711m and P712m would report false link errors.
* The Open Connection timeout was reduced to 900 microseconds so that SAS connections terminate gracefully and data transfer stalls are prevented.
* The Smart Array controller would not connect to hard drives within 20ms under heavy stress.
* Upon power up, a Post message will now be displayed to the user to indicate that a cache module is needed for the P711m controller.
* When running heavy I/O in RAID 5, while an HP P410 controller was connected to more than 17 SAS drives in an HP DL180 G6 server with a 25SFF backplane, a lockup issue (error code 0xAB or 0xEA) could occur.
* During heavy I/O when the HP P711m controller is connected to a HP P2000sa G3 MSA Array System via a HP 6Gb SAS Switch, a lockup issue (error code 0x15) could occur.
* After a system with (2) or more empty SAS storage boxes, Box 1, 2, 3 , attached to an HP SAS Expander card is powered up and then a drive is hot plugged into Box 2 or above, ACU and ORCA would incorrectly display the drive in Box 1. - *******Problems Fixed**:**********
* When SATA drives are configured as spares for a period of 60 days or more, the storage controller would lockup, reporting as 0xAB error. - ***Problems Fixed**:******
* Fixed an issue with the HP P812 controller in which a rare lockup (code 0xD4) could occur upon reboot.
* Fixed an issue where disk location information was reported incorrectly in the HP DL580 G5 with the HP SAS Expander card
* Fixed an issue where a RAID 6 volume could have inconsistent parity data in the last stripe in certain configurations after a volume transformation operation had occurred.
* Fixed an issue where removal of a HP P2000saG3 controller module could cause a controller lockup (code 0xAB).
* Fixed an issue where the hot-add of a 3TB drive to HP DL180G6 12 drive backplane could cause the controller to lock up (code 0x15).
* Fixed an issue where the controller would lock up (code 0xBC) due to incorrectly placing host data into a write-cache line that had a memory error.
* Fixed an issue where a controller configured for 100% read cache could cause a false "A cache error was detected. Run a diagnostic report for more information" error to be displayed in the 'Cache Status Details' column in ACU.
* Fixed an issue where after hot-adding a SATA disk to an MSA-60, MSA-70, or HP DL180-G6 12-drive backplane, the storage controller could become unresponsive. Reference Customer Advisory [c03011608](http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03011608).
* Fixed an issue where the controller could become unresponsive while handling a hot-removal event when experiencing heavy I/O.
* Fixed an issue that could be experienced during a volume transformation operation. If a logical Unrecovered Read Error occurred, it could cause the bad block(s) to be moved to the incorrect location in the transformed volume if the original volume was configured at an offset in the array.
* Fixed an issue where simultaneous handling of many Unrecoverable Read Errors on SATA disks supporting Native Command Queuing could result in a lockup (code 0x15).
* Fixed an issue where a disk of size >2TB could be incorrectly marked as failed.
* Fixed an issue that caused a lockup (code 0x13) with a SSD RAID 10 array under heavy I/O load.
* Fixed an issue where SATA disks could occasionally be marked as failed or missing during boot when no cache module is installed on the controller.
* Fixed an issue where a controller running with no cache module, attached to SATA disks, could encounter a lockup (code 0x15) when running HP Insight Diagnostics software or offline HDD firmware flash utility.
* Fixed an issue with cable pull between the controller and an enclosure IO module that would cause a lockup (code 0x13) in Open VMS / Solaris systems.
* Fixed several issues that caused the controller to become unresponsive at boot up time. Reference CA [C03161926](http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?locale=en_US&objectID=c03161926).
* Fixed the controller firmware to properly process F1 and F2 keys at startup. Reference CA [c03127437](http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?locale=en_US&objectID=c03127437).
* Fixed an issue in which 3TB drives were not managed as spares.
* Fixed an issue in which the Server Serial Number, Product ID, and Other Configurations were cleared or set to default. Reference Customer Advisory _[c03083515_](http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03083515&lang=en&cc=us&taskId=101&prodSeriesId=3884098&prodTypeId=3709945) - Customers who already installed firmware version 5.70 do not need to update to
5.70(B). - ***Problems Fixed**:******
* Fixed an issue with the HP P812 controller in which a rare lockup (code 0xD4) could occur upon reboot.
* Fixed an issue where disk location information was reported incorrectly in the HP DL580 G5 with the HP SAS Expander card
* Fixed an issue where a RAID 6 volume could have inconsistent parity data in the last stripe in certain configurations after a volume transformation operation had occurred.
* Fixed an issue where removal of a HP P2000saG3 controller module could cause a controller lockup (code 0xAB).
* Fixed an issue where the hot-add of a 3TB drive to HP DL180G6 12 drive backplane could cause the controller to lock up (code 0x15).
* Fixed an issue where the controller would lock up (code 0xBC) due to incorrectly placing host data into a write-cache line that had a memory error.
* Fixed an issue where a controller configured for 100% read cache could cause a false "A cache error was detected. Run a diagnostic report for more information" error to be displayed in the 'Cache Status Details' column in ACU.
* Fixed an issue where after hot-adding a SATA disk to an MSA-60, MSA-70, or HP DL180-G6 12-drive backplane, the storage controller could become unresponsive. Reference Customer Advisory [c03011608](http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03011608).
* Fixed an issue where the controller could become unresponsive while handling a hot-removal event when experiencing heavy I/O.
* Fixed an issue that could be experienced during a volume transformation operation. If a logical Unrecovered Read Error occurred, it could cause the bad block(s) to be moved to the incorrect location in the transformed volume if the original volume was configured at an offset in the array.
* Fixed an issue where simultaneous handling of many Unrecoverable Read Errors on SATA disks supporting Native Command Queuing could result in a lockup (code 0x15).
* Fixed an issue where a disk of size >2TB could be incorrectly marked as failed.
* Fixed an issue that caused a lockup (code 0x13) with a SSD RAID 10 array under heavy I/O load.
* Fixed an issue where SATA disks could occasionally be marked as failed or missing during boot when no cache module is installed on the controller.
* Fixed an issue where a controller running with no cache module, attached to SATA disks, could encounter a lockup (code 0x15) when running HP Insight Diagnostics software or offline HDD firmware flash utility.
* Fixed an issue with cable pull between the controller and an enclosure IO module that would cause a lockup (code 0x13) in Open VMS / Solaris systems.
* Fixed several issues that caused the controller to become unresponsive at boot up time. Reference CA [C03161926](http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?locale=en_US&objectID=c03161926).
* Fixed the controller firmware to properly process F1 and F2 keys at startup. Reference CA [c03127437](http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?locale=en_US&objectID=c03127437).
* Fixed an issue in which 3TB drives were not managed as spares.
* Fixed an issue in which the Server Serial Number, Product ID, and Other Configurations were cleared or set to default. Reference Customer Advisory _[c03083515_](http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03083515&lang=en&cc=us&taskId=101&prodSeriesId=3884098&prodTypeId=3709945) - ***Problems Fixed:****
* Resolved an issue where the server's serial number, product ID, and/or BIOS Configuration options may be cleared if the server's HP Smart Array RAID configuration was created by first using the Smart Array's Option ROM Configuration for Arrays (ORCA) utility or Smart Array Auto-Configuration and then later deleting the configured volume. This may impact all HP ProLiant G6 and G7 BladeSystem servers using the Smart Array Controllers P711m or P712m installed with firmware version 5.32. For more details, please review the customer advisory located here: