Unsolved

This post is more than 5 years old

2 Intern

 • 

129 Posts

6251

February 3rd, 2017 10:00

should perccli report raid10 inconsistent ?

hi everyone
I'm seeing this below and I wonder why?
...
/c0/v1 :
======

---------------------------------------------------------------
DG/VD TYPE   State Access Consist Cache Cac sCC      Size Name
---------------------------------------------------------------
3/1   RAID10 Optl  RW     No      RWBC  R   OFF 18.188 TB
---------------------------------------------------------------

Cac=CacheCade|Rec=Recovery|OfLn=OffLine|Pdgd=Partially Degraded|dgrd=Degraded
Optl=Optimal|RO=Read Only|RW=Read Write|B=Blocked|Consist=Consistent|
R=Read Ahead Always|NR=No Read Ahead|WB=WriteBack|
AWB=Always WriteBack|WT=WriteThrough|C=Cached IO|D=Direct IO|sCC=Scheduled
Check Consistency


PDs for VD 1 :
============

-----------------------------------------------------------------------
EID:Slt DID State DG     Size Intf Med SED PI SeSz Model Sp
-----------------------------------------------------------------------
50:0     76 Onln   3 1.818 TB SAS  HDD N   N  512B ST32000444SS U
50:1     75 Onln   3 1.818 TB SAS  HDD N   N  512B ST32000444SS U
50:2     57 Onln   3 1.818 TB SAS  HDD N   N  512B ST32000444SS U
50:3    181 Onln   3 1.818 TB SAS  HDD N   N  512B ST32000444SS U
50:4     33 Onln   3 1.818 TB SAS  HDD N   N  512B ST32000444SS U
50:5    179 Onln   3 1.818 TB SAS  HDD N   N  512B ST32000444SS U
50:6     37 Onln   3 1.818 TB SAS  HDD N   N  512B ST32000444SS U
50:7     45 Onln   3 1.818 TB SAS  HDD N   N  512B ST32000444SS U
50:8     36 Onln   3 1.818 TB SAS  HDD N   N  512B ST32000444SS U
50:9     28 Onln   3 1.818 TB SAS  HDD N   N  512B ST32000444SS U
50:10    46 Onln   3 1.818 TB SAS  HDD N   N  512B ST32000444SS U
50:11    31 Onln   3 1.818 TB SAS  HDD N   N  512B ST32000444SS U
50:12    26 Onln   3 1.818 TB SAS  HDD N   N  512B ST32000444SS U
50:13    43 Onln   3 1.818 TB SAS  HDD N   N  512B ST32000444SS U
50:14    27 Onln   3 1.818 TB SAS  HDD N   N  512B ST32000444SS U
50:15    29 Onln   3 1.818 TB SAS  HDD N   N  512B ST32000444SS U
50:17    53 Onln   3 1.818 TB SAS  HDD N   N  512B ST32000444SS U
50:18    55 Onln   3 1.818 TB SAS  HDD N   N  512B ST32000444SS U
50:19    89 Onln   3 1.818 TB SAS  HDD N   N  512B ST32000444SS U
50:20    54 Onln   3 1.818 TB SAS  HDD N   N  512B ST32000444SS U
-----------------------------------------------------------------------

EID-Enclosure Device ID|Slt-Slot No.|DID-Device ID|DG-DriveGroup
DHS-Dedicated Hot Spare|UGood-Unconfigured Good|GHS-Global Hotspare
UBad-Unconfigured Bad|Onln-Online|Offln-Offline|Intf-Interface
Med-Media Type|SED-Self Encryptive Drive|PI-Protection Info
SeSz-Sector Size|Sp-Spun|U-Up|D-Down|T-Transition|F-Foreign
UGUnsp-Unsupported|UGShld-UnConfigured shielded|HSPShld-Hotspare shielded
CFShld-Configured shielded


VD1 Properties :
==============
Strip Size = 64 KB
Number of Blocks = 39059456000
Span Depth = 2
Number of Drives Per Span = 10
Write Cache(initial setting) = WriteBack
Disk Cache Policy = Enabled
Encryption = None
Data Protection = None
Active Operations = Background Initialization (0%)
Exposed to OS = Yes
Creation Date = 03-02-2017
Creation Time = 04:14:41 PM
Emulation type = None

#end
Would you know if this is normal?
I also cannot start consistency check:

$ perccli /c0/v1 start cc force
Controller = 0
Status = Failure
Description = None

Detailed Status :
===============

------------------------------------------------
VD Operation Status ErrCd ErrMsg
------------------------------------------------
 1 CC        Failed  1001 Start CC not possible
------------------------------------------------

to me it's weird, but then, it's my fist raid10 on Dell hardware.
many thanks,
L.

Moderator

 • 

9.6K Posts

 • 

42.5K Points

February 3rd, 2017 12:00

Hi,

It looks like the array is still doing the background initialization on the array, this may be why it will not let you do a consistency check.  

2 Intern

 • 

129 Posts

February 3rd, 2017 12:00

hi Josh,

>
well, I'm not so sure...

$ perccli /c0/v1 show init
Controller = 0
Status = Success
Description = None


VD Operation Status :
===================

-----------------------------------------------------------
VD Operation Progress% Status          Estimated Time Left
-----------------------------------------------------------
 1 INIT      -         Not in progress -
-----------------------------------------------------------

$ perccli /c0/v1 start init force
Controller = 0
Status = Failure
Description = None

Detailed Status :
===============

-------------------------------------------------
VD Operation Status ErrCd ErrMsg
-------------------------------------------------
 1 INIT      Failed  1001 Start FGI not possible
