TWI416319B - Boot method for computer system using redundant array of independent disks - Google Patents

Abstract

A boot method for a computer system using Redundant Array of Independent Disks (RAID) includes examining whether an identifier stored in one of a first number of disks currently installed in the computer system is identical to one of a plurality of identifiers stored in the computer system, and when confirming that the identifier stored in the disk is identical to one of the plurality of identifiers stored in the computer system, performing an identifier update process, for updating the plurality of identifiers stored in the computer system and a first number of identifiers stored in the first number of disks.

Description

Boot method for a computer system using an independent disk backup array

The present invention relates to a booting method of a computer system using an independent disk backup array, and more particularly to a method for booting a program according to hard disk attribute data of a computer system.

Redundant Array of Independent Disks (RAID) is a technology for managing data storage space. It can be achieved by software or hardware. It not only integrates multiple small-capacity hard disks into a large-capacity hard disk. And provide data protection features. RAID technology is widely used in computer systems that require multiple hard drives, such as Network Attached Storage (NAS) systems. RAID is divided into different levels, such as RAID-0, RAID-1, RAID-5, RAID-6, and so on. RAID-0 is called equal-volume mode. It cuts each hard disk in the computer system into equal blocks, and takes a fixed-size block in each hard disk to form a data volume. When the data is to be stored in the computer system, RAID-0 writes the data segment to the data reel according to the number of hard disks in the computer system. Since the data is spread over multiple hard disks on average, the data transfer rate when using RAID-0 is doubled by the number of hard disks. RAID-0 has no backup function. When any hard disk in the computer system is unavailable, all data will be lost. RAID-1 is called the mirror mode. It writes the data to the main hard disk of the computer system and also writes the same data to the mirrored hard disk. The full backup operation performed by RAID-1 makes the mirrored hard disk replace the work of the main hard disk when the main hard disk is damaged.

The NAS system is a storage device that provides file access and management between different computer systems through the network. Since the data is stored on the NAS system rather than the web server, the time to use the data access service is not limited by the power off of the web server, and the file data is easier to manage. Taking the NAS system as an example, the conventional NAS system uses the software RAID-1 to manage the operating system data in the NAS system. However, when using two NAS systems A and B managed by RAID-1, if the user When a hard disk of NAS system B is removed and placed on NAS system A, NAS system A cannot recognize that the newly added hard disk is from a NAS system other than itself, and because of the mirroring characteristics of RAID-1, NAS system A The operating system data stored in the system and the operating system data stored in the hard disk of the newly added NAS system B may interfere with each other. The related descriptions can be shown in Figures 1 and 2.

In the first and second figures, the NAS systems A and B can respectively accommodate four hard disks, the shaded area indicates the hard disk operating system block of the NAS system B, and the latticed area indicates the hard disk operating system area of the NAS system A. Piece. Figure 1 depicts a hard disk 10 (only the operating system block is depicted in the figure) removed by NAS system B, placed into NAS system A, and NAS system A uses the newly added hard disk 10 as the bootable hard disk. At this time, the operating system data of the NAS system B stored in the hard disk 10 is copied to all the operating system blocks of the NAS system A; in other words, the operating system data of the NAS system A is synchronized by the operating system data of the NAS system B. As a result, the hard disk other than the hard disk 10 in the NAS system A will not be able to complete the booting process because the operating system data does not match the hard disk. Figure 2 depicts that the hard disk 10 is removed by the NAS system B, placed on the NAS system A, and the NAS system A uses its own hard disk as the bootable hard disk. At this time, the operating system data of the hard disk of the NAS system A is overwritten to the hard disk. The operating system block of 10; in other words, the operating system data of the NAS system B originally stored in the hard disk 10 is synchronized by the operating system data of the NAS system A. In the case of FIG. 2, if the user removes the hard disk 10 and puts it back into the NAS system B, the operating system data of the NAS system A stored in the hard disk 10 may be overwritten to the operating system of other hard disks in the NAS system B. The block causes the operating system data to not match the hard disk and cannot complete the boot process.

In addition, since RAID-0 stores the data equally on all hard disks, there is no backup function. When the NAS system starts the booting process when one of the hard disks is not locked, the operating system data of the normally installed hard disk will follow. The boot program is updated, and the un-locked hard drive will not be recognized. After that, even if the loose hard disk is locked and turned on again, the operating system data of the hard disk is different from the operating system data of other normally installed hard disks, so that the NAS system cannot recognize the hard disk, and all the NAS systems The data scroll is equal to the damage status.

