rssLink RSS for all categories
 
icon_red
icon_green
icon_red
icon_red
icon_blue
icon_green
icon_green
icon_red
icon_red
icon_red
icon_orange
icon_green
icon_green
icon_green
icon_green
icon_blue
icon_green
icon_orange
icon_red
icon_green
icon_red
icon_red
icon_green
icon_red
icon_red
icon_red
icon_red
icon_orange
icon_green
 

FS#306 — FS#4387 — filerz101.mail

Attached to Project— E-mail
Incident
all
CLOSED
100%
The filer does not respond, we intervene.
Date:  Wednesday, 22 September 2010, 14:15PM
Reason for closing:  Done
Comment by OVH - Friday, 16 July 2010, 10:57AM

The server is frozen, we re-launch.


Comment by OVH - Friday, 16 July 2010, 10:59AM

A faulty CPU is the source of the defect, we plan to have alternatives.

--------------- ------------------------------------ -------------- ---------
TIME EVENT-ID MSG-ID SEVERITY
--------------- ------------------------------------ -------------- ---------
Jul 16 00:43:10 bbd2b3ec-2f3b-e7ea-9e45-a938b60263ca INTEL-8000-WS Critical

Host : filerz101
Platform : System Product Name Chassis_id : System Serial Number

Fault class : fault.cpu.intel.nb.fsb
Problem in : hc://:product-id=System-Product-Name:chassis-id=System:server-id=filerz101/motherboard=0/chip=1
faulted but still in service
FRU : hc://:product-id=System-Product-Name:chassis-id=System:server-id=filerz101/motherboard=0/chip=1
faulty

Description : Front Side bus between CPU and northbridge Refer to
http://sun.com/msg/INTEL-8000-WS for more information.

Response : System panic or reset by BIOS

Impact : System may panic or be reset by BIOS

Action : Schedule a repair procedure to replace the affected CPU. Use
'fmadm faulty' to identify the module.