Dell Unity: DPE의 SAS 포트를 사용하여 Dell Unity 어레이를 연결해서는 안 됩니다.

Summary: DPE(Disk Processor Enclosure)의 SAS 포트를 사용하여 두(2) 개의 Dell Unity 어레이를 함께 연결하면 데이터를 사용할 수 없고 데이터가 손실될 수 있습니다.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

  • 두(2) 개의 Dell Unity 어레이가 DPE의 SAS 포트에 의해 함께 연결된 경우 하나의 Unity DPE(Unity A)는 다른 Unity DPE(Unity B)를 DAE로 간주합니다. Unity A는 Unity B에서 디스크를 0으로 만듭니다.

 

  • Unity B는 패닉이 발생하여 다음을 사용하여 서비스 모드로 재부팅될 수 있습니다. 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:

 

 

  •  다음에서 "잘못된 슬롯" 메시지를 확인할 수 있습니다. /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

 

 

  • 드라이브 0_0_0, 0_0_1, 0_0_2, 0_0_3이 /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

Cause

두(2) 개의 Dell Unity 어레이가 DPE의 SAS 포트를 사용하여 함께 연결된 경우 하나의 Unity DPE(Unity A)는 다른 Unity DPE(Unity B)를 DAE로 간주합니다. Unity A는 Unity B에서 디스크를 0으로 만듭니다.

Resolution

DPE의 SAS 포트를 사용하여 두(2) 개의 Dell Unity 어레이를 함께 연결하지 마십시오. 
이미 이러한 방식으로 연결된 경우 출고 시 초기화를 수행해야 합니다.
엔지니어링이 개입할 수 있는 방법은 없습니다. 

 

 

 

 

Affected Products

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

Products

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 ...
Article Properties
Article Number: 000351789
Article Type: Solution
Last Modified: 19 Sep 2025
Version:  2
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.