THIS FIELD NOTICE IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTY OF MERCHANTABILITY. YOUR USE OF THE INFORMATION ON THE FIELD NOTICE OR MATERIALS LINKED FROM THE FIELD NOTICE IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS FIELD NOTICE AT ANY TIME.
Revision | Publish Date | Comments |
---|---|---|
1.0 |
21-Sep-21 |
Initial Release |
Affected Product ID | Comments |
---|---|
UCS-SD38TK1X-EV |
|
UCS-SD38TK1X-EV= |
Part Alternate |
UCS-SD76TK1X-EV |
|
UCS-SD76TK1X-EV= |
Part Alternate |
UCS-SD15TK1X-EV |
|
UCS-SD15TK1X-EV= |
Part Alternate |
UCS-SD38TKB1X-EV |
|
UCS-SD38TKB1X-EV= |
Part Alternate |
UCS-SD76TKB1X-EV |
|
UCS-SD76TKB1X-EV= |
Part Alternate |
UCS-SD15TKB1X-EV |
|
UCS-SD15TKB1X-EV= |
Part Alternate |
UCS-SD32TK3X-EP |
|
UCS-SD32TKB3X-EP |
|
UCS-SD32TK3X-EP= |
Part Alternate |
UCS-SD32TKB3X-EP= |
Part Alternate |
HX-SD15TK1X-EV |
|
HX-SD15TK1X-EV= |
|
HX-SD15TKB1X-EV |
|
HX-SD15TKB1X-EV= |
|
HX-SD32TK3X-EP |
|
HX-SD32TK3X-EP= |
|
HX-SD32TKB3X-EP |
|
HX-SD32TKB3X-EP= |
|
HX-SD38TK1X-EV |
|
HX-SD38TK1X-EV= |
|
HX-SD38TKB1X-EV |
|
HX-SD38TKB1X-EV= |
|
HX-SD76TK1X-EV |
|
HX-SD76TK1X-EV= |
|
HX-SD76TKB1X-EV |
|
HX-SD76TKB1X-EV= |
|
APIC-SD38TK1X-EV |
|
APIC-SD38TK1X-EV= |
|
UCSX-SD15TK1X-EV |
|
UCSX-SD15TK1X-EV= |
|
UCSX-SD32TK3X-EP |
|
UCSX-SD32TK3X-EP= |
|
UCSX-SD38TK1X-EV |
|
UCSX-SD38TK1X-EV= |
|
UCSX-SD76TK1X-EV |
|
UCSX-SD76TK1X-EV= |
Defect ID | Headline |
---|---|
CSCvy52309 | SSD Timeout - Drive goes to failure mode and stop current operation |
Certain Solid State Drive (SSD) models might detect a Logical Block Address (LBA) mismatch condition and halt the drive IO operation. The drive will no longer be recoverable if this condition occurs.
Certain high capacity SSD models are composed of 512Gb Flash memory chips. When reading the data from this Flash memory chip, the impacted drive firmware mistakenly drops one bit of the physical data address, which causes an internal mismatch condition. Because user-data stored in the Flash memory is protected by the LBA seeded cyclic redundancy check (CRC), the drive correctly detects the address mismatch and stops drive operation.
The drive will experience sudden unexpected failure and will not recover by a power cycle.
This issue is fixed in the drive firmware 0103 and later. Customers should upgrade to these software bundles (or later), which contain the fixed drive firmware.
Platform | Release |
---|---|
UCS B-Series Blade Server Software |
UCS Infrastructure and UCS Manager Software - Release 4.1(3e) or |
UCS C-Series Rack-Mount UCS-Managed Server Software |
or |
UCS C220 M5 Rack Server Software | Release 4.1(3d) |
UCS C240 M5 Rack Server Software | Release 4.1(3d) |
UCS C240 M6 Rack Server Software | Release 4.2(1b) |
UCS C220 M6 Rack Server Software | Release 4.2(1b) |
For more details on how to use the Host Update Utility (HUU) to update disk drive firmware, see Cisco UCS C-Series Rack Servers End-User Guides.
For more details on how to upgrade the disk firmware using Cisco UCS Manager, see Cisco UCS Manager Firmware Management Guides.
Note: By default, a Host Firmware Package (HFP) will exclude Local Disk firmware. In order to ensure that you can manually modify your HFP to include the Local Disk firmware, uncheck the Local Disk check box in the Excluded Components section.
This issue only impacts the drive Product IDs (PIDs) mentioned in the Products Affected section. Of these impacted PIDs, only those drives that run firmware version 0102 are affected. Drives which match the PIDs in the Products Affected section and have the 0103 and later firmware versions are fixed and do not require an update. Drives which do not match the the PIDs in the Products Affected section are not impacted, even though their firmware version might appear to be an earlier version.
There are several ways to identify the PID and firmware based on the preferred management utility.
UCS Manager Managed Servers
The most direct method to quickly gather all drive details from Unified Computing System Manager (UCS Manager) managed servers is to use the Managed Object Browser (MOB) built in to the UCS Manager. Input your IP address into the query and open the link in a browser. Note that in this example, the drive does not match the PID in the Products Affected section and is therefore not impacted.
In order to directly view individual server drive models and firmware, navigate to the UCS Manager Virtual IP (VIP) page in your browser. In the Navigation Pane (left-hand side), choose Equipment > Rack Mount > Servers or Equipment > Chassis > Servers. In the Action Pane (middle of the screen), click the Inventory > Storage > Disks tabs. Here you can double-click each individual disk to view more details, which includes Model and Firmware. In this example, the drive PID matches an entry in the Products Affected section and the firmware version 0102. This is an impacted drive.
Standalone Rack Servers (Cisco IMC Managed)
For Cisco IMC Managed servers, navigate to the Cisco IMC IP. In order to view the PIDs of the installed drives, navigate to the Compute page. Click the PID Catalog > HDD tabs. Verify the Product ID against the Products Affected table.
In order to view the firmware running on any potentially impacted HDDs, navigate to the Storage page and choose the appropriate storage controller. Click the Physical Drive Info tab and check the individual Physical Drives check boxes. As the PID is listed in the Products Affected section and the firmware is 0102, this is an impacted drive.
If you require further assistance, or if you have any further questions regarding this field notice, please contact the Cisco Systems Technical Assistance Center (TAC) by one of the following methods:
My Notifications—Set up a profile to receive email updates about reliability, safety, network security, and end-of-sale issues for the Cisco products you specify.
Unleash the Power of TAC's Virtual Assistance