Drive Management Handbook ​

1. Drive Loading Process ​

• Drive is an abstract drive object configured in the CSR of the drive backplane. Each slot corresponds to a Drive object.
• The Drive object reports common properties for various protocol drives, including but not limited to SAS, SATA, NVMe-MI, and SSD_FORMAT. Support for M.2 and other drives will be added in the future.

2. Non-Passthrough Drives ​

Non-passthrough drives refer to drives managed by RAID controller cards. In storage, they primarily appear as internal physical drive (PD) classes.

2.1 PD Classes ​

controller calls the get_ctrl_pd_list method to load and obtain PD classes.

A PD class uses the pd_identify_service to establish a connection with the Drive object in the corresponding slot.

The following figure shows the sequence for establishing a connection between the PD object and the Drive object.

3. Passthrough Drives ​

3.1 NVMe ​

NVMe objects are configured in the vpd repository. The drive backplane loads the corresponding CSR through Connector. The presence and type registers of the drive in the corresponding slot jointly determine presence of Connector.

A NVMe object establishes a connection with the Drive object through a slot, which simplifies the complex connection process required for PD objects.

The NVMe object sends updated properties to the Drive object after its management service completes acquisition and update. The Drive object then adds the properties to the tree.