Dell Unity: Os arrays do Dell Unity não devem ser conectados usando a porta SAS no DPE.

Resumo: Se dois (2) arrays Dell Unity estiverem conectados usando a porta SAS no DPE (Disk Processor Enclosure), poderá ocorrer indisponibilidade de dados e perda de dados.

Este artigo aplica-se a Este artigo não se aplica a Este artigo não está vinculado a nenhum produto específico. Nem todas as versões do produto estão identificadas neste artigo.
Confira outros recursos

Sintomas

  • Se dois (2) arrays do Dell Unity estiverem conectados pela porta SAS no DPE, um DPE do Unity (Unity A) acha que o outro DPE do Unity (Unity B) é um DAE. O Unity A zerará o disco no Unity B.

 

  • O Unity B pode entrar em pane e reinicializar no modo de serviço com o seguinte: Rescue Reason: 0x0b00
Rescue reason for code 0x0b00 - There is a problem with the system software on this Storage Processor (BOOTFL). 
To attempt to correct this problem, first run Data Collection, and then try the following in order: 
Check all cables, reboot each SP, and reimage each Storage Processor (SP). 
If this does not resolve the issue, contact your service provider.
SP Service Hint Code: 0xFC0B0203 - Could not load mirror driver
Troubleshooting Steps Performed:

 

 

  •  Mensagens de "slot errado" podem ser observadas em /EMC/C4Core/log/c4_safe_ktrace.log
14:11:08 service@FNXXXXXX spa:~/user# cat /EMC/C4Core/log/c4_safe_ktrace.log |grep -i 'wrong'
2025/07/31-23:20:43.860481 ~~~~ 7FB93D53D700 std:WARN SERV DBS 100C0 : MIR: MirrorReadMcrFruSignature: Wrong slot. Want: 0_0_0 Found: 0_1_0
2025/07/31-23:20:43.863842 ~~~~ 7FB93D53D700 std:WARN SERV DBS 100C0 : MIR: MirrorReadMcrFruSignature: Wrong slot. Want: 0_0_1 Found: 0_1_1
2025/07/31-23:20:43.866140 ~~~~ 7FB93D53D700 std:WARN SERV DBS 100C0 : MIR: MirrorReadMcrFruSignature: Wrong slot. Want: 0_0_2 Found: 0_1_2
2025/07/31-23:20:43.885914 ~~~~ 7FB93D53D700 std:WARN SERV DBS 100C0 : MIR: MirrorReadMcrFruSignature: Wrong slot. Want: 0_0_3 Found: 0_1_3
2025/07/31-23:21:44.088368 ~~~~ 7F01FE39E700 std:WARN SERV DBS 100C0 : MIR: MirrorReadMcrFruSignature: Wrong slot. Want: 0_0_0 Found: 0_1_0
2025/07/31-23:21:44.091689 ~~~~ 7F01FE39E700 std:WARN SERV DBS 100C0 : MIR: MirrorReadMcrFruSignature: Wrong slot. Want: 0_0_1 Found: 0_1_1
2025/07/31-23:21:44.093958 ~~~~ 7F01FE39E700 std:WARN SERV DBS 100C0 : MIR: MirrorReadMcrFruSignature: Wrong slot. Want: 0_0_2 Found: 0_1_2
2025/07/31-23:21:44.113774 ~~~~ 7F01FE39E700 std:WARN SERV DBS 100C0 : MIR: MirrorReadMcrFruSignature: Wrong slot. Want: 0_0_3 Found: 0_1_3
2025/07/31-23:22:50.870445 ~~~~ 7F9B11D9E700 std:WARN SERV DBS 100C0 : MIR: MirrorReadMcrFruSignature: Wrong slot. Want: 0_0_0 Found: 0_1_0
2025/07/31-23:22:50.873760 ~~~~ 7F9B11D9E700 std:WARN SERV DBS 100C0 : MIR: MirrorReadMcrFruSignature: Wrong slot. Want: 0_0_1 Found: 0_1_1
2025/07/31-23:22:50.875969 ~~~~ 7F9B11D9E700 std:WARN SERV DBS 100C0 : MIR: MirrorReadMcrFruSignature: Wrong slot. Want: 0_0_2 Found: 0_1_2
2025/07/31-23:22:50.890182 ~~~~ 7F9B11D9E700 std:WARN SERV DBS 100C0 : MIR: MirrorReadMcrFruSignature: Wrong slot. Want: 0_0_3 Found: 0_1_3

 

 

  • Unidades 0_0_0, 0_0_1, 0_0_2, 0_0_3 relatadas como unidades inválidas em /EMC/C4Core/log/start_c4.log
