Fault handling method, system and electronic equipment

Abstract

The present application discloses a fault handling method, system and electronic device. The present application determines the faulty component in the electronic device by detecting the component status of the electronic device, and disables the faulty component based on the obtained disabling instruction when it is determined that the faulty component meets the use conditions so that the device system can still maintain the operating state after disabling the faulty component. Therefore, based on the scheme of the present application, the faulty component of the electronic device (such as a server) can be automatically detected and disabled based on the component status detection, conditional determination of whether the faulty component meets the use conditions, and disabling control of the faulty component. There is no need for operation and maintenance personnel to manually open the device chassis on site to troubleshoot and solve the problem, which can achieve fast and efficient fault handling and service recovery, and reduce labor costs.

Description

Technical Field

[0001] The present application belongs to the technical field of equipment operation and maintenance, and in particular, relates to a fault handling method, system and electronic equipment. Background Art

[0002] When certain components on a device (eg, a server) system fail or an unrecoverable problem occurs, the device's operating system may hang or display a blue screen.

[0003] Currently, maintenance is usually done manually by operation and maintenance personnel, who open the equipment chassis on site to troubleshoot and solve problems. However, this method makes it difficult to solve equipment failures in a timely manner. For example, due to the work schedule of the operation and maintenance personnel, it may take several days for the equipment service to be restored. The efficiency of fault handling and service recovery is low and requires high labor costs. Summary of the invention

[0004] To this end, this application discloses the following technical solutions:

[0005] A fault handling method, the method comprising:

[0006] detecting a component status of at least one device component in the electronic device;

[0007] If there is a target component whose corresponding component status represents a device component failure, obtaining a disabling instruction for instructing to disable the target component;

[0008] Determining whether the target component satisfies a predetermined usage condition in the electronic device; the usage condition is a condition for indicating that the system of the electronic device can maintain an operating state after disabling the target component;

[0009] If satisfied, the target component is disabled.

[0010] Optionally, the detecting a component status of at least one device component in the electronic device includes:

[0011] The predetermined controller of the electronic device obtains the fault diagnosis instruction transmitted by the management device, and detects the component state of at least one device component in the electronic device according to the component error information captured by the predetermined controller indicating that an error has occurred in the operation of the component;

[0012] Alternatively, when the predetermined controller captures component error information indicating an error in component operation, it detects a component state of at least one device component in the electronic device according to the component error information.

[0013] Optionally, obtaining a disabling instruction for instructing to disable the target component includes:

[0014] A predetermined controller of the electronic device obtains a disabling instruction transmitted by a management device for instructing to disable the target component;

[0015] Or, the predetermined controller triggers a disabling instruction for instructing to disable the target component based on the detection result of the component state indicating the event of the existence of the target component;

[0016] Wherein, before obtaining the disabling instruction transmitted by the management device for instructing to disable the target component, the method further includes:

[0017] The predetermined controller at least feeds back component status information of the target component to the management device, so that the management device generates and transmits the disabling instruction to the predetermined controller of the electronic device based on the component status representing component failure corresponding to the target component.

[0018] Optionally, determining whether the target component meets a predetermined usage condition in the electronic device includes:

[0019] a predetermined controller of the electronic device determining whether there is at least one non-faulty component in the electronic device that can be used to provide the component function of the target component;

[0020] If so, the target component satisfies the usage condition;

[0021] If not, the target component does not meet the usage condition.

[0022] Optionally, disabling the target component includes:

[0023] The predetermined controller of the electronic device sends a power-off instruction to the power management unit of the target component, so that the power management unit controls the target component to be powered off.

[0024] Optionally, the method further includes:

[0025] If the use condition is not satisfied, power is retained to the target component to refuse to disable the target component.

[0026] Optionally, after disabling the target component, the method further includes:

[0027] The predetermined controller of the electronic device obtains a restart instruction for instructing to restart the electronic device, and restarts the electronic device;

[0028] The restart instruction is an instruction transmitted by the management device, or an instruction triggered by the predetermined controller based on an event of completing disabling the target component.

[0029] An electronic device, comprising:

[0030] Memory, used to store computer instruction sets;

[0031] The controller is used to implement any of the fault handling methods described above by executing an instruction set stored in a memory.

