I've set up two separate RAIDs recently.
Case 1: ASUS A7V MoBo. Promise Fasttrak100 PCI card controller running RAID-0 on two 20gb Seagate Barracudas. RAID was not used as bootable system drive. Running Win 2000 pro.
Outcome 1: System was never stable. Within a month, the raid was not responding. Tried to reformat the drives separately on another machine, and one was totally dead. Unresponsive even to Win98 FDISK. Seagate replaced it! The RAID controller was removed and the system now runs just fine.
Case 2: GigaByte GA7DXR+ MoBo. Built-in Promise Fasttrak133 controller running RAID-1 on two IBM DeskStar 60gm 60GXPs. This drive was to be used as the sole system bootable drive for data security. Running Win XP full home version.
Outcome: System was never stable enough to get all the way through all peripheral installations. Within hours of running, the drive on RAID channel one was totally fried, unresponsive even to FDISK on another machine. Sent that drive back to IBM (will I get lucky again?), and disabled the Promise chip in BIOS. Now the system runs perfectly on the remaining drive after reformatting.
QUESTIONS:
What am I doing wrong? I'm using the right RAID drivers, and new matched drives. Windows always recognised the drives, but something is killing them!
FACTS
-All drives were more than adequately cooled
-I can't use Linux and don't want to learn
-I never made any changes to the RAID bios, and used the auto-setup features without making any big changes.
-In both cases, it was IDE-0 that failed.
Has anyone else had this problem? Or is there something I don't know about happening here?
THANKS!
Case 1: ASUS A7V MoBo. Promise Fasttrak100 PCI card controller running RAID-0 on two 20gb Seagate Barracudas. RAID was not used as bootable system drive. Running Win 2000 pro.
Outcome 1: System was never stable. Within a month, the raid was not responding. Tried to reformat the drives separately on another machine, and one was totally dead. Unresponsive even to Win98 FDISK. Seagate replaced it! The RAID controller was removed and the system now runs just fine.
Case 2: GigaByte GA7DXR+ MoBo. Built-in Promise Fasttrak133 controller running RAID-1 on two IBM DeskStar 60gm 60GXPs. This drive was to be used as the sole system bootable drive for data security. Running Win XP full home version.
Outcome: System was never stable enough to get all the way through all peripheral installations. Within hours of running, the drive on RAID channel one was totally fried, unresponsive even to FDISK on another machine. Sent that drive back to IBM (will I get lucky again?), and disabled the Promise chip in BIOS. Now the system runs perfectly on the remaining drive after reformatting.
QUESTIONS:
What am I doing wrong? I'm using the right RAID drivers, and new matched drives. Windows always recognised the drives, but something is killing them!
FACTS
-All drives were more than adequately cooled
-I can't use Linux and don't want to learn
-I never made any changes to the RAID bios, and used the auto-setup features without making any big changes.
-In both cases, it was IDE-0 that failed.
Has anyone else had this problem? Or is there something I don't know about happening here?
THANKS!
Facebook
Twitter