| Asset ID: |
1-71-1991284.1 |
| Update Date: | 2018-01-22 |
| Keywords: | |
Solution Type
Technical Instruction Sure
Solution
1991284.1
:
FS System: How to recover a drive using the fscli tool
| Related Items |
- Oracle FS1-2 Flash Storage System
|
| Related Categories |
- PLA-Support>Sun Systems>DISK>Flash Storage>SN-EStor: FSx
|
In this Document
Applies to:
Oracle FS1-2 Flash Storage System - Version 6.1.6 and later
Information in this document applies to any platform.
Goal
This document describes the steps to recover a drive using the fscli tool if the drive is replaced or goes offline and comes back.
Refer to <Document 2001248.1> FS System: Understanding Drive Enclosure Disk Drive States.
Solution
-
Confirm drive status using the fscli tool or Graphical User Interface (GUI).
D:\FSCLI>fscli login -u administrator -oracleFS IP address
D:\FSCLI>fscli enclosure -list -details -enclosure /ENCLOSURE-09 > DiskStatus.txt
Review the file DiskStatus.txt and check that the disk is in RECOVERED status.
Example:
DiskDrive
DriveStatus : RECOVERED
Model : H109030SESUN300G
SerialNumber : 1409C9PEMJ
FirmwareVersion : A690
DriveSlot : 21
StorageClass : perfdisk
Capacity
Gigabytes : 304.7
Bytes : 304685419480
-
Physically check drive LEDs.
If LEDs are illuminated contact the Oracle support.
If there is an option for support to connect remotely, please obtain and check the IOM dump.
Refer to <Document 1954866.1> FS System: How to Collect the System-Wide Diagnostic Dump From Drive Enclosure (DE2-24C or DE2-24P) IO Module (IOM).
Open the saved file and search for 'Drive Bay' and the drive slot number. Check the 'fault LED' and 'array LED' are 'OFF'.
Example:
**** Drive Bay 1 status ****
present : yes
SES_info_bit : not set
RAID_info_byte: 0x0
spin up time : 0+00:00:26.696
drive_type : SAS
WWN : 5000CCA0227A3A22
faults : none
fault LED : OFF
array LED : OFF
inject : NONE
pending : ONLINE
current : ONLINE
SlotA
bypass : 0x00
SlotB
bypass : 0x00
force off : no
Additionally check that status from the DE Console in the GUI if logs are not available:
Refer to <Document 1991213.1> FS System: How to SSH to Drive Enclosure RAID Console.
In the following example Drv 08 status is 07_Reinserted:
SCSI>{s0000-1F87} 03-18-2015 09:51:23. 843676. usec
Obj cmd offset 0x0000-7FB0-3735-66F8, len 0x3735-6700
Preproc buffer 0x1A97-DBC0
sim::EnQueue 0xDC5 RAID 10S 02 Clean
RAID 6 02 Clean
RAID C 02 Clean
------------------------------------------------------
totalDrives 0000-0018
Drv Owner Media BSize AccessOn PhySt LogSt
00 00 00 520. CU0CU1 64_Online 06_InUse
01 00 00 520. CU0CU1 64_Online 06_InUse
02 00 00 520. CU0CU1 64_Online 06_InUse
03 00 00 520. CU0CU1 64_Online 06_InUse
04 00 00 520. CU0CU1 64_Online 06_InUse
05 00 00 520. CU0CU1 64_Online 06_InUse
06 00 00 520. CU0CU1 64_Online 06_InUse
07 00 00 520. CU0CU1 64_Online 06_InUse
08 00 00 520. CU0CU1 64_Online 07_Reinserted
09 00 00 520. CU0CU1 64_Online 06_InUse
0A 00 00 520. CU0CU1 64_Online 06_InUse
0B 00 00 520. CU0CU1 64_Online 06_InUse
0C 00 00 520. CU0CU1 64_Online 06_InUse
0D 00 00 520. CU0CU1 64_Online 06_InUse
0E 00 00 520. CU0CU1 64_Online 06_InUse
0F 00 00 520. CU0CU1 64_Online 06_InUse
10 00 00 520. CU0CU1 64_Online 06_InUse
11 00 00 520. CU0CU1 64_Online 06_InUse
12 00 00 520. CU0CU1 64_Online 06_InUse
13 00 00 520. CU0CU1 64_Online 06_InUse
14 00 00 520. CU0CU1 64_Online 06_InUse
15 00 00 520. CU0CU1 64_Online 06_InUse
16 00 00 520. CU0CU1 64_Online 06_InUse
17 00 00 520. CU0CU1 64_Online 06_InUse
------------------------------------------------------
-
Clear drive failure history.
D:\FSCLI>fscli enclosure -clearDriveHistory -help
enclosure -clearDriveHistory
Clears the failure history that is associated with the specified drive
slot.
SYNOPSIS
enclosure -clearDriveHistory
-enclosure enclosure-id-or-fqn
-driveSlot drive-index
[{-sessionKey | -u admin-user -oracleFS oracle-fs-system}]
[{-outputformat | -o} { text | xml }]
[{-timeout timeout-in-seconds | -verify | -usage | -example | -help}
DESCRIPTION
An Oracle Customer Support representative might require that you clear
the history of a specific drive slot. Clearing the drive slot history
removes the persistent record of drive failures that have occurred in
the slot. Running the "enclosure -clearDriveHistory" command also clears
the history of the drives that were pulled and reinserted. Whenever a
drive is pulled and reinserted, the drive failure count increments. When
the drive count increments to four failures, the Oracle FS System marks
the drive slot as "faulty". Clearing the drive slot history prevents the
drive slot from being marked as "faulty" if no drive replacement was
done.
Only administrators with primary administrator, admin1, or support roles
are authorized to run this command.
OPTIONS
-driveSlot
Specifies the drive slot number for the drive. Drive slot numbers
range from 0 to the total number of drives in the Drive Enclosure
minus 1.
-enclosure
Specifies the fully qualified name (FQN) or unique identifier (ID)
of the Drive Enclosure that contains the drive with the history to
clear. The FQN includes the chassis ID, which is displayed on the
front of the Drive Enclosure.
Example:
fscli enclosure -enclosure /ENCLOSURE-10 -clearDriveHistory -driveSlot 8
The drive status will either become the spare drive or change its status to Rebuilding.
References
<NOTE:1991213.1> - FS System: How to SSH to Drive Enclosure RAID Console
<NOTE:1954866.1> - FS System: How to Collect the System-Wide Diagnostic Dump From Drive Enclosure (DE2-24C or DE2-24P) IO Module (IOM)
<NOTE:1989554.1> - FS System: How to Manually Fail a Drive from the Drive Enclosure RAID Console
Attachments
This solution has no attachment
