Microcode Update for SAV-15K.3
146/300 GB
SAS Hard Disk Drive
Microcode Level 7417
July 26, 2017
Table of Contents
2.
AIX and VIOS(PowerVM Virtual I/O Server) Operating System
2.2 Determine Drive Model,
FRU&PN and Current Microcode Level
2.3.1 Internet AIX self
extracting file (.bin)
2.4 Microcode Download
Procedure
3.1 Linux 2.6 kernel(such as SuSE SLES 9 or RHEL
4)
===============================================================
The Microcode files provided in this package are for SAS disk
drives used in
with AIX or Linux operating systems
Below
is the list of microcode files in this package:
NOTE: To insure the integrity of microcode files, please make sure the checksum value is correct after extraction
Size |
Disk Drive
Model |
FRU# |
P/N (VPD) |
Microcode File
Name |
Checksum |
73GB |
ST9146853SS |
44V4426 |
74Y9206 |
ST91468.A1700D32.37343137 |
32719 |
146GB |
ST9146853SS |
44V6845 |
74Y6485 |
||
46K4806 |
74Y6491 |
||||
00E6169 |
74Y6485 |
||||
00E6173 |
74Y6491 |
||||
00FX876 |
00FX871 |
||||
300GB |
ST9300653SS |
74Y6496 |
74Y6486 |
ST93006.A1700D32.37343137 |
|
74Y6497 |
74Y6492 |
||||
00E9912 |
00E9927 |
Release date |
Code level |
Impact/Severity |
Change Description |
July 2017 |
7417 |
Function/ ATT |
Disable BMS (Background Media Scan)
causing premature PFA trip |
Nov. 2016 |
7416 |
|
FW change
to disable/ignore Serial Port data when pins are shorted (as result of corrosion) |
April 2014 |
7414 |
|
- Fixed SMART seek counter leading to
premature SMART trip - Fixed BGMS
(Background Media Scan) returning incorrect data in log sense - Other fixes and enhancements |
Nov 2013 |
7411 |
|
Added new PN,
fixed unexpected SMART trip, fixed excessive read look ahead for back to back verify commands |
July 2013 |
740F |
|
Added a function to trip PFA (SMART) for
excessive recovered seek errors. Network roll to pick up other fixes and
enhancements |
May 2012 |
740D |
|
New RoHS FRU added – Modified idle Dithering - Network Roll |
Oct 2011 |
740A |
|
Initial Release |
===============================================================
Note:
For VIOS systems, microcode of shared physical I/O resources can only be
updated from VIOS partition.
To
update disk drive microcode, from VIOS partition, enter the following
command:
oem_setup_env
Then follow the instruction in section 2.3 to transfer/extract the microcode file, and section 2.4.1 to update the disk drive code.
Approximately
20 minutes if using Diagnostics CD; Approximately 5 minutes/drive using AIX
concurrent diagnostics.
2.2 Determine Drive Model, FRU&PN and
Current Microcode Level
To see the drive type and current
microcode level, Execute the following command:
lscfg -vl hdisk* |pg ; For
drives NOT configured for RAID
lscfg –vl pdisk*
|pg ; For drives configured for RAID
Vital
Product Data (VPD)
hdisk12 U5886.001.P81T030-P1-D10 SAS Disk Drive (73400 MB)
Manufacturer................IBM
Machine Type and Model......ST9300653SS
FRU Number..................74Y6496
ROS Level and ID............37343137
Serial Number...............6XN01AMY
EC Level....................N23780
Part Number.................74Y6486
Device Specific.(Z0)........000006329F001002
Device Specific.(Z1)........04257417
Device Specific.(Z2)........0021
Device Specific.(Z3)........11044
Device Specific.(Z4)........
Device Specific.(Z5)........22
Device Specific.(Z6)........N23780
If the data returned in the “Part Number”, “FRU Number”, and “Machine Type and Model” fields
match the one listed in section 1.1
Note:
Drive microcode level in “
===============================================================
2.3 Transferring and
Unpacking the Microcode Update Package
a) Make a directory on an AIX
system to receive the AIX format file.
Enter: mkdir
/tmp/fwupdate
b) Transfer the AIX format file to /tmp/fwupdate directory (using "Save as ...").
You'll see the filename is SAV15K3.bin
c) Unpack the file by executing the instructions below.
Enter the commands:
cd /tmp/fwupdate
chmod +x SAV15K3.bin
./SAV15K3.bin
[Don't overlook the periods (.) in the above command.]
The directory SAV15K3 with microcode files
listed in section 1.1 will be added to /tmp/fwupdate.
d-Enter the following command to copy the
microcode files to " /etc/microcode "
directory :
cp /tmp/fwupdate/ SAV15K3/ST9*
/etc/microcode
e- If
transferring files to a different system using floppy diskettes, use the
following procedure to copy files to diskette
Note: Don't overlook the complete path of microcode files, AIX Diag microcode download
will not
work if files are not copied with complete path onto the diskette.
Enter
the following command to copy microcode file(s) onto a floppy diskette
ls /etc/microcode/ microcodefilename | backup -ivf /dev/rfd0
where microcodefilename is microcode file that
is needed, for example:
ls /etc/microcode/ ST* | backup -ivf /dev/rfd0
Note: The
instructions that follow are specific AIX commands. AIX commands are CASE
(lower and upper) SENSITIVE,
and must be entered exactly as shown, including
filenames.
a) Make
a directory on an AIX system to receive the
Enter: mkdir
/tmp/microcode
b)
Transfer the
You'll see the filename is SAV15K3–7417-AIX.rpm
c) Unpack
the file by executing the instructions below:
Enter the commands:
rpm -ihv
--ignoreos
--force SAV15K3–7417-AIX.rpm ;(please note, there are two dashes)
The
file size and checksum will be verified.
The
microcode files will be added to /etc/microcode/
Copy
microcode updates from the CD-ROM to standard locations on your local disk:
1.
2. Microcode files will be copied to /usr/lib/microcode
Notes:
- "/etc/microcode" is a symbolic link to "/usr/lib/microcode".
- If permission does not allow the copy to the above stated directory
or file then the user will be prompted for a new location.
========================================================
Warning: Do not power off the system or the drive during microcode download as
this may permanently damage the disk drive
NOTE: Please save current and older versions of the microcode update files in
case you need to restore your system.
Caution: The microcode download process is nondestructive to the hard disks;
however, as a precaution, ensure that a backup operation has been performed on
the affected systems PRIOR to the microcode installation.
Can microcode be installed Concurrently? YES
Is system reboot needed to activate the
microcode: Yes if stand alone diagnostics CD is used, NO if concurrent
diagnostics is used.
Installation Time: Approximately 20 minutes/drive if stand alone
diagnostics is used(using Diagnostics CD);
Approximately 5 minutes/drive if concurrent diagnostics is used.
2.4.1.2.1 Concurrent
Download
1.
Type diag at the prompt.
2. Select the "Task Selection" from diagnostics menu.
3. Select "Microcode Download" from "Task Selection" menu.
4. Select resource that microcode will be applied to(hdisk? For physical disk, pdisk for RAID configured disks) and press ENTER, then
press "F7" to commit..
5- A small screen displays the message " *** NOTICE***
The microcode installation occurs while the attached drives are
available for use..... "
Press enter to continue
6. Select the source for microcode, use arrow key to go up/down, Enter to continue.
/etc/microcode
diskette
- Use /etc/microcode
if "restore" command is used to copy files from diskette onto the
disk
- Use diskette if using diskette as the source for download
NOTE: A prompt will ask you to insert the
microcode diskette in diskette drive(if Diskette is
selected above). Insert the diskette and press ENTER
7- Display shows a list of microcodes
available for the selected drive, highlight option "M
ST9xx...", the latest microcode for the drive and press ENTER. A
message may warn you that current level of microcode is not available on the
media, press ENTER to continue.
8. You will receive a msg. "Current
Microcode is...." and "Download has completed successfully"
(this may take a few minutes)
9. Return to the Tasks Selection menu and repeat this procedure for each hard
disk that requires this microcode.
10. Exit diagnostic(and reboot if needed).
2.4.1.2.2 Standalone (Service Mode) Download
This procedure is
used for all drives including rootvg or paging space
drives
1. Properly shutdown the system.
2. Boot up the system in standalone diagnostics mode with the CDROM diagnostics(Use diagnostics level 4.21 or above; It is
recommended to use the same level
of Diagnostic CD as the AIX ).
3. Select the "Task Selection" from diagnostics menu.
4. Select "Microcode Download" from "Task Selection" menu.
5. Select resource that microcode will be applied to(hdisk?) and PRESS ENTER.
6. Press "F7" to commit.
(The current microcode
level of the resource you selected earlier will be displayed at the top of the
screen)
7. Make the following selections on the next screen:
Select Input Device
--------------------------------------- [ diskette]
Microcode level to download
-----------------------------[ latest]
Download latest level even if
-----------------------------[ yes]
current is missing
NOTE: A prompt will ask you to insert the
microcode diskette into the floppy drive. Insert the diskette which
accompanies these instructions. If this level is already installed in the drive
you've selected a message will let you know. A message also may come up to let
you know that the Diskette(or Disk) does not have the
previous level microcode file. This is true and is not required to complete the
download.
PRESS "F7" to commit
8. You will receive a msg. "Current Microcode
is...." and "Download has completed successfully"
(this may take a
few minutes)
9. Return to the Tasks Selection menu and repeat this procedure for each hard
disk that requires this microcode.
10. Exit diagnostic and reboot system in normal mode.
======================================================
Microcode can be updated using the iprconfig utility. The iprconfig
utility
allows for multiple levels of adapter and device
microcode to exist on the
system at the same time. After the device to
update microcode is
selected, all available microcode levels are
presented to choose to download.
1. If using SLES
9 base, install the package by typing:
rpm -ivh --ignoreos SAV15K3–7417-LINUX.rpm
2. Update the microcode by typing:
iprconfig
Press Enter.
3. Select Download microcode and press
Enter.
4. Select the device you wish to update by
typing a 1 then pressing Enter. Multiple devices may be selected.
5. Select the microcode image to be
downloaded to the device by typing a 1 then pressing Enter.
6. Press Enter again to confirm the
download (display shows “Microcode Download in Progress” with elapsed time)
7. If multiple devices were selected, repeat
from Step 5 for the next device.
To check the microcode level:
1. Start iprconfig
utility,
2. Select "Display hardware
status" option.
3. Select disk to query by typing a 1 next
to it and pressing "Enter"
4. Look at the "Firmware
Version" field
--------------------------------------------------------------------------
Microcode can be updated using the iprconfig utility. The iprconfig
utility
allows for multiple levels of adapter and device
microcode to exist on the
system at the same time. After the device to
update microcode is
selected, all available microcode levels are
presented to choose to download.
NOTE: if iprconfig command is not found,
install iprutils:
sudo apt-get install iprutils
1. sudo tar -C / -xzvf SAV15K3–7417-LINUX.tgz
sudo iprconfig
Press Enter.
3. Select Download microcode and press
Enter.
4. Select the device you wish to update by
typing a 1 then pressing Enter. Multiple devices may be selected.
5. Select the microcode image to be
downloaded to the device by typing a 1 then pressing Enter.
6. Press Enter again to confirm the
download (display shows “Microcode Download in Progress” with elapsed time)
7. If multiple devices were selected,
repeat from Step 5 for the next device.
To check the microcode level:
1. Start iprconfig
utility,
2. Select "Display hardware
status" option.
3. Select disk to query by typing a 1 next
to it and pressing "Enter"
4. Look at the "Firmware
Version" field