[0032] Optionally, the controller is a baseboard management controller of the electronic device.

[0033] A fault handling system comprises a management device and at least one electronic device connected to the management device, wherein:

[0034] The management device is used to generate and transmit management instructions to corresponding electronic devices;

[0035] The electronic device is used to execute the fault handling method as described in any one of the above.

[0036] It can be seen from the above scheme that the fault handling method, system and electronic device disclosed in the present application determine the faulty component in the electronic device by detecting the component status of the electronic device, and disable the faulty component based on the obtained disabling instruction when it is determined that the faulty component meets the use conditions so that the device system can still maintain the operating state after disabling the faulty component. Therefore, based on the scheme of the present application, the faulty component of the electronic device (such as a server) can be automatically detected and disabled based on the component status detection, conditional determination of whether the faulty component meets the use conditions, and disabling control of the faulty component. There is no need for operation and maintenance personnel to manually open the device chassis on site to troubleshoot and solve the problem, which can achieve fast and efficient fault handling and service recovery, and reduce labor costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying any creative work.

[0038] Figure 1 It is a flowchart of the troubleshooting method provided by this application;

[0039] Figure 2 This is an architecture diagram of remote management of electronic devices based on management devices provided by this application;

[0040] Figure 3 This is an example of visually displaying component failure information on a management device provided by the present application;

[0041] Figure 4 This is an example of disabling configuration of a faulty component on a management device side provided by the present application;

[0042] Figure 5 It is another flowchart of the fault handling method provided by the present application;

[0043] Figure 6 This is another flowchart of the fault handling method provided by the present application;

[0044] Figure 7 It is a structural schematic diagram of an electronic device provided by this application;

[0045] Figure 8 It is a structural diagram of the fault handling system provided by this application. DETAILED DESCRIPTION

[0046] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0047] The present application discloses a fault handling method, system and electronic device, which are used to solve the problem in traditional technology that when certain components of a device (such as a server) fail or an unrecoverable problem occurs, the device chassis needs to be manually opened on site to troubleshoot and solve the problem, resulting in low efficiency in fault handling and service recovery and high labor costs, and to achieve fast and efficient fault handling and service recovery.

[0048] The fault handling method disclosed in the present application can be applied to devices in many general or special computing device environments or configurations, such as personal computers, server computers (servers / servos), handheld devices or portable devices, tablet devices, multi-processor devices, etc.

[0049] See also Figure 1 The flowchart of the fault handling method provided is as follows:

[0050] Step 101: Detect a component status of at least one device component in an electronic device.

[0051] The electronic device here is the execution main device of the method of this application, such as a server, a server, etc.

[0052] In this step, a predetermined controller of the electronic device is used to capture component error information of each component in the electronic device, and the component status of each component of the device is detected based on the captured information.

[0053] Among them, the predetermined controller can be but is not limited to the BMC (Baseboard Management Controller) of the electronic device, and the BMC is used to capture the operation error logs and other component error information of each component of the server and other equipment, such as the CPU (Central Processing Unit), memory, disk, PSU (Power Supply Unit), RLSER (side panel for plugging in PCIE card), BP (Board Panel, hard disk backplane), etc.

[0054] Optionally, in one embodiment, a management device may be set up for remote management of one or more servers and other electronic devices, and a remote management interaction function and a matching visual management interface for each server may be provided on the management device. Optionally, the management device may provide a visual management interface for the remote management interaction function based on a web page.

[0055] In this implementation, the BMC is used to capture the operation error log and other information of each component in real time during the operation of the electronic device, so as to be used as a basis for detecting whether the component is faulty or not. Figure 2 The BMC receives fault diagnosis instructions transmitted by the management device through communication methods such as LAN (Local Area Network), WLAN (Wireless Local Area Network) or the Internet, such as fault diagnosis instructions periodically transmitted by the management device based on a set time interval, or fault diagnosis instructions triggered and transmitted by the management device based on manual operations of the administrator, etc., and responds to the received fault diagnosis instructions, detects whether the component has a fault according to the captured operation error log and other information and the set detection strategy.

[0056] In implementation, the method is not limited to the above-mentioned management device-based implementation method, and remote management devices may not be set up for electronic devices such as servers. Under this implementation method, the BMC can detect whether a component has a fault in real time or periodically based on a set time interval based on the captured information, according to the set detection strategy, based on the real-time capture of information such as the operation error log of each component.