In short, if the hard disk swapping action occurs between two NAS systems using RAID-1, the mirroring characteristics of RAID-1 may cause the operating system data in the two NAS systems to rewrite each other, making the NAS system unable to Identifying some of the hard disks and not completing the boot process; on the other hand, if the NAS system is booting without a hard disk connected properly, the data spool generated according to RAID-0 may be damaged, even if the hard drive is re-locked. The disc cannot be accessed by the user. The above problems may occur on all computer systems that use RAID technology, which reduces the stability of the computer system using hard disks.

Accordingly, it is a primary object of the present invention to provide a booting method for a computer system for managing a hard disk using an independent disk backup array.

The invention discloses a booting method for a computer system for managing a hard disk using an independent disk backup array, which comprises checking an identification code stored by one of the first number of hard disks currently set in the computer system, One of a plurality of identification codes recorded by the computer system, the plurality of identification codes being different from each other, corresponding to all available hard disks of the computer system; and confirming that the identification code stored on the hard disk is a plurality of files recorded by the computer system After one of the identification codes, an identification code update procedure is performed to update the plurality of identification codes recorded by the computer system and the first number of identification codes stored by the first number of hard disks.

The present invention is applied to a computer system using a Redundant Array of Independent Disks (RAID) technology and having a removable hard disk, such as a Network Attached Storage (NAS) system. The hard disk is an abbreviation of a removable hard disk. The present invention defines a hard disk metadata (Metadata), which is used as a property data and related information of a computer system hard disk, and performs a booting process of a computer system according to the hard disk metadata to prevent the conventional technology from being incapable of being recognized by the computer system. A problem with a hard disk that causes the boot process to fail or the data spool to be corrupted.

Please refer to FIG. 3, which is a schematic diagram of a hard disk element data according to an embodiment of the present invention. The format of the hard disk meta-data in FIG. 3 is a continuous string, which includes identification (Identifier, ID) data, quantity (AN) data, and time (Data Counter, DC) data. The ID data is used to indicate the hard disk identification code, and is used to identify a hard disk as a hard disk or a foreign hard disk of the computer system, and can be a medium access control (MAC) bit of the hard disk. Address, Universally Unique Identifier (UUID) consisting of 32 hexadecimal digits or other randomly generated long string, as long as the ID data of each hard disk can be unique. The AN data is the number of hard disks in the current computer system that contain user-specific Data Volumes. The DC data is the time information about the order in which the operating system writes to the hard disk, so as to avoid the situation in which the operating system data cannot be judged after the time setting is changed. The DC data is changed every time the computer system is turned on or when a hard disk is added to the computer system. The value of the DC data is expressed in an incremental form in an embodiment of the present invention; the larger the value of the DC data, indicates the operating system stored in the hard disk. The newer the information. Please note that the hard disk meta-data in FIG. 3 is only one embodiment of the present invention. In other embodiments of the present invention, the order of ID data, AN data, and DC data may be arranged in other arrangements, and ID, AN, and The length of the DC data is not limited and can be designed as needed. In addition, when the computer system establishes the hard disk metadata on the hard disk, the ID data, the AN data, and the DC data may also be stored in the discontinuous memory block. In order to avoid the failure of the hard disk to cause the computer system to successfully complete the boot, the present invention simultaneously stores a backup hard disk meta data when storing the hard disk metadata, and when the hard disk metadata changes, the backup hard The disc metadata will also be updated.

Please refer to FIG. 4, which is a schematic diagram of a process 40 for managing a hard disk in an independent disk backup array according to an embodiment of the present invention. The process 40 is a boot process of a computer system, which discloses a computer system. How to create and use hard disk metadata, more than one hard disk can be set in the computer system. The process 40 includes the following steps: Step 400: Start.

Step 402: Determine whether system initialization has been completed. If yes, proceed to step 410; if no, proceed to step 404.

Step 404: Create hard disk meta data for each hard disk.

Step 406: Determine whether the system initialization is successful. If yes, go back to step 400; if no, go to step 408.

Step 408: Generate a first prompt message to inform the system that the initialization failed.

Step 410: Check whether the identification code currently stored in one of the hard disks of the computer system is one of the identification codes recorded by the computer system. If yes, go to step 414; if no, go to step 412.

Step 412: Disabling the hard disk as a bootable hard disk; returning to step 410, checking another hard disk.

