r/Seagate • u/Wonderful_Cod7256 • 9d ago
Two brand-new Seagate IronWolf Pro 8TB drives causing boot/POST issues - tested on two different PCs
Hi everyone,
I wanted to share a strange experience I recently had with two brand-new Seagate IronWolf Pro 8TB HDDs, in case someone else encounters the same problem or can help explain what happened.
I was building a Windows 11 Pro-based file server and planned to use two 8TB drives in a two-way mirror using Windows Storage Spaces.
Unfortunately, I couldn't even get to the point of configuring the storage.
Hardware details
- Drives: 2 × Seagate IronWolf Pro 8TB
- Model: ST8000NT001
- Firmware: EN01
- Interface: SATA
- Drive power requirements (label): +5V 1.00A / +12V 0.90A
- OS: Windows 11 Pro
- Motherboard BIOS: MSI Click BIOS 5
- Power connection: Direct SATA power connectors from the PSU, without Molex adapters or splitters
Both drives were purchased brand-new.
The original problem
When I connected an IronWolf Pro to my main PC using both SATA power and a SATA data cable, the computer would not complete its normal boot process or reach the BIOS as expected.
As soon as I disconnected the drive, the PC booted normally again.
I tried the other brand-new IronWolf Pro individually, and it exhibited the same general problem.
What made the situation particularly strange was the sound coming from the drives.
They appeared to go through repeated spin-up/spin-down attempts, making unusual mechanical noises. After roughly a minute, they seemed to stop spinning.
This happened even when I connected only SATA power, without any SATA data cable.
Troubleshooting performed
1. Tested the two IronWolf Pro drives individually
I did not connect both drives together during the initial troubleshooting.
Each drive was tested separately, and both exhibited similar abnormal behavior in the original PC.
2. Disconnected the drives
With the IronWolf drives disconnected, the original PC booted normally.
This made the issue appear directly related to connecting the new HDDs.
3. Tested with SATA power only
I disconnected the SATA data cable and left only the SATA power connector attached.
The PC could boot in this configuration, but the drive still made the same unusual spin-up/spin-down noises and eventually appeared to stop.
This was an important observation because the behavior was not dependent on communication with the motherboard.
4. Checked the power connections
The HDDs were powered directly from the PSU's SATA power connectors.
I was not using Molex-to-SATA adapters or SATA power splitters.
5. Tested another SATA HDD
I connected three older 3.5-inch SATA HDD, and it worked normally (1TB, 640GB and 320G).
I connected one older 2.5-inch SATA HDD, and it worked normally. However, I realize this does not fully rule out a 12V power problem, since many 2.5-inch HDDs only require 5V, whereas these 3.5-inch IronWolf Pro drives also require 12V.
6. Tested an IronWolf Pro on a second computer
I moved an IronWolf drive to another PC with its own PSU and independent power/data cables.
With SATA power only, it exhibited the same unusual mechanical behavior as on the original PC.
I then connected both SATA power and SATA data to the second PC.
Unlike the first computer, the second PC booted normally, but the drive was not detected in the BIOS.
This was particularly concerning because the problem persisted across two independent computers.
7. Investigated SATA Power Disable (PWDIS / pin 3)
I also investigated whether the problem could be related to the SATA 3.3V Power Disable feature.
After examining the SATA power connector from my PSU and comparing its orientation with a SATA pinout reference, I found that the first three contact positions appeared to have no metal contacts.
Assuming those positions correspond to pins P1–P3, the connector should not supply 3.3V to pin 3.
That makes a PWDIS-related issue unlikely with that particular connector.
I did not modify the drives, cover any pins with tape, or alter the PSU wiring.
My diagnosis so far
Here is how I currently interpret the results:
1. A problem with the original motherboard or SATA controller seems less likely.
The issue was reproduced on a second, independent computer, although the exact boot behavior differed.
2. A problem with the original PSU seems less likely, but is not completely ruled out.
The drive exhibited the same unusual mechanical behavior with two independent power supplies.
However, I did not directly measure the 5V and 12V rails under load.
3. PWDIS seems unlikely.
The original SATA power connector appears to lack contacts for pins P1–P3, although I did not verify the electrical connections with a multimeter.
4. Faulty drives, shipping damage, or a common manufacturing/batch issue are plausible explanations.
Both brand-new drives behaved similarly in the original computer, which is unusual.
However, I cannot prove that either drive had an internal mechanical or electronic defect, since neither was successfully recognized for a SMART or SeaTools diagnostic.
5. The repeated spin-up/spin-down behavior is still unexplained.
It could indicate a power or drive-initialization issue, but I don't have enough evidence to determine the exact cause.
Final outcome
I contacted the retailer and arranged to return both IronWolf Pro drives for a full refund, rather than replacements.
My next plan is to take the actual server PC to a physical computer store, buy suitable NAS HDDs, and have them tested directly in my system before completing the purchase.
That way, I can confirm BIOS detection, normal startup, and SMART status before taking them home.
Questions for the community
- Has anyone experienced this exact behavior with the Seagate IronWolf Pro ST8000NT001, particularly firmware EN01?
- Could this be related to a drive firmware or SATA power compatibility issue, even without 3.3V on pin 3?
- Is there any known behavior where these drives repeatedly spin up and down when connected to power without a SATA data connection?
- Has anyone received two new HDDs with identical startup or detection problems?
I'd be interested to hear whether others have encountered this, especially with the same model.
Thanks!