[0057] For the above two implementations, illustratively, taking the CPU status detection as an example, when the CPU error log is captured continuously for a set number of times (e.g., 3 times), the BMC determines that the CPU is faulty. Otherwise, if the number of CPU error logs captured continuously does not reach the set threshold, it is determined that the CPU is not faulty.

[0058] Step 102: If there is a target component whose corresponding component status represents a device component failure, obtain a disabling instruction for instructing to disable the target component.

[0059] After detecting a target component with a fault through device component status detection, a disabling instruction for instructing to disable the target component is further obtained.

[0060] Preferably, after the BMC of the electronic device detects a faulty target component, it can at least feed back component status information of the target component to the management device, such as the fault status of the target component, the time when the fault occurred, etc., and visually display the relevant status information of the target component on the visual management interface of the management device. On this basis, the administrator of the management device determines whether to disable the faulty component based on the remotely fed back device component status information, and if it is determined to be disabled, configures and submits component information of the component to be disabled, triggers a disabling instruction for the submitted component and transmits it to the electronic device. The BMC of the electronic device accordingly obtains the disabling instruction for the faulty target component transmitted by the management device.

[0061] See also Figure 3 For example, Figure 3 Based on the server feedback, the management device visual management interface displays the DIMM (Dual-Inline-Memory-Modules) fault status information and fault occurrence time. Figure 4 Based on the feedback fault information, the administrator submits the disabling configuration information of the faulty component DIMM to the management device, so that the management device sends an instruction to disable the DIMM to the BMC of the server.

[0062] Optionally, in the absence of a management device, a predetermined controller of the electronic device (such as a BMC of a server) may automatically generate a disabling instruction for disabling a target component based on a detection event of a faulty target component, and this embodiment does not impose any restrictions on this.

[0063] Step 103: Determine whether the target component meets a predetermined usage condition in the electronic device.

[0064] After obtaining a disabling instruction for a target component with a fault, a predetermined controller of the electronic device, such as a BMC, first determines whether the target component meets predetermined usage conditions in the electronic device, and finally determines whether to disable the target component based on the determination result.

[0065] The above-mentioned use condition is a condition for indicating that the system of the electronic device can maintain an operating state after disabling the target component.

[0066] A predetermined controller of an electronic device, such as a BMC of a server, can determine whether a target component satisfies the above-mentioned usage conditions by determining whether there is at least one non-faulty component in the electronic device that can be used to provide the component function of the target component (that is, essentially determining whether there are other components that can meet the required functions of the target component after disabling the target component), wherein, if so, it is determined that the target component satisfies the above-mentioned usage conditions; otherwise, if not, it is determined that the target component does not meet the above-mentioned usage conditions.

[0067] Furthermore, in implementation, it may be possible but not limited to determine whether there is at least one non-faulty component in the electronic device that can be used to provide the component function of the target component based on the following strategy, and then determine whether the target component meets the above-mentioned usage conditions:

[0068] 11) Determine whether there is a non-faulty component of the same type as the target component (faulty component) in the electronic device. If so, the target component meets the usage condition, otherwise, it does not meet the condition.

[0069] The number of some components in an electronic device may be multiple, for example, the number of CPUs and PSUs in a server may be multiple. For these types of components, when a component failure is detected, such as a CPU failure, it is preferred to determine whether there are available non-faulty components of the same type to identify whether disabling the faulty component can at least ensure the minimum configuration operation of the device system, and whether the target component meets the usage conditions based on the minimum configuration operation of the device system.

[0070] The following is an example of this implementation method:

[0071] Assume that there are 3 CPUs in a server, and after one of them fails, if the failed CPU is disabled, there are still two normal CPUs, then the system can be kept running based on the two normal CPUs, in which case the failed CPU is determined to meet the usage conditions; however, if 3 CPUs have failed before and two have been disabled, and now the third one also fails, then the system cannot be kept running after disabling the third failed CPU, in which case the current failed CPU is determined to not meet the usage conditions.

[0072] 12) Determine whether there is a non-faulty component in the electronic device that is of a different type from the target component (faulty component) but can provide the functions required by the target component. If so, the target component meets the usage conditions, otherwise, it does not meet the conditions.

