Seagate Ramping 32TB HAMR HDD in Q1, 40TB+ HDDs in 2025

Seagate
(Image credit: Seagate)

Seagate is on track to ramp up production of its first 32TB hard drive based on its heat-assisted magnetic recording (HAMR) technology in early 2024 and then initiate mass production of 40TB+ HDDs roughly two years after, according to the company's financial report last week. 

"We also expect to begin aggressively ramping 3TB per disk products based on HAMR technology in early calendar 2024," said Dave Mosley, chief executive of Seagate, in a call with financial analysts and investors. "These drives deliver capacity starting at 30 terabytes and offer customers the same flexibility to adopt either CMR or SMR configurations to further boost aerial density into the mid-30TB range."

Seagate has repeatedly reemphasized that its HAMR-based HDDs will largely retain its 10-platter 3.5-inch helium-filled platform with new laser-enhanced write heads, new media, and some other differences. The company's first HAMR-powered 32 TB HDDs are set to ramp volume production in early calendar 2024, which is more or less in line with the company's strategic roadmap from a few years back, which sets the timeframe for HAMR-based drives for 2023, but that was before the company had to design its 2nd Generation HAMR HDD platform to ensure viable yields.  

Indeed, the new platform seems to meet all internal goals. In fact, the company has more than succeeded as the new drives are drop-in compatible with existing infrastructure in terms of power consumption, according to Seagate. 

"We also continued to hit all key HAMR product development milestones," said Mosley. "Initial customer qualifications are progressing very well, and we continue to hit our reliability and yield metrics."

When it comes to the fulfillment of the short-term roadmap, everything looks fine for Seagate. There may be a minor slip from a roadmap it demonstrated a few years back, but given the fact that the company is not behind its rivals in terms of absolute capacity and in terms of areal density, this may be articulated as a minor issue. 

"Qualification and revenue ramp plans for our 30TB+ products remain fully on track with high-volume ramp starting early in calendar 2024," the head of Seagate said. "The launch in ramp of our HAMR products is a competitive differentiator and increasingly important in light of the green shoots that we're starting to see with respect to cloud demand trends."

Anton Shilov
Contributing Writer

Anton Shilov is a contributing writer at Tom’s Hardware. Over the past couple of decades, he has covered everything from CPUs and GPUs to supercomputers and from modern process technologies and latest fab tools to high-tech industry trends.

  • hotaru251
    whats the capacity limit before drives are too big to be rebuilt in safe time due to limitations of their speed?
    Reply
  • thullet
    hotaru251 said:
    whats the capacity limit before drives are too big to be rebuilt in safe time due to limitations of their speed?
    Assuming you're talking about rebuilding a RAID and not the independent disk: Depends on load, number of parity drives, numbers of drives in the array, reliability of the drives and risk tolerance.
    Reply
  • tamalero
    thullet said:
    Assuming you're talking about rebuilding a RAID and not the independent disk: Depends on load, number of parity drives, numbers of drives in the array, reliability of the drives and risk tolerance.
    still.. rebuilding 40 tbs would be like 3-4 days.
    I mean for my 8 tb drive it takes 12 -16 hours and its a 8 drive array.
    Reply
  • thullet
    tamalero said:
    still.. rebuilding 40 tbs would be like 3-4 days.
    I mean for my 8 tb drive it takes 12 -16 hours and its a 8 drive array.
    But you're not running your array with single parity right?
    Reply
  • USAFRet
    RAID rebuild time is dependent on actual consumed space, and system hardware.

    My QNAP, rebuilding a 4 drive RAID 5, takes about 1.5 hours per TB consumed space.
    Reply
  • thullet
    USAFRet said:
    RAID rebuild time is dependent on actual consumed space, and system hardware.
    And load, numbers of parity drives, number of drives in the array.. as stated.
    Reply