Home Server

Microsoft Windows home server - 10 clien...
June 4, 2010 at 16:12:49
Specs: WHS
I've got a problem with WHS not "balancing" the drives out. My "system" drive [not C:] is at 99% and I have three other drives of similar size (1.5TB) that are 60% full.

I've tried both the "Migrate.cmd" batch file and the "Drive Balancer.exe" file, with no joy. I've taken files off of the pooled "D:" drive and put them on another box, with no joy. The non-system drives went down from 70% to 60% (+ or -) as I pulled files off, but there didn't seem to be any "pattern" as to which directories were on which drive. Taking 10G to 12G off at a time, I could see where the 2nd, 3rd and 4th drives were being affected, but nothing I did ever moved the needle on the system drive.

Is there a way to see which files DE "thinks" are on the system drive? The two common aforementioned solutions just keep saying that the system drive is full. FYI, reinstalling is not a go-to solution.

See More: Home Server

Report •

June 9, 2010 at 00:34:16
I don't understand what the purpose is... what are you trying to acheive?

Report •

June 9, 2010 at 16:06:42
"I've got a problem with WHS not "balancing" the drives out."

Report •

June 14, 2010 at 05:52:47
I can read, but I still don't understand what you mean by "balancing the drives out". Maybe it's just me though, anyone else care to take a shot at this?

Report •

Related Solutions

June 18, 2010 at 06:12:14
The system drive, C:, should not be part of the pooled drives. You shouldn't be storing data on it.

Report •

June 18, 2010 at 08:15:40
do a seach on balancer.exe and then you will understand what 24HG_Hoop is asking about.

Report •

June 18, 2010 at 18:08:05
George - honestly not trying to be condescending, but the second sentence starts "...My "system" drive [not C:] is at 99%..."

Thanks for looking anyway. I've spent countless hours on this issue, so I'm probably just going to migrate everything off, then kick WHS to the curb.

Report •

June 18, 2010 at 18:27:25
"My "system" drive [not C:]"

That'a a conundrum.

In MS speak "boot drive' is where ntldr and boot.ini reside. "System" is where the OS is located. They can be on the same partition, or not.

If this is where the OS resides then GeorgeMcQ is correct and this drive should not be part of the pool.

Conversely you could undo the pool, after you backup, as it exists now and make the three drives in a pool and then put back your data. See if it balances.

Update: have you checked on this thread concerning the recommendations, one of which is clear the log files?


Report •

June 18, 2010 at 19:13:39
In MS Win Home Server, "system" is actually a mandatory 20Gig partition carved out of the drive that also houses a partion which IS in the pool ("D:") The entire drive shows up as "Disk 0 - (System)"; however, there is NO data on the 20Gig partition. Further, there is no way to stop the balance of the drive [what is the conventional D: partition in regular Win systems] from being used in the pool.

My intention was to forgoe that specific full-circle discussion by highlighting that I was NOT talking about the system drive [C:], which is 42% full with JUST the OS and two or three add-ins. There actually IS a method to the madness.

Checked the link provided - I don't have much at all in the temp folders (if anything), and I've tried the other options they suggested. One guy had a very similar problem, but found that "Wuala" (whatever that is) was the culprit. I don't have that. I can't run drive balancer - it says there's too much (99%) on that first partitioned drive to let DB work. SOOooooo.... Asking the same question again (sorry) is there a way to get into the OS/registry/folder structure/whatever and manually change the "markers" [little bit of text file that says XYZ file is stored on ABC drive] so that fewer of them think ABC is that full partition?

Report •

Ask Question