[0073] For a faulty target component, if there is a non-faulty component in the electronic device that is not of the same type but can provide the functions required by the target component, then after disabling the target component, at least the minimum configuration operation of the device system can be guaranteed. Therefore, in this case, it is determined that the target component meets the usage conditions, otherwise, it is determined that it does not meet the conditions.

[0074] For example, for a faulty EC used to implement a certain control function, assuming that it is determined that the CPU in the electronic device is able to perform the required control function, it can be determined that the faulty EC meets the usage conditions.

[0075] During implementation, the component type and the number of components of the same type in the electronic device can be combined to select an adaptive method from the above two implementations to determine whether the faulty component meets the usage conditions. For a component type in which the electronic device includes multiple components, implementation 11) can be adopted, or the above two implementations can be combined (for example, when it is determined based on 11) that all components of the same type are faulty, further determine whether there are replaceable components of a different type based on 12)). For a component type in which the electronic device includes only one component, implementation 12) is adopted.

[0076] Step 104: If satisfied, disable the target component.

[0077] If it is determined that the target component satisfies the above-mentioned usage conditions, that is, the system of the electronic device can maintain an operating state after disabling the target component, the target component is disabled based on the disabling instruction, thereby stopping the electronic device from using the faulty target component, and correspondingly eliminating problems such as operating system hang or blue screen caused by component failure.

[0078] A power-off instruction may be sent to a power management unit of a target component through a predetermined controller of the electronic device, and the power management unit of the target component may control power-off of the target component to disable the target component.

[0079] Specifically, the embodiments of the present application configure independent power management units for different types of components, and refer to Figure 2For example, CPU VR (Voltage Regulated) is configured as the power management unit of CPU, MEMVR is configured as the power management unit of memory / storage, Rlser VR is configured as the power management unit of Rlser, and combined with the power supply and management functions of the PSU's own chip, the PSU itself is configured as the power management unit of PSU, and BP PSOC (Power System On a Chip) is configured as the power management unit of BP, and so on.

[0080] On this basis, for the faulty component, the BMC sends a power-off instruction carrying the faulty component information to the power management unit corresponding to the component, so that the power management unit can control the power-off of the faulty component in a targeted manner. Specifically, the power management unit cuts off the supply voltage to the faulty component, for example, pulls the corresponding voltage signal to a low level, simulates the hot plug operation of the faulty component, and realizes the power-off control of the faulty component.

[0081] By controlling the power off of the faulty component, the electronic device stops using the faulty component (i.e., the target component), thereby eliminating problems such as operating system hang or blue screen caused by component failure. After disabling the faulty component, at least the minimum configuration of the device system can be guaranteed to run.

[0082] It should be noted that, during implementation, for a management device that is remotely set up for an electronic device, the corresponding remote control function may be configured or not configured on the management device side according to actual needs. For example, a remote fault diagnosis control function for the electronic device is configured on the management device side. Based on this function, the electronic device performs the fault detection processing of the component status only after receiving the fault diagnosis instruction of the management device, otherwise it will not be executed. A fault component disabling function for the electronic device is configured on the management device side. Based on this function, the electronic device performs the disabling processing of the faulty component only after receiving the disabling instruction of the faulty component from the management device, otherwise it will not be executed, etc. Alternatively, the fault diagnosis control function and / or the fault component disabling function are configured on the electronic device side, and the electronic device performs the corresponding component status detection and / or fault component disabling processing based on the corresponding event trigger, and the management device is only responsible for providing the collection of fault processing situations (such as periodic active collection, or passive collection based on reports from electronic devices) and display functions, etc. This embodiment does not limit this.

[0083] As can be seen from the above scheme, the method of this embodiment determines the faulty component in the electronic device by detecting the component status of the electronic device, and disables the faulty component based on the obtained disabling instruction when it is determined that the faulty component meets the use conditions so that the device system can still maintain the operating state after disabling the faulty component. Therefore, based on the scheme of this application, the faulty component of the electronic device (such as a server) can be automatically detected and disabled based on the component status detection, conditional determination of whether the faulty component meets the use conditions, and disabling control of the faulty component. There is no need for operation and maintenance personnel to manually open the device chassis on site to troubleshoot and solve the problem, which can achieve fast and efficient fault handling and service recovery, and reduce labor costs.

[0084] In one embodiment, see Figure 5 The fault handling method provided in the present application may further include the following processing after step 103:

[0085] Step 105: If the target component does not meet the above usage conditions, keep the power supply to the target component to refuse to disable the target component.

[0086] If the target component does not meet the above usage conditions, it means that the device system cannot maintain the operating state after disabling the target component. For example, there is only one CPU in the device and the CPU is faulty, or the device has three CPUs, two of which have been disabled due to failure and the third is further detected to be faulty. In this case, the power supply to the target component is retained, that is, the BMC does not send a power-off instruction to the power management unit of the target component in response to the obtained disable instruction for the target component, and refuses to disable the target component.

[0087] In this case, the service of the electronic device cannot be automatically restored, and problems such as device hanging or blue screen may still exist. Preferably, in order to realize the rapid recovery of device services as much as possible, the BMC of the electronic device can record relevant log information, such as the type and quantity of faulty components (such as the log of all three CPU failures of the device), fault time, etc., and return the recorded log information to the management device for visual display, so that the management side can schedule the fault handling work as soon as possible, and combine the returned log information to deal with the faulty components in the electronic device in a targeted manner during fault handling (without performing troubleshooting on each component one by one).

[0088] In addition, optionally, when the target component meets the usage conditions and is disabled, relevant logs can also be generated in the BMC of the electronic device, such as the type, location / number, failure time, etc. of the faulty component, and returned to the management device so that the management personnel can promptly understand the component status and disabling status of each remote electronic device.

[0089] In one embodiment, see Figure 6 The fault handling method flow chart provided in the present application may further include the following processing after step 104 (disabling the target component):

[0090] Step 106: A predetermined controller of the electronic device obtains a restart instruction for instructing to restart the electronic device, and restarts the electronic device.

[0091] Among them, the restart instruction for instructing to restart the electronic device can be an instruction triggered by the management device and remotely transmitted to the electronic device, such as an instruction automatically generated and transmitted by the management device by parsing the disabling log of the target component returned by the electronic device, or an instruction manually initiated by an administrator, etc., or, in the case where no management device is set, the restart instruction can also be an instruction automatically generated by the electronic device (such as a server) based on the event of disabling the target component, and this embodiment does not impose any restrictions on this.

[0092] After receiving the restart instruction, the predetermined controller of the electronic device (such as the BMC of the server) responds to the instruction and restarts the electronic device. After the electronic device is restarted, the electronic device maintains the operation of the device system based on the predetermined corresponding components that can be used to provide the functions required by the faulty component, such as non-faulty components of the same type or different types, and the faulty component is not used during the operation of the system, and the problems such as the operating system hang or blue screen caused by the faulty component are eliminated at the same time, and the system service can be quickly restored.

[0093] Therefore, for electronic equipment (such as servers / servoir), when a component failure occurs, the faulty component can be automatically detected and disabled, eliminating the need for operation and maintenance personnel to manually open the equipment chassis on site to troubleshoot and solve the problem, thereby achieving fast and efficient fault handling and service recovery, and reducing labor costs.

[0094] In addition, an embodiment of the present application further discloses an electronic device, which is the main device for executing the method of the present application, and may be, but is not limited to, a server, a servo, or other device.

[0095] The electronic device has a structure such as Figure 7 As shown, specifically including:

[0096] Memory 701, used for storing computer instruction sets;

[0097] A set of computer instructions can be implemented in the form of a computer program.

[0098] The controller 702 is used to implement the fault handling method disclosed in any of the above method embodiments by executing a computer instruction set.

[0099] Optionally, the controller 702 may be a baseboard management controller BMC of the electronic device.

[0100] In addition, electronic devices may also include processors such as a central processing unit (CPU), an application-specific integrated circuit (ASIC), a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, as well as components such as a communication interface and a communication bus. The memory, processor and communication interface communicate with each other through the communication bus.

[0101] The communication interface is used for communication between electronic devices and other devices. The communication bus can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The communication bus can be divided into an address bus, a data bus, a control bus, etc.

[0102] In addition, the present application also discloses a fault handling system, see Figure 8 The system includes a management device 801 and at least one electronic device 802 connected to the management device, wherein:

