A lithium battery detection terminal system fault self-recovery method and system

By regularly backing up and verifying the system files of the lithium battery detection terminal at startup, automatic fault recovery is achieved, and the failure problems caused by limited number of Nand flash burns and user misoperation are solved, improving stability and reducing maintenance costs , while enhancing security.

CN114185706BActive Publication Date: 2024-12-06FUJIAN NEBULA ELECTRONICS CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202111341300.2
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-11-12
Publication Date
2024-12-06
Estimated Expiration
2041-11-12

AI Technical Summary

Technical Problem

The lithium battery detection terminal has a system failure caused by the limited number of Nand flash burns and user misoperation, resulting in the system being unable to start normally or the maintenance cost is high.

Method used

By regularly backing up system kernel files, key system files and application data, and using verification algorithms to verify these files at startup. If the verification fails, restore the backup data to restart the system until all files pass the verification, and achieve Automatic fault recovery of the system.

Benefits of technology

It improves the operating stability of the lithium battery detection terminal, reduces maintenance and hardware costs, and enhances security through different verification algorithms.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114185706B_ABST
    Figure CN114185706B_ABST
Patent Text Reader

Abstract

The present invention provides a lithium battery detection terminal system fault self-recovery method and system in the field of lithium battery technology, the method comprising: step S10, regularly backing up backup data; step S20, reading the system kernel after the lithium battery detection terminal is powered on; step S30, verifying the system kernel files carried by the system kernel through a verification algorithm, and after recovering the system kernel files that failed the verification through backup data, mounting the root file system to the system kernel; step S40, verifying the key system files carried by the root file system through a verification algorithm, and after recovering the key system files that failed the verification through backup data, mounting the application to the system kernel; step S50, verifying the application through a verification algorithm, and after recovering the application that failed the verification through backup data, the system starts normally. The advantages of the present invention are: greatly improving the stability of the operation of the lithium battery detection terminal and greatly reducing the maintenance cost.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of lithium battery technology, and in particular to a lithium battery detection terminal system fault self-recovery method and system. Background Art

[0002] Lithium battery testing terminals mostly use Flash chips to store non-volatile data. The types of Flash chips include Norflash and Nand flash. Although Nor flash has no problem of limited number of burn-in and write-out times, it is expensive and not suitable for storing large-capacity non-volatile data in lithium battery testing terminals. Nand flash is suitable for storing large-capacity non-volatile data in lithium battery testing terminals because of its low cost, but due to its physical and process characteristics, it has problems of limited number of burn-in and write-out times and bad blocks.

[0003] Although there are processing mechanisms for Nand flash defects in hardware drivers and file systems, in actual applications, system failures of lithium battery detection terminals are still frequently caused, resulting in the system being unable to start normally or not working properly. In addition, user misoperation in actual use may also cause system files or configuration files to be missing, thus causing system failures.

[0004] In case of system failure of lithium battery detection terminal, after-sales maintenance personnel traditionally need to re-burn the system firmware of lithium battery detection terminal, which is time-consuming and labor-intensive. In addition, the application range of lithium battery detection terminal is wide, resulting in extremely high cost of fault maintenance. Therefore, how to provide a lithium battery detection terminal system fault self-recovery method and system to improve the stability of lithium battery detection terminal operation and reduce maintenance costs has become a technical problem to be solved urgently. Summary of the invention

[0005] The technical problem to be solved by the present invention is to provide a method and system for self-recovery of a lithium battery detection terminal system fault, so as to improve the stability of the operation of the lithium battery detection terminal and reduce the maintenance cost.

[0006] In a first aspect, the present invention provides a method for self-recovery of a lithium battery detection terminal system fault, comprising the following steps:

[0007] Step S10: The lithium battery detection terminal regularly backs up the backup data including system kernel files, key system files and applications;

[0008] Step S20: After the lithium battery detection terminal is powered on and started, the boot program is automatically run, and the system kernel of each partition is read into the memory through the boot program;