Step 414: Check whether the time information of the operating system data stored in the hard disk is the latest in the time information of the operating system data stored in all the hard disks in the computer system. If yes, go to step 416; if no, go to step 412.

Step 416: Check whether the number of hard disks stored in each hard disk containing the user-specific data reel is equal to the number of hard disks being used by the computer system to generate a first inspection result, and check each hard disk storage. Whether the number of hard disks containing the user-specific data reels is equal to produce a second check result. If the first and second check results are all equal, step 420 is performed; if any of the check results are not equal, step 418 is performed.

Step 418: A second prompt message is generated to inform the data reel that the damage may be damaged.

Step 420: End.

The purpose of the system initialization actions of steps 402 through 408 is to enable the process 40 to be used by new, unused computer systems. The system initialization is performed only once. Step 404 is used to establish the hard disk metadata of each hard disk currently in the computer system, including ID data, AN data and DC data. While the hard disk metadata is being created on the hard disk, the computer system records the ID data of each hard disk in a non-volatile memory on the motherboard of the computer system, such as a NAND flash memory. The number of ID data recorded by the computer system is related to how many hard disks have been used in the computer system. Not only the ID data of the hard disk currently set in the computer system is recorded.

Since the computer system for initialization has not been used, the initial value of the AN data is 0, and the DC data also has an initial value. If the computer system is successfully initialized, the computer system proceeds to step 410 to check whether the ID data stored in a hard disk H is one of a plurality of ID data recorded by the computer system. If the initialization fails, the computer system generates a prompt message to inform the user that the system initialization failed. After the user knows that the initialization has failed, the computer system can be reformatted and process 40 is performed again. Since the user knows that the subsequent steps after the initialization failure are not the scope of the main protection of the present invention, they will not be described in detail herein. In another aspect, if it is determined that the computer system has been initialized and the hard disk metadata is created, the computer system can ignore the system initialization actions from step 402 to step 408, and the process 40 is directly executed from step 410.

When the computer system performs step 410, it is found that the ID data stored in the hard disk H is not one of the ID data recorded by the computer system. It can be seen that the hard disk H is not its own hard disk, because the hard disk metadata of the hard disk H is not by the computer. The system is established. In other words, the hard disk H is a hard disk from another place (possibly other computer system), and the computer system proceeds to step 412 to prohibit the hard disk H as a bootable hard disk. As a result, the problem of rewriting the operating system data of other computer systems to the operating system block of the hard disk of the computer system as shown in FIG. 1 does not occur, and the booting process of the computer system can continue. When the computer system knows that the hard disk H is not its own hard disk, it returns to step 410 to continue checking the ID data of other hard disks to improve the efficiency of identifying the boot disk.

On the other hand, when the computer system checks that the ID data stored in the hard disk H is one of the ID data recorded by the computer system, it can be seen that the hard disk H is the hard disk of the computer system itself, but does not mean that the hard disk H can be used as Boot the hard drive. The computer system shall perform step 414 to check the time information of the operating system data stored in the hard disk H, whether it is the latest in the time information of the operating system data stored in all the hard disks in the computer system; in other words, check the hard disk H The value of the stored DC data is the maximum of the values of the DC data stored on all hard disks in the computer system. If the computer system checks that the value of the DC data stored in the hard disk H is the maximum value of the DC data stored on all the hard disks, it means that the computer system can boot successfully if the hard disk H is used as the bootable hard disk. At this point, the computer system proceeds to step 416. If the computer system checks that the value of the DC data stored in the hard disk H is not the maximum value, the computer system performs step 412, prohibits the hard disk H as the bootable hard disk, and continues to check the ID data of the other hard disk.

For example, if the computer system contains a hard disk H, there are 4 hard disks. When the computer system checks that the value of the DC data stored in the hard disk H is 100, the value of the DC data stored on other hard disks is 100. , 100, 60, means that the hard disk H has the latest operating system data, which can be used as a bootable hard disk. In contrast, when the value of the DC data stored in the hard disk H is 60, and the value of the DC data stored in the other hard disk is 100, it can be seen that the operating system data stored in the hard disk H is higher than the operating system stored in other hard disks. The data is older and may not be used for a long time. Therefore, the computer system prohibits the hard disk H as a bootable hard disk, and prevents the old operating system data from being overwritten to the hard disk with the latest operating system data.

