If its able to boot, data would have to be traveling through that cable. The first thing I would try is clearing the hardware logs and confirming that all firmware is up to date. If the issue persists after that, there may be an underlying problem, but I would treat as a reporting issue for now. The easiest place to clear the log in question would be from the iDRAC at Overview > Logs > System Event Log, then scroll to the bottom and clear it.
The server boots on a SSD that is connected to a SATA port (OD caddy) so no data goes trough the SAS Cable. On any case I will clean the logs connecting to Idrac and will see..
I just did the log clear procedure on Idrac, and re-check the fit of the SAS cables at the back plane and at the connector on the motherboard. Still having the same message. The controller is being recognized by the OS but at boot time the message is on the splash screen (right before the Network Remote Boot option) but now is not appearing at the LCD Display so no yellow lights presents.
Can a lower memory voltage attempt blow the SAS cable but not the controller? Is this possible?
With where we're at now, I'm not sure we can continue much further without replacement parts. This is normally where I'd ask about any spare parts you have on hand, or go ahead and start making replacements. If you have another backplane and SAS cable to test with, I'd recommend it.
As for memory voltage blowing the SAS controller, I haven't seen any schematics, so I can't say for sure. I'm not sure how memory voltage on the board would affect voltage on the PERC though, since they'd be running off different lines and the server supports both 1.5v and 1.35v memory.
Dell-DylanJ
4 Operator
•
2.9K Posts
0
May 2nd, 2019 12:00
If its able to boot, data would have to be traveling through that cable. The first thing I would try is clearing the hardware logs and confirming that all firmware is up to date. If the issue persists after that, there may be an underlying problem, but I would treat as a reporting issue for now. The easiest place to clear the log in question would be from the iDRAC at Overview > Logs > System Event Log, then scroll to the bottom and clear it.
silca80
9 Posts
0
May 2nd, 2019 22:00
Dylan, thanks for your answer.
The server boots on a SSD that is connected to a SATA port (OD caddy) so no data goes trough the SAS Cable. On any case I will clean the logs connecting to Idrac and will see..
Thanks in advance..
Dell-DylanJ
4 Operator
•
2.9K Posts
0
May 3rd, 2019 07:00
If that's the case, I'd be looking at either the connectors on the PERC, the SAS cabling, or the backplane, as the source of this error.
silca80
9 Posts
0
May 4th, 2019 09:00
Dylan, thanks for your time.
I just did the log clear procedure on Idrac, and re-check the fit of the SAS cables at the back plane and at the connector on the motherboard. Still having the same message. The controller is being recognized by the OS but at boot time the message is on the splash screen (right before the Network Remote Boot option) but now is not appearing at the LCD Display so no yellow lights presents.
Can a lower memory voltage attempt blow the SAS cable but not the controller? Is this possible?
Regards
Dell-DylanJ
4 Operator
•
2.9K Posts
0
May 6th, 2019 07:00
With where we're at now, I'm not sure we can continue much further without replacement parts. This is normally where I'd ask about any spare parts you have on hand, or go ahead and start making replacements. If you have another backplane and SAS cable to test with, I'd recommend it.
As for memory voltage blowing the SAS controller, I haven't seen any schematics, so I can't say for sure. I'm not sure how memory voltage on the board would affect voltage on the PERC though, since they'd be running off different lines and the server supports both 1.5v and 1.35v memory.