![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||||
Solution Type Predictive Self-Healing Sure Solution 1640003.1 : Seagate Firmware Update Requirement
In this Document
Applies to:Sun Fire X4500 Server - Version Not Applicable and laterSun Fire X4540 Server - Version Not Applicable and later Information in this document applies to any platform. PurposeThis document explains the requirements to move from Seagate revision 0F firmware to revision 15 firmware To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the My Oracle Support Community - Sun x86 Systems
ScopeThis document covers the requirements for upgrading firmware on Seagate disks but does not cover the confidential content reserved by Seagate. Confidential content will remain hidden to preserve Seagates discrepancy relationship with Oracle Corporation. DetailsThere is a requirement to move from Seagate firmware SU0F to SU15 for applicable drive types to satisfy system and environment conditions on Oracle servers. A drive's firmware should be upgraded at the customers earliest convenience to prevent long term issues that may arise from a condition understood and already addressed by the Seagate / Oracle relationship. Seagate's drives are manufactured at the highest level of quality so any condition that has been observer by Seagate or it's resellers is usually rapidly addressed. It is therefore up to the reseller to provide upgrade notifications to the customer so that they may increment their firmware revision on each drive at their convenience. Moving from Seagate firmware revision SU0B to SU0D: Certain Disk Drives May Experience Data Miscompare or Drive Initialization Issues. (Doc ID 1020312.1) Moving from Seagate firmware revision SU0D or SU0E to SU0F: No publicly available fixes can be published.
Moving from Seagate firmware revision SU0F to SU10: No publicly available fixes can be published. Incorrect handling of RERR when processing an unrecovered error - Reference IDD-118589 Short DST test does not come to completion - Reference SDD-118553 EE Assert when servicing a Data FIS error - Reference SDD-118926 DST Short test looping when interrupted by host I/O - Reference CDD-129652 Moving from Seagate firmware revision SU10 to SU12: No publicly available fixes can be published. Memory link corrupt caused by freeing VBM cache node twice due to command abort - Reference CDD-122618 IRAW reports false-data error - Reference CDD-133641 Overlapping command times out during sequential Verify workload - Reference CDD-133767 Miscompare due to ERC timeout on cached write data - Reference CDD-135270 Improved RAID systems sequential performance - Reference CDD-142557 SMART attribute 188 counter (timeouts) in incremented incorrectly - Reference IDD-116630 Ensure flash failure due to cache corruption following reset - Reference SDD-103724 Assert Failure: IRAW scheduler failed to schedule next IRAW disk activity - Reference SDD-104834 Processing task mgmt functions during sequential read commands cause an assert - Reference SDD-116644 Assert failure during code download - Reference SDD-134971 Moving from Seagate firmware revision SU12 to SU13: Fix "Compare Error" on a system at 2k Hz vibration (outside of specification) during large sequential write by controlling the WCE error recovery time. Enable TDTarg channel workaround associated with qualifying "Data Sync" during read process which may reduce read performance. Moving from Seagate firmware revision SU13 to SU14: Change RAW temperature threshold from 18 degree C to 12 degree C requested by Oracle. Moving from Seagate firmware revision SU14 to SU15: Change RAW temperature threshold from 12 degree C to 10 degree C requested by Oracle. Attachments This solution has no attachment |
||||||||||||||||||
|