- Joined
- Nov 26, 2007
- Messages
- 310 (0.05/day)
Processor | AMD Ryzen R7 3900X |
---|---|
Motherboard | Gigabyte X570 Asrock X570 Taichi |
Cooling | 2x LL140, 4x LL120 / bequiet! Dark Rock 4 |
Memory | 32GB Corsair Vengence RGB DDR4 (3600 Mhz) |
Video Card(s) | Red Devil 5700XT |
Storage | x1 Inland 1TB Nvme, 1x Samsung 860 EVO 1TB, 1x WD 1TB, 1x Crucial MX500 500GB, 1x Sandisk X400 256GB |
Display(s) | Samsung C32H711 |
Case | Fractal Design Meshify C |
Audio Device(s) | Onboard |
Power Supply | Seasonic Prime Titanium 850W |
Mouse | Logitech G502 Proteus Spectrum |
Keyboard | Logitech G910 |
Software | Windows 10 Pro |
I attempted a RAID 0 configuration yesterday with a Seagate and Western Digital. After a good hour of studying it all I went ahead and did setup the array.
I ran into problems from the start, but long story short I managed to install Windows 7 x64. After enduring random unresponsive programs after I had the basics up and running I decided the speed, while nice, was not worth the slow OS response I saw. At that point I decided to go back to a regular non-RAID setup. [I used 64K block size and had Fast Initialization enabled (just FYI).]
This is where my real problems began. After restoring my non-RAID configuration my system starting acting very weird. For ease of reading I'll use bullet points:
I began to diagnose, and in my panic I took out several parts at once, but when installing I put them back in one at a time testing each to see if if any of them was the cause for the trouble. No dice. I even tested the power supply and every rail checks out. Also ran extended tests on all hard drives with WD's Data Lifeguard tool, and they all check out.
As of now it's up and running and performing perfectly again.
With that information I have a few questions:
On the note of RAID 0:
I ran into problems from the start, but long story short I managed to install Windows 7 x64. After enduring random unresponsive programs after I had the basics up and running I decided the speed, while nice, was not worth the slow OS response I saw. At that point I decided to go back to a regular non-RAID setup. [I used 64K block size and had Fast Initialization enabled (just FYI).]
This is where my real problems began. After restoring my non-RAID configuration my system starting acting very weird. For ease of reading I'll use bullet points:
- Slow post time
- Chassis fan headers 1 & 2 power up then power off after post, then power the LED's on, but the fans only spin when physically aided.
- System reports a failed overclock when there was no overclock
- System crashed once after entering and exiting the bios.
I began to diagnose, and in my panic I took out several parts at once, but when installing I put them back in one at a time testing each to see if if any of them was the cause for the trouble. No dice. I even tested the power supply and every rail checks out. Also ran extended tests on all hard drives with WD's Data Lifeguard tool, and they all check out.
As of now it's up and running and performing perfectly again.
With that information I have a few questions:
- Do I have any reason to worry about my PC or any of it's components in the near future?
- I was offered an RMA from ASUS, but if I don't have to use it I don't want to. To those with similar experiences would it be best to RMA my board?
- After reinstalling my 2nd drive [of three] (the Seagate) my bios gave me information about which drives and devices were on each SATA port. This info was never available before and ever since I rebooted it has not come back. Is this another 'good' sign that I need to RMA it?
On the note of RAID 0:
- Was it a mistake to RAID two differing brands of HDD? Their specs are similar, but the WD does have that 2 processor feature.