Jump to content
10 posts in this topic

Recommended Posts

First off, here's my setup:

 

CPU: C2D e6600

Mobo: P5B-Deluxe wifi

GPU: x1800GTO (Flashed to XL)

RAM: 1GB DDR2 mushkin

PSU: 600W OCZ gameXstream

 

The hard drives in my system are my OSX drive (80GB SATA), WinXP drive (250GB SATA2) and a data drive (250GB SATA2). My data drive was originally a dynamic-disk and ntfs support isn't a happy thing so I decided that I'd format it and set it to be FAT32 so that I'd be able to move data easily between boots. So I transfered my stuff off it which took a good hour, then formatted in disk director, booted and tried to put my data back on. What happened next is the weird part. When I dragged my stuff back onto the data drive, it started going fine but every ~200mb the disk would stop spinning, you'd hear it stop and nothing would happen. It took around 8 hours to move the data back on. I tried to watch a video on it and half way through the video just stopped for 30 seconds or so then started again. Does anyone know what I can do about this?

Link to comment
https://www.insanelymac.com/forum/topic/35949-hard-drive-stops-activity/
Share on other sites

I had a similar issue. Once in a while, one of my disks was randomly stopping, while I was working on the computer. I could hear the "clong of death" and the OS freeze for a moment, until the disk started to spin again. Not sure about the reason, but what I did was to change the position of the power cables and it solved the problem.

 

Before, I had two hard disks sharing the same line in the source power (by this, I mean that my source power has two main lines, each one with two 12v ATA connectors and one 5v floppy connector). Now, I have one hard disk attached to each line, and the issue has never happened again.

 

Just my two cents.

Try removing a couple of unnecessary kexts. The first is probably installed. The second is probably removed, but check anyway.

 

Follow the HWSensor and TPMACPI links in my signature. As always, after messing with kexts, delete the Extensions.mkext and Extensions.kextcache files and reboot.

 

If that fails to help, then look at some logs. Go to the Utilities folder and find Console. Run it and click the Logs button in the left side of the toolbar. Study the system.log and console.log for repetitive errors that may be slowing things down.

Edited by Rammjet

Thanks proteo. Your solution worked great! I never thought of it as a problem because for some reason windows never gave me problems with that. I'm just going to do another boot to confirm everything worked out but I'm pretty sure this fixed the problem.

 

Rammjet thanks a lot for your suggestion too. If this doesn't work on boot I'll give yours a shot.

 

Edit:

 

Everything looks great now. Thanks to everyone for the quick replies. Even my xbench scores went up :)

Edited by Daimajin

Yes, I had no problems with Windows either. Actually, I didn't have this problem before updating to 10.4.8. My guess is that now that more kexts are being used, some energy-related functions in the OS are having minor issues with non-Apple hardware.

×
×
  • Create New...