• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Installed new HD, now computer has gone nuts (fixed)

E

Electrode

Diamond Member
This last friday, I bought and installed a new WD 40 GB 7200 RPM IDE hard drive. I booted up and all hell broke loose. Nothing has worked quite right since.

When I first installed it, there were no really obvious problems. I did cfdisk and mkreiserfs without errors, but the problems started showing up after that.

I mounted the new partition, and began moving some files on to it. While I was browsing the forums, the computer suddenly rebooted itself. During the startup process, it rebooted again. When I finally did get back to a login prompt, I began to go through my procedure of starting the SETI clients, renicing them, and starting X. However, when I started the first SETI client, the computer rebooted AGAIN! :|

It never did get through the init process again, so to get the computer running, I had to use a floppy. When I logged in again, I tried to mount the new HD. Instant reboot. Tried a few more times, and finally got it to work, only to find that many of the files on the new HD were corrupt.

The next thing I tried was taking the new HD out and trying to boot. It appeared to work at first, but when I started SETI, it rebooted. It rebooted again when I tried to SCP a file.

I tried the HD in another computer, and it appeared to work, but then again, it worked fine at first in this computer too.


Right now, the computer boots by itself, but the moment any program tries to write, the system reboots itself.
So what do I do now? How could a problem that started when I added the new HD continue after I took it out?


Specs:
CPU: Dual Pentium 3 667
RAM: 1664 MB PC133
Motherboard: MSI 694D Pro-AR
Storage: WD 13 GB 5400 RPM IDE
OS: Linux (kernel 2.4.19-pre2, glibc 2.2.5)
 
yeah, you have a pretty power hungry system as it is with that much RAM and dualies (albeit celeries) adding the larger and faster hdd might have been the straw that broke the camels back, try a larger psu if you can.
 
I thought that a 300 watt PSU would be more than enough for this rig, but I'll try a bigger one once I save up some cash.
 
technically, there's no problem with both udma drives running on the same channel. what happens is that both drives, including the uata100 one, will both run at 66...

have you tried running Western Digitals drive fitness tools on it.. it came with your drive if you bought the retail pack .. or you can just download it from www.westerndigital.com .. it might be your drive is defective and is causing the system problems.

one thing you could try to test if the power supply is the culprit is to remove all hard drives except for the new 40gb one, install an OS on it, and try it out... that way, the power is the same as the original drive. If there are no problems, then its probably your PSU.. if the reboots continue, then its a faulty drive. =P

good luck!
 
Well, I already tried running with just the new hard drive, just the old hard drive, and with both with new drive as master and as slave. Even with a hard drive from another computer.

So here's where I am so far:

No matter what HD I am using, how many, or in what configuration, the computer still crashes every time I try to do something with it. I have also tested the new HD in other computers and it works fine.

So what is the deal?
 
I'd remove all but one stick of ram, swapping a stick each time if error continues. After that I'd suspect failing mobo...odd. These types of problems are teh maj0r sux0r. Sorry for ya.

-Rhi
 
I'll try swapping the RAM tomorrow. Too tired to do anything now.

As for the PSU, I haven't had the chance. The current PSU is my biggest (the others have 250's) and I have no spares. I'd need to buy a new one.

I sure hope it's something that won't be expensive to repair. I only have $19 and I won't be getting more any time soon. 🙁
 
Well, I tried the RAM one stick at a time, even trying it in other slots, and it still crashes, so that's not the problem.

So, what now?
 
this is starting to look like motherboard failure....
clearly we've concluded it isn't the hard drive, memory, or power supply ...
 
It certainly sounds like a PSU issue but with you being busted you'll have to keep searching for other potential culprits until you recieve a fresh infusion of funds 🙁
 
So, it's down to either a PSU or motherboard problem. What exactly could I do (other then take the mobo out of another computer) to figure out which is causing the problem?
 
The first place to look is for a short. I once had a screw lodged under my motherboard and the system would re-boot at odd times. Didn't find the real culprit until I was getting ready to RMA the board.

Once you've eliminated a possible short, since you have a limited budget, your best option looks like using one of your 250 W supplies to test. Minimize your rig (mb/single cpu if possible, video, hd, floppy, and the smallest PC133 memory stick you have) and 250 should be plenty.

If this doesn't work, then you probably have a bad board. If it does, switch back to your 300W and then start adding components one at a time.

 
Well, I found the problem, but it's not really something I wanted it to be. Looks like my second CPU is the culprit. It ran fine on just one CPU, but when I added the second CPU, the crashing resumed.

I suppose half of a computer is better than no computer. 🙂 Maybe I can get a few bucks selling it in FS/FT.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top