locked
Problem with XP Pro dynamic Raid 5, help needed. RRS feed

  • Question

  • My serer had a power supply problem which affected the system to the point where it wouldn't start every time. The initial thought was a bad boot disk, but after testing it was discoverd it was the power supply was the cause. In the process I had move the system from the original boot drive to a new one.  During the process the raid drive would or would not be seen on boot. This would cause the system to take up to 30 minutes to boot up. When running disk manager wouldn't easily find the raid drives, this process could take several hours without positive results.

    I finally decided to replace the power supply and that helped. Drives were identified on boot, restarts was down to minutes, but the raid was not available.

    Currently disk manager reports the raid as "failed" and the only option available in the menu is it to delete partition. I did add a new drive both unpartitioned and partitioned to see if that would enable the restore partition option, but that isn't the case. I'm not sure I have any more options with the disk manager.

    Active@'s partition recovery can see the raid and the directory structure just fine. This is from the demo of the latest version, my older version was dos-based and I'm waiting to hear back if it will work with xp's dynamic disks.

    I have dmdiag reports, but about the only thing I believe I can see in there is that the drives are all correctly typed as dynamic. Beyond that I'm not sure what the report is telling me.

    At this point I'm guessing the system is confused as to what is exactly on the drives. Maybe a boot record, or some other internal structure. I'd love to get this data back, but have no idea what I need to do.

    Friday, December 16, 2011 5:21 PM

All replies

  • I guess I forgot to mention that I did image all the drives before starting on this recovery path. I was hoping there is some built-in microsoft tool that would help, because if I do the 3rd party method it requires having another drive to recover to.

     

    I also forgot to mention the drive have all tested out good with the extended tests from the mfgr. I'm pretty comfortable with the idea that the power supply was the problem and luckily I didn't write to that dyanmic disk during the trouble period, but it appears the OS had decided (guessing during the OS reinstall) that this drive was something different and made changes which have confused itself. But, those are just dumb guesses.

    Saturday, December 17, 2011 6:05 AM
  • Is there any microsoft support number that I could call?
    Monday, December 19, 2011 2:59 PM