Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Well, we brought in reinforcements - in the form of an Asus i9 ROG Strix G Laptop - and, long story short, the drive in question isn't recognized by Win 11 at all. As evidenced by other HDDs we have and subsequent testing, the drive dock is working via both Win 11 and macOS Monterey.

This tells me that the subject WD Ultrastar 16TB HC550 HDD probably has some sort of an internal issue ... at least at this point. I'm still wondering about why macOS' Disk Utility "two-step secure erase" process seemed to be running fine, but I suppose it's possible that manually ending the two-step erase run may have caused an issue ... but I digress.

I'll get back to this thread with what happens after we order and receive a replacement HDD.
 
What is your basis for stating this?

I found this:

  • Mount times become significantly slower (particularly Time Machine drives). Directory traversals become exponentially longer as the directory structures themselves are changed after initial creation. Unfortunately, Apple removed the ability to create HFS+ Encrypted volumes since Big Sur.

  • I bought an External dual-drive with high-end thunderbolt-3 connection, and two high-performance Toshiba 14TB enterprise level drives - and formatted one APFS one HFS+ I must say APFS is horrible on rotational drives. It is not just slow - it causes the whole OS to hang when it becomes suddenly "busy" doing its thing. Any manipulation of the file-systems is extremely slow and cumbersome. The only benefit is the flexibility in creating and moving around multiple volumes (I use it as hot-backup drive for several different Macs). Otherwise - only HFS+
 
  • Like
Reactions: gregmac19
APFS is known to cause excessive defragmentation on platter-based drives.
It also seems to make the drive "thrash". See second bulleted paragraph in the reply above this one...
 
  • Like
Reactions: gregmac19
Thanks for the information, Adora and Fishrrman.

I searched and found other sources that indicate HFS+ is better for HDD. That HFS+ is better than APFS for HDD is a surprise to me, as the documentation for Carbon Copy Cloner 6, which I use, says to choose APFS.
 
greg wrote:
"APFS for HDD is a surprise to me, as the documentation for Carbon Copy Cloner 6, which I use, says to choose APFS"

Time machine requires APFS now, for both SSDs -and- platter-based backup drives.

I will take a GUESS that CCC (also SuperDuper) require it to be compatible with the latest versions of the Mac OS which also require APFS. There might be other reasons as well (that I don't know about)...
 
Thanks for the information, Adora and Fishrrman.

I searched and found other sources that indicate HFS+ is better for HDD. That HFS+ is better than APFS for HDD is a surprise to me, as the documentation for Carbon Copy Cloner 6, which I use, says to choose APFS.

Interesting that they in particular say this given this blog post:

The issue is an interesting but not uncommon one over extended technology cycles. As we transition from one technology to another, what was once an optimization becomes a bottleneck for the next technology. We saw this with tape to disc to solid state.

Optimizing for tape access was critical when seek times were seconds to minutes. People bought 3rd party tools to sort their data. Also less common to put lots of unrelated data on one tape.

With disk drives, "rewinds" are much less of an issue and with more capacity so letting users put every unrelated thing on one filesystem is much more user-friendly. However, the mechanical nature of the devices still means seeking small blocks of data can still dominate data access. Filesystems of times past went to great lengths to keep files' data blocks optimized for long sequential access. Performance differences could be orders of magnitude.

With SSD, the cost of seeks is *almost* neglible. It's still better if data is sequential but not worth going through historical heroics to optimize (e.g. various reordering and reallocation of data, more complex data structures to minimize seeking, etc).

As another example of this, MS implemented a new data sorting algorithm with SQL Server 2016 that was optimized for large memory systems and SSD. However, while the new algorithm is somewhat faster for modern target servers, it is painful to sort datasets larger than the server's memory on HDD. I recall one time I had to keep canceling a query for an analysis I thought would take a few minutes because it didn't come for hours. It was very confusing until I found someone blog post about a flag that would tell MS SQL to revert to the old algorithm.

In any case, I am not sure how much better HFS+ is than APFS on SSD but Apple is clearly going that way and so using HFS+ on SSD seems like a recipe for future conflict. On the other hand, HFS+ is so much better optimized for HDD than APFS that I can't recommend using APFS there even in the short-term (for general use, not counting special cases like Time Machine, etc and there I can't speak either way to whether an HDD with APFS to run Time Machine makes any sense).
 
  • Like
Reactions: HDFan and gregmac19
Well, we brought in reinforcements - in the form of an Asus i9 ROG Strix G Laptop - and, long story short, the drive in question isn't recognized by Win 11 at all. As evidenced by other HDDs we have and subsequent testing, the drive dock is working via both Win 11 and macOS Monterey.

This tells me that the subject WD Ultrastar 16TB HC550 HDD probably has some sort of an internal issue ... at least at this point. I'm still wondering about why macOS' Disk Utility "two-step secure erase" process seemed to be running fine, but I suppose it's possible that manually ending the two-step erase run may have caused an issue ... but I digress.

I'll get back to this thread with what happens after we order and receive a replacement HDD.

Thanks for sharing the updates. Always curious to hear the story through the end.

One other thing I was going to recommend before I read the above news -- during an extended I/O operation like your 2-pass erase, you can monitor with Activity Monitor -> Disk -> Data Write/sec. That will tell you how much the system is writing per second. If the erase was the only thing happening on that machine, you could attribute all of that number to the erase. Then in this case one would expected ~ 250MB/sec based on the specs of that drive. If Activity Monitor was reporting a much lower number in that field you could assume something was going wrong.
 
  • Like
Reactions: gregmac19
I'm not understanding you clearly, rebelo. Are you suggesting that we plug the HDD into a newer Mac machine or are you suggesting that the OS we're using may be too old to recognize a 16TB HDD?
Both are old :) You'd have to test it. It always worked for me on newer machines and newer OS.
 
Interesting that they in particular say this given this blog post:
Thanks for all the detailed advice and information you have provided on this thread, and specifically for the blog post from Bombich! I found it exceptionally helpful!

I think the following from the end of the Bombich post is worth emphasis, and thus I am posting it here:


“Does this mean I should avoid using APFS on my HDDs?

No, let's not throw out the baby with the bath water. APFS has loads of really nice features, like snapshots and volume space sharing. Managing volumes within an APFS container is a dream compared to the older method of preallocating space to specific partitions. It's important to understand why we might expect to see performance differences between the two filesystems and when that might impact your use of the filesystem, but this one performance aspect on its own isn't enough reason to avoid it.”
 
Thanks for all the detailed advice and information you have provided on this thread, and specifically for the blog post from Bombich! I found it exceptionally helpful!

I think the following from the end of the Bombich post is worth emphasis, and thus I am posting it here:


“Does this mean I should avoid using APFS on my HDDs?

No, let's not throw out the baby with the bath water. APFS has loads of really nice features, like snapshots and volume space sharing. Managing volumes within an APFS container is a dream compared to the older method of preallocating space to specific partitions. It's important to understand why we might expect to see performance differences between the two filesystems and when that might impact your use of the filesystem, but this one performance aspect on its own isn't enough reason to avoid it.”

You got me there -- I didn't read that article all the way through. I was just looking for a credible 3rd party site to explain the situation...

I am surprised he drew that conclusion at the end. I agree APFS container management and such is nicer but just can't recommend it for HDD. Many others on MR will say the same thing ("HDD killer" is the term they often use -- I don't go that far in that I believe even 100% random I/O shouldn't kill an otherwise solid HDD). The issue is two fold -- on HDD random I/O is literally two orders of magnitude slower than sequential, and HDD are already slow in modern computing terms. HDD seek latencies are painful. Even a few extra random I/O on an HDD will be noticable to the user. I just find the experience with heavy random I/O workloads on an HDD too painful. Using a filesystem that doesn't try to minimize seeks on an HDD just seems like asking to be frustrated.

The issue is different with SSD which are so fast these days that often not the bottleneck for what most people do. When I finally switched my primary data drive to SSD some years ago, I couldn't find a Thunderbolt enclosure I liked so I bought a relatively cheap USB3 enclosure with plans to switch once the next generation of Thunderbolt enclosures came out. Now I could probably get >2x speedup with a quick switch of the enclosure but I haven't bothered because there just isn't that much upside for what I do relative to my time. Back in the HDD era, I would have literally spent an entire day tweaking my computer if I thought I could get a 2x speedup.

A lot of people on this forum won't recommend HDD at all these days. I also don't go that far but I do think the number of use cases for which they are optimal continues to narrow. I still keep a few around and happy to use them for select niche uses but don't recommend them to most people outside of specific use cases. The issue often isn't that they aren't "good enough" for the intended purpose but that modern software isn't being optimized for them.

Back to your situation -- exFAT is most practical for seamless back and forth between macOS and Windows. It's not optimal on either but it should be fine on a non-boot/system drive for most purposes. If Mac-only is okay, I would use HFS+ on an HDD unless I needed specific APFS features (e.g. Time Machine backup with recent versions of macOS). APFS will work but it won't be optimal to start and may become painfully slow over time depending on how it is used.

In any case if the system won't let you create your desired filesystem on a new drive without a full erase (or worse a 2-pass erase) something is off. Post the details here and we'll see if we can help.
 
We just took delivery of a WD DC HC550 Ultrastar 16TB HDD - and it is, by far, the largest storage drive we've ever owned. We occasionally need to work with PC machines, so I decided that exFAT and GUID were the best way to go with formatting this new drive, but the problem is that the Disk Utility program refused to format the drive via the fastest setting. Even when I worked with a WD Tech Support rep on this, the ultimate answer was that they would replace the drive. In other words, they didn't have an answer for us.

The machine we're employing for the format task is a mid-2015 MBP15 running via Monterey (12.7.5). Having had no luck with WD tech support, I decided to try the 2-pass setting in Disk Utility and it seems to be working...but it's coming up on 24 hours of run time as I type this. I know that I'm asking about a large storage device, but this still begs some questions:

What are Mac people using to format their large storage devices - in a single pass?

Has anyone been in a similar situation with Disk Utility - and how long did it take to format your large drive?


Cheers for your thoughts on this.
I always encrypt my large drives. Hence, any quick format will do just fine (no wipe is necessary since the previous data is encrypted).

PS: APFS is the only native option for encrypted drives since Big Sur. Rotational or not.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.