[0009] Step S30, verifying the system kernel files carried by the system kernel of each partition by using a first verification algorithm, restoring the system kernel files that failed the verification by using the backup data, and then mounting each root file system to the system kernel of the corresponding partition;

[0010] Step S40: verifying the key system files carried by each of the root file systems using a second verification algorithm, restoring the key system files that failed the verification using the backup data, and then mounting each application into the system kernel of the corresponding partition;

[0011] Step S50: verify the applications in each partition in turn using a third verification algorithm, and after restoring the applications that failed the verification using the backup data, the system startup of the lithium battery detection terminal is completed.

[0012] Furthermore, the step S10 is specifically as follows:

[0013] The lithium battery detection terminal creates a backup cycle and a backup path, and regularly backs up the backup data to the backup path based on the backup cycle;

[0014] The backup data includes system kernel files, key system files and applications.

[0015] Furthermore, the step S30 specifically includes:

[0016] Step S31, calculating the system kernel file carried by the system kernel of each partition by a first verification algorithm to obtain a first verification code, and determining whether the first verification code is consistent with the verification code carried by the system kernel file. If so, the verification passes, and the process proceeds to step S33; if not, the verification fails, and the process proceeds to step S32;

[0017] Step S32: After restoring the system kernel file that failed verification through the backup data, the system is automatically restarted and the process goes to step S20;

[0018] Step S33: Mount each root file system into the system kernel of the corresponding partition.

[0019] Furthermore, the step S40 specifically includes:

[0020] Step S41, calculating the second verification code for the key system files carried by each of the root file systems by a second verification algorithm, and determining whether the second verification code is consistent with the verification code carried by the key system files. If so, the verification passes, and the process proceeds to step S43; if not, the verification fails, and the process proceeds to step S42;

[0021] Step S42: After restoring the critical system files that failed verification through the backup data, the system is automatically restarted and the process proceeds to step S20;

[0022] Step S43: Mount each application into the system kernel of the corresponding partition.

[0023] Furthermore, the step S50 specifically includes:

[0024] Step S51, obtaining the mount status identifier of each partition, and judging whether all applications have been mounted based on the mount status identifier, if so, proceeding to step S52; if not, continuing to mount the remaining applications, and proceeding to step S52 after updating the mount status identifier;

[0025] Step S52: Pack all applications of each partition into an application package, calculate each application package in turn by a third verification algorithm to obtain a third verification code, and determine whether the third verification code is consistent with the verification code pre-calculated in the application package. If so, the verification passes, and the system startup of the lithium battery detection terminal is completed; if not, the verification fails, and the process goes to step S52;

[0026] Step S52: After all applications in the application package that failed verification are restored through the backup data, the system is automatically restarted and the process proceeds to step S20.

[0027] In a second aspect, the present invention provides a lithium battery detection terminal system fault self-recovery system, comprising the following modules:

[0028] The data backup module is used for the lithium battery detection terminal to regularly back up the backup data including system kernel files, key system files and applications;

[0029] The system kernel reading module is used to automatically run the boot program after the lithium battery detection terminal is powered on and starts, and read the system kernel of each partition into the memory through the boot program;

[0030] A system kernel file verification module, used to verify the system kernel files carried by the system kernel of each partition by using a first verification algorithm, and after restoring the system kernel files that failed the verification by using the backup data, mount each root file system to the system kernel of the corresponding partition;

[0031] Critical system file verification, used to verify the critical system files carried by each of the root file systems using a second verification algorithm, and after recovering the critical system files that failed the verification using the backup data, mount each application into the system kernel of the corresponding partition;

[0032] The application verification module is used to verify the applications of each partition in turn through a third verification algorithm, and after restoring the applications that failed the verification through the backup data, the system startup of the lithium battery detection terminal is completed.

[0033] Furthermore, the data backup module is specifically:

[0034] The lithium battery detection terminal creates a backup cycle and a backup path, and regularly backs up the backup data to the backup path based on the backup cycle;

[0035] The backup data includes system kernel files, key system files and applications.

[0036] Furthermore, the system kernel file verification module specifically includes:

[0037] A first verification unit, configured to calculate a first verification code for a system kernel file carried by the system kernel of each partition by using a first verification algorithm, and determine whether the first verification code is consistent with the verification code carried by the system kernel file. If so, the verification passes and the root file system mounting unit is entered; if not, the verification fails and the system kernel file recovery unit is entered;

[0038] A system kernel file recovery unit, used to automatically restart the system and enter the system kernel reading module after recovering the system kernel file that failed verification through the backup data;

[0039] The root file system mounting unit is used to mount each root file system into the system kernel of the corresponding partition.

[0040] Furthermore, the key system file verification specifically includes:

[0041] a second verification unit, configured to calculate a second verification code for the key system files carried by each of the root file systems by a second verification algorithm, and determine whether the second verification code is consistent with the verification code carried by the key system files; if so, the verification passes and the application mounting unit is entered; if not, the verification fails and the key system file recovery unit is entered;

[0042] A key system file recovery unit, used to automatically restart the system and enter the system kernel reading module after recovering the key system files that failed verification through the backup data;

[0043] The application mounting unit is used to mount each application into the system kernel of the corresponding partition.

[0044] Furthermore, the application verification module specifically includes:

[0045] A mount status identification verification unit, used to obtain the mount status identification of each partition, and determine whether the mounting of all applications is completed based on the mount status identification, and if so, enter the third verification unit; if not, continue to mount the remaining applications, and enter the third verification unit after updating the mount status identification;

[0046] A third verification unit is used to package all applications of each partition into an application package, calculate each application package in turn by a third verification algorithm to obtain a third verification code, and determine whether the third verification code is consistent with the verification code pre-calculated in the application package. If so, the verification passes and the system startup of the lithium battery detection terminal is completed; if not, the verification fails and enters the application recovery unit;

[0047] The application recovery unit is used to automatically restart the system and enter the system kernel reading module after recovering all applications in the application package that failed verification through the backup data.

[0048] The advantages of the present invention are:

[0049] 1. Regularly back up system kernel files, key system files and applications, and use verification algorithms to verify system kernel files, key system files and applications in turn when the system starts. If the verification fails, it means that the file is damaged. After the corresponding file is restored using the backup data, the system is automatically restarted for re-verification until the system kernel files, key system files and applications are all verified and passed. The system is started normally. That is, when any file among the system kernel files, key system files and applications is damaged, the backup data can be used for automatic recovery and restart, without the need to re-burn the system firmware as traditionally, so that Nand flash can also be well used, which ultimately greatly improves the stability of the lithium battery detection terminal and greatly reduces the maintenance cost and hardware cost.

[0050] 2. Since a system contains a large number of applications, the efficiency of application verification is greatly improved by packaging all applications in each partition into application packages for unified calculation and verification.

[0051] 3. The system kernel files, key system files and applications are verified respectively by the first verification algorithm, the second verification algorithm and the third verification algorithm. That is, it is not limited to use the same verification algorithm. Different verification algorithms can be used as needed to verify the system kernel files, key system files and applications, which increases the difficulty of cracking the verification algorithm and greatly improves security. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] The present invention will be further described below in conjunction with embodiments with reference to the accompanying drawings.

[0053] Figure 1The present invention is a flow chart of a lithium battery detection terminal system fault self-recovery method.

[0054] Figure 2 The present invention is a flowchart of a method for self-recovery of a lithium battery detection terminal system fault.

[0055] Figure 3 It is a structural schematic diagram of a lithium battery detection terminal system fault self-recovery system of the present invention. DETAILED DESCRIPTION

[0056] The technical solution in the embodiment of the present application has the following overall idea: when the system starts, the system kernel files, key system files and applications are checked in turn using a verification algorithm. If the verification fails, it means that the file is damaged. After the corresponding file is restored using the backup data, the system is automatically restarted for re-verification until the system kernel files, key system files and applications are all verified and passed. Then the system is started normally to improve the stability of the operation of the lithium battery detection terminal and reduce maintenance costs.

[0057] Please refer to Figures 1 to 3 As shown, a preferred embodiment of a lithium battery detection terminal system fault self-recovery method of the present invention includes the following steps:

[0058] Step S10: The lithium battery detection terminal regularly backs up the backup data including system kernel files, key system files and applications;

[0059] Step S20: After the lithium battery detection terminal is powered on and started, the system automatically runs a bootloader, and reads the system kernel of each partition into the memory through the bootloader;

[0060] Step S30, verifying the system kernel files carried by the system kernel of each partition by using a first verification algorithm, restoring the system kernel files that failed the verification by using the backup data, and mounting each root file system (root file system) to the system kernel of the corresponding partition;

[0061] Step S40: verifying the key system files carried by each of the root file systems using a second verification algorithm, restoring the key system files that failed the verification using the backup data, and then mounting each application into the system kernel of the corresponding partition;

[0062] Step S50: verify the applications in each partition in turn using a third verification algorithm, and after restoring the applications that failed the verification using the backup data, the system startup of the lithium battery detection terminal is completed.

[0063] The first verification algorithm, the second verification algorithm and the third verification algorithm are not limited to any algorithm, for example, they can be selected from CRC32, DM5 or SHA-1 as needed. The use of different verification algorithms can increase the difficulty of cracking the verification algorithm, thereby improving security.

[0064] The step S10 is specifically as follows:

[0065] The lithium battery detection terminal creates a backup cycle and a backup path, and regularly (periodically) backs up the backup data to the backup path based on the backup cycle; in specific implementation, the backup data can be encrypted to improve data security;

[0066] The backup data includes system kernel files, key system files and applications.

[0067] The step S30 specifically includes:

[0068] Step S31, calculating the system kernel file carried by the system kernel of each partition by a first verification algorithm to obtain a first verification code, and determining whether the first verification code is consistent with the verification code carried by the system kernel file. If so, the verification passes, and the process proceeds to step S33; if not, the verification fails, and the process proceeds to step S32;

[0069] Step S32: After restoring the system kernel file that failed verification through the backup data, the system is automatically restarted and the process goes to step S20;

[0070] Step S33: Mount each root file system into the system kernel of the corresponding partition.

[0071] The step S40 specifically includes:

[0072] Step S41, calculating the second verification code for the key system files carried by each of the root file systems by a second verification algorithm, and determining whether the second verification code is consistent with the verification code carried by the key system files. If so, the verification passes, and the process proceeds to step S43; if not, the verification fails, and the process proceeds to step S42;

[0073] Step S42: After restoring the critical system files that failed verification through the backup data, the system is automatically restarted and the process proceeds to step S20;

[0074] Step S43: Mount each application into the system kernel of the corresponding partition. For example, mount different applications into the APP partition, DADA partition, CONF partition, etc.

[0075] The step S50 specifically includes:

[0076] Step S51, obtaining the mount status identifier of each partition, and judging whether all applications have been mounted based on the mount status identifier, if so, proceeding to step S52; if not, continuing to mount the remaining applications, and after updating the mount status identifier, proceeding to step S52; the mount status identifier is used to identify whether all applications have been mounted;

[0077] Step S52: All applications of each partition are packaged into application packages respectively, and a third verification code is calculated for each application package in turn by a third verification algorithm to determine whether the third verification code is consistent with the verification code pre-calculated in the application package. If so, the verification is passed, and the system startup of the lithium battery detection terminal is completed; if not, the verification fails, and the process goes to step S52;

[0078] Step S52: After all applications in the application package that failed verification are restored through the backup data, the system is automatically restarted and the process proceeds to step S20.

[0079] That is, the application package of the first partition is verified first, and if the verification is passed, the application package of the second partition is verified, and if the verification is passed, the application package of the third partition is verified, and so on.

[0080] A preferred embodiment of a lithium battery detection terminal system fault self-recovery system of the present invention includes the following modules:

[0081] The data backup module is used for the lithium battery detection terminal to regularly back up the backup data including system kernel files, key system files and applications;

[0082] The system kernel reading module is used for automatically running the bootloader after the lithium battery detection terminal is powered on, and reading the system kernel of each partition into the memory through the bootloader;

[0083] a system kernel file verification module, configured to verify the system kernel files carried by the system kernel of each partition by using a first verification algorithm, and after restoring the system kernel files that failed the verification by using the backup data, mount each root file system into the system kernel of the corresponding partition;

[0084] Critical system file verification, used to verify the critical system files carried by each of the root file systems using a second verification algorithm, and after recovering the critical system files that failed the verification using the backup data, mount each application into the system kernel of the corresponding partition;

[0085] The application verification module is used to verify the applications of each partition in turn through a third verification algorithm, and after restoring the applications that failed the verification through the backup data, the system startup of the lithium battery detection terminal is completed.

[0086] The first verification algorithm, the second verification algorithm and the third verification algorithm are not limited to any algorithm, for example, they can be selected from CRC32, DM5 or SHA-1 as needed. The use of different verification algorithms can increase the difficulty of cracking the verification algorithm, thereby improving security.

[0087] The data backup module is specifically:

[0088] The lithium battery detection terminal creates a backup cycle and a backup path, and regularly (periodically) backs up the backup data to the backup path based on the backup cycle; in specific implementation, the backup data can be encrypted to improve data security;

[0089] The backup data includes system kernel files, key system files and applications.

[0090] The system kernel file verification module specifically includes:

[0091] A first verification unit, configured to calculate a first verification code for a system kernel file carried by the system kernel of each partition by using a first verification algorithm, and determine whether the first verification code is consistent with the verification code carried by the system kernel file. If so, the verification passes and the root file system mounting unit is entered; if not, the verification fails and the system kernel file recovery unit is entered;

[0092] A system kernel file recovery unit, used to automatically restart the system and enter the system kernel reading module after recovering the system kernel file that failed verification through the backup data;

[0093] The root file system mounting unit is used to mount each root file system into the system kernel of the corresponding partition.

[0094] The key system file verification specifically includes:

[0095] a second verification unit, configured to calculate a second verification code for the key system files carried by each of the root file systems by a second verification algorithm, and determine whether the second verification code is consistent with the verification code carried by the key system files; if so, the verification passes and the application mounting unit is entered; if not, the verification fails and the key system file recovery unit is entered;

[0096] A key system file recovery unit, used to automatically restart the system and enter the system kernel reading module after recovering the key system files that failed verification through the backup data;

[0097] The application mounting unit is used to mount each application into the system kernel of the corresponding partition. For example, different applications are mounted into the APP partition, DADA partition, CONF partition and other partitions.

[0098] The application verification module specifically includes:

[0099] A mount status identification verification unit, used to obtain the mount status identification of each partition, and judge whether the mounting of all applications is completed based on the mount status identification, and if so, enter the third verification unit; if not, continue to mount the remaining applications, and enter the third verification unit after updating the mount status identification; the mount status identification is used to identify whether all applications have been mounted;

[0100] A third verification unit is used to package all applications of each partition into application packages respectively, calculate each application package in turn by a third verification algorithm to obtain a third verification code, and determine whether the third verification code is consistent with the verification code pre-calculated in the application package. If so, the verification passes and the system startup of the lithium battery detection terminal is completed; if not, the verification fails and enters the application recovery unit;

[0101] The application recovery unit is used to automatically restart the system and enter the system kernel reading module after recovering all applications in the application package that failed verification through the backup data.

[0102] That is, the application package of the first partition is verified first, and if the verification is passed, the application package of the second partition is verified, and if the verification is passed, the application package of the third partition is verified, and so on.

[0103] In summary, the advantages of the present invention are:

[0104] 1. Regularly back up system kernel files, key system files and applications, and use verification algorithms to verify system kernel files, key system files and applications in turn when the system starts. If the verification fails, it means that the file is damaged. After the corresponding file is restored using the backup data, the system is automatically restarted for re-verification until the system kernel files, key system files and applications are all verified and passed. The system is started normally. That is, when any file among the system kernel files, key system files and applications is damaged, the backup data can be used for automatic recovery and restart, without the need to re-burn the system firmware as traditionally, so that Nand flash can also be well used, which ultimately greatly improves the stability of the lithium battery detection terminal and greatly reduces the maintenance cost and hardware cost.

[0105] 2. Since a system contains a large number of applications, the efficiency of application verification is greatly improved by packaging all applications in each partition into application packages for unified calculation and verification.

[0106] 3. The system kernel files, key system files and applications are verified respectively by the first verification algorithm, the second verification algorithm and the third verification algorithm. That is, it is not limited to use the same verification algorithm. Different verification algorithms can be used as needed to verify the system kernel files, key system files and applications, which increases the difficulty of cracking the verification algorithm and greatly improves security.

[0107] Although the specific implementation modes of the present invention are described above, those skilled in the art should understand that the specific implementation modes described are only illustrative and are not intended to limit the scope of the present invention. Equivalent modifications and changes made by those skilled in the art in accordance with the spirit of the present invention should be included in the scope of protection of the claims of the present invention.

Claims

1. A lithium battery detection terminal system fault self-recovery method, characterized in that: The steps include: Step S10: The lithium battery detection terminal regularly backs up the backup data including system kernel files, key system files and applications; Step S20: After the lithium battery detection terminal is powered on and started, the boot program is automatically run, and the system kernel of each partition is read into the memory through the boot program; Step S30, verifying the system kernel files carried by the system kernel of each partition by using a first verification algorithm, restoring the system kernel files that failed the verification by using the backup data, and then mounting each root file system to the system kernel of the corresponding partition; Step S40: verifying the key system files carried by each of the root file systems using a second verification algorithm, restoring the key system files that failed the verification using the backup data, and then mounting each application into the system kernel of the corresponding partition; Step S50: verify the applications of each partition in turn by using a third verification algorithm, and after restoring the applications that failed the verification by using the backup data, complete the startup of the system of the lithium battery detection terminal; The step S30 specifically includes: Step S31, calculating the system kernel file carried by the system kernel of each partition by a first verification algorithm to obtain a first verification code, and determining whether the first verification code is consistent with the verification code carried by the system kernel file. If so, the verification passes, and the process proceeds to step S33; if not, the verification fails, and the process proceeds to step S32; Step S32: After restoring the system kernel file that failed verification through the backup data, the system is automatically restarted and the process goes to step S20; Step S33, mounting each root file system into the system kernel of the corresponding partition; The step S40 specifically includes: Step S41, calculating the second verification code for the key system files carried by each of the root file systems by a second verification algorithm, and determining whether the second verification code is consistent with the verification code carried by the key system files. If so, the verification passes, and the process proceeds to step S43; if not, the verification fails, and the process proceeds to step S42; Step S42: After restoring the critical system files that failed verification through the backup data, the system is automatically restarted and the process proceeds to step S20; Step S43, mounting each application into the system kernel of the corresponding partition; The step S50 specifically includes: Step S51, obtaining the mount status identifier of each partition, and judging whether all applications have been mounted based on the mount status identifier, if so, proceeding to step S52; if not, continuing to mount the remaining applications, and proceeding to step S52 after updating the mount status identifier; Step S52: Pack all applications of each partition into an application package, calculate each application package in turn by a third verification algorithm to obtain a third verification code, and determine whether the third verification code is consistent with the verification code pre-calculated in the application package. If so, the verification passes, and the system startup of the lithium battery detection terminal is completed; if not, the verification fails, and the process goes to step S52; Step S52: After all applications in the application package that failed verification are restored through the backup data, the system is automatically restarted and the process proceeds to step S20.

