Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

51215

January 27th, 2014 18:00

Dell MD3000i Firmware Update Error

Hello,

I am new around these forums and had a question with regards to updating the MD3000i. I am currently running a unit with two controllers on the following version:

Firmware version: 07.35.22.61      

NVSRAM version: N1532-735890-004 

EMW version: 03.35.G6.50

AMW version: 03.35.G6.50      

I was able to successfully update the firmware on the disks but when i tried updating the firmware and the NVSRAM at the same time to

N1532-735890-005 and 07.35.39.64

I got the following:

OPERATING ENVIRONMENT DATA

Client system name: %NAME%
Client OS: Windows Vista

Application version: 03.35.G6.50
Storage array management version: 03.35.G6.50
Storage array name:
Firmware version: 07.35.22.61
Management class: devmgr.v1035api01.Manager

**************************************************

ERROR DATA

Command sent to RAID controller module in slot: 1
Host name: %NAME%
IP address: %IP ADDRESS%

Return code: Error 68 - A problem has occurred during the download. Please retry the operation.
Operation when error occurred: PROC_loadControllerFirmware
Timestamp: ##################

STACK DATA

devmgr.v1035api01.sam.jal.ManagementOperationFailedException:
    at devmgr.v1035api01.sam.jal.SYMbolClient.dispatchOperation(Unknown Source)
    at devmgr.v1035api01.sam.jal.StorageArrayFacade.issueCommand(Unknown Source)
    at devmgr.v1035api01.sam.jal.StorageArrayFacade.downloadToController(Unknown Source)
    at devmgr.v1035api01.sam.jal.StorageArrayFacade.stagedControllerFirmwareDownload(Unknown Source)
    at devmgr.v1035api01.sam.controllerdownload.ProgressAndCompletionStatusDialog$2.performOp(Unknown Source)
    at devmgr.v1035api01.shared.BackgroundTask.run(Unknown Source)


THREAD DATA

Thread[Reference Handler,10,system]
Thread[Finalizer,8,system]
Thread[Signal Dispatcher,9,system]
Thread[Java2D Disposer,10,system]
Thread[TimerQueue,5,system]
Thread[AWT-Windows,6,main]
Thread[AWT-Shutdown,5,main]
Thread[DestroyJavaVM,5,main]
Thread[GarbageCollectorThread,6,main]
Thread[ChangeDetector,6,main]
Thread[LogMsgThread,6,main]
Thread[Np_Link_Monitor0,6,main]
Thread[RecoveryProfile-18,6,main]
Thread[RecoveryProfile-19,6,main]
Thread[RecoveryProfile-17,6,main]
Thread[AEN-20,6,main]
Thread[AEN-22,6,main]
Thread[AEN-21,6,main]
Thread[Timer-0,6,main]
Thread[Timer-1,6,main]
Thread[Timer-2,6,main]
Thread[RecoveryProfile-2140,6,main]
Thread[AEN-2141,6,main]
Thread[Timer-3,6,main]
Thread[AWT-EventQueue-0,6,main]
Thread[Image Animator 3,3,main]
Thread[Image Fetcher 0,8,main]

I am not sure what the error above could mean but is this related to a connection issue when transferring the file? My other question was whether it was OK to try to update the firmware and the NVSRAM at the same time or should I do this separately? Thank for all the help.

Moderator

 • 

7K Posts

January 28th, 2014 05:00

Hello glenn07,

It looks like there was an issue copying the file from your system to the MD3000. I would retry it again & see if you get the same error again. Here is the way we recommend upgrading the firmware if you don’t already have it.

Steps to update the firmware:

 

  1. Ensure you have a tested backup of the data contained on the array
  2. It is highly recommended to gather support bundle from the "Support" tab of the MD Storage Manager before performing any firmware upgrade operations. Also recommend getting another support bundle after the upgrade is complete.
  3. You must stop all I/O going to the array
  4. Load MDSM to verify connectivity, then close MDSM but leave the main management screen open
  5. From the main management screen in MDSM use the “upgrade raid controller firmware” on the “devices” screen to upgrade to the latest firmware
  6. Verify connectivity through MDSM
  7. Update the hard drive firmware if applicable
  8. Reboot the stack
  9. Power down the server(s)
  10. Power down the MD3000(i)
  11. Power down any attached storage (MD1000/12xx)
  12. Leave the power off for 2-3 minutes
  13. Power up in reverse order
    1. Verify connection to the array and virtual disks and verify that data is presented to each of the connected servers

 

This update process will take 60-90 minutes but will vary depending on how long the reboots take to complete.

Please let us know if you have any other questions.

2 Posts

January 28th, 2014 19:00

Sam,

If I am going from:

Firmware version: 07.35.22.61     

NVSRAM version: N1532-735890-004

to:

07.35.39.64 and N1532-735890-005

do I select the option to update the firmware and NVSRAM at the same time or are these done separately? Thank you for your time.

Moderator

 • 

7K Posts

January 29th, 2014 09:00

Hello glenn07,

Typically you can select the option to do both at the same time. But if it fails to do so then we recommend that you upgrade the firmware first then upgrade the NVSRAM.

Please let us know if you have any other questions.

2 Posts

January 30th, 2014 03:00

Hi Sam,

When would you do the disk firmware before or after the Controller and NVSRAM?

Moderator

 • 

7K Posts

January 30th, 2014 06:00

Hello Harty UK,

You want to install the disk firmware last. As it is stated in my post above (step 7) you want to install the harddrive firmware last before you power down the stack & then power back on the stack.

Please let us know if you have any other questions.

2 Posts

January 31st, 2014 06:00

Thanks Sam, all went well.

 

Only issue being, there is a MD1000 attached, it has 1TB SAS drives in it (ST1000NM001) - in the HDD firmware bundle this model isn't listed, but I did find a .exe for the latest firmware for this model (PS08, its currently PS06). I have extracted the exe file, and cannot find a .df file for me to update the firmware through the MDSM - any thoughts?

I ran the .exe file on the server and it doesn't detect the disks.

 

All the best

Alex.

No Events found!

Top