If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
HELP: FAILED RAID 0
I am guessing I am screwed.
I have a Windows Server that had RAID 0 on it (I didn't set it up that way, previous tech guy did). It is a ATA/133 RAID built into the motherboard. I got a message from the server saying that there is not enough disk space. So, I slid off the side panel on the case and peered inside. There was a CDROM with an extra spot for an IDE hard drive off it. So I decied to throw a Western Digitial drive on it (Secondary controller). I shut the computer down first of course, quickly attached the second drive, and rebooted. First message that I got on the reboot (after the BIOS) was "Invalid Partition." Uh-oh. I thought that the WD I just put in was thinking it was the boot device. I checked the BIOS, and no, it was not--HDD0 was, and that is from the RAID. Rebooted, now just a blank black screen. Scared, I completely took the WD out. Rebooted, same thing. Checked the RAID drives, still connected, still spinning up. Rebooted, and now I get some kind of "trap" code every time I boot with a bunch of meaningless (to me) numbers. Unfortanately, there is no backup because the company does not have the funding for one. Is there any way possible to completely rebuild this RAID 0 or get the data off it in some way? Pretty please? Help? Suggestions? I am going to try and boot with a Windows CD and the RAID drivers and see if it sees anything on the RAID. Hopefully it will, but the trap code worries me. |
#2
|
|||
|
|||
|
#3
|
|||
|
|||
Thanks.
After tinkering it for a while, I was finding I could not boot from anything--not even a floppy or CD as it would just hang; even with the RAID controller disabled, and basically just the motherboard, video card, and floppy disk attached. Even setting the BIOS to failsafe settings (no default option) didn't work. If I were to leave it off for awhile, the system would begin to boot, but then either freeze or go to a blue screen of death (random errors). So, I decided to flash the BIOS, but before I did I read the instructions on the CMOS clear jumper. So, I did that first before the flash, and then zam! it worked. So, something must have been in the BIOS to keep the system from booting at all. Upon booting, I immediately backed up all data. The server does not have a virus scan (they don't want to pay the money for one), but I am thinking that perhaps the BIOS was hit and my just rebooting it after weeks of being constantly on kicked everything into motion. Now that this scare happened, the boss finally realizes the importance of a backup system and virus scan. However, we can skip the virus scan since we are moving to a Linux server instead...with a mirroring RAID. |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
How I built a 2.8TB RAID storage array | Yeechang Lee | Storage & Hardrives | 42 | March 3rd 05 12:04 AM |
How I built a 2.8TB RAID storage array | Yeechang Lee | Storage (alternative) | 42 | March 3rd 05 12:04 AM |
P4C800-E Delux: Setting up SATA Drives with RAID | Will | Asus Motherboards | 13 | July 12th 04 04:33 AM |
How to set up RAID 0+1 on P4C800E-DLX MB -using 4 SATA HDD's & 2 ATA133 HHD? | Data Wing | Asus Motherboards | 2 | June 5th 04 03:47 PM |
RAID-1 reliability | marcodeo | Storage (alternative) | 26 | August 30th 03 09:53 PM |