Solved ‪The physical disk's sector size is not supported by the storage pool. (0x80E70004)‬

Hi

When I try to create storage space pool I get this error

‪The physical disk's sector size is not supported by the storage pool.
(0x80E70004)‬

Click to expand...

both drives has 512 bytes sectore size, I also tried 4K sectore size but I got same error . what is the problem ?

solved using partition manager to change cluster size to 4K

Hi William,

I have the exact same problem, could you please let me know how you solved it in detail ?

Many thanks!

healthyboy said:

Hi William,

I have the exact same problem, could you please let me know how you solved it in detail ?

Many thanks!

Click to expand...

The OP used the Windows 11 Partition Manager to change the cluster size from what is stated in the post. I have found it easier to use MiniTool Partition Wizard for this type of disk management. You can visit the sites below to download their free software and the instructions for changing cluster size. You can also wait for the OP to reply to your post and follow the instructions s/he used.

Yes I used NIUBI Partition Editor Free Edition

Many thanks to you both :)

healthyboy said:

Many thanks to you both :)

Click to expand...

Thanks for the reply, glad you were able to solve the problem.

I'm having the same challenge. I have 4 identical hard drives. I added three into a pool successfully, and then later tried to add the fourth, but received the same error. Here's the data on the two drives (the first is the storage pool, and the second is disk I want to add)
C:\Windows\System32>fsutil fsinfo sectorInfo D:
LogicalBytesPerSector : 4096
PhysicalBytesPerSectorForAtomicity : 4096
PhysicalBytesPerSectorForPerformance : 4096
FileSystemEffectivePhysicalBytesPerSectorForAtomicity : 4096
Device Alignment : Aligned (0x000)
Partition alignment on device : Aligned (0x000)
Performs Normal Seeks
Trim Supported
Not DAX capable
Is Thinly-Provisioned, SlabSize : 536,870,912 bytes (512.0 MB)

C:\Windows\System32>fsutil fsinfo sectorInfo z:
LogicalBytesPerSector : 512
PhysicalBytesPerSectorForAtomicity : 4096
PhysicalBytesPerSectorForPerformance : 4096
FileSystemEffectivePhysicalBytesPerSectorForAtomicity : 4096
Device Alignment : Aligned (0x000)
Partition alignment on device : Aligned (0x000)
Performs Normal Seeks
Trim Not Supported
Not DAX capable
Not Thinly-Provisioned

The storage pool claims to have 4096 LogicalBytesPerSector. If it's made up of disks with 512, how is this possible?

I've tried formatting the drive to 4096 cluster sizes with windows and MiniTool, but the same error occurs. Any ideas on how to fix this?

I was able to add it. I formatted the 4th drive with a partition with 4096 cluster sizes, then deleted that partition and restarted Windows. After booting up, I was able to add the unpartitioned drive to the storage spaces. Now, the storage space drive information is:

LogicalBytesPerSector : 4096
PhysicalBytesPerSectorForAtomicity : 4096
PhysicalBytesPerSectorForPerformance : 4096
FileSystemEffectivePhysicalBytesPerSectorForAtomicity : 4096
Device Alignment : Aligned (0x000)
Partition alignment on device : Aligned (0x000)
Performs Normal Seeks
Trim Supported
Not DAX capable
Is Thinly-Provisioned, SlabSize : 536,870,912 bytes (512.0 MB)


I still don't understand how disks with 512 logical bytes per sector become 4096 LogicalBytesPerSector when they are added into the storage space, but at least it's working.

miserton said:

I still don't understand how disks with 512 logical bytes per sector become 4096 LogicalBytesPerSector when they are added into the storage space, but at least it's working.

Click to expand...

I'm having the same problem as everyone else, and given that this is the only search result that hits for error 0x80E70004, here are the steps I used to fix this, using both NIUBI Partition Editor Free Edition and Windows Disk Management:

1: In NIUBI, right click on the disk you want to add, delete all partitions, apply.
2: In diskmgmt.msc, create a NFTS partition with 4096 cluster size
3: In NIUBI, delete the partition you just created
4: Reboot
5: Open storage spaces and add the disk

I don't know why this tricks storage spaces into thinking that the disk's "sector size" is 4k, but whatever, it "works"

I had similar issue.

The solution seems to reside into the reboot.

I simply deleted partition of the disks that I wanted to create a pool on.
Then reboot, then it works!

So there must be a cache in the OS which prevent this to be easier, still, no new software to install, simply the windows 11 'manage' software to delete the partition, a reboot, and that's it.

I have a bunch of old disk mounted on a USB rack, all are 512 sector logical and physical.
Of course Storage Space refuses to mount them with the infamous error 0x80E70004.
But guess what ? It is a false error message. It was not about sector size at all.
It was about the CanPool bit which was set to False for some reason. I set it to True by Resetting the disks.
You'll have to run a PowerShell in administrator and type :

So there must be a cache in the OS which prevent this to be easier, still, no new software to install, simply the windows 11 'manage' software to delete the partition, a reboot, and that's it.

Click to expand...

and

But guess what ? It is a false error message. It was not about sector size at all.
It was about the CanPool bit which was set to False for some reason. I set it to True by Resetting the disks.
You'll have to run a PowerShell in administrator and type :
Code:

Powershell:

Get-PhysicalDisk
Get-PhysicalDisk | Select FriendlyName, UniqueId
Reset-PhysicalDisk -UniqueId "your_id"

Click to expand...

To confirm, it is the CanPool flag:



Use the same original UniqueId value in place of "your id" in the commands.

Afterwards Storage Spaces happily created my pool without complaint.

Thank you very much for getting to the bottom of this!