14:11:08 service@FNXXXXXX spa:~/user# cat /EMC/C4Core/log/start_c4.log
2025-07-31 23:20:38.835 ===== reinit_if_needed =====
2025-07-31 23:20:39.200 ===== bringup_backend =====
2025-07-31 23:20:39.741 Loading mirror driver
2025-07-31 23:20:44.980 CM(sep)::start failed: Error: Command failed: -o execute -a 52609 – -o module_start -m sep: : NON_SPECIFIC at /EMC/csx/ubin64/csx_ctl.pl line 210.
2025-07-31 23:20:48.302 Shutting down backend SAS ports...
2025-07-31 23:20:52.354 Shut down backend SAS ports COMPLETED.
2025-07-31 23:21:02.119 MIR: system drive: 0_0_0 and 0_0_1 and 0_0_2 and 0_0_3 are invalid drives
2025-07-31 23:21:02.142 Three or more system drives {0_0_0,0_0_1,0_0_2,0_0_3}
are invalid.
2025-07-31 23:21:02.195 Bringing up the CSX infrastructure (timeout: 60, debug: 0)
2025-07-31 23:21:02.290 lst 0xb0000000:lsz 0x7d58000:ld 0xb7d57fff:hst 0x260000000:hsz 0xde0000000:hd0x103fffffff
2025-07-31 23:21:05.480 Starting the platform container.
2025-07-31 23:21:07.333 Bring up the GMS Server.
2025-07-31 23:21:07.410 Detected Memory Size (dmidecode): <65536>MB.
2025-07-31 23:21:08.293 Bolero_X1
2025-07-31 23:21:45.207 CM(sep)::start failed: Error: Command failed: -o execute -a 33971 – -o module_start -m sep: : NON_SPECIFIC at /EMC/csx/ubin64/csx_ctl.pl line 210.
2025-07-31 23:21:45.360 Increment the boot counter and go straight into Service Mode

Causa

Se dois (2) arrays do Dell Unity estiverem conectados usando a porta SAS no DPE, um DPE do Unity (Unity A) acha que o outro DPE do Unity (Unity B) é um DAE. O Unity A zerará o disco no Unity B.

Resolução

Não conecte dois (2) arrays Dell Unity usando a porta SAS no DPE. 
Se eles já estiverem conectados dessa forma, será necessário fazer uma reinicialização de fábrica.
Não há nada que a Engenharia possa fazer para intervir. 

 

 

 

 

Produtos afetados

Dell EMC Unity 300F, Dell EMC Unity 350F, Dell EMC Unity 400, Dell EMC Unity 400F, Dell EMC Unity 450F, Dell EMC Unity 500, Dell EMC Unity 500F, Dell EMC Unity 550F, Dell EMC Unity 600, Dell EMC Unity 600F

Produtos

Dell EMC Unity, Dell Unity 450F DC, Dell Unity 300, Dell Unity 300 DC, Dell Unity 350F DC, Dell EMC Unity XT 380, Dell EMC Unity XT 380F, Dell Unity 400 DC, Dell EMC Unity XT 480, Dell EMC Unity XT 480F, Dell EMC Unity 650F, Dell EMC Unity XT 680 , Dell EMC Unity XT 680F, Dell EMC Unity XT 880, Dell EMC Unity XT 880F, Dell EMC Unity Family |Dell EMC Unity All Flash, Dell EMC Unity Hybrid ...
Propriedades do artigo
Número do artigo: 000351789
Tipo de artigo: Solution
Último modificado: 22 jan. 2026
Versão:  3
Encontre as respostas de outros usuários da Dell para suas perguntas.
Serviços de suporte
Verifique se o dispositivo está coberto pelos serviços de suporte.