locked
Disk allocation seems impossible, how to fix? RRS feed

  • Question

  • Hello everybody,

    I am relatively new in the WHS world and I am getting frustrated trying to get my drives working correctly.

    What am I running?
    Hardware: Asus M4N78-VM, AMD Athlon XII 250, 4Gb, 80Gb WD primary (IDE), 2 * WB 1TB (SATA) disks (and 1 temporary dvd-drive for the install)
    Software: WHS SP3 32-bit

    What am I trying to archieve?
    I want the OS to be on the smallest drive and the data mirrored (Raid 1) on the 2 large disks. (I ran a normal 2003 server before and this was perfectly possible).

    Problem:
    WHS allocates 20Gb for the OS (C:) and 60Gb (D:) for data. I can then add the first WD 1TB disk for the storage pool and the second for backup purposes. So far no problem. Then I start filling the D: disk with data, when it reaches 60Gb I cannot add any more data. What happened to the first 1Tb disk?

    In WHS Console the 'computeroverview' tells me that the D: disk has 3666% available.

    What I ultimately want is no data on the small disk (only the OS), and all data on the large disks. How can I achieve this? I reinstalled already as the system became heavily unstable from allocating disks with regular 'diskmanagement' as I find the WHS-Console somewhat limited in the possibilities but that might just be my limited experience.

    The question then is: how to get the disks allocated so the 80Gb is the OS-disk, and the 2 1Tb disks storage/backup.

    Thanks in advance,

    Peter

    PS: my machine is mainly used for streaming movies to a Popcornhour NMT and a HTPC. Therefore I want all data on the fast SATA-disks.
    Monday, December 21, 2009 6:35 PM

Answers

  • There is no supported way to achieve what you want; Windows Home Server setup uses a multi-stage script that is run automatically to install and update everything appropriately. It may be possible if you interrupt the scripted setup routines at the right point, however doing so is unsupported and will probably severely impact any server recovery scenario (e.g. a system disk failure, or OS corruption).

    In general, you should not attempt to manage storage on your own. Allow Windows Home Server to do so; install drives and add them to the storage pool using the console rather than attempting to manage them yourself in the Disk Management MMC snap-in. There is a warning that displays every time you log in to your server desktop, rather than through the console, which tells you that anything you do is potentially risky. Take that warning to heart; there are tools available that can cause significant server issues, right up to complete data loss.


    I'm not on the WHS team, I just post a lot. :)
    • Marked as answer by Peter-WHS-Noob Tuesday, December 22, 2009 7:12 PM
    Monday, December 21, 2009 8:46 PM
    Moderator
  • From what I see, your server seems not to be updated. Missing at least two Power Packs, which changed some stuff how the disks are presented. Click the Update button in the console under Settings/General as often, as still new updates are offered. What are the version numbers shown in the console in Settings/Ressources?

    Besides that - copying stuff to d:\shares is always good for trouble, since it interferes badly with duplication and drive extender functionality at all - you should use the UNC path or the shortcut Shared folders on server as target. Also logging in to the desktop should only be done in emergency cases. The normal handling would happen through the console and shared folders.

    Best greetings from Germany
    Olaf
    • Marked as answer by Peter-WHS-Noob Tuesday, December 22, 2009 7:12 PM
    Monday, December 21, 2009 10:41 PM
    Moderator

