Jake Anderson wrote:
On 27/07/09 17:34, Gerald wrote:
to all,
I have a SOLTEK motherboard that is giving problems.
I have spent 3 hours running memtest and it gives a clean bill of
health.
This means that the CPU is OK and the MEMORY is OK
I have run SEATOOLS on any hard disks that I will use in the system.
This gives a clean bill of health also. Again, showing cpu,memory now
HDD ok
I have also run 'DBAN' on the drives and this also finds no problems.
So... memory ok, ..cpu.. ok.. hard drives.. ok, and the ide controllers
are ok.
Now try to install any distro and the system crashes. The KB leds flash.
OR the livd CD boots or not, but if so, then all can be fine until
mounting partitions. I then get unable to mount UUID****. I can use
fdisk or gparted or MCC to create partition with no problems.Then use mkfs.ext* to format the Drives/Partitions. The only trouble is mounting them, but not all partitions have the problem.At this point it is difficult to be precise. Any partition may
mount or not and having tried to mount give the UUID problem.
Further.. the problems are still there if a new IDE drive is used or if the drive
is mounted USB
Any ideas on what is going on.
Gerald

memtest doesn't test the CPU that much actually.
If the power supply caps (particularly those on the MBO close to the cpu) are toast then any sudden CPU intensive spurt (especially if combined with disk activity) can cause it to crash.

I've seen this multiple times with other machines, if you get intermittent booting/random weird lockups check the system power supply, and the motherboard caps.
I second this advise. I have seen a number of unstable, older Soltek motherboards, with capacitors that have 'bulged' or 'bled' indicating failure of those caps. Have a good look at your motherboard capacitors.

D.

--
"Never ascribe to malice that which may adequately be explained by 
incompetence." - Napoleon Bonaparte

--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html

Reply via email to