CN110795281A - File recovery method, device, equipment and storage medium - Google Patents
File recovery method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN110795281A CN110795281A CN201910973528.XA CN201910973528A CN110795281A CN 110795281 A CN110795281 A CN 110795281A CN 201910973528 A CN201910973528 A CN 201910973528A CN 110795281 A CN110795281 A CN 110795281A
- Authority
- CN
- China
- Prior art keywords
- configuration table
- file configuration
- file
- backup
- basic
- 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.)
- Pending
Links
Images
Classifications
-
- 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
- G06F11/1415—Saving, restoring, recovering or retrying at system level
- G06F11/1435—Saving, restoring, recovering or retrying at system level using file system or storage system metadata
-
- 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
- G06F11/1415—Saving, restoring, recovering or retrying at system level
- G06F11/1438—Restarting or rejuvenating
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/11—File system administration, e.g. details of archiving or snapshots
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/4401—Bootstrapping
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Quality & Reliability (AREA)
- Library & Information Science (AREA)
- Computer Security & Cryptography (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application provides a file recovery method, a file recovery device, equipment and a storage medium, wherein the method comprises the following steps: in the boot initialization stage of an embedded equipment system, confirming that the initialization of the embedded equipment system fails; acquiring a basic file configuration table and a backup file configuration table from a file system; the backup file configuration table is a backup of the base file configuration table; if the basic file configuration table is different from the backup file configuration table, restoring the basic file configuration table according to the backup file configuration table so as to initialize according to the restored basic file configuration table. The embedded device can automatically repair the damaged file configuration table in the system boot initialization stage, so that the operating system can be normally started, the service influence on the network device is reduced, the maintenance efficiency is improved, and the maintenance cost is reduced.
Description
Technical Field
The present application relates to the field of embedded technologies, and in particular, to a file recovery method, apparatus, device, and storage medium.
Background
With the continuous development of information technology, embedded technology has been applied to various fields. Before the embedded device runs, the embedded device needs to read and verify a system file in a system boot stage to complete initialization, so as to bring a system environment to a proper state and start an operating system to run. However, in the running process of the embedded device, due to abnormal operations (such as halt, power failure, etc.) and the vulnerability and instability of the system, system files in the file system are often damaged. For example, a file configuration table in a file system of an embedded device is damaged or a file data area is wrong, and both the damage of files of the embedded device and the file data area can cause initialization failure of the embedded device, so that the system cannot be started normally to affect normal service of network equipment.
In practice, the most reason for the failure of the initialization of the embedded device is the damage of the file configuration table in the file system. In the prior art, after the initialization of the embedded device fails in the system boot initialization stage, no matter the reason is that the file configuration table is damaged or the file data area is wrong, the disk needs to be dismounted again, and the system file is restored by using professional software. The method affects the normal service of the network equipment, improves the maintenance cost and has lower efficiency.
Disclosure of Invention
At least one embodiment of the present specification provides a file recovery scheme to implement automatic repair of a damaged file configuration table by an embedded device in a system boot initialization stage. Therefore, the operating system can be normally started, the service influence on the network equipment is reduced, the maintenance efficiency is improved, and the maintenance cost is reduced.
In a first aspect, a file recovery method is provided, which is applied to a boot initialization stage of an embedded device system, and includes:
confirming that initialization of the embedded equipment system fails;
acquiring a basic file configuration table and a backup file configuration table from a file system; the backup file configuration table is a backup of the base file configuration table;
if the basic file configuration table is different from the backup file configuration table, restoring the basic file configuration table according to the backup file configuration table so as to initialize according to the restored basic file configuration table.
In a second aspect, a file recovery apparatus is provided, which is applied to a boot initialization stage of an embedded device system, and the apparatus includes:
the confirmation module is used for confirming that the initialization of the embedded equipment system fails;
the acquisition module is used for acquiring a basic file configuration table and a backup file configuration table from a file system; the backup file configuration table is a backup of the base file configuration table;
and the recovery module is used for recovering the basic file configuration table according to the backup file configuration table when the basic file configuration table is different from the backup file configuration table so as to initialize according to the recovered basic file configuration table.
In a third aspect, a computer device is provided, which includes a memory, a processor, and a computer program stored on the memory and executable on the processor, and in a boot initialization stage of an embedded device system, the processor executes the computer program to implement the file recovery method according to any embodiment of the present specification.
In a fourth aspect, a computer-readable storage medium is provided, on which a computer program is stored, which program, when being executed by a processor, is adapted to carry out the steps of the method of any of the embodiments of the present description.
It can be seen from the above technical solutions that, in at least one embodiment of this specification, when the initialization of the embedded device fails in the system boot initialization stage, the basic file configuration table is automatically restored according to the backed-up file configuration table by comparing the backed-up file configuration table with the basic file configuration table, so that the initialization of the system environment is completed, and the operating system is normally started. In practice, most of the reasons causing initialization failure are that a file configuration table in a file system is damaged, so that a disk does not need to be detached to a great extent and a professional software is not used for recovering system files, thereby reducing the influence on the normal service of the on-line equipment, reducing the maintenance cost and improving the maintenance efficiency.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the specification.
Drawings
FIG. 1 is a flowchart illustrating a file recovery method according to an exemplary embodiment;
FIG. 2 is a flow diagram illustrating one implementation of confirming an initialization failure in accordance with an illustrative embodiment;
FIG. 3 is a flow diagram illustrating another implementation of validating an initialization failure in accordance with an illustrative embodiment;
FIG. 4 is a flowchart illustrating one implementation of obtaining a base file configuration table and a backup file configuration table in accordance with an illustrative embodiment;
FIG. 5 is a schematic diagram illustrating a file restore apparatus in accordance with an exemplary embodiment;
FIG. 6 is a schematic diagram of a validation module shown in accordance with an exemplary embodiment;
FIG. 7 is a schematic diagram illustrating an acquisition module according to an example embodiment.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present specification. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the specification, as detailed in the appended claims.
The terminology used in the description herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the description. As used in this specification and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It should be understood that although the terms first, second, third, etc. may be used herein to describe various information, these information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, the first information may also be referred to as second information, and similarly, the second information may also be referred to as first information, without departing from the scope of the present specification. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
In order to make the file recovery scheme clearer in at least one embodiment of the present specification, some related words are introduced.
The file system is a software mechanism in the operating system responsible for managing and storing file information, and is a system for organizing and allocating the space of the file storage device, and responsible for storing files and protecting and retrieving the stored files. In particular, it is responsible for creating files, storing, reading, modifying, dumping files, controlling the access of files for users. The FAT file system is one of the file systems commonly used for embedded devices, and often stores system files. The embedded device may be failed to initialize and the operating system may not be started normally due to the damage of the FAT Table (file allocation Table) in the FAT file system or the error of the file data area.
The FAT table is an index of the whole FAT file system file, and the correctness of the FAT table ensures the correctness of the data file management of the whole file system. If a disk is compared to a book, the FAT table can be considered to correspond to a directory in the book, and the file is the content of each chapter. In the FAT file system, files are stored in accordance with a clustered data structure defined in a FAT table. The FAT table records a storage chain table of disk data files, and is extremely important for reading data, so that Microsoft creates a backup for the FAT table in the FAT file system. As long as the FAT table is changed by normal system reading and writing, the backup FAT table is also updated, so that the contents of the backup FAT table and the FAT table are usually synchronized instantly.
And the cluster is the minimum unit for disk file storage management. A file is typically stored in one or more clusters, and the files are stored in a chain, so that a file is stored by a cluster chain. In the FAT file system, connection information between clusters on a hard disk is stored in an entry of a FAT table, and each entry records information of one cluster. The cluster information recorded in the FAT table entry can indicate that the current cluster is occupied, and the cluster can not be used any more; the mark 'bad cluster' can not be used any more; marking the cluster number of the next cluster, and jumping to the position of the next cluster to continue reading after the content of the current cluster is read; and marking the end of reading, and finishing the current reading operation. Because the connection information (FAT table) between clusters is stored in the hard disk, when an operating system reads a file, the operating system can always accurately find the position of each cluster and correctly read the position. The number of entries of the FAT is equivalent to the total cluster number on the hard disk, the number of bytes occupied by each entry is also suitable for the total cluster number, and the cluster number needs to be stored.
In the file recovery method provided in at least one embodiment of the present specification, when initialization fails in a boot initialization stage of an embedded device system, by comparing that a backup file configuration table is different from a basic file configuration table, the basic file configuration table is automatically recovered according to the backup file configuration table, so that initialization of the embedded device system is achieved, and an operating system can be normally started. In practice, most of the reason for the initialization failure of the embedded device is that the file configuration table is damaged, so the scheme can solve the problem of initialization failure to a great extent, thereby reducing the influence on the normal service of the on-line device, reducing the maintenance cost and improving the maintenance efficiency.
In one example, the system boot initialization phase of the embedded device is implemented by BootLoader bootstrap program. The Bootloader is a first section of code executed by the embedded system after power-on, and is used for initializing hardware equipment and establishing a memory space mapping diagram, so that the software and hardware environment of the system is brought to a proper state to start the operation system to run. If the initialization fails, the operating system cannot be started.
In order to make the file recovery scheme provided in this specification clearer, the following describes in detail the file recovery scheme execution process provided in this specification with reference to the accompanying drawings and specific embodiments:
referring to fig. 1, fig. 1 is a flowchart of a file recovery method according to an embodiment. The method is applied to the booting initialization stage of the embedded device system.
As shown in fig. 1, the process includes:
step 101, confirming that initialization of the embedded equipment system fails;
after the embedded device is started, initialization operation is first required to bring the software and hardware environment of the system to a proper state, so as to normally start the operating system.
In one example, the initializing the embedded device system may include reading a system file and verifying the read system file. The initialization failure in this step may include a failure to read a system file; reading the system file successfully, but verifying the read system file fails.
In one example, the embedded device system initialization failure is a failure in reading or verifying a system file due to a damaged file configuration table.
In one example, the embedded device system fails to initialize, and the file data area error causes a failure in reading or verifying the system file.
102, acquiring a basic file configuration table and a backup file configuration table from a file system; the backup file configuration table is a backup of the base file configuration table;
since the file configuration table is an index to the file system and is extremely important to the file system, there is typically an immediate update backup of the file configuration table. The file configuration table in actual use is called a basic file configuration table, and the file configuration table which plays a backup role is called a backup file configuration table.
In step 101, after the initialization of the embedded device system fails, a basic file configuration table and a backup file configuration table are automatically obtained from the file system. In practice, the most reason for the failure of the initialization of the embedded device system is the corruption of the base file configuration table. There are only a few cases where initialization fails due to a file data area error.
Step 103, if the basic file configuration table is different from the backup file configuration table, restoring the basic file configuration table according to the backup file configuration table, so as to initialize according to the restored basic file configuration table.
In this step, the basic file configuration table and the backup file configuration table acquired in step 102 are compared. And if the basic file configuration table is different from the backup file configuration table and the basic file configuration table can be considered damaged, restoring the basic file configuration table by using the backup file configuration table. And the embedded equipment is initialized again on the basis of the recovered basic file configuration table, and an operating system is started.
In one example, the base file configuration table is different from the backup file configuration table, including: and if the cluster chain in the table entry of the basic file configuration table is different from the cluster chain of the corresponding table entry in the backup file configuration table, determining that the basic file configuration table is different from the backup file configuration table. And the cluster is the minimum unit for disk file storage management. A file may be composed of multiple clusters, forming a cluster chain. For example, a file may be held by a cluster chain having a cluster number in the order "4-2-3-6". An entry in the file configuration table corresponds to a cluster, and information related to the corresponding cluster is stored in the entry, which may include: the address of the next cluster in the chain, an end of file symbol, a bad cluster symbol, a reserved cluster symbol or a free cluster symbol, etc.
In this embodiment, when the embedded device fails to initialize the system, the basic file configuration table and the backup file configuration table are obtained from the file system, and the damaged basic file configuration table is automatically recovered by using the backup file configuration table, so that initialization is completed and the operating system is started. Because the initialization failure is mostly caused by the damage of the basic file configuration table in practice, the scheme can automatically recover the damaged basic file configuration table, so that the problem of initialization failure in most cases can be solved. When the initialization of the embedded equipment system fails, the disk does not need to be dismounted every time to recover the system file by using the special software, so that the influence on the normal service of the on-line equipment is reduced, the maintenance cost is reduced, and the maintenance efficiency is improved.
Referring to fig. 2, fig. 2 is a flowchart of an implementation of step 101 provided in this specification. As shown in fig. 2, the process may include:
and the embedded equipment searches the corresponding file data area through a file configuration table in the file system at the system initialization stage and reads the corresponding file.
In one example, the embedded device queries a basic file configuration table FAT1 table in a FAT file system at a boot loader stage of the system, and searches and reads a file data area of a corresponding file according to the FAT1 table.
in the process of not reading the system file 201, if the read content cannot be identified, the information of failure in reading the system file is detected, and at this time, the initialization failure of the embedded device system can be confirmed.
In an example, when the embedded device fails to query a basic file configuration table FAT1 table in a FAT file system (the basic file configuration table is damaged) at a boot loader stage of the system, if information that reading of the system file fails is detected, it may be determined that initialization of the embedded device system fails.
In another example, the embedded device queries a basic file configuration table FAT1 table in a FAT file system in a BootLoader phase of the system, and searches and reads a file data area of a corresponding file according to the FAT1 table. And if the system file cannot be correctly identified when the content of the file data area is read, the information of failure in reading the system file can be detected, and the initialization failure of the embedded equipment system can be confirmed.
As shown in the flowchart of fig. 2, after detecting that reading the system file fails, it is determined that initializing the embedded device system in step 101 fails.
Referring to fig. 3, fig. 3 is a flowchart of another implementation of step 101 provided in this specification. As shown in fig. 3, the process may include:
the detailed method of this step is similar to step 201, and is not described herein again.
in the system initialization stage, after reading the system file, the embedded device needs to verify the read system file, and the initialization can be completed and the operating system can be normally started only if the verification is successful.
In one example, the embedded device queries a basic file configuration table FAT1 table in a FAT file system at a boot loader stage of the system, and searches and reads file data of a corresponding file according to the FAT1 table. And comparing the verification information in the FAT1 table of the basic file configuration table with the verification information of the corresponding file, wherein the comparison result is inconsistent, and the system file verification failure can be detected at this moment.
in step 302, the system file is checked, and if the check information in the basic file configuration table is inconsistent with the check information of the corresponding file, it may be detected that the system file fails to check.
In one example, the embedded device queries a basic file configuration table FAT1 table in a FAT file system at a boot loader stage of the system, and searches and reads file data of a corresponding file according to the FAT1 table. When the basic file configuration table FAT1 table is damaged, the verification information in the basic file configuration table FAT1 table is inconsistent with the verification information of the corresponding file, and the system file verification failure can be detected.
In one example, the embedded device queries a basic file configuration table FAT1 table in a FAT file system at a boot loader stage of the system, and searches and reads file data of a corresponding file according to the FAT1 table. Due to the file data error, the verification information in the basic file configuration table FAT1 table is inconsistent with the verification information of the corresponding file, and at this time, it may be detected that the system file verification fails.
As shown in the flowchart of fig. 3, after detecting that the system file is failed to be verified, it is determined that initialization of the embedded device system is failed in step 101.
Referring to fig. 4, fig. 4 is a flowchart of one implementation of step 102 provided herein. As shown in fig. 4, the process may include:
usually, the operating system boots the recording area and the basic file configuration table to have a relative position relationship on the disk, and the basic file configuration table is followed by the backup file configuration table. The location information of the base file profile table is determined, as is the location information of the backup file profile table.
In this step, based on the location information determined in step 401, a basic file allocation table and a backup file allocation table are obtained by offsetting a certain location on the basis of the operating system boot record area.
In one example, the DBR section of the operating system boot recording area is separated from the FAT1 table by 31 reserved sectors, and the FAT1 table and the FAT2 table can be found by shifting the 31 reserved sectors based on the DBR section.
In one example, the operating system boot recording area DBR section is followed by the base file configuration table FAT1 table, which can be found by directly finding the FAT1 table and FAT2 table at the DBR section end location.
As shown in fig. 4, the location information of the basic file configuration table is determined by determining the relative location relationship between the operating system boot record area and the basic file configuration table on the disk, so as to implement the step 102 of obtaining the basic file configuration table and the backup file configuration table from the file system.
As shown in fig. 5, the present specification provides a file recovery apparatus, which may perform the black chain guard method according to any embodiment of the present specification. The apparatus may include a confirmation module 501, an acquisition module 502, and a recovery module 503. Wherein:
a confirming module 501, configured to confirm that initialization of the embedded device system fails;
an obtaining module 502, configured to obtain a basic file configuration table and a backup file configuration table from a file system; the backup file configuration table is a backup of the base file configuration table;
a restoring module 503, configured to restore the basic file configuration table according to the backup file configuration table when the basic file configuration table is different from the backup file configuration table, so as to initialize according to the restored basic file configuration table.
Optionally, as shown in fig. 6, the confirmation module 501 includes:
the reading sub-module 601 is used for reading a system file;
a checking submodule 602, configured to check the system file;
the detection submodule 603 is configured to detect that reading the system file fails; or, the method is used for detecting that the system file fails to check.
The reading sub-module 601 and the checking sub-module 602 are detected and fed back by the detection sub-module 603 in real time. After receiving the detection information of the reading failure, the reading sub-module 601 confirms that the initialization is failed and does not perform the verification operation of the verification sub-module 602 any more; after receiving the detection information of successful reading, the reading sub-module 601 performs a verification operation of the verification sub-module 602, and if the verification sub-module 602 receives the detection information of failed verification, it determines that the initialization is failed; if the checking sub-module 602 receives the detection information that the checking is successful, it confirms that the initialization is successful.
Optionally, as shown in fig. 7, the obtaining module 502 includes:
a calculation submodule 701, configured to calculate, according to the operating system boot record area, location information of the basic file configuration table and the backup file configuration table;
the obtaining sub-module 702 is configured to obtain the basic file configuration table and the backup file configuration table according to the location information.
Optionally, the recovering module 503, when it is determined that the basic file configuration table is different from the backup file configuration table, includes: and when the cluster chain in the table entry of the basic file configuration table is different from the cluster chain of the corresponding table entry in the backup file configuration table, determining that the basic file configuration table is different from the backup file configuration table.
The implementation process of the functions and actions of each module in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.
For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of at least one embodiment of the present specification. One of ordinary skill in the art can understand and implement it without inventive effort.
The present specification also provides a computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor is capable of implementing the file recovery method of any embodiment of the specification when executing the program.
The present specification also provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, is capable of implementing the file restoration method of any of the embodiments of the specification.
The non-transitory computer readable storage medium may be a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc., which is not limited in this application.
Other embodiments of the present description will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This specification is intended to cover any variations, uses, or adaptations of the specification following, in general, the principles of the specification and including such departures from the present disclosure as come within known or customary practice within the art to which the specification pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the specification being indicated by the following claims.
It will be understood that the present description is not limited to the precise arrangements described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present description is limited only by the appended claims.
The above description is only a preferred embodiment of the present disclosure, and should not be taken as limiting the present disclosure, and any modifications, equivalents, improvements, etc. made within the spirit and principle of the present disclosure should be included in the scope of the present disclosure.
Claims (11)
1. A file recovery method is applied to a boot initialization phase of an embedded device system, and comprises the following steps:
confirming that initialization of the embedded equipment system fails;
acquiring a basic file configuration table and a backup file configuration table from a file system; the backup file configuration table is a backup of the base file configuration table;
if the basic file configuration table is different from the backup file configuration table, restoring the basic file configuration table according to the backup file configuration table so as to initialize according to the restored basic file configuration table.
2. The method of claim 1, wherein confirming that initialization of the embedded device system failed comprises:
reading a system file;
and detecting that the system file is read unsuccessfully.
3. The method of claim 1, wherein confirming that initialization of the embedded device system failed comprises:
reading a system file;
verifying the system file;
and detecting that the system file fails to be checked.
4. The method of claim 1, wherein obtaining the base file configuration table and the backup file configuration table from the file system comprises:
calculating the position information of the basic file configuration table and the backup file configuration table according to the operating system guide record area;
and acquiring the basic file configuration table and the backup file configuration table according to the position information.
5. The method of claim 1, wherein the base file configuration table is different from the backup file configuration table, comprising:
and if the cluster chain in the table entry of the basic file configuration table is different from the cluster chain of the corresponding table entry in the backup file configuration table, determining that the basic file configuration table is different from the backup file configuration table.
6. The file recovery device is applied to a boot initialization phase of an embedded device system, and comprises the following components:
the confirmation module is used for confirming that the initialization of the embedded equipment system fails;
the acquisition module is used for acquiring a basic file configuration table and a backup file configuration table from a file system; the backup file configuration table is a backup of the base file configuration table;
and the recovery module is used for recovering the basic file configuration table according to the backup file configuration table when the basic file configuration table is different from the backup file configuration table so as to initialize according to the recovered basic file configuration table.
7. The apparatus of claim 6, wherein the confirmation module comprises:
the reading submodule is used for reading the system file;
the checking submodule is used for checking the system file;
the detection submodule is used for detecting that the reading of the system file fails; or, the method is used for detecting that the system file fails to check.
8. The apparatus of claim 6, wherein the obtaining module comprises:
the calculation submodule is used for calculating the position information of the basic file configuration table and the backup file configuration table according to the operating system guide recording area;
and the obtaining submodule is used for obtaining the basic file configuration table and the backup file configuration table according to the position information.
9. The apparatus of claim 6,
the recovery module, when configured to confirm that the basic file configuration table is different from the backup file configuration table, includes: and when the cluster chain in the table entry of the basic file configuration table is different from the cluster chain of the corresponding table entry in the backup file configuration table, determining that the basic file configuration table is different from the backup file configuration table.
10. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the method of any one of claims 1 to 5 when executing the program during a boot initialization phase of an embedded device system.
11. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910973528.XA CN110795281A (en) | 2019-10-14 | 2019-10-14 | File recovery method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910973528.XA CN110795281A (en) | 2019-10-14 | 2019-10-14 | File recovery method, device, equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110795281A true CN110795281A (en) | 2020-02-14 |
Family
ID=69440194
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910973528.XA Pending CN110795281A (en) | 2019-10-14 | 2019-10-14 | File recovery method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110795281A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112100000A (en) * | 2020-11-11 | 2020-12-18 | 卡斯柯信号(北京)有限公司 | Data recovery method and device based on security critical system |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1168174A1 (en) * | 2000-06-19 | 2002-01-02 | Hewlett-Packard Company, A Delaware Corporation | Automatic backup/recovery process |
| CN1776640A (en) * | 2005-12-16 | 2006-05-24 | 北京中星微电子有限公司 | FAT file system error treating method and device |
| CN104063477A (en) * | 2014-06-30 | 2014-09-24 | 广东威创视讯科技股份有限公司 | Processing method and processing device for startup abnormalities of embedded system |
| CN109815061A (en) * | 2019-01-31 | 2019-05-28 | 深兰科技（上海）有限公司 | A kind of method, apparatus, equipment and the medium of the anti-brick of embedded system |
-
2019
- 2019-10-14 CN CN201910973528.XA patent/CN110795281A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1168174A1 (en) * | 2000-06-19 | 2002-01-02 | Hewlett-Packard Company, A Delaware Corporation | Automatic backup/recovery process |
| CN1776640A (en) * | 2005-12-16 | 2006-05-24 | 北京中星微电子有限公司 | FAT file system error treating method and device |
| CN104063477A (en) * | 2014-06-30 | 2014-09-24 | 广东威创视讯科技股份有限公司 | Processing method and processing device for startup abnormalities of embedded system |
| CN109815061A (en) * | 2019-01-31 | 2019-05-28 | 深兰科技（上海）有限公司 | A kind of method, apparatus, equipment and the medium of the anti-brick of embedded system |
Non-Patent Citations (1)
| Title |
|---|
| 莫京军: "PC机启动故障的维护", 《湖南水利》 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112100000A (en) * | 2020-11-11 | 2020-12-18 | 卡斯柯信号(北京)有限公司 | Data recovery method and device based on security critical system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7734945B1 (en) | Automated recovery of unbootable systems | |
| US6820214B1 (en) | Automated system recovery via backup and restoration of system state | |
| US6851073B1 (en) | Extensible system recovery architecture | |
| CN101589592B (en) | Multi-protocol removable storage device | |
| US8006125B1 (en) | Automatic detection and recovery of corrupt disk metadata | |
| EP3244315B1 (en) | Method and apparatus for performing data recovery in redundant storage system | |
| KR100655124B1 (en) | Software installation and testing system for a built-to-order computer system | |
| US7509544B2 (en) | Data repair and synchronization method of dual flash read only memory | |
| US9727411B2 (en) | Method and processor for writing and error tracking in a log subsystem of a file system | |
| CN107315616B (en) | Firmware loading method and device and electronic equipment | |
| CN101436138A (en) | Control device and control method for software upgrade and dynamic rolling back | |
| CN102929665B (en) | For the system of drive installation | |
| US20020163760A1 (en) | Disaster recovery tape drive | |
| US6934805B2 (en) | Method and apparatus for managing computer storage devices for improved operational availability | |
| US7574621B2 (en) | Method and system for identifying and recovering a file damaged by a hard drive failure | |
| US6363457B1 (en) | Method and system for non-disruptive addition and deletion of logical devices | |
| CN111400267A (en) | Method and device for recording log | |
| CN110795281A (en) | File recovery method, device, equipment and storage medium | |
| CN106445737A (en) | Multi-backup starting method | |
| CN115827069A (en) | Starting control method, system and device for server mainboard | |
| CN113448760B (en) | Method, system, equipment and medium for recovering abnormal state of hard disk | |
| CN110795155B (en) | System starting method and device, electronic equipment and storage medium | |
| CA2299850C (en) | System and method for the management of computer software maintenance | |
| CN113204359A (en) | Online server upgrading method and device | |
| US20160004607A1 (en) | Information processing apparatus and information processing method |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200214 |