First, I apologize if I'm beating a dead horse here!
This may shed some light on this question.
I found two documents that refer to the same drive series, including ST12000VN0008.
First is the datasheet, which can be found here:
Ironwolf datasheet
Ironwolf datasheet from 2022 for ST12000VN0008, on page 2:
Next is the manual, which can be found here:
Ironwolf manual
Ironwolf product manual from 8/2021 for ST12000VN0008, on page 8 (page 9 of the PDF):
In spite of how surprising it is that such a technical oversight could be spread throughout their datasheets, I think this comparison of the same specification for the same drive model, stated differently in two different documents, supports my theory that someone at Seagate started using 10Exx to mean 10^xx, probably a long time ago, and that notation has been thoughtlessly copied for years. This theory is bolstered by the fact that WD, a company with arguably similar technology, specifies 1 error in 10^15 bits read for the same enterprise-level SATA drives.
I tried to find a way to contact a real human at Seagate, but they don't appear to provide any way to do that on their website.
This may shed some light on this question.
I found two documents that refer to the same drive series, including ST12000VN0008.
First is the datasheet, which can be found here:
Ironwolf datasheet
Ironwolf datasheet from 2022 for ST12000VN0008, on page 2:
Next is the manual, which can be found here:
Ironwolf manual
Ironwolf product manual from 8/2021 for ST12000VN0008, on page 8 (page 9 of the PDF):
In spite of how surprising it is that such a technical oversight could be spread throughout their datasheets, I think this comparison of the same specification for the same drive model, stated differently in two different documents, supports my theory that someone at Seagate started using 10Exx to mean 10^xx, probably a long time ago, and that notation has been thoughtlessly copied for years. This theory is bolstered by the fact that WD, a company with arguably similar technology, specifies 1 error in 10^15 bits read for the same enterprise-level SATA drives.
I tried to find a way to contact a real human at Seagate, but they don't appear to provide any way to do that on their website.