[0103] Management device 801, used to generate and transmit management instructions to corresponding electronic devices;

[0104] The electronic device 802 is used to execute the fault handling method disclosed in any of the above method embodiments.

[0105] The management device 801 can remotely manage and interact with each electronic device 802 via wireless or wired connection.

[0106] The management device 801 and at least one electronic device 802 interact with each other through corresponding remote management to automatically detect and disable faulty components of the electronic device on the electronic device side. There is no need for operation and maintenance personnel to manually open the device chassis on site to troubleshoot and solve problems, which can achieve fast and efficient fault handling and service recovery and reduce labor costs.

[0107] It should be noted that the various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referenced to each other.

[0108] For the convenience of description, the above system or device is described by dividing it into various modules or units according to its functions. Of course, when implementing the present application, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0109] It can be known from the description of the above implementation methods that those skilled in the art can clearly understand that the present application can be implemented by means of software plus a necessary general hardware platform. Based on such an understanding, the technical solution of the present application can be essentially or partly contributed to the prior art in the form of a software product, which can be stored in a storage medium such as ROM / RAM, a magnetic disk, an optical disk, etc., and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in the various embodiments of the present application or certain parts of the embodiments.

[0110] Finally, it should be noted that, in this article, relational terms such as first, second, third and fourth are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the statement "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.

[0111] The above is only a preferred implementation of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A fault handling method, the method comprising: detecting a component state of at least one device component in the electronic device; If there is a target component whose corresponding component status represents a device component failure, obtaining a disabling instruction for instructing to disable the target component; Determining whether the target component satisfies a predetermined usage condition in the electronic device; the usage condition is a condition for indicating that the system of the electronic device can maintain an operating state after disabling the target component; If satisfied, disabling the target component; Wherein, determining whether the target component meets a predetermined usage condition in the electronic device includes: a predetermined controller of the electronic device determining whether there is at least one non-faulty component in the electronic device that can be used to provide the component function of the target component; If so, the target component satisfies the usage condition; If not, the target component does not meet the usage condition.

2. The method according to claim 1, wherein detecting a component status of at least one device component in the electronic device comprises: The predetermined controller of the electronic device obtains the fault diagnosis instruction transmitted by the management device, and detects the component state of at least one device component in the electronic device according to the component error information captured by the predetermined controller indicating that an error has occurred in the operation of the component; Alternatively, when the predetermined controller captures component error information indicating an error in component operation, it detects a component state of at least one device component in the electronic device according to the component error information.

3. The method according to claim 1, wherein obtaining a disabling instruction for instructing to disable the target component comprises: A predetermined controller of the electronic device obtains a disabling instruction transmitted by a management device for instructing to disable the target component; Or, the predetermined controller triggers a disabling instruction for instructing to disable the target component based on the detection result of the component state indicating the event of the existence of the target component; Wherein, before obtaining the disabling instruction transmitted by the management device for instructing to disable the target component, the method further includes: The predetermined controller at least feeds back component status information of the target component to the management device, so that the management device generates and transmits the disabling instruction to the predetermined controller of the electronic device based on the component status representing component failure corresponding to the target component.

4. The method according to claim 1, wherein disabling the target component comprises: The predetermined controller of the electronic device sends a power-off instruction to the power management unit of the target component, so that the power management unit controls the target component to be powered off.

5. The method according to claim 1, further comprising: If the use condition is not satisfied, power is retained to the target component to refuse to disable the target component.

6. The method according to claim 1, after disabling the target component, further comprising: The predetermined controller of the electronic device obtains a restart instruction for instructing to restart the electronic device, and restarts the electronic device; The restart instruction is an instruction transmitted by a management device, or an instruction triggered by the predetermined controller based on an event of completing disabling the target component.

7. An electronic device comprising: Memory, used to store computer instruction sets; A controller, configured to implement the fault handling method according to any one of claims 1 to 6 by executing an instruction set stored in a memory. 8 . The electronic device according to claim 7 , wherein the controller is a baseboard management controller of the electronic device.

9. A fault handling system, comprising a management device and at least one electronic device connected to the management device, wherein: The management device is used to generate and transmit management instructions to corresponding electronic devices; The electronic device is used to execute the fault handling method as described in any one of claims 1-6.

Images