IBM pSeries Servers - Microcode Update for Ultrastar 146LZX 9/18/36/73/146 GB   IBM pSeries Servers Microcode Update for KS5XX15KV6 73/146/300/450/600 GB 15K RPM SAS Hard Disk Drive Microcode Level 861H   DATE: June 2, 2022 Revised June 20, 2022 Table of Contents 1.   General Information 1.1 Disk Drives Affected 1.2 Microcode Change History 2.  AIX and VIOS(PowerVM Virtual I/O Server) Operating System 2.1 Installation Time 2.2 Determine Drive Model, FRU&PN and Current Microcode Level 2.3.1 Internet AIX self extracting file (.bin) 2.3.2 Internet RPM package 2.3.3 CD-ROM 2.4 Microcode Download Procedure 3.   Linux Operating System 3.1 ReadHat (RHEL) and SLES 3.2 Ubuntu 4.   Revisions =============================================================== 1.   General Information The Microcode files provided in this package are for SAS disk drives used in IBM system P Servers with AIX or Linux operating systems 1.1 Disk Drives Affected  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 600GB ST600MP0016 00E8653 00LY478 ST600MP.A1800012.38363148 42881 00E8665 00LY521 00E9914 00LY507 450GB ST600MP0016 44V4432 00LY494 ST300MP.A1800012.38363148 300GB ST300MP0016 74Y6496 00LY477 74Y6498 00LY520 00E9912 00LY506 00LY429 00LY511 10N7208 00LY493 02YC612 02YC610 146GB 00E6169 00LY476 00E6173 00LY519 00FX876 00LY505 10N7232 00LY492 73GB 00E6168 00LY475 10N7230 00LY491   1.2 Microcode Change History Release date Code level Impact/ Severity Change Description June 2022 861H Function/ ATT The change in this microcode only affects disk drive supplier?s MFG process, no effect on drive?s function in customer systems Dec 2021 861G Function/ ATT -This level of microcode is required to support new NAND component; the change is in controller FW. -Other fixes and enhancements April 2021 861E Function/ ATT - Drive become unresponsive during write same command processing - Drive become unresponsive following hard reset during write command -  Single SAS port become unresponsive May 2020 861B Serviceability/ ATT FW change is made for IBM MFG to support new PN. No functional change in this code Sept 2019 861A Function/ ATT -Fixed a fw bug that causes drive to fail when there are too many back-to-back ?skip? commands, this only affects raid member drives only (pdisk ), not JBOD (hdisk) -Other fixes and enhancements Nov 2018 8619 Performance/ ATT Performance Improvement (Improved random read with q-depth=1) June 2018 8618 New/ New Initial Release   =============================================================== 2.  AIX and VIOS(PowerVM Virtual I/O Server) Operating System 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. 2.1 Installation Time 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)   hdisk2           U5887.001.G232002-P1-D2  SAS Disk Drive (300000 MB)           Manufacturer................IBM         Machine Type and Model......ST300MP0016         FRU Number..................74Y6496         ROS Level and ID............38363148         Serial Number...............SAE00K23         EC Level....................P02080         Part Number.................00LY477         Device Specific.(Z0)........000006329F003002         Device Specific.(Z1)........1031861H         Device Specific.(Z2)........0021         Device Specific.(Z3)........16183         Device Specific.(Z4)........         Device Specific.(Z5)........22         Device Specific.(Z6)........P02080         Hardware Location Code......U5887.001.G232002-P1-D2     If the data returned in the ?Part Number?, ?FRU Number?, and ?Machine Type and Model?  fields match the one listed in section 1.1 AND the "ROS Level and ID...." field of that data is below "38363148", this microcode applies. Note: Drive microcode level in ?ROS Level and ID ?? field is displayed in Hex value of ASCII characters in VPD data. Each alpha-numeric ASCII character converts to a 2-digit hex number. For example in VPD displayed above, 38 Hex= ASCII character "8";  36 Hex= ASCII character "6"; 31 Hex=ASCII character "1"; 48 Hex=ASCII character "H",  microcode level is "861H ". Also note that the microcode level "861H " is displayed in ?Z1? field. =============================================================== 2.3 Transferring and Unpacking the Microcode Update Package 2.3.1 Internet AIX self extracting file (.bin) 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 KS5XX15KV6.bin c) Unpack the file by executing the instructions below.   Enter the commands:   cd /tmp/fwupdate   chmod +x KS5XX15KV6.bin   ./ KS5XX15KV6.bin [Don't overlook the periods (.) in the above command.] The directory KS5XX15KV6 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/ KS5XX15KV6/ST9*  /etc/microcode e- If you are using stand alone AIX diag (bootable USB flash or CD/DVD) to update drive?s microcode, transfer microcode files to a USB drive and place it in ?/etc/microcode? directory.     Please refer to this page for USB flash drive usage       https://www.ibm.com/support/pages/using-and-taking-advantage-usb-devices-and-aix 2.3.2 Internet RPM package 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 RPM format file.     Enter:      mkdir /tmp/microcode b) Transfer the RPM format file to the /tmp/microcode directory.     You'll see the filename is KS5XX15KV6?861H-AIX.rpm c) Unpack the file by executing the instructions below:     Enter the commands:         rpm -ihv --ignoreos  --force KS5XX15KV6?861H-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/   2.3.3 CD-ROM Copy microcode updates from the CD-ROM to standard locations on your local disk: 1. RPM packaged microcode files will be copied to "/tmp/microcode/RPM" 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. ======================================================== 2.4 Microcode Download Procedure 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 isused(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 theDiskette(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.                               ====================================================== 3.   Linux Operating System   3.1 ReadHat (RHEL) and SLES   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 KS5XX15KV6?861H-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     -------------------------------------------------------------------------- 3.2 Ubuntu   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.  tar -C-xzvf KS5XX15KV6?861H-LINUX.tgz 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     4.   Revisions          Section 1.2 ?Changed Description? changed for 861H