I have over 60 8TB, 4TB and 3TB drives. Data on theses spans 5+ years.
I have several docking stations, each from a different supplier--2, 4 and 8 bays.
Most of my drives were purchased as self contained, backup units like Seagate and WD.
My work involves downloading various file types to the drives.
For downloading, I keep them in their enclosure. When I'm done, I connect them to a dedicated desktop or laptop, whichever is available and use 2 USB3 ports to copy to a blank drive.
I always used docking stations but this year, I have a desk space limitation. I'm using the circuit boards from the Seagate and WD hard drive enclosures.
I don't use disk duplicators because my live downloaded disks are always fragmented. Since every downloaded drive requires a final backup, copying does both disk defrag and backup at the same time.
I first noticed the problem (title above) 5 years ago. I've run into this with W7 and W10 and a combination of the two. I've seen it with different docking stations and yesterday, I saw it while using circuit boards (as explained above).
For an 8TB drive, over a period of 2 months, I will download, delete, change, modify and download more files until the 8TB is full. These past 2 months I've used a StarTech.com 4 port docking station. I've used a Seagate 8TB drive. Last night, my 8TB was full. I took it to my copy station. My Acer laptop wasn't doing anything last night so I used it. It's W10. (W10 isn't an issue because as I said above, I've seen this over 5 years and it's not OS related). Connected the 8TB to the circuit board from the enclosure and fired it up. No drive visible. A look at hard disk manager showed the drive as having 2 partitions, one 20GB!!! This specific description isn't meaningful because this issue (title above) has presented it itself in at least (counting last night) 4 different ways. The bottom line is that the drive formatted on one docking stations isn't readable on another docking station. I went back to my StarTech.com to make sure I didn't damage the drive when I removed it. StarTech.com read it perfectly. So I swapped the circuit board connected to the Acer for an Allertech 2 bay drive and everything was fine. Just finishing up the copy now.
2 days ago, I did the exact same thing with a different 8TB downloaded drive using the circuit boards with the same (mfgr) 8TB drives and there was no issue.
The facts that don't change over the past 5 years are: it happens with different disk mfgrs; different docking stations (including hard drive enclosures); different OS's; different size HDD.
After 5 years, 20+ HDD backup copies and several new docking stations/circuit boards, the problem pops up every now and then.
I'm wondering if it happens a lot more and people just reformat their drives, thinking they made a mistake.
I stupidly did that the first time too, all 8TB. But when I was done, for some reason, I was suspicious so I put the drive in the docking station I used in the first place and it wouldn't read it. In other words, a drive formatted in one docking station, in repeated tests back and forth, could not be read in another.
Last piece of information.. Drives are always formatted 64KB/NTFS/GPT.
Hoping someone else has noticed this too.
I have several docking stations, each from a different supplier--2, 4 and 8 bays.
Most of my drives were purchased as self contained, backup units like Seagate and WD.
My work involves downloading various file types to the drives.
For downloading, I keep them in their enclosure. When I'm done, I connect them to a dedicated desktop or laptop, whichever is available and use 2 USB3 ports to copy to a blank drive.
I always used docking stations but this year, I have a desk space limitation. I'm using the circuit boards from the Seagate and WD hard drive enclosures.
I don't use disk duplicators because my live downloaded disks are always fragmented. Since every downloaded drive requires a final backup, copying does both disk defrag and backup at the same time.
I first noticed the problem (title above) 5 years ago. I've run into this with W7 and W10 and a combination of the two. I've seen it with different docking stations and yesterday, I saw it while using circuit boards (as explained above).
For an 8TB drive, over a period of 2 months, I will download, delete, change, modify and download more files until the 8TB is full. These past 2 months I've used a StarTech.com 4 port docking station. I've used a Seagate 8TB drive. Last night, my 8TB was full. I took it to my copy station. My Acer laptop wasn't doing anything last night so I used it. It's W10. (W10 isn't an issue because as I said above, I've seen this over 5 years and it's not OS related). Connected the 8TB to the circuit board from the enclosure and fired it up. No drive visible. A look at hard disk manager showed the drive as having 2 partitions, one 20GB!!! This specific description isn't meaningful because this issue (title above) has presented it itself in at least (counting last night) 4 different ways. The bottom line is that the drive formatted on one docking stations isn't readable on another docking station. I went back to my StarTech.com to make sure I didn't damage the drive when I removed it. StarTech.com read it perfectly. So I swapped the circuit board connected to the Acer for an Allertech 2 bay drive and everything was fine. Just finishing up the copy now.
2 days ago, I did the exact same thing with a different 8TB downloaded drive using the circuit boards with the same (mfgr) 8TB drives and there was no issue.
The facts that don't change over the past 5 years are: it happens with different disk mfgrs; different docking stations (including hard drive enclosures); different OS's; different size HDD.
After 5 years, 20+ HDD backup copies and several new docking stations/circuit boards, the problem pops up every now and then.
I'm wondering if it happens a lot more and people just reformat their drives, thinking they made a mistake.
I stupidly did that the first time too, all 8TB. But when I was done, for some reason, I was suspicious so I put the drive in the docking station I used in the first place and it wouldn't read it. In other words, a drive formatted in one docking station, in repeated tests back and forth, could not be read in another.
Last piece of information.. Drives are always formatted 64KB/NTFS/GPT.
Hoping someone else has noticed this too.
Last edited by a moderator:
My Computer
At a glance
w7 Professional SP1, 64bitAMD A8 PRO-7600B R7 10 COMPUTE CORES 4C+6G 3....8GBINTEGRATED
- Computer type
- PC/Desktop
- Computer Manufacturer/Model Number
- HP
- OS
- w7 Professional SP1, 64bit
- CPU
- AMD A8 PRO-7600B R7 10 COMPUTE CORES 4C+6G 3.10GHZ
- Motherboard
- HP
- Memory
- 8GB
- Graphics Card(s)
- INTEGRATED
- Hard Drives
- MULTIPLE
- Antivirus
- AVAST
- Browser
- CHROME