IBM服务器不定时自动重启

1、主板或电源的可以性大。你可以去BIOS的系统日志里看一下。应该有纪录的。

2、还有就是重新安装过系统，居然能稳定几天。这个有点不明白。如果条件允许的话，建议你做完系统后，什么也不要安装。纯系统，也不要插网线，看看能坚持多长时间。如果能有1周。那就有可能是什么软件冲突了。

先对这个错误有个认识： DllRegisterServer in COM failed. Return code was: 0x80070005 Symptom: When attempting to register a COM object (e.g. Active-X component or OCX) with ‘Regsvr32’, i.e.: regsvr32 COM it fails with a message box displaying: DllRegisterServer in COM failed. Return code was: 0x80070005 Where ‘COM’ is the name of the COM object file. Cause: The error value ‘0x80070005’ means ‘Access Denied’. This means that an attempt has been made to update part of the registry that you do not have permissions to update. There are many parts of the registry that can be read but not updated (except by ‘system’ or the local administrator). Possibly Remedies: Check that you have local administration rights. If you are a local administrator (i.e. a member of the ‘Administrators’ group on the workstation) then most likely someone or some application has modified (intentionally or unintentionally) the permissions on one or more registry keys and that this is preventing access. (Alternately, it may be that the key that is failing is one that normally only ‘system’ can update.) To identify which registry key is causing the problem use Regmon (a freeware tool published by System Internals). Use Regmon to capture all registry access when regsvr32 is run. If an ‘OpenKey’ request fails with ‘Access Denied’ (which is listed by Regmon as ‘ACCDENIED’) then run regedt32 and check the permissions on that registry key. If necessary change the permissions on the key to grant local Administrators ‘Full Control’. They try registering the COM object again. The only times I have encountered this problem it affected more than one key, so be prepared to repeat this process. 可以看出，这个错误是由于没有对注册表项操作的权限引起的。其中提到用工具Regmon，这个工具是用来监视注册表的，例如对 revsvr32 LiveShareCom.dll进行注册的时候，设置"Regmon过滤"包含LiveShareCom，当进行注册的时候，会在Regmon中显示对注册表的修改，在“结果”列中，如果出现"Access Denied"结果，则说明此项没有权限，用Regmon的定位功能，将该项定位到Regedit中，右键单击该注册表项，设置他们的Permissions...为可控状态即可。

raid被破坏，可能是硬盘坏了或者被误操作。能否保住数据，图片中看不出来。做好丢失数据的准备吧！

在CTRL+A提示的时候，按下CTRL+A可以进下级菜单查看raid详情。

两块逻辑盘，ARRAY0和ARRAY1，状态都不正常。0目前在rebuild重建，1有错误。其中，1应该是有一块物理硬盘坏了或者相关通道有问题，0一般可以重建完成，重建完成后，状态可能跟1一样。如果是这样，硬盘故障的可能性会小一些，连接线、背板或者raid卡之间嫌疑会增大

---