locked
D Drive Unformatted RRS feed

  • Question

  • My home-built WinHS machine has been rock-solid for a long time. It currently contains 5 HDDs with a total capacity in excess of 6 tB. Most of the data are DVDs and Blu-rays, which are duplicated on a second server running linux-based OpenFiler. I have an innate distrust in the long-term stability of all computers, especially if built by me from retired parts!

    So it came as no surprise to discover, after installing some "critical updates" through Windows Update, that my WinHS had broken. Home Server Console won't even start, and the system asks permission to report numerous OS errors to Microsoft. Further investigation revealed that the D Drive is unformatted, no data. However, all the HDDs are reported as healthy by Device Manager, and most of the data are probably intact.

    Just guessing, but, based on past experience, I suspect that one of the HDDs glitched or failed. Is it worth the time to try and recover the system, or should I just start over with something else?

    All I really need is NAS for media. Anything "important" is stored elsewhere. And maybe it's time to actually build the server with all NEW parts, not just new HDDs!

    Saturday, September 18, 2010 3:53 PM

Answers

  • All of that is normal, given a disk failure that affected the partition table on the system drive.


    I'm not on the WHS team, I just post a lot. :)
    • Marked as answer by _Sleeperman Sunday, September 26, 2010 11:46 PM
    Thursday, September 23, 2010 5:11 PM
    Moderator

All replies

  • And, if recovering the system is worth the effort, how could it be done?
    Saturday, September 18, 2010 5:32 PM
  • And, if recovering the system is worth the effort, how could it be done?
    You boot from the DVD and perform a Server Reinstallation.
    Sunday, September 19, 2010 4:43 AM
    Moderator
  • I tried that; the only option is "New Installation". Also, the (WinHS version 1) Installation Disk isn't detecting one of the HDDs. All the drives are shown in BIOS, and during initial bootup.

    I've just about decided to bail on this thing, and build a low-power server based on a new 1156/H55 mainboard and a Core I3-530 CPU. Once it's running and fully updated, the data could be restored from the old drives and/or my OpenFiler NAS box.

    If this turns out to have been caused by a single failed HDD, I'll be very disappointed that WinHS couldn't isolate the problem like it's supposed to. If ALL the storage drives turn out to have been unformatted by WinHS, and ALL data lost on otherwise healthy HDDs, will go with linux and wait for Vail, version 2.

    For now, will tinker with it a bit longer. If no progress can be made, it goes to the bone yard for salvage.

    Sunday, September 19, 2010 5:35 PM
  • There are five HDDs in this computer, I've now been able to confirm that there are four storage drives in C:\FS, all with data apparently intact; they are C, H, S, and U. As before, D:\ is still reported as unformatted.

    Still not able to do "Server Update" or launch Home Server Console. Think I'm done wasting time with this, unless someone has a suggestion.

    Sunday, September 19, 2010 7:42 PM
  • The machine is being rebuilt. New components are on the way, including an Intel server MB.

    I'm currently looking at my WinHS HDDs on another computer. The data partition on the system drive is, indeed, unformatted; the data partition is reported as healthy, but about 700 gB of data are MIA. Data on the other drives are intact. Surprisingly, most of the data drives have a small amount of unallocated space, usually a few mB; anyone know if this is normal?

    Probable cause of this carnage might be a failure of the system drive, corrupting the data partion in such a way as to unformat it. Without a formatted D drive, WinHS is nearly useless.

    Another issue I noticed is that WinHS had barely used any of the storage available on the newest 2 tB HDD added to the pool. For some unknown reason WinHS preferred the older drives, most of which were nearly full, including the system drive's data partition. Another mystery there.

    This is my second server failure involving WinHS. The first was caused by an Antec power supply, which, despite the UPS it was plugged into, malfunctioned and fried every drive, including the FDD and DVD reader. It took several months for the smell of burning electronics to fade from the room! In that case, the data was backed up to DL DVD's, which were copied to the replacement server one at a time. But, one or two of the DVDs would not fully copy because of errors.

    So, if anyone thinks duplicated data on WinHS, or anywhere else, are completely safe, think again. As Bill Clinton might say, the meaning of the word "safe" depends on your definition.

    Thursday, September 23, 2010 3:10 PM
  • All of that is normal, given a disk failure that affected the partition table on the system drive.


    I'm not on the WHS team, I just post a lot. :)
    • Marked as answer by _Sleeperman Sunday, September 26, 2010 11:46 PM
    Thursday, September 23, 2010 5:11 PM
    Moderator
  • I assume that "Server Update" wasn't an option because of the unformatted D partition. But WinHS's preference for nearly-full drives in the storage pool vexes me; perhaps something could have been done to force some load-balancing amongst the HDDs?
    Thursday, September 23, 2010 9:13 PM
  • New WinHS machine now built; much faster than the old one! Data will take some time to transfer over from the OpenFiler box, even with a direct ethernet connection via crossover cable. I've networked WinHS a number of different ways, but always end up with a steady 40-50 mB/sec while copying bunches of movies.

    The end result of all this will be a more robust home network. WinHS + NAS backup makes a pretty good combo.

    Sunday, September 26, 2010 11:45 PM