![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||||||
Solution Type Problem Resolution Sure Solution 2190111.1 : FS System: Newly added drives in a Drive Enclosure display a status of UNSUPPORTED
In this Document
Created from <SR 3-13410998151> Applies to:Oracle FS1-2 Flash Storage System - Version All Versions to All Versions [Release All Releases]Information in this document applies to any platform. SymptomsNewly installed drives report as UNSUPPORTED in Oracle FS System Manager GUI and FSCLI. Overall system status changes to WARNING after the drives are added. Verify using Oracle FS System Manager GUI :
Verify using Oracle FS System Manager CLI (FSCLI) : #fscli enclosure -list -details -enclosure /<Enclosure ID or fqn> Eg: #fscli enclosure -list -details -enclosure /ENCLOSURE-01 /ENCLOSURE-01 Id : 50800200014753E2 Chassis Number : 0 DiskDrive DriveStatus : UNSUPPORTED <---------------
From the FS1-2 log bundle : EnclosureInformation_DiskDrive[7]_DriveStatus = UNSUPPORTED <-------------------
EnclosureInformation_DiskDrive[7]_Model = HSFAC2DA4SUN400G EnclosureInformation_DiskDrive[7]_SerialNumber = 160XXXXXXX EnclosureInformation_DiskDrive[7]_FirmwareVersion = D29E EnclosureInformation_DiskDrive[7]_DriveSlot = 7 EnclosureInformation_DiskDrive[7]_Capacity = 406337758840 EnclosureInformation_DiskDrive[7]_EnclosureIdentity_Id = 508002000XXXXXXXX EnclosureInformation_DiskDrive[7]_EnclosureIdentity_Fqn = /ENCLOSURE-01 EnclosureInformation_DiskDrive[7]_StorageClass = UNKNOWN EnclosureInformation_DiskDrive[7]_EncryptionSupported = true EnclosureInformation_DiskDrive[7]_EncryptionEnabled = true
ChangesThe addition of a new drive enclosure or insertion of additional drives into an existing drive enclosure (in the case of SSD). CauseThe firmware package for the drive model is not installed on the system. NOTE: This document do not apply if the firmware for a drive model is installed and the drive status persists as UNSUPPORTED.
Example : Addition of SSD DRIVE (model HSFAC2DA4SUN400G -> Sunset Cover Plus 400GB FIPS SSD) and it's status is shown as UNSUPPORTED.
Execute fscli software_update -list and verify the firmware for a particular DRIVE model is staged/installed under sections StagedDriveFirmware & InstalledDriveFirmware. #fscli login -u <username> <fs-system IP> #fscli software_update -list Staged Software: /STAGED StagedGlobalStorageManagerSoftware
InstalledDriveFirmware DriveFirmware InstalledGlobalStorageManagerSoftware
As one can see from the output above, the firmware package for "Sunset Cove Plus 400GB FIPS SSD" is NOT installed. The firmware package is just staged. If the firmware package for a particular drive model is not installed, the DRIVE will not be accepted into the system configuration and as a result will show as UNSUPPORTED. Other way around is to ssh to FS1-2 and check whether the firmware package is installed.
Example : Below output indicate firmware for model "HSFAC2DA4SUN400G (FIPS)" is NOT installed but just staged to the system. [root@pilot1 ~]# ls -l /rpms/AxiomONE-SW-*/*hgst400* -rw-r--r-- 1 root root 1006775 Jul 27 00:33 /rpms/AxiomONE-SW-installed/oraclefs-hdd-hgst400gb-nfp-060200-017300.x86_64.rpm -rw-r--r-- 1 root root 1006947 Jul 27 00:33 /rpms/AxiomONE-SW-staged/oraclefs-hdd-hgst400gb-fip-060204-029400.x86_64.rpm <--------------
Solution1.Remove all the newly installed drives. 2.Install the required drive firmware using the Flash Storage Service Manager client software to update Drive Enclosure drives:
3.Insert drives one by one and accept. NOTE: All Drive Firmware update operations are disruptive, and require a maintenance window of approximately 1 hour. Installing all available Drive Firmware upgrades at the same time adds only a few minutes to the update process and avoids the need to perform additional disruptive Drive Firmware updates should new drive models be added to the system.
References<NOTE:1968129.1> - FS System: FS1-2 Upgrade R6.x to R6.x Procedures<NOTE:1967797.1> - FS System: How to Download Software and Firmware Updates for the FS1-2 Attachments This solution has no attachment |
||||||||||||||||||||
|