| /openbmc/libbej/test/json/ |
| H A D | storage_large.json | 39 "Drives": [ array
41 "@odata.id": "/redfish/v1/Systems/1/Storage/1/Drives/1"
44 "@odata.id": "/redfish/v1/Systems/1/Storage/1/Drives/2"
47 "@odata.id": "/redfish/v1/Systems/1/Storage/1/Drives/3"
50 "@odata.id": "/redfish/v1/Systems/1/Storage/1/Drives/4"
53 "@odata.id": "/redfish/v1/Systems/1/Storage/1/Drives/5"
56 "@odata.id": "/redfish/v1/Systems/1/Storage/1/Drives/6"
59 "@odata.id": "/redfish/v1/Systems/1/Storage/1/Drives/7"
62 "@odata.id": "/redfish/v1/Systems/1/Storage/1/Drives/8"
65 "@odata.id": "/redfish/v1/Systems/1/Storage/1/Drives/9"
[all …]
|
| H A D | storage.json | 40 "Drives": [ array
42 "@odata.id": "/redfish/v1/Chassis/StorageEnclosure1/Drives/Disk.Bay.1"
45 "@odata.id": "/redfish/v1/Chassis/StorageEnclosure1/Drives/Disk.Bay.2"
48 "@odata.id": "/redfish/v1/Chassis/StorageEnclosure1/Drives/Disk.Bay.3"
51 "@odata.id": "/redfish/v1/Chassis/StorageEnclosure1/Drives/Disk.Bay.4"
54 "@odata.id": "/redfish/v1/Chassis/StorageEnclosure1/Drives/Disk.Bay.5"
57 "@odata.id": "/redfish/v1/Chassis/StorageEnclosure1/Drives/Disk.Bay.6"
|
| H A D | chassis.json | 27 "Drives": [ array
29 "@odata.id": "/redfish/v1/Chassis/SomeChassis/Drives/SATA_0"
32 "Drives@odata.count": 1
|
| H A D | drive_oem.json | 2 "@odata.id": "/redfish/v1/drives/1",
16 "target": "/redfish/v1/drives/1/Actions/Drive.SecureErase",
20 "target": "/redfish/v1/drives/1/Actions/Drive.Reset",
|
| /openbmc/docs/designs/ |
| H A D | nvmemi-over-smbus.md | 13 monitor NVMe drives so appropriate action can be taken.
18 `NVM Express Basic Management Command` that can read the NVMe drives information
22 For our purpose is retrieve NVMe drives information, therefore, using NVM
24 communicate with NVMe drives. According to different platforms, temperature
36 - Provide a daemon to monitor NVMe drives. Parameters to be monitored are Status
40 - Capability of communication over hardware channel I2C to NVMe drives.
119 | StatusFlags | string | Indicates the status of the drives |
122 | BackupdrivesFault | bool | If warning type about backup drives happened |
161 drive to get data. Data get from NVMe drives are "Status Flags", "SMART
166 This service will run automatically and look up NVMe drives every second.
[all …]
|
| /openbmc/linux/drivers/scsi/megaraid/ |
| H A D | mbox_defs.h | 44 * Command for random deletion of logical drives
434 * @num_ldrv : no. of Log Drives configured
439 * @ldrv_state : state of log drives
526 * mraid_ldrv_info_t - information about the logical drives
527 * @nldrv : Number of logical drives configured
543 * mraid_pdrv_info_t - information about the physical drives
555 * @mraid_ldrv_info_t : logical drives information
556 * @mraid_pdrv_info_t : physical drives information
619 * logdrv_param_t - logical drives parameters
644 * @lparam : logical drives parameters
[all …]
|
| /openbmc/linux/Documentation/hwmon/ |
| H A D | drivetemp.rst | 24 drives with temperature sensors.
36 Reading the drive temperature may reset the spin down timer on some drives.
37 This has been observed with WD120EFAX drives, but may be seen with other
38 drives as well. The same behavior is observed if the 'hdtemp' or 'smartd'
44 drives experience similar behavior.
46 A known workaround for WD120EFAX drives is to read the drive temperature at
47 intervals larger than twice the spin-down time. Otherwise affected drives
|
| /openbmc/linux/include/linux/phy/ |
| H A D | phy-mipi-dphy.h | 52 * Time, in picoseconds, that the transmitter drives the Clock
86 * Time, in picoseconds, that the transmitter drives the HS-0
97 * Time, in picoseconds, that the transmitter drives the HS-0
126 * Time, in picoseconds, that the transmitter drives LP-11
136 * Time, in picoseconds, that the transmitter drives the Data
173 * Time, in picoseconds, that the transmitter drives the
185 * Time, in picoseconds, that the transmitter drives the HS-0
213 * Time, in picoseconds, that the new transmitter drives the
224 * Time, in picoseconds, that the transmitter drives the
247 * Time, in microseconds, that a transmitter drives a Mark-1
|
| /openbmc/linux/drivers/md/ |
| H A D | Kconfig | 101 A RAID-1 set consists of several disk drives which are exact copies
105 kernel. In a set with N drives, the available space is the capacity
107 drives.
148 A RAID-5 set of N drives with a capacity of C MB per drive provides
150 of a single drive. For a given sector (row) number, (N - 1) drives
153 while a RAID-5 set distributes the parity across the drives in one
156 A RAID-6 set of N drives with a capacity of C MB per drive
158 against a failure of any two drives. For a given sector
159 (row) number, (N - 2) drives contain data sectors, and two
160 drives contains two independent redundancy syndromes. Like
[all …]
|
| /openbmc/linux/Documentation/admin-guide/blockdev/ |
| H A D | paride.rst | 13 CD-ROM, LS-120 and tape drives use the parallel port to connect to their
19 (The Iomega PPA-3 adapter used in the ZIP drives is an example of this
26 drives use the ISA replicator to interface a floppy disk controller,
38 drives or scanners. Many different devices are supported by the
43 - MicroSolutions backpack hard-drives
45 - SyQuest EZ-135, EZ-230 & SparQ drives
50 - Hewlett-Packard 5GB and 8GB tape drives
51 - Hewlett-Packard 7100 and 7200 CD-RW drives
191 3.3 Some drives need a printer reset
194 There appear to be a number of "noname" external drives on the market
[all …]
|
| /openbmc/linux/drivers/ata/pata_parport/ |
| H A D | Kconfig | 19 parallel port Series 5 IDE protocol. (Most BACKPACK drives made
20 before 1999 were Series 5) Series 5 drives will NOT always have the
31 parallel port Series 6 IDE protocol. (Most BACKPACK drives made
32 after 1999 were Series 6) Series 6 drives will have the Series noted
59 (low speed) adapter that is used in some portable hard drives.
125 used in some 2.5" portable hard drives.
|
| /openbmc/qemu/tests/qemu-iotests/ |
| H A D | 124 | 95 self.drives = list()
122 self.drives.append({
127 return self.drives[-1]
182 drive = self.drives[-1]
260 self.add_bitmap('bitmap0', self.drives[0], **kwargs)
266 self.hmp_io_writes(self.drives[0]['id'], (('0xab', 0, 512),
271 self.hmp_io_writes(self.drives[0]['id'], (('0x9a', 0, 512),
327 drive0 = self.drives[0]
383 drive0 = self.drives[0]
442 # Create bitmaps and full backups for both drives
[all …]
|
| /openbmc/linux/drivers/hwmon/ |
| H A D | drivetemp.c | 3 * Hwmon client for disk and solid state drives with temperature sensors
7 * Hwmon client for S.M.A.R.T. hard disk drives with temperature sensors.
13 * This drive supports reporting the temperature of SATA drives. It can be
14 * easily extended to report the temperature of SCSI drives.
17 * for ATA drives is the SCT Command Transport feature set as specified in
50 * undesirable. However, some older drives may instead
66 * in degrees C on almost all drives. Some drives may report a fractional
72 * - A few Maxtor drives report an unknown or bad value in attribute 194.
73 * - Certain Apple SSD drives repor
[all...] |
| /openbmc/linux/Documentation/scsi/ |
| H A D | hpsa.rst | 11 driver (for logical drives) AND a SCSI driver (for tape drives). This
57 (e.g. hot-plugged tape drives, or newly configured or deleted logical drives,
62 tape drives, or entire storage boxes containing pre-configured logical drives.
|
| H A D | st.rst | 33 QIC-drives). The result is that any tape can be read, writing can be
123 The tape driver currently supports up to 2^17 drives if 4 modes for
167 The st driver maintains statistics for tape drives inside the sysfs filesystem.
290 this read command. Should be disabled for those drives that don't like
435 for SCSI-1 drives and SCSI-2 seek for SCSI-2 drives. The file and
453 SCSI mode page 15. Note that some drives other methods for
454 control of compression. Some drives (like the Exabytes) use
455 density codes for compression control. Some drives use another
457 driver. Some drives without compression capability will accept
471 drives and several early drives this is the physically first
[all …]
|
| /openbmc/linux/fs/adfs/ |
| H A D | Kconfig | 10 here, Linux will be able to read from ADFS partitions on hard drives
15 /dev/[hs]d?1) on each of your drives. Please read the file
28 hard drives and ADFS-formatted floppy disks. This is experimental
|
| /openbmc/linux/Documentation/admin-guide/device-mapper/ |
| H A D | dm-raid.rst | 124 2 drives 3 drives 4 drives
142 2 drives 3 drives 4 drives
158 2 drives 3 drives 4 drives
225 given for both the metadata and data drives for a given position.
233 # RAID4 - 4 data drives, 1 parity (no metadata devices)
242 # RAID4 - 4 data drives, 1 parity (with metadata devices)
|
| /openbmc/libbej/test/ |
| H A D | bej_encoder_test.cpp | 101 "@odata.id": "/redfish/v1/drives/1",
106 "target": "/redfish/v1/drives/1/Actions/Drive.Reset",
135 bejTreeAddString(&root, &odataId, "@odata.id", "/redfish/v1/drives/1"); in createDriveOem()
151 "/redfish/v1/drives/1/Actions/Drive.Reset"); in createDriveOem()
295 const char* drives[1] = {"/redfish/v1/Chassis/SomeChassis/Drives/SATA_0"}; in createChassisResource() local
333 redfishCreateArrayOfLinksJson(&links, "Drives", /*linkCount=*/1, drives, in createChassisResource()
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/ |
| H A D | CertificateCollection.json | 142 … "/redfish/v1/Systems/{ComputerSystemId}/Storage/{StorageId}/Drives/{DriveId}/Certificates",
143 "/redfish/v1/Chassis/{ChassisId}/Drives/{DriveId}/Certificates",
144 …/CompositionService/ResourceBlocks/{ResourceBlockId}/Storage/{StorageId}/Drives/{DriveId}/Certific…
145 … "/redfish/v1/CompositionService/ResourceBlocks/{ResourceBlockId}/Drives/{DriveId}/Certificates",
146 …eBlocks/{ResourceBlockId}/Systems/{ComputerSystemId}/Storage/{StorageId}/Drives/{DriveId}/Certific…
147 … "/redfish/v1/ResourceBlocks/{ResourceBlockId}/Storage/{StorageId}/Drives/{DriveId}/Certificates",
148 "/redfish/v1/ResourceBlocks/{ResourceBlockId}/Drives/{DriveId}/Certificates",
149 …eBlocks/{ResourceBlockId}/Systems/{ComputerSystemId}/Storage/{StorageId}/Drives/{DriveId}/Certific…
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | CertificateCollection.json | 142 … "/redfish/v1/Systems/{ComputerSystemId}/Storage/{StorageId}/Drives/{DriveId}/Certificates",
143 "/redfish/v1/Chassis/{ChassisId}/Drives/{DriveId}/Certificates",
144 …/CompositionService/ResourceBlocks/{ResourceBlockId}/Storage/{StorageId}/Drives/{DriveId}/Certific…
145 … "/redfish/v1/CompositionService/ResourceBlocks/{ResourceBlockId}/Drives/{DriveId}/Certificates",
146 …eBlocks/{ResourceBlockId}/Systems/{ComputerSystemId}/Storage/{StorageId}/Drives/{DriveId}/Certific…
147 … "/redfish/v1/ResourceBlocks/{ResourceBlockId}/Storage/{StorageId}/Drives/{DriveId}/Certificates",
148 "/redfish/v1/ResourceBlocks/{ResourceBlockId}/Drives/{DriveId}/Certificates",
149 …eBlocks/{ResourceBlockId}/Systems/{ComputerSystemId}/Storage/{StorageId}/Drives/{DriveId}/Certific…
|
| /openbmc/linux/Documentation/cdrom/ |
| H A D | cdrom-standard.rst | 50 adapted their drives to one or more of the already existing electrical
57 drives are either IDE/ATAPI or SCSI, and it is very unlikely that any
58 manufacturer will create a new interface. Even finding drives for the
71 ejection. Undoubtedly, the capabilities of the different drives vary,
72 but even when two drives have the same capability their drivers'
93 Driver is simply to give people writing application programs for CD-ROM drives
103 the IDE/ATAPI drives and, of course, the SCSI drives, but as prices
106 that these drives behave in the same way. In December 1994, one of the
107 cheapest CD-ROM drives was a Philips cm206, a double-speed proprietary
109 proprietary drives became obsolete and IDE/ATAPI drives became the
[all …]
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Inventory/Item/ |
| H A D | Drive.interface.yaml | 35 How much of the drives life is remaining in a percentage from 0-100 .
86 Possible encryption states drives could have
99 Possible lock states drives could have
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/csdl/ |
| H A D | DriveMetrics_v1.xml | 59 …<String>/redfish/v1/Systems/{ComputerSystemId}/Storage/{StorageId}/Drives/{DriveId}/Metrics</Strin…
60 <String>/redfish/v1/Chassis/{ChassisId}/Drives/{DriveId}/Metrics</String>
61 …/CompositionService/ResourceBlocks/{ResourceBlockId}/Storage/{StorageId}/Drives/{DriveId}/Metrics<…
62 …<String>/redfish/v1/CompositionService/ResourceBlocks/{ResourceBlockId}/Drives/{DriveId}/Metrics</…
63 …eBlocks/{ResourceBlockId}/Systems/{ComputerSystemId}/Storage/{StorageId}/Drives/{DriveId}/Metrics<…
64 …<String>/redfish/v1/ResourceBlocks/{ResourceBlockId}/Storage/{StorageId}/Drives/{DriveId}/Metrics<…
65 <String>/redfish/v1/ResourceBlocks/{ResourceBlockId}/Drives/{DriveId}/Metrics</String>
66 …eBlocks/{ResourceBlockId}/Systems/{ComputerSystemId}/Storage/{StorageId}/Drives/{DriveId}/Metrics<…
|
| H A D | CertificateCollection_v1.xml | 106 …<String>/redfish/v1/Systems/{ComputerSystemId}/Storage/{StorageId}/Drives/{DriveId}/Certificates</…
107 <String>/redfish/v1/Chassis/{ChassisId}/Drives/{DriveId}/Certificates</String>
108 …/CompositionService/ResourceBlocks/{ResourceBlockId}/Storage/{StorageId}/Drives/{DriveId}/Certific…
109 …<String>/redfish/v1/CompositionService/ResourceBlocks/{ResourceBlockId}/Drives/{DriveId}/Certifica…
110 …eBlocks/{ResourceBlockId}/Systems/{ComputerSystemId}/Storage/{StorageId}/Drives/{DriveId}/Certific…
111 …<String>/redfish/v1/ResourceBlocks/{ResourceBlockId}/Storage/{StorageId}/Drives/{DriveId}/Certific…
112 … <String>/redfish/v1/ResourceBlocks/{ResourceBlockId}/Drives/{DriveId}/Certificates</String>
113 …eBlocks/{ResourceBlockId}/Systems/{ComputerSystemId}/Storage/{StorageId}/Drives/{DriveId}/Certific…
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/installed/ |
| H A D | CertificateCollection_v1.xml | 106 …<String>/redfish/v1/Systems/{ComputerSystemId}/Storage/{StorageId}/Drives/{DriveId}/Certificates</…
107 <String>/redfish/v1/Chassis/{ChassisId}/Drives/{DriveId}/Certificates</String>
108 …/CompositionService/ResourceBlocks/{ResourceBlockId}/Storage/{StorageId}/Drives/{DriveId}/Certific…
109 …<String>/redfish/v1/CompositionService/ResourceBlocks/{ResourceBlockId}/Drives/{DriveId}/Certifica…
110 …eBlocks/{ResourceBlockId}/Systems/{ComputerSystemId}/Storage/{StorageId}/Drives/{DriveId}/Certific…
111 …<String>/redfish/v1/ResourceBlocks/{ResourceBlockId}/Storage/{StorageId}/Drives/{DriveId}/Certific…
112 … <String>/redfish/v1/ResourceBlocks/{ResourceBlockId}/Drives/{DriveId}/Certificates</String>
113 …eBlocks/{ResourceBlockId}/Systems/{ComputerSystemId}/Storage/{StorageId}/Drives/{DriveId}/Certific…
|