Unsolved
This post is more than 5 years old
2 Posts
0
1128
May 30th, 2017 14:00
DSM SA is causing system crash
Have a T610 with H700 controller. About 6 months ago it had HD failure. I installed the DSM openmange product to get more info on the hardware. The HD was replaced and things seemed fine. Recently noticed that on reboot the server would get stuck rebooting with a blue screen. Sometime it come after a boots, other times it was hours. Checked the logs and found it was getting a PCIE fatal bus error couple of minutes after windows loaded. The error points to the PERC controller, only card installed.
Long story short after trying multiple things I disabled the DSM SA services and it starts up fine! I think it is related to the DSM trying to scan the controller to soon ( maybe )
Anyone have any idea why the DSM product would cause the PERC controller to give a blue screen ?
0 events found


DELL-Chris H
7 Practitioner
•
9.7K Posts
•
48K Points
0
May 31st, 2017 07:00
Mpcc,
Would you verify if the server is up to date on BIOS, iDrac, and the H700? Then lastly would you confirm the version of OpenManage you are using. The server being really out of date can start to cause inconsistencies, as well as errors.
Now if the server is several updates behind these then we will need to walk the server up to current, and not just jump to the most recent, as that can cause issues as well.
Let me know what you see.
mpcc
2 Posts
0
June 1st, 2017 10:00
The BIOS is 3.0.0, H700 is 12.3.0, OM is 8.1; I'm not inclined to update BIOS unless a specific issue is identified and fixed. I realize they are not current. Another check I did was to manually start the DSM SA services after the system had been up and running. Again it crashed a few minutes after these services started.
I uninstalled the OM, rebooted and it came up without issue. I reinstalled OM and rebooted again. So far no issues. I'm going to let it run for a while, then perform a few more reboots to verify if any issues come back.
Thanks for taking a look. Perhaps there was something in the OM install that was corrupted. Two othe identical systems have not had any issues.