CN113849432B - Server firmware data storage method, starting method, device, equipment and medium - Google Patents
Server firmware data storage method, starting method, device, equipment and medium Download PDFInfo
- Publication number
- CN113849432B CN113849432B CN202111062571.4A CN202111062571A CN113849432B CN 113849432 B CN113849432 B CN 113849432B CN 202111062571 A CN202111062571 A CN 202111062571A CN 113849432 B CN113849432 B CN 113849432B
- Authority
- CN
- China
- Prior art keywords
- server
- target
- data
- firmware data
- area
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 52
- 238000013500 data storage Methods 0.000 title claims abstract description 30
- 238000011084 recovery Methods 0.000 claims abstract description 78
- 238000004891 communication Methods 0.000 claims abstract description 73
- 238000007726 management method Methods 0.000 claims description 86
- 230000006870 function Effects 0.000 claims description 18
- 238000004590 computer program Methods 0.000 claims description 14
- 238000010586 diagram Methods 0.000 description 9
- 238000005192 partition Methods 0.000 description 4
- 238000012544 monitoring process Methods 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000033228 biological regulation Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000003745 diagnosis Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000017525 heat dissipation Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/14—Handling requests for interconnection or transfer
- G06F13/16—Handling requests for interconnection or transfer for access to memory bus
- G06F13/1668—Details of memory controller
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- Stored Programmes (AREA)
Abstract
The application discloses a server firmware data storage method, a starting method, a device, equipment and a medium, comprising the following steps: creating a communication connection link between a target component of the server and an external storage chip; the target component is a component supporting a platform firmware protection recovery function in the server; acquiring target firmware data stored in a temporary storage area in the target component; and transmitting the target firmware data to the external storage chip through the communication connection link for storage, so that the target component acquires the target firmware data in a mode of reading data from the external storage chip after the data loss event occurs in the temporary storage area. According to the application, the firmware data of the temporary storage area of the target component is stored into the external storage chip through the communication connection link established between the standard interface provided by the external storage chip and the target component of the server, so that the reliability of storing the firmware data is improved, and the stability of the performance of the server is ensured.
Description
Technical Field
The present application relates to the field of server technologies, and in particular, to a method, an apparatus, a device, and a medium for storing server firmware data.
Background
At present, during the running process of the server, the firmware data in the components are generally required to be used for carrying out corresponding operation on the server, and if faults, such as sudden power failure or dead halt, occur in the running process of the server, the data can be lost, so that the normal use of the server is affected.
For example, the BMC (Baseboard Manager Controller, baseboard management controller) is used as a baseboard management system on a server, and is mainly responsible for important functions of asset information display, hardware monitoring, heat dissipation regulation, system configuration, remote monitoring, log collection, fault diagnosis, system maintenance and the like of the server. The server BMC having the PFR (Platform Firmware Resilience) function is divided into an active area (i.e., active area), a recovery area (i.e., recovery area), and a staging area (i.e., status area), and the BMC starts from the active area. When the active area is damaged, the server may restore the active area using the restore area. When the recovery area and the active area are damaged at the same time, the server can recover the recovery area by using the temporary storage area and recover the active area by using the recovery area again, so that the temporary storage area is the last guarantee that the BMC can be started normally.
However, the temporary storage area and the active area of the BMC are usually stored in the same flash chip, when the active area is destroyed, it is difficult to ensure that the temporary storage area is not destroyed, and at this time, if the recovery area is also destroyed, the server cannot be started. In addition, the temporary storage area is emptied every time the BMC is updated by burning the chip. Thus, the normal availability of the BMC's zone data determines whether the BMC can start up normally.
In summary, how to improve the reliability of firmware data storage in a server component and ensure the stability of the server performance is a problem to be solved in the art.
Disclosure of Invention
Accordingly, the present application is directed to a method, apparatus, device, and medium for storing firmware data of a server, which can externally store the firmware data of the server, thereby ensuring the stability of the server performance. The specific scheme is as follows:
in a first aspect, the present application discloses a server firmware data storage method, which is applied to a server, and includes:
creating a communication connection link between a target component of the server and an external storage chip; the target component is a component supporting a platform firmware protection recovery function in the server;
acquiring target firmware data stored in a temporary storage area in the target component;
and transmitting the target firmware data to the external storage chip through the communication connection link for storage, so that the target component acquires the target firmware data in a mode of reading data from the external storage chip after the data loss event occurs in the temporary storage area.
Optionally, the creating a communication connection link between the target component of the server and the external storage chip includes:
creating a communication connection link between a baseboard management controller of the server and an embedded multimedia card;
correspondingly, the obtaining the target firmware data stored in the temporary storage area in the target component includes:
and acquiring target firmware data stored in a temporary storage area in the baseboard management controller.
Optionally, the transmitting the target firmware data to the external storage chip through the communication connection link for storage, so that the target component obtains the target firmware data by reading data from the external storage chip after the data loss event occurs in the temporary storage area, including:
and transmitting the target firmware data to the embedded multimedia card for storage through the communication connection link, so that the baseboard management controller can acquire the target firmware data in a mode of reading the data from the embedded multimedia card after the data loss event occurs in the temporary storage area, the recovery area and the active area.
Optionally, after the target firmware data is obtained by reading data from the embedded multimedia card, the method further includes:
and carrying out data recovery on the temporary storage area, the recovery area and the active area in the baseboard management controller by using the target firmware data read from the embedded multimedia card.
Optionally, the performing data recovery on the temporary storage area, the recovery area and the active area in the baseboard management controller by using the target firmware data read from the embedded multimedia card includes:
performing data recovery on the temporary storage area of the baseboard management controller by using the target firmware data read from the embedded multimedia card;
restoring the restoration area of the baseboard management controller by using the restored temporary storage area;
and restoring the active area of the baseboard management controller by using the restored active area so as to start the baseboard management controller by using the restored active area.
Optionally, the creating a communication connection link between the target component of the server and the external storage chip includes:
after the target component is started, a driving program of an external storage chip is obtained, and the driving program is loaded through the target component;
and after the driver is loaded, the external storage chip is mounted to the target component so as to build a communication connection link between the target component of the server and the external storage chip.
In a second aspect, the present application discloses a method for starting a server component, which is applied to a server, and includes:
judging whether the active area of the target component in the server is damaged or not; the target component is a component supporting a platform firmware protection recovery function in the server;
if the active area is damaged, judging whether a recovery area and a temporary storage area of the target assembly are damaged or not;
if the temporary storage area and the recovery area are damaged, reading pre-stored target firmware data from an external storage chip, and starting the target assembly by utilizing the target firmware data; the target firmware data are firmware data which are transmitted from the temporary storage area to the external memory chip for storage when the temporary storage area is not damaged in advance.
In a third aspect, the present application discloses a server firmware data storage device, applied to a server, comprising:
the link creation module is used for creating a communication connection link between a target component of the server and an external storage chip; the target component is a component supporting a platform firmware protection recovery function in the server;
the data acquisition module is used for acquiring target firmware data stored in the temporary storage area in the target component;
and the data storage module is used for transmitting the target firmware data to the external storage chip for storage through the communication connection link, so that the target assembly can acquire the target firmware data in a mode of reading the data from the external storage chip after the data loss event occurs in the temporary storage area.
In a fourth aspect, the application discloses an electronic device comprising a processor and a memory; the processor implements the aforementioned server firmware data storage method when executing the computer program stored in the memory.
In a fifth aspect, the present application discloses a computer-readable storage medium for storing a computer program; wherein the computer program, when executed by the processor, implements the aforementioned server firmware data storage method.
Therefore, the application firstly establishes a communication connection link between the target component of the server and the external storage chip; the target component is a component supporting a platform firmware protection recovery function in the server, then target firmware data stored in a temporary storage area in the target component is obtained, the target firmware data is transmitted to the external storage chip for storage through the communication connection link, and the target firmware data is obtained in a mode of reading data from the external storage chip after a data loss event occurs in the temporary storage area. Therefore, the application establishes a communication connection link between the external storage chip and the target component of the server, and saves the data of the temporary storage area of the target component to the external storage chip through the communication connection link, thereby realizing external storage of firmware data, improving the reliability of firmware data storage and further ensuring the stability of the performance of the server.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are required to be used in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are only embodiments of the present application, and that other drawings can be obtained according to the provided drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flow chart of a method for storing server firmware data according to the present application;
FIG. 2 is a flowchart of a specific method for storing server firmware data according to the present application;
fig. 3 is a schematic diagram of a hardware connection structure between a BMC and an embedded multimedia card according to the present application;
FIG. 4 is a process flow diagram of a baseboard management controller data storage method of the present disclosure;
FIG. 5 is a diagram of an embedded multimedia card mounted application code according to the present application;
FIG. 6 is a flowchart of a method for starting a server component according to the present disclosure;
FIG. 7 is a schematic diagram of a server firmware data storage device according to the present application;
fig. 8 is a block diagram of an electronic device according to the present disclosure.
Detailed Description
The following description of the embodiments of the present application will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
The embodiment of the application discloses a server firmware data storage method, which is applied to a server, and is shown in fig. 1, and comprises the following steps:
step S11: creating a communication connection link between a target component of the server and the external storage chip; the target component is a component supporting a platform firmware protection recovery function in the server.
In this embodiment, a communication connection link can be established between the standard interface provided by the external storage chip and a component supporting the platform firmware protection recovery function in the server. Among them are but not limited to BIOS (Basic Input Output System ), CPLD (Complex Programmable logic device, complex programmable logic device), BMC, and the like.
In this embodiment, the creating a communication connection link between the target component of the server and the external storage chip may specifically include: after the target component is started, a driving program of an external storage chip is obtained, and the driving program is loaded through the target component; and after the driver is loaded, the external storage chip is mounted to the target component so as to build a communication connection link between the target component of the server and the external storage chip. It can be understood that, in general, after the target component is started, a driver corresponding to the external storage chip is first obtained, then the driver is loaded through the target component, and after the loading of the driver is completed, the external storage chip is mounted on the target component, that is, a communication connection link between the target component and the external storage chip of the server is set up, so that data communication between the target component and the external storage chip of the server can be realized.
Step S12: and acquiring target firmware data stored in a temporary storage area in the target component.
In this embodiment, after the communication connection link between the target component of the server and the external storage chip is created, further, firmware data pre-stored in the temporary storage area in the target component, that is, target firmware data, is obtained.
Step S13: and transmitting the target firmware data to the external storage chip through the communication connection link for storage, so that the target component acquires the target firmware data in a mode of reading data from the external storage chip after the data loss event occurs in the temporary storage area.
In this embodiment, after the target firmware data stored in the temporary storage area of the target component is obtained, the target firmware data may be sent to the external storage chip for storage through the communication connection link, and after the firmware data in the temporary storage area of the target component is lost, the pre-stored target firmware data may be obtained from the external storage chip, and the server may be operated correspondingly by using the obtained target firmware data. For example, when the BMC is refreshed by burning the chip, the temporary storage area is usually emptied, and at this time, the target firmware data corresponding to the temporary storage area, which is stored locally in advance, may be obtained from the external embedded multimedia card where the communication connection link is created in advance, and the temporary storage area is restored by using the obtained target firmware data.
Therefore, the embodiment of the application firstly creates a communication connection link between the target component of the server and the external storage chip; the target component is a component supporting a platform firmware protection recovery function in the server, then target firmware data stored in a temporary storage area in the target component is obtained, the target firmware data is transmitted to the external storage chip for storage through the communication connection link, and the target firmware data is obtained in a mode of reading data from the external storage chip after a data loss event occurs in the temporary storage area. Therefore, in the embodiment of the application, the communication connection link is established between the standard interface provided by the external storage chip and the target component of the server, and the target firmware data in the temporary storage area of the target component is stored in the external storage chip through the communication connection link, so that the external storage of the firmware data can be realized, the reliability of the storage of the firmware data is improved, and the stability of the performance of the server is further ensured.
The embodiment of the application discloses a specific server firmware data storage method, which is shown in fig. 2 and comprises the following steps:
step S21: creating a communication connection link between a baseboard management controller of the server and the embedded multimedia card; the baseboard management controller supports platform firmware protection restoration functions.
In this embodiment, a communication connection link may be established between a standard interface provided by the embedded multimedia card and the baseboard management controller supporting the platform firmware protection recovery function server. Specifically, referring to fig. 3, fig. 3 shows a communication connection link between a BMC of a server and a memory chip of an embedded multimedia card (eMMC, embedded Multi Media Card), and in fig. 3, the BMC is in hardware communication with the embedded multimedia card through four communication links, namely CLK, date Strobe, CMD, DAT0-7, and the interface speed is up to 400Mbytes per second, so that a log file of the BMC can be ensured to be quickly and accurately stored in the embedded multimedia card.
Step S22: and acquiring target firmware data stored in a temporary storage area in the baseboard management controller.
In this embodiment, after the communication connection link between the baseboard management controller of the server and the embedded multimedia card is created, further, the firmware data pre-stored in the temporary storage area of the baseboard management controller is extracted to obtain the target firmware data.
Step S23: and transmitting the target firmware data to the embedded multimedia card for storage through the communication connection link, so that the baseboard management controller can acquire the target firmware data in a mode of reading the data from the embedded multimedia card after the data loss event occurs in the temporary storage area, the recovery area and the active area.
In this embodiment, after the target firmware data stored in the temporary storage area of the baseboard management controller is obtained, the target firmware data may be sent to the embedded multimedia card through the communication connection link to be stored, and after the temporary storage area, the recovery area and the active area of the baseboard management controller all have data loss events, the target firmware data corresponding to the temporary storage area, which is stored locally in advance, may be read from the embedded multimedia card.
Specifically, referring to fig. 4, fig. 4 shows a process flow diagram of a method for storing firmware data in a temporary storage area of a baseboard management controller, and in fig. 4, after a server is powered on to start the baseboard management controller, an embedded multimedia card is loaded through a communication connection link created between the baseboard management controller based on the server and the embedded multimedia card in advance, so that the baseboard management controller is mounted on the embedded multimedia card. Further, after the embedded multimedia card is mounted on the baseboard management controller, the baseboard management controller further detects whether the mounting is successful, as shown in fig. 5, whether the embedded multimedia card is mounted with the baseboard management controller is successful or not can be detected through a preset program instruction, and log alarm prompt information of 'Disk non exists, please check hardware' is displayed when the communication connection link is not successful; if the mount is successful, the judging instruction of whether the temporary storage partition for storing the firmware data exists is continuously executed, if the "Partition not exist now, create it" is displayed, the temporary storage partition does not exist and the corresponding temporary storage partition needs to be created.
Specifically, in this embodiment, after the target firmware data is obtained by reading data from the embedded multimedia card, the method may further include: and carrying out data recovery on the temporary storage area, the recovery area and the active area in the baseboard management controller by using the target firmware data read from the embedded multimedia card. It will be appreciated that a baseboard management controller supporting platform firmware protection restoration functions typically includes an active area, a restoration area, and a temporary area, and that the baseboard management controller is powered up from the active area. Because the active area and the temporary storage area are stored on the same flash chip, when the active area is damaged, the temporary storage area is damaged in normal conditions, and the active area can be recovered through the recovery area at the moment, but when the recovery area is damaged, the temporary storage area, the recovery area and the active area in the baseboard management controller can be recovered by reading target firmware data stored in advance from the embedded multimedia card and utilizing the read target firmware data. The target firmware data are firmware data which are sent to the embedded multimedia card from the temporary storage area of the baseboard management controller to be stored when the temporary storage area is not damaged in advance.
In this embodiment, the performing data recovery on the temporary storage area, the recovery area, and the active area in the baseboard management controller by using the target firmware data read from the embedded multimedia card may specifically include: performing data recovery on the temporary storage area of the baseboard management controller by using the target firmware data read from the embedded multimedia card; restoring the restoration area of the baseboard management controller by using the restored temporary storage area; and restoring the active area of the baseboard management controller by using the restored active area so as to start the baseboard management controller by using the restored active area. It can be understood that, after the data loss event occurs in the temporary storage area, the recovery area and the active area, the baseboard management controller can obtain the target firmware data by reading the data from the embedded multimedia card, so that the temporary storage area of the baseboard management controller can be recovered by using the read target firmware data, then the recovery area of the baseboard management controller is recovered by using the recovered temporary storage area, the active area of the baseboard management controller is recovered by using the recovered recovery area, and the baseboard management controller is started by using the recovered active area.
For more specific processing procedures in the steps S21 and S22, reference may be made to the corresponding contents disclosed in the foregoing embodiments, and no detailed description is given here.
It can be seen that, in the embodiment of the present application, a communication connection link between a baseboard management controller of a server and an embedded multimedia card is created, then target firmware data stored in a temporary storage area in the baseboard management controller is obtained, and then the target firmware data is transmitted to the embedded multimedia card for storage through the communication connection link, so that the baseboard management controller obtains the target firmware data by reading data from the embedded multimedia card after a data loss event occurs in the temporary storage area, a recovery area and an active area. According to the embodiment of the application, the target firmware data of the temporary storage area of the baseboard management controller is stored in the embedded multimedia card through the communication connection link pre-established between the baseboard management controller and the embedded multimedia card of the server, so that the external storage of the firmware data of the baseboard management controller is realized, after the temporary storage area, the recovery area and the active area of the baseboard management controller have data loss events, the target firmware data is acquired from the embedded multimedia card, and the temporary storage area of the baseboard management controller is recovered by utilizing the target firmware data, thereby improving the reliability of the firmware data storage of the baseboard management controller and ensuring the stability of the server performance.
The embodiment of the application discloses a method for starting a server component, which is applied to a server, and is shown in fig. 6, and the method comprises the following steps:
step S31: judging whether the active area of the target component in the server is damaged or not; the target component is a component supporting a platform firmware protection recovery function in the server.
In this embodiment, after the server is powered on, a target component supporting a platform firmware protection recovery function in the server is started, and whether an active area in the target component is damaged is determined. For example, after the server is powered on and started, it is first determined whether damage occurs to an active area of the server baseboard management controller for startup.
Step S32: and if the active area is damaged, judging whether the recovery area and the temporary storage area of the target assembly are damaged or not.
In this embodiment, after determining whether the active area of the target component in the server is damaged, if the active area is damaged, determining whether the recovery area and the temporary storage area in the target component are damaged is continued. In a specific embodiment, if the active area of the baseboard management controller in the server is damaged, determining whether the recovery area in the baseboard management controller is damaged, if the recovery area in the baseboard management controller is not damaged, recovering the active area by using the recovery area, and starting the baseboard management controller by using the recovered active area.
Step S33: if the temporary storage area and the recovery area are damaged, reading pre-stored target firmware data from an external storage chip, and starting the target assembly by utilizing the target firmware data; the target firmware data are firmware data which are transmitted from the temporary storage area to the external memory chip for storage when the temporary storage area is not damaged in advance.
In this embodiment, after the active area is damaged and whether the recovery area and the temporary storage area of the target component are damaged is determined, if both the temporary storage area and the recovery area are damaged, target firmware data stored locally in advance may be obtained from an external memory chip, and the target component may be started by using the target firmware data; the target firmware data is the firmware data which is transmitted from the temporary storage area to the external memory chip and stored when the temporary storage area is not damaged in advance. Further, after the target firmware data is obtained, the target component may be started up using the target firmware data. For example, after the temporary storage area, the recovery area and the active area of the baseboard management controller are damaged, the temporary storage area of the baseboard management controller can be recovered by using the target firmware data which is read from the embedded multimedia card and stored in advance, the recovery area of the baseboard management controller is recovered by using the recovered temporary storage area, the active area of the baseboard management controller is recovered by using the recovered recovery area, and the baseboard management controller is started by using the recovered active area.
For more specific processing procedures regarding the above steps, reference may be made to the corresponding contents disclosed in the foregoing embodiments, and no further description is given here.
It can be seen that, in the embodiment of the present application, whether an active area of a target component in a server is damaged is first determined, if the active area is damaged, whether a recovery area and a temporary storage area of the target component are damaged is determined, if both the temporary storage area and the recovery area are damaged, target firmware data stored in advance is read from an external memory chip, and the target component is started by using the target firmware data; the target firmware data are firmware data which are transmitted from the temporary storage area to the external memory chip for storage when the temporary storage area is not damaged in advance. Therefore, when the active area, the temporary storage area and the recovery area of the target component are damaged, the embodiment of the application can acquire the pre-stored target firmware data corresponding to the temporary storage area of the target component from the storage chip outside the target component, and start the target component by using the target firmware data, so that the normal start of the server firmware can be ensured, and the stability of the server performance is further ensured.
Correspondingly, the embodiment of the application also discloses a server firmware data storage device which is applied to a server, and referring to fig. 7, the device comprises:
a link creation module 11 for creating a communication connection link between a target component of the server and an external memory chip; the target component is a component supporting a platform firmware protection recovery function in the server;
the data acquisition module 12 is configured to acquire target firmware data stored in a temporary storage area in the target component;
and the data storage module 13 is configured to transmit the target firmware data to the external storage chip for storage through the communication connection link, so that the target component obtains the target firmware data by reading data from the external storage chip after the data loss event occurs in the temporary storage area.
The specific workflow of each module may refer to the corresponding content disclosed in the foregoing embodiment, and will not be described herein.
Therefore, in the embodiment of the application, the communication connection link between the target component of the server and the external storage chip is firstly established, then the target firmware data stored in the temporary storage area in the target component is obtained, and the target firmware data is transmitted to the external storage chip for storage through the communication connection link, so that the target component can obtain the target firmware data in a mode of reading data from the external storage chip after the data loss event occurs in the temporary storage area. Therefore, in the embodiment of the application, the communication connection link is established between the standard interface provided by the external storage chip and the target component of the server, and the target firmware data in the temporary storage area of the target component is stored in the external storage chip through the communication connection link, so that the external storage of the firmware data is realized, the reliability of the data storage is improved, and the stability of the performance of the server is further ensured.
In some specific embodiments, the link creation module 11 may specifically include:
a first link creation unit for creating a communication connection link between a baseboard management controller of the server and an embedded multimedia card;
accordingly, the data acquisition module 12 may specifically include:
and the data acquisition unit is used for acquiring the target firmware data stored in the temporary storage area in the baseboard management controller.
In some specific embodiments, the data storage module 13 may specifically include:
and the data storage unit is used for transmitting the target firmware data to the embedded multimedia card for storage through the communication connection link, so that the baseboard management controller can acquire the target firmware data in a mode of reading the data from the embedded multimedia card after the data loss event occurs in the temporary storage area, the recovery area and the active area.
In some specific embodiments, after the data saving unit, the method specifically may further include:
and the first data recovery unit is used for carrying out data recovery on the temporary storage area, the recovery area and the active area in the baseboard management controller by utilizing the target firmware data read from the embedded multimedia card.
In some specific embodiments, the first data recovery unit may specifically include:
a second data recovery unit, configured to perform data recovery on the temporary storage area of the baseboard management controller by using the target firmware data read from the embedded multimedia card;
a third data recovery unit, configured to recover a recovery area of the baseboard management controller by using the recovered temporary storage area;
and a fourth data recovery unit, configured to recover an active area of the baseboard management controller by using the recovered recovery area, so as to start the baseboard management controller by using the recovered active area.
In some specific embodiments, the link creation module 11 may specifically include:
the program loading unit is used for acquiring a driving program of an external storage chip after the target component is started and loading the driving program through the target component;
and the second link creation unit is used for mounting the external storage chip to the target component after the driver is loaded so as to build a communication connection link between the target component of the server and the external storage chip.
Further, the embodiment of the present application further discloses an electronic device, and fig. 8 is a block diagram of an electronic device 20 according to an exemplary embodiment, where the content of the diagram is not to be considered as any limitation on the scope of use of the present application.
Fig. 8 is a schematic structural diagram of an electronic device 20 according to an embodiment of the present application. The electronic device 20 may specifically include: at least one processor 21, at least one memory 22, a power supply 23, a communication interface 24, an input output interface 25, and a communication bus 26. Wherein the memory 22 is configured to store a computer program that is loaded and executed by the processor 21 to implement relevant steps in the server firmware data storage method disclosed in any of the foregoing embodiments. In addition, the electronic device 20 in the present embodiment may be specifically an electronic computer.
In this embodiment, the power supply 23 is configured to provide an operating voltage for each hardware device on the electronic device 20; the communication interface 24 can create a data transmission channel between the electronic device 20 and an external device, and the communication protocol to be followed is any communication protocol applicable to the technical solution of the present application, which is not specifically limited herein; the input/output interface 25 is used for acquiring external input data or outputting external output data, and the specific interface type thereof may be selected according to the specific application requirement, which is not limited herein.
The memory 22 may be a carrier for storing resources, such as a read-only memory, a random access memory, a magnetic disk, or an optical disk, and the resources stored thereon may include an operating system 221, a computer program 222, and the like, and the storage may be temporary storage or permanent storage.
The operating system 221 is used for managing and controlling various hardware devices on the electronic device 20 and computer programs 222, which may be Windows Server, netware, unix, linux, etc. The computer program 222 may further include a computer program that can be used to perform other specific tasks in addition to the computer program that can be used to perform the server firmware data storage method performed by the electronic device 20 as disclosed in any of the previous embodiments.
Further, the application also discloses a computer readable storage medium for storing a computer program; wherein the computer program, when executed by a processor, implements the previously disclosed server firmware data storage method. For specific steps of the method, reference may be made to the corresponding contents disclosed in the foregoing embodiments, and no further description is given here.
In this specification, each embodiment is described in a progressive manner, and each embodiment is mainly described in a different point from other embodiments, so that the same or similar parts between the embodiments are referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant points refer to the description of the method section.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative elements and steps are described above generally in terms of functionality in order to clearly illustrate the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. The software modules may be disposed in Random Access Memory (RAM), memory, read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
Finally, it is further noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The foregoing has described in detail the method, apparatus, device and medium for storing server firmware data, and specific examples have been applied to illustrate the principles and embodiments of the present application, and the above description of the embodiments is only for helping to understand the method and core idea of the present application; meanwhile, as those skilled in the art will have variations in the specific embodiments and application scope in accordance with the ideas of the present application, the present description should not be construed as limiting the present application in view of the above.
Claims (8)
1. A method for storing server firmware data, applied to a server, comprising:
creating a communication connection link between a target component of the server and an external storage chip; the target component is a component supporting a platform firmware protection recovery function in the server;
acquiring target firmware data stored in a temporary storage area in the target component;
transmitting the target firmware data to the external memory chip through the communication connection link for storage, so that the target component acquires the target firmware data in a mode of reading data from the external memory chip after a data loss event occurs in the temporary storage area;
the creating a communication connection link between the target component of the server and an external storage chip includes: creating a communication connection link between a baseboard management controller of the server and an embedded multimedia card;
correspondingly, the obtaining the target firmware data stored in the temporary storage area in the target component includes: acquiring target firmware data stored in a temporary storage area in the baseboard management controller;
the transmitting the target firmware data to the external memory chip through the communication connection link for storage, so that the target component obtains the target firmware data by reading data from the external memory chip after the data loss event occurs in the temporary storage area, including:
and transmitting the target firmware data to the embedded multimedia card for storage through the communication connection link, so that the baseboard management controller can acquire the target firmware data in a mode of reading the data from the embedded multimedia card after the data loss event occurs in the temporary storage area, the recovery area and the active area.
2. The method for storing firmware data of a server according to claim 1, wherein after the target firmware data is obtained by reading data from the embedded multimedia card, further comprising:
and carrying out data recovery on the temporary storage area, the recovery area and the active area in the baseboard management controller by using the target firmware data read from the embedded multimedia card.
3. The server firmware data storage method of claim 2, wherein the data recovery of the temporary storage area, the recovery area, and the active area in the baseboard management controller using the target firmware data read from the embedded multimedia card comprises:
performing data recovery on the temporary storage area of the baseboard management controller by using the target firmware data read from the embedded multimedia card;
restoring the restoration area of the baseboard management controller by using the restored temporary storage area;
and restoring the active area of the baseboard management controller by using the restored active area so as to start the baseboard management controller by using the restored active area.
4. A server firmware data storage method according to any one of claims 1 to 3, wherein said creating a communication connection link between a target component of said server and an external storage chip comprises:
after the target component is started, a driving program of an external storage chip is obtained, and the driving program is loaded through the target component;
and after the driver is loaded, the external storage chip is mounted to the target component so as to build a communication connection link between the target component of the server and the external storage chip.
5. A method for starting up a server component, which is applied to a server and comprises the following steps:
judging whether the active area of the target component in the server is damaged or not; the target component is a component supporting a platform firmware protection recovery function in the server; the target component is a baseboard management controller;
if the active area is damaged, judging whether the recovery area and the temporary storage area of the baseboard management controller are damaged or not;
if the temporary storage area and the recovery area are damaged, reading pre-stored target firmware data from an embedded multimedia card, and starting the baseboard management controller by utilizing the target firmware data; the target firmware data are firmware data which are transmitted from the temporary storage area to the embedded multimedia card through a communication connection link to be stored when the temporary storage area is not damaged in advance; the communication connection link is a communication connection link between the baseboard management controller and the embedded multimedia card, which is created in advance.
6. A server firmware data storage device, for application to a server, comprising:
the link creation module is used for creating a communication connection link between a target component of the server and an external storage chip; the target component is a component supporting a platform firmware protection recovery function in the server;
the data acquisition module is used for acquiring target firmware data stored in the temporary storage area in the target component;
the data storage module is used for transmitting the target firmware data to the external storage chip for storage through the communication connection link, so that the target assembly can acquire the target firmware data in a mode of reading the data from the external storage chip after a data loss event occurs in the temporary storage area;
the link creation module is specifically configured to: creating a communication connection link between a baseboard management controller of the server and an embedded multimedia card;
correspondingly, the data acquisition module is specifically configured to: acquiring target firmware data stored in a temporary storage area in the baseboard management controller;
the data storage module is specifically configured to: and transmitting the target firmware data to the embedded multimedia card for storage through the communication connection link, so that the baseboard management controller can acquire the target firmware data in a mode of reading the data from the embedded multimedia card after the data loss event occurs in the temporary storage area, the recovery area and the active area.
7. An electronic device comprising a processor and a memory; wherein the processor, when executing the computer program instructions stored in the memory, implements a server firmware data storage method as claimed in any one of claims 1 to 4.
8. A computer readable storage medium for storing computer program instructions; wherein the computer program instructions, when executed by a processor, implement a server firmware data storage method as claimed in any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111062571.4A CN113849432B (en) | 2021-09-10 | 2021-09-10 | Server firmware data storage method, starting method, device, equipment and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111062571.4A CN113849432B (en) | 2021-09-10 | 2021-09-10 | Server firmware data storage method, starting method, device, equipment and medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113849432A CN113849432A (en) | 2021-12-28 |
| CN113849432B true CN113849432B (en) | 2023-08-15 |
Family
ID=78973540
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111062571.4A Active CN113849432B (en) | 2021-09-10 | 2021-09-10 | Server firmware data storage method, starting method, device, equipment and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113849432B (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN209821732U (en) * | 2019-03-26 | 2019-12-20 | 南京铁道职业技术学院 | Pull formula computer mainframe of convenient maintenance |
| CN112134448A (en) * | 2020-08-04 | 2020-12-25 | 华为技术有限公司 | Server and data center |
-
2021
- 2021-09-10 CN CN202111062571.4A patent/CN113849432B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN209821732U (en) * | 2019-03-26 | 2019-12-20 | 南京铁道职业技术学院 | Pull formula computer mainframe of convenient maintenance |
| CN112134448A (en) * | 2020-08-04 | 2020-12-25 | 华为技术有限公司 | Server and data center |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113849432A (en) | 2021-12-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20170116084A1 (en) | Method and System for Monitoring Virtual Machine Cluster | |
| US8806265B2 (en) | LPAR creation and repair for automated error recovery | |
| JP5183542B2 (en) | Computer system and setting management method | |
| CN106547645B (en) | Method for automatically restoring image file and server system | |
| CN110413432B (en) | Information processing method, electronic equipment and storage medium | |
| CN112769652B (en) | Node service monitoring method, device, equipment and medium | |
| CN111581021B (en) | Application program starting abnormality repairing method, device, equipment and storage medium | |
| CN113672306B (en) | Server component self-checking abnormity recovery method, device, system and medium | |
| US7546604B2 (en) | Program reactivation using triggering | |
| EP2860633A1 (en) | Method for maintaining file system of computer system | |
| CN113849432B (en) | Server firmware data storage method, starting method, device, equipment and medium | |
| WO2024119787A1 (en) | Method and apparatus for amd server system installation power-off processing, device and medium | |
| CN115098294B (en) | Abnormal event processing method, electronic equipment and management terminal | |
| CN112445549A (en) | Operation and maintenance method, operation and maintenance device, electronic equipment and medium | |
| CN115964108A (en) | Cloud desktop destroying method and device, electronic equipment and storage medium | |
| CN113687867B (en) | Shutdown method, system, equipment and storage medium of cloud platform cluster | |
| CN110289977B (en) | Fault detection method, system, equipment and storage medium for logistics warehouse system | |
| CN113515291A (en) | Equipment online upgrading method and device | |
| JP2002229798A (en) | Computer system, its bios management method, and bios management program | |
| CN108509252B (en) | Virtual machine starting device and method and host | |
| CN111400094A (en) | Method, device, equipment and medium for restoring factory settings of server system | |
| JP5268820B2 (en) | Rewriting method for monitoring device program | |
| CN110868764A (en) | Wireless connection self-recovery method, device, equipment and storage medium | |
| CN112988247B (en) | Log processing method and device, electronic equipment and readable storage medium | |
| WO2024121952A1 (en) | Failure restoration expediting system, failure restoration expediting method, and failure restoration expediting program |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |