- Joined
- Oct 9, 2007
- Messages
- 47,230 (7.55/day)
- Location
- Hyderabad, India
| System Name | RBMK-1000 |
|---|---|
| Processor | AMD Ryzen 7 5700G |
| Motherboard | ASUS ROG Strix B450-E Gaming |
| Cooling | DeepCool Gammax L240 V2 |
| Memory | 2x 8GB G.Skill Sniper X |
| Video Card(s) | Palit GeForce RTX 2080 SUPER GameRock |
| Storage | Western Digital Black NVMe 512GB |
| Display(s) | BenQ 1440p 60 Hz 27-inch |
| Case | Corsair Carbide 100R |
| Audio Device(s) | ASUS SupremeFX S1220A |
| Power Supply | Cooler Master MWE Gold 650W |
| Mouse | ASUS ROG Strix Impact |
| Keyboard | Gamdias Hermes E2 |
| Software | Windows 11 Pro |
Earlier this week, reports emerged of a simple firmware update going wrong for Seagate, rendering some batches of the company's Barracuda 7200.11 hard-drives useless. The flaw in the said firmware update (version SD1A) locked the drive's microcode, preventing the system BIOS from even detecting the drive, in case the user wanted to restore a drive damaged from the update. SD1A was released to fix stuttering problems caused as a result of a bad implementation of the drives' SATA micro-controllers, the earliest diagnosis of the problem the drives were facing. An employee of Seagate working in its engineering, attempted to explain the SD1A firmware debacle, from the perspective of someone who doesn't work with the company's public-relations.
The SD1A firmware, according to the employee, wasn't given out as a singular release, but rather in several revisions to individual customers on a support-customer level, rather than an all-out public download. That was to address customers quickly, when the issue first surfaced as a flaw with the firmware. The problem actually existed where errors during drive operation was written to the drive's firmware to build on a log. When that log reached 320 entries, it would cause errors during initialization of the drive, when it is powered on, when the drive's firmware micro-code is read by the system BIOS. Errors in that process would cause the drive not to be detected / improperly initialized by the system. In a Tom's Hardware report, the employee explains that normally, a customer would go through the usual process of contacting tech-support for the preventative update and "this firmware had to go through five different checks to make sure it applies to the specific conditions to qualify sending to a customer, before now. 5 chances for us to go 'your drive needs the other (or none) firmware update'." However, management, in order to quell the possibility of liability for drive failures, pushed a general public release of the firmware. "Suddenly, it's down to one check, and even that was more designed for a contingency just in case the wrong firmware was sent out." The SD1A firmware mostly affected 500 GB versions of the Barracuda 7200.11 series, after it was released last week. Seagate pulled back the SD1A firmware after the issue of the firmware damaging hard-drives became chronic. The company later released a newer firmware update that can be found here.
View at TechPowerUp Main Site
The SD1A firmware, according to the employee, wasn't given out as a singular release, but rather in several revisions to individual customers on a support-customer level, rather than an all-out public download. That was to address customers quickly, when the issue first surfaced as a flaw with the firmware. The problem actually existed where errors during drive operation was written to the drive's firmware to build on a log. When that log reached 320 entries, it would cause errors during initialization of the drive, when it is powered on, when the drive's firmware micro-code is read by the system BIOS. Errors in that process would cause the drive not to be detected / improperly initialized by the system. In a Tom's Hardware report, the employee explains that normally, a customer would go through the usual process of contacting tech-support for the preventative update and "this firmware had to go through five different checks to make sure it applies to the specific conditions to qualify sending to a customer, before now. 5 chances for us to go 'your drive needs the other (or none) firmware update'." However, management, in order to quell the possibility of liability for drive failures, pushed a general public release of the firmware. "Suddenly, it's down to one check, and even that was more designed for a contingency just in case the wrong firmware was sent out." The SD1A firmware mostly affected 500 GB versions of the Barracuda 7200.11 series, after it was released last week. Seagate pulled back the SD1A firmware after the issue of the firmware damaging hard-drives became chronic. The company later released a newer firmware update that can be found here.
View at TechPowerUp Main Site
Last edited by a moderator:
