Start a Conversation

Unsolved

This post is more than 5 years old

S

7464

June 2nd, 2016 10:00

PS5000 - Storage array still initializing

To keep this from being too long I'll only include the high points and I can provide additional detail you need.

I have 2 PS5000 arrays that were formerly used to provide backup storage. All data had been moved off the arrays and the volumes deleted. Using the EqualLogic Group manager, I removed the arrays from the pool and from the group. I physically moved the arrays to another data center.

I interconnected the first array and power it on. Using the Remote Setup Wizard I was able to initialize the array as the initial member of a new group.

I interconnected the second array to the network and powered it on. With the Remote Setup Wizard, I attempted to add the second array to the group I created when I initialized the first array. This failed; I received a notification that the group could not be found. I am able to connect to the group so I know it exists; I may have typed the group name incorrectly when I specified the group to add the member to..

At this point the Remote Setup Wizard didn't see an uninitialized array but I was able to telnet to the second array. I initiated a reset command to reset the array to factory defaults. The reset appeared to start. This was a couple weeks ago.

I can connect to the active serial port. This notification is displayed when I connect: "The storage array is still initializing.  Limited commands will be available until the initialization is complete. Please try again later."


I am trying to determine what steps to take to make the array operational. Firmware version is 7.1.4. There is no data on the array. The LED indicators on the front of each drive is solid green.

Thanks for any info you can provide.

5 Practitioner

 • 

274.2K Posts

June 2nd, 2016 11:00

Hello, 

 What happened after you did the reset?  Did it reboot? 

 Sounds like maybe that process didn't complete.  Possibly a failing drive didn't get cleared. 

  When you login using grpadmin, type "su raidtool" 

  Please send the output, 

  You should see a list of all the drives under the "Available Drives".   There should be no raid info displayed. 

 I would reseat all the drives, then try reset again and make sure it actually got reset.  

 

 Regards, 

Don 

  

5 Practitioner

 • 

274.2K Posts

June 2nd, 2016 11:00

Hello, 

Resets are very quick, only a couple of minutes. 

Re: Drives. I would do so yes.  

I would do the reset again.  When it comes back up, and you log in, it should prompt you to run setup.  

If not then run the RAIDTOOL command. 

Don 

14 Posts

June 2nd, 2016 11:00

Thanks for the quick response.

So far as I know it didn't reboot after I did the reset. However, it is in another building so it could have booted after I left it. Approximately how long should a reset take?

Should the array be powered off to reseat the drives?

I'll update with the su raidtool result; it may be a couple of days before I can get it.

14 Posts

June 8th, 2016 08:00

I have ran the "Reset" command from the command line twice. This is the result:

CLI> reset
% Error - Object does not exist
% Error - Object does not exist

Warning: This command resets an array to the factory
defaults (original condition).  The result is the
elimination of all group and volume configuration
information and any volume data residing on the array.

It is strongly recommended that you not reset a running
array. Instead, use the delete member command which moves
data from this array to other arrays and automatically
resets this array.

This member Unknown
IP Addresses associated with this member:

Reset this array to factory defaults? [n/DeleteAllMyDataNow] DeleteAllMyDatanO Now
Setting cache to write through
cflush: RAID is faulted beyond recovery. The array cannot be rebooted
or halted in this state.
There are two options:
         1. Fix RAID and retry the shutdown.
         2. Power off the array. The data in the cache will be preserved until
            the battery is exhausted.
unable to clear cache and set to write through mode
Resetting system, this will take a few minutes.
Deleting backup password files
Deleting agent.cnf
Cleaning-up /pss/dumps/
Cleaning-up /pss/update/
Successfully stopped process
Successfully stopped process
*** ERROR *** No disks found
Zeroing drives, nvram and rebooting the system
 


#########################################################
#                                                       #
#       EqualLogic (R), Inc. storage array              #
#               Copyright 2001-2007                     #
#    70-0115 Rev=R10 SN=RMS93475A0280B4 ECO=C00         #
#                                                       #
#########################################################
            -- Type Ctrl-p key to enter setup mode --

BOOTROM version 7.0.0
Build Date: Thu Jan 24 08:07:38 EST 2008
Total memory: 0x40000000 bytes (1024MB)
NP Loading ...Done
SP Loading ...Done
   

Dell Inc. Storage Array


Copyright 2001-2015 Dell Inc.


SP:1.02:mips_pss_init.c:363:INFO:28.2.107:Control module in slot 0 with serial number RMS93475A0280B4 is designated as active.

MFS set up
Building databases...
Executing patch setup
SP:1465325912.80:cache_driver.cc:1072:INFO:28.2.39:Active control module cache set to write-back mode.

Tue Jun  7 14:58:45 EDT 2016
Jun  7 14:58:45 init: kernel security level changed from 0 to 1


PS Series Storage Arrays

Unauthorized Access Prohibited

Running "RAIDTOOL" produces this result:

CLI> su 'raidtool'
You are running a support command, which is normally restricted to PS Series Tec
hnical Support personnel. Do not use a support command without instruction from
Technical Support.
Driver Status: Ok
RAID LUN 0 Faulted Beyond Recovery.
  14 Drives (0?(core.dsb.status=1 drive_status=1000 drive_device=-1)
             ,8?(core.dsb.status=1 drive_status=1000 drive_device=-1)
             ,1?(core.dsb.status=1 drive_status=1000 drive_device=-1)
             ,9?(core.dsb.status=1 drive_status=1000 drive_device=-1)
             ,2?(core.dsb.status=1 drive_status=1000 drive_device=-1)
             ,10?(core.dsb.status=1 drive_status=1000 drive_device=-1)
             ,3?(core.dsb.status=1 drive_status=1000 drive_device=-1)
             ,11,4?(core.dsb.status=1 drive_status=1000 drive_device=-1)
             ,12?(core.dsb.status=1 drive_status=1000 drive_device=-1)
             ,5?(core.dsb.status=1 drive_status=1000 drive_device=-1)
             ,13,6?(core.dsb.status=1 drive_status=1000 drive_device=-1)
             ,14?(core.dsb.status=1 drive_status=1000 drive_device=-1)
             )
  RAID 10 (64KB sectPerSU)
  Capacity     2,532,311,040 bytes
Available Drives List: 0,1,2,3,4,5,6,7,8,9,10,12,14,15
CLI>

5 Practitioner

 • 

274.2K Posts

June 8th, 2016 08:00

Hello, 

 I'm going to guess you've got some old/flacky drives.  Part of the RAIDset labels are still there.  I would try removing drive 11.  It's the only one not showing as "available"    Then try reset again. 

 Don 

 

14 Posts

June 9th, 2016 07:00

I removed drives 11 & 13 from the array and reset it. I was prompted to initialize the array so it appears to be performing as expected. I see how it does when I initialize the array.

Since this is an old, unsupported array, I may not replace the drives. Are there any consequences to running the array with those drives pulled out enough so that they are not connected?

5 Practitioner

 • 

274.2K Posts

June 9th, 2016 10:00

Hello, 

 No, as long as they are in the slots to help promote proper air flow.  

 Don 

No Events found!

Top