R5300 G6 reports SATA All-in-one cable connection error

2026-01-18 14:47:00 Published
  • 0 Followed
  • 0Collected ,7Browsed

Network Topology

The drive configuration is a 12LFF backplane (0302A6VS), with the P460 card connected to two F0/F1 SATA SSDs, and F8-F11 being four NVMe drives.

Problem Description

Customer reported batch repair for about 10 R5300 G6 servers with drive All-in-one cable alarm in SEL: Configuration Error-Incorrect cable connected / Incorrect interconnection---Incorrect SATA cable connection to the system board. No actual usage issues found.

Process Analysis

1. The customer provided logs from two devices, revealing an Incorrect SATA cable connection alarm after upgrading the HDM version around 9:40 on November 15. Suspected to be a false positive.

alarm message:

1821         Info        NA   NA   NA   From BMC       2024-11-15 09:41:33 UTC+08:00  Reboot Cause: [BMC] [warm reset] BMC occurred warm reset because of updating BMC. 2024-11-15 09:40:41

1830         Minor     Cable / Interconnect       Cable       Asserted  From BMC       2024-11-15 09:41:43 UTC+08:00       Configuration Error-Incorrect cable connected / Incorrect interconnection---Incorrect SATA cable connection to the system board     

1877         Info        NA   NA   NA   From BMC       2024-11-15 09:49:24 UTC+08:00  Reboot Cause: [BMC][cold reset] BMC occurred cold reset because of resetting BMC. 2024-11-15 09:48:44 UTC+8

1883         Minor     Cable / Interconnect       Cable       Asserted  From BMC       2024-11-15 09:49:30 UTC+08:00       Configuration Error-Incorrect cable connected / Incorrect interconnection---Incorrect SATA cable connection to the system board

Firmware upgrade records:

%# 2024-11-15 09:39:49.771 UTC+08:00 HDM210235A4GP********1S [BMC.update] 517 [SUCCESS]: [root][redfish][10.x.x.x] Update space preparation succeeded.

%# 2024-11-15 09:39:54.845 UTC+08:00 HDM210235A4GP********1S [BMC.update] 517 [SUCCESS]: [root][redfish][10.x.x.x] Issued the update verification command successfully.

%# 2024-11-15 09:40:07.254 UTC+08:00 HDM210235A4GP********1S [BMC.update] 517 [SUCCESS]: [root][redfish][10.x.x.x] Issued the update command successfully.

%# 2024-11-15 09:40:10.418 UTC+08:00 HDM210235A4GP********1S [BMC.update] 2667 [SUCCESS]: [root][redfish][10.x.x.x] Issued upgrade configuration. Module: HDM; Conf: Retain(Primary).

%# 2024-11-15 09:41:45.299 UTC+08:00 HDM210235A4GP********1S [BMC.update] 710 [SUCCESS]: [root][redfish][10.x.x.x] Module: HDM; Location: Primary; Model: R5300 G6; Version: 2.03 -> 2.08; Update result: Succeeded.

%# 2024-11-15 09:51:41.206 UTC+08:00 HDM210235A4GP********1S [BMC.update] 517 [SUCCESS]: [root][redfish][10.x.x.x] Update space preparation succeeded.

%# 2024-11-15 09:51:41.711 UTC+08:00 HDM210235A4GP********1S [BMC.update] 517 [SUCCESS]: [root][redfish][10.x.x.x] Issued the update verification command successfully.

%# 2024-11-15 09:51:48.275 UTC+08:00 HDM210235A4GP********1S [BMC.update] 517 [SUCCESS]: [root][redfish][10.x.x.x] Issued the update command successfully.

%# 2024-11-15 09:51:49.783 UTC+08:00 HDM210235A4GP********1S [BMC.update] 3642 [SUCCESS]: [root][redfish][10.x.x.x] Issued upgrade configuration. Module: BIOS; Conf: Retain(BIOS and ME).

%# 2024-11-15 10:13:10.568 UTC+08:00 HDM210235A4GP********1S [BMC.update] 710 [SUCCESS]: [root][redfish][10.x.x.x] Module: BIOS; Location: BIOS; Model: R5300 G6; Version: 6.00.25 -> 6.10.40; Update result: Succeeded.

 

%# 2024-11-15 10:13:10.593 UTC+08:00 HDM210235A4GP********1S [BMC.update] 710 [SUCCESS]: [root][redfish][10.x.x.x] Module: BIOS; Location: ME; Model: R5300 G6; Version: 6.00.25 -> 6.10.40; Update result: Succeeded.

2. The CPLD version is V005, and the faulty version is V004; the Release Notes for V005 indicate that this issue has been resolved. Trigger condition: the error occurs only with specific machine configurations. In V004, there is a probabilistic false positive in the logic loop detection, and the All-in-one cable alarm detection log is reported only once when the BMC starts up and not repeated afterward. After an on-site BMC upgrade, the HDM reboots, at which point the alarm is triggered.

Solution

Upgrade CPLD version to V005 or above.

Please rate this case:   
0 Comments

No Comments

Add Comments: