Pillar Axiom 600 Storage System
 

PLA-Support>Sun Systems>DISK>Axiom>SN-DK: Ax600
 

In this Document

Symptoms

Changes

Cause

Solution

Verify Current Disk Drive Firmware

Update Disk Drive Firmware

References

Applies to:

Symptoms

Unrecoverable read errors may occur on certain disk drive models in the Axiom 600. The affected drive models and firmware versions are listed below.

This document addresses this issue for Axiom 600s running R5.x software only. Axioms running R4.x should reference <Document 2076301.1> Pillar Axiom: 300GB and 600GB Disk Firmware Upgrade to Address Unrecoverable Read Errors for the Axiom 600 Running R4.x.

Changes

Cause

The vendor has determined that unrecoverable read errors may occur on certain disk drive models when a burst of I/O activity follows an extended idle period.  However, the Axiom system architecture is such that extended idle periods on any disk drive is extremely unlikely.  As such, the likelihood of this problem occurring in an Axiom is very low.  Customers wishing to upgrade to the latest drive firmware should ensure data is properly backed up and perform the upgrade during a maintenance window.

Solution

This issue is alleviated by installing firmware version P820. This is the vendor version, which is not viewable in the Axiom. Vendor firmware version P820 displays as either 2052-00047-03 or 2052-00049-03, depending on the drive model. To install this fix, follow these instructions.  Updating drive firmware is an offline activity.  It is estimated that each iteration of a firmware upgrade will take between 1 and 2 hours depending on the Axiom configuration.

Verify Current Disk Drive Firmware

Use the Pillar Axiom Storage Service Manager GUI or CLI to display the drive part numbers and firmware versions to see if they require this fix:

• Pillar Axiom Storage Services Manager:
1. Select the Monitor tab
2. Expand Hardware then select Bricks
3. Right click on the first Brick and select View Details
4. Review the list of drives and their associated firmware versions.
5. Repeat steps 3 and 4 for the remaining Bricks.
   
   
• Axiom CLI:
  
  C:\axiomcli login -u administrator -p pillar -axiom <shared_ip_of_Axiom>
  C:\axiomcli brick -list
  /BRICK-001
  /BRICK-002
  C:\axiomcli brick -list -brick /BRICK-001 -details
  Brick                     : /BRICK-001
      Name                      : BRICK-001
      Id                        : 200C000B083A5436
      Fqn                       : /BRICK-001
      BrickWwn                  : 200C000B083A5436
      Type                      : FIBRE_CHANNEL_RAID
      Model                     : 1000-00009-00
      HardwareComponentStatus   : NORMAL
      TemperatureStatus         : NORMAL
      SerialNumber              : SGAMS00046DLN00D
      ManagementState           : AVAILABLE
      OverallBrickStatus        : NORMAL
      Ssn                       : A001365BFM
  /BRICK-001/0
      Id                    : 200C000B083A5436
      StorageClass          : fchd
      StorageDomain
          Id                    : 4130303133363542A214000000000000
          Fqn                   : /default
      MediaType                 : FC_ROTATING_MEDIA
      OverallBrickNodeStatus    : NORMAL
      DiskDriveNumber : 0
          Status                : NORMAL
          Model                 : 1450-00298-30 <============ Part Number
          ManufacturingModel    : 3500-00036-33
          SerialNumber          : J80HRGVL
          Spare                 : false
          Capacity              : 300
          FirmwareVersion       : 2052-00047-01 <============ Firmware Version
      DiskDriveNumber           : 1
          Status                : NORMAL
          Model                 : 1450-00298-30 <============ Part Number
          ManufacturingModel    : 3500-00036-33
          SerialNumber          : HZ2MX5ML
          Spare                 : false
          Capacity              : 300
          FirmwareVersion       : 2052-00047-01 <============ Firmware Version
  ...
   
  In the above example the part number information shows that BRICK-001, Drives 0 & 1 are susceptible to this problem.  Several lines below that is the Axiom firmware version and confirms the newer firmware version is needed to avoid this issue on these drives.

If a customer sends in a log bundle, Oracle Support can determine if there are affected drives by greping for the part numbers in the SystemConfiguration .txt file. 

Update Disk Drive Firmware

So as not to create a new Service Request, be sure to disable Call Home before starting any firmware upgrades.  See <Document 1535352.1> Pillar Axiom: How to Disable Call Home to Prevent Automatic Service Request ASR Generation for details.

If one or more of the affected drives are identified, the Axiom must first be upgraded to R5.4.18 or higher.  Upgrade the Axiom Storage Service Manager software using the directions in <Document 1441772.1> Pillar Axiom: Software/Firmware Upgrade Procedures R5.x to R5.x. For those Axioms already running R5.4.18 and above, you will only need to download the drive firmware part of that patch (p22167172_5418_Generic_3of3.zip). 

With the Axiom running at least R5.4.18 and the appropriate drive firmware package downloaded and unzipped, stage then upgrade the drive firmware.

• Upgrade using the Axiom Storage Service Manager GUI:
1. Log into the GUI as administrator and select the Support tab at the top of the Navigation Tree on the left.
2. Under Tools in the navigation tree, select Drive Firmware.
3. To stage the drive firmware, you have two choices.  From the Menu Bar select Actions and then Upload Drive Firmware Package or from the main window right click, and then select Upload Drive Firmware Package.
4. In the pop-up window, provide the path to the location of the drive firmware rpm package.  Using the default location after it is unzipped (it will be in the sub-directory: p22167172_5418_Generic3of3\drivefw), load the drive firmware package:
   
   
   
   and select OK.
   
   
5. With the drive firmware staged, start the process by either selecting Actions in the Menu Bar or right click in the main window:
   
   
   
   
   
6. In the Update Drive Firmware pop-up, select Disrupt data access:
   
   
   
   
   
7. The Pilot will reboot and connection to the GUI will be lost as the Axiom performs a cold start.  After 5-7 minutes, the reboot will be complete and GUI access will be restored.
8. When the cold start is complete and the system returns to a Normal status, you may see a SystemStartProcess task and a SystemStartInterruptHandlingChainOperation tasks stuck at 66% and 1% respectively.  A manual Pilot failover will be required to clear these tasks.
   
   NOTE: Do NOT attempt a manual Pilot failover while the drive firmware update is running.  Doing so will interrupt the upgrade process and may result in LUNs going offline requiring additional recovery steps.
   
   
   
9. If applicable, repeat the procedure for the second drive model.
   
   
• Upgrade using the axiomcli CLI:
  
  
1. Login and stage the drive firmware:
   
   C:\>axiomcli login -u administrator -p pillar -axiom <shared_ip_of_axiom>
   Login Successful
   
   C:\>axiomcli software_update -add -hdd <path_to_firmware_file>
   Command Succeeded
   Checking existing drive firmware, please wait.
   
   Brick
       Id : 200C000B083A5436
       Fqn : /BRICK-001/0
       Drive
           Slot : 0
           FirmwareVersion
               Current     : 2052-00047-01
               Recommended : 2052-00047-03
       Drive
           Slot : 1
           FirmwareVersion
               Current     : 2052-00047-01
               Recommended : 2052-00047-03
   
   
    
2. Install staged drive firmware:
   
   C:\>axiomcli software_update -install -hdd
   Warning: Contact the Support Center before proceeding! Proceeding without their assistance could risk data loss. Continue(y/N)?
   y
   Command Succeeded
   C:\>
    
3. The Pilot will reboot and connection to the CLI will be lost. After 5-7 minutes, the reboot will be complete and CLI access will be restored.
4. Drive firmware upgrades will begin after Pilot reboot and can be monitored using "axiomcli task -list" command.
5. Once drive firmware upgrade has completed, the upgrade can be verified using the same "axiomcli brick -list -brick <BRICK FQN> -details" command as above.
6. When the drive firmware upgrades are complete, the Pilots will reboot again.
7. If applicable, repeat the procedure for the second drive model.

When all drive firmware upgrades have been completed, follow the instructions at the end of the <Document 1535352.1> Pillar Axiom: How to Disable Call Home to Prevent Automatic Service Request ASR Generation to re-enable call-home.

References

This solution has no attachment