Acceso a MD3000 perdido

Soporte Servidores Fuera de Garantía

Soporte Servidores Fuera de Garantía
Grupo dedicado a gestionar sus consultas sobre PowerEdge y PowerVault fuera de garantía

Acceso a MD3000 perdido

Esta pregunta ha sido respondida por Dell-Lizbeth Perea

Buenas tardes,

Tras llevar a cabo el reemplazo de una controladora en fallo de nuestro almacenamiento MD3000, hemos perdido por completo el acceso a la gestión y el volúmen a través del software Dell Modular Disk Storage manager.

Cuando arranca el array, llegamos a hacer ping a la interfaz de gestión de una de las controladoras durante un tiempo, hasta que llega a este punto en el arranque (log de consola):

Exception: Data Abort

cpsr:  60000013   pc:  0x

Antes de esto se ve que está intentando reiniciar el software en la controladora constantemente:

09/20/17-10:14:22 (GMT) (tRAID): NOTE:  QLProcessSystemError: Restart RISC

09/20/17-10:14:22 (GMT) (tRAID): ERROR: QLGetFwState: MBOX_CMD_GET_FW_STATE fail

ed.  Stat f000

09/20/17-10:14:22 (GMT) (tRAID): NOTE:  QLRebootTimer: Status after Get FW State

4543

09/20/17-10:14:22 (GMT) (tRAID): NOTE:  QLRebootTimer: QLGetFwState failed

09/20/17-10:14:23 (GMT) (tRAID): NOTE:  QLStartFw: Downloading Driver's FW image

03.00.01.47 from 0058c2e0 4c0c8 bytes , result 0

09/20/17-10:14:50 (GMT) (tRAID): WARN:  QLMailboxCommand: Cmd = 0069, completion

timeout

09/20/17-10:14:50 (GMT) (tRAID): WARN:  QLMailboxCommand: command completion tim

eout, cmd = 0x69

09/20/17-10:14:51 (GMT) (tRAID): NOTE:  Qlogic coredump file written to 'H2BFR4J

:/tmp/QLogic_Coredump_port_0_H2BFR4J',rc 204E50, expected 204E50

09/20/17-10:14:51 (GMT) (tRAID): WARN:  Qlogic coredump file write failed.fclose

returned -1

09/20/17-10:14:51 (GMT) (tRAID): NOTE:  QLProcessSystemError: Restart RISC

09/20/17-10:14:51 (GMT) (tRAID): ERROR: QLGetFwState: MBOX_CMD_GET_FW_STATE fail

ed.  Stat f000

09/20/17-10:14:51 (GMT) (tRAID): NOTE:  QLRebootTimer: Status after Get FW State

4543

09/20/17-10:14:51 (GMT) (tRAID): NOTE:  QLRebootTimer: QLGetFwState failed

09/20/17-10:14:52 (GMT) (tRAID): WARN:  QLStartAdapter: ControllerErrorCount exc

eeds threshold.

09/20/17-10:14:52 (GMT) (tRAID): ERROR: QLInitializeDevice: QLStartAdapter faile

d

09/20/17-10:14:52 (GMT) (tRAID): ERROR: QLAddDevice: controller/device/chip init

ialization failed.

09/20/17-10:14:52 (GMT) (tRAID): ERROR: qlgEnableHostInterface: QLInitializeDevi

ce failed.

Adjunto todo el log de arranque:

ÿ

-=<###>=-

Attaching interface lo0... done

Adding 9767 symbols for standalone.

Error

09/20/17-10:11:21 (GMT) (tRootTask): NOTE:  I2C transaction returned 0x0423fe00

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

5900 Ethernet 91c111 #1

    01 Register read                                               Passed

    02 Register test                                               Passed

3A00 NAND Flash

    06 Bad Blocks Test                                             Passed

2310 Application Accelerator Unit

    01 AAU Register Test                                           Passed

6D00 LSI SAS 1068 IOC--Base Board

    01 IOC Register Read Test                                      Passed

    02 IOC Register Address Lines Test                             Passed

    03 IOC Register Data Lines Test                                Passed

6F01 QLOGIC EP4032 CHIP 0

    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.

Current date: 09/20/17  time: 02:10:07

Send <BREAK> for Service Interface or baud rate change

09/20/17-10:11:40 (GMT) (tRAID): NOTE:  Set Powerup State

09/20/17-10:11:40 (GMT) (tRAID): NOTE:  SOD Sequence is Normal, 0

09/20/17-10:11:40 (GMT) (tRAID): NOTE:  SOD: removed SAS host from index 0

09/20/17-10:11:40 (GMT) (tRAID): NOTE:  In iscsiIOQLIscsiInitDq.  iscsiIoFstrBas

e = 0x0

09/20/17-10:11:40 (GMT) (tRAID): NOTE:  Turning on tray summary fault LED

