Kia Ora, I have the same system a couple of problems I noticed with your setup. 1) Your power supply is far too weak... especially with 2 proc in you need at LEAST 26Amps on the 12+ volt power rail. (I doubt you 360 watt is anywhere near this). Use a Toppower 450Watt or Enermax PSU. 360W is definitely too thin. 2) The OCZ ram you have will not work with this board. OCZ is designed for Single proc performance level enthusiast boards, and has very tweaked and high CAS timmings. This board is a server board, and does not work well (at all...) with the OCZ pc3200 ecc reged ram. I made the same mistake when first purchacing and got... many...many problems. I have a number of threads open with OCZ/MSI/2cpu forums on this issue... Scrap the OCZ ram. Get Samsung pc400 ecc ram. I did and I get MUCH MUCH more stabler operation (samsung adheres to jdec standards and therefore is cas 3 at pc3200 not cas 2 like corsair/mushkin/ocz) 3) The Raid on this MOBO is software only.... Disable all arrays through the vt8xxx bios util (hit tab at startup). Then use Linux software raid through yast to setup the array. I get Better performance using linux software raid than I do from the Via windows driver designed by the manufacturer... (I use 2 hitachi 160gbs drives, with raptors should should get even better). Hope this has been informative. Kind regards Joel New Zealand On Thu, 2004-06-17 at 04:57, Brock Witherspoon wrote:
Grüss,
I have 4 of these systems that will go into production soon. 3 of them are exactly the same, while the 4th has different hard drives. All of them are experiencing the same problem. I have gone from FreeBSD 5.2.1 to Mandrake 10 (amd64 RC1) to SuSE 9.1 Professional (DVD box set) in search of something that will actually work and perform well. I just used YaST to download the most recent kernel patches, so I'm now at 2.6.4-54-5-smp.
Here is my configuration:
MSI K8T Master2-FAR 2x Opteron 242 2x 512MB OCZ DDR400 RAM ("Specially Engineered and Optimized for the AMD Athlon64 FX platform") 2x WD Raptor 36GB (also WD 160GB SATA drives) 52x IDE CD-ROM 360 Watt Thermaltake PS
These will be servers, so they have no video cards in them (therefore no X etc.). I used an old ViRGE PCI card to do the install. (ncurses based YaST could use some work BTW, particularly in setting up the partitions)
I have a fresh install of SuSE 9.1 Professional, installed off of the DVD in the box set. I had to disable acpi in order to install, and naturally I went with the Linux software RAID to raid the disks.
Watching top is very interesting. Right before a crash, the wa (I/O wait) CPU % goes way up, 50% or more. Then the system becomes unresponsive.
I've searched the 'net and this list and still haven't come up with a thorough prescription for how to fix my problem. I seemed to have made some progress after enabling the libata driver, as the test machine lasted a lot longer this time before failing.
I've got INITRD_MODULES="via_sata libata reiserfs raid1" in /etc/sysconfig/kernel and append = "resume=/dev/hda11 splash=silent acpi=off apm=off console=tty0" in /etc/lilo.conf.
I'm not sure if the libata module "took"; someone else said that I needed to see my SATA drives as sd# rather than hd#. Well, in the boot messages the drives were still called hda and hdc. I am unfamiliar with the entire kernel rebuilding process in Linux, and with how the modules work.
Mostly I just want to hear from somebody else who has this motherboard, exactly what they did to get everything working, because I've tried everything I'm capable of doing. I've found some helpful things so far, but I haven't yet hit the magic bullet.
Of course I can put up any further needed information. I've just got to get these machines working!
Thank you,
Brock Witherspoon