TW201337541A - Port abnormality detecting device, computer, network system and program - Google Patents

Abstract

A port abnormality detecting device is provided, to determine whether an error is caused due to a failure in a device itself or due to a failure in a physical port in the case that the error occurs when the device is connected with the physical port. When a certain device is connected to a certain physical port, the fact whether the device is in normal work or an error is generated through the port is detected. Based on the collected detection results, a management table 53 showing whether the device is in normal work or error is generated is made by the combinations of a plurality of physical ports 51 with a plurality of devices 52. As per the contents of the management table 53, the error of the combination of a physical port and a device is determined based on whether it is caused due to a failure in the device or is the physical port.

Description

埠 Anomaly detection device, computer, network system and program

The present invention relates to a sputum anomaly detecting device, and more particularly to a sputum anomaly detecting device for detecting a sputum abnormality of a connecting device.

Further, the present invention relates to a computer and a network system having such a defect detecting device.

Further, the present invention relates to a program for causing a computer to execute a flaw detection method for detecting an abnormality of a connection device.

In the field of the computer, as disclosed in, for example, JP-A-2009-187483, a plurality of cymbals respectively connected to a device (storage device) are provided, and the 埠 is created and held, respectively, in an active state or in A system of maps in an invalid state (see Figure 6 of the same bulletin). In addition, it is also shown in the same publication that the error code and the error count value generated by the 埠 are held in the register (see Fig. 5 of the same publication).

Prior technical literature Patent literature

Patent Document 1 Special Publication No. 2009-187483

However, in the above-mentioned conventional system aspect, the map is combined with a device connected to the device to display an active state or an invalid state (or an error state). Therefore, there is a problem that, for example, even if the display is in an error state, it is impossible to judge whether the error is due to a failure of the device itself or because the connection of the physical device is abnormal. therefore, The user sometimes misunderstands the normal device as a malfunction, or continues to use the flaw that has caused the connection abnormality (fault), and cannot properly avoid the error.

Accordingly, an object of the present invention is to provide an abnormality detecting device that can determine whether the error is due to a malfunction of the device itself or a malfunction due to physical defects when an error occurs in the physical device of the connection device.

Further, an object of the present invention is to provide a computer and a network system including the cockroach abnormality detecting device.

Further, an object of the present invention is to provide a program for causing a computer to execute a flaw detection method for detecting an abnormality of a connection device.

In order to solve the above problems, the 埠 abnormality detecting device of the present invention detects a plurality of physical abnormalities detecting devices that are connected to the device, and is characterized in that: a connection error detecting unit is provided, and when a device is connected to a physical ,, Detecting whether the above-mentioned device passes the physical operation or whether an error occurs; the management table creating unit collects the detection result of the connection error detecting unit, and combines the physical devices of the plurality of physical devices with the devices of the plurality of devices. a management table for displaying whether the operation is normal or an error is generated, and an error type determination unit that determines the error for the combination of the physical device and the device that generated the error according to the content of the management table. The fault is either due to the above physical failure.

In the present specification, the term "physical" means that the connection port of the device is actually connected by wiring.

In the sputum abnormality detecting device of the present invention, when the connection error detecting unit is connected to a certain physical sputum, it is detected whether the device passes the physical 埠 normally or generates an error. The management table creation unit collects the detection result of the connection error detecting unit, and creates a management table for displaying whether or not the operation is normal or an error occurs for each of the plurality of physical devices and the combination of the devices of the plurality of devices. The error type determination unit determines whether the error is due to a failure of the above device or a failure of the physical device due to the combination of the physical device and the device in which the error has occurred, based on the contents of the management table. Therefore, by means of the anomaly detecting means, when an error occurs in the physical port of the connecting device, it can be judged whether the error is due to a malfunction of the device itself or a malfunction due to physical defects.

For example, the error is a failure of the device itself. If the physical connection to the device is normal, the user can quickly and appropriately avoid the error by exchanging the device connected to the physical device with the normal device. Or, the error is due to a physical failure. If the device connected to the physical device is normal, the user can quickly and appropriately avoid by reconnecting the normal device to another normal physical device. error.

In the case of the sputum abnormality detecting device according to the embodiment, the erroneous type determining unit is configured to refer to the management table based on the combination of the specific physical device and the specific device in which the error has occurred, based on the specific one of the plurality of devices. Whether the device other than the device has been normally operated by the specific physical device described above, and determines whether the error is due to the failure of the specific physical device, and according to whether the specific device is It has been normally operated by the physical physics other than the above-mentioned specific physical enthalpy among the plurality of physical physics, and it is judged whether or not the above-mentioned error is due to the failure of the above specific device.

In the sputum abnormality detecting device according to the embodiment, the error type determining unit refers to the management table when there is a combination of a specific physical 产生 and a specific device in which an error has occurred. Then, the error type determination unit determines whether the error is due to the failure of the specific physical flaw based on whether or not the other device other than the specific device among the plurality of devices has normally operated through the specific physical flaw. Further, the error type determination unit determines whether the error is due to a failure of the specific device, based on whether the specific device has been normally operated by a physical device other than the specific physical device among the plurality of physical devices. Therefore, the above-mentioned error can be judged with high accuracy because of malfunction of the device itself or malfunction due to physical defects.

In the 埠 abnormality detecting device according to the first aspect of the invention, the management table creating unit performs the number of connections of each combination for each of the plurality of physical 埠 and a combination of the plurality of devices. The number of normal actions or errors generated is recorded on the above management form.

In the 埠 abnormality detecting device according to the embodiment, the management table creating unit performs the number of connections and the normal operation of each combination for each of the plurality of physical 埠 and a combination of the plurality of devices. Or the number of errors generated is recorded on the above management form. Therefore, for example, by referring to the above management table, the user compares the number of connections and the positive for the combination of the physical device and the device that generated the error. The number of times of frequent actions or errors, whereby the error can be judged with good accuracy because of a malfunction of the above device or because of a malfunction of the above physical flaw.

In the 埠 abnormality detecting device according to the embodiment, the connection error detecting unit outputs an error code indicating the error when the error is detected, and the management table creating unit is based on the output of the connection error detecting unit. An error code generated for each physical volume of the plurality of physical frames and an error code generated for each device of the plurality of devices are recorded on the management table.

In the 埠 abnormality detecting device according to the embodiment, the connection error detecting unit outputs an error code indicating the error when detecting the occurrence of the error. The management table creation unit records an error code generated for each physical volume of the plurality of physical files and an error code generated for each device of the plurality of devices on the management table based on an output of the connection error detecting unit. Therefore, for example, by referring to the management table, the user can judge each physical failure with good accuracy based on an error code generated for each physical 埠 of the plurality of physical 、 and an error code generated for each device of the plurality of devices. Or, each device has failed.

The computer of the present invention is a computer characterized by the above-described flaw abnormality detecting device.

In the computer aspect of the present invention, when an error occurs in the physical flaw of the connected device, it can be judged whether the error is due to a malfunction of the device itself or a malfunction due to physical defects.

For example, the error is a failure of the device itself. If the physical connection to the device is normal, the user can quickly and appropriately avoid the error by exchanging the device connected to the physical device with the normal device. Or, the error is due to a physical failure. If the device connected to the physical device is normal, the user can quickly and appropriately avoid by reconnecting the normal device to another normal physical device. error.

In a computer according to an embodiment of the present invention, a motherboard including a BIOS that functions as the connection error detecting unit, the management table creating unit, and the error type determining unit; and a management table memory unit that stores the management table The plurality of devices include a storage device storing an operating system for the computer, and the plurality of physical devices include a cassette mounted on the motherboard for connecting the storage device.

Here, "BIOS" means a basic input/output system (Basic Input/Output System).

In the computer aspect of the embodiment, the BIOS executes the operations of the connection error detecting unit and the management table creating unit. Further, the management table storage unit memorizes the management table created by the above BIOS. Furthermore, the BIOS executes the operation of the error type determination unit described above. That is, according to the contents of the management table, it is determined whether the error is due to the failure of the storage device or the failure of the physical device for the combination of the physical device and the storage device in which the above error has occurred. Therefore, on this computer side, an error has occurred in the physical connection to the storage device that stores the operating system. At this time, it can be judged that the error is due to a failure of the storage device itself or due to a physical failure.

For example, the error is a failure of the storage device itself. If the physical connection to the storage device is normal, the user can quickly and appropriately exchange the storage device connected to the physical device with the normal storage device. Avoid errors and start the computer's operating system. Or, the error is due to a physical failure. If the storage device connected to the physical device is normal, the user can quickly and appropriately reconnect the normal storage device to another normal physical device. Avoid errors and start the computer's operating system.

In a computer according to one embodiment, the plurality of devices include a plurality of storage devices respectively storing the operating system for the computer, and the BIOS includes an OS selection processing unit, wherein the OS selection processing unit is based on the error type. The determination result of the determination unit displays that the operating system that can be activated in the operating systems stored in the plurality of storage devices is selected to be activated or not activated.

Here, "OS" means the operating system (Operating System).

In the computer aspect of this embodiment, the plurality of devices include a plurality of storage devices each storing an operating system for the computer. The OS selection processing unit included in the BIOS displays, based on the determination result of the error type determination unit, the activation or activation of the operating system that can be activated in the operating systems stored in the plurality of storage devices. For example, according to the judgment result of the error type determining unit, if it is connected to a normal physical storage device (the operating system is stored) The OS selection processing unit selects the normal storage device to activate the operating system stored in the normal storage device. Therefore, if a normal storage device connected to a normal physical port exists, the user does not have to worry about starting the above computer. On the other hand, according to the determination result of the error type determination unit, if the normal storage device (the storage device storing the work system) connected to the normal physical device does not exist, the OS selection processing unit displays that the activation cannot be started. Therefore, the user can attempt to start the computer by connecting the new storage device (the storage device storing the operating system) to the normal physical device by referring to the management table, for example.

The network system of the present invention is a network system for communicably connecting a plurality of the above-mentioned computers via a network, wherein one of the plurality of computers is a main computer, and the main computer except the memory is about the main In addition to the management table storage unit of the management table of the computer, an additional management table storage unit for storing the management table of the computer other than the host computer among the plurality of computers is provided.

In the network system of the present invention, one of the plurality of computers is a main computer, and in addition to memorizing the management table memory of the management table of the main computer, the memory of the plurality of computers is also recorded. An additional management table storage unit of the above management table of a computer other than the main computer (referred to as "other computer" as appropriate). That is, the main computer keeps in mind the management forms of other computers in addition to its own management forms. Therefore, the above-mentioned host computer can grasp the state of the device or physical failure of other computers in the network system. Therefore, it is possible to centrally manage a plurality of computers.

The program of the present invention is a program for causing a computer to execute a plurality of physical anomaly detection methods for detecting a plurality of physical anomalies respectively connected to the device, wherein the detection method includes: a connection error detection step, which is connected to a device. In a physical state, detecting whether the device passes the physical 埠 or whether an error occurs; and the management table creation step is to collect the detection result of the connection error detecting step, for each physical 埠 and plural of the plurality of physical 埠a combination of devices of the device, respectively, for creating a management table indicating whether the device is operating normally or generating an error; and an error type determining step for determining the combination of the physical device and the device that generated the error according to the content of the management table The error is due to a malfunction of the above device or due to a malfunction of the above physical defects.

The program of the present invention is executed by a computer as a flaw detection method. In the connection error detecting step in the above-described sputum abnormality detecting method, when a certain device is connected to a physical 埠, it is detected whether the device passes the physical 埠 or the error occurs. In the management table creation step, the detection result of the connection error detection step is collected, and a management table indicating whether or not the operation is normal or an error is generated for each combination of the physical devices of the plurality of physical files and the devices of the plurality of devices. In the error type judging step, based on the contents of the management table described above, it is judged whether the error is due to the failure of the above device or the failure of the above physical defect for the combination of the physical device and the device in which the above error has occurred. Therefore, if When the computer executes the 埠 anomaly detection method displayed by the program, when an error occurs in the physical 埠 of the connected device, it can be judged whether the error is due to a malfunction of the device itself or a malfunction due to physical defects.

For example, the error is a failure of the device itself. If the physical connection to the device is normal, the user can quickly and appropriately avoid the error by exchanging the device connected to the physical device with the normal device. Or, the error is due to a physical failure. If the device connected to the physical device is normal, the user can quickly and appropriately avoid by reconnecting the normal device to another normal physical device. error.

As apparent from the above, with the defect detecting device and the computer of the present invention, when an error occurs in the physical port of the connecting device, it can be judged whether the error is due to a malfunction of the device itself or a malfunction due to physical defects.

In addition, in the network system of the present invention, since the main computer stores the management forms of other computers in addition to its own management table, it is possible to centrally manage a plurality of computers.

Further, by causing the computer to execute the program of the present invention as the 埠 abnormality detecting method, when an error occurs in the physical 埠 of the connected device, it can be judged whether the error is due to a malfunction of the device itself or a malfunction due to physical defects.

Hereinafter, the present invention will be described in detail by way of the embodiments shown in the drawings.

Fig. 1 is a block diagram showing a computer (indicated by the symbol PC1) of an embodiment including the flaw detecting device of the present invention.

The computer PC1 includes a motherboard 90, a CPU (Central Processing Unit) 11 mounted on the motherboard 90, a USB (Universal Serial Bus) controller 12, and SATA (Serial Advanced Technology Attachment; The serial advanced technology attachment) controller 13, chipset 14, RAM (Random Access Memory) 15, BIOS-ROM 16, information storage ROM 17, and LAN interface (I/F) 18.

The CPU 11 performs various numerical calculations, information processing, machine control, and the like using a program (including an OS) stored in a storage device to be described later.

A plurality of USB ports USB1, USB2, USB3, and USB4 as physical ports are connected to the USB controller 12. The USB controller 12 selects USB埠USB1, USB2, ..., USB4 by the control of the BIOS (or OS) or the chipset 14. In this example, the USB memories EEE, FFF, GGG, and HHH, which are storage devices respectively storing the OS, are connected to the USB ports USB1, USB2, USB3, and USB4.

A plurality of SATA, SATA1, SATA2, SATA3, SATA4, SATA5, and SATA6 as physical ports are connected to the SATA controller 13. The SATA controller 13 selects SATA 埠 SATA1, SATA2, ..., SATA6 by the control of the BIOS (or OS) or the chipset 14. In this example, hard disk drives (HDD) XXX and YYY, which are storage devices respectively storing the OS, are connected to SATA, SATA, and SATA2. Solid-state drives (SSD) ZZZ and AAA, which are storage devices for storing OS, are connected to SATA, SATA3, and SATA4. Stored as OS The storage device DVD (Digital Versatile Disc) drive CCC is connected to SATA 埠 SATA5. Further, a floppy (registered trademark) disk drive (FDD) DDD as a storage device storing an OS is connected to SATA 埠 SATA6.

The chip set 14 constitutes a peripheral circuit for the CPU 11. The chip set 14 manages the transfer of data between the USB controller 12, the SATA controller 13, the RAM 15, the information storage ROM 17, and the LAN interface 18.

The RAM 15 temporarily stores data and uses it as a work area for the CPU 11.

The BIOS-ROM 16 is composed of a flash ROM and stores a program for executing the basic operation of the computer (hereinafter referred to as "BIOS program").

The information storage ROM 17 is composed of a flash ROM. As shown in FIG. 3, the operation setting data 17a for the CPU 11 or the chip set 14, the priority activation device information 17b, and the machine management table 17c as a management table are stored. The operation setting data 17a is referred to in order to set the CPU 11 or the chip set 14 when the BIOS program is started. The priority boot device information 17b stores which of the plurality of devices connected to the USB 埠 USB1, USB2, ..., USB4 or SATA 埠 SATA1, SATA2, ..., SATA6 is preferentially activated (more correctly, which one is made) Physical 埠 priority start information (this information is called "startup priority"). The machine management table 17c will be described later.

The LAN interface 18 shown in FIG. 1 communicates with an external device (other computer or the like) via the network 900.

Further, a display unit 19 for displaying an image such as an LCD (Liquid Crystal Display Element) and a keyboard and a mouse (not shown) for inputting and outputting by the user are connected to the motherboard 90.

Fig. 5 illustrates the contents of the machine management table 17c. The machine management table 17c has a table head 51 that defines a plurality of physical files, a front side portion 52 of a plurality of devices, and a body portion 53.

Regarding the header 51, in this example, SATA 埠 SATA1, SATA 2, ..., SATA 6, and USB 埠 USB 1, USB 2, USB 3, and USB 4 can be cited.

Regarding the watch side portion 52, in this example, as a storage device, a hard disk drive (HDD) XXX, YYY, a solid state drive (SSD) ZZZ, AAA, a DVD drive CCC, and a floppy (registered trademark) magnetic can be cited. Disc Drive (FDD) DDD. Further, although the name of the device is simplified in the table side portion 52, for the sake of convenience of the user, for example, "A company manufactures 250 GB (billion bytes) HDD Serial No. XXX", " The company B manufactures 80 GB HDD Serial No. YYY", and the manufacturer's name, memory capacity, and the like are listed together.

The body portion 53 displays whether or not the normal operation (in this example, activation) is performed for each physical 埠 of the plurality of physical 特定 specified by the head portion 51 and each device of the plurality of devices specified by the front portion 52. An error has occurred. In this example, for each of these combinations in the form of (the number of normal starts) / (the number of attempts to start), the score is used to indicate the number of times the combination attempt is initiated and the number of times the combination is normally started.

Further, an error code (for example, SATA 埠 SATA2, "0xAA", "0xBB", "0xCC", ...) generated by each physical 显示 is displayed in the order of the head portion 53 in the order of the head portion 53. . The history sequence of the error code is specified as "error code history 1", "error code history 2", "error code history 3" by the field 54 provided on the left side of the error code column 55 (below the table side portion 52). ....

Further, an error code generated for each device (for example, a hard disk drive (HDD) YYY, "0x12", "0x34", "0x56", ...) is displayed on the right side of the body portion 53 in order of history. Device error code column 56. The sequence of the error code is specified in the column 56 provided above the device error code column 56 (on the right side of the header 51) as "ERR1", "ERR2", "ERR3", ....

In this example, the machine management table 17c is basically made by the BIOS program as follows (more detailed, and then explained using an action flow). That is, each time the computer PC1 is activated, the BIOS program functions as a connection error detecting unit to detect whether a certain device has a normal operation or an error. Moreover, each time the computer PC1 is activated, the detection result is collected, for each physical device of the plurality of physical ports SATA1, SATA2, ..., SATA6 and the plurality of SATA devices XXX, YYY, ZZZ, AAA, CCC, DDD devices Combinations, or a combination of physical physics of USB1, USB2, USB3, USB4 and a plurality of USB devices EEE, FFF, GGG, HHH, respectively, whether to record normal operation or generate an error (again, due to The shape of the connector is different, so it is impossible to have a combination of SATA port and USB device or a combination of USB port and SATA device). When an error is detected, the BIOS program outputs the above error code.

In addition, each time the computer PC1 is activated, the BIOS program functions as a management table creation unit, and the combination of each of the physical devices and devices is combined with the number of times the combination attempt is initiated and the number of normal startups in the combination is used as a detection result. The machine 埠 management table 17c is produced (more precisely, the body portion 53). In addition, the BIOS program records the error codes in the error code column 55 and the device error code column 56, respectively.

Further, in this example, the BIOS program functions as an error type determination unit, and based on the contents of the machine management table 17c, for the combination of the physical device and the device in which the error has occurred, it is judged whether the error is due to malfunction of the device or because of physicality. Awkward failure. Therefore, when an error occurs in the physical flaw of the connected device, it can be judged that the error is due to a malfunction of the device itself or a malfunction due to physical defects.

For example, with the machine management table 17c, the number of attempts to start is 10 times in the combination of the physical port SATA1 and the device YYY, and the number of normal starts is 0 in the combination (denoted as 0/10). That is, 10 times have produced an error. Here, look at the physical 埠 SATA1 line in the vertical direction, for the combination of physical 埠 SATA1 and other devices XXX, ZZZ, AAA, CCC, DDD, 5/5, 7/7, 4/4, 2/2, 2/2 In this case, all attempts to start are started normally. In addition, the horizontal viewing device YYY is 0/4, 0/2, 0/1, 0/0, 0/0 for the combination of device YYY and other physical ports SATA2, SATA3, SATA4, SATA5, SATA6. It is stated that all attempts to start have generated an error. Therefore, the BIOS program can determine that the physical port SATA1 is normal and the device YYY is faulty. The BIOS program displays the message on the display unit 19 to notify the user.

As a result, the user can quickly and appropriately avoid the error by exchanging, for example, the device YYY connected to the failure of the physical port SATA1 with the normal device.

Further, with the machine management table 17c, the number of attempts to start is 10 times in the combination of the physical port USB3 and the device EEE, and the number of normal starts is 0 in this combination (denoted as 0/10). That is, 10 times have produced an error. Here, the horizontal view device EEE is listed for the device EEE and He has a combination of USB1, USB2, and USB4. It is recorded in 10/10, 10/10, and 6/6. All the attempts to start are started normally. In addition, looking at the physical 埠 USB3 in the vertical direction, for the combination of the physical 埠USB3 and other devices FFF, GGG, HHH, the records are 0/15, 0/2, 0/2, all the attempts to start have generated errors. . Therefore, the BIOS program can judge that the device EEE is normal, and the physical 埠 USB3 is faulty. The BIOS program displays the message on the display unit 19 to notify the user.

As a result, the user can quickly and appropriately avoid errors by, for example, reconnecting the normal device EEE to another normal physical device USB3.

Thus, the BIOS program refers to the machine management table 17c when there is a combination of a specific physical device and a specific device that has generated an error. Then, the BIOS program determines whether the error is due to the failure of the specific physical device according to whether the device other than the specific device has been normally operated by the specific physical device, and according to whether the specific device has passed the specific physical device. Other physical actions occur normally, and it is judged whether the above error is due to the failure of the above specific device. Therefore, the above-mentioned error can be judged with high accuracy because of malfunction of the device itself or malfunction due to physical defects. As a result, the user can avoid errors quickly and appropriately.

In addition, the user refers to the 埠 error code column 55 and the device error code column 56 of the table 17c according to the machine 根据, according to the physics of the plurality of physical ports SATA1, SATA2, ..., SATA6, USB1, USB2, USB3, USB4.错误 generated error code, and for a plurality of devices XXX, YYY, ZZZ, AAA, CCC, DDD, EEE, FFF, GGG, The error code generated by each device of the HHH can accurately judge each physical failure or the failure of each device.

6, FIG. 7, FIG. 8, FIG. 9, and FIG. 10 show the flow of operations regarding the machine management table 17c using the BIOS program.

(1) When the power of the computer PC1 is turned "ON", as shown in step S1 of Fig. 6, the CPU 11 and the chipset 14 are activated, and the BIOS program is read from the BIOS-ROM 16. Thereby, as shown in step S2, the BIOS program is started. The following steps are performed by the BIOS program. For the sake of brevity, the main body (BIOS program) for explaining the operation will be omitted as appropriate. In addition, physical 埠 is appropriately referred to simply as 埠.

Next, as shown in step S3, the BIOS program acquires the machine management table 17c in the information storage ROM 17 of the computer PC1, and arranges it in a specific area on the RAM 15.

Next, as shown in step S4, the start priority of which display is stored in the information storage ROM 17 to which priority is activated is obtained. Corresponding to this, as shown in step S5, reference is made to the line (row) to be designated with the highest priority activation on the machine management table 17c.

(2) Next, as shown in step S6 of Fig. 7, it is judged whether or not the number of times the OK number is referenced on the machine management table 17c is "0" in all devices. Here, if the number of times of starting the activation is not 0 in all the devices (that is, the number of times of starting the activation is one or more times in any of the devices) (NO in step S6), it can be determined that the referenced 埠 is normal. Alternatively, even if the number of times of activation is 0 in all devices (YES in step S6), if the number of attempts to start is 0 in all devices (YES in step S11), the reference to the frame is also normal. . Then, as shown in step S7, try to take It is necessary to identify the information of the device connected to its reference (this information is referred to as "device information").

If the device information cannot be acquired (NO in step S8), as shown in step S17, a message "There is a possibility that the device is faulty or the next priority is retrieved" is displayed on the display unit. 19 on. Then, the process proceeds to step S18 of Fig. 8 which will be described later.

On the other hand, if the device information can be acquired in step S8 of Fig. 7 (YES in step S8), as shown in step S9, it is determined whether or not the device is the device provided by the front side portion 52 of the machine management table 17c.

Here, if the device is not the device provided by the front side portion 52 of the machine management table 17c (NO in step S9), as shown in step S10, the device is determined as a new device, and the name of the device is added to The machine 埠 manages the new column on the side 52 of the table 17c. Then, the process proceeds to step S12 of Fig. 9 which will be described later.

On the other hand, if the device is the device of the front side portion 52 of the machine management table 17c (YES in step S9), the process proceeds to step S12 of Fig. 9 which will be described later.

(3) In step S6 of Fig. 7, on the machine management table 17c, the line of the number of times the OK is initiated in the above reference is 0 in all devices (YES in step S6), and the number of attempts to start is at all. If the device is not 0 (i.e., the number of attempts to start is one or more times in any of the devices) (NO in step S11), it can be judged that the defect has occurred. Then, the process proceeds to step S16 of Fig. 8, and a message "There is a possibility that the failure has occurred, and the next priority is retrieved" is displayed on the display unit 19.

(4) Next, as shown in step S18 of Fig. 8, reference is made to the line (row) designated to be activated by the following priority on the machine management table 17c.

Next, in step S19, it is judged whether or not it is normal for all the defects. If there is an unconfirmed 埠 (NO in step S19), it returns to step S6 of Fig. 7, and the processing is repeated for the other 埠. On the other hand, if all the ticks have been confirmed (YES in step S19), as shown in step S20, the message "There is a possibility that all of the defects have been retrieved, but all of them have failed, and cannot be activated" is displayed. Displayed on the display unit 19 (the OS startup error ends).

(5) At step S12 of Fig. 9, the device is referred to in the machine management table 17c. If the number of times the OK is initiated for the device is 0 at all ( (YES in step S13), and the number of attempts to start the device is not 0 at all (ie, the number of attempts to start is more than once at any time) ( If NO in step S14, it can be judged that the device is malfunctioning. Then, the process proceeds to step S15, and a message "There is a possibility that the device has failed, and cannot be activated" is displayed on the display unit 19 (the OS startup error is ended).

The above-described steps S16, S20, and S15 are operations of the BIOS program as the error type determining unit.

On the other hand, if the number of times the OK is initiated for the device is not 0 at all times (i.e., the number of times the start OK is more than one at any time) (NO at step S13), or the number of attempts to start the 在 is at all 埠If it is 0 (YES in step S14), the device is normal or defective, and it cannot be judged based on the machine management table 17c of the current point. Then, the process proceeds to step S21 of Fig. 10 which is described later.

(6) In step S21 of Fig. 10, only the number of times (+1) of the device which is currently referred to by the machine management table 17c in the information storage ROM 17 of the own computer PC1 is attempted to start the device. In other words, a measurement method corresponding to the combination of the device and the device is used on the body portion 53 of the machine management table 17c. For example, if the description before the rewriting is 0/0, the reference is rewritten to 0/1.

Next, as shown in step S22, an attempt is made to start the OS stored in the device. Then, if the startup of the OS is normally completed (YES in step S23), it can be judged that the device is normal. Then, as shown in step S24, only the number of activations of the device in the column of the device management table 17c in the information storage ROM 17 of the computer PC1 itself is added once (+1). In other words, the measurement method corresponding to the combination of the device and the device is used in the body portion 53 of the machine management table 17c. For example, if the description before the rewriting is 0/1, it is rewritten to 1/1. Thereby, the state in which the OS can be used is obtained.

In addition, the processing of the next priority is performed in step S16 of FIG. 8, and the process of starting the device connected to the device in step S22 of FIG. 10 is the operation of the OS selection processing unit of the BIOS program. By the operation of the OS selection processing unit in the BIOS program, if the normal storage device connected to the normal device exists, the user does not need to worry about starting the computer PC1.

On the other hand, if the OS is not normally started in step S22 (NO in step S23), the BIOS program judges that the device is malfunctioning, and the OS cannot be used to end the processing.

The above-described step S23 is an operation of the BIOS program as a connection error detecting unit. Further, steps S21 and S24 are operations of the BIOS program as the management table creation unit.

Whenever the power is turned on, the computer PC1 performs the operations of FIGS. 6, 7, 8, 9, and 10. Thereby, for each combination of the device and the device, the BIOS program aggregates the number of times the combination attempt is started and the number of times the combination is normally started (the number of startup OKs) as a detection result on the machine management table 17c. Thereby, for the combination of the device and the device in which the error has occurred, the error can be increased because of the failure of the device or the accuracy of the determination of the failure of the device.

In the above embodiment, the combination of the physical physics and the device is displayed in the form of the number of attempts to start the combination and the number of times the combination is normally started (the number of times of normal startup) / (the number of attempts to start). It is on the body portion 53 of the machine management table 17c, but is not limited thereto. It is also possible to display whether or not the combination of physical devices and devices, such as ○ or ×, or OK or NG, is only indicated by a symbol. Alternatively, it is also possible to display whether or not to start normally by a binary value as in 1 or 0.

Further, in the above embodiment, the operation of the machine management table 17c is executed by the BIOS program, but the invention is not limited thereto. The action on the machine management table 17c can also be performed using the OS or the application software (a program for execution on the OS).

Fig. 2 shows a structure of a network system (indicated by reference numeral 100) according to an embodiment of the present invention.

The network system 100 is provided with the above-mentioned computer (hereinafter referred to as "client device") PC1 and the client via the network 900. The computers PC1 are configured in the same manner as the client PCs PC2, PC3, PC4, PC5, and the host PC0 as the host computer. Moreover, the network 900 can also be either wired or wireless.

The machine management table 17c of the client machine PC1 is displayed as a table #1 in FIG. 2 below the client machine PC1. The client machines PC2, PC3, PC4, and PC5 respectively have the same tables #2, #3, #4, and #5 as the table #1 (that is, the machine management table 17c).

As shown in FIG. 4, the host PC0 is provided with an information storage ROM 17' composed of a flash ROM in place of the information storage ROM 17 of the client machine PC1. Similarly to the information storage ROM 17, the information storage ROM 17' stores the operation setting data 17a for the CPU 11 or the chipset 14, the priority activation device information 17b, and the machine management table of the local machine (host PC0) as a management table. 17c. Further, the information storage ROM 17' includes an additional management table storage unit, and stores a machine management table 17d of other devices (client machines PC1, PC2, ..., PC5). The machine management table 17c of the local machine (host PC0) is displayed above the host PC0 as the table #0 in FIG. 2, and partially overlaps the table #0 to display the tables #1, #2, #3, #4. , #5.

The BIOS programs of the client devices PC2, . . . , PC5, and the host PC0 are identical to the BIOS programs of the client device PC1, respectively, and the machine management table 17c shown in FIG. 6, FIG. 7, FIG. 8, FIG. 9, and FIG. Actions. Therefore, the BIOS programs of the client machines PC2, . . . , PC5 and the host PC0 are exactly the same as those in the client machine PC1. When an error occurs in the physical port of the connected device, it can be judged that the error is due to the failure of the device itself or Because of physical failures.

In addition, the host PC0 has a client verification tool as an application software that operates on the OS in this example. This client check tool is stored in a bootable storage device that the host PC0 has.

Figure 11 and Figure 12 show the action flow of using this client check tool. The steps in Figures 11 and 12 are performed by the client check tool. For the sake of brevity, the main body (client check tool) for explaining the operation will be appropriately omitted below.

First, as shown in step S101 of Fig. 11, the data of the machine management table 17c in the information storage ROM 17 of a certain client device is acquired via the network 900.

Next, as shown in step S102, it is confirmed that the machine of the client machine manages the line 17c (埠). Here, for this line, if the number of times of starting the OK is 0 for all devices (YES in step S103), and the number of attempts to start is 0 for all devices (YES in step S104), it cannot be judged at the current point. Whether the flaw is broken. Then, the process proceeds to step S105 of Fig. 12 which will be described later.

On the other hand, for this line, if the number of times of starting the OK is not 0 for any device (that is, the number of times of starting the OK is more than once in any device) (NO in step S103), or the number of attempts to start is not 0 for any device. (That is, the number of attempts to start is one or more times in any device) (NO in step S104), as shown in step S109, it is determined whether the number of attempts to start is equal to the number of times of starting the OK. Here, for a device combined with the row (埠), if the number of attempts to start is different from the number of startup OKs (NO in step S109), the possibility of the problem is displayed as a warning on the host PC0. The display unit (the same as the display unit 19 in Fig. 1 . Sample). On the other hand, for all devices combined in the row (埠), if the number of attempts to start and the number of startup OKs are equal, it can be judged that the defect is normal.

Next, as shown in step S105 of Fig. 12, the list (device) of the machine management table 17c of the client device is confirmed. Here, for this column, if the number of activations is 0 for all 埠 (YES in step S106), and the number of attempts to start is 0 for all devices (YES in step S107), as shown in step S108. In this example, "no problem" is displayed on the display.

On the other hand, for this column, if the number of times of starting the OK is not 0 for any one (that is, the number of times of starting the OK is one or more times), (NO in step S106), or the number of attempts to start is not 0 for any one. (That is, the number of attempts to start is one or more times) (NO in step S107), as shown in step S111, it is determined whether the number of attempts to start is equal to the number of times of starting the OK. Here, for a certain combination of the columns (devices), if the number of attempts to start is different from the number of startup OKs (NO in step S111), the possibility that the device has a problem is displayed as a warning on the display unit. . On the other hand, for all the combinations of the columns (devices), if the number of attempts to start and the number of startup OKs are equal, it can be judged that the flaw is normal. Then, as shown in step S108, "no problem" is displayed on the display unit.

The client collation tool executes the processing from step S102 of Fig. 10 to step S112 of Fig. 12 with respect to each row and each column of the machine management table 17c of the client machine.

The client collation tool executes the processing from step S101 of Fig. 10 to step S112 of Fig. 12 for each of the client machines PC1, PC2, ..., PC5.

Thereby, the host PC0 can grasp the fault conditions of other computers in the network system 100, that is, devices or physical devices in the client machines PC1, PC2, ..., PC5. Therefore, the host PC0 can be used to centrally manage a plurality of computers including the host PC0 and the client machines PC1, PC2, ..., PC5.

In the above embodiment, the flaw detecting device of the present invention is applied to a computer, but the invention is not limited thereto. The sputum anomaly detecting device of the present invention is widely applicable to an electronic device or system including a plurality of cymbals and a device connected to the cymbal. For example, the sputum anomaly detecting apparatus of the present invention can be applied to a system including a switching hub or a wired router having a plurality of ports and a device connected thereto.

11‧‧‧CPU

12‧‧‧ Controller

13‧‧‧ Controller

14‧‧‧ Chipset

15‧‧‧RAM

16‧‧‧BIOS-ROM

17, 17'‧‧‧ Information Storage ROM

17a‧‧‧Action setting data

17b‧‧‧Priority start device information

17c, 17d‧‧‧ Machine Management Form

18‧‧‧LAN interface

19‧‧‧ Display Department

51‧‧‧ head

52‧‧‧Side side

53‧‧‧ Body Department

54‧‧‧Error Code Resume

55‧‧‧埠Error code column

56‧‧‧Device error code column

90‧‧‧ motherboard

100‧‧‧Network system construction

900‧‧‧Network

USB1, USB2, USB3, USB4‧‧‧USB埠

SATA1, SATA2, ..., SATA6‧‧‧ SATA埠

Fig. 1 is a view showing a structure of a computer block according to an embodiment of the flaw detecting device of the present invention.

2 is a diagram showing a network system configuration in which a plurality of computers as shown in FIG. 1 are communicably connected via a network.

Fig. 3 is a view showing the contents of the information storage ROM (Read Only Memory) stored on the computer (corresponding to the client device in Fig. 2) of Fig. 1.

Fig. 4 is a view showing the memory contents of the information storage ROM mounted on the host in Fig. 2;

FIG. 5 is a diagram showing the contents of a machine management table stored in the information storage ROM.

Fig. 6 is a view showing a part of an operation flow of the computer of Fig. 1.

Fig. 7 is a view showing a part of an operation flow of the computer of Fig. 1.

Fig. 8 is a view showing a part of an operation flow of the computer of Fig. 1.

Fig. 9 is a view showing a part of an operation flow of the computer of Fig. 1.

Fig. 10 is a view showing a part of an operation flow of the computer of Fig. 1.

Figure 11 is a diagram showing a part of the operation flow of the host in Figure 2.

Figure 12 is a diagram showing a part of the operation flow of the host in Figure 2.

51‧‧‧ head

52‧‧‧Side side

53‧‧‧ Body Department

54‧‧‧Error Code Resume

55‧‧‧埠Error code column

56‧‧‧Device error code column

Claims (9)

An anomaly detecting device for detecting a plurality of physical anomalies of a plurality of physical anomalies respectively connected to the device, characterized by comprising: a connection error detecting unit that detects that the device passes the physical layer when a device is connected to a physical device Whether the operation is normal or an error occurs; the management table creation unit collects the detection result of the connection error detecting unit, and displays whether the display is normal for each of the physical devices of the plurality of physical devices and the combination of the devices of the plurality of devices. An operation table for generating an error or an error; and an error type determination unit for determining, based on the content of the management table, a combination of a physical device and a device that generated the error, because the device is malfunctioning or because of the physical Awkward failure. The abnormality detecting device according to the first aspect of the patent application, wherein the error type determining unit is a combination of a specific physical device and a specific device that has generated an error, and refers to the management table according to the specific device among the plurality of devices. Whether the other device has been normally operated by the specific physical defect described above, and determines whether the error is due to the failure of the specific physical defect, and according to whether the specific device has passed the other physical physical defects other than the specific physical device Physically and normally, it is judged whether the above error is due to the failure of the above specific device. For example, the abnormality detecting device of claim 1 or 2, wherein the management table creating unit is for each of the plurality of physical objects The combination of each device of the plurality of devices and the number of times the connection is performed and the number of normal operations or errors are recorded on the management table. The 埠 abnormality detecting device according to any one of claims 1 to 3, wherein the connection error detecting unit outputs an error code indicating the error when detecting the occurrence of the error, and the management table creating unit is based on the connection error. The output of the detecting unit records an error code generated for each physical volume of the plurality of physical files and an error code generated for each device of the plurality of devices on the management table. A computer characterized by comprising an anomaly detecting device according to any one of claims 1 to 4. The computer of claim 5, comprising: a motherboard equipped with a BIOS that functions as the connection error detecting unit, the management table creating unit, and the error type determining unit; and a management table memory unit that stores the management table The plurality of devices include a storage device storing an operating system for the computer, and the plurality of physical devices include a cassette mounted on the motherboard for connecting the storage device. The computer of claim 6, wherein the plurality of devices include a plurality of storage devices respectively storing the operating system for the computer, wherein the BIOS includes an OS selection processing unit, and the OS selection processing unit determines the error type according to the error type. Ministry judgment result The bootable operating system that is not stored in the operating system of the plurality of storage devices is selected to be activated or not activated. A network system is a network system for communicatively connecting a plurality of computers according to any one of claims 5 to 7 via a network, wherein one of the plurality of computers is In addition to the management table storage unit of the management table of the host computer, the main computer includes an additional management table memory unit for storing the management table of the computer other than the main computer among the plurality of computers. . A program for causing a computer to execute a plurality of physical anomaly detection methods for detecting a plurality of physical anomalies respectively connected to the device, wherein the method for detecting an anomaly abnormality comprises: a connection error detection step, which is connected to a physical device by a device And detecting a normal operation or an error of the device by the physical device; and a management table creation step of collecting the detection result of the connection error detection step, for each physical device of the plurality of physical devices and each device of the plurality of devices a combination of the management table for displaying whether the operation is normal or the error is generated; and the error type determination step, which is based on the content of the management table, and determines the error for the combination of the physical device and the device that generated the error. The failure of the device is due to the failure of the above physical defects.