Hello,

I have a Dell PowerVault MD1000 with PERC 5/E Sas controller. I Want to know a list of DELL Poweredge server able to connect with it.

Can i connect with a DELL Poweredge R720 or newer server?

Many thanks.

Regards,

Here are this week's top-rated support articles based on accuracy, usefulness, & ease of understanding:

• How to clear the SBE memory log on your PowerEdge server 
• Create and initialize a virtual disk (VD) on your PowerEdge RAID controller (PERC)
• Information on Conditional Forwarders and Stub Zones in Windows DNS
• Windows Server: Common issues in Broadcom Advanced Control Suite 4 (BACS4)
• Use command line to install the OMSA VIB plug-in on PowerEdge servers running ESXi 5.x or 6.x

Hello,

Our office has a new MD3860f with 20 1.2TB drives. I had updated firmware and NVSRAM to the newest version. We had those 20 drives in RAID 10 mode. This week we got other 60 4TB drives, so I took out existing 20 drives and installed the 60 new drives. After I reboot the array, I can connect it with the management IP address, but it is showing Storage Array Unknown and status showing Needs Attention (The RAID Controller is currently in lockeddown mode). When I try to start "Manage Storage Array", all I got is Recovery Guru window showing Storage Array in Recovery Mode.

I have attached serial cable and using putty to access console interface using 9600-8-1 setting. But when I send Ctrl-Break command, it gives me options for Service Interface (S) and baud rate change. When I go to service interface, I get only 3 options as shown below;

1) Display IP Configuration

2) Display Seven Segment LED Code

 Q) Quit Menu

How can I clear the Lockdwon mode? Tell me where I may execute the commands on the RAID controller in storage array.

Hello,

I'm having issues upgrading the tape drive in our Powervault TL 2000. It is connected to a Windows Server 2012 R2 server via a SAS switch.

While connected with the LTO-4 tape drive installed, Windows and DPM recognize the media changer and the tape drive.

Once I install the brand new LTO-6 drive in the tape library, it brings the drive online, scans, then says ready but after a few minutes the status changes to "HE: drive logged out Code: FB 01". While the LTO-6 drive is installed Windows and ITDT only sees the tape drive not the media changer and DPM only shows a standalone drive. When trying to upgrade the drive firmware on the web interface I received the error "Error During Firmware Upgrade: IR: SCSI invalid opcode !"  but I was able to update the firmware for the drive via ITDT on the server. The web interface of the library is still showing the firmware and drive product ID of the LTO-4 drive.

The library is on E.30 firmware and the drive is on G9P1. If I swap the drives back to the LTO-4 everything works as expected. 

Any help is appreciated.

Thanks!

We run an MD3220 along with an expansion shelf .  The expansion shelf is a model MD1220.  We have a planned power outage for our building coming up soon.  We have no generators onsite.  So, I need to figure out how to do a graceful shutdown.  Can anyone provide me with a step-by-step guide on how to correctly power this thing off and back on?  This system is very new to me, so I'm quite clueless on where to start.  What I learned today is that it seems I can access the admin console via PowerVault Modular Disk Storage Manager.  Beyond that, I could really use your help.

I lost all connection to the MD3000 after the RAID card produced a PCI-e error. I gracefully shut down the server and took the RAID card and the PCI-E riser card out of my DELL2950 server and cleaned and re-seated both. I reconnected the SAS cable and started the server up with no errors. Now I do not see the RAID card in Device Manager and as a result, cannot see the MD3000 enclosure. I use a Dell SAS 5e Adapter Controller. So my question is do I need a new RAID card or do I reinstall drivers?

I have a second server attached to the MD3000 mapped to two other Virtual Drives. It still is connected to them but does not see the contents. When I go to Disk Manager in Windows, it says I have to Initialize the disks to see them. Will that erase them? I cannot have that. It also wants me to choose between MBR and GPT. I dont know what the original settings for that is. A little advice please. Thanks

I downloaded the Support Information if needed.

I have Dell MD3220 that I was trying to update the firmware before putting it  back into service.

The bridge firmware update worked, the I tried to update the firmware to the current version it failed and now I have large brick.  I am not trying to save any data.

I am now trying to update firmware to the current version using the serial port with Hyper-terminal.  After 2 hours of the file transfer I get the following message.

Transfer Cancelled by Remote System.

I can get the bridge firmware to update using the serial port.

Any idea's?

I have a MD3200i running firmware version 07.84.53.60 on the RAID module. This MD3200i has always only had one controller. Everything has been running fine but I want to add a second module to this system.

Are there any gotchas that I should be aware of before attempting this? Do I need to power down the MD3200i and all ESXi hosts attached to it before installing the module? What if the new module has a newer firmware version than the firmware installed on the current module?

Hi,

I'm having issues with the drive of our PowerVault TL2000.

A job initially failed with "Inventory lost - destination probably full ... Code: 8A 4B". Through the web interface, I was able to move the tape from the drive to a free slow without issue.

When I rebooted the TL2000 to clear the error the following happens:

- blinking green status light (Web interface Library status says 'Connecting Drive', and Drive 1 Status 'Offline')
- after ~10 minutes the drive starts scanning the magazines
- after a couple more minutes The TL2000 status LED changes to solid green
- shortly after, TL2000 fan speed increases and the Amber alert LED comes on solid with a "Drive Comm.-Err F101"
- at this time, the Web interface indicates:

Status: HE: drive logged out Code: FB 01

Drive 1 Status: Exception F1 01 - Error 22/22

Thanks very much for your assistance.

Harry J.

Hi All,

I had a controller fail in one of our MD3200i yesterday.  This is no problem, we have spare hardware available for these circumstances.

I'm aware that when you insert a new/replacement controller, it will download and install the firmware to match the running controller. No problem.   My question is - does it matter if there is any pre-existing configuration on the REPLACEMENT controller? The controller we are going to use as a replacement has been used in our spare MD3200i (some DR work and benchmarking previously).  

So, do i need to wipe the configuration first, or will the configuration from the existing controller simply be downloaded to the replacement controller?

Thanks!!

Hello,

I have a Powervault NX3100 with a COA for Storage Server 2008.

Where can I find/how can I get the files to restore to original on new storage?

Thank you,

Mike

We have a MD3200i connected using iSCSI with 2 controllers.  On occasion we will get a warning stating the Virtual Disk is not on the preferred path.  Over the years this happens 2 or 3 times a year and we simply go in via Powervault Modular Disk Storage Manager and through menu Storage \ Virtual Disk \ Change \ Ownership-Preferred Path \...   BUT almost all menu options are grayed out by the time you drill down.  So in this case once you get down to the Change menu option all items below it are grayed out.

For some reason I feel like this has happened several years ago, but can't remember what caused it.

Perhaps I will need to completely shutdown everything on this device and then powercycle the device, but would like to avoid this.

Does anyone know why I am seeing this?

Storage Management Version is 10.84.G6.44 and has been this for years.

Firmware Info:

Storage Array
 
    Storage Array Name: MD3200i
    Current Package Version: 07.84.44.60
    Current NVSRAM Version: N26X0-784890-00

RAID Controller Modules
 
    Location: Enclosure 0, Slot 0
    Current Package Version: 07.84.44.60
    Current NVSRAM Version: N26X0-784890-004
    Board ID: 2660
    Sub-Model ID: 143

    Location: Enclosure 0, Slot 1
    Current Package Version: 07.84.44.60
    Current NVSRAM Version: N26X0-784890-004
    Board ID: 2660
    Sub-Model ID: 143

Again none of the firmware or software versions have changed in years.

Any advice would be appreciated as I need to move the controller back to preferred path, but can't get to menu option to change it due to many of them being grayed out.

Thanks,

Greg

We have several TL2000 tape loaders at remote sites used for backup. Periodically the long-running jobs will somewhat consistently fail with an E00084ED error in backup exec, indicating a communication error with the tape drive. These are accompanied in the event log by event ID 129 "Reset to device, \Device\RaidPort1, was issued", and event ID 11 "The driver detected a controller error on \Device\RaidPort1. ITDT diagnostics show no problems with the drive or communication.

Small jobs to tape work and verify, long jobs to disk work and verify, long jobs to take nearly always fail. In the past we have replaced cleaned drives with new cleaning cartridges, replaced entire tape drives, switched to brand new tapes, none of which had any effect. Only splitting the jobs up into smaller ones (< 12 hr run time including verify) stopped the failures, and this is becoming impractical. 

The event log errors seem to point to something with the storage controller, a Dell 6Gbps SAS HBA. LSI cards and autoloaders seem to have these issues frequently, Microsoft has a trouobleshooting document :

that includes the following advice: 

• Slow the transfer rate settings if the timeouts are associated with tape drives - using 5MBS transfer rate usually cures the timeouts.