All replies

  • There is no supported way to achieve what you want; Windows Home Server setup uses a multi-stage script that is run automatically to install and update everything appropriately. It may be possible if you interrupt the scripted setup routines at the right point, however doing so is unsupported and will probably severely impact any server recovery scenario (e.g. a system disk failure, or OS corruption).

    In general, you should not attempt to manage storage on your own. Allow Windows Home Server to do so; install drives and add them to the storage pool using the console rather than attempting to manage them yourself in the Disk Management MMC snap-in. There is a warning that displays every time you log in to your server desktop, rather than through the console, which tells you that anything you do is potentially risky. Take that warning to heart; there are tools available that can cause significant server issues, right up to complete data loss.


    I'm not on the WHS team, I just post a lot. :)
    • Marked as answer by Peter-WHS-Noob Tuesday, December 22, 2009 7:12 PM
    Monday, December 21, 2009 8:46 PM
    Moderator
  • Thanks for your thoughts on this topic, the server set itself up so that C: is 20Gb, and D: is 56,6Gb (according to explorer.exe), when I look at WHS Console at 'Server Storage' I have 3 fysical disks for storage, the 2 large ones (1Tb / 931,51Gb) and one small one (76,69Gb).
    WHS configured this for me, I will no longer use the Diskmanagement-tool for this

    How come (in explorer) I see (D:) only the second partition of the smallest fysical disk mentioned as 56,6Gb but not my other 2 large disks?

    I have attached 3 pictures to clarify.

    Allso, my fear is that when I fill the machine with data again I reach the 60Gb limit again. Then what use are my large disks to me?
    I will fill up (600Gb of testdata) now and post the result tomorrow.

    Photobucket



    Monday, December 21, 2009 9:39 PM
  • Photobucket
    Monday, December 21, 2009 9:44 PM
  • Monday, December 21, 2009 9:46 PM
  • From what I see, your server seems not to be updated. Missing at least two Power Packs, which changed some stuff how the disks are presented. Click the Update button in the console under Settings/General as often, as still new updates are offered. What are the version numbers shown in the console in Settings/Ressources?

    Besides that - copying stuff to d:\shares is always good for trouble, since it interferes badly with duplication and drive extender functionality at all - you should use the UNC path or the shortcut Shared folders on server as target. Also logging in to the desktop should only be done in emergency cases. The normal handling would happen through the console and shared folders.

    Best greetings from Germany
    Olaf
    • Marked as answer by Peter-WHS-Noob Tuesday, December 22, 2009 7:12 PM
    Monday, December 21, 2009 10:41 PM
    Moderator
  • So far I have 80Gb on the 'shares' so I feel that I have been taking a wrong approach to WHS: I filled the D: harddrive from explorer.exe and not WHS Console. (files I did not want to share -> I will add folders in WHS Console for non-shared folder with the appropriate permissions)

    I feel that working from the WHS Console will be more space-efficient as the folderduplication can be set for each folder. I have a lot of movies but my pictures are more important, so I will duplicate the pictures but not the movies. This should leave me with 600Gb more space to work with. Quite a nice feature.

    Anyway, final results will appear tomorrow.

    Cheers for reading and thinking.

    Peter
    Monday, December 21, 2009 10:47 PM
  • From what I see, your server seems not to be updated. Missing at least two Power Packs, which changed some stuff how the disks are presented. Click the Update button in the console under Settings/General as often, as still new updates are offered. What are the version numbers shown in the console in Settings/Ressources?

    Besides that - copying stuff to d:\shares is always good for trouble, since it interferes badly with duplication and drive extender functionality at all - you should use the UNC path or the shortcut Shared folders on server as target. Also logging in to the desktop should only be done in emergency cases. The normal handling would happen through the console and shared folders.

    Best greetings from Germany
    Olaf

    I first installed yesterday, and reinstalled today. Therefore I had SP3 the first time, screwed up, then reinstalled and posted pictures of the reinstall which is still updating to SP3.

    I work with RDP to set the box up for other functionality (voip321.exe with skype.exe, a Canon MX850 network printer and hanewin.exe for communication and automounting of files to my Popcornhour, SABnzbd.exe and virtual pc). When that is done (again) I will use the normal Console on any client pc to administer the server. Normal work will be done on a Virtual machine through a HP thin client.

    Current version numbers are: see picture below

    I am learning fast from the feedback given here. Thanks!

    Peter (from The Netherlands)
    Monday, December 21, 2009 11:09 PM
  • Monday, December 21, 2009 11:15 PM
  • I still have to activate, I feel it is better to wait until the box is stable, then activate.
    Monday, December 21, 2009 11:17 PM
  • 1800.0 is Power Pack 1 without any further updates.
    Best greetings from Germany
    Olaf
    Tuesday, December 22, 2009 11:09 AM
    Moderator
  • After a large update:

    http://i163.photobucket.com/albums/t295/GeoNav-Int/Home%20Server/2009-12-221302startupmessage.jpg

    Restarted, then the message did not reappear (lucky)
    Tuesday, December 22, 2009 12:16 PM
  • showing the resources from today

    <a href="http://photobucket.com" target="_blank"><img src="http://i163.photobucket.com/albums/t295/GeoNav-Int/Home%20Server/WHSconsoleshowingresources2009-12-2.jpg" border="0" alt="Photobucket"></a>

    Tuesday, December 22, 2009 12:17 PM
  • 1800.0 is Power Pack 1 without any further updates.
    Best greetings from Germany
    Olaf

    You are correct, this was after a fresh install...
    Tuesday, December 22, 2009 12:21 PM
  • Thanks for the good advice (multilevel scripting) from Ken Warren and using the WHS Console for file and folder management (Olaf Engelke).

    I'm happy again!

    Peter
    Tuesday, December 22, 2009 7:12 PM