Steps 410, 412, and 414 can be summarized as a step of finding a hard disk that can be used for booting based on the hard disk identification code carried by the hard disk metadata and the time information of the operating system data. After performing ID data check or DC data check on each hard disk, the computer system proceeds to step 416 to check the AN data of each hard disk, that is, the number of hard disks containing the user-specific data scroll in the current computer system. Please note that the user does not necessarily use the entire hard disk currently set in the computer system to create a data reel. Therefore, the number of hard disks containing the user-specific data reel is not necessarily equal to the total number of hard disks in the computer system.

The AN data check is divided into two parts. One is to check whether the value of the AN data stored on each hard disk is equal to the number of hard disks being used by the computer system. The second is to check the value of the AN data stored on each hard disk. Are they equal to each other? Step 416 can prevent the computer system from starting the program when the hard disk is loose, resulting in the destruction of the data reel. If the first and second check results generated in step 416 are all equal, indicating that the computer system is successfully powered on, the computer system ends the process 40. If any of the check results produced in step 416 are not equal, the computer system generates a prompt message in accordance with step 418 to inform the user that the data scroll may be corrupted.

For example, when the value of the AN data stored on the hard disk H and other hard disks is 4, and the number of hard disks being used in the computer system is also 4, it means that the hard disk of the computer system is properly installed, and the process 40 is completed. The post-reel can be used smoothly without damage. In contrast, when the value of AN data stored on hard disk H and other hard disks is 4, the number of hard disks being used in the computer system is 3, indicating that there may be a hard disk in the computer system. A message indicates that the data reel may be damaged. In this case, the user can turn off the power of the computer system to confirm whether all the hard disks are properly installed, or ignore the prompt message and command the computer system to complete the booting process. Since the action selected by the user does not fall within the scope of the main protection of the present invention, it will not be described in detail in FIG. In addition, please note that when the computer system completes the system initialization, there is a hard disk to join, the new hard disk may not have hard disk metadata, or there is hard disk metadata but the value of AN data is 0, then the computer system will not Perform the AN data check in step 416 on the newly added hard disk. After the completion of the process 40, the newly added hard disk will be registered with the computer system to become a hard disk that can be used by the computer system to obtain updated hard disk metadata.

In short, the process 40 is divided into three parts, as indicated by the dashed lines in Figure 4. The first part includes steps 402 to 408. For the system initialization program, the computer system establishes hard disk metadata on each hard disk during initialization. The second part includes steps 410 to 414, which are operating system data protection programs, wherein the computer system will distinguish which hard disks may or may not be used as boot disks according to the ID data and DC data in the hard disk metadata. The mirroring feature of the independent disk backup array RAID-1 causes the operating system block of the hard disk to be incorrectly overwritten and the boot process cannot be completed. The third part includes steps 416 and 418. For the user data protection program, the computer system checks the AN data stored on each hard disk to prevent the computer system from booting when the hard disk is not properly connected. The data spool generated by the disk backup array RAID-0 is corrupted.

It should be noted that the process 40 is a preferred embodiment of the present invention, and those skilled in the art can make various changes and modifications. For example, the system initialization program in the process 40 is combined with the operating system data protection program as another boot process, and the operating system data can be separately protected; or the system initialization program in the process 40 is matched with the user data protection program as Another boot process can protect user data separately. In addition, other embodiments of the present invention may perform only ID data and DC data inspection, or only ID data inspection and AN data inspection.

The present invention further provides an update process of the ID data, the DC data, and the AN data. The processes may be performed after the process 40 of FIG. 4, so that the computer system can instantly update the hard disk metadata at a specific time to enhance the data of the computer system. Protective function. Please refer to FIG. 5. FIG. 5 is a schematic diagram of a process 50 according to an embodiment of the present invention. The process 50 is used to update ID data. The process 50 includes the following steps: Step 500: Start.

Step 502: Detect whether the booting process is completed. If yes, go to step 512; if no, continue to step 502.

Step 504: Detect whether the shutdown program starts. If yes, go to step 512; if no, continue to step 504.

Step 506: Detect whether any hard disk is removed from the computer system under the operating state after the booting process is completed. If yes, go to step 512; if no, continue to step 506.

Step 508: Detect whether any hard disk is added to the computer system under the operating state after the startup process of the computer system is completed. If yes, proceed to step 510; if no, proceed to step 508.

Step 510: Determine whether the newly added hard disk needs to be registered as a hard disk usable by the computer system. If yes, go to step 512; if no, go to step 516.

Step 512: Update all ID data stored in the non-volatile memory of the computer system.

Step 514: Set the computer system to the ID data used by each hard disk and write to each hard disk.

