HD Failure - Anyone seen this?

edited May 2004 in Hardware
Strangest problem: Started machine one day and got hung at Verifying DMI pool.

Looked at the strip set and the array failed

Used WD diag tool and created a new MBR on single disk, formatted drive.

Now it takes forever to load a diskette...let alone the OS.

When tyring to load XP Pro, get a black screen after setup inspects. Eventually gets to the setup but hangs a setup is starting Windows.

I can't tell if this is a hardware problem, bios, or mb.

I am stuck

Comments

  • kryystkryyst Ontario, Canada
    edited May 2004
    It sounds like your RAID is messed up. I'd ditch your raid set up and re-create it.
  • edited May 2004
    kryyst wrote:
    It sounds like your RAID is messed up. I'd ditch your raid set up and re-create it.

    Yeah that is what I thought...figured I lost the MBR. Killed the raid, tried a single HD. Used WD diag tool and put on a new MBR and formatted the partition using NTFS at 4k block. Figured I was good to go.

    Bammm...nothing hangs again in setup.

    This is really strange as this box ran for over 14 months without a single problem.

    Same OS..absolutely no changes to the system other then I started powering it down during the day due to heat.
  • edited May 2004
    Tried intsalling using the first HD from the failed stripe set. No luck. Continued to hang at the Verifying DMI Pool, took forever to boot to a DOS disk, as well as on the setup of XP intall.

    Put in second HD from the failed stripe set. Ran the WD DLG11_Dos utility. Formatted HD with this utility as NTFS with a 4kb block.

    Ran XP install, worked flawlessly.

    NOTE: I did not change any setting in bios or memory. Left sound card in, as well as CDR, CD and Zip drive.

    Only thing I can think is that the first HD had a critical failure. MBR gone for sure. Not sure if it was a virus or not....currently run NAV and have never had this problem before.

    Will put erratic HD back in and continue to test.

    Hope this might help some one else

    Cheers.
  • kryystkryyst Ontario, Canada
    edited May 2004
    Sounds like either the tables got screwed up on the first drive. Or possible more likely it still thought it was part of the old raid and was causing issues.
Sign In or Register to comment.