I recently bought and started using DrivePool on my home media server. I am running a fresh install of Windows Server 2019 Datacenter. Since I installed DrivePool, I am no longer able to use the Deduplication role, as the service won't start. Removing DrivePool and rebooting allows the Deduplication service to start again successfully. To be clear, I am not using Deduplication in conjunction with any drives that are part of my pool, but it is used on another volume to provide massive space savings on File History and even image backups of my PCs. So, not having Deduplication working is a pretty big issue!
The Dedupe service seems to be failing with the following information in the Event Log:
Has anyone else seen this issue? Could one of the developers let me know if this is a known problem? This does *not* happen on Windows Server 2016, so I assume something has changed in Windows Server 2019 such that the Dedupe service is looking for something from the pool drive that DrivePool isn't responding correctly on.
I'm using v 2.2.3.950 BETA as this specifically calls out Windows Server 2019 compatibility. If there's a different version to try, please let me know!
Thanks,
- TheBigMan
Updated 07/05/2019 with specific error information from the Event Log
Question
TheBigMan
Hi,
I recently bought and started using DrivePool on my home media server. I am running a fresh install of Windows Server 2019 Datacenter. Since I installed DrivePool, I am no longer able to use the Deduplication role, as the service won't start. Removing DrivePool and rebooting allows the Deduplication service to start again successfully. To be clear, I am not using Deduplication in conjunction with any drives that are part of my pool, but it is used on another volume to provide massive space savings on File History and even image backups of my PCs. So, not having Deduplication working is a pretty big issue!
The Dedupe service seems to be failing with the following information in the Event Log:
===
Data Deduplication error: Unexpected error.
Operation:
Starting File Server Deduplication Service.
Error-specific details:
Error: DeviceIoControl (FSCTL_GET_NTFS_VOLUME_DATA), 0x80070001, Incorrect function.
===
Has anyone else seen this issue? Could one of the developers let me know if this is a known problem? This does *not* happen on Windows Server 2016, so I assume something has changed in Windows Server 2019 such that the Dedupe service is looking for something from the pool drive that DrivePool isn't responding correctly on.
I'm using v 2.2.3.950 BETA as this specifically calls out Windows Server 2019 compatibility. If there's a different version to try, please let me know!
Thanks,
- TheBigMan
Updated 07/05/2019 with specific error information from the Event Log
Link to comment
Share on other sites
16 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.