IBM pSeries Servers - Microcode Update for Ultrastar 146LZX 9/18/36/73/146 GB   IBM Power Systems (AIX/Linux) Microcode Update for Ultrastar DCHC320 8 TB 4K 7200RPM SAS Hard Disk Drive Microcode Level P6V3   DATE: May 17, 2019 Table of Contents 1.      General Information 1.1     Disk Drives Affected 1.2  Microcode Change History 2.      Microcode Download Procedure-AIX and VIOS(PowerVM Virtual I/O Server) OS 2.1 Installation Time 2.2 Determine Drive Model, FRU&PN and Current Microcode Level 2.3 Transferring and Unpacking the Microcode Update Package 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 =============================================================== 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 8TB HUS728T8TAL420 00LY301 00LU835 HUS728T.A180001C.50365633 03550   1.2  Microcode Change History Release date Code level Severity/ Impact Change Description May 2019 P6V3 New/ New Initial Release     =============================================================== 2.     Microcode Download Procedure-AIX and VIOS(PowerVM Virtual I/O Server) OS 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) Hdisk0          UESLL.001.G62300L-P1-D12  SAS 4K Nearline Drive (8000000 MB)           Manufacturer................IBM         Machine Type and Model......HUS728T8TAL4200         FRU Number..................00LY301         ROS Level and ID............50365633         Serial Number...............VAG6RNKL         EC Level....................P02098         Part Number.................01LU835         Device Specific.(Z0)........000006329F003002         Device Specific.(Z1)........V8IPP6V3         Device Specific.(Z2)........00SS         Device Specific.(Z3)........18216         Device Specific.(Z4)........         Device Specific.(Z5)........22         Device Specific.(Z6)........P02098         Hardware Location Code......UESLL.001.G62300L-P1-D12         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, 50 Hex= ASCII character "P"; 36 Hex= ASCII character "6"; 56 Hex=ASCII character "V"; 33 Hex=ASCII character "3",  microcode level is "P6V3". Also note that the microcode level "P6V3" 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 DCHC320.bin c) Unpack the file by executing the instructions below.   Enter the commands:   cd /tmp/fwupdate   chmod +x DCHC320.bin   ./ DCHC320.bin [Don't overlook the periods (.) in the above command.] The directory SSD530 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/ DCHC320/*  /etc/microcode 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 DCHC320-P6V3-AIX.rpm c) Unpack the file by executing the instructions below:     Enter the commands:         rpm -ihv --ignoreos  --force DCHC320-P6V3-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 is used(using Diagnostics CD); Approximately 5 minutes/drive if concurrent diagnostics is used. 2.4.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                       usb mass storage    (ISO 9660 file system format)                       configure device    - Select location of microcode file and press enter 7- Display shows a list of microcodes available for the selected drive, highlight option "M  xx...", 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.2 Standalone (Service Mode) Download Use similar steps as above when booting from a Diagnostics CD ====================================================== 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 DCHC320-P6V3-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 DCHC320-P6V3-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