System won't POST when a specific HDD is plugged in

[snowfox99]

Got a bit of a bizarre one for ya, I have four Seagate Constellation 4TB drives that were part of a RAIDZ array in a server that just recently died. I put together a temporary system with an old FX8320 and MSI 970 Gaming board just to get the array going again and access its data.

 

One of the drives *really* doesn't seem to like this particular motherboard. With the problem drive plugged in, the system will power on, turn on the display, but only output a black screen with POST code A2 in the corner. According to Google that's a drive detection error, which nearly made me shit myself at first cause I thought one of my drives was dead.

 

However, the problem drive worked fine in the HP server, and as a troubleshooting step I plugged it into my main PC and it booted fine, Windows detected the drive and CrystalDiskInfo reported it as healthy.

 

The FX board posts fine with all three other drives, but absolutely will not get past A2 with that drive connected, even if it's the only storage device plugged in.

 

Any ideas?

[TylerD321]

Have you tried using different sata cable in that computer or a different port?

[snowfox99]

1 minute ago, TylerD321 said:

Have you tried using different sata cable in that computer or a different port?

Yep, swapped around ports and cables, pulled the cable off another drive that was detected fine, and as soon as I boot with it plugged into the problem drive, same issue.

[snowfox99]

UPDATE: I'm an idiot, I fixed it, hopefully no one saw this post.

[TylerD321]

8 minutes ago, snowfox99 said:

EDIT: I'm an idiot, hopefully no one saw this post.

Evidently 38 people have seen this so far!! I’m curious what the issue was though.

[snowfox99]

4 minutes ago, TylerD321 said:

Evidently 38 people have seen this so far!! I’m curious what the issue was though.

I looked at the BIOS update changelog for that MSI motherboard, and the most recent revision mentioned something about "fixed SATA definitions". Flashed that and I was good to go. Still odd that one specific drive tripped it up when three other identical ones didn't, but, whatever, I'm just happy my data is safe.

[Blqckqut]

1 hour ago, TylerD321 said:

Evidently 38 people have seen this so far!

how did you see?