Dell Unity：不應使用 DPE 上的 SAS 連接埠連接 Dell Unity 陣列。

摘要: 如果使用磁碟處理器機櫃 （DPE） 上的 SAS 連接埠連接兩 （2） 個 Dell Unity 陣列，可能會發生資料無法使用和資料遺失的情況。

本文章適用於 本文章不適用於 本文無關於任何特定產品。 本文未識別所有產品版本。
查看其他資源

症狀

  • 如果兩 （2） 個 Dell Unity 陣列透過 DPE 上的 SAS 連接埠連接在一起，其中一個 Unity DPE （Unity A） 會認為另一個 Unity DPE （Unity B） 是 DAE。Unity A 會將 Unity B 上的磁碟清零。

 

  • 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

原因

如果兩 （2） 個 Dell Unity 陣列使用 DPE 上的 SAS 連接埠連接在一起，其中一個 Unity DPE （Unity A） 會認為另一個 Unity DPE （Unity B） 是 DAE。Unity A 會將 Unity B 上的磁碟清零。

解析度

請勿使用 DPE 上的 SAS 連接埠連接兩 （2） 個 Dell Unity 陣列。
如果它們已以這種方式連接，則必須進行原廠重新初始化。
工程部門無能為力。 

 

 

 

 

受影響的產品

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

產品

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 ...
文章屬性
文章編號: 000351789
文章類型: Solution
上次修改時間: 22 1月 2026
版本:  3
向其他 Dell 使用者尋求您問題的答案
支援服務
檢查您的裝置是否在支援服務的涵蓋範圍內。