Step 516: Do not change the ID data.

Steps 502 and 504 are steps for the hard disk to be cold swapped when the computer system is powered off. Steps 506 and 508 are steps for the hot swap of the hard disk in the operating state after the booting process of the computer system is completed. When the computer system detects that the booting process is completed according to step 502, or detects that the shutdown process has started according to step 504, or detects that a hard disk is removed under the operating state of the computer system according to step 506, the computer system performs The ID data of step 512 and step 514 is updated.

According to step 512, the computer system updates all the ID data stored in the non-volatile memory in the motherboard, so that the value of each ID data recorded by the computer system is different from the previous value. According to step 514, the computer system retrieves part of the ID data from the reset ID data into the corresponding hard disks currently in the computer system. Since the computer system may detect the addition or removal of the hard disk, the number of ID data extracted by the computer system from the non-volatile memory may increase or decrease relative to the original ID data. For example, suppose that the computer system stores 10 ID data and originally has 4 hard disks. When the computer system detects that a hard disk is removed according to step 506, the number of hard disks set in the computer system is determined by The number of 4 is reduced to three. Therefore, according to step 514, the computer system extracts three ID data from 10 ID data and writes the corresponding three hard disks.

On the other hand, when the computer system detects that a hard disk is added to the computer system under the operating state of the computer system according to step 508, the computer system determines whether the newly added hard disk is necessary according to the instruction message from the user according to step 510. Register as a hard drive that can be used by computer systems. If the newly added hard disk must be registered, the computer system performs the ID data update of steps 512 and 514. As described above, all ID data, original hard disks and new ones stored in the non-volatile memory of the computer system are added. The ID data stored on the hard drive will be updated. If the newly added hard disk does not need to be registered, the computer system proceeds to step 516, does not change all the ID data stored in the non-volatile memory of the computer system, and does not change the ID data stored in the original hard disk. When the computer system is in operation, since the hard disk may be hot swapped multiple times, steps 506, 508, and subsequent steps may be performed multiple times.

Through the process 50, the computer system can accurately identify the old and new operating system data stored on the hard disk according to the ID data, and then prohibit the hard disk with the old operating system data as the bootable hard disk, and strengthen the operation. The protection function of the computer system for the operating system data. Please note that the process 50 is a preferred embodiment for updating the ID data, and those skilled in the art can make various changes and modifications according to the process 50. For example, if the specification of the computer system is set to prohibit the hot swap of the hard disk, step 506 and step 508 need not be performed.

Please refer to FIG. 6. FIG. 6 is a schematic diagram of a process 60 according to an embodiment of the present invention. The process 60 is used to update DC data. The process 60 includes the following steps: Step 600: Start.

Step 602: Detect whether the booting process is completed. If yes, go to step 610; if no, continue to step 602.

Step 604: Detect whether any hard disk is removed from the computer system under the operating state of the computer system after the booting process is completed. If yes, go to step 610; if no, continue to step 604.

Step 606: Detect whether any hard disk is added to the computer system under the operating state after the startup process of the computer system is completed. If yes, go to step 608; if no, continue to step 606.

Step 608: Determine whether the newly added hard disk needs to be registered as a hard disk usable by the computer system. If yes, go to step 610; if no, go to step 614.

Step 610: Obtain a maximum value of the values of the DC data stored on all the hard disks in the computer system.

Step 612: adding the maximum value to a difference value, generating an addition result, and writing the addition result to all hard disks in the computer system.

Step 614: Do not change the DC data.

When the computer system detects that the booting process is completed according to step 602, or detects that a hard disk is removed in the operating state of the computer system according to step 604, the computer system performs steps 610 and 612 to obtain all the hard disks therein. The maximum value T _MAX in the stored DC data is added to the maximum value T _MAX and a difference Δt, and the addition result (T _MAX +Δt) is written to the position of the DC data stored in all the hard disks of the current computer system to update DC data currently stored on all hard drives. The DC data of the removed hard drive will not be updated. The difference Δt can be equal to 1, and can also be other positive integer values.

When the computer system detects that a hard disk is added to the computer system under the operating state of the computer system according to step 606, the computer system determines, according to the instruction message from the user, whether the newly added hard disk needs to be registered as a computer system according to step 608. A hard disk that can be used. If the newly added hard disk has to be registered, the computer system performs the DC data update in steps 610 and 612; if the newly added hard disk does not need to be registered, the computer system proceeds to step 614 without changing the storage of all the hard disks in the current computer system. DC data.

