Granted Patent B2

US 12,423,114 · App. 18/567,652 · Granted Sep 23, 2025

Inventors: Jun Liu (Jiangsu, CN); Xufang Zhang (Jiangsu, CN)

Assignee: SUZHOU METABRAIN INTELLIGENT TECHNOLOGY CO., LTD.

G06F9/4411G06F8/61G06F9/4406

Abstract

Claims (43)

1. A method for controlling magnetic-disk loading, comprising:

obtaining magnetic-disk-configuration information of a server;

when it is determined according to the magnetic-disk-configuration information that the server comprises a plurality of magnetic-disk drives, configuring, in an installation configuration file of an operating system, a loading sequence of the magnetic-disk drives and a loading sequence of magnetic disks that are managed by each of the magnetic-disk drives; or when it is determined according to the magnetic-disk-configuration information that the server comprises a single magnetic-disk drive, configuring, in the installation configuration file of the operating system, a loading sequence of magnetic disks that are managed by the magnetic-disk drive; and

according to a configured installation configuration file of the operating system, installing the operating system into the server, to fix the configured loading sequence into the operating system;

wherein the step of configuring, in the installation configuration file of the operating system, the loading sequence of the magnetic-disk drives and the loading sequence of the magnetic disks that are managed by each of the magnetic-disk drives comprises:

configuring, in a kickstart configuration file, the loading sequence of the magnetic-disk drives and the loading sequence of the magnetic disks that are managed by each of the magnetic-disk drives; and

the step of configuring, in the installation configuration file of the operating system, the loading sequence of the magnetic disks that are managed by the magnetic-disk drive comprises:

configuring, in the kickstart configuration file, the loading sequence of the magnetic disks that are managed by the magnetic-disk drive; and

wherein before the step of configuring, in the kickstart configuration file, the loading sequence, the method further comprises:

when it is determined according to the magnetic-disk-configuration information that the server comprises the plurality of magnetic-disk drives, configuring, in a default configuration file, the loading sequence of the magnetic-disk drives and the loading sequence of the magnetic disks that are managed by each of the magnetic-disk drives; or

when it is determined according to the magnetic-disk-configuration information that the server comprises the single magnetic-disk drive, configuring, in the default configuration file, the loading sequence of the magnetic disks that are managed by the magnetic-disk drive.

2. The method for controlling the magnetic-disk loading according to claim 1 , wherein the step of configuring, in the default configuration file, the loading sequence of the magnetic-disk drives and the loading sequence of the magnetic disks that are managed by each of the magnetic-disk drives comprises:

controlling, in the default configuration file, by using a modprobe.blacklist parameter, the magnetic-disk drive that is loaded in a delaying mode, and controlling, by using scsi_mod.scan=sync, the loading sequence of the magnetic disks that are managed by a same magnetic-disk drive; and

the step of configuring, in the default configuration file, the loading sequence of the magnetic disks that are managed by the magnetic-disk drive comprises:

controlling, in the default configuration file, by using the scsi_mod.scan=sync, the loading sequence of the magnetic disks that are managed by the magnetic-disk drive.

3. The method for controlling the magnetic-disk loading according to claim 2 , wherein the step of configuring, in the kickstart configuration file, the loading sequence of the magnetic-disk drives and the loading sequence of the magnetic disks that are managed by each of the magnetic-disk drives comprises:

when the operating system uses an upstart starting-up manager, controlling, in the kickstart configuration file, by using a rdloaddriver parameter, the loading sequence of the magnetic-disk drives, and controlling, by using the scsi_mod.scan=sync, the loading sequence of the magnetic disks that are managed by the same magnetic-disk drive.

4. The method for controlling the magnetic-disk loading according to claim 2 , wherein after the step of, according to the configured installation configuration file of the operating system, installing the operating system into the server, the method further comprises:

when the operating system uses a systemd starting-up manager, adding into a % post part of the kickstart configuration file a removing instruction of removing the magnetic-disk drive that is loaded in the delaying mode that is disposed in the default configuration file.

5. The method for controlling the magnetic-disk loading according to claim 2 , wherein the step of configuring, in the kickstart configuration file, the loading sequence of the magnetic disks that are managed by the magnetic-disk drive comprises:

controlling, in the kickstart configuration file, by using the scsi_mod.scan=sync, the loading sequence of the magnetic disks that are managed by the magnetic-disk drive.

6. A device for controlling the magnetic-disk loading, comprising:

a memory configured for storing a computer-readable instruction; and

one or more processors configured for, when executing the computer-readable instruction, implementing the steps of the method for controlling the magnetic-disk loading according to claim 1 .

7. One or more non-transitory computer-readable storage mediums storing a computer-readable instruction, wherein the computer-readable instruction, when executed by the one or more processors, causes the one or more processors to implement the steps of the method according to claim 1 .

8. The method for controlling the magnetic-disk loading according to claim 1 , wherein the magnetic-disk-configuration information comprises: types of the magnetic disks and a quantity of the magnetic disks corresponding to each of the types of the magnetic disks.

9. The method for controlling the magnetic-disk loading according to claim 1 , wherein after the step of obtaining the magnetic-disk-configuration information of the server, the method further comprises:

according to the magnetic-disk-configuration information, determining a quantity of the magnetic-disk drives.

10. The method for controlling the magnetic-disk loading according to claim 1 , wherein the kickstart configuration file is an automatic response file in a process of installation of the operating system.

11. The device for controlling the magnetic-disk loading according to claim 6 , wherein the operation of configuring, in the default configuration file, the loading sequence of the magnetic-disk drives and the loading sequence of the magnetic disks that are managed by each of the magnetic-disk drives comprises:

controlling, in the default configuration file, by using a modprobe.blacklist parameter, the magnetic-disk drive that is loaded in a delaying mode, and controlling, by using scsi_mod.scan=sync, the loading sequence of the magnetic disks that are managed by a same magnetic-disk drive; and

the operation of configuring, in the default configuration file, the loading sequence of the magnetic disks that are managed by the magnetic-disk drive comprises:

controlling, in the default configuration file, by using the scsi_mod.scan=sync, the loading sequence of the magnetic disks that are managed by the magnetic-disk drive.

12. The device for controlling the magnetic-disk loading according to claim 11 , wherein the operation of configuring, in the kickstart configuration file, the loading sequence of the magnetic-disk drives and the loading sequence of the magnetic disks that are managed by each of the magnetic-disk drives comprises:

when the operating system uses an upstart starting-up manager, controlling, in the kickstart configuration file, by using a rdloaddriver parameter, the loading sequence of the magnetic-disk drives, and controlling, by using the scsi_mod.scan=sync, the loading sequence of the magnetic disks that are managed by the same magnetic-disk drive.

13. The device for controlling the magnetic-disk loading according to claim 11 , wherein after the operation of, according to the configured installation configuration file of the operating system, installing the operating system into the server, the method further comprises:

when the operating system uses a systemd starting-up manager, adding into a % post part of the kickstart configuration file a removing instruction of removing the magnetic-disk drive that is loaded in the delaying mode that is disposed in the default configuration file.

14. The device for controlling the magnetic-disk loading according to claim 11 , wherein the operation of configuring, in the kickstart configuration file, the loading sequence of the magnetic disks that are managed by the magnetic-disk drive comprises:

controlling, in the kickstart configuration file, by using the scsi_mod.scan=sync, the loading sequence of the magnetic disks that are managed by the magnetic-disk drive.

15. The one or more non-transitory computer-readable storage mediums according to claim 7 , wherein the operation of configuring, in the default configuration file, the loading sequence of the magnetic-disk drives and the loading sequence of the magnetic disks that are managed by each of the magnetic-disk drives comprises:

controlling, in the default configuration file, by using a modprobe.blacklist parameter, the magnetic-disk drive that is loaded in a delaying mode, and controlling, by using scsi_mod.scan=sync, the loading sequence of the magnetic disks that are managed by a same magnetic-disk drive; and

the operation of configuring, in the default configuration file, the loading sequence of the magnetic disks that are managed by the magnetic-disk drive comprises:

controlling, in the default configuration file, by using the scsi_mod.scan=sync, the loading sequence of the magnetic disks that are managed by the magnetic-disk drive.

Assignments (2)

Priority Claims (1)

Continuity (1)

References Cited (10)