locked
Will it work? What the Home server is all about RRS feed

  • Question

  • Through something that shouldn't have happened I crashed my Raid 0 configuration.  They reverted to non-raid and a brief examination indicated it's rocket science and possible expensive purchasing restorative software to get it back.  So I'm backed up on the WHS and it says it's restoring right now, albeit slowly.  It will be truly magnificant if it works but I'm a bit puzzled and somewhat skeptical.

    I did not recreate the array and re-allocate into two volumes as it was originally.  The server however thinks it knows what it's doing and is cheerfully doing a C/system volume restore right now using the target drive size as laid out on the array.  I thought I might have to restore to the non-raid disk 1 but it almost suggests that the restoration process is redoing the array.  i read that array configuration is actually stored on the drive so  I suppose this is plausible.

    What do you think?  Will I have the array back when it's done?  Any chance it will actually work?

    Monday, April 19, 2010 4:59 PM

All replies

  • Windows Home Server restores partitions rather than volumes or arrays. I honestly think it more likely that it will restore the C: partition to one drive, probably using the entire drive (since the drive probably looked "uninitialized"). that said, if you provided storage drivers on USB, it's also entirely possible that your server is restoring successfully to the array.


    I'm not on the WHS team, I just post a lot. :)
    Monday, April 19, 2010 6:01 PM
    Moderator
  • You are correct.  I have successfully restored the C drive and it picked the first non-raid drive in what used to be a two disk raid 0.  IT DID WORK THOUGH AND I'M ECSTATIC.  About to restore the Data drive.  More later.

    Monday, April 19, 2010 6:41 PM
  • What kind of RAID were you using? If it was Windows RAID, I'm unsurprised that it failed to restore the array...
    I'm not on the WHS team, I just post a lot. :)
    Monday, April 19, 2010 6:56 PM
    Moderator
  • Intel Matrix Storage Manager at the bios level.

    I had 2 250's raid 0 then partitioned 200gb and 270gb.

    It took the first disk and dropped the 200gb system volume into a same size partition and then left the remainder of the disk unallocated.

    This presented a problem in that the data volume was larger than the second disk and it refused to restore so I had to round up a > 270 gb external drive to accept the restore.  Once I did that it was uneventful.  There are some lessons there:

    Write down the exact partitioning schema of the raid array and re-create precisely prior to a restore.  This would have allowed a restore process that would have been identical.  Right now I have 2 jbod drives and my system drive is not using the full capacity of the first disk.  I can fix it though with Partition Magic.  The jury is out on whether to redo the raid.  It broke for very finicky reasons.  I hibernated and installed some additional ram, then attempted to come out of hibernation - that's when the fun began.

    Tuesday, April 20, 2010 9:45 PM