SAS-12G Error

dF - Power on diagnostic fault.

what does the manament software say?

Management software doesn't see it, says the other controller isn't installed. 

Hello,

Yes I've reseated the controller. Also opened it up , reseated the CMOS battery and DIMM.

Thanks for the replies!

Hello I-AM-PAT,

Did you check MDSM recovery guru?

The recovery guru is a component of Modular Disk Storage Manager (MDSM) that diagnoses critical events on the Dell PowerVault MD Storage Array and recommends step-by-step recovery procedures for problem resolution.

How to access Recovery Guru:

https://dell.to/3FcVzcA.

Have you tried to reseat the controller?

Please ask me if you have any questions,

Hello I-AM-PAT,

Thank you for your reply.

Could you please also check recovery guru?

What is Array Status LED: Solid, Blinking Amber or Not Green?

Please ask me if you have any questions.

The guru says the controller is not installed.

As for the array itself, its blinking amber. The management application notifying me the 2nd controller is uninstalled.

Thanks!

Tried to login and now it's asking for the controller firmware since it's in lockdown mode.

I downloaded the version from the Dell support site but it isn't taking it -- am I doing something wrong?

I found a console cable and connected it to the controller.

Here is the error I"m seeing

RTC Error: Real-time clock device is not working

RTC Warning: Battery for real-time clock and NVSRAM must be replaced

Is that battery the little CMOS one? If so, could you kindly advise which model?

Along with this:

01/03/15-02:32:05 (tRAID): NOTE: DQ FTDC: Reinitialized DQ Trace History metadata: sanity check failed
01/03/15-02:32:06 (tRAID): SOD: Instantiation Phase Complete
01/03/15-02:32:05 (tRAID): NOTE: FTDC: Deferring format string copies due to pending restore
01/03/15-02:32:05 (tRAID): WARN: Error threshold exceeded: "Client_Corrupt_DB_Detected_On_Alt"
01/03/15-02:32:05 (tRAID): WARN: LEM:Client threshold Exceeded
01/03/15-02:32:05 (tRAID): NOTE: LEM: checkError(); Error threshold exceeded;SUSPENDED_LOCKDOWN;
01/03/15-02:32:05 (tRAID): WARN: sodLockdownCheck: sodSequence update: SuspLockdown
01/03/15-02:32:05 (tRAID): NOTE: Inter-Controller Communication Channels Opened
01/03/15-02:32:06 (tRAID): WARN: Error threshold exceeded: "Client_Corrupt_DB_Detected_On_Alt"
01/03/15-02:32:06 (tRAID): WARN: Client reported lockdown: "Client_Corrupt_DB_Detected_On_Alt"

Thanks!

I-AM-PAT,

We would need to look at the support bundles to confirm the issue. Would you be able to pull them and then upload them here. After uploading them would you Private Message Maria and myself the svc tag used to upload them, that way we can locate them?

Let me know. 

How do I see what lockdown mode I'm in?

As for support, we're out of warranty so I'll assume there would be a cost, or is this provided a no-cost since I'm locked out of my device and no work around?

Thanks!

Would you confirm which lockdown state you are currently in? Also, based on the segment of log you provided it would appear that there is database corruption, which was what looks to have triggered the lockdown. This is was done in order to protect from possible data loss. So what you would need to do is call in to support for them to assist in clearing the lockdown. 

So I've fixed the lockdown issue, but now I have two more issues:

1. The SAN doesn't see any of my HBAs (used to)

2. The SAN reports this error on one controller: RTC Warning: Battery for real-time clock and NVSRAM must be replaced (I've replaced the RTC battery)

You need to do a serial capture to see the controller boot up, and you will see it there.

As for support, it would be paid, either by warranty or pay as you need. Without it would be going about it clearing it on your own. 

Here is some additional info from the other controller

01/10/22-18:08:19 (tRAID): WARN: Lockdown case-DB CORRUPT. NVPS did not update from Sstor.
01/10/22-18:08:19 (tRAID): NOTE: Controller is in lockdown; skipping sendStagedFirmwareUpdateEvent()
01/10/22-18:08:20 (tRAID): SOD: Initialization Phase Complete
==============================================
Title: Disk Array Controller
Copyright 2013-2017 NetApp, Inc. All Rights Reserved.

Name: RC
Version: 08.25.13.60
Date: 09/12/2017
Time: 12:42:26 CDT
Models: 2701
Manager: devmgr.v1125api15.Manager
==============================================

01/10/22-18:08:19 (tRAID): NOTE: SYMbol available
01/10/22-18:08:19 (tRAID): WARN: *********************************************************
01/10/22-18:08:19 (tRAID): WARN: *********************************************************
01/10/22-18:08:19 (tRAID): WARN: ** **
01/10/22-18:08:19 (tRAID): WARN: ** WARNING!!!!!! **
01/10/22-18:08:19 (tRAID): WARN: ** **
01/10/22-18:08:19 (tRAID): WARN: ** This controller is locked down due to detected **
01/10/22-18:08:19 (tRAID): WARN: ** corruption in the primary database. **
01/10/22-18:08:19 (tRAID): WARN: ** In order to prevent any configuration loss, the **
01/10/22-18:08:19 (tRAID): WARN: ** backed up database must be restored. **
01/10/22-18:08:19 (tRAID): WARN: ** **
01/10/22-18:08:19 (tRAID): WARN: ** **
01/10/22-18:08:19 (tRAID): WARN: *********************************************************
01/10/22-18:08:19 (tRAID): WARN: *********************************************************
01/10/22-18:08:19 (tRAID): NOTE: Flashing tray summary fault LED
01/10/22-18:08:20 (tRAID): SOD: sodComplete Notification Complete
01/10/22-18:08:20 (tRAID): sodMain CtlrLockdown sequence finished, elapsed time = 57 seconds
01/10/22-18:08:20 (tRAID): sodMain complete
01/10/22-18:08:20 (tRAID): WARN: SOD lockdown sequence complete - suspending...

I would suggest waiting till we identify the issue before we start doing anything, so we don't create other issues.