Please refer to FIG. 7. FIG. 7 is a schematic diagram of a process 70 according to an embodiment of the present invention. The process 70 is used to update AN data. The process 70 includes the following steps: Step 700: Start.

Step 702: Determine whether the user-specific material reel is successfully established. If yes, go to step 704; if no, go to step 718.

Step 704: Calculate the number of hard disks including the user-specific data reel, that is, AN data.

Step 706: Write the AN data to a hard disk containing a user-specific data reel.

Step 708: Detect whether any hard disk is removed from the computer system under the operation state of the computer system after the booting process is completed. If yes, go to step 712; if no, continue to step 708.

Step 710: Detect whether any hard disk is added to the computer system under the operating state after the startup process of the computer system is completed. If yes, go to step 714; if no, continue to step 710.

Step 712: Check if the removed hard disk contains a user-specific data scroll. If yes, go to step 720; if no, go to step 718.

Step 714: Determine whether the newly added hard disk needs to be registered as a hard disk of the computer system. If yes, go to step 716; if no, go to step 718.

Step 716: Write the initial value of the AN data to the newly added hard disk.

Step 718: The AN data is not changed.

Step 720: Obtain the value of the AN data in the current computer system.

Step 722: Subtracting the obtained AN data by one, generating a subtraction result, and writing the subtraction result to a hard disk containing a user-specific data reel.

Since the computer system may change the data reel setting every time the computer system is turned on, in the process 70, the computer system first determines, according to step 702, whether the user-specific material reel is successfully established. If it is determined that the user-specific data scrolling fails to be established, the computer system does not change the AN data, and the AN data maintains the value before the last computer system shutdown. If it is determined that the user-specific data reel is successfully established, the computer system performs steps 704 and 706 to calculate the AN data, and writes the calculated value of the AN data to the hard disk containing the user-specific data reel. For example, suppose the computer system can hold up to 5 hard disks and currently only 4 hard disks H1 to H4 are set in it, and the user creates a data reel with hard disks H1, H3, and H4. At this time, the computer system calculates AN. The value of the data is 3, and AN=3 is written to the hard disks H1, H3, and H4.

Steps 708 and 710 are simultaneous steps. After the startup process is completed, the computer system continuously detects whether a hard disk is added or removed from the computer system. When the computer system detects that a hard disk has been removed from the computer system in accordance with step 708, the computer system will subsequently perform steps 712, 718, 720, 722. In detail, the computer system further checks whether the removed hard disk contains a user-specific data reel. If the removed hard disk does not contain a data reel, it indicates that the removal of the hard disk does not affect the currently used data reel. At this time, the computer system does not change the AN data. If the removed hard disk contains a data reel, the computer system obtains the value of the AN data in the current computer system and decrements the value of the AN data by one to generate a subtraction result, and then writes the subtraction result into a user-specific data reel. Hard drive. In the above example, if the hard disk H2 is removed, the AN data will not be changed; if the hard disk H1 is removed, the value of the acquired AN data is still 3, and the AN data obtained by the computer system will be obtained. The value is decremented by 1, and AN=2 is written to hard disks H3 and H4.

When the computer system detects that a hard disk is added to the computer system according to step 710, the computer system will subsequently perform steps 714, 716, and 718. In detail, the computer system determines whether the newly added hard disk needs to be registered as a hard disk of the computer system according to the user's instruction message. If the newly added hard disk must be registered, the computer system writes the initial value of the AN data to the new one. Add a hard drive. The newly added hard disk will not be used immediately, but will wait for the next computer system to start the booting process (for example, process 40), and then the user decides whether to use the newly added hard disk to create a data scroll. If the new hard disk does not need to be registered, the computer system will not change the AN data.

Through the instant update of the hard disk metadata through the processes 50, 60 and 70, the computer system can use the ID data, the DC data and the AN data which can accurately distinguish the old and the old operating system data stored in the hard disk during the process 40. The completion of the boot process not only ensures the best protection of the operating system data, but also avoids the destruction of the data reel caused by the improper installation of the hard disk, which greatly improves the stability of the computer system.

In the prior art, if a hard disk exchange operation occurs between computer systems that manage operating system data by the independent disk backup array RAID-1, the mirroring characteristics of RAID-1 may cause work between computer systems. The system data is duplicated, so that the computer system cannot recognize the hard disk and cannot complete the booting process; if the computer system manages the user data with RAID-0, the booting process may be performed in the case where the hard disk is not properly connected in the computer system, and the data reel may be Damaged, resulting in inaccessible user data. In contrast, when the computer system performs the boot process of the present invention according to the hard disk metadata defined in the present invention, and the data update process assists the boot process, the computer system can accurately distinguish which hard disks are prohibited as boot disks. The operating system block of the hard disk is prevented from being incorrectly overwritten and the booting process cannot be completed. At the same time, the user can be reminded whether the hard disk is not properly installed, thereby preventing the data scroll from being damaged.

In summary, the present invention avoids the problems caused by the use of RAID-1 and RAID-0 to manage the hard disk in the computer system, greatly improves the stability of the computer system, and the operating system data and user data in the hard disk are also the most. Good protection.

The above are only the preferred embodiments of the present invention, and all changes and modifications made to the scope of the present invention should be within the scope of the present invention.

10. . . Hard disk

Figures 1 and 2 are schematic diagrams of mutual interference of operating system data in two known NAS systems.

FIG. 3 is a schematic diagram of a hard disk element data according to an embodiment of the present invention.

FIG. 4 is a schematic diagram of a booting process for a computer system according to an embodiment of the present invention.

FIG. 5 is a schematic diagram of a process for updating an identifier stored in a hard disk according to an embodiment of the present invention.

FIG. 6 is a schematic diagram showing a flow of time information for updating operating system data stored in a hard disk according to an embodiment of the present invention.

FIG. 7 is a schematic diagram of a process for updating the number of hard disks including a user-specific data reel according to an embodiment of the present invention.

Claims (22)

A booting method for a computer system, the computer system uses a Redundant Array of Independent Disks (RAID) to manage a hard disk, and the booting method includes: checking a first one currently set in the computer system One of the number of hard disks stored in the hard disk is one of the plurality of identification codes recorded by the computer system, and the plurality of identification codes are different from each other, corresponding to all available hard disks of the computer system And after confirming that the identification code stored in the hard disk is one of the plurality of identification codes recorded by the computer system, performing an identification code update procedure to update the plurality of identification codes recorded by the computer system and The first number of identification codes stored by the first number of hard disks. The booting method of claim 1, further comprising: disabling the hard disk as the computer system when confirming that the identification code stored in the hard disk is not one of the plurality of identification codes recorded by the computer system One bootable hard drive. The booting method of claim 1, wherein the identifier update program comprises: detecting whether a booting process of the computer system is completed; and updating the complex number recorded by the computer system when detecting that the booting process is completed And the first number of identification codes of the plurality of identification codes that have been updated in the computer system are respectively written into the first number of hard disks to update the first number of hard disks to be stored The first number of identification codes. The booting method of claim 1, wherein the identifier update program comprises: detecting whether a shutdown program of the computer system starts; and detecting the plural recorded by the computer system when detecting the shutdown program starts And the first number of identification codes of the plurality of identification codes that have been updated in the computer system are respectively written into the first number of hard disks to update the first number of hard disks to be stored The first number of identification codes. The booting method of claim 1, wherein the identifier update program includes: detecting whether any one of the first number of hard disks is in a computer system after the booting process of one of the computer systems is completed Removing; detecting that the first number of hard disks, one of the hard disks, is removed from the computer system after the booting process is completed, updating the plurality of identification codes recorded by the computer system; The second plurality of identification codes of the plurality of identification codes that have been updated in the computer system are written into the corresponding second number of hard disks to update the second number of identification codes stored by the second number of hard disks, wherein The second number of hard disks are other hard disks other than the removed hard disk of the first number of hard disks. The booting method of claim 1, wherein the identifier update program comprises: detecting whether any hard disk is added to the computer system after the booting process of the computer system is completed; detecting that a hard disk is in After the completion of the boot process, when the computer system is added, it is determined whether the hard disk to be registered is required to be a hard disk usable by the computer system; when the added hard disk must be registered as a hard disk usable by the computer system, Updating the plurality of identification codes recorded by the computer system; and writing the second number of identification codes of the plurality of identification codes updated in the computer system to the corresponding second number of hard disks to update the first a second number of identification codes stored by the second plurality of hard disks, wherein the second number of hard disks includes the first number of hard disks and the added hard disk. The booting method of claim 6, wherein the identifier update program further comprises: changing the plural recorded by the computer system when the joined hard disk does not need to be registered as a hard disk usable by the computer system The identification code and the first number of identification codes stored by the first number of hard disks. The booting method of claim 1, further comprising: checking whether a value of a time data stored in the hard disk is a maximum value of a first quantity of time data stored in the first number of hard disks And the time information indicates time information of the operating system data stored in the hard disk; and when the value of the time data stored in the hard disk is confirmed to be the maximum value of the value of the first quantity of time data, A time data update program for updating time information of operating system data stored on each of the first plurality of hard disks. The booting method of claim 8 further includes: when confirming that the value of the time data stored in the hard disk is not the maximum value of the value of the first quantity of time data, prohibiting the hard disk as the One of the computer systems is booting the hard drive. The booting method of claim 8, wherein the time data update program comprises: detecting whether a booting process of the computer system is completed; and detecting the booting process completion, obtaining the first number of hard disks And storing one of the values of the first quantity of time data; and adding the maximum value to a difference, generating an addition result, and writing the addition result to the first number of hard disks a hard disk to update the first quantity of time data stored by the first number of hard disks. The booting method of claim 8, wherein the time data update program includes: detecting whether any hard disk in the first number of hard disks is in a computer system after a booting process of the computer system is completed Removing the first number of hard disks, and detecting that the first number of hard disks are stored in the computer system after the booting process is completed One of the values of the time data; and adding the maximum value to a difference, generating an addition result, and writing the addition result to each of the second number of hard disks, wherein the second A number of hard disks are other hard disks other than the removed hard disk of the first number of hard disks. The booting method of claim 8, wherein the time data update program includes: detecting whether any of the first number of hard disks is added to the computer system after the booting process of the computer system is completed; After detecting the completion of the boot process, the hard disk is determined to be registered as a hard disk usable by the computer system; and the hard disk to be registered must be registered as the hard disk And obtaining, by the computer system, a hard disk, obtaining a maximum value of the first plurality of time data values of the first number of hard disks; and adding the maximum value to a difference value to generate an addition result, And adding the addition result to each hard disk of the second number of hard disks to update the second quantity of time data stored by the second number of hard disks, wherein the second number of hard disks includes the first A number of hard drives and the hard drive to join. The booting method of claim 12, wherein the time data update program further comprises: changing the first number of hard disks when the joined hard disk does not need to be registered as a hard disk usable by the computer system The first number of time data stored. The booting method of claim 1, further comprising: checking whether a value of one of the data stored in each of the first plurality of hard disks is equal to the first quantity, to generate a first check result, The quantity information is the number of hard disks containing the data volume in the first number of hard disks; and checking whether the value of the quantity of data stored in each hard disk of the first number of hard disks is equal. To generate a second inspection result. The booting method of claim 14, further comprising: generating a prompt message to confirm that the data reel may be damaged when it is confirmed that the first check result and the second check result are not equal. The booting method of claim 14, further comprising: performing a quantity update program to update each of the first number of hard disks when confirming that the first check result and the second check result are all equal The quantity of data stored on a hard disk. The booting method of claim 16, wherein the quantity data update program comprises: determining whether the data reel is successfully established; and when the data reel is successfully established, calculating the quantity data; writing the quantity data to the first quantity of hard The disc contains a hard disk of the data reel; detecting whether any of the first number of hard disks is removed from the computer system after the booting process of one of the computer systems is completed; and detecting whether there is a hard disk After the boot process is completed, join the computer system. The booting method of claim 17, wherein the quantity data update program further comprises: not changing the quantity data when the data scroll establishment fails. The booting method of claim 17, wherein the quantity update program further comprises: detecting that the first number of hard disks are removed from the computer system after the booting process is completed Checking whether the removed hard disk contains a data reel; when confirming that the removed hard disk contains a data reel, obtaining the value of the quantity data; and subtracting a difference from the value of the quantity data to generate a subtraction result And writing the subtraction result to the hard disk of the computer system containing the data reel to update the quantity of data stored in the hard disk containing the data reel. The booting method of claim 19, wherein the quantity data update program further comprises: changing the quantity data when confirming that the removed hard disk does not include a data reel. The booting method of claim 17, wherein the quantity update program further comprises: detecting that a hard disk is added to the computer system after the booting process is completed, determining whether the hard disk to be registered is required to be registered The hard disk of the computer system; and when the added hard disk is to be registered as a hard disk of the computer system, an initial value of the quantity data is written to the added hard disk. The booting method of claim 21, wherein the quantity update program further comprises: changing the quantity data when the joined hard disk does not need to be registered as a hard disk of the computer system.