2. A lithium battery detection terminal system fault self-recovery method as claimed in claim 1, characterized in that: The step S10 is specifically as follows: The lithium battery detection terminal creates a backup cycle and a backup path, and regularly backs up the backup data to the backup path based on the backup cycle; The backup data includes system kernel files, key system files and applications.

3. A lithium battery detection terminal system fault self-recovery system, characterized by: Includes the following modules: The data backup module is used for the lithium battery detection terminal to regularly back up the backup data including system kernel files, key system files and applications; The system kernel reading module is used to automatically run the boot program after the lithium battery detection terminal is powered on and starts, and read the system kernel of each partition into the memory through the boot program; A system kernel file verification module, used to verify the system kernel files carried by the system kernel of each partition by using a first verification algorithm, and after restoring the system kernel files that failed the verification by using the backup data, mount each root file system to the system kernel of the corresponding partition; Critical system file verification, used to verify the critical system files carried by each of the root file systems using a second verification algorithm, and after recovering the critical system files that failed the verification using the backup data, mount each application into the system kernel of the corresponding partition; An application verification module, used to verify the applications of each partition in turn by using a third verification algorithm, and after restoring the applications that failed the verification by using the backup data, complete the startup of the system of the lithium battery detection terminal; The system kernel file verification module specifically includes: A first verification unit, configured to calculate a first verification code for a system kernel file carried by the system kernel of each partition by using a first verification algorithm, and determine whether the first verification code is consistent with the verification code carried by the system kernel file. If so, the verification passes and the root file system mounting unit is entered; if not, the verification fails and the system kernel file recovery unit is entered; A system kernel file recovery unit, used to automatically restart the system and enter the system kernel reading module after recovering the system kernel file that failed verification through the backup data; A root file system mounting unit is used to mount each root file system into the system kernel of the corresponding partition; The key system file verification specifically includes: a second verification unit, configured to calculate a second verification code for the key system files carried by each of the root file systems by a second verification algorithm, and determine whether the second verification code is consistent with the verification code carried by the key system files; if so, the verification passes and the application mounting unit is entered; if not, the verification fails and the key system file recovery unit is entered; A key system file recovery unit, used to automatically restart the system and enter the system kernel reading module after recovering the key system files that failed verification through the backup data; An application mounting unit, used to mount each application into the system kernel of the corresponding partition; The application verification module specifically includes: A mount status identification verification unit, used to obtain the mount status identification of each partition, and determine whether the mounting of all applications is completed based on the mount status identification, and if so, enter the third verification unit; if not, continue to mount the remaining applications, and enter the third verification unit after updating the mount status identification; A third verification unit is used to package all applications of each partition into an application package, calculate each application package in turn by a third verification algorithm to obtain a third verification code, and determine whether the third verification code is consistent with the verification code pre-calculated in the application package. If so, the verification passes and the system startup of the lithium battery detection terminal is completed; if not, the verification fails and enters the application recovery unit; The application recovery unit is used to automatically restart the system and enter the system kernel reading module after recovering all applications in the application package that failed verification through the backup data.

4. A lithium battery detection terminal system fault self-recovery system as claimed in claim 3, characterized in that: The data backup module is specifically: The lithium battery detection terminal creates a backup cycle and a backup path, and regularly backs up the backup data to the backup path based on the backup cycle; The backup data includes system kernel files, key system files and applications.