Hi,
I am getting the drive balancer error shown in the attachment. My WHS is up to date with all patches/service packs. I used to be able to run drive balancer with no issues (v1.05 and v1.06). Now it's a problem. If I run drive balancer without including "D" , it works. Any help would be greatly appreciated.
Welcome to We Got Served Forums
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. If you already have an account, login here - otherwise create an account for free today!
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. If you already have an account, login here - otherwise create an account for free today!
Drive Balancer Error V1.06
Started by
mike751
, Oct 23 2010 04:56 PM
#1
Posted 23 October 2010 - 04:56 PM
#2
Posted 25 October 2010 - 10:08 PM
Hi,
I am getting the drive balancer error shown in the attachment. My WHS is up to date with all patches/service packs. I used to be able to run drive balancer with no issues (v1.05 and v1.06). Now it's a problem. If I run drive balancer without including "D" , it works. Any help would be greatly appreciated.
Sorry for the long delay...
Here's what is going on. You want to include the D drive in your balancing effort and it is only the borderline of having enough free space to do so. I've put in extra safe guards in 1.05 and 1.06 so people won't "hurt" their system disks. I never suggest using the system disk as part of the balancing effort unless it's a large disk (greater than 160GB). My suggestion is to actually try and clear off the D drive first, and then don't ever include it in the balancing effort moving forward.
Sorry I don't have a better answer, but the solution is what you are already doing, but at least you now know why.
-Brian
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users





Back to top







