JP3951808B2 - Hard disk drive subsystem - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention is used in an information processing apparatus, and a hard disk including operating system modules and data necessary for starting up the information processing apparatus as stored contents. Creedosa Bus system To In particular, a hard disk that can read the boot module at startup at high speed. Creedosa Bus system To Related.
[0002]
[Prior art]
In a conventional PC system (personal computer system), a boot module necessary for system startup is usually stored in an HDD subsystem (hard disk drive subsystem) connected to the PC.
[0003]
When the PC system starts up, the PC first loads the OS (operating system) modules and data, which are indispensable for starting up the system, from the HDD via the controller to the memory system prepared in the PC, By sequentially performing the recorded processing, the system is finally set up.
[0004]
[Problems to be solved by the invention]
However, with the recent expansion of the PC system and its software functions, the functions of the boot module corresponding to this have also expanded, and the data amount of the boot module has increased.
[0005]
Therefore, the above-described conventional technique has a problem that the startup time of the system becomes longer due to an increase in the read data amount of the boot module.
[0006]
Here, even if the data amount of the boot module increases, the module execution time does not increase relatively due to the recent technological innovation related to the main processor. However, the hard disk storing and reading the boot module has not undergone technological innovation as compared with the processor, and the increase in the amount of read data from the hard disk causes the increase in the reading time as it is.
[0007]
This is because the processor-related processing is all performed with electrical signals, so the performance improves in proportion to the increase in signal transmission speed, whereas the hard disk moves the head to contact the recording medium and reads the signal. This is because a significant performance improvement cannot be expected unless the physical structure is improved.
[0008]
However, except when there is a change in the hardware or software of the apparatus, the PC system has a characteristic of executing the same boot module in the same procedure every time it is started up.
[0009]
In the present invention, by utilizing this characteristic and having a mechanism for automatically storing the boot module in the journal memory in advance, the reading time of the boot module is shortened, and as a result, the total system startup time is shortened.
[0010]
[Means for Solving the Problems]
The first hard disk drive subsystem with journal memory of the present invention is read by the hard disk including the operating system modules and data necessary for starting the information processing system, that is, the hard disk including the boot module group in the stored contents and the previous start. A hard disk drive subsystem comprising a non-volatile memory for storing a copy of the boot module group as journal data and a controller for controlling the non-volatile memory, wherein the non-volatile memory includes a copy of the boot module group There is journal data attribute information that holds certain journal data and attribute information that can identify each boot module of the journal data, and the controller notifies the boot start from the host device to which the hard disk drive subsystem is connected. In response to the instruction to read the boot module specified by the attribute information from the host device, the attribute information is compared with the journal data attribute information, and if this attribute information is registered in the journal data attribute information, It has control means for reading a designated boot module from a journal data area, reading it from a hard disk if it is not registered, and passing it to the host device.
[0011]
A second hard disk drive subsystem with a journal memory according to the present invention is the first hard disk drive subsystem with a journal memory, wherein the nonvolatile memory is instructed to sequentially read after receiving the boot start. The controller also has a read data attribute information record for temporarily storing the attribute information of the module, and the controller of the controller sequentially reads the read data attribute information record after receiving the boot end from the host device, and If attribute information is not registered in the journal data attribute information, means for reading the boot module specified by the read attribute information from the hard disk, copying it to the journal data area, and updating the journal data attribute information with the attribute information Also characterized by having That.
[0012]
The third hard disk drive subsystem with journal memory according to the present invention is the second hard disk drive subsystem with journal memory, wherein the control means of the controller has attributes of a boot module instructed to read during booting. When comparing information and journal data attribute information, if there is at least one unregistered module, it is turned on and also has an update request representative flag that is referred to at the end of booting. Update processing of journal data and journal data attribute information is performed.
[0013]
The fourth hard disk drive subsystem with journal memory of the present invention is the second hard disk drive subsystem with journal memory, wherein the control means of the controller includes attribute information of each boot module for which a read instruction has been issued. If it is not registered in comparison with the journal data attribute information, an update request individual flag is added to the corresponding record of the read data attribute information record, and this individual flag is updated in the journal data and journal data attribute information after the boot is completed. It also has a means for referring to the processing.
[0014]
A fifth hard disk drive subsystem with journal memory of the present invention is the second, third, or fourth hard disk drive subsystem with journal memory, wherein the controller also has a computer virus detection means, The control means reads the boot module serving as update data from the hard disk prior to the update processing of the journal data and journal data attribute information after the boot is completed, and checks the presence or absence of infection using the virus detection means. Further, the present invention is characterized by having means for updating the journal data and journal data attribute information after confirming that there is no infection.
[0015]
The sixth hard disk drive subsystem with journal memory according to the present invention is the fifth hard disk drive subsystem with journal memory, and the control means determines that if it is infected by the virus check, the host device And a means for writing back the individual boot modules in the journal data area designated by the journal data attribute information to the hard disk in response to an instruction from the host device.
[0016]
A seventh hard disk drive subsystem with journal memory according to the present invention is any one of the first to sixth hard disk drive subsystems with journal memory, wherein journal data attribute information and read data attribute information record of the journal memory are recorded. Is a predetermined number of records per module and is recorded in the order in which reading is instructed.
[0017]
An eighth hard disk drive subsystem with journal memory according to the present invention is any one of the first to seventh hard disk drive subsystems with journal memory, and records journal data attribute information and read data attribute information in the journal memory. The attribute information includes a file name.
[0018]
A ninth hard disk drive subsystem with journal memory according to the present invention is any one of the first to eighth hard disk drive subsystems with journal memory, wherein the journal memory is a flash memory.
[0019]
The first control program of the present invention is a program for controlling the hard disk drive subsystem in the host device to which the second hard disk drive subsystem with journal memory is connected, and notifies the hard disk drive subsystem of the start of booting. If the read boot module is a predetermined boot end module, a boot end notification is issued, and the read data attribute information record and journal data attribute are recorded. It has a procedure for instructing start of update processing of journal data and journal data attribute information according to the comparison of information and the comparison result.
[0020]
A second control program of the present invention is a program for controlling a hard disk drive subsystem in a host device to which the third, fourth, or fifth hard disk drive subsystem with journal memory is connected. Instruct the subsystem to start the boot and read the individual boot modules specified by the attribute information. If the read boot module is a predetermined boot end module, notify the boot end and update the information. If the request representative flag value is referred to and it is on, a procedure for instructing start of update processing of journal data and journal data attribute information is provided.
[0021]
The third control program of the present invention is a program for controlling the hard disk drive subsystem in the host device to which the sixth hard disk drive subsystem with journal memory is connected, and notifies the hard disk drive subsystem of the start of booting. When the read boot module is a predetermined boot end module, the boot end is notified and the update request representative flag value is referred to. If it is ON, a procedure for instructing update processing of journal data and journal data attribute information, a procedure for requesting display of attribute information of an infected boot module when a virus infection report is received, and a write back of the boot module as a response Is displayed, hard Reading of the journal data attribute information click drive subsystem, and having a procedure for instructing writing to the hard disk of the boot module on the journal data area designated by the attribute information.
[0022]
The fourth control program of the present invention is the first, second, or third control program, and includes a file name as the attribute information.
[0023]
DETAILED DESCRIPTION OF THE INVENTION
Next, a first embodiment of the present invention will be described in detail with reference to the drawings. FIG. 1 is a block diagram showing the configuration of a PC system 1 including a journal memory-equipped HDD subsystem 6 that is the subject of the present invention.
[0024]
Referring to FIG. 1, a PC system 1 includes a main processor unit (MPU) 2 that processes and executes data, a memory 3 that temporarily stores data and programs, and a journal that stores data and programs semipermanently. The system includes a HDD subsystem 6 with memory, a DISK interface controller 4 that controls reading and writing of data with respect to the HDD subsystem 6 with journal memory, and a system controller 5.
[0025]
The system controller 5 connects the MPU 2, the memory 3, and the DISK interface controller 4, and controls communication between the MPU 2, the memory 3, and the DISK interface controller 4.
[0026]
The DISK interface controller 4 and the journal subsystem with HDD 6 are ATA interfaces or SCSI-compliant interfaces.
[0027]
FIG. 2 is a block diagram showing a detailed configuration of the journal memory-equipped HDD subsystem 6 that is the subject of the present invention and the firmware 41 that controls it. Referring to FIG. 2, the HDD subsystem 6 with journal memory includes an HDD (hard disk drive) 8 for recording data semi-permanently, a journal memory 9 to which a boot module stored in the HDD 8 is copied, an HDD 8 and a journal memory 9. The HDD subsystem controller 7 controls the data communication with the system controller 5.
[0028]
Additional components of the journal memory 9 and the HDD subsystem controller 7 are mounted on an HDD controller board or the like in a conventional HDD device.
[0029]
The journal memory 9 has a read / write performance (access time) equivalent to that of the memory 3 and is configured by a nonvolatile memory that retains information even when the power is turned off. As an example of the nonvolatile memory, a flash memory, a battery or a battery backup RAM, or the like is used.
[0030]
The journal memory 9 includes a journal data attribute information database 91, a read data attribute information database 92, and a journal data area 93, which are roughly divided into three areas. The data attribute information is composed of information groups that can uniquely identify data, and can be arbitrarily set. Hereinafter, the database is abbreviated as DB.
[0031]
The boot module itself is stored in the journal data area 93, and the journal data attribute information DB 91 is instructed to read the attribute information for uniquely identifying the boot module read when the system was successfully started up last time. It is constructed as a DB with one boot module as one record in order.
[0032]
That is, if the boot module attribute information in the journal data attribute information DB 91 is recorded, the boot module is always stored in the journal data area 93. In the last record of the journal data area 93, a code indicating the end of the DB is recorded.
[0033]
Similar to the journal data attribute information DB 91, the read data attribute information DB 92 is constructed as a DB having attribute information for uniquely specifying a boot module as one record of one boot module. In the read data attribute information DB 92, When the PC system 1 is actually started up, it has a mechanism for recording the attribute information of the data module instructed to be read from the MPU 2 to the HDD subsystem controller 7 through the system controller 5 each time.
[0034]
The read data attribute information DB 92 is initialized every time it is started up. That is, the read data attribute information DB 92 plays a role of a log in which the boot modules that are actually instructed are recorded in the order in which the instruction is instructed. It is possible to confirm whether or not the content of the attribute information DB 91 is a boot module for which an instruction has been given.
[0035]
Similar to the journal data attribute information DB 91, a code indicating the end of the DB (database) is recorded in the last record of the read data attribute information DB 92.
[0036]
The HDD subsystem controller 7 has control means 71 for controlling reading and writing of the HDD 8 and controlling the journal memory 9 in the same manner as a normal HDD subsystem. The control means 71 compares the attribute information of the boot module instructed to read with the attribute information of the journal data attribute information DB 91, or compares the attribute information of the read data attribute information DB 92 and the journal data attribute information DB 91. 711.
[0037]
The control means 71 is a means for controlling the reading and writing of data with respect to the HDD 8 and journal memory 9 connected to the HDD subsystem controller 7, and based on the designated boot module attribute information, a journal data area instead of the HDD 8. 93 has a function of reading the boot module in the HDD subsystem controller 7 and copying the boot module in the HDD 8 to the journal data area 93.
[0038]
The attribute information comparison unit 711 compares the boot module attribute information in the journal data attribute information DB 91 and the read data attribute information DB 92 to determine whether or not they match. For comparison, registers # 1 and # 2 capable of temporarily storing data records of the journal data attribute information DB 91 and the read data attribute information DB 92 are mounted. These registers are realized by a scratch pad memory, and are realized by assigning words to the registers # 1 and # 2.
[0039]
The firmware 41 is software stored in the DISK interface controller 4. The firmware 41 initializes the read data attribute DB 92 with the activation of the system controller 5 as a trigger, and notifies the HDD subsystem controller 7 of the journal start, and read data attribute information. A program for notifying the HDD subsystem controller 7 of the end of journal is implemented using the reading of the database end code of DB92 as a trigger.
[0040]
That is, the firmware 41 executes a journal reading and writing start / end signal and a processing procedure to the journal memory 9.
[0041]
Next, the operation of the present embodiment will be described with reference to the drawings. In order to simplify the description, a series of N boot modules necessary for starting up the PC system 1 of FIG. 1 are read in the order of reading, boot module # 1, boot module # 2,. To do.
[0042]
Similarly, in order to simplify the description, the data attribute information stored in the journal data attribute information DB 91 and the read data attribute information DB 92 is composed of a file name, a time stamp, and a data size of the specified boot module. It is assumed that the boot module is uniquely determined by these three pieces of information.
[0043]
FIG. 3 shows a data storage image of N boot modules in the HDD 8 and the journal data area 93 at that time. FIG. 4 shows a storage image of attribute data regarding N boot modules in the journal data attribute information DB 91 and the read data attribute information DB 92.
[0044]
Although not shown, there is an example in which each record of the read data attribute information DB 92 has a flag (update request individual flag) indicating that it is necessary to read the module from the HDD 8 and update the journal data area 93 accordingly.
[0045]
The N boot modules stored in the HDD 8 are stored in advance when the PC system 1 is installed. Here, in addition to the N boot modules, a journal end module to be read in the (N + 1) th when the system startup is completed is prepared.
[0046]
The journal end module is a module for notifying the HDD subsystem controller 7 of the end of the journal from the booted system.
[0047]
Receiving the journal end notification, the HDD subsystem controller 7 writes the journal end code in the N + 2th record of the journal data attribute information DB 91 and the read data attribute information DB 92.
[0048]
Then, using the read data attribute information DB 92 recorded so far, if the module does not exist in the journal data area 93, it is described in the firmware 41 in order to copy the boot module data from the HDD 8 to the journal data area 93. It is a mechanism to start the program.
[0049]
5 to 7 are flowcharts showing the operation of this embodiment. First, referring to FIG. 5, the PC system 1 is turned on (step 1), the system controller 5 is activated, which activates the DISK interface controller 4 and activates the firmware 41 (step 2). The firmware 41 issues a command for initializing the read data attribute information DB 92 to the control means 71, notifies the MPU 2 that journal recording has started (step 3), and sets a record counter (this counter value is a). It is initialized to 0 (step 4).
[0050]
Next, the MPU 2 first issues a command for reading the boot module # 1 to the system controller 5. The system controller 5 issues an instruction to the HDD subsystem controller 7 to read the module (step 5).
[0051]
The HDD subsystem controller 7 uses the control means 71 to record the attribute information of the boot module # 1 in which the read instruction has been issued in the record a of the read data attribute information DB 92, and at the same time, the same attribute information in the attribute information comparison means 711. Record in register # 1 (step 6).
[0052]
The attribute information comparison means 711 checks whether or not the content of the register # 1 is an end code (step 7). If it is the end code, the operation proceeds to the operation phase C. Otherwise, the attribute information comparison means 711 moves to the record a of the journal data attribute information DB 91. The contents are read into the register # 2 in the attribute information comparison means 711 (step 8).
[0053]
Next, the control means 71 refers to the comparison result for the contents of the register # 1 and the register # 2 (step 9). If the results are the same, the control means 71 transfers the data from the journal data area 93 of the journal memory 9 to the register # 2. The data of the boot module # 1 specified from the recorded data attribute information is read out to the system controller 5 (step 10).
[0054]
If the comparison results are different, the control means 71 reads the data of the boot module # 1 specified by the attribute information of the register # 1 from the HDD 8 to the system controller 5 (step 11).
[0055]
When booting up for the first time after installing the boot module in the HDD 8, or when the contents of the boot module # 1 stored in the HDD 8 are updated due to a system change, the contents of the register # 2 and the contents of the register # 1 are different. Therefore, the contents of the boot module # 1 are read from the HDD 8.
[0056]
If the contents of the register # 2 and the contents of the register # 1 are the same, the boot module # 1 originally intended to be read from the HDD 8 has the same contents as the boot module # 1 already stored in the journal data area 93. Therefore, the boot module # 1 is read from the journal data area 93 to the HDD subsystem controller 7.
[0057]
The system controller 5 stores the read data in the memory 3, and the process of the boot module # 1 is executed by the MPU 2 (step 13). When the execution is successful (step 14), the firmware 41 advances the record counter (a) by 1 (step 15), and the MPU 2 issues a read command for the next boot module # 2, and therefore shifts to the operation phase B.
[0058]
If the execution fails, the PC system 1 stops and the process is terminated.
[0059]
When the operations of steps 5 to 15 are repeated and the execution up to the boot module #N is completed, a series of startup processing of the PC system 1 is completed.
[0060]
At the next execution, the journal end module is read. After receiving this, the end of the journal is received from the upper level (above the DISK interface controller 4) that has been interpreted or executed.
[0061]
The control means 71 checks from the contents of the register # 1 that it is an end code (step 7), and shifts to the operation C phase.
[0062]
Referring to FIG. 7, in the phase of operation C, first, firmware 41 initializes record counter (a) to 0, and notifies HDD subsystem controller 7 of the end of the journal (step 17). Next, the contents of row a of the read data attribute information DB 92 are read into the register # 1 in the control means 71 (step 18).
[0063]
If the content of the register # 1 is an end code, it is copied to the a line at that time in the journal data attribute information DB 91 and the process ends (step 25).
[0064]
If the content of the register # 1 is not an end code, the attribute information of row a of the journal data attribute information DB 91 is taken into the register # 2 (step 20), and the comparison results of the registers # 1 and # 2 do not match (step 20). 21) The data specified from the attribute information recorded in the register # 1 is copied from the HDD 8 to the journal memory 9 (step 22).
[0065]
Since the counter is initialized, the first information read into the register # 1 is the attribute information of the boot module # 1, and if the journal data area 93 is in the initial state, the contents of the boot module # 1 are transferred from the HDD 8 to the journal data area. 93. Further, the contents of the register # 1 (the attribute information of the boot module # 1) are copied to the a line (0th line) of the journal data attribute information DB 91 (step 23).
[0066]
Thereafter, the firmware 41 increments the record counter (a) by 1 (step 24), and repeats the operations of steps 18 to 24 until the end code is read into the register # 1. When the copying up to the journal end module is completed, all the modules necessary for starting up the system 1 in a series are copied to the journal data area 93, and the attribute information is recorded in the journal data attribute information DB 91.
[0067]
When the end code is read into the register # 1 (step 19), the end code as the content of the register # 1 is recorded in the a line of the journal data attribute information DB 91 (step 25).
[0068]
All processes are completed as described above, and the same operation is repeated when the system is terminated and restarted.
[0069]
Next, another example of this embodiment will be described. In the present embodiment, the control means 71 includes an update request representative flag. This flag is set to ON when the boot module is read from the HDD 8 and sent out in step 11 of FIG. 6 (step 12).
[0070]
In step 7 of FIG. 5, the firmware 41 transmits an end code (journal end notification) to the control means 71 and then reads the update request representative flag value. Only when this is on (step 16), the operation C phase is entered.
[0071]
Next, still another example of the present embodiment will be described. In this embodiment, the control means 71 is provided with an update request representative flag, which is turned on when the boot module is read out from the HDD 8 and sent out in step 11 of FIG. Further, the update request individual flag is turned on and added to the row a of the read data attribute information DB 92 (second item of step 12).
[0072]
Then, the control means 71 reads the update request individual flag together with the attribute information of the read data attribute information DB 92 at step 18 instead of the operations at steps 20 and 21 in FIG. 24.
[0073]
Next, the specific startup time of the PC system 1 according to the present invention is verified based on the specific read / write performance of the HDD 8 and the journal memory 9.
[0074]
Currently, the HDD 8 that is widely used at present generally employs an HDD subsystem having an average read speed of about 40 MBytes per second corresponding to the UltraATA66 interface.
[0075]
On the other hand, by adopting the memory 3 corresponding to the PC 133 that is currently widely used as the journal memory 9, when the contents of the HDD 8 and the journal memory 9 are the same, the average reading speed of the memory of the same standard It is possible to read at about 500 MBytes per second.
[0076]
Here, assuming that the total capacity of N boot modules is 1000 MBytes, when all N boot modules are read only by the HDD 8, the module read time needs 1000/40 = 25 seconds.
[0077]
On the other hand, when all N boot modules are read from the journal memory 9 according to the present invention, the reading is completed in 1000/500 = 2 seconds.
[0078]
In both cases, the time for the main processor unit 2 to process N boot modules is the same, so the time for starting up the PC system 1 by reading N boot modules is shortened by 23 seconds, which is the difference between the two. Become.
[0079]
That is, the system start-up time can be shortened by 20 seconds or more without making a major modification to the PC system 1 simply by adopting the HDD subsystem 6 with journal memory of the present invention.
[0080]
Next, a second embodiment of the present invention will be described in detail with reference to the drawings. FIG. 8 is a block diagram showing the configuration of the HDD subsystem 6 with journal memory of this embodiment. Referring to FIG. 8, the HDD subsystem controller 7A is provided with a virus detection means 72 in addition to the control means 71A and the attribute information comparison means 711.
[0081]
The virus detection means 72 is a mechanism that reads the content to be copied into the subordinate work area before copying the boot module from the HDD 8 to the journal data area 93 and checks whether it is contaminated with a computer virus.
[0082]
Next, the operation of this embodiment will be described with reference to the drawings. Here, the definition of the boot module is the same as that of the first embodiment and is as shown in FIG. When the PC system 1 is started up, N boot modules are read and executed in the same manner as in the flowcharts of FIGS.
[0083]
When the execution up to the boot module N is finished, the journal end module is next read and sent out, the control means 71 receives the journal end from the firmware 41, and after checking that the content of the register # 1 is the end code, 9 shifts to the phase of operation C ′.
[0084]
In the phase of operation C ′ in FIG. 9, first, the firmware 41 initializes the record counter (a) to 0 (step 31). Next, the content of row a of the read data attribute information DB 92 is read into the register # 1 (step 32). If this content is not the end code (step 33), the row a of the journal data attribute information DB 91 is taken into the register # 2. (Step 34) If the registers # 1 and # 2 do not match (step 35), the data specified from the attribute information recorded in the register # 1 is copied from the HDD 8 to the work area under the virus detection means 72. (Step 36), the virus detection means 72 checks whether the data is contaminated with a computer virus (step 36).
[0085]
If the computer virus is contaminated, the infection detection flag is turned on, and the attribute information recorded in the register # 1 is stored in the status area (step 39). If it is not contaminated, a response is immediately returned, and the firmware 41 advances the record counter (a) by one and repeats a series of operations until the end code is read into the register # 1.
[0086]
When the end code is taken into the register # 1, the control means 71 checks the infection detection flag, and if it is off, the control means 71 shifts to the phase of operation C in FIG. If the infection flag is on, the infection is notified to the firmware 41 of the DISK interface controller 4 by, for example, attention (step 41). The firmware 41 acquires the detailed status such as the infected boot module attribute information and then notifies the MPU 2 together with the display request.
[0087]
The MPU 2 displays infection information and detailed information (step 42). At this time, as a countermeasure, the operator also selects whether or not to return the series of boot modules of the HDD 8 to the previous boot module group. Upon receiving the selection to return, the MPU 2 instructs to delete the boot module of the current HDD 8 and executes the deletion. Next, the MPU 2 issues a write-back instruction to the DISK interface controller 4. Note that the MPU 2 may read the read data attribute information DB 92 for designating the deleted boot module.
[0088]
Moving to FIG. 10, when the firmware 41 receives the write back instruction (step 50), the firmware 41 initializes the record counter (step 51), and instructs the control means 71 to write back. The control means 71 fetches the row a of the DB 91 into the register # 1 (step 52). If the register # 1 is not the end code (step 54), the boot module specified by the attribute information of the register # 1 is retrieved from the journal data area 93. The data is read into the work area and written into the HDD 8 (step 54).
[0089]
The firmware 41 increments the record counter a, and steps 52 to 55 are repeated. When the end code is read into the register # 1, the write back operation ends.
[0090]
As a result, if the boot module of the HDD 8 is contaminated with a computer virus that prevents the next system startup, the contents of the journal memory 9 that is not contaminated with the computer virus are written back to the HDD 8. It is possible to return to the state before being contaminated.
[0091]
Therefore, at the next start-up, there is a new effect that the system can be started up without being affected by the computer virus.
[0092]
【The invention's effect】
As described above, if the hard disk subsystem with journal memory of the present invention is prepared, the system startup time can be shortened by reading all the boot modules from the journal memory having a sufficiently fast read / write performance compared to the HDD, and Since all hardware mechanisms including the journal memory are mounted on the HDD subsystem and can be connected through the conventional DISK interface controller, the conventional PC system can be applied without significant modification, and the system time can be reduced.
[0093]
Next, using the journal data attribute information DB and the read data attribute information DB, the contents of the journal data area and the contents of the boot module group of the HDD are compared each time it is started up, and the module that has been changed is copied after the system is started up. Even if the system is updated, the system startup time can be reduced.
[0094]
Further, by not using the HDD that stores the boot module, the product life can be extended as compared with the prior art. This is because the product life tends to be shortened as the frequency of use of the HDD increases, but in the present invention, unless the system is updated, all boot modules are always read from the journal memory, and the number of HDD accesses is reduced. .
[Brief description of the drawings]
FIG. 1 is a block diagram showing a configuration of a PC system 1 including a journal memory-equipped HDD subsystem 6 which is a first embodiment of the present invention and is the subject of the present invention.
FIG. 2 is a block diagram showing a detailed configuration of a journal memory-equipped HDD subsystem 6 that is the first embodiment of the present invention and a firmware 41 for controlling the same.
3 is a diagram showing a data storage image of N boot modules in the HDD 8 and the journal data area 93 according to the first embodiment of this invention. FIG.
FIG. 4 is a diagram showing a storage image of attribute data regarding N boot modules in the journal data attribute information DB 91 and the read data attribute information DB 92 according to the first embodiment of this invention;
FIG. 5 is a flowchart showing the operation of the first embodiment of the present invention.
FIG. 6 is a flowchart showing the operation of the first embodiment of the present invention.
FIG. 7 is a flowchart showing the operation of the first embodiment of the present invention.
FIG. 8 is a block diagram showing a configuration of a journal memory-equipped HDD subsystem 6 according to the second embodiment of this invention;
FIG. 9 is a flowchart showing the operation of the second exemplary embodiment of the present invention.
FIG. 10 is a flowchart showing the operation of the second exemplary embodiment of the present invention.
[Explanation of symbols]
1 PC system
2 MPU
3 memory
4 DISK interface controller
41 Firmware
5 System controller
6 HDD subsystem with journal memory
7, 7A HDD subsystem controller
71, 71A Control means
711 Attribute information comparison means
72 Virus detection means
8 HDD
9 Journal memory
91 Journal data attribute information DB
92 Read data attribute information DB
93 Journal data area

Claims (9)

The operating system modules and data necessary for starting up the information processing system, that is, the hard disk including the boot module group in the storage contents and a copy of the boot module group read out at the previous startup are held as journal data. A hard disk drive subsystem including a non-volatile memory and a controller for controlling the non-volatile memory, the non-volatile memory having journal data that is a copy of the boot module group and an attribute that can identify each boot module of the journal data has a journal data attribute information database which holds information, wherein the controller receives the boot start notification from the host device hard disk drive subsystem attached, said specified by the attribute information from the host device boot module Of receiving a read instruction when comparing the attribute information and the journal data attribute information database, If this attribute information is registered in the journal data attribute information database, the specified from storage et rear of the journal data reads the boot module, reading from the hard disk if it is not registered, features and be Ruha over disk drives subsystem that a control means for each pass to the host device. The nonvolatile memory also has a read data attribute information record for temporarily storing the attribute information of the boot modules instructed to be read sequentially after receiving the boot start, and the controller of the controller is booted from the host device. reads said read data attribute information recording after receiving the termination sequence, if the attribute information of each read module is not registered in the journal data attribute information database, from the hard disk boot module the read attribute information specifies reading, the di Yanarude copied to storage et rear motor, hard disk drive subsystem as claimed in claim 1, wherein also have means for updating the journal data attribute information database with the attribute information. It said control means of said controller is configured to turn on if even one unregistered module when performing the comparison of the attribute information of the boot module is instructed to read during boot and journal data attributes information database, boot update request representative flag that is referenced at the end also have, if this flag is on, hard of claim 2, wherein the update processing of the journal data and journal data attributes information database is performed Disk drive subsystem. The control means of the controller, if not registered in the comparison between the attribute information and journal data attributes information database for each boot module for which the read instruction, the update request separate flag in the corresponding record of the read data attribute information recording append a hard disk drive subsystem as claimed in claim 2, characterized in that it has a means for referring to the individual flag update processing of the journal data and the journal data attribute information database after the boot ends. The controller also has a detection means of computer viruses, the control means, prior to the update processing of the journal data and journal data attributes information database after the boot completion, read from the hard disk boot module to be updated data , claim 2, characterized in that it has this checks for infection with the virus detecting means, a means for performing update processing of the journal data and journal data attributes information database make sure no infection, 3 hard disk drive subsystem as claimed or 4,. Wherein, in the virus check, and means for notifying the host device if infected, in response to an instruction from the host device, the journal data which is specified by the journal data attribute information database hard disk drive subsystem as claimed in claim 5, wherein also have means for writing back each boot module stored et rear in the hard disk. The non-volatile memory journal data attribute information database及 beauty read data attribute information recording any of claims 1 to 6, characterized in that the to and the order in which they were instructed to read recording a predetermined number of records per module hard disk drive sub-system of the crab described. Journal data attributes information database of the non-volatile memory, as attribute information of the read data attribute information recording, ha over according to any one of claims 1 to 7, characterized in that it comprises a file name of each boot module Disk drive subsystem. Hard disk drive subsystem as claimed in any of claims 1 to 8, characterized in that the flash memory the non-volatile memory.

Images