Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
WHS not showing correct Total Size for drives RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    I just had to redo my home server due to the installation corrupting or something, so I took this opportunity to swap out the 750 gig main drive that came with the system with a 1 terrabyte (TB) one and did a factory reset.  It installed just fine and everything is working.  Except...

    I have been rebuilding the system by copying files off of the old drives, then adding them back in.    I'm doing this by hooking the drive up via USB with an adapter, remote desktop into the server, and just do a copy from the original drive to the proper shared folders under D:\SHARES.

    I just added another 1 TB drive to the system.  Everything went great, and WHS Console now shows both drives as healthy, and with 931.51 GB each.  So I started to copy some more files (in the same way) and during the copy, it suddenly told me I was out of disk space?

    A check of WHS Console, under the server storage pie chart, shows 610 GB in shared folders, 132 GB in system, 4.2 GB in PC backups, and 1.1TB free.  Both drives are still healthy.  However, when I look at the D drive in file explorer, I see that "DATA (D:)" has 1.08 TB in free space, but only 911 GB Total Size?

    Why isn't it reporting the correct total size of my drives?  I can't copy anything now because it thinks the drives are out of space.

    Is there any way to figure out what is wrong, or to try to "reset" this to get it to show the actual storage space?

    Thanks!
    Wednesday, August 19, 2009 5:52 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    This is a cosmetic bug, which has been introduced with a solution, which did offer Vista clients the full storage size.
    Before it was so, that only the free space on drive D: on the server was presented - and Vista clients rejected to copy anything, if the selected amount of files was more than the free space on server drive D:.
    Since now the total size can be larger than drive D:, Explorer is somewhat irritated. Since that is part of the Windows code, which is not in the hands of the Windows Home Server team, getting this fixed seems to be rather difficult.

    Best greetings from Germany
    Olaf
    • Proposed as answer by kariya21Moderator Thursday, August 20, 2009 1:17 AM
    • Marked as answer by PacerDawn Thursday, August 20, 2009 3:44 AM
    Wednesday, August 19, 2009 8:04 PM
    Moderator

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    This is a cosmetic bug, which has been introduced with a solution, which did offer Vista clients the full storage size.
    Before it was so, that only the free space on drive D: on the server was presented - and Vista clients rejected to copy anything, if the selected amount of files was more than the free space on server drive D:.
    Since now the total size can be larger than drive D:, Explorer is somewhat irritated. Since that is part of the Windows code, which is not in the hands of the Windows Home Server team, getting this fixed seems to be rather difficult.

    Best greetings from Germany
    Olaf
    • Proposed as answer by kariya21Moderator Thursday, August 20, 2009 1:17 AM
    • Marked as answer by PacerDawn Thursday, August 20, 2009 3:44 AM
    Wednesday, August 19, 2009 8:04 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    I just had to redo my home server due to the installation corrupting or something, so I took this opportunity to swap out the 750 gig main drive that came with the system with a 1 terrabyte (TB) one and did a factory reset.  It installed just fine and everything is working.  Except...

    I have been rebuilding the system by copying files off of the old drives, then adding them back in.    I'm doing this by hooking the drive up via USB with an adapter, remote desktop into the server, and just do a copy from the original drive to the proper shared folders under D:\SHARES.

    I just added another 1 TB drive to the system.  Everything went great, and WHS Console now shows both drives as healthy, and with 931.51 GB each.  So I started to copy some more files (in the same way) and during the copy, it suddenly told me I was out of disk space?

    A check of WHS Console, under the server storage pie chart, shows 610 GB in shared folders, 132 GB in system, 4.2 GB in PC backups, and 1.1TB free.  Both drives are still healthy.  However, when I look at the D drive in file explorer, I see that "DATA (D:)" has 1.08 TB in free space, but only 911 GB Total Size?

    Why isn't it reporting the correct total size of my drives?  I can't copy anything now because it thinks the drives are out of space.

    Is there any way to figure out what is wrong, or to try to "reset" this to get it to show the actual storage space?

    Thanks!

    Is your server is up-to-date?  If not, you should update it so you get the fix Olaf is describing.  If your server is up-to-date, you may have problems because you copied to D:\shares.  Copying to D:\shares is unsupported (as a matter of fact, logging into the server desktop for any reason is unsupported), not recommended and is probably why you are having issues with free space (because it can cause the exact problem you have now).  My suggestion is to pull your drives out of your server, backup the data on the drives, and do a Factory Reset (which will wipe all drives during the installation process).  Once you do that, copy your data to your server using the UNC path (\\server\[sharename]).  Do not use D:\shares any more.
    Thursday, August 20, 2009 1:14 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Olaf hit it right on the head.  The space free on the primary system DATA partition is what is used to determine how much you can copy at one time, not the space free across all drives.  So, you cannot copy a group of files who's total size is greater than the free space on the primary DATA partition.  Instead, you have to copy bits at a time so as to give the server time to load balance and free up system data partition drive space.  Disappointing, but not game-breaking.

    And, while I have never had problems copying directly to the d:\shares folder before, I will follow your advice and only use the network shares from now on. 

    Thanks so much for the info!
    Thursday, August 20, 2009 3:43 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Olaf hit it right on the head.  The space free on the primary system DATA partition is what is used to determine how much you can copy at one time, not the space free across all drives.  So, you cannot copy a group of files who's total size is greater than the free space on the primary DATA partition.

    That's not true any more.  If your server is up-to-date (which is why I asked if it was), you won't have that problem.  What are the component numbers on your server (Settings button, Resources tab)?

    Instead, you have to copy bits at a time so as to give the server time to load balance and free up system data partition drive space.  Disappointing, but not game-breaking.

    And, while I have never had problems copying directly to the d:\shares folder before, I will follow your advice and only use the network shares from now on. 

    Thanks so much for the info!

    Thursday, August 20, 2009 7:09 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    That's not true any more.  If your server is up-to-date (which is why I asked if it was), you won't have that problem.  What are the component numbers on your server (Settings button, Resources tab)?

    Interesting.  I updated my system until Windows Update showed no more updates so I'm pretty sure I'm caught up, but please let me know if I'm not.  Here's the version info:

    Windows Home Server with Power Pack 2

    Windows Home Server Console: 6.0.2030.2
    Windows Home Server Backup & Restore: 6.0.2030.0
    Windows Home Server Drive Extender: 6.0.2030.0
    Windows Home Server Remote Access: 6.0.2030.0
    Windows Home Server Storage Manager: 6.0.2030.0

    Also, I am copying directly on the Home Server itself from the USB drive via Remote Desktop (over the network would take days if not weeks at the rate it was going when I tried that), and I am using the network paths (from the Shared Folders on Server shortcut) rather than going directly to the D: drive.  Selecting a group of files that totalled over 300 gigs with only 250 gigs available on the system DATA partition still resulted in the not enough disk space to copy error.

    Oh, and I'm using Teracopy as well, so that may be something (perhaps it needs the same fix that windows explorer does?).  But even still, I would expect an application other than windows file explorer that tries to copy files shouldn't get that issue.
    Thursday, August 20, 2009 8:45 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Interesting.  I updated my system until Windows Update showed no more updates so I'm pretty sure I'm caught up, but please let me know if I'm not.  Here's the version info:

    Windows Home Server with Power Pack 2

    Windows Home Server Console: 6.0.2030.2
    Windows Home Server Backup & Restore: 6.0.2030.0
    Windows Home Server Drive Extender: 6.0.2030.0
    Windows Home Server Remote Access: 6.0.2030.0
    Windows Home Server Storage Manager: 6.0.2030.0

    Yep, you're up-to-date.

    Also, I am copying directly on the Home Server itself from the USB drive via Remote Desktop (over the network would take days if not weeks at the rate it was going when I tried that) and I am using the network paths (from the Shared Folders on Server shortcut) rather than going directly to the D: drive.

    OK.  That should work.

    Selecting a group of files that totalled over 300 gigs with only 250 gigs available on the system DATA partition still resulted in the not enough disk space to copy error.

    Oh, and I'm using Teracopy as well, so that may be something (perhaps it needs the same fix that windows explorer does?).  But even still, I would expect an application other than windows file explorer that tries to copy files shouldn't get that issue.
    I know that other users that have used TeraCopy had the same issue as well.  Try using Windows Explorer and see if it works.
    Thursday, August 20, 2009 8:53 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Try using Windows Explorer, or robocopy, or RichCopy, instead of teracopy. Windows Home Server "tricks" the client into seeing the free space in the storage pool as the available space, but it sounds to me like teracopy isn't fooled...
    I'm not on the WHS team, I just post a lot. :)
    Thursday, August 20, 2009 8:58 PM
    Moderator