Where would I "slow the transfer rate"? Are there any other troubleshooting steps I can take?

PowerEdge T610 server running Windows Server 2008r2, BE 2010, Dell 6Gbps SAS HBA, TL2000 autoloader with single LTO5 drive. 

For reasons too embarrassing and frustrating to blather about, I am the proud owner of a Dell MD1200 enclosure and 12 ST4000NM0014 4TB Seagate drives (short story: I thought they were ST4000NM0023's, which work fine in our enclosure). The drives ending in 14 are 12Gbps and almost identical to the drives ending in 23 except the latter are 6 Gbps.

The drives show as 475Gb capacity on our R620 with Dell PERC 810 (and, incidentally, a LSI 9280-8e RAID controller that I've tried). Can I use my 12Gbps drives on my 6Gbps MD1200 or is this simply not going to work?

The drives show up as 475G on the BIOS configuration screen too, so I'm sure it's not an O/S problem (happens to be CentOS 7.2, but again that's not in play here).

The BIOS is 2.5.4, the MD1200 firmware is 1.06. I tried to update the 9280-8e and my version is higher than Broadcom's, and I think but I'm not sure that the PERC's firmware is the latest.

I don't want to waste too much more time; I know it's not officially supported but maybe someone out there knows that it's foolish to even try...

Here are this week's top-rated support articles based on accuracy, usefulness, & ease of understanding:

• Extracting RAID controller logs via MegaCLI (Windows + Linux)
• PowerEdge server FAQ
• How to configure iDRAC and systems management options on PowerEdge servers
• Export of SupportAssist Collection (previously TSR) and RAID controller log via iDRAC 7+8
• PowerEdge Servers - What are the different RAID levels and their specifications?

Hello,

We have a Dell MD 3260 with two enclosures. Originally 60 4TB disks in the first and 35 4TB Disks in the second.  Recently 12 4TB disks have been added to the second enclosure.  A RAID volume has not been configured to the new drives but we have a error coming now.

Storage array: 40016

Degraded physical disk paths

Channel: 1

Related physical disks: (1, 3, 4)

What is physically "Channel 1"?

HI, we have dual controller system with md3200i and one enclosure…

Soon I find in MDSM that one of controllers is missed or removed, just empty space in manager, but controller is in storage system, and I can ping it.

We use VMware, and multipathing driver for failover switched ok, and nobody understand that controller is down...

After piece of bit searching I find how to connect to service console with PS2 serial cable… and I look that

Send <BREAK> for Service Interface or baud rate change

05/03/17-07:27:49 (tRAID): NOTE:  Set Powerup State

05/03/17-07:27:49 (tRAID): NOTE:  SOD Sequence is Normal, 0

05/03/17-07:27:50 (tRAID): NOTE:  Turning on tray summary fault LED

05/03/17-07:27:50 (tRAID): NOTE:  SODRebootLoop- Limit:5 Cnt:6

05/03/17-07:27:50 (tRAID): NOTE:  Flashing tray summary fault LED

05/03/17-07:27:50 (tRAID): WARN:  Controller entering SODReboot lockdown state...

I search again for solution, and find how to run command “lemClearLockdown”, and run it…

After that, controller can be viewed in failed state in MDSM, I’m happy now I can see it and switch it back in online mode, but my happy is short.

Now on service console, I see that:

-=<###>=-

Instantiating /ram as rawFs,  device = 0x1

Formatting /ram for DOSFS

Instantiating /ram as rawFs, device = 0x1

Formatting...Retrieved old volume params with %38 confidence:

Volume Parameters: FAT type: FAT32, sectors per cluster 0

  0 FAT copies, 0 clusters, 0 sectors per FAT

  Sectors reserved 0, hidden 0, FAT sectors 0

  Root dir entries 0, sysId (null)  , serial number 10000

  Label:"           " ...

Disk with 1024 sectors of 512 bytes will be formatted with:

Volume Parameters: FAT type: FAT12, sectors per cluster 1

  2 FAT copies, 1010 clusters, 3 sectors per FAT

  Sectors reserved 1, hidden 0, FAT sectors 6

  Root dir entries 112, sysId VXDOS12 , serial number 10000

  Label:"           " ...

RTC Error:  Real-time clock device is not working

OK.

Adding 14630 symbols for standalone.

Reset, Power-Up Diagnostics - Loop 1 of 1

3600 Processor DRAM

     01 Data lines                                                  Passed

     02 Address lines                                               Passed

3300 NVSRAM

     01 Data lines                                                  Passed

4410 Ethernet 82574 1

     01 Register read                                               Passed

     02 Register address lines                                      Passed

6D40 Bobcat

     02 Flash Test                                                  Passed

3700 PLB SRAM

     01 Data lines                                                  Passed

     02 Address lines                                               Passed

7000 SE iSCSI BE2 1

     01 Register Read Test                                          Passed

     02 Register Address Lines Test                                 Passed

     03 Register Data Lines Test                                    Passed

3900 Real-Time Clock

     01 RT Clock Tick                                               Passed

Diagnostic Manager exited normally.

eth0: LinkUp event

05/03/17-08:20:14 (tNetCfgInit): NOTE:  Network Ready

Current date: 05/03/17  time: 14:35:59

Send <BREAK> for Service Interface or baud rate change

05/03/17-08:20:22 (tRAID): NOTE:  SOD Sequence is Normal, 0

05/03/17-08:20:22 (tRAID): NOTE:  Turning on tray summary fault LED

05/03/17-08:20:22 (tRAID): NOTE:  SODRebootLoop- Limit:5 Cnt:1

05/03/17-08:20:22 (tRAID): NOTE:  Installed Protocols: <MTPs: INIC SAS USB > <ITPs: RDMA ISER IPOIB > <STPs: FCP RmtDMA iSCSI SAS >

05/03/17-08:20:22 (tRAID): NOTE:  Required  Protocols: <MTPs: INIC SAS > <ITPs: UNK > <STPs: iSCSI SAS >

05/03/17-08:20:22 (tRAID): NOTE:  loading flash file: iSCSI

05/03/17-08:20:23 (tRAID): NOTE:  soc is a stub

05/03/17-08:20:24 (tRAID): NOTE:  SYMBOL: SYMbolAPI registered.

05/03/17-08:20:25 (tRAID): WARN:   RCBBitmapManager total RPA size = 1828716544

05/03/17-08:20:25 (tRAID): NOTE:  fcn is a stub

05/03/17-08:20:25 (tRAID): NOTE:  In iscsiIOQLIscsiInitDq.  iscsiIoFstrBase = 0x5

05/03/17-08:20:25 (tRAID): NOTE:  qlg40xx is a stub

05/03/17-08:20:25 (tRAID): NOTE:  loading flash file: MTLSEBET1G

MTLSE Driver version 2.300.310.144 built on Jun 13 2011 : 17:47:51

05/03/17-08:20:26 (tRAID): NOTE:  mtlsebeDqInit

*** Disabled FULL TRACE ***

05/03/17-08:20:26 (tRAID): NOTE:  mtlsebeDqInit return

Found 4 BE devices on this controller

05/03/17-08:20:26 (tRAID): NOTE:  MTL sgl_pool pool 2080 objects created

05/03/17-08:20:26 (tRAID): NOTE:  mtlsebe::Mtl::supportsDeviceId 0x21019a2 - TRUE

05/03/17-08:20:26 (tRAID): NOTE:  mtlsebe::Mtl::supportsDeviceId 0x21019a2 - TRUE

05/03/17-08:20:26 (tRAID): NOTE:  mtlsebe::Mtl::supportsDeviceId 0x21019a2 - TRUE

05/03/17-08:20:26 (tRAID): NOTE:  mtlsebe::Mtl::supportsDeviceId 0x21019a2 - TRUE

05/03/17-08:20:26 (tRAID): NOTE:  mtlsebe::Mtl::supportsDeviceId 0x21019a2 - TRUE

05/03/17-08:20:26 (tRAID): NOTE:  mtlsebe::Mtl::supportsDeviceId 0x21019a2 - TRUE

05/03/17-08:20:26 (tRAID): NOTE:  mtlsebe::Mtl::supportsDeviceId 0x21019a2 - TRUE

05/03/17-08:20:26 (tRAID): NOTE:  mtlsebe::Mtl::supportsDeviceId 0x21019a2 - TRUE

05/03/17-08:20:26 (tRAID): WARN:  init: ioc: 0, PLVersion: 06-000-05-00

05/03/17-08:20:26 (tRAID): NOTE:  NumberOfCmndBuffs: 1024, NumberOfMsgFrames: 1950, NumberOfInitiators: 64, NumberOfTargets: 480

05/03/17-08:20:26 (tRAID): NOTE:  NumberOfIocs: 1, NumberOfEnclosures: 40, NumberOfEnclosurePhys: 38, NumberOfRouteTable: 1024

05/03/17-08:20:26 (tRAID): NOTE:  NumberOfExpanders: 40

05/03/17-08:20:26 (tRAID): WARN:  Allocated for PL: DDR: 153842, CRAM: 89616

05/03/17-08:20:26 (tRAID): WARN:  fast: 89616, DMAAble: 215506

05/03/17-08:20:26 (tRAID): WARN:  CRAM allocated: HW Structs: 0, Total: 89616

05/03/17-08:20:26 (tRAID): NOTE:  iopiConfig: set LED mode A

05/03/17-08:20:26 (tRAID): NOTE:  iopiConfig: set LED mode A

05/03/17-08:20:26 (tRAID): NOTE:  iopiConfig: set LED mode A

05/03/17-08:20:26 (tSasPlTmr): NOTE:  sas::PLITimerMgr::process run, semaphore=47e8058

05/03/17-08:20:26 (tRAID): NOTE:  eel::VirtualDriveEvent allocating 2048 objects

05/03/17-08:20:27 (tRAID): NOTE:  SOD: Instantiation Phase Complete

05/03/17-08:20:27 (tSasPlTmr): NOTE:  iopiConfig: set LED mode A

05/03/17-08:20:27 (IOSched): NOTE:  SAS Expander Added: expDevHandle:x11 enclHandle:x2 numPhys:25 port:2 ioc:0 channel:0

05/03/17-08:20:27 (IOSched): NOTE:  SAS Expander Added: expDevHandle:x12 enclHandle:x3 numPhys:25 port:3 ioc:0 channel:1

05/03/17-08:20:27 (IOSched): NOTE:  SAS Expander Added: expDevHandle:x21 enclHandle:x4 numPhys:38 port:2 ioc:0 channel:0

05/03/17-08:20:27 (IOSched): NOTE:  SAS Expander Added: expDevHandle:x22 enclHandle:x5 numPhys:38 port:3 ioc:0 channel:1

05/03/17-08:20:28 (tSasEvtWkr): NOTE:  Alt controller path up on channel:0 devH:x20 expDevH:x11 phy:16 itn:2

05/03/17-08:20:28 (tSasExpChk): NOTE:  Local Expander Firmware Version: 25.03.54.00

05/03/17-08:20:28 (tRAID): NOTE:  Inter-Controller Communication Channels Opened

05/03/17-08:20:28 (tSasEvtWkr): NOTE:  Alt controller path up on channel:1 devH:x1f expDevH:x12 phy:12 itn:16

05/03/17-08:20:28 (tSasExpChk): NOTE:  Alternate Expander Firmware Version: 25.03.54.00

05/03/17-08:20:29 (IOSched): NOTE:  discoveredEncl: trayId:1 slotCount:12 eli:500c04f21726fe00

05/03/17-08:20:29 (IOSched): NOTE:  discoveredEncl: trayId:1 slotCount:12 eli:500c04f21726fe00

05/03/17-08:20:30 (IOSched): NOTE:  New Initiator: channel: 1, devHandle: x1f, sasAddress: 5782bcb43dbcdf08

05/03/17-08:20:30 (IOSched): NOTE:  New Initiator: channel: 0, devHandle: x20, sasAddress: 5782bcb43dbcdf0c

05/03/17-08:20:30 (tSasInitWkr): NOTE:  Adding partner controller drive side initiator, chan:1 devH:x1f SAS Address:5782bcb43dbcdf08

05/03/17-08:20:30 (tSasInitWkr): NOTE:  New Initiator:  1 - channel:1, devHandle:x1f, SAS Address:5782bcb43dbcdf08

05/03/17-08:20:30 (tSasInitWkr): NOTE:  Adding partner controller drive side initiator, chan:0 devH:x20 SAS Address:5782bcb43dbcdf0c

05/03/17-08:20:30 (tSasInitWkr): NOTE:  New Initiator:  2 - channel:0, devHandle:x20, SAS Address:5782bcb43dbcdf0c

05/03/17-08:20:31 (IOSched): NOTE:  SAS: Opening ICON channel to alt controller on alt channel

05/03/17-08:20:32 (tRAID): NOTE:  LockMgr Role is Slave

05/03/17-08:20:35 (tSasDiscCom): WARN:  SAS: Initial Discovery Complete Time: 31 seconds since last power on/reset, 10 seconds since sas instantiated

05/03/17-08:20:40 (tRAID): NOTE:  WWN baseName 0004d4ae-527cff77 (valid==>SoftRst)

05/03/17-08:20:40 (tRAID): NOTE:  spmEarlyData: Using data from alternate

ServerEngines BladeEngine 2 Firmware Update Utility v2.0.310.144

Copyright 2009 ServerEngines CorpoFound BE card 0x0 at 2.0 bar1-base 0xf0200000 bar2-base 0xf0220000 dev 0x2df2898

flash_rbver = 2.0.38.0

flash_armfwver = 2.300.310.148

Bad File CRC after decompression

ERROR: VKI_READ failed while reading BE_FW from flash

ufi_rbver = 2.0.0.0

ERROR: VKI_READ failed while reading BE_FW from flash

ufi_armfwver = None

Flash on BladeEngine at 02 : 00 does not match UFI SEBE2T1G

05/03/17-08:20:42 (tRAID): WARN:  MTLSE: Flashing BE Firmware at 2:0

05/03/17-08:20:42 (tRAID): NOTE:  Delaying NMI watchdog during flash...

05/03/17-08:20:42 (tRAID): WARN:  MTLSE: Updating BE flash at 2:0tThis may take few minutes...

Bad File CRC after decompression

ERROR: VKI_READ failed while reading BE_FW from flash

No signature found

05/03/17-08:20:43 (tRAID): ERROR: MTLSE: Flash of 2:0 FAILED

05/03/17-08:20:43 (tRAID): PANIC: Flash update failed at 2:0

Stack Trace for tRAID:

0x0025f8a4 vxTaskEntry  +0x5c : sodMain (0, 0)

0x05cf6e60 sodMain      +0x240: sodPreInitialization() ()

0x05cf591c sodPreInitialization()+0x1c : sodEnableHostInterface() ()

0x05cf5694 sodEnableHostInterface()+0x34 : sodLogStartup(void (*)()) ()

0x05cf4bb0 sodLogStartup(void (*)())+0xd0 : 0x064c72e4 ()

0x064c7314 ioni::enableHostInterfaces()+0x34 : ioni::IoniManager::enableHostInterfaceChannels() ()

0x064b3a44 ioni::IoniManager::enableHostInterfaceChannels()+0x1a4: ioni::ChannelData::enableInterface() ()

0x064c1b10 ioni::ChannelData::enableInterface()+0x50 : 0x0202bfe4 ()

0x0202c07c b_isn::IscsiNetworkManager::enableInterface(const ioni::ChannelData *)+0x9c : mtlsebe::Mtl::enableMtlInterface(unsigned long, unsigned int, unsigned int, unsigned long long, int) ()

0x02d7fda0 mtlsebe::Mtl::enableMtlInterface(unsigned long, unsigned int, unsigned int, unsigned long long, int)+0x160: update_be(unsigned long, bool) ()

0x02d762b4 update_be(unsigned long, bool)+0x1f4: _vkiCmnErr__link ()

0x0015a7c4 _vkiCmnErr   +0x104: 0x0015aa00 (0x5a6e6c, 0x2de4888, 0x1dcd810)

0x0015adc8 vkiLogShow   +0x588: psvJobAdd (0x15b840, 0x1dcddc8, 0, 0)

0x00141f44 psvJobAdd    +0x64 : msgQSend ()

0x00404cfc msgQSend     +0x61c: taskUnlock ()

05/03/17-08:20:44 (IOSched): WARN:  channel: 0: Could not get connection

05/03/17-08:20:44 (IOSched): NOTE:  IDR: devH:x20 expDevH:x11 IOCStatus:x8000 IOCLogInfo:x3112010c ioc:0 sasAddr:5782bcb43dbcdf0c

05/03/17-08:20:44 (IOSched): WARN:  channel: 0: Could not get connection

-=<###>=-

And controller is in LOCK state again… I search for that error

“Bad File CRC after decompression

ERROR: VKI_READ failed while reading BE_FW from flash

ufi_rbver = 2.0.0.0

ERROR: VKI_READ failed while reading BE_FW from flash

ufi_armfwver = None”

but can’t find any solution…

Unfortunately support is ended long time ago, and I’m looking for help…

I miss some information, both controllers are with package version:   07.75.28.60

Regards and every help is appreciated.