Ignoring drive Z:\ Unable to get volume information (HRESULT3)

Question

error 1 - HTMD Forum - Welcome to the world of Device Management! This is community build by Device Management Admins for Device Management Admins❤️ Ask your questions!! We are here to help you! - Ignoring drive Z: Unable to get volume information (HRESULT3) reg1 - HTMD Forum - Welcome to the world of Device Management! This is community build by Device Management Admins for Device Management Admins❤️ Ask your questions!! We are here to help you! - Ignoring drive Z: Unable to get volume information (HRESULT3) reg2 - HTMD Forum - Welcome to the world of Device Management! This is community build by Device Management Admins for Device Management Admins❤️ Ask your questions!! We are here to help you! - Ignoring drive Z: Unable to get volume information (HRESULT3)

Ignoring drive Z:\ Unable to get volume information (HRESULT3). How to fix this?

solved 0
Ebinesar1981 2020-06-28T13:28:07+05:30 3 Answers 607 views Beginner
0

Answers ( 3 )

  2. Ebinesar1981
    0
    2020-06-28T14:26:38+05:30
    Reply

    There is no such Z drive for my DP server. C drive for OS and E drive for content lib.

    My DP server log

    smsdpprov.log

    [26C][Sun 06/28/2020 05:53:33]:Content ‘016aadd8-5fd6-4c81-9f7c-3af4310151a4’ for package ‘P01002A8’ has been added to content library successfully
    [26C][Sun 06/28/2020 05:53:33]:Ignoring drive Z:\. Unable to get volume information (HRESULT 3).
    [26C][Sun 06/28/2020 05:53:33]:Ignoring drive Z:\. Unable to get volume information (HRESULT 3).
    [26C][Sun 06/28/2020 05:53:34]:Ignoring drive Z:\. Unable to get volume information (HRESULT 3).

    • Deepak Rai
      0
      2020-07-06T23:21:21+05:30
      Reply

      The screenshots are not clear enough to read out the logs. So if you can share it here please. https://snipboard.io/

      I bet you would have already tried this but taking my chances.

      You can correct this by updating the following registry keys on your DP.

      HKEY_LOCAL_MACHINE\software\microsoft\sms\dp
      ContentLibraryPath REG_SZ E:\SCCMContentLib
      ContentLibUsableDrives REG_SZ E:\,D:\,E:\
      UsablePackageShareDrives REG_SZ E:\,D:\,E:\

      LOG: Ignoring drive D:\. Unable to get volume information (HRESULT 3). SMS_PACKAGE_TRANSFER_MANAGER

      Remove the bogus drive letter from COntentLibUsableDrives and UsablePackageShareDrives. You may need to restart the DistMgr/PkgTransferMgr components.

      BTW It was marked as BUG.

      As this appears to be a bug report, please send a frown through the console or contact support. See https://docs.microsoft.com/en-us/sccm/core/understand/find-help#product-feedback for more information. Thank you!

      additionally.

      When setting up a System Center 2012 Configuration Manager Distribution Point, we come across the Drive Settings page where we can specify the drive settings for the distribution point. You can configure up to two disk drives for the content library and two disk drives for the package share, although System Center 2012 Configuration Manager can use additional drives when the first two reach the configured drive space reserve. The Drive Settings page configures the priority for the disk drives and the amount of free disk space that remains on each disk drive.

      =============

      Drive space reserve (MB) : The value that you configure for this setting determines the amount of free space on a drive before System Center 2012 Configuration Manager chooses a different drive and continues the copy process to that drive. Content files can span multiple drives.

      Best answer
  4. Anoop C Nair
    0
    2020-06-28T13:57:05+05:30
    Reply

    Are you able to access z drive from primary server using system account ?

Leave an answer

Sorry, you do not have permission to answer to this question .