Data processing method and device

Abstract

The invention provides a data processing method and device, and the method comprises the steps: responding to automatic deployment of an operating system, starting execution, and determining an installation state of the operating system on a specified target installation hard disk; under the condition that the operating system installation state is installation starting, creating a target directory under an operating system file structure of the target installation hard disk; and copying the out-of-band drive of the target installation hard disk to the target directory under the condition that the installation state of the operating system is that the target drive is installed.

Description

Technical Field

[0001] This application relates to, but is not limited to, the field of data processing technologies, and in particular, to a data processing method and apparatus. Background Art

[0002] Automatic deployment refers to a series of steps automatically executed during the operating system installation process. In related technologies, when the operating system performs automatic deployment, it is necessary to first load the out-of-band (OOB) driver so that the operating system can recognize the target installation hard disk, and then install the target driver on the target installation hard disk. However, the OOB driver will be loaded repeatedly, resulting in problems such as low success rate and poor flexibility. Summary of the Invention

[0003] In view of this, embodiments of this application at least provide a data processing method and apparatus.

[0004] The technical solutions of the embodiments of this application are implemented as follows:

[0005] Embodiments of this application provide a data processing method, including:

[0006] In response to the start of the automatic deployment of the operating system, determining the installation status of the operating system on the specified target installation hard disk;

[0007] When the installation status of the operating system is starting to install, creating a target directory in the operating system file structure of the target installation hard disk;

[0008] When the installation status of the operating system is installing the target driver, copying the out-of-band driver of the target installation hard disk to the target directory.

[0009] Embodiments of this application provide a data processing apparatus, including:

[0010] A determination unit, configured to determine the installation status of the operating system on the specified target installation hard disk in response to the start of the automatic deployment of the operating system;

[0011] A creation unit, configured to create a target directory in the operating system file structure of the target installation hard disk when the installation status of the operating system is starting to install;

[0012] A copying unit, configured to copy the out-of-band driver of the target installation hard disk to the target directory when the installation status of the operating system is installing the target driver.

[0013] It should be understood that the above general description and the following detailed description are only exemplary and explanatory, and do not limit the technical solutions of this application. Description of the Drawings

[0014] The accompanying drawings here are incorporated into the specification and form a part of this specification. These drawings illustrate embodiments consistent with the present application and, together with the specification, are used to explain the technical solutions of the present application.

[0015] Figure 1 Schematic diagram of the implementation process of a data processing method provided by an embodiment of the present application Figure 1 ;

[0016] Figure 2 Schematic diagram of the implementation process of a data processing method provided by an embodiment of the present application Figure 2 ;

[0017] Figure 3 Schematic diagram of the implementation process of a data processing method provided by an embodiment of the present application Figure 3 ;

[0018] Figure 4 Schematic diagram of the composition structure of a data processing device provided by an embodiment of the present application;

[0019] Figure 5 Schematic diagram of the hardware entity of an electronic device provided by an embodiment of the present application. Detailed implementation manners

[0020] In order to make the objectives, technical solutions, and advantages of the present application clearer, the technical solutions of the present application will be further elaborated in detail below with reference to the accompanying drawings and embodiments. The described embodiments should not be regarded as limitations to the present application. All other embodiments obtained by those of ordinary skill in the art without creative efforts fall within the scope of protection of the present application.

[0021] In the following description, reference is made to "some embodiments", which describe a subset of all possible embodiments. However, it can be understood that "some embodiments" can be the same subset or different subsets of all possible embodiments and can be combined with each other without conflict.

[0022] It should be noted that the terms "first / second / third" involved in the embodiments of the present application are only used to distinguish similar objects and do not represent a specific order for the objects. It can be understood that "first / second / third" can be interchanged in a specific order or sequence when allowed, so that the embodiments of the present application described here can be implemented in an order other than that illustrated or described here.

[0023] Those skilled in the art can understand that, unless otherwise defined, all terms (including technical terms and scientific terms) used herein have the same meaning as the general understanding of those of ordinary skill in the technical field to which the embodiments of this application belong. It should also be understood that terms defined in a general dictionary, such as those, should be understood to have a meaning consistent with the meaning in the context of the prior art, and will not be interpreted with an idealized or overly formal meaning unless specifically defined as here.

[0024] Automatic deployment refers to a series of steps automatically executed during the operating system installation process. In the related art, one method for implementing the automatic deployment of an operating system (e.g., Windows system) is to prepare in advance a file Autounattend.xml placed in the root directory of a USB flash drive. This file records various installation settings. After the Windows installation disk is started, the installer will automatically detect the Autounattend.xml file on the USB flash drive and install according to the settings therein. The installation settings in the Autounattend.xml file include specifying the target hard disk. For example, <installto> 、 <diskid> X< / diskid> 、< / installto> . Wherein, X is the hard disk number, which can be specified by numbers, for example, 0, 1, 2, etc.

[0025] When the operating system performs automatic deployment, the operating system does not necessarily support all storage devices. For example, the storage device on the server is Intel VMD Raid, and the target installation hard disk cannot be recognized after the operating system installation disk is started. Therefore, it is necessary to first load the OOB driver so that the operating system can recognize the target installation hard disk, and then install the target driver on the target installation hard disk. Generally, the OOB driver is placed in the $winpedriver$ directory of the installation disk. The installer will automatically detect the target driver in the $winpedriver$ directory and load the target driver, so as to install the target driver on the target installation hard disk. However, when installing the target driver, the OOB driver will be repeatedly loaded, and it will be determined that there is an error of repeatedly loading the driver, resulting in a pop-up error prompt and the installation being aborted. Therefore, the existing automatic deployment has problems such as low success rate and poor flexibility.

[0026] An embodiment of the present application provides a data processing method. By responding to the start of automatic deployment of the operating system, the installation status of the operating system on a specified target installation hard disk is determined. Thus, when the installation status of the operating system is starting to install, a target directory is created under the operating system file structure of the target installation hard disk. Then, when the installation status of the operating system is installing the target driver, the out-of-band driver of the target installation hard disk is copied to the target directory. In this way, since the out-of-band driver is copied to the already created target directory when installing the target driver, the possibility of repeatedly loading the out-of-band driver is reduced. Furthermore, it is possible to improve the success rate of automatic deployment of the operating system while reducing the possibility of popping up error prompts and installation abortion, thereby improving the flexibility of automatic deployment of the operating system.

[0027] The data processing method provided by the embodiment of the present application can be executed by an electronic device. The electronic device can be various types of terminals such as a laptop computer, a tablet computer, a desktop computer, a set-top box, a mobile device (e.g., a mobile phone, a portable music player, a personal digital assistant, a dedicated messaging device, a portable game device), etc., or can be implemented as a server. The server can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or can also be a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, Content Delivery Network (CDN), and big data and artificial intelligence platforms.

[0028] Figure 1 It is a schematic flow of a data processing method provided by an embodiment of the present application Figure 1 , as Figure 1 shown, the method includes steps S101 to S103, where:

[0029] Step S101, in response to the start of automatic deployment of the operating system, determine the installation status of the operating system on a specified target installation hard disk.

[0030] Here, the operating system is the core software of the electronic device, responsible for managing and coordinating the hardware resources of the electronic device, providing an interface for the user to interact with the electronic device, and supporting the operation of application programs. The operating system can include, but is not limited to, one of the following: Windows, Linux, MacOS, Android, etc.

[0031] In some embodiments, operating system automatic deployment refers to the process of automatically installing, configuring, and managing an operating system using automated tools and technologies. The automatic deployment of the operating system can be performed through automated scripts or automated deployment commands. Therefore, in response to starting the automated deployment script or executing the automated deployment command, it can be determined that the operating system automatic deployment begins to execute.

[0032] In some embodiments, the automatic deployment of the operating system can be carried out through a target file. Therefore, in response to loading the target file, the operating system automatic deployment begins to execute. Among them, the target file can be an Autounattend.xml file. The target file can be used to trigger the automatic deployment of the operating system.

[0033] The installation status of the operating system on the specified target installation hard disk can characterize the process of the operating system automatic deployment. In some embodiments, the installation status of the operating system on the specified target installation hard disk can include but is not limited to one of the following: not installed, starting installation, installing target drivers, decompressing the installation package to the target installation hard disk, installation completed, etc.

[0034] In some embodiments, in response to determining the target installation hard disk, the installation program of the operating system can be run and the target polling script can be called, and then based on the target polling script, the installation status of the operating system on the target installation hard disk can be determined.

[0035] In some embodiments, the Unified Extensible Firmware Interface (UEFI) program can be run to generate a target file based on the UEFI program, and then based on the UEFI program and the Baseboard Management Controller (BMC), at least one virtual hard disk can be determined, and the target file and the Out-of-Band (OOB) driver can be saved in at least one virtual hard disk. The target file is used to trigger the automatic deployment of the operating system.

[0036] Step S102, in the case where the operating system installation status is starting installation, create a target directory under the operating system file structure of the target installation hard disk.

[0037] Here, the target installation hard disk refers to the hard disk used to install the operating system. In some embodiments, the number of target installation hard disks can be one. There may be multiple hard disks on the machine, and the operating system can only be installed on one of them, and this hard disk is the target installation hard disk.

[0038] In some embodiments, the target installation hard disk has corresponding hard disk information. Among them, the hard disk information can include but is not limited to at least one of the following: product name (also known as Product Name), capacity (also known as Size), serial number (also known as Serial Number), hard disk number (also known as Disk ID), etc.

[0039] The operating system file structure refers to the way the operating system organizes files and directories on the hard disk. In some embodiments, the operating system file structure may include, but is not limited to, at least one of the following: root directory, system directory, user directory, program directory, library directory, temporary directory, log directory, etc.

[0040] The target directory refers to the directory where the driver is installed during the automatic deployment of the operating system. In some embodiments, the target directory is a temporary directory. The target directory can be used to install the target driver and store the OOB driver.

[0041] In some embodiments, the target directory can be created by executing a target command. The target command may include, but is not limited to, at least one of the following: Mkdir command, Touch command, New-Item command, etc. By executing the target command under the operating system file structure of the target installation hard disk, the target directory can be created.

[0042] In some embodiments, the target directory can be created by using a scripting language. Scripting languages such as Python and Bash can be used, combined with the application programming interface (API) of the operating system, to create directories.

[0043] In some embodiments, in response to the start of the automatic deployment of the operating system, an extraction command can be called to load the OOB driver into the installation environment based on the extraction command to determine the target installation hard disk.

[0044] In some embodiments, a preset detection program can be called to determine the hard disk information, and then based on the hard disk information, the hard disk number in the target file can be modified to determine the target installation hard disk.

[0045] In some embodiments, when the operating system installation status is not installed, the installation status of the operating system on the specified target installation hard disk can be continuously determined until the operating system installation status is starting to install, so as to create a target directory under the operating system file structure of the target installation hard disk.

[0046] Step S103, when the operating system installation status is to install the target driver, copy the out-of-band driver of the target installation hard disk to the target directory.

[0047] Here, the target driver is the driver that needs to be installed into the operating system. In some embodiments, the number of target drivers is at least one.

[0048] In some embodiments, the target driver is a driver that the operating system itself does not have, and the target driver can be obtained from a server or the cloud.

[0049] In some embodiments, the OOB driver is provided by the hardware device manufacturer and can be used to ensure that the device can be used immediately after the operating system is installed, without the user having to download or install the driver additionally.

[0050] In some embodiments, when the operating system installation state is to install the target driver, the OOB driver can be installed into the operating system. However, since the OOB driver needs to be loaded first so that the operating system can recognize the target installation hard disk, and then the target driver is installed on the target installation hard disk, the OOB driver will be loaded repeatedly. Through the data processing method of the present application, when the operating system installation state is to install the target driver, the out-of-band driver of the target installation hard disk is copied to the target directory, reducing the possibility of repeated loading of the OOB driver.

[0051] In some embodiments, based on the target polling script, the installation state of the operating system on the target installation hard disk can be determined, so that when the operating system installation state is to install the target driver, the OOB driver of the target installation hard disk can be copied to the target directory.

[0052] In some embodiments, the OOB driver of the target installation hard disk can be copied to the target directory by executing a copy command. For example, the copy command can include but is not limited to at least one of the following: Xcopy command, Robocopy command, etc. The OOB driver of the target installation hard disk can be copied to the target directory by executing the copy command.

[0053] In some embodiments, the OOB driver of the target installation hard disk can be copied to the target directory by using a cloning tool, etc. The cloning tool can be any suitable tool, such as DiskGenius, EaseUS Disk Copy, etc. The OOB driver of the target installation hard disk can be copied to the target directory by using the cloning tool.

[0054] In some embodiments, the target polling script has a copy function, and when the operating system installation state is to install the target driver, the OOB driver of the target installation hard disk can be copied to the target directory through the target polling script.

[0055] In the embodiments of the present application, by responding to the start of the automatic deployment of the operating system, the installation status of the operating system on the specified target installation hard disk is determined. Thus, when the installation status of the operating system is starting to install, a target directory is created under the operating system file structure of the target installation hard disk. Then, when the installation status of the operating system is installing the target driver, the out-of-band driver of the target installation hard disk is copied to the target directory. In this way, since the out-of-band driver is copied to the created target directory when installing the target driver, the possibility of repeatedly loading the out-of-band driver is reduced. Furthermore, the success rate of the automatic deployment of the operating system can be improved while reducing the possibility of pop-up error prompts and installation abortion, and the flexibility of the automatic deployment of the operating system is increased.

[0056] In some embodiments, the target directory is used to drive the installation of the target driver and store the out-of-band driver.

[0057] Here, the target directory can be a temporary directory. In some embodiments, the number of target directories is at least one.

[0058] It should be noted that the target directory is also created during the normal execution of the automatic deployment of the operating system. However, the target directory is only used to drive the installation of the target driver. The present application expands the use of the target directory. The target directory can be used to drive the installation of the target driver and store the OOB driver, thereby avoiding the situation of repeated loading of the OOB driver.

[0059] In some embodiments, when the installation status of the operating system is installing the target driver, the OOB driver of the target installation hard disk can be copied to the target directory so that the target directory stores the OOB driver.

[0060] In some embodiments, when the OOB driver is stored in the target directory, the OOB driver is not loaded into the current installation environment and is only installed under the operating system file structure of the target installation hard disk. This mechanism was discovered by analyzing the installation log of Windows2025. The installation log includes what operations were performed at each time point of Windows and the results of these operations.

[0061] In the embodiments of the present application, the target directory can be used to drive the installation of the target driver and store the out-of-band driver. While expanding the function of the target directory, the success rate of the automatic deployment of the operating system can be improved without affecting the automatic deployment of the operating system.

[0062] In some embodiments, when determining the installation status of the operating system on the specified target installation hard disk, the following steps can be performed. That is, "determining the installation status of the operating system on the specified target installation hard disk" in step S101 can include step S11 and step S12, where:

[0063] Step S11, in response to determining the target installation hard disk, run the installation program of the operating system and call the target polling script.

[0064] Here, the installation program of the operating system is a software tool for installing and configuring the operating system on computer hardware. The target polling script is a program code that obtains system status, data updates, or performs specific tasks by periodically checking.

[0065] In some embodiments, the installation program of the operating system can be used to detect the target file, and in the case of detecting the target file, perform automatic deployment of the operating system according to the installation settings in the target file.

[0066] In some embodiments, in the case where the target installation hard disk is not determined, the installation program of the operating system cannot perform automatic deployment of the operating system. Therefore, the target installation hard disk can be determined first, and then the installation program of the operating system can be run.

[0067] In some embodiments, the target polling script can be called by a timer. The timer can be used to repeatedly execute a certain function at a specified time interval, and the target polling script can be called by using the timer.

[0068] In some embodiments, the target polling script can be called by a recursive function, etc. The recursive function can include but is not limited to one of the following: FetchData function, setTimeout function, etc. The polling script can be called by using the recursive function.

[0069] In some embodiments, the target polling script can be called by the Start command. The Start command can be used to start a separate window to run the specified program or command.

[0070] In some embodiments, a bootable installation medium can be created first, and then the installation medium can be started to run the installation program of the operating system. Among them, the installation medium can include but is not limited to at least one of the following: USB drive, optical disc, etc.

[0071] In some embodiments, in response to the start of automatic deployment of the operating system, an extraction command can be called to load the OOB driver into the installation environment based on the extraction command to determine the target installation hard disk.

[0072] In some embodiments, a preset detection program can be called to determine the hard disk information, and then based on the hard disk information, modify the hard disk number in the target file to determine the target installation hard disk.

[0073] Step S12, based on the target polling script, determine the installation status of the operating system on the target installation hard disk.

[0074] Here, the installation status of the operating system on the specified target installation hard disk may include, but is not limited to, one of the following: not installed, installation started, installing target driver, decompressing the installation package to the target installation hard disk, installation completed, etc.

[0075] In some embodiments, the target polling script can be configured by setting a polling interval, and then based on the configured target polling script, the target polling script can be called based on the polling interval to determine the installation status of the operating system on the target installation hard disk.

[0076] In some embodiments, key metrics of the operating system installation status can be determined based on the target polling script, and then based on the key metrics of the operating system installation status, the installation status of the operating system on the target installation hard disk can be determined. Among them, the key metrics of the operating system installation status may include, but are not limited to, at least one of the following: partition table status, boot record status, system service status, etc.

[0077] In some embodiments, when the key metric of the operating system installation status includes the partition table status, the partition table of the target installation hard disk can be checked for existence based on the partition table status to determine the installation status of the operating system on the target installation hard disk. When the key metric of the operating system installation status includes the boot record status, whether the boot record has been correctly installed can be checked based on the boot record status to determine the installation status of the operating system on the target installation hard disk. When the key metric of the operating system installation status includes the system service status, whether the core services of the operating system have been started can be checked based on the system service status to determine the installation status of the operating system on the target installation hard disk.

[0078] In some embodiments, the directory structure corresponding to the target installation hard disk and the file content corresponding to the target installation hard disk can be determined based on the target polling script, and then based on the directory structure corresponding to the target installation hard disk and the file content corresponding to the target installation hard disk, the installation status of the operating system on the target installation hard disk can be determined.

[0079] In the embodiments of the present application, in response to determining the target installation hard disk, the installation program of the operating system can be run and the target polling script can be called, so that the installation status of the operating system on the target installation hard disk can be determined through the target polling script, and the installation status of the operating system on the target installation hard disk can be determined in real time, improving the accuracy of the installation status.

[0080] In some embodiments, when determining the installation status of the operating system on the specified target installation hard disk, the following steps can be performed, that is, step S12 can include step S121 and step S122, where:

[0081] Step S121: Based on the target polling script, determine the directory structure corresponding to the target installation hard disk and the file content corresponding to the target installation hard disk.

[0082] Here, the directory structure corresponding to the target installation hard disk refers to the organization method of files and folders on the target installation hard disk.

[0083] The file content corresponding to the target installation hard disk refers to the data actually stored in each file on the target installation hard disk. In some embodiments, the file content corresponding to the target installation hard disk can be of any suitable type, such as text, binary code, pictures, audio, video, etc.

[0084] In some embodiments, the file system traversal command can be run periodically based on the target polling script to determine the directory structure corresponding to the target installation hard disk. Among them, the file system traversal command can include, but is not limited to, at least one of the following: ls - R command, Tree command, etc.

[0085] In some embodiments, the content of the target installation hard disk can be read periodically based on the target polling script to determine the file content corresponding to the target installation hard disk. During implementation, the target polling script can determine the name, size, modification time, etc. of the files on the target installation hard disk.

[0086] In some embodiments, the target polling script can verify the integrity of the file content through hash verification. Hash verification is a string, such as MD5, SHA1, SHA256, etc. By calculating the hash value of the file, the integrity and consistency of the file can be verified to ensure that the file has not been tampered with or damaged during transmission or backup.

[0087] Step S122: Based on the directory structure corresponding to the target installation hard disk and the file content corresponding to the target installation hard disk, determine the installation status of the operating system on the target installation hard disk.

[0088] Here, based on the directory structure corresponding to the target installation hard disk and the file content corresponding to the target installation hard disk, it can be determined whether the target file or target driver is installed during the automatic deployment of the operating system, so as to determine the installation status of the operating system on the target installation hard disk.

[0089] In some embodiments, when the directory structure corresponding to the target installation hard disk and the file content corresponding to the target installation hard disk indicate that the target file does not exist on the target installation hard disk, the installation status of the operating system on the target installation hard disk can be not installed.

[0090] In some embodiments, when the directory structure corresponding to the target installation hard disk and the file content corresponding to the target installation hard disk indicate that the target driver exists on the target installation hard disk and the file content of the target driver is incomplete, the installation status of the operating system on the target installation hard disk may be to install the target driver.

[0091] In some embodiments, the first installation status may be determined based on the directory structure corresponding to the target installation hard disk, the second installation status may be determined based on the file content corresponding to the target installation hard disk, and then the installation status of the operating system on the target installation hard disk may be determined based on the first installation status and the second installation status. Among them, the first installation status may include, but is not limited to, one of the following: not installed, installation started, installing the target driver, decompressing the installation package to the target installation hard disk, installation completed, etc. The second installation status may include, but is not limited to, one of the following: not installed, installation started, installing the target driver, decompressing the installation package to the target installation hard disk, installation completed, etc.

[0092] In some embodiments, the first installation status and the second installation status may be the same or different. When the first installation status and the second installation status are the same, the first installation status or the second installation status is used as the installation status of the operating system on the target installation hard disk. When the first installation status and the second installation status are different, the first installation status and the second installation status are re-determined.

[0093] In the embodiments of the present application, through the target polling script, the directory structure corresponding to the target installation hard disk and the file content corresponding to the target installation hard disk are determined, so as to determine the installation status of the operating system on the target installation hard disk based on the directory structure corresponding to the target installation hard disk and the file content corresponding to the target installation hard disk. Using different information to determine the installation status of the operating system on the target installation hard disk improves the accuracy of the installation status.

[0094] In some embodiments, the data processing method provided by the embodiments of the present application may further include steps S104 to S106, where:

[0095] Step S104, run the Unified Extensible Firmware Interface program to generate a target file based on the Unified Extensible Firmware Interface program; wherein, the target file is used to trigger the automatic deployment of the operating system.

[0096] Here, the Unified Extensible Firmware Interface (UEFI) program is an executable file that conforms to the UEFI specification and is usually used to run in the UEFI firmware environment. UEFI is a computer firmware interface standard that can be used for the operating system to be automatically loaded from the pre-boot environment to the operating system.

[0097] The target file is a file used to trigger the automatic deployment of the operating system. In some embodiments, the target file can be in any suitable format, such as Extensible Markup Language (XML), HyperText Markup Language (HTML), Comma-Separated Values (CSV), etc. XML is a widely used markup language that can be used to store and transmit data. HTML is a standard markup language that can use tags to describe the structure and content of a file. CSV is a text format that can be used to store tabular data.

[0098] In some embodiments, various installation settings are recorded in the target file, and the automatic deployment of the operating system can be performed based on the installation settings. During implementation, the installation settings can include specifying the target installation hard disk.

[0099] In some embodiments, the UEFI program can be run using the Bcfg command or the UEFI firmware settings interface, or a tool (such as Efibootmgr) can be used to load and run the UEFI program. The running mode of the UEFI program in this application is not limited. Among them, the Bcfg command is a tool in the UEFI Shell environment used to manage and modify the startup and driver program options stored in non-volatile random access memory. It allows users to view, add, delete, and reorder startup items and driver program options.

[0100] In some embodiments, the UEFI program provides an EFI_FILE_PROTOCOL interface that can be used to operate files and directories. When generating the target file based on the UEFI program, the target file can be created first based on the Open method, and then data can be written to the target file using the Write method to generate the target file.

[0101] Step S105: Determine at least one virtual hard disk based on the Unified Extensible Firmware Interface program and the Baseboard Management Controller.

[0102] Here, the Baseboard Management Controller (BMC) is a controller used to execute monitoring and management functions.

[0103] In some embodiments, at least one virtual hard disk can be determined in the BMC based on the UEFI program and the BMC. In some embodiments, the at least one virtual hard disk can include at least one of the following: the first virtual hard disk, the second virtual hard disk, etc.

[0104] In some embodiments, after generating a target file based on the UEFI program, a partitioning tool can be used to create at least one partition in the BMC, and then the at least one partition can be used as at least one virtual hard disk. Among them, the partitioning tool can be any suitable tool, for example, the Fdisk tool, the Parted tool, etc.

[0105] In some embodiments, the Intelligent Platform Management Interface (IPMI) and / or Redfish can be sent to the BMC to notify the BMC to map the virtual USB flash drive to the host, so that at least one virtual hard disk can be determined in the virtual USB flash drive mapped by the host. Among them, the host is a device that needs to perform the automatic deployment of the operating system.

[0106] Step S106, save the target file and the out-of-band driver in at least one virtual hard disk.

[0107] Here, the target file and the OOB driver can be saved in the same virtual hard disk, or the target file and the OOB driver can be saved in different virtual hard disks respectively.

[0108] In some embodiments, the target file and the OOB driver can be copied to the at least one created virtual hard disk, so that the target file and the OOB driver can be saved in the at least one virtual hard disk.

[0109] In some embodiments, the at least one virtual hard disk includes a first virtual hard disk and a second virtual hard disk. The target file can be saved in the first virtual hard disk, and the OOB driver can be saved in the second virtual hard disk. Among them, the second virtual hard disk is different from the first virtual hard disk.

[0110] In the embodiments of the present application, a target file for triggering the automatic deployment of the operating system is generated through a running Unified Extensible Firmware Interface program, so that the automatic deployment of the operating system can be normally executed without manual input of installation parameters or intervention in the installation process, reducing the installation cost. At the same time, then the target file and the out-of-band driver are saved in at least one virtual hard disk, and the target file and the out-of-band driver can be isolated from the physical hard disk where the operating system is located, reducing the possibility of loss of the target file and the out-of-band driver.

[0111] In some embodiments, the at least one virtual hard disk includes a first virtual hard disk and a second virtual hard disk; when saving the target file and the out-of-band driver in the at least one virtual hard disk, the following steps can be executed, that is, step S106 can include step S161 and step S162, where:

[0112] Step S161, save the target file in the first virtual hard disk.

[0113] Here, the first virtual hard disk is a virtual hard disk for storing the target file. In some embodiments, the first virtual hard disk may be a virtual USB.

[0114] In some embodiments, the first virtual hard disk is a virtual hard disk created when the UEFI program generates the target file, and the first virtual hard disk is a readable and writable virtual hard disk.

[0115] In some embodiments, the target file can be copied to the created first virtual hard disk, so that the target file can be stored in the first virtual hard disk.

[0116] Step S162, save the out-of-band driver in the second virtual hard disk; wherein, the second virtual hard disk is different from the first virtual hard disk.

[0117] Here, the second virtual hard disk is a virtual hard disk for storing the OOB driver. In some embodiments, the second virtual hard disk may be an OOB driver virtual USB.

[0118] In some embodiments, the second virtual hard disk is different from the first virtual hard disk.

[0119] In some embodiments, the second virtual hard disk is a virtual hard disk inherent in the BMC, and the second virtual hard disk is a readable virtual hard disk.

[0120] In some embodiments, the OOB driver can be copied to the second virtual hard disk, so that the OOB driver can be stored in the second virtual hard disk.

[0121] In the embodiments of the present application, different second virtual hard disks and first virtual hard disks are created to store the target file in the first virtual hard disk and store the out-of-band driver in the second virtual hard disk, so that the target file and the out-of-band driver can be stored independently, improving the security and isolation of file storage.

[0122] In some embodiments, the data processing method provided by the embodiments of the present application may further include step S107 and step S108, wherein:

[0123] Step S107, in response to calling the boot loader, based on the boot loader, start the installation disk; wherein, the installation disk is used to store the target driver.

[0124] Here, the boot loader (also known as the Boot Loader) is a file that runs during the automatic deployment of the operating system and can be used to load the operating system kernel into memory and start the operating system.

[0125] In some embodiments, the boot loader can be a file on the installation disk and can be used to boot the installation disk. During implementation, the boot loader is the first file to run during the boot process of the installation disk. The boot loader can be stored at any appropriate location on the installation disk. For example, / efi / boot / bootx64.efi.

[0126] In some embodiments, the installation disk is different from the target installation hard disk. At least one installation package can be stored on the installation disk. The at least one installation package includes the installation package corresponding to the target driver.

[0127] In some embodiments, the installation disk can be a DVD disc or a USB flash drive. The present application does not limit the specific form of the installation disk.

[0128] Step S108, in response to booting the installation disk, enter the installation environment and load the target file.

[0129] Here, the installation environment refers to the environment for installing the target driver. In some embodiments, the installation environment can be a WinPE environment. WinPE is a lightweight pre-installation environment based on the Windows kernel launched by Microsoft and can be used for tasks such as system deployment, troubleshooting, data recovery, and maintenance.

[0130] In some embodiments, in response to booting the installation disk, enter the installation environment. Then, the installation program of the operating system can automatically detect the target file from the virtual hard disk and load the target file.

[0131] In the embodiments of the present application, in response to calling the boot loader, the installation disk is booted based on the boot loader, enter the installation environment and load the target file, which improves the reliability and stability of the automatic deployment of the operating system.

[0132] In some embodiments, when the automatic deployment of the operating system starts to execute, the following steps can be performed. That is, "in response to the start of the automatic deployment of the operating system" in step S101 can include step S1011. The data processing method provided by the embodiments of the present application can further include step S109 and step S110, where:

[0133] Step S1011, in response to loading the target file, the automatic deployment of the operating system starts to execute.

[0134] Here, the target file can be used to trigger the automatic deployment of the operating system. Therefore, in response to loading the target file, the automatic deployment of the operating system starts to execute.

[0135] In some embodiments, the installation settings of the target file can include commands to be executed before installation. After loading the target file, the start of the automatic deployment of the operating system can be triggered by the commands to be executed before installation.

[0136] In some embodiments, the target file may have an identifier. During the process of loading the target file, in response to loading the identifier, the start execution of the automatic deployment by the operating system can be triggered.

[0137] Step S109, in response to the start execution of the automatic deployment by the operating system, call the decompression command.

[0138] Here, the decompression command is a command-line tool in the installation environment and can be used to load the driver in the installation environment. In implementation, the decompression command can be the Drvload command.

[0139] In some embodiments, the commands executed before installation may include calling the decompression command. The decompression command can be called through the commands executed before installation in response to the start execution of the automatic deployment by the operating system.

[0140] In some embodiments, the commands executed before installation may first decompress the OOB driver in compressed format in the virtual hard disk, then detect the current Windows version information and call the Drvload command, so as to load the OOB driver matching the Windows version.

[0141] Step S110, based on the decompression command, load the out-of-band driver into the installation environment to determine the target installation hard disk.

[0142] Here, the OOB driver can be loaded into the installation environment based on the decompression command, thereby triggering the determination of the target installation hard disk.

[0143] In some embodiments, based on the storage path of the OOB driver, the OOB driver in compressed format can be decompressed in the second virtual hard disk of the BMC, then the OOB driver matching the Windows version can be loaded and the OOB driver can be loaded into the installation environment, thereby triggering the determination of the target installation hard disk.

[0144] In some embodiments, a preset detection program can be called to determine the hard disk information, and then based on the hard disk information, modify the hard disk number in the target file to determine the target installation hard disk.

[0145] In the embodiments of the present application, by responding to the loading of the target file, the start execution of the automatic deployment by the operating system is triggered, realizing the triggering of the automatic deployment of the operating system without manual intervention, saving the deployment time. At the same time, in response to the start execution of the automatic deployment by the operating system, the decompression command is called to load the out-of-band driver into the installation environment to determine the target installation hard disk, and the target installation hard disk can be flexibly determined according to the actual installation situation.

[0146] In some embodiments, the method provided by the embodiments of the present application may further include step S110 and step S120, where:

[0147] Step S110, call a preset detection program to determine the hard disk information.

[0148] Here, the preset detection program refers to a program used to detect hard disk information. In some embodiments, the preset detection program may include, but is not limited to, at least one of the following: CrystalDiskInfo, HD Tune Pro, MyDiskTest, etc. Among them, CrystalDiskInfo can support detecting the information of mechanical hard disks and solid-state hard disks, detecting, analyzing, and reading hard disk information. HD Tune Pro is a hard disk tool software that can detect hard disk information. MyDiskTest is a tool used to detect mobile storage devices such as USB flash drives and can detect hard disk information.

[0149] In some embodiments, the hard disk information may include, but is not limited to, at least one of the following: product name, capacity, serial number, hard disk number, etc. Among them, the hard disk number can be any appropriate number, for example, 0, 1, 2, etc.

[0150] In some embodiments, in the Windows system, the hard disk number in the hard disk information is not related to other information. That is, the hard disk number under the Windows system is random. For example, there are two hard disks in the Windows system, namely hard disk A and hard disk B. After the Windows system is restarted, the hard disk number of hard disk A may be 0, and the hard disk number of hard disk B may be 1. After the Windows system is restarted again, the hard disk number of hard disk A may be 1, and the hard disk number of hard disk B may be 0.

[0151] Step S120, based on the hard disk information, modify the hard disk number in the target file to determine the target installation hard disk.

[0152] Here, the role of determining the target installation hard disk is to make the installation program of the operating system clear that the operating system is to be installed on the hard disk with the specified number to achieve automatic deployment of the operating system.

[0153] In some embodiments, the relevant configuration part related to the hard disk in the target file can be determined through a preset detection program, and then based on the hard disk information, the hard disk number in the target file is modified to determine the target installation hard disk.

[0154] In some embodiments, before modifying the hard disk number in the target file, the hard disk number in the target file can be a default value or a random number. After modifying the hard disk number in the target file, the target installation hard disk can be specified.

[0155] In the embodiment of the present application, the hard disk information is determined by calling a preset detection program, and the hard disk number in the target file is modified based on the hard disk information to determine the target installation hard disk, so that the target installation hard disk can be determined in real time, improving the accuracy of the target installation hard disk.

[0156] The following describes the application of the data processing method provided by the embodiments of the present application in an actual scenario.

[0157] Automatic deployment refers to a series of steps automatically executed during the installation process of an operating system. In the related art, one method to implement the automatic deployment of an operating system (for example, Windows system) is to prepare in advance a file Autounattend.xml placed in the root directory of a USB flash drive. Various installation settings are recorded in this file. After the Windows installation disk is started, the installation program will automatically detect the Autounattend.xml file on the USB flash drive and install according to the settings therein. The installation settings in the Autounattend.xml file include specifying the target hard disk. For example, <installto> 、 <diskid> X< / diskid> 、< / installto> . Among them, X is the hard disk number, which can be specified by numbers, for example, 0, 1, 2, etc.

[0158] When the operating system performs automatic deployment, the operating system may not support all storage devices. For example, the storage device on the server is Intel VMD Raid, and the target installation hard disk cannot be recognized after the operating system installation disk is started. Therefore, it is necessary to first load the OOB driver so that the operating system can recognize the target installation hard disk, and then install the target driver on the target installation hard disk. The general method is to place the OOB driver in the $winpedriver$ directory of the installation disk. The installation program will automatically detect the target driver in the $winpedriver$ directory and load the target driver, so as to install the target driver on the target installation hard disk. However, when installing the target driver, the OOB driver will be loaded repeatedly, and it will be determined that there is an error of repeated driver loading, resulting in a pop-up error prompt and the installation being aborted. Therefore, the existing automatic deployment has problems such as low success rate and poor flexibility.

[0159] An embodiment of the present application provides a data processing method. By responding to the start of automatic deployment of the operating system, the installation status of the operating system on a specified target installation hard disk is determined. Thus, when the installation status of the operating system is starting to install, a target directory is created under the operating system file structure of the target installation hard disk. Then, when the installation status of the operating system is to install the target driver, the out-of-band driver of the target installation hard disk is copied to the target directory. In this way, since the out-of-band driver is copied to the created target directory when installing the target driver, the possibility of repeatedly loading the out-of-band driver is reduced. Furthermore, while improving the success rate of automatic deployment of the operating system, the possibility of pop-up error prompts and installation interruption can be reduced, and the flexibility of automatic deployment of the operating system is improved.

[0160] Figure 2 It is a schematic implementation process of a data processing method provided by an embodiment of the present application Figure 2 , such as Figure 2 shown. The method includes steps S201 to S210, where:

[0161] Step S201, run the Unified Extensible Firmware Interface program to generate a target file based on the Unified Extensible Firmware Interface program;

[0162] Step S202, determine the first virtual hard disk and the second virtual hard disk based on the Unified Extensible Firmware Interface program and the Baseboard Management Controller;

[0163] Step S203, save the target file in the first virtual hard disk and save the out-of-band driver in the second virtual hard disk;

[0164] Step S204, in response to calling the boot loader, start the installation disk based on the boot loader. In response to starting the installation disk, enter the installation environment and load the target file;

[0165] Step S205, in response to loading the target file, the automatic deployment of the operating system starts to execute;

[0166] Step S206, in response to the start of automatic deployment of the operating system, call the decompression command, and load the out-of-band driver into the installation environment based on the decompression command to determine the target installation hard disk;

[0167] Step S207, in response to determining the target installation hard disk, run the installation program of the operating system and call the target polling script;

[0168] Step S208, based on the target polling script, determine the installation status of the operating system on the target installation hard disk;

[0169] Step S209, when the installation status of the operating system is starting to install, create a target directory under the operating system file structure of the target installation hard disk;

[0170] Step S210, when the operating system installation status is to install the target driver, copy the out-of-band driver of the target installation hard disk to the target directory.

[0171] It should be noted that in the method provided in this application, the magnitudes of the serial numbers of the above steps / processes do not mean the sequence of execution. The execution sequence of each step / process should be determined by its function and internal logic, and should not constitute any limitation to the implementation process of the embodiments of this application. For example, step S201 and step S202 can be executed simultaneously or in a sequential order.

[0172] In the implementation of this application, during the process of detecting the installation program, query the installation status of the operating system on the target installation hard disk through the target polling script. When the operating system installation status is to start installation, create a target directory under the operating system file structure of the target installation hard disk. When the operating system installation status is to install the target driver, copy the out-of-band driver of the target installation hard disk to the target directory, reducing the possibility of repeatedly loading the OOB driver.

[0173] Figure 3 Schematic diagram of the implementation process of a data processing method provided by an embodiment of this application Figure 3 , such as Figure 3 shown. The method includes steps S31 to S39, where:

[0174] Step S31, run UEFI Application (corresponding to the aforementioned Unified Extensible Firmware Interface program) to generate Autounattend.xml (corresponding to the aforementioned target file), save Autounattend.xml in virtual USB (corresponding to the aforementioned first virtual hard disk), and send IPMI and / or Redfish to BMC, and save the OOB driver (corresponding to the aforementioned out-of-band driver) in the OOB driver virtual USB (corresponding to the aforementioned second virtual hard disk);

[0175] Step S32, call the Boot loader in the Window image to start the installation disk to enter the WindPE environment (corresponding to the aforementioned installation environment), and the Windows installation program (corresponding to the installation program of the aforementioned operating system) automatically detects and loads Autounattend.xml on the virtual USB, triggering the commands defined in Autounattend.xml that are executed before installation to run automatically;

[0176] Step S33: In response to the command executed before installation, call the Drvload command (corresponding to the aforementioned decompression command), load the OOB driver into the WinPE environment, detect the hard disk information through a preset detection program, update the target installation hard disk number in Autounattend.xml, and call the background timed polling script (corresponding to the aforementioned target polling script);

[0177] Here, after executing step S33, execute step S34 and step S35

[0178] Step S34: The Windows installation program continues to run;

[0179] Step S35: Based on the background timed polling script, detect the Windows installation status in real time (corresponding to the installation status of the aforementioned operating system on the target installation hard disk);

[0180] Step S36: When the Windows installation status is to start installation, decompress the installation package to the target installation hard disk, and create a $WINDOWS.~BT\drivers\unattend directory (corresponding to the aforementioned target directory) under the operating system file structure of the target installation hard disk;

[0181] Step S37: Based on the background timed polling script, detect that the Windows installation status is to install the target driver;

[0182] Step S38: Based on the background timed polling script, copy the OOB driver to the $WINDOWS.~BT\drivers\unattend directory;

[0183] Step S39: The installation is completed.

[0184] In the embodiment of the present application, the function of loading the OOB driver and specifying the target installation hard disk during the automatic installation of Windows 2025 is realized. After the Windows installation program finishes decompressing the installation package, it will automatically search for and install the OOB driver in the $WINDOWS.~BT\drivers\unattend directory. It has been experimentally observed that the OOB driver in this directory will not be loaded into the current WinPE environment, but only installed into the system on the hard disk, avoiding the repeated loading of the OOB driver.

[0185] Based on the above embodiments, the embodiment of the present application further provides a data processing device, Figure 4 The composition structure diagram of a data processing device provided by the embodiment of the present application is as shown in Figure 4As shown, the data processing device 400 includes a determination unit 401, a creation unit 402, and a replication unit 403, where:

[0186] The determination unit 401 is configured to determine the installation status of the operating system on the specified target installation hard disk in response to the start of automatic deployment of the operating system.

[0187] The creation unit 402 is configured to create a target directory under the operating system file structure of the target installation hard disk when the installation status of the operating system is starting to install.

[0188] The replication unit 403 is configured to copy the out-of-band driver of the target installation hard disk to the target directory when the installation status of the operating system is to install the target driver.

[0189] In some embodiments, the target directory is used to drive the installation of the target driver and store the out-of-band driver.

[0190] In some embodiments, the determination unit 401 is further configured to, in response to determining the target installation hard disk, run the installation program of the operating system and call the target polling script; based on the target polling script, determine the installation status of the operating system on the target installation hard disk.

[0191] In some embodiments, the determination unit 401 is further configured to, based on the target polling script, determine the directory structure corresponding to the target installation hard disk and the file content corresponding to the target installation hard disk; based on the directory structure corresponding to the target installation hard disk and the file content corresponding to the target installation hard disk, determine the installation status of the operating system on the target installation hard disk.

[0192] In some embodiments, the data processing device 400 further includes a storage unit configured to run the Unified Extensible Firmware Interface program to generate a target file based on the Unified Extensible Firmware Interface program; wherein, the target file is used to trigger the automatic deployment of the operating system; based on the Unified Extensible Firmware Interface program and the Baseboard Management Controller, determine at least one virtual hard disk; save the target file and the out-of-band driver in at least one virtual hard disk.

[0193] In some embodiments, the at least one virtual hard disk includes a first virtual hard disk and a second virtual hard disk; the storage unit is further configured to save the target file in the first virtual hard disk; save the out-of-band driver in the second virtual hard disk; wherein, the second virtual hard disk is different from the first virtual hard disk.

[0194] In some embodiments, the data processing device 400 further includes a loading unit configured to, in response to calling the startup load, start the installation disk based on the startup load; wherein, the installation disk is used to store the target driver; in response to starting the installation disk, enter the installation environment and load the target file.

[0195] In some embodiments, the determining unit 401 is further configured to, in response to loading a target file, automatically start the operating system deployment for execution; in response to the start of the automatic operating system deployment for execution, call an extraction command; and based on the extraction command, load an out-of-band driver into the installation environment to determine a target installation hard disk.

[0196] In some embodiments, the determining unit 401 is further configured to call a preset detection program to determine hard disk information; and based on the hard disk information, modify the hard disk number in the target file to determine a target installation hard disk.

[0197] The description of the data processing apparatus embodiments above is similar to the description of the method embodiments above, and has beneficial effects similar to those of the method embodiments. For technical details not disclosed in the data processing apparatus embodiments of the present application, please refer to the description of the method embodiments of the present application for understanding.

[0198] It should be noted here that: the descriptions of the above embodiments tend to emphasize the differences between the embodiments, and their similarities can be referred to each other. The descriptions of the above device, storage medium, computer program, and computer program product embodiments are similar to the descriptions of the method embodiments above, and have beneficial effects similar to those of the method embodiments. For technical details not disclosed in the device, storage medium, computer program, and computer program product embodiments of the present application, please refer to the description of the method embodiments of the present application for understanding.

[0199] It should be noted that in the embodiments of the present application, if the above method is implemented in the form of a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the embodiments of the present application, in essence, or the part that contributes to the related technology, can be embodied in the form of a software product. The software product is stored in a storage medium and includes several instructions for causing an electronic device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the methods described in the embodiments of the present application. The aforementioned storage medium includes: various media such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a magnetic disk, or an optical disc that can store program codes. In this way, the embodiments of the present application are not limited to any specific combination of hardware and software.

[0200] The embodiments of the present application provide an electronic device, including a memory and a processor. The memory stores a computer program that can run on the processor, and when the processor executes the computer program, the above method is implemented.

[0201] An embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the above method is implemented. The computer-readable storage medium may be transient or non-transient.

[0202] An embodiment of the present application provides a computer program product. The computer program product includes a non-transient computer-readable storage medium storing a computer program. When the computer program is read and executed by a computer, some or all of the steps in the above method are implemented. The computer program product may be specifically implemented in a manner of hardware, software, or a combination thereof. In an optional embodiment, the computer program product is specifically embodied as a computer storage medium. In another optional embodiment, the computer program product is specifically embodied as a software product, such as a Software Development Kit (SDK), etc.

[0203] It should be noted that Figure 5 FIG. is a schematic diagram of the hardware entity of an electronic device provided by an embodiment of the present application. As shown in the figure, the hardware entity of the electronic device 500 includes: a processor 501, a communication interface 502, and a memory 503, where:

[0204] The processor 501 generally controls the overall operation of the electronic device 500.

[0205] The communication interface 502 can enable the electronic device to communicate with other terminals or servers through a network.

[0206] The memory 503 is configured to store instructions and applications executable by the processor 501, and can also cache data to be processed or already processed by the processor 501 and each module in the electronic device 500 (for example, image data, audio data, voice communication data, and video communication data), and can be implemented by flash memory (FLASH) or random access memory (Random Access Memory, RAM). Data transmission can be performed between the processor 501, the communication interface 502, and the memory 503 through a bus 504.

[0207] It should be pointed out here that: The descriptions of the above storage medium and device embodiments are similar to those of the above method embodiments and have similar beneficial effects to the method embodiments. For the technical details not disclosed in the storage medium and device embodiments of the present application, please refer to the descriptions of the method embodiments of the present application for understanding.

[0208] It should be understood that the "one embodiment" or "an embodiment" mentioned throughout the specification means that the specific features, structures or characteristics related to the embodiment are included in at least one embodiment of the present application. Therefore, the appearances of "in one embodiment" or "in an embodiment" throughout the specification do not necessarily refer to the same embodiment. In addition, these specific features, structures or characteristics may be combined in one or more embodiments in any suitable manner. It should be understood that in various embodiments of the present application, the magnitudes of the sequence numbers of the above steps / processes do not mean the order of execution. The order of execution of each step / process should be determined by its function and internal logic, and should not constitute any limitation to the implementation process of the embodiments of the present application. The sequence numbers of the embodiments of the present application are only for description and do not represent the advantages or disadvantages of the embodiments.

[0209] It should be noted that in this article, the term "comprising", "including" or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements, but also includes other elements not expressly listed, or further includes elements inherent to such process, method, article or device. Without further limitation, an element defined by the phrase "comprising a..." does not exclude the existence of additional identical elements in the process, method, article or device including the element.

[0210] In several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are only illustrative. For example, the division of the units is only a logical function division, and there may be other division methods in actual implementation. For example, multiple units or components can be combined, or can be integrated into another system, or some features can be ignored, or not executed. In addition, the coupling, direct coupling or communication connection between the components shown or discussed with each other can be through some interfaces, and the indirect coupling or communication connection of the devices or units can be electrical, mechanical or other forms.

[0211] The units described above as separate components may or may not be physically separated, and the components shown as units may or may not be physical units; they may be located in one place or distributed to multiple network units; some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0212] In addition, each functional unit in the embodiments of the present application may be all integrated in one processing unit, or each unit may be separately used as a unit, or two or more units may be integrated in one unit; the above integrated unit may be implemented in the form of hardware, or in the form of a combination of hardware and software functional units.

[0213] Those of ordinary skill in the art can understand that all or part of the steps of implementing the above method embodiments can be completed by hardware related to program instructions. The foregoing program can be stored in a computer-readable storage medium. When the program is executed, it performs the steps including those of the above method embodiments; and the foregoing storage medium includes: various media such as removable storage devices, read-only memories, magnetic disks, or optical discs that can store program codes.

[0214] Alternatively, if the above integrated units of the present application are implemented in the form of software function modules and sold or used as independent products, they can also be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the present application, in essence or the part that contributes to the related technology, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the methods described in the various embodiments of the present application. And the foregoing storage medium includes: various media such as removable storage devices, ROMs, magnetic disks, or optical discs that can store program codes.

[0215] As described above, only the implementation manners of the present application are provided, but the protection scope of the present application is not limited thereto. Any person skilled in the art within the technical scope disclosed by the present application can easily think of changes or substitutions, which should all be covered within the protection scope of the present application.

Claims

1. A data processing method, the method comprising: Determining the installation status of the operating system on a specified target installation hard disk in response to the start of automatic deployment of the operating system; Creating a target directory under the operating system file structure of the target installation hard disk when the installation status of the operating system is starting to install; Copying the out-of-band driver of the target installation hard disk to the target directory when the installation status of the operating system is installing the target driver.

2. The method according to claim 1, wherein the target directory is used to drive the installation of the target driver and store the out-of-band driver.

3. The method according to claim 1, wherein determining the installation status of the operating system on a specified target installation hard disk comprises: Running the installation program of the operating system and invoking a target polling script in response to determining the target installation hard disk; Determining the installation status of the operating system on the target installation hard disk based on the target polling script.

4. The method according to claim 3, wherein determining the installation status of the operating system on the target installation hard disk based on the target polling script comprises: Determining the directory structure corresponding to the target installation hard disk and the file content corresponding to the target installation hard disk based on the target polling script; Determining the installation status of the operating system on the target installation hard disk based on the directory structure corresponding to the target installation hard disk and the file content corresponding to the target installation hard disk.

5. The method according to claim 1, the method further comprising: Running a Unified Extensible Firmware Interface program to generate a target file based on the Unified Extensible Firmware Interface program; wherein the target file is used to trigger the automatic deployment of the operating system; Determining at least one virtual hard disk based on the Unified Extensible Firmware Interface program and the Baseboard Management Controller; Saving the target file and the out-of-band driver in the at least one virtual hard disk.

6. The method according to claim 5, wherein the at least one virtual hard disk comprises a first virtual hard disk and a second virtual hard disk; Saving the target file and the out-of-band driver in the at least one virtual hard disk comprises: Saving the target file in the first virtual hard disk; Saving the out-of-band driver in the second virtual hard disk; wherein the second virtual hard disk is different from the first virtual hard disk.

7. The method according to claim 5, the method further comprising: Starting the installation disk based on the boot loader in response to invoking the boot loader; wherein the installation disk is used to store the target driver; Entering the installation environment and loading the target file in response to starting the installation disk.

8. The method according to claim 7, wherein responding to the start of automatic deployment of the operating system comprises: The automatic deployment of the operating system starts to execute in response to loading the target file; The method further comprises: Invoking an extraction command in response to the start of execution of the automatic deployment of the operating system; Loading the out-of-band driver into the installation environment based on the extraction command to determine the target installation hard disk.

9. The method according to any one of claims 1 to 8, the method further comprising: Invoking a preset detection program to determine hard disk information; Based on the hard disk information, modifying the hard disk number in the target file to determine the target installation hard disk.

10. A data processing device, the device comprising: A determination unit, configured to determine the installation status of the operating system on a specified target installation hard disk in response to the start of automatic deployment of the operating system; A creation unit, configured to create a target directory under the operating system file structure of the target installation hard disk when the installation status of the operating system is starting to install; A copying unit, configured to copy the out-of-band driver of the target installation hard disk to the target directory when the installation status of the operating system is installing the target driver.

Images