Console Keeps Spinning up USB HDD When Asleep for No Reason

I have been enjoying my XBox One X for a few years now, and don't feel as though there's any reason to get a 'Series' console.

I decided to upgrade my storage pool a few months ago by purchasing a new USB HDD.
I have had a 4TB Seagate Backup Plus Portable permanently connected to my console for a while now, and haven't noticed any issues what so ever.
The only reason I wanted to replace it is to increase the storage capacity.

However, as I intended to leave the new drive connected to my console indefinitely; I opted to purchase a certified 'gaming' drive... even though the device itself is probably no different than any other USB storage device of the same capacity and USB version.

I opted to get the "WD_BLACK P10 6TB Game Drive for Xbox".

Mostly because the price for this drive was actually less than any other 6TB USB HDD option.
But, felt confident that because all of the marketing for that product is targeting naïve gamers with little to no technical understanding, that there must be at least some 'gaming' specific aspects to the drive's functionality.
However, I remained sceptical on that assumption to a certain degree.

As a USB external storage device for my console; it is perfectly fine while in use; loading games at an acceptable speed and although not as quiet as the 4TB option I had previously had connected, still not an intrusive amount of sound coming from it while it is powered on.

That is until I put my console to sleep...

Every few seconds... 3 maybe 4... the drive spins up, as though being woken up by the host device.
It doesn't remain spinning though, definitely not long enough for the console to access any data.
I'm familiar with USB HDDs and know that from a completely rest state they can take around 10 to 15 seconds before the host device can read/write any data... most devices won't even present the drive in any menus until it is fully started up and at a stable spindle speed.

However, for the amount of time my XBox One X starts this HDD up for; there is no way it is doing anything at all.
The console is just sending a 'wake-up' signal to the drive as pulse, rather than starting it up to access any data.
I can confirm this by the fact that the drive doesn't actually reach full spindle speed before it sounds like it goes back to it's rest state.

As I mentioned this is every 3 to 4 seconds while the console is in 'sleep' mode.

If I change the consoles settings to 'Shutdown (energy saving)' the drive shuts off entirely... even though the USB ports are still powered, as evident by the other devices I have connected such as my controller battery charger.
This indicates to me that the 'always on' power state of the USB port the drive is connected isn't the cause of the drive not remaining 'off' during the consoles 'Sleep' mode, as if it were any active powered USB connection would make it behave in the same manner.
The console itself is actively triggering the drive to wake up, only to not do anything further, leading the drive to quickly go back into a dormant state.

The sound isn't entirely irritating to me, but my concern is the unnecessary wear this is putting on the drive.
My understanding of electric motors of any design is that they occur the most amount of wear during the initial power up state.

I have tried using the 'Shutdown' option.
Which does stop the HDD from spinning up every few seconds needlessly.
However, I am accustom to the faster booting times of the 'Sleep' option, plus the ability to turn my console on remotely and use 'remote play' while I am away from home.
Without the use of 'Sleep' mode the XBox One X is actually incredibly slow at starting up fully... a 'first-world problem' indeed, but still one that can be negated by the consoles own settings.

For the record; I am sure there is nothing wrong with the 'WD_BLACK P10 6TB Game Drive for Xbox' as I purchased it brand new and sealed.
It is also not affected by a powered USB connection, and does not persist the rhythmic 'start-up' cycle if the attached device isn't actively accessing it.

This is something the XBox console itself is doing.
Every few seconds my console is telling the drive to wake up, but not accessing any data what so ever.
As I said, the wake signal seems to be every 3 or 4 seconds and is only long enough to cause the drive to spin up for less time than it would take to bring it up to full-speed.

I am unsure if the 4TB Seagate Backup Plus Portable acted in the same way, but I don't recall ever hearing that drive randomly starting up every few seconds.

I purchased this 'WD_BLACK P10 6TB Game Drive for Xbox' under the impression that it would be the perfect companion and accessory for my XBox One X console.
However, it does concern me that it is not behaving as though it is designed to be used in the manner which it is marketed to do so.

It is worth mentioning that I have tried changing the "When console is off, turn off storage" setting... which seems to do absolutely nothing what so ever, as the drive spins up every few seconds while the console is in 'Sleep' mode regardless of weather this setting is on or off.

My conclusion is that there is something in the XBox's system software that is causing this issue, and it is NOT the drive.
I exclaimed that because I know whoever from Microsoft replies to this is going to try and 'pass-the-buck' baling Western Digital for the issue.
However, as I stated very clearly above; the issue is not the drive being prevented from resting due to an active power connection, as it remains inactive when connected to a powered USB port without the host device actively accessing it.
The issue is without any doubt in my mind the console sending a regular 'wake-up' signal for absolutely no reason to the drive.

Microsoft have certified this product as compatible with the XBox family of consoles, and given Western Digital the rights to even put XBox branding on the product.
However, there is something amiss in the actual connectivity between the two devices... something that should not be there and assumedly would have been caught during development and testing of the product.

I would politely ask that if you don't have anything contractive to add to this, then please don't waste your time commenting.
I have tried several troubleshooting steps to identify the cause of this issue, and all investigation leads to the console itself being at fault.
However, that fault is not a malfunction or defect, but rather something in the consoles software that is creating the issue.
Something that assumedly should be fixed with the aforementioned "When console is off, turn off storage" setting... which seemingly does absolutely nothing.

I am also sure I am not alone in experiencing this issue, as I have found a few instances of others asking for help resolving a similar problem... only to be advised the usual generic options that never work and are more like meaningless token catchphrases of tech-support than genuine resolutions.

And, yes... I did try turning it off and on again.

:)