Unsolved

This post is more than 5 years old

15 Posts

4199

August 1st, 2017 13:00

MD3220 - SAS Port Failed

Hello,

We had a failed controller card on an MD3220, so we ordered a replacement. We received a new controller card from our Dell part rep and swapped it out. We can now see the card and it is showing as online.

Immediately following, I found that the other controller is giving us this SAS Port Failed error. All connections have been verified as seated properly. Any idea what could be causing this?

15 Posts

August 1st, 2017 14:00

...

15 Posts

August 1st, 2017 14:00

...

15 Posts

August 1st, 2017 14:00

...

15 Posts

August 1st, 2017 14:00

...

Community Manager

 • 

8K Posts

 • 

375 Points

August 2nd, 2017 07:00

Hello ProTech3m,

Do you have any MD1200 or MD1220 expansion enclosures attached to your MD3220? Wide port errors are generally associated with a controller reset. Now what may have happened, is that your controller could have reset during its boot sequence. This is not unusual when changes are made. The controller will see the changes, commit them to running memory, then reboot to commit them to permanent memory.

What is need is to look at the event log. You want to see if there are corresponding wide port optimal messages. You also might look for Start of Day Routine start and completed messages. If that’s all completing then you are good to go as there is no error.

Please let us know if you have any other questions.

15 Posts

August 2nd, 2017 12:00

Hello Sam,

Thank you for the response. YES, we do have two MD1220's attached to that MD3200, Unfortunately, I do not see an entry for "wide port optimal" relating to Enclosure 0, Slot 1.

Community Manager

 • 

8K Posts

 • 

375 Points

August 3rd, 2017 07:00

Hello ProTech3m,

Can I get you to gather a support bundle from your MD3220? We need to review it so that we can see why you are getting the error, and so we can let you know how best to resolve your error. I will send you a private message, so that you can reply back with the support bundle.

Please let us know if you have any other questions.

Community Manager

 • 

8K Posts

 • 

375 Points

August 3rd, 2017 13:00

Hello ProTech3m,

Thanks for the support bundle. We are seeing this error   Host Interface(s): Unable to retrieve latest data; using last known state. When you get that error it is most of the time cleared by reboot of that raid controller. In your case the controller that needs to be rebooted is controller0 in your MD3200.

We also noticed that you are running a really old version of firmware on your MD3200. The current version is 08.20.24.60 and you are at 07.80.41.60. I would recommend that when you can upgrade the firmware to the latest version. Here is a link to the latest firmware just in case you need it.

Controller Firmware

http://www.dell.com/support/home/us/en/19/drivers/driversdetails?driverId=4CP5X&fileId=3678779429&osCode=W12R2&productCode=powervault-md3200&languageCode=en&categoryId=SG

Resource cd

http://www.dell.com/support/home/us/en/19/drivers/driversdetails?driverId=R9G1X&fileId=3587386326&osCode=W12R2&productCode=powervault-md3200&languageCode=en&categoryId=CD

HDD/SSD Firmware

http://www.dell.com/support/home/us/en/19/drivers/driversdetails?driverId=NG0X5&fileId=3676772686&osCode=W12R2&productCode=powervault-md3200&languageCode=en&categoryId=EH

Here are the steps for doing a firmware upgrade as well.

  1. Gather support bundle in MDSM
  2. WARNING: If you have a single controller PowerVault MD3200/MD3600 series storage array you must stop all I/O operations before starting the firmware upgrade.
  3. Extract the firmware to folders and remember location.
  4. Burn or mount the ISO for the resource cd.
  5. Uninstall the MDSM from hosts (reboot required)
  6. Install MDSM from resource DVD (reboot required)
  7. Clear the Major Event Log.
  8. Update to 07.75.28.60 if not already there, then update to latest firmware.
  • If you receive an error while checking the SPM database, ensure that you have an out of band management connection to both RAID controllers.
  1. Verify connection and data.

10. Update the hard drive firmware.

11. Reboot stack and verify all is optimal.

  1. Power down the server(s)
  2. Power down the MD32x0(i)
  3. Power down any attached storage (MD12xx)
  4. Leave the power off for 2-3 minutes

 

 Please allow for at least 60-85 minutes for the updates.  Time may vary depending on how long each reboot takes.

 

Please let us know if you have any other questions.

15 Posts

August 3rd, 2017 14:00

Hi Sam,

 

Thank you for all of the information. Unfortunately, this is a remote server, so I do not have physical access to the box. Additionally, it is a backup for a mission critical production box, so I prefer not to install new software in order to mount the iso file. As much as I would like to update all of the firmware, that may be a difficult. In the meanwhile, how can I go about rebooting the controller card? I have been using the GUI, can it be done in that? If not, how do I access the CLI?

Community Manager

 • 

8K Posts

 • 

375 Points

August 4th, 2017 08:00

Hello ProTech3m,

You can use MDSM to reboot the controller. You can use SMCLI as that is installed when you install MDSM. Here is a link to SMCLI guide just in case you need it. http://topics-cdn.dell.com/pdf/powervault-md3200_cli%20guide_en-us.pdf

Please let us know if you have any other questions.

15 Posts

August 7th, 2017 10:00

I tried:

C:\Program Files (x86)\Dell\MD Storage Software\MD Storage Manager\client>SMcli [The known IP of the controller] -c reset controller 0

With no luck. It returned a "Unknown or unresponsive address..."

15 Posts

August 7th, 2017 13:00

I found the reset in the GUI and tried that as well. No dice!

OPERATING ENVIRONMENT DATA

Client system name: ********
Client OS: Windows Server 2008 R2

Application version: 10.80.G6.47
Storage array management version: 10.80.G6.47
Storage array name: ********-ARRAY
Firmware version: 07.80.41.60
Management class: devmgr.v1080api06.Manager

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

ERROR DATA

Command sent to RAID controller module in slot:
Host name: 0.0.0.0
IP address: 0.0.0.0

Return code: The Reset RAID Controller Module operation was unabl e to establish communication with RAID controller module 0 to verify the reset operation completed successfully. Possible causes include network or connection problems, or a RAID controller module initialization error. Check these possible causes and then retry the operation.
Operation when error occurred: Resetting Storage Array
Timestamp: Aug 7, 2017 3:38:10 PM

STACK DATA

devmgr.v1080api06.sam.jal.ManagementOperationFailedException:
at devmgr.v1080api06.sam.jal.StorageArrayFacade.createException(StorageArrayFacade.java:11037)
at devmgr.v1080api06.sam.jal.StorageArrayFacade.resetController(StorageArrayFacade.java:8309)
at devmgr.v1080api06.sam.advanced.resetcontroller.ResetCntrlProgressDialog$ResetBackgroundTask.performOp(ResetCntrlProgressDialog.java:248)
at devmgr.v1080api06.shared.AbstractTaskAdapter.run(AbstractTaskAdapter.java:104)


THREAD DATA

Thread[Reference Handler,10,system]
Thread[Finalizer,8,system]
Thread[Signal Dispatcher,9,system]
Thread[Attach Listener,5,system]
Thread[Java2D Disposer,10,system]
Thread[TimerQueue,5,system]
Thread[AWT-Shutdown,5,main]
Thread[AWT-Windows,6,main]
Thread[EventQueueMonitor-ComponentEvtDispatch,5,main]
Thread[Thread-3,5,main]
Thread[AWT-EventQueue-0,6,main]
Thread[DestroyJavaVM,5,main]
Thread[ChangeDetector,6,main]
Thread[LogMsgThread,6,main]
Thread[Np_Link_Monitor0,6,main]
Thread[DMVGarbageCollectorThread,6,main]
Thread[RecoveryProfile-15,6,main]
Thread[AEN-16,6,main]
Thread[Timer-0,6,main]
Thread[Thread-35,6,main]
Thread[Timer-3,6,main]
Thread[Thread-50,6,main]
Thread[Image Animator 0,3,main]

Community Manager

 • 

8K Posts

 • 

375 Points

August 17th, 2017 13:00

Hello ProTech3m,

When the reset doesn’t work via MDSM then you will need to manually pull the controller to reboot it.

Please let us know if you have any other questions.

No Events found!

Top