Start a Conversation

Unsolved

This post is more than 5 years old

TB

100877

April 1st, 2014 13:00

Dell MD3000 Replacement Hard Drive Status Offline

I have an MD3000 and I am attempting add additional hard drives to the array.  I have dell parts and good firmware, the array sees the hard drives in the slots, however the disks are showing as offline.

I have reviewed the SMCLI and believe that I can use the revive option to wake the drives, just don't want to do that if I run the risk of destroying data if I do this.

Thanks.

Moderator

 • 

7.6K Posts

April 2nd, 2014 06:00

Hello Tom Butler,

What version of firmware are you running on the MD3000? Sometimes drives will not come online if not on the latest firmware version of 07.35.39.64. Here is the link to the latest version of firmware if you need it. http://www.dell.com/support/drivers/us/en/19/DriverDetails/Product/powervault-md3000?driverId=R315163&osCode=WNET&fileId=2731121563&languageCode=en&categoryId=SF

There is chance that by running revive command on the slot that it can harm your data. what I would do is to make sure that you have a test backup before you do it just in case there are any issues.

Please let us know if you have any other questions.

April 2nd, 2014 08:00

Sam L.  Below is a grab from the array summary.  I am using the most recent firmware as far as I can see.  I would like to set a time to schedule an outage to stop all IO on this array and get these drives where I can use them.  If all I/O is stopped and we have a good back up should I be safe brining the new drives alive with the revive command or is there a better method to use?

PROFILE FOR STORAGE ARRAY: *********** (Wed Apr 02 09:24:38 CDT 2014)

SUMMARY------------------------------

  Number of RAID controller modules: 2

  Number of disk groups: 4

  RAID 6: Enabled

  Total number of virtual disks used:     4    

     Number of standard virtual disks:    3    

     Number of access virtual disks:      1    

  Total number of virtual disks allowed:  256  

  Snapshot Virtual Disks:                                  Disabled  

     Number of snapshots used:                             0          

     Number of snapshots allowed:                          0          

     Number of snapshots allowed per source virtual disk:  0          

  Virtual Disk Copy:            Disabled  

     Number of copies used:     0          

     Number of copies allowed:  0          

  Number of physical disks:        12                                

  Mixed physical disk types:       Enabled                          

  Current physical disk type(s):   Serial Attached SCSI (SAS) (12)  

  Total hot spare physical disks:  3                                

     Standby:                      1                                

     In use:                       2                                

  Number of expansion enclosures:          0  

  Number of expansion enclosures allowed:  2  

  Storage Partitioning:             Enabled  

     Number of partitions used:     1        

     Number of partitions allowed:  4        

  Number of virtual disks allowed per partition: 256

  Access virtual disk:  LUN 31,31 (see Mappings section for details)                      

  Default host OS:      Windows Server 2003/Server 2008 Non-Clustered (Host OS index 0)  

  Current configuration                                              

     Firmware version:                             07.35.39.64        

     NVSRAM version:                             N133X-735890-005  

     EMW version:                                  03.35.G6.50        

     AMW version:                                  03.35.G6.50        

  Pending configuration                                              

     Staged firmware download supported:           Yes                

     Firmware version:                             None              

     NVSRAM version:                               None              

     Transferred on:                               None              

  RAID Controller Module enclosure audible alarm:  Disabled          

  NVSRAM configured for batteries:          Yes  

  Start cache flushing at (in percentage):  80    

  Stop cache flushing at (in percentage):   80    

  Cache block size (in KB):                 4    

  Media scan frequency (in days): 15

  Failover alert delay (in minutes): 5

  Feature enable identifier: 313200000000000000000000518760F9

  Feature pack: Basic

  Feature pack submodel ID: 39

  Storage array world-wide identifier (ID): 6001EC9000DFDEA200000000518760F8

Moderator

 • 

7.6K Posts

April 2nd, 2014 08:00

Hello Tom Butler,

Can I get you to gather a support bundle from the MD3000 so I can review it & see what is going on with the drives.  I will send you a private message that you can upload the logs to so I can pull them down & let you know what I am seeing.  

Please let us know if you have any other questions.

Moderator

 • 

7.6K Posts

April 2nd, 2014 11:00

Hello Tom Butler,

First off thanks for the logs as it helps get a better as to what is going on with your MD3000. The first thing that I noticed is that you have 2 of your hotspares are in use. I also see that drive Enclosure 0 Disk 4 & Enclosure 0 Disk 13 are both offline. I am guessing that those were the drives that were replaced & not coming online. The new disk that you put into those drives did they come from another MD unit? The reason that I ask is that the disks were put into an offline status due to the MD reading them and seeing that there was data on the drives that doesn’t match the data that is in the current MD. Also to protect the data on the drive it puts them in an offline status. Now if that is the case then we can bring the drives online by running a replace command from SMCLI. Here is a link to the SMCLI guide. ftp://ftp.dell.com/manuals/Common/powervault-md3200_reference%20guide2_en-us.pdf

Here is the command that you can run to see if you can bring the drive online is the replace command.

Replace Physical Disk (this command can be found on pg. 235 of the guide).

replace physicalDisk ([enclosureID,slotID] | ) this command can be found on pg. 235 of the guide.

you will need to run that command for both 0,4 & 0,13.

 

Now if both of those drives have no data on them & you are sure then you can run an Initialize on them. But need to warn you that if you do an initialize on them that you will wipe all data on those drives that you run the command on. Here is the command for doing an initialize. & the command can be found on pg. 353 of the guide as well.

Start Physical Disk Initialize

start physicalDisk [enclosureID,slotID] initialize

 

A few other things that I noticed from the support bundle is that it looks like your raid battery for both controllers are also not showing as charged and looks like they have died. Now you can get replacement ones if you wanted to or you can keep running as is & it will do direct reads & writes to the drives as caching is disabled when you have failed raid battery.

Please let us know if you have any other questions.

No Events found!

Top