skip to main content

ThinkSystem ER3 Read Intensive SATA 6Gb SSDs

Product Guide

Home
Top
Author
Updated
22 May 2024
Form Number
LP1858
PDF size
13 pages, 148 KB

Abstract

The ThinkSystem ER3 Read Intensive SATA 6Gb SSDs, in capacities up to 960GB, are 6Gb SATA drives, available in M.2 form factor. They are suitable for general data storage functions and operating system boot purposes on ThinkSystem servers.

This product guide provides essential presales information to understand the ER3 SSDs and their key features, specifications, and compatibility. This guide is intended for technical specialists, sales specialists, sales engineers, IT architects, and other IT professionals who want to learn more about the ER3 SSDs and consider their use in IT solutions.

Change History

Changes in the May 22, 2024 update:

  • Removed the 2.5-inch drives as not announced:
    • ThinkSystem 2.5" ER3 240GB Read Intensive SATA 6Gb HS SSD, 4XB7A90868
    • ThinkSystem 2.5" ER3 480GB Read Intensive SATA 6Gb HS SSD, 4XB7A90869
    • ThinkSystem 2.5" ER3 960GB Read Intensive SATA 6Gb HS SSD, 4XB7A90870
    • ThinkSystem 2.5" ER3 1.92TB Read Intensive SATA 6Gb HS SSD, 4XB7A90871
    • ThinkSystem 2.5" ER3 3.84TB Read Intensive SATA 6Gb HS SSD, 4XB7A95567

Introduction

The ThinkSystem ER3 Read Intensive SATA 6Gb SSDs, in capacities up to 960GB, are 6Gb SATA drives, available in an M.2 form factor. They are suitable for general data storage functions and operating system boot purposes on ThinkSystem servers.

ThinkSystem ER3 Read Intensive SATA 6Gb SSDs
Figure 1. ThinkSystem ER3 Read Intensive SATA 6Gb SSDs

Did you know?

The ER3 M.2 SATA SSDs deliver affordability and performance with superior M.2 random read speeds of up to 90,000 IOPS. In addition, it offers low active read power consumption at only 3.5W for energy efficiency.

Part number information

The following tables list the information for ordering part numbers and feature codes.

Table 1. Ordering part numbers and feature codes
Part number Feature Description Vendor part number
M.2 drives (non-hot-swap)
4XB7A89422 BYF7 ThinkSystem M.2 ER3 240GB Read Intensive SATA 6Gb NHS SSD ER3-GD240
4XB7A90049 BYF8 ThinkSystem M.2 ER3 480GB Read Intensive SATA 6Gb NHS SSD ER3-GD480
4XB7A90230 BYF9 ThinkSystem M.2 ER3 960GB Read Intensive SATA 6Gb NHS SSD ER3-GD960

The part numbers include the following items:

  • One M.2 drive drive
  • Documentation flyer

Features

The ThinkSystem ER3 Read Intensive SATA 6Gb SSDs have the following features:

  • Based on the SSSTC ER3 family of solid state drives
  • 3D TLC NAND flash
  • End-to-end data protection
  • Thermal throttling/sensor
  • Power loss protection (PLP)
  • High I/O & throughput performance
  • Inrush current management
  • ROHS-compliant
  • Command sets: TRIM, S.M.A.R.T, NCQ
  • TCG Enterprise compliant self-encrypting drive (SED)

Read Intensive SSDs and Mixed Use SSDs have similar read and write IOPS performance, but the key difference between them is their endurance (or lifetime) — that is, how long they can perform write operations because SSDs have a finite number of program/erase (P/E) cycles. Read Intensive SSDs typically have a better cost per read IOPS ratio but lower endurance and performance compared to Mixed Use SSDs.

The TBW value assigned to a solid-state device is the total bytes of written data (based on the number of P/E cycles) that a drive can be guaranteed to complete (% of remaining P/E cycles = % of remaining TBW). Reaching this limit does not cause the drive to immediately fail. It simply denotes the maximum number of writes that can be guaranteed. A solid-state device will not fail upon reaching the specified TBW. At some point based on manufacturing variance margin, after surpassing the TBW value, the drive will reach the end-of-life point, at which the drive will go into a read-only mode.

For example, the ER3 960 GB M.2 drive has an endurance of 1,750 TB of total bytes written (TBW). This means that for full operation over five years, write workload must be limited to no more than 959 GB of writes per day, which is equivalent to 1.0 full drive writes per day (DWPD). For the device to last three years, the drive write workload must be limited to no more than 1,598 GB of writes per day, which is equivalent to 1.7 full drive writes per day.

The benefits of drive encryption

Self-encrypting drives (SEDs) provide benefits in three main ways:

  • By encrypting data on-the-fly at the drive level with no performance impact
  • By providing instant secure erasure (cryptographic erasure, thereby making the data no longer readable)
  • By enabling auto-locking to secure active data if a drive is misplaced or stolen from a system while in use

The following sections describe the benefits in more details.

Automatic encryption

It is vital that a company keep its data secure. With the threat of data loss due to physical theft or improper inventory practices, it is important that the data be encrypted. However, challenges with performance, scalability, and complexity have led IT departments to push back against security policies that require the use of encryption. In addition, encryption has been viewed as risky by those unfamiliar with key management, a process for ensuring a company can always decrypt its own data. Self-encrypting drives comprehensively resolve these issues, making encryption both easy and affordable.

When the self-encrypting drive is in normal use, its owner need not maintain authentication keys (otherwise known as credentials or passwords) in order to access the data on the drive. The self-encrypting drive will encrypt data being written to the drive and decrypt data being read from it, all without requiring an authentication key from the owner.

Drive retirement and disposal

When hard drives are retired and moved outside the physically protected data center into the hands of others, the data on those drives is put at significant risk. IT departments retire drives for a variety of reasons, including:

  • Returning drives for warranty, repair, or expired lease agreements
  • Removal and disposal of drives
  • Repurposing drives for other storage duties

Nearly all drives eventually leave the data center and their owner's control. Corporate data resides on such drives, and when most leave the data center, the data they contain is still readable. Even data that has been striped across many drives in a RAID array is vulnerable to data theft because just a typical single stripe in today’s high-capacity arrays is large enough to expose for example, hundreds of names and bank account numbers.

In an effort to avoid data breaches and the ensuing customer notifications required by data privacy laws, companies use different methods to erase the data on retired drives before they leave the premises and potentially fall into the wrong hands. Current retirement practices that are designed to make data unreadable rely on significant human involvement in the process, and are thus subject to both technical and human failure.

The drawbacks of today’s drive retirement practices include the following:

  • Overwriting drive data is expensive, tying up valuable system resources for days. No notification of completion is generated by the drive, and overwriting won’t cover reallocated sectors, leaving that data exposed.
  • Methods that include degaussing or physically shredding a drive are expensive. It is difficult to ensure the degauss strength is optimized for the drive type, potentially leaving readable data on the drive. Physically shredding the drive is environmentally hazardous, and neither practice allows the drive to be returned for warranty or expired lease.
  • Some companies have concluded the only way to securely retire drives is to keep them in their control, storing them indefinitely in warehouses. But this is not truly secure because a large volume of drives coupled with human involvement inevitably leads to some drives being lost or stolen.
  • Professional disposal services is an expensive option and includes the cost of reconciling the services as well as internal reports and auditing. Transporting of the drives also has the potential of putting the data at risk.

Self-encrypting drives eliminate the need to overwrite, destroy, or store retired drives. When the drive is to be retired, it can be cryptographically erased, a process that is nearly instantaneous regardless of the capacity of the drive.

Instant secure erase

The self-encrypting drive provides instant data encryption key destruction via cryptographic erasure. When it is time to retire or repurpose the drive, the owner sends a command to the drive to perform a cryptographic erasure. Cryptographic erasure simply replaces the encryption key inside the encrypted drive, making it impossible to ever decrypt the data encrypted with the deleted key.

Self-encrypting drives reduce IT operating expenses by reducing asset control challenges and disposal costs. Data security with self-encrypting drives helps ensure compliance with privacy regulations without hindering IT efficiency. So called "Safe Harbor" clauses in government regulations allow companies to not have to notify customers of occurrences of data theft if that data was encrypted and therefore unreadable.

Furthermore, self-encrypting drives simplify decommissioning and preserve hardware value for returns and repurposing by:

  • Eliminating the need to overwrite or destroy the drive
  • Securing warranty returns and expired lease returns
  • Enabling drives to be repurposed securely

Auto-locking

Insider theft or misplacement is a growing concern for businesses of all sizes; in addition, managers of branch offices and small businesses without strong physical security face greater vulnerability to external theft. Self-encrypting drives include a feature called auto-lock mode to help secure active data against theft.

Using a self-encrypting drive when auto-lock mode is enabled simply requires securing the drive with an authentication key. When secured in this manner, the drive’s data encryption key is locked whenever the drive is powered down. In other words, the moment the self-encrypting drive is switched off or unplugged, it automatically locks down the drive’s data.

When the self-encrypting drive is then powered back on, it requires authentication before being able to unlock its encryption key and read any data on the drive, thus protecting against misplacement and theft.

While using self-encrypting drives just for the instant secure erase is an extremely efficient and effective means to help securely retire a drive, using self-encrypting drives in auto-lock mode provides even more advantages. From the moment the drive or system is removed from the data center (with or without authorization), the drive is locked. No advance thought or action is required from the data center administrator to protect the data. This helps prevent a breach should the drive be mishandled and helps secure the data against the threat of insider or outside theft.

Technical specifications

The following table lists the technical specifications for the ER3 SSDs in the M.2 form factor

Table 2. Technical specifications for M.2 drives
Feature 240 GB drive 480 GB drive 960 GB drive
Interface 6 Gb SATA 6 Gb SATA 6 Gb SATA
Form factor M.2 2280 M.2 2280 M.2 2280
Capacity 240 GB 480 GB 960 GB
SED encryption TCG Enterprise TCG Enterprise TCG Enterprise
Endurance (drive writes per day for 5 years) 1 DWPD 1 DWPD 1 DWPD
Endurance (total bytes written) 430 TB 870 TB 1750 TB
Data reliability (UBER) < 1 in 1017 bits read < 1 in 1017 bits read < 1 in 1017 bits read
MTBF 2,000,000 hours 2,000,000 hours 2,000,000 hours
Performance  
IOPS reads (4 KB blocks) 90,000 90,000 90,000
IOPS writes (4 KB blocks) 10,000 15,000 15,000
Sequential read rate (128 KB blocks) 520 MB/s 520 MB/s 520 MB/s
Sequential write rate (128 KB blocks) 280 MB/s 520 MB/s 520 MB/s
Read latency (random) 120 µs 120 µs 120 µs
Write latency (random) 90 µs 70 µs 70 µs
Environment  
Shock, non-operating 1,500 G (Max) at 0.5 ms 1,500 G (Max) at 0.5 ms 1,500 G (Max) at 0.5 ms
Vibration, non-operating 3.13 GRMS (5-800 Hz) 3.13 GRMS (5-800 Hz) 3.13 GRMS (5-800 Hz)
Typical power (R/W) 3.5 W / 3.8 W 3.5 W / 3.8 W 3.5 W / 3.8 W

Server support

The following tables list the ThinkSystem servers that are compatible.

Table 3. Server support (Part 1 of 4)
Part Number Description AMD V3 2S Intel V3/V4 4S 8S Intel V3 Multi Node V3/V4 1S V3
SR635 V3 (7D9H / 7D9G)
SR655 V3 (7D9F / 7D9E)
SR645 V3 (7D9D / 7D9C)
SR665 V3 (7D9B / 7D9A)
ST650 V3 (7D7B / 7D7A)
SR630 V3 (7D72 / 7D73)
SR650 V3 (7D75 / 7D76)
SR630 V4 (7DG8 / 7DG9)
SR850 V3 (7D97 / 7D96)
SR860 V3 (7D94 / 7D93)
SR950 V3 (7DC5 / 7DC4)
SD535 V3 (7DD8 / 7DD1)
SD530 V3 (7DDA / 7DD3)
SD550 V3 (7DD9 / 7DD2)
SD520 V4 (7DFZ / 7DFY)
ST45 V3 (7DH4 / 7DH5)
ST50 V3 (7DF4 / 7DF3)
ST250 V3 (7DCF / 7DCE)
SR250 V3 (7DCM / 7DCL)
M.2 drives (non-hot-swap)
4XB7A89422 ThinkSystem M.2 ER3 240GB Read Intensive SATA 6Gb NHS SSD Y Y Y Y Y Y Y N Y Y N Y Y Y Y N N Y Y
4XB7A90049 ThinkSystem M.2 ER3 480GB Read Intensive SATA 6Gb NHS SSD Y Y Y Y Y Y Y N Y Y N Y Y Y Y N N Y Y
4XB7A90230 ThinkSystem M.2 ER3 960GB Read Intensive SATA 6Gb NHS SSD Y Y Y Y Y Y Y N Y Y N Y Y Y Y N N Y Y
Table 4. Server support (Part 2 of 4)
Part Number Description GPU Rich Edge Super Computing 1S Intel V2
SR670 V2 (7Z22 / 7Z23)
SR675 V3 (7D9Q / 7D9R)
SR680a V3 (7DHE)
SR685a V3 (7DHC)
SR780a V3 (7DJ5)
SE350 (7Z46 / 7D1X)
SE350 V2 (7DA9)
SE360 V2 (7DAM)
SE450 (7D8T)
SE455 V3 (7DBY)
SC750 V4 (7DDJ)
SC777 V4 (7DKA)
SD665 V3 (7D9P)
SD665-N V3 (7DAZ)
SD650 V3 (7D7M)
SD650-I V3 (7D7L)
SD650-N V3 (7D7N)
ST50 V2 (7D8K / 7D8J)
ST250 V2 (7D8G / 7D8F)
SR250 V2 (7D7R / 7D7Q)
M.2 drives (non-hot-swap)
4XB7A89422 ThinkSystem M.2 ER3 240GB Read Intensive SATA 6Gb NHS SSD Y N N N N Y N N Y Y N N N N N N N N Y Y
4XB7A90049 ThinkSystem M.2 ER3 480GB Read Intensive SATA 6Gb NHS SSD Y N N N N Y N N Y Y N N N N N N N N Y Y
4XB7A90230 ThinkSystem M.2 ER3 960GB Read Intensive SATA 6Gb NHS SSD Y N N N N Y N N Y Y N N N N N N N N N Y
Table 5. Server support (Part 3 of 4)
Part Number Description 2S Intel V2 AMD V1 Dense V2 4S V2 8S 4S V1
ST650 V2 (7Z75 / 7Z74)
SR630 V2 (7Z70 / 7Z71)
SR650 V2 (7Z72 / 7Z73)
SR635 (7Y98 / 7Y99)
SR655 (7Y00 / 7Z01)
SR655 Client OS
SR645 (7D2Y / 7D2X)
SR665 (7D2W / 7D2V)
SD630 V2 (7D1K)
SD650 V2 (7D1M)
SD650-N V2 (7D1N)
SN550 V2 (7Z69)
SR850 V2 (7D31 / 7D32)
SR860 V2 (7Z59 / 7Z60)
SR950 (7X11 / 7X12)
SR850 (7X18 / 7X19)
SR850P (7D2F / 2D2G)
SR860 (7X69 / 7X70)
M.2 drives (non-hot-swap)
4XB7A89422 ThinkSystem M.2 ER3 240GB Read Intensive SATA 6Gb NHS SSD Y Y Y Y Y Y Y Y Y N N N N Y N N N N
4XB7A90049 ThinkSystem M.2 ER3 480GB Read Intensive SATA 6Gb NHS SSD Y Y Y Y Y Y Y Y Y N N N N Y N N N N
4XB7A90230 ThinkSystem M.2 ER3 960GB Read Intensive SATA 6Gb NHS SSD Y Y Y Y Y Y Y Y Y N N N N Y N N N N
Table 6. Server support (Part 4 of 4)
Part Number Description 1S Intel V1 2S Intel V1 Dense V1
ST50 (7Y48 / 7Y50)
ST250 (7Y45 / 7Y46)
SR150 (7Y54)
SR250 (7Y52 / 7Y51)
ST550 (7X09 / 7X10)
SR530 (7X07 / 7X08)
SR550 (7X03 / 7X04)
SR570 (7Y02 / 7Y03)
SR590 (7X98 / 7X99)
SR630 (7X01 / 7X02)
SR650 (7X05 / 7X06)
SR670 (7Y36 / 7Y37)
SD530 (7X21)
SD650 (7X58)
SN550 (7X16)
SN850 (7X15)
M.2 drives (non-hot-swap)
4XB7A89422 ThinkSystem M.2 ER3 240GB Read Intensive SATA 6Gb NHS SSD N N N N N N N N N N N N N N N N
4XB7A90049 ThinkSystem M.2 ER3 480GB Read Intensive SATA 6Gb NHS SSD N N N N N N N N N N N N N N N N
4XB7A90230 ThinkSystem M.2 ER3 960GB Read Intensive SATA 6Gb NHS SSD N N N N N N N N N N N N N N N N

Operating system support

SAS and SATA SSDs operate transparently to users, storage systems, applications, databases, and operating systems.

Operating system support is based on the controller used to connect to the drives. Consult the controller product guide for more information:

IBM SKLM Key Management support

To effectively manage a large deployment of SEDs in Lenovo servers, IBM Security Key Lifecycle Manager (SKLM) offers a centralized key management solution. Certain Lenovo servers support Features on Demand (FoD) license upgrades that enable SKLM support.

The following table lists the part numbers and feature codes to enable SKLM support in the management processor of the server.

Table 7. FoD upgrades for SKLM support
Part number Feature code Description
Security Key Lifecycle Manager - FoD (United States, Canada, Asia Pacific, and Japan)
00D9998 A5U1 SKLM for System x/ThinkSystem w/SEDs - FoD per Install w/1Yr S&S
00D9999 AS6C SKLM for System x/ThinkSystem w/SEDs - FoD per Install w/3Yr S&S
Security Key Lifecycle Manager - FoD (Latin America, Europe, Middle East, and Africa)
00FP648 A5U1 SKLM for System x/ThinkSystem w/SEDs - FoD per Install w/1Yr S&S
00FP649 AS6C SKLM for System x/ThinkSystem w/SEDs - FoD per Install w/3Yr S&S

The IBM Security Key Lifecycle Manager software is available from Lenovo using the ordering information listed in the following table.

Table 8. IBM Security Key Lifecycle Manager licenses
Part number Description
7S0A007FWW IBM Security Key Lifecycle Manager Basic Edition Install License + SW Subscription & Support 12 Months
7S0A007HWW IBM Security Key Lifecycle Manager For Raw Decimal Terabyte Storage Resource Value Unit License + SW Subscription & Support 12 Months
7S0A007KWW IBM Security Key Lifecycle Manager For Raw Decimal Petabyte Storage Resource Value Unit License + SW Subscription & Support 12 Months
7S0A007MWW IBM Security Key Lifecycle Manager For Usable Decimal Terabyte Storage Resource Value Unit License + SW Subscription & Support 12 Months
7S0A007PWW IBM Security Key Lifecycle Manager For Usable Decimal Petabyte Storage Resource Value Unit License + SW Subscription & Support 12 Months

The following tables list the ThinkSystem servers that are compatible with the FoD upgrades for SKLM.

Table 9. IBM SKLM Key Management support (Part 1 of 4)
Part Number Description AMD V3 2S Intel V3/V4 4S 8S Intel V3 Multi Node V3/V4 1S V3
SR635 V3 (7D9H / 7D9G)
SR655 V3 (7D9F / 7D9E)
SR645 V3 (7D9D / 7D9C)
SR665 V3 (7D9B / 7D9A)
ST650 V3 (7D7B / 7D7A)
SR630 V3 (7D72 / 7D73)
SR650 V3 (7D75 / 7D76)
SR630 V4 (7DG8 / 7DG9)
SR850 V3 (7D97 / 7D96)
SR860 V3 (7D94 / 7D93)
SR950 V3 (7DC5 / 7DC4)
SD535 V3 (7DD8 / 7DD1)
SD530 V3 (7DDA / 7DD3)
SD550 V3 (7DD9 / 7DD2)
SD520 V4 (7DFZ / 7DFY)
ST45 V3 (7DH4 / 7DH5)
ST50 V3 (7DF4 / 7DF3)
ST250 V3 (7DCF / 7DCE)
SR250 V3 (7DCM / 7DCL)
A5U1 SKLM for System x w/SEDs - FoD per Install w/1Yr S&S N N N N Y N N N N N N N N N N N N Y Y
AS6C SKLM for System x w/SEDs - FoD per Install w/3Yr S&S N N N N Y N N N N N N N N N N N N Y Y
Table 10. IBM SKLM Key Management support (Part 2 of 4)
Part Number Description GPU Rich Edge Super Computing 1S Intel V2
SR670 V2 (7Z22 / 7Z23)
SR675 V3 (7D9Q / 7D9R)
SR680a V3 (7DHE)
SR685a V3 (7DHC)
SR780a V3 (7DJ5)
SE350 (7Z46 / 7D1X)
SE350 V2 (7DA9)
SE360 V2 (7DAM)
SE450 (7D8T)
SE455 V3 (7DBY)
SC750 V4 (7DDJ)
SC777 V4 (7DKA)
SD665 V3 (7D9P)
SD665-N V3 (7DAZ)
SD650 V3 (7D7M)
SD650-I V3 (7D7L)
SD650-N V3 (7D7N)
ST50 V2 (7D8K / 7D8J)
ST250 V2 (7D8G / 7D8F)
SR250 V2 (7D7R / 7D7Q)
A5U1 SKLM for System x w/SEDs - FoD per Install w/1Yr S&S N N N N N N N N N N N N N N N N N N Y Y
AS6C SKLM for System x w/SEDs - FoD per Install w/3Yr S&S N N N N N N N N N N N N N N N N N N Y Y
Table 11. IBM SKLM Key Management support (Part 3 of 4)
Part Number Description 2S Intel V2 AMD V1 Dense V2 4S V2 8S 4S V1
ST650 V2 (7Z75 / 7Z74)
SR630 V2 (7Z70 / 7Z71)
SR650 V2 (7Z72 / 7Z73)
SR635 (7Y98 / 7Y99)
SR655 (7Y00 / 7Z01)
SR655 Client OS
SR645 (7D2Y / 7D2X)
SR665 (7D2W / 7D2V)
SD630 V2 (7D1K)
SD650 V2 (7D1M)
SD650-N V2 (7D1N)
SN550 V2 (7Z69)
SR850 V2 (7D31 / 7D32)
SR860 V2 (7Z59 / 7Z60)
SR950 (7X11 / 7X12)
SR850 (7X18 / 7X19)
SR850P (7D2F / 2D2G)
SR860 (7X69 / 7X70)
A5U1 SKLM for System x w/SEDs - FoD per Install w/1Yr S&S N Y Y N N N N N N N N Y Y Y Y Y Y N
AS6C SKLM for System x w/SEDs - FoD per Install w/3Yr S&S N Y Y N N N N N N N N Y Y Y Y Y Y N
Table 12. IBM SKLM Key Management support (Part 4 of 4)
Part Number Description 1S Intel V1 2S Intel V1 Dense V1
ST50 (7Y48 / 7Y50)
ST250 (7Y45 / 7Y46)
SR150 (7Y54)
SR250 (7Y52 / 7Y51)
ST550 (7X09 / 7X10)
SR530 (7X07 / 7X08)
SR550 (7X03 / 7X04)
SR570 (7Y02 / 7Y03)
SR590 (7X98 / 7X99)
SR630 (7X01 / 7X02)
SR650 (7X05 / 7X06)
SR670 (7Y36 / 7Y37)
SD530 (7X21)
SD650 (7X58)
SN550 (7X16)
SN850 (7X15)
A5U1 SKLM for System x w/SEDs - FoD per Install w/1Yr S&S N N N N Y Y Y Y Y N Y N N N N N
AS6C SKLM for System x w/SEDs - FoD per Install w/3Yr S&S N N N N Y Y Y Y Y N Y N N N N N

Warranty

The ER3 SSDs carry a one-year, customer-replaceable unit (CRU) limited warranty. When the SSDs are installed in a supported server, these drives assume the system’s base warranty and any warranty upgrades.

Solid State Memory cells have an intrinsic, finite number of program/erase cycles that each cell can incur. As a result, each solid state device has a maximum amount of program/erase cycles to which it can be subjected. The warranty for Lenovo solid state drives (SSDs) is limited to drives that have not reached the maximum guaranteed number of program/erase cycles, as documented in the Official Published Specifications for the SSD product. A drive that reaches this limit may fail to operate according to its Specifications.

Physical specifications

The ER3 SSDs have the following physical specifications:

  • M.2 form factor:
    • Length: 80 mm
    • Width: 22 mm
    • Thickness: 3.65 mm
    • Weight: 10g

Operating environment

The ER3 SSDs are supported in the following environment:

  • Temperature, operating: 0 to 70 °C (32 to 158 °F)
  • Temperature, non-operating: -40 to 85 °C (-40 to 185 °F)
  • Relative humidity: 5 to 95% (noncondensing)

Agency approvals

The ER3 SSDs conform to the following regulations:

  • CE
  • UL
  • BSMI
  • RoHS

Related product families

Product families related to this document are the following:

Trademarks

Lenovo and the Lenovo logo are trademarks or registered trademarks of Lenovo in the United States, other countries, or both. A current list of Lenovo trademarks is available on the Web at https://www.lenovo.com/us/en/legal/copytrade/.

The following terms are trademarks of Lenovo in the United States, other countries, or both:
Lenovo®
System x®
ThinkSystem®

The following terms are trademarks of other companies:

AMD is a trademark of Advanced Micro Devices, Inc.

Intel® is a trademark of Intel Corporation or its subsidiaries.

Other company, product, or service names may be trademarks or service marks of others.