-------------------------------------------------

there are two more raid volumes in that chassis under a one H800. The whole lot:

DG/VD TYPE   State Access Consist Cache Cac sCC      Size Name
---------------------------------------------------------------
0/0   Cac0   Optl  RW     Yes     RWTD  -   OFF  512.0 GB
3/1   RAID10 Optl  RW     No      RWBC  R   OFF 18.188 TB
1/2   RAID0  Optl  RW     Yes     RWBC  R   OFF 38.195 TB
2/3   RAID0  Optl  RW     Yes     RWBC  R   OFF 12.731 TB
---------------------------------------------------------------

All these disks currently in raid10, plus one more, were before parts of a raid5 volume and all was a OK.
Although inconsistent the volume is in the OS and appears normal.

it's quite a puzzle to me.
thanks



Moderator

 • 

9.6K Posts

 • 

42.5K Points

February 3rd, 2017 13:00

What OS are you using? You may want to install server administrator. 

2 Intern

 • 

129 Posts

February 3rd, 2017 14:00

it's Centos 7.3

OS should not play any role here, right ?

Moderator

 • 

9.6K Posts

 • 

42.5K Points

February 3rd, 2017 14:00

2 Intern

 • 

129 Posts

February 8th, 2017 09:00

there is something troubling here happening:

this VD was created with omconfig:

$ omreport storage vdisk controller=1
List of Virtual Disks on Controller PERC H800 Adapter (Slot 6)

Controller PERC H800 Adapter (Slot 6)
ID                                : 0
Status                            : Ok
Name                              : Virtual Disk0
State                             : Background Initialization
Hot Spare Policy violated         : Not Assigned
Encrypted                         : No
Progress                          : 0% complete
Layout                            : RAID-10
Size                              : 5,588.00 GB (6000069312512 bytes)
T10 Protection Information Status : No
Associated Fluid Cache State      : Not Applicable
Device Name                       : /dev/sdb
Bus Protocol                      : SATA
Media                             : HDD
Read Policy                       : Adaptive Read Ahead
Write Policy                      : Write Back
Cache Policy                      : Not Applicable
Stripe Element Size               : 64 KB
Disk Cache Policy                 : Enabled

 perccli /c1/v0 show
Controller = 1
Status = Success
Description = None


Virtual Drives :
==============

-----------------------------------------------------------------------
DG/VD TYPE   State Access Consist Cache Cac sCC     Size Name          
-----------------------------------------------------------------------
0/0   RAID10 Optl  RW     No      RWBD  -   OFF 5.457 TB Virtual Disk0
-----------------------------------------------------------------------

would you, anybody @Dell know this error codes:

$ perccli /c1/v0 start cc

VD Operation Status ErrCd ErrMsg                
------------------------------------------------
 0 CC        Failed  1001 Start CC not possible
------------------------------------------------

I've tried two different PE815, firmware on both is the same, DSU used.

Both systems have different chassis makes attached(although LSI in both I imagine).

I see this on both.

2 Posts

June 26th, 2018 00:00

Hello, were you able to find solution or reason for this? Iam having the same trouble and there is not much to google about it :/

 

root@vod0-iva:~# perccli /c0/v1 start init
Controller = 0
Status = Failure
Description = None

Detailed Status :
===============

-------------------------------------------------
VD Operation Status ErrCd ErrMsg
-------------------------------------------------
1 INIT Failed 255 Start FGI not possible
-------------------------------------------------

 

root@vod0-iva:/mnt# perccli /c0/v1 start cc
Controller = 0
Status = Failure
Description = None

Detailed Status :
===============

------------------------------------------------
VD Operation Status ErrCd ErrMsg
------------------------------------------------
1 CC Failed 255 Start CC not possible
------------------------------------------------

root@vod0-iva:/mnt# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 2.7T 0 disk
|-sda1 8:1 0 9M 0 part
`-sda2 8:2 0 2.7T 0 part
`-vg.system-lv.root 254:0 0 80G 0 lvm /
sdb 8:16 0 24.6T 0 disk
sdc 8:32 0 24.6T 0 disk
sdd 8:48 0 24.6T 0 disk
sde 8:64 0 24.6T 0 disk
sdf 8:80 0 24.6T 0 disk
sdg 8:96 0 24.6T 0 disk
sdh 8:112 0 24.6T 0 disk
sdi 8:128 0 138.8G 0 disk

VD LIST :
=======

-----------------------------------------------------------------
DG/VD TYPE State Access Consist Cache Cac sCC Size Name
-----------------------------------------------------------------
0/0 RAID1 Optl RW No RWBC - OFF 2.728 TB system
1/1 RAID50 Optl RW No RWTD - OFF 24.556 TB vol1
2/2 RAID50 Optl RW No RWTD - OFF 24.556 TB vol2
3/3 RAID50 Optl RW No RWTD - OFF 24.556 TB vol3
4/4 RAID50 Optl RW No RWTD - OFF 24.556 TB vol4
5/5 RAID50 Optl RW No RWTD - OFF 24.556 TB vol5
6/6 RAID50 Optl RW No RWTD - OFF 24.556 TB vol6
7/7 RAID50 Optl RW No RWTD - OFF 24.556 TB vol7
-----------------------------------------------------------------

 

 

1 Rookie

 • 

2 Posts

May 3rd, 2022 11:00

It is probably doing a background init as opposed to a regular foreground init. Check with:

 

perccli /c0/v1 show bgi

 

Once it's finished, you can start the cc. Which probably happened 5 years ago for the OP

 

No Events found!

Top