Were these drive New or were they just advertised as "New"?
I've seen sellers pulling Enterprise drives, cleaning them up, formatting and putting them in vacuum packs and selling "as new"
You didn't mention where you got them from or what Mac you are using to initialize them, both important pieces of information.
One possibility is that your Mac cannot handle 4TB drives.
I just bought three NOS 4 TB HGST drives. They are the expensive “Deskstar 7400” enterprise series. I have an unusual problem with two of them..
As I explain, I’ll refer to just one drive:
The first time installing the drive (in an external bay) I was not able to initialize the main drive itself, (the “physical disk” ) I used the standard mac formats: “Guild Partition Map” and “OSx Extended (journaled) - but I got an error.
But then I WAS able to erase/ initialize the (single) volume, to the full 4 TB.
Was there a mistake here?
Regardless, after successfully initializing the volume, the drive checked fine, and I was able to write huge amounts of data to it, both by dragging, and by using Carbon Copy Cloner. This drive seems fine for maybe 24 hrs, and passed every test. Then suddenly it starts to have problems, like I can’t drag files to or from it. I get a prompt showing Mac Error 50. (I’ve read up on this, but I can only find a solution for getting files off, not for permanently fixing the drive.)
At that point both the main drive, and the (sole) partition fail the Mac’s “Disk Utility” repair diagnostic, and there is no repair possible.
If I power-cycle the Mac, the main drive once again passes Disk Utility, and the partition suddenly can be repaired! During this repair, I get the following prompt:
“Updating boot support partitions as need ….”
This has all happened about FIVE times so far, since I put it into use on Friday.
Although the drive checks out 100% ok in every other way, (using Tech tool Pro, DiskWarrior, SMART readings, etc ) I am really freaking out about this.
So, any ideas?
Additionally, the second drive has an extra problem, which may be fatal:
Besides the above, and even though it also checks out 100% in every other way, I cannot write to it using Carbon Copy Cloner. CCC tells me that there are write errors.
It does this even if I JUST re-initialed it.
Ughh. Is it toast?