09/20/17-10:11:42 (GMT) (tRAID): NOTE:  SYMBOL: SYMbolAPI registered.

09/20/17-10:11:42 (GMT) (tRAID): NOTE:  lost persistent dq data because buffer w

as modified or size changed.

esmc0: LinkUp event

09/20/17-10:11:43 (GMT) (tNetCfgInit): NOTE:  Network Ready

09/20/17-10:11:46 (GMT) (tRAID): NOTE:  Initiating Drive channel: ioc:0 bringup

09/20/17-10:11:48 (GMT) (tRAID): NOTE:  IOC Firmware Version: 00-24-63-00

09/20/17-10:11:56 (GMT) (tSasEvtWkr): NOTE:  sasIocPhyUp: chan:1 phy:0 prevNumAc

tivePhys:2 numActivePhys:2

09/20/17-10:11:56 (GMT) (tSasEvtWkr): NOTE:  sasIocPhyUp: chan:1 phy:1 prevNumAc

tivePhys:2 numActivePhys:2

09/20/17-10:12:06 (GMT) (tRAID): NOTE:  IonMgr: Drive Interface Enabled

09/20/17-10:12:06 (GMT) (tRAID): NOTE:  SOD: Instantiation Phase Complete

09/20/17-10:12:06 (GMT) (tRAID): WARN:  No attempt made to open Inter-Controller

Communication Channels

09/20/17-10:12:06 (GMT) (tRAID): NOTE:  Failing The Alternate Controller

09/20/17-10:12:06 (GMT) (tRAID): WARN:  Alt Ctl Reboot:

                               Reboot CompID: 0x401

                               Reboot reason: 0x6

                               Reboot reason extra: 0x0

09/20/17-10:12:06 (GMT) (tRAID): NOTE:  holding alt ctl in reset

09/20/17-10:12:06 (GMT) (tRAID): NOTE:  LockMgr Role is Master

09/20/17-10:12:06 (GMT) (tRAID): WARN:  FBM:validateSubModel: Exception - Alt co

ntroller not ready

09/20/17-10:12:06 (GMT) (tSasDiscCom): NOTE:  SAS Discovery complete task spawne

d

09/20/17-10:12:07 (GMT) (tRAID): NOTE:  spmEarlyData: No data available

09/20/17-10:12:07 (GMT) (sasCheckExpanderSet): NOTE:  Expander Firmware Version:

0116-e05c

09/20/17-10:12:07 (GMT) (sasCheckExpanderSet): NOTE:  Expander SAS address: Hi =

x5a4badb4 Low = x4e0f0f10

09/20/17-10:12:12 (GMT) (tSasDiscCom): WARN:  SAS: Initial Discovery Complete Ti

me: 30 seconds

09/20/17-10:12:12 (GMT) (tRAID): NOTE:  WWN baseName 0004a4ba-db4e0c98 (valid==>

SigMatch)

09/20/17-10:12:12 (GMT) (tRAID): NOTE:  IonMgr: Host Interface Enabled

09/20/17-10:12:12 (GMT) (tRAID): NOTE:  SOD: Pre-Initialization Phase Complete

09/20/17-10:12:13 (GMT) (tRAID): WARN:  BID: initialize(): Power latched!

09/20/17-10:12:23 (GMT) (tRAID): NOTE:  ACS: Icon ping to alternate failed: -2,

resp: 0

09/20/17-10:12:23 (GMT) (tRAID): NOTE:  ACS: autoCodeSync(): Process start. Comm

Mode: 0, Status: 0

09/20/17-10:12:23 (GMT) (tRAID): WARN:  ACS: autoCodeSync(): Skipped since alt n

ot communicating.

09/20/17-10:12:23 (GMT) (tRAID): NOTE:  SOD: Code Synchronization Initialization

Phase Complete

09/20/17-10:12:23 (GMT) (tRAID): NOTE:  Caught IconSendInfeasibleException Error

in iop::requestAltIopDelay

09/20/17-10:12:24 (GMT) (tRAID): NOTE:  CheckInMonitor: Check-in failed (IconSen

dInfeasibleException Error)

09/20/17-10:12:24 (GMT) (NvpsPersistentSyncM): NOTE:  NVSRAM Persistent Storage

updated successfully

09/20/17-10:12:24 (GMT) (tRAID): NOTE:  USM Mgr initialization complete with 0 r

ecords.

09/20/17-10:12:24 (GMT) (tRAID): WARN:  Received IconSendInfeasibleException Err

or adding small edr records from alt controller

09/20/17-10:12:25 (GMT) (tRAID): WARN:  spm: unable to exchange features, assumi

ng none

09/20/17-10:12:25 (GMT) (tRAID): NOTE:  SPM acquireObjects exception: IconSendIn

feasibleException Error

09/20/17-10:12:25 (GMT) (tRAID): NOTE:  DBRead               0.176 secs

09/20/17-10:12:25 (GMT) (tRAID): NOTE:  sas: Peering Disabled (Alt Unavailable)

09/20/17-10:12:26 (GMT) (tRAID): NOTE:  QLStartFw: Downloading Driver's FW image

03.00.01.47 from 0058c2e0 4c0c8 bytes , result 0

09/20/17-10:12:53 (GMT) (tRAID): WARN:  QLMailboxCommand: Cmd = 0069, completion

timeout

09/20/17-10:12:53 (GMT) (tRAID): WARN:  QLMailboxCommand: command completion tim

eout, cmd = 0x69

09/20/17-10:12:54 (GMT) (tRAID): NOTE:  Qlogic coredump file written to 'H2BFR4J

:/tmp/QLogic_Coredump_port_0_H2BFR4J',rc 204E50, expected 204E50

09/20/17-10:12:54 (GMT) (tRAID): WARN:  Qlogic coredump file write failed.fclose

returned -1

09/20/17-10:12:54 (GMT) (tRAID): NOTE:  QLProcessSystemError: Restart RISC

09/20/17-10:12:54 (GMT) (tRAID): ERROR: QLGetFwState: MBOX_CMD_GET_FW_STATE fail

ed.  Stat f000

09/20/17-10:12:54 (GMT) (tRAID): NOTE:  QLRebootTimer: Status after Get FW State

4543

09/20/17-10:12:54 (GMT) (tRAID): NOTE:  QLRebootTimer: QLGetFwState failed

09/20/17-10:12:55 (GMT) (tRAID): NOTE:  QLStartFw: Downloading Driver's FW image

03.00.01.47 from 0058c2e0 4c0c8 bytes , result 0

09/20/17-10:13:23 (GMT) (tRAID): WARN:  QLMailboxCommand: Cmd = 0069, completion

timeout

09/20/17-10:13:23 (GMT) (tRAID): WARN:  QLMailboxCommand: command completion tim

eout, cmd = 0x69

09/20/17-10:13:23 (GMT) (tRAID): NOTE:  Qlogic coredump file written to 'H2BFR4J

:/tmp/QLogic_Coredump_port_0_H2BFR4J',rc 204E50, expected 204E50

09/20/17-10:13:23 (GMT) (tRAID): WARN:  Qlogic coredump file write failed.fclose

returned -1

09/20/17-10:13:23 (GMT) (tRAID): NOTE:  QLProcessSystemError: Restart RISC

09/20/17-10:13:23 (GMT) (tRAID): ERROR: QLGetFwState: MBOX_CMD_GET_FW_STATE fail

ed.  Stat f000

09/20/17-10:13:23 (GMT) (tRAID): NOTE:  QLRebootTimer: Status after Get FW State

4543

09/20/17-10:13:23 (GMT) (tRAID): NOTE:  QLRebootTimer: QLGetFwState failed

09/20/17-10:13:25 (GMT) (tRAID): NOTE:  QLStartFw: Downloading Driver's FW image

03.00.01.47 from 0058c2e0 4c0c8 bytes , result 0

09/20/17-10:13:52 (GMT) (tRAID): WARN:  QLMailboxCommand: Cmd = 0069, completion

timeout

09/20/17-10:13:52 (GMT) (tRAID): WARN:  QLMailboxCommand: command completion tim

eout, cmd = 0x69

09/20/17-10:13:53 (GMT) (tRAID): NOTE:  Qlogic coredump file written to 'H2BFR4J

:/tmp/QLogic_Coredump_port_0_H2BFR4J',rc 204E50, expected 204E50

09/20/17-10:13:53 (GMT) (tRAID): WARN:  Qlogic coredump file write failed.fclose

returned -1

09/20/17-10:13:53 (GMT) (tRAID): NOTE:  QLProcessSystemError: Restart RISC

09/20/17-10:13:53 (GMT) (tRAID): ERROR: QLGetFwState: MBOX_CMD_GET_FW_STATE fail

ed.  Stat f000

09/20/17-10:13:53 (GMT) (tRAID): NOTE:  QLRebootTimer: Status after Get FW State

4543

09/20/17-10:13:53 (GMT) (tRAID): NOTE:  QLRebootTimer: QLGetFwState failed

09/20/17-10:13:54 (GMT) (tRAID): NOTE:  QLStartFw: Downloading Driver's FW image

03.00.01.47 from 0058c2e0 4c0c8 bytes , result 0

09/20/17-10:14:21 (GMT) (tRAID): WARN:  QLMailboxCommand: Cmd = 0069, completion

timeout

09/20/17-10:14:21 (GMT) (tRAID): WARN:  QLMailboxCommand: command completion tim

eout, cmd = 0x69

09/20/17-10:14:22 (GMT) (tRAID): NOTE:  Qlogic coredump file written to 'H2BFR4J

:/tmp/QLogic_Coredump_port_0_H2BFR4J',rc 204E50, expected 204E50

09/20/17-10:14:22 (GMT) (tRAID): WARN:  Qlogic coredump file write failed.fclose

returned -1

09/20/17-10:14:22 (GMT) (tRAID): NOTE:  QLProcessSystemError: Restart RISC

09/20/17-10:14:22 (GMT) (tRAID): ERROR: QLGetFwState: MBOX_CMD_GET_FW_STATE fail

ed.  Stat f000

09/20/17-10:14:22 (GMT) (tRAID): NOTE:  QLRebootTimer: Status after Get FW State

4543

09/20/17-10:14:22 (GMT) (tRAID): NOTE:  QLRebootTimer: QLGetFwState failed

09/20/17-10:14:23 (GMT) (tRAID): NOTE:  QLStartFw: Downloading Driver's FW image

03.00.01.47 from 0058c2e0 4c0c8 bytes , result 0

09/20/17-10:14:50 (GMT) (tRAID): WARN:  QLMailboxCommand: Cmd = 0069, completion

timeout

09/20/17-10:14:50 (GMT) (tRAID): WARN:  QLMailboxCommand: command completion tim

eout, cmd = 0x69

09/20/17-10:14:51 (GMT) (tRAID): NOTE:  Qlogic coredump file written to 'H2BFR4J

:/tmp/QLogic_Coredump_port_0_H2BFR4J',rc 204E50, expected 204E50

09/20/17-10:14:51 (GMT) (tRAID): WARN:  Qlogic coredump file write failed.fclose

returned -1

09/20/17-10:14:51 (GMT) (tRAID): NOTE:  QLProcessSystemError: Restart RISC

09/20/17-10:14:51 (GMT) (tRAID): ERROR: QLGetFwState: MBOX_CMD_GET_FW_STATE fail

ed.  Stat f000

09/20/17-10:14:51 (GMT) (tRAID): NOTE:  QLRebootTimer: Status after Get FW State

4543

09/20/17-10:14:51 (GMT) (tRAID): NOTE:  QLRebootTimer: QLGetFwState failed

09/20/17-10:14:52 (GMT) (tRAID): WARN:  QLStartAdapter: ControllerErrorCount exc

eeds threshold.

09/20/17-10:14:52 (GMT) (tRAID): ERROR: QLInitializeDevice: QLStartAdapter faile

d

09/20/17-10:14:52 (GMT) (tRAID): ERROR: QLAddDevice: controller/device/chip init

ialization failed.

09/20/17-10:14:52 (GMT) (tRAID): ERROR: qlgEnableHostInterface: QLInitializeDevi

ce failed.

09/20/17-10:14:52 (GMT) (tRAID): NOTE:  ****************************************

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

09/20/17-10:14:52 (GMT) (tRAID): NOTE:    QLogic Target Application, Version 2.0

1.08 6-13-2005 (W2K)

09/20/17-10:14:52 (GMT) (tRAID): NOTE:          iSCSI Target Application

09/20/17-10:14:52 (GMT) (tRAID): NOTE:   ***************************************

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

Exception: Data Abort

cpsr:  60000013   pc:  0x

Por favor, ¿podría alguien ayudarme? Necesito recuperar el acceso a nuestro vdisk para hacer un backup.

Gracias por adelantado. Saludos,

Javier

Respuesta comprobada
  • Hola,

     

                    Gracias por enviarnos el Service Tag.

                    Desde el portal fuera de garantía le podemos facilitar información que tengamos disponible en línea que pueda resultarle útil para resolver el problema:

     

    Manuales y Documentación

    Artículos de soporte de Dell PowerVault
                   

                    Si puede por favor confirmarnos si consigue resolverlo o si necesita de nuestra asistencia. Dejamos el post abierto para cualquier otro cliente también pueda ayudarle.

     

    Un saludo

Todas las respuestas
  • Estimado cliente,

     

                    Gracias por contactarnos, para que Dell pueda gestionar su consulta necesitamos el Service Tag de su equipo, el cual le hemos solicitado por e-mail.

                    El post sigue abierto para que cualquier otro cliente también pueda darle una respuesta.

                   

    Saludos

  • Hola,

     

                    Gracias por enviarnos el Service Tag.

                    Desde el portal fuera de garantía le podemos facilitar información que tengamos disponible en línea que pueda resultarle útil para resolver el problema:

     

    Manuales y Documentación

    Artículos de soporte de Dell PowerVault
                   

                    Si puede por favor confirmarnos si consigue resolverlo o si necesita de nuestra asistencia. Dejamos el post abierto para cualquier otro cliente también pueda ayudarle.

     

    Un saludo