JP2009176096A - System and method for installing operating system on data preservation server at remote end from computer including no hard disk drive - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a system and method for installing an OS on a data preservation server at an remote end from a computer that does not include a kind of hard disk drive. <P>SOLUTION: Using a startup firmware and a network preservation driver, a disk drive that can be installed from an OS is recognized by connection of a logical unit space and the disk drive. The startup firmware acquires a network parameter to preserve a driver, and provides a control function of the network disk to an installation program. The computer including no hard disk drive can, when transmitting a complicated operation procedure for generating a system image file as well as an image file itself to the logical unit space by a process thereafter, avoid operation error due to user's unfamiliarity with flow, to reduce human error during system construction. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

The present invention is a system and method for introducing an OS into a remote data storage server from a computer that does not have a fixed disk device. In particular, the OS is introduced into a remote data storage server from a computer main unit that does not have a fixed disk device. It is related to the method with the system.

For IT personnel, large-scale computer system management is a very heavy burden. In a computer that does not have a fixed disk device, centralized management of storage devices can not only reduce the difficulty of hardware / software management of the computer, but can also improve the utilization effect of storage space.

The design concept of this configuration is to remove the fixed disk device (Hard Drive) of the computer main machine that becomes a management bottleneck, by network data storage technology, after the computer power is turned on via a network storage protocol (Network Storage protocol) between networks, Immediately connect to the network and the remote data storage server, and acquire the disk device information necessary for OS startup. The network data storage server allocates a space in advance in a physical disk device, introduces and stores an OS related file in the space, and serves as a startup disk device for a computer that does not have a fixed disk device.

FIG. 1 shows an application mode diagram of a computer and a network data storage system that do not have a kind of fixed disk device. Mainly including a data storage server 11, a network communication device (switcher, router, hub, etc.) 12, a plurality of computers (Disk Computers) 131 to 133 having no fixed disk device, and a network 14, the data storage server 11 and a plurality of Computers 131 to 133 that do not have a fixed disk device are connected to the network 14 and devices such as a network interface and the network communication device 12, and communicate with the data storage server 11 and the computers 131 to 133 that do not have a plurality of fixed disk devices, Establish a network communication agreement and send and receive data. SCSI over IP or SCSI over FC network packets are transmitted to the data storage server 11 from the plurality of computers 131 to 133 that do not have the fixed disk device, and the disk device (not shown) of the data storage server 11 reads and writes the disk data. The data or response is sent from the data storage server 11 via the network 14 to the computer that does not have the requested fixed disk device.

FIG. 2 is a technical aspect diagram of computer startup without a known fixed disk device. The computers 21, 210 and 211 having no fixed disk device use a normal computer system, and each of them includes one or more microprocessors 22, a network interface 23 and a non-volatile memory 24. However, the computers 21, 210, and 211 that do not have a fixed disk device do not have a physical disk device attached. Instead, each of the computers 21, 210, 211 having no fixed disk device is provided with a non-volatile memory 24, the program of the boot firmware 26 is stored in the non-volatile memory 24, and the boot firmware 26 is networked. A storage driver 27, a network agreement driver 28, and a network interface driver 29 are provided. After powering on the computer 21 having no fixed disk device, the basic input / output system (hereinafter referred to as BIOS) on the system automatically reads the startup firmware 26 from the nonvolatile memory 24. Then, loading and execution are started in the main memory 25 of the computer system. Due to the function of the startup firmware 26, the computers 21, 210, and 211 that do not have a fixed disk device execute the startup firmware 26 via the microprocessor 22, control the network interface 23, and execute the BIOS. , Together with the data storage server 213, connected via the network 212, reads the information of the disk devices 214 and 216 and the OS image files 215 and 217 stored in the disk device, the BIOS executes the OS and starts the OS Complete the task.

FIG. 3 is a diagram showing an aspect of OS introduction using a known technology image file. The personal computer 31 uses a normal computer system. The computer is connected to one or more optical disk devices 34 and one or more fixed disk devices 32, respectively. The optical disk device 34 reads data from an OS installation disk 35 and uses the OS installation disk 35 to generate the computer system. Can be started. The fixed disk device 32 uses a normal disk device and has a storage space for the OS 33a and various application programs 33b. The personal computer 31 uses the OS installation disk 35 to introduce the OS file, and then the fixed disk device 32. Thus, the OS 33a can be activated to execute the application program 33b. In order to make the OS have a boot capability for a computer that does not have a fixed disk device, at least the computer that does not have the fixed disk device provided in the personal computer 31 stores the disk image data for booting in the data storage server 36 in advance. To prepare for reading of the disk device and the OS file via the data storage server 36. At present, as a general method in the industry, an OS file stored in the fixed disk device 32 of the personal computer 31 is transferred via the network 310 to a file stored in the fixed disk device 32 by a method of program upload (Upload program). All are copied to the disk device 37 of the data storage server 36. However, the logic space 39 allocated in advance by the data storage server 36 and the space of the fixed disk device 32 are made to coincide with each other, and all the data of the fixed disk device 32 is copied to the logic space 39 for later computer processing. The OS image file 38 for starting is prepared.

In order to start the OS image file 38, at least an OS core program, an application program, and user setting data are required. After the OS is installed in the fixed disk device 32, it is necessary to upload the file of the fixed disk device 32 to the logic space 39 set in advance by the network storage service task using the upload tool. The upload method is to copy the disk space or copy all of the OS 33a and each application program 33b stored in the fixed disk device 32 via the network 310 to the disk logic space 39 of the network storage service task. The computer 310 having no fixed disk device is connected to the network storage service task, acquires the disk space and OS on the network, and starts the OS or executes each application program. The problem of OS management and application program management of a computer that does not have a fixed disk device by a disk image file is that the OS 33a on the fixed disk device 32 is uploaded to the network storage server 36. After the application program 33b is installed, the files of all the disk devices are copied to the disk logic space 39 on the network using another tool.

In addition, it is difficult to manage the OS by using a disk image file. If an application program contained in the image file is modified, the file of the device is modified by the physical disk device in which the image file is constructed. In addition, a new disk image file must be uploaded again. Since the above-described operation is completely different from the normal OS installation flow, it is confusing for the IT manager, and causes an operation error or data corruption in the image file upload process, and the OS cannot be started normally.

As described above, in the process of constructing a computer that does not have a fixed disk device, the method of introducing the OS into the network disk space is because the operation of data conversion or image file upload is more intuitive and can reduce human error. It is a solution that the industry strives for.

It is a main object of the present invention to provide a system and method for introducing an OS system into a remote data storage server from a computer having no fixed disk device. The boot firmware of the present invention is stored in a non-volatile memory of a computer motherboard or a read-only memory of a network card or stored in a part of the computer system BIOS. The startup firmware includes a network storage program, a network communication program, and a network interface program. The startup firmware is loaded into the main memory of the computer system after the computer power is turned on, and is previously set in a non-volatile memory, or obtains network parameters from a dynamic host configuration protocol (Dynamic Host Protocol). The startup firmware automatically establishes a connection with the remote data storage server and acquires information on the authorized disk device. Subsequently, the computer system uses the OS introduction optical disc to execute a computer booting and optical disc OS introduction program.

At the stage of installing the OS program, it is determined whether or not the system has a network communication agreement and network control capability. If the specified value of the installation program does not have a network connection function, the present invention provides a function of automatically loading a network interface driver, a network communication driver and a network storage driver having admissibility. Is the purpose. The network interface driver provides a computer network controller control function, the network interface driver provides a computer with a network controller control function, and the network communication driver provides an upper-layer communication agreement and a network packet processing function. Executes connection of the network disk device and communication with the OS. After the loading is completed, the network storage driver continues to execute the startup program control task, which has established the connection with the remote data storage server again, according to the startup firmware pre-connection information. At this time, the startup firmware continues to maintain information and functions for connecting to the data storage server, and prepares for an information call of a disk device in a lower hierarchy than the OS. After the network storage driver obtains the disk device information from the data storage server, it immediately responds to the OS installation program for physical disk device identification by the OS installation program. Thereafter, the OS installation program uses the disk device to perform disk formatting and OS file installation.

The present invention alleviates the hurdles for building a computer system that does not have a fixed disk device, makes the process the same as the basic OS installation, and once the user installs the physical disk device, the file of the disk device is stored in the data storage server. The OS can be installed on a computer that does not have a fixed disk device by the OS installation program, instead of creating an image file. The method of the present invention provides a reliable system construction flow for a computer that does not have a fixed disk device, and a fixed disk device such as a user incorrectly constructing an OS system file due to inexperience in creating a disk image file, or forgetting to upload an OS system file. Abnormal start-up of computers that do not have can be avoided. Therefore, the method of the present invention can greatly reduce the trouble caused by mishandling, and can simplify the complexity of the entire system operation.

FIG. 4 is a schematic diagram of a system in a preferred embodiment of the present invention. In a preferred embodiment in which an operating system is introduced into a remote data storage server from a computer without a fixed disk device according to the present invention, at least the computer industry 41 without a fixed disk device, a data storage server 411 and a network 410 are provided. The computer 41 and the data storage server 411 that do not have a disk device are also connected to the network 410, and the network 410 uses the Internet or a local area network (LAN). The preferred embodiment of the present invention further includes other functional units, but for the sake of simplicity of illustration and description, this configuration is limited to that associated with the preferred embodiment of the present invention. As an example, a computer 41 that does not have a fixed disk device and a microprocessor, a storage device, a network controller, or a network switcher or router of a network device in the data storage server 411 are not shown. Further, the number of computers 41 having no fixed disk device is not limited to one shown in the preferred embodiment of the present invention. The number may be two, three or more. In the following preferred embodiments, a computer 41 and a data storage server 411 that do not have a fixed disk device will be described.

The data storage server 411 uses a computer server having data management and data storage functions. The server includes at least a microprocessor and a main memory, and controls the network 410 and the disk device by combining the microprocessor and the main memory. In a preferred embodiment of the present invention, the data storage server 411 provides a disk device for starting an OS and executing an application program to a computer 41 having no fixed disk device. Therefore, the data storage server 411 has at least a logic unit space 412, and the logic unit space 412 introduces an OS file and data for starting the computer 41 not having a disk device in advance. The unit space 412 uses a logic code as a basic unit for disc space identification, and the data storage server 411 partitions the plurality of logic unit spaces 412 and assigns a unique logic unit code to each logic unit space 412. Thereafter, the computer 41 having no fixed disk device can identify the correspondence between the disk device to be acquired and the data storage server from the logic unit code.

The computer 41 having no fixed disk device is a computer or server PC having no standard fixed disk device, and includes at least a microprocessor, an input device, a memory device, and a network controller. The network controller enables connection to a network switcher or router, and provides a network storage function of the computer 41 having no fixed disk device. The computer 41 having no fixed disk device further includes a startup firmware 46, which is a kind of firmware program, which is usually stored in a non-volatile memory on the computer motherboard, Or it is embedded in a basic input / output system (Basic Input Output System, hereinafter referred to as BIOS) of a computer. As an example, it is embedded in a boot ROM (Boot ROM) of a network card or directly in a pre-boot execution environment (hereinafter referred to as PXE) program. The startup firmware 46 is characterized by the fact that the BIOS automatically loads and executes the startup firmware 46 in the memory device when the computer is started. The boot firmware 46 can control the network controller, and performs the account authentication to the authentication server or the IP address of the computer via the dynamic host configuration protocol (DHCP) at the BIOS execution stage. Implement network-related communication agreements. Further, the computer 41 having no fixed disk device reads the OS installation program 42, and the OS installation program 42 is usually stored in at least one VCD or DVD optical disk. On the other hand, the OS installation program 42 is read and executed from an input device of a computer 41 that does not have a fixed disk device, and is provided as a user OS system setting and storage device selection tool. In the preferred embodiment of the present invention, Microsoft Windows (registered trademark) and Linux OS are mainly targeted. In addition, the introduction program includes a preinstallation system such as a Windows Preinstallation Environment (WinPE).

The boot firmware 46 has a network access capability, and provides the OS installation program 42 with means for introducing an OS file into the remote data storage server 411. As a specific method, after powering on the computer 41 without the fixed disk device, the startup firmware 46 is read from the nonvolatile memory by the BIOS and loaded into the memory device of the computer 41 without the fixed disk device. The startup firmware 46 has three main subroutines. A network storage program 47, a network communication program 48, and a network interface program 49, respectively. Among them, the network storage program 47 provides the processing capability of upper-layer network communication agreements such as connection authentication and data exchange between the computer 41 and the data storage server 411 that do not have a fixed disk device. In a preferred embodiment of the present invention, iSCSI
(Internet Small Computer Systems Interface) As an example of a network communication agreement, connection to the data storage server 411 is performed via the network storage program 47. On the other hand, the network communication program 48 is responsible for network layer packet exchange such as TCP / IP network communication agreements, and establishes, divides, merges and maintains connections of network packets. The network communication program 48 receives a network request from the network storage program 47, passes the request to the lower-layer network program 49, replaces the network request with a network packet, and sends it to the physical network 410 line. The network interface program 49 is a network controller control program, and the network controller is exemplified by an Ethernet (registered trademark) controller. After receiving the packet from the network controller of the computer 41 that does not have a fixed disk device, the network interface program 49 takes out the network packet from the buffer memory area and receives the network packet. Then, the data is sent to the network communication program 48 to perform network packet analysis work.

The OS installation program 42 is read into a memory from an input device such as an optical disk device of a computer 41 that does not have a fixed disk device, a network disk, or a removable disk device, and is executed. The OS installation program 42 checks the peripheral devices of the computer in advance and loads an appropriate driver. The drivers are obtained from an optical disk device, a floppy disk device, an external storage device, or a network disk, respectively. The OS installation program 42 has three main subroutines. A network storage driver 43, a network communication driver 44, and a network interface driver 45, respectively. In the method of the present invention, since the OS installation program 42 itself does not necessarily have the network control capability, it is necessary to determine whether the OS installation program 42 has a network communication function from the computer 41 that does not have the fixed disk device. The network interface driver 45 controls the program of the network controller by the computer 41 that does not have the fixed disk device. The network interface driver 45 provides the computer 41 that does not have the fixed disk device with a network transmission / reception function. On the other hand, the network communication driver 44 provides a network communication agreement processing function to the computer 41 that does not have a fixed disk device, and this function includes a transmission control protocol (Transmission Control Protocol, TCP), a user diagram protocol (User Diagram Protocol, UDP), Network communication protocol stacks such as Internet Protocol (Internet Protocol, IP) and Address Resolution Protocol (ARP) are included. The network storage driver 43 is a program for communicating with the remote data storage server 411. The network storage driver 43 obtains functions such as information stored in the logic unit space 412 of the remote data storage server 411 and a command request of the logic unit space 412 in the computer 41 having no fixed disk device, and the OS installation program 42. And a physical logic unit space 412 is provided to the introduction program.

Refer to FIGS. 4 and 5 for the communication between the OS installation program and the startup firmware and the implementation of network parameter acquisition. FIG. 5 is an operation mode diagram of the OS installation program and the startup firmware in the preferred embodiment of the present invention. Among them, the computer 41 having no fixed disk device has a startup firmware 46 in addition to the memory device 53, and an OS installation program 42.
(The OS installation program 42 is normally stored in one or more VCD or DVD optical disks and is read and executed from the input device of the computer 41 that does not have a fixed disk device). At least a network storage driver 43 is provided for processing. Further, the startup firmware 46 has startup firmware mapping 52, and the startup firmware mapping 52 includes network parameters (the IP address of the data storage server 411, the IP address of the computer 41 without the fixed disk device, and the logic unit). And the startup firmware mapping 52 is stored in the memory device 53 of the computer 41 having no fixed disk device. The memory device 53 may be a main memory inside the computer 41 not having a fixed disk device, or a memory device connected to the outside of the computer 41 not having a fixed disk device. An interrupt vector (Interrupt Vector) 51 is registered in the address of the startup firmware mapping 52 inside the memory device 53 of the computer 41 that does not have a fixed disk device.

The startup firmware 46 is loaded into the memory device 53 and executed by the BIOS after the computer 41 having no fixed disk device is turned on. The boot firmware 46 establishes a disk device connection via the network 410 and the remote data storage server 411, and stores the network parameter information of the connection in one boot firmware mapping 52. The firmware mapping 52 is stored in the memory device 53 of the computer 41 that does not have a fixed disk device. Subsequently, the activation firmware 46 registers the disk interrupt vector 51 in the memory device 53 of the computer 41 that does not have a fixed disk device. In a preferred embodiment of the invention, the known INT 13H is illustrated. Through the above-described process, the preparation work for the startup firmware 46 is completed. Thereafter, after the computer is started by the OS installation program 42, the network storage driver 43 is stored in the remote storage data storage server 411 from the startup firmware mapping 52 prepared in advance by the startup firmware 46. The network parameter is taken out, and the data storage server 411 is connected using the network parameter. The OS installation program 42 calls the startup firmware 46 via the interrupt vector 51 according to the demand of the system, and acquires low-level information. The startup firmware 46 returns the information acquired by the above connection or acquires related disk information from the data storage server 411 at the remote end through the network 410 connection, and returns it to the OS installation program 42.

FIG. 6 is a system flow diagram in a preferred embodiment of the present invention. Among them, a computer not having a fixed disk device and a data storage server are connected to a network, and the data storage server has a logic unit space. On the other hand, in addition to storing the startup firmware mapping in a computer that does not have the fixed disk device, it has a network controller. In this introduction method, after the computer 61 without the fixed disk device is turned on, the BIOS of the computer without the fixed disk device reads the startup firmware from the nonvolatile memory and loads the startup firmware into the main memory 62. The startup firmware controls the network controller via the network interface program and establishes a network connection by the network communication program. On the other hand, the startup firmware acquires network parameters from the nonvolatile memory, or acquires network parameters from the DHCP server according to a DHCP communication agreement. The network parameter provides information necessary for the connection 63 to the network storage program and the logic unit space, and the activation firmware records the network parameter and registers the interrupt vector 64 in the activation firmware mapping. After the boot firmware obtains one or more authorized logic unit spaces from the logic unit space, there is no OS file for booting in the logic unit space. A computer that does not have a fixed disk device is started from an input device (such as an optical disk device). At this time, the computer having no fixed disk device is started from the OS installation disk 65, the installation program is loaded into the main memory of the computer, and the OS installation program 66 is executed.

At this stage, the system checks the network access capability of the OS installation program and the network agreement 67 support capability. If the OS installation program does not have network access capability at this time, the network interface driver 68 is loaded to control the network controller of the computer. Subsequently, the network communication driver 69 is loaded to provide various network communication protocol stacks. Finally, the network storage driver 610 is loaded, and the network storage driver provides disk information and a disk operation function to the OS installation program. In the preferred embodiment of the present invention, an iSCSI communication agreement is used. If the OS installation program itself has a network connection capability, only the network storage driver 610 is installed.

At this time, since the network storage driver does not know how to connect to the network data storage server, the network storage driver connects to the logic unit space 611 based on the setting of the startup firmware. Since the method for obtaining the network parameters of the startup firmware is a known technique, the description of the iBFT (iSCSI Boot Firmware Table) format described in the Power Control Interface (ACPI) literature can be referred to here. Will be omitted. After the network storage driver completes the connection with the logic unit space, the installed program acquires the physical disk device by sending the acquired disk information back to the OS installation program, and the disk format (Format) and the disk device The OS file introduction operation 612 can be started. By completing the introduction operation 613, the entire flow of the present invention is completed.

FIG. 7 is a flow diagram of the introduction method in the preferred embodiment of the present invention. Among them, a computer having no fixed disk device has a memory device, and a data storage server has a logic unit space. Computers and data storage servers that do not have the fixed disk device are also connected to the network. The method includes the following.

This is because the startup firmware is provided inside a computer that does not have a fixed disk device, and the startup firmware acquires network parameters for connection to the data storage server. The network parameter includes at least a parameter of a logic unit space of the data storage server. The network parameters are recorded in the memory device of the computer not having the fixed disk device by the startup firmware, and the interrupt vector is registered in the memory device of the computer not having the fixed disk device. as well as,

An OS installation program is provided for reading by a computer that does not have a fixed disk device, and parameters of the logic unit space are obtained by calling the interrupt vector from the OS installation program. The boot firmware responds to the interrupt request, boots a computer that does not have the fixed disk device by the OS installation program, and executes the OS installation program in the logic unit space of the data storage server.

Figure of application of a kind of computer without a fixed disk device and network storage system Technical aspect diagram of activation by a computer having no known fixed disk device OS image file introduction mode diagram of known technology System schematic diagram in a preferred embodiment of the present invention Operational diagram of OS installation program and startup firmware in a preferred embodiment of the present invention System flow diagram in a preferred embodiment of the present invention. Flow diagram of introduction method in a preferred embodiment of the present invention

Explanation of symbols

11 Data storage server 12 Network communication device 131 Computer without fixed disk device 132 Computer without fixed disk device 133 Computer without fixed disk device 14 Network 21 Computer without fixed disk device 22 Microprocessor 23 Network interface 24 Non-volatile memory 25 Main Memory 26 Boot firmware 27 Network storage driver 28 Network agreement driver 29 Network interface driver 210 Computer 211 without fixed disk device 211 Computer without fixed disk device 212 Network 213 Data storage server 214 Disk device 215 Operating system image file 216 Disk device 21 7 Operating system image file 31 Personal computer 32 Fixed disk device 33a Operating system 33b Application program 34 Optical disk device 35 Operating system installation disk 36 Data storage server 37 Disk device 38 Operating system image file 39 Disk logic space 310 Network 41 Computer without fixed disk device 42 Operating System Installation Program 43 Network Storage Driver 44 Network Communication Driver 45 Network Interface Driver 46 Startup Firmware 47 Network Storage Program 48 Network Communication Program 49 Network Interface Program 410 Network 411 Data Storage Ba 412 Logic Unit space 51 interrupt vectors 52 boot firmware mapping 53 storage device

Claims (13)

A computer without the fixed disk device has a memory device, and a data storage server has a logic unit space. The computer not having the fixed disk device and the data storage server are also connected to the network; the method includes the following contents:
Boot firmware is provided inside a computer having no fixed disk device, and the boot firmware is for acquiring network parameters for connection to the data storage server, and the network parameters are at least the logic of the data storage server. Having unit space parameters, recording the network parameters in a memory device of a computer not having a fixed disk device, and registering an interrupt vector in the memory device of the computer not having the fixed disk device; ,
An operating system installation program is provided for reading a computer that does not have a fixed disk device, the logic unit space parameters are obtained by calling the interrupt vector from the operating system installation program, and the operating system installation program has the fixed disk device installed. A method of introducing an operating system to a remote data storage server from a computer that does not have a fixed disk device that executes an operating system installation program in the logic unit space of the data storage server. 2. The method of introducing an operating system to a remote data storage server from a computer having no fixed disk device according to claim 1, wherein the boot firmware responds to an interrupt vector call by an operating system installation program. The boot firmware has boot firmware mapping, the boot firmware mapping stores network parameters, and the boot firmware mapping is recorded in a memory device of a computer having no fixed disk device. A method for introducing an operating system to a remote data storage server from a computer having no fixed disk device according to claim 1. A network storage driver is included in the operating system, and the network storage driver provides a logic unit space information acquisition and a logic unit space command request of a data storage server by a computer having no fixed disk device, and the operating system installation program The method of introducing an operating system to a remote data storage server from a computer having no fixed disk device according to claim 1, wherein a physical logic unit space is provided. The operating system installation program includes a network storage driver, a network communication driver, and a network interface driver. The network interface driver provides a network transmission / reception function to a computer that does not have a fixed disk device, and the network communication driver does not have a fixed disk device. A network communication agreement processing function by a computer is provided, and the network storage driver provides a computer that does not have a fixed disk device to obtain a logic unit space of the data storage server and a command request for the logic unit space. 2. An operating unit from a computer having no fixed disk device according to claim 1, characterized in that a large logic unit space is provided. A method of introducing the I ring system in the data storage server of the remote end. The startup firmware includes a network storage program, a network communication program, and a network interface program, the network storage program provides a processing function for an upper layer network communication agreement, the network communication program performs network layer packet exchange, 2. The method of introducing an operating system to a remote data storage server from a computer having no fixed disk device according to claim 1, wherein the network interface program receives and transmits network packets. 2. The data storage server of a remote end of an operating system from a computer without a fixed disk device according to claim 1, wherein the memory device of the computer without the fixed disk device is a main memory inside the computer without the fixed disk device. How to introduce. The memory system of the computer without the fixed disk device is a memory device externally attached to the computer without the fixed disk device. The method to introduce to the data storage server. Including a computer without a fixed disk device, a data storage server and a network, and also has a computer and data storage server without the fixed disk device connected to the network;
The data storage server has at least one logic unit space;
A memory device is provided in a computer that does not have the fixed disk device, a startup firmware is attached, an operating system installation program is read, and the startup firmware records the network parameters of the data storage server connection in the memory device, and the network The parameter has at least a logic unit space parameter, and an interrupt vector is registered in the memory device. The operating system introduction program has at least a network storage driver, and the network unit driver calls the interrupt vector to call the logic unit space. Start the computer that has no fixed disk device from the operating system installation program after obtaining the parameters;
The logic unit space is a system that introduces an operating system to a remote data storage server from a computer that does not have a fixed disk device provided to install the operating system by an operating system introduction program. The startup firmware includes a network storage program, a network communication program, and a network interface program, the network storage program provides a processing function for an upper layer network communication agreement, the network communication program performs network layer packet exchange, 10. The system for introducing an operating system to a remote data storage server from a computer having no fixed disk device according to claim 9, wherein the network interface program receives and transmits network packets. 10. The server for storing data at a remote end of an operating system from a computer without a fixed disk device according to claim 9, wherein the memory device of the computer without the fixed disk device is a main memory inside the computer without the fixed disk device. System to be introduced. 10. The memory device of the computer not having the fixed disk device is a memory device externally attached to the computer not having the fixed disk device, and the operating system is installed at a remote end from the computer having no fixed disk device according to claim 9. A system installed on a data storage server. The operating system installation program further includes a network communication driver and a network interface program. The network interface driver provides a network transmission / reception function to a computer that does not have a fixed disk device. The system for introducing an operating system to a data storage server at a remote end from a computer having no fixed disk device according to claim 9, characterized in that it provides a function for processing a communication agreement.