MacBook Pro Corrupt Disk... help??

korobokkuru · Dec 28, 2014

Hi, I have a MacBook Pro with OS X 10.6.8

For several months it crashes frequently, especially if I use several programs at once. The screen suddenly goes black but it does not shut down. If I am playing music, the same one second of sound will repeat over and over again.

When this happens, the only solution is to hold down the power button until it shuts off, and then restart. Usually it makes a popping noise when it shuts down but not always. (Maybe the popping noise is normal? Idk)

I finally decided to look into this problem as it is very bothersome and I have lost a lot of unsaved files because recently it happens more and more frequently.

According to the disk utility, the startup disk is corrupt. I have tried to repair it in single user mode using applejack and fsck but I still get the same error message:

I have the original installation CD but I can't use it because the superdrive is broken. After I insert the disc into the drive, it makes noises for a minute or two as if it's trying to read it, but then spits it back out. I tried several discs as a test but none of them work. I tried resetting the SMC and cleaning the drive but that didn't work, either.

I am wondering, is it worth it to buy a cheap external superdrive and try to repair the disk or reinstall OS X myself, or should I give up and take it to the genius bar where they will probably charge me a boatload of money? Ideas?

BrianBaughn · Dec 29, 2014

There is no difference between using Disk Utility (from a installer disk or external drive) and Applejack in single-user mode...so...you've done all you can do in that regard.

It's possible that your hard drive is OK and that the third-party app "DiskWarrior" could repair the directory but I'd say just get a new drive since DW costs $120.

If the disk is damaged/dying this is a time sensitive matter. You need to be backed up and if you're not you should probably proceed with getting a new drive right away. This may be an opportunity to upgrade to an SSD!

Looks like you'll need to get an external DVD device (Just about any will do. No need to get the high-priced Apple one) no matter what the situation. So, if you're backed up, get the new DVD drive, reformat the old drive and check it with Disk Utility. If it checks out OK it could still be bad, though. Only a thorough scan of all the blocks on the drive by another third-party app will let you know. However, if it checks out OK you can go ahead and reinstall and recover from your backup. If problems reappear you can get a new drive.

If you're not backed up get a new drive right away as well as an external housing or USB to SATA connector (so you can get your files off the old drive). If you get an SSD you'd better format it first using the external housing or connector before taking the original drive out of the MBP.

Swapping drives on a MBP is easy and you'll find the instructions at iFixit.com.

korobokkuru · Dec 29, 2014

Thank you so much BrainBaughn!! This was so helpful!

I have my files backed up on a drive with time machine a few weeks ago but I'm away from home and won't have access to it until the middle of January. I do have another drive with me so I think I will just back up whatever files that haven't been backed up or that I will need while I'm away.

My mom thinks I'm crazy to try to repair my Mac by myself but I think factory repair or in store repair will be way more expensive. If it's factory repair they will also want to replace the busted superdrive, and the screen is cracked, too... All of that is going to add up to the price of a new PC (I know I'm horrible for not taking better care of this computer)

I will get the external DVD device ASAP and I'll post again if I have any problems. Thanks again!!

korobokkuru · Dec 29, 2014

UPDATE!! Still having problems!

Hi again,
Today I bought an external DVD drive and I was able to run the installation CD. I successfully reinstalled OS X Snow Leopard.

My Mac seemed to be fixed at first after reinstall. Overall it was running better and the disk utility no longer showed an error.

I wanted to test it out to see if it was really fixed, so I opened as many apps as I could and eventually it crashed like it always does. When I restarted the computer, it was back to its old self and crashed again almost immediately.

I ran the disk utility again and now it's showing more errors than it was before I reinstalled OS X! Even though there were no errors immediately after reinstallation!

I'm assuming this means the hard drive needs to be replaced? I was so hopeful when there were no errors after reinstall...

DeltaMac · Dec 29, 2014

The problem is that when your MBPro crashes/locks up, and you have to force power off, that always runs the risk of corrupting directories, or individual files.
I think that a disk repair should always be the next step after a hard crash. Often, nothing is repaired, but sometimes you will stay a step ahead by fixing some minor issues, before they become more "challenging"

Now that you have a working DVD drive, boot to your Snow Leopard installer, and run Disk Utility from the Utilities menu. Try a Repair Disk then.
It's very possible that won't help, but you should try it now....

If that doesn't clear out the Disk Utility remarks, then you should:
Backup - if you still need to backup - to another drive.
Boot to your installer DVD, Erase your hard drive, again using Disk Utility.
Quit Disk Utility, reinstall OS X, and restore all your stuff.
Takes some time to do right, but you should have less problems, and likely a much smoother/faster system when you are done.

korobokkuru · Dec 29, 2014

Starting to get confused?

So I tried again this time using the disk utility to repair and I had the same issue: initially the repair was successful but then it crashed again anyway (and this time I wasn't even doing anything that uses a lot of memory...) And after the crash the disk utility comes back again with new errors, even though the disk was supposedly "successfully repaired."

I understand that wiping the hard drive and then reinstalling OS X again would help my computer run better, but I don't expect that would fix the crashes--since it keeps crashing anyway even after the disk is supposedly "repaired" and has no errors.

If the crashes themselves are causing the errors, how can I be sure that the hard drive is the cause for the crash? Could it be another issue that is the real problem and the errors showing up on disk utility are only secondary?
I don't know what else would cause crashes like this except for an issue with the hard drive, though?

Maybe I'll take it in to the genius bar or somewhere just so they can confirm the source of the problem...

Thoughts??

korobokkuru · Dec 29, 2014

Kernel Panic?

Sorry to spam the forum. I've figured out that the crashes are actually kernel panics. I don't know if that changes anything?

I'm pretty sure the panics started a few years ago after I accidentally left my Mac plugged in during a power outage. I've always suspected the power surge did some damage. I should have gotten it taken care of when it was still under warranty, my mistake...

It's just the past few months that the panics have become really frequent. Like multiple times every day.

Does that change anything as far as hard drive replacement etc?

BrianBaughn · Dec 30, 2014

More evidence of what was already a possibility.

You should be hoping that it's either the HD or RAM has gone bad. I should have thought of that when you mentioned crashing. The RAM is also easy to replace. If it's a motherboard problem it's probably not worth fixing unless you luck into a cheap replacement.

As DeltaMac says the crashing is a probable contributor of HD corruption.

How much RAM does the computer have and in what form (one stick, two sticks, amount of each)? If there's two RAM modules in there, you could take one out at a time and see if you get the crashes. Not likely that two RAM sticks would go bad.

Fishrrman · Dec 30, 2014

OP:
Could the problem be localized to a bad internal hard drive?

Do you have ANOTHER hard drive (external) that you could try booting from?

What year is the MacBook?

Most of the (non-retina) MacBooks have internal drives that are VERY easily replaceable.

Might be time to think about upgrading to an SSD.
You will -LIKE- the performance increase!

korobokkuru · Dec 30, 2014

@BrianBaughn There are two sticks, 4GB each. I will try taking one out.
@Fishrrman I do have an external hard drive, I'll try installing OSX on that and booting from there to see what happens. The MacBook is from 2011.

I tried wiping the hard drive and reinstalling everything. As I suspected it runs better but the crashes are not at all fixed. I haven't recovered the majority of my data yet since I won't have access to my drive with time machine until mid January.

I tried booting it in safe mode again before I wiped it and there were no panics. I did everything I could think of to make it crash and it got really, really, really slow, but no panic. Does that mean anything?

Below is the log of the most recent kernel panic. Can anyone make anything of this?

Wed Dec 31 00:48:26 2014
panic(cpu 0 caller 0x83356c97): NVRM[0/1:0:0]: Read Error 0x00000100: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0xc0000000 0xa64ec000 0x0a5480a2, D0, P2/4
Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)
0x7a9e9c38 : 0x21b837 (0x5dd7fc 0x7a9e9c6c 0x223ce1 0x0)
0x7a9e9c88 : 0x83356c97 (0x8356c22c 0x835dc840 0x8357af88 0x0)
0x7a9e9d28 : 0x834715db (0xce33c04 0xc1a2004 0x100 0x1ab9c000)
0x7a9e9d78 : 0x834685d4 (0xc1a2004 0x100 0x7a9e9da8 0x83346774)
0x7a9e9da8 : 0x83b8b965 (0xc1a2004 0x100 0x438004ee 0x1)
0x7a9e9ee8 : 0x83490258 (0xc1a2004 0xc348004 0x0 0x0)
0x7a9e9f28 : 0x8335fe2b (0xc1a2004 0xc348004 0x0 0x0)
0x7a9e9fc8 : 0x8335c50a (0x0 0x9 0x0 0x0)
0x7a9ea178 : 0x8335e696 (0x0 0x600d600d 0x7027 0x7a9ea1a8)
0x7a9ea248 : 0x8293810d (0xc1d00041 0xbeef0003 0x19613980 0x71)
0x7a9ea2e8 : 0x82938685 (0x6bad5000 0x19613980 0x151cd004 0x0)
0x7a9ea328 : 0x8290fec3 (0x6bad5000 0x19613980 0x151cd004 0x0)
0x7a9ea358 : 0x82937cba (0x6bad5000 0x19613980 0x151cd004 0x829591dc)
0x7a9ea378 : 0x8290f418 (0x6bad5000 0x19613980 0x151cd004 0x7a9ea388)
0x7a9ea398 : 0x82938630 (0x6bad5000 0x151cd000 0x0 0x4d8)
0x7a9ea3d8 : 0x82912905 (0x6bad5000 0x151cd000 0x0 0x0)
0x7a9ea418 : 0x82910325 (0x6bad5000 0x6bca3000 0x0 0x14e71780)
0x7a9ea468 : 0x829634e9 (0x6bad5000 0x6bca3000 0x0 0x14e71780)
0x7a9ea4f8 : 0x82954c9b (0x14e71780 0x151cd000 0x0 0x1)
0x7a9ea558 : 0x82954f02 (0x6bca3000 0x6bca3788 0x151cd000 0x0)
0x7a9ea5a8 : 0x829553d6 (0x6bca3000 0x6bca3788 0x7a9ea8cc 0x7a9ea86c)
0x7a9ea8e8 : 0x829521a1 (0x6bca3000 0x6bca3788 0x1 0x0)
0x7a9ea908 : 0x8291988f (0x6bca3000 0x6bca3788 0x0 0x0)
0x7a9ea938 : 0x82953c64 (0x6bca3000 0x7a9eaa7c 0xa48d4080 0x6bca3000)
0x7a9ea978 : 0x8291dc93 (0x6bca3000 0x7a9eaa7c 0xc4 0x6bc73000)
0x7a9eaab8 : 0x829575d8 (0x6bca3000 0x1 0x7a9eabcc 0x7a9eabc8)
0x7a9eab68 : 0x82919fe1 (0x6bca3000 0x1 0x7a9eabcc 0x7a9eabc8)
0x7a9eabe8 : 0x56da06 (0x6bca3000 0x0 0x7a9eae3c 0x7a9eac74)
0x7a9eac38 : 0x56e2a5 (0x829a8720 0x6bca3000 0x19484988 0x1)
0x7a9eac88 : 0x56eb59 (0x6bca3000 0x10 0x7a9eacd0 0x0)
0x7a9eada8 : 0x286638 (0x6bca3000 0x10 0x19484988 0x1)
0x7a9ebe58 : 0x21dbe5 (0x19484960 0x1b5535a0 0x1fc368 0x5003)
0x7a9ebe98 : 0x210a86 (0x19484900 0x0 0xdf44a10 0x15364730)
0x7a9ebef8 : 0x216f84 (0x19484900 0x0 0x0 0x0)
0x7a9ebf78 : 0x295c57 (0xca75888 0x0 0x0 0x0)
0x7a9ebfc8 : 0x2a256d (0xca75884 0x0 0x10 0xca75884)
Kernel Extensions in backtrace (with dependencies):
com.apple.GeForce(6.3.6)@0x8290e000->0x829c4fff
dependency: com.apple.NVDAResman(6.3.6)@0x832f0000
dependency: com.apple.iokit.IONDRVSupport(2.2)@0x825c5000
dependency: com.apple.iokit.IOPCIFamily(2.6.5)@0x7a6b5000
dependency: com.apple.iokit.IOGraphicsFamily(2.2)@0x82e6b000
com.apple.nvidia.nv50hal(6.3.6)@0x83a55000->0x83e69fff
dependency: com.apple.NVDAResman(6.3.6)@0x832f0000
com.apple.NVDAResman(6.3.6)@0x832f0000->0x835ddfff
dependency: com.apple.iokit.IOPCIFamily(2.6.5)@0x7a6b5000
dependency: com.apple.iokit.IONDRVSupport(2.2)@0x825c5000
dependency: com.apple.iokit.IOGraphicsFamily(2.2)@0x82e6b000

BSD process name corresponding to current thread: Google Chrome He

Mac OS version:
10K549

Kernel version:
Darwin Kernel Version 10.8.0: Tue Jun 7 16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386
System model name: MacBookPro6,2 (Mac-F22586C8)

System uptime in nanoseconds: 753564107120
unloaded kexts:
com.apple.driver.AppleUSBUHCI 4.2.0 (addr 0x81c6d000, size 0x65536) - last unloaded 196630026713
loaded kexts:
com.apple.filesystems.msdosfs 1.6.3 - last loaded 128774566137
com.apple.driver.AppleHWSensor 1.9.3d0
com.apple.driver.AGPM 100.12.31
com.apple.driver.AudioAUUC 1.57
com.apple.driver.AppleMikeyHIDDriver 1.2.0
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.driver.AppleUpstreamUserClient 3.5.7
com.apple.driver.AppleMikeyDriver 2.0.5f14
com.apple.driver.AppleIntelHDGraphics 6.3.6
com.apple.driver.AppleHDA 2.0.5f14
com.apple.driver.AudioIPCDriver 1.1.6
com.apple.driver.AppleMCCSControl 1.0.20
com.apple.driver.SMCMotionSensor 3.0.1d2
com.apple.iokit.AppleBCM5701Ethernet 3.0.5b8
com.apple.driver.AppleIntelHDGraphicsFB 6.3.6
com.apple.driver.AppleGraphicsControl 2.10.6
com.apple.GeForce 6.3.6
com.apple.driver.AirPortBrcm43224 428.42.4
com.apple.driver.ACPI_SMC_PlatformPlugin 4.7.0a1
com.apple.driver.AppleLPC 1.5.1
com.apple.kext.AppleSMCLMU 1.5.2d10
com.apple.filesystems.autofs 2.1.0
com.apple.driver.AppleUSBTCButtons 201.6
com.apple.driver.AppleUSBTCKeyboard 201.6
com.apple.driver.AppleUSBCardReader 2.6.1
com.apple.driver.AppleIRController 303.8
com.apple.BootCache 31.1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.iokit.SCSITaskUserClient 2.6.8
com.apple.iokit.IOAHCIBlockStorage 1.6.4
com.apple.driver.AppleFWOHCI 4.7.3
com.apple.driver.AppleSmartBatteryManager 160.0.0
com.apple.driver.AppleUSBHub 4.2.4
com.apple.driver.AppleEFINVRAM 1.4.0
com.apple.driver.AppleAHCIPort 2.1.7
com.apple.driver.AppleUSBEHCI 4.2.4
com.apple.driver.AppleACPIButtons 1.3.6
com.apple.driver.AppleRTC 1.3.1
com.apple.driver.AppleHPET 1.5
com.apple.driver.AppleSMBIOS 1.7
com.apple.driver.AppleACPIEC 1.3.6
com.apple.driver.AppleAPIC 1.4
com.apple.driver.AppleIntelCPUPowerManagementClient 142.6.0
com.apple.security.sandbox 1
com.apple.security.quarantine 0
com.apple.nke.applicationfirewall 2.1.12
com.apple.driver.AppleIntelCPUPowerManagement 142.6.0
com.apple.driver.AppleProfileReadCounterAction 17
com.apple.driver.AppleProfileTimestampAction 10
com.apple.driver.AppleProfileThreadInfoAction 14
com.apple.driver.AppleProfileRegisterStateAction 10
com.apple.driver.AppleProfileKEventAction 10
com.apple.driver.AppleProfileCallstackAction 20
com.apple.iokit.IOSurface 74.2
com.apple.iokit.IOBluetoothSerialManager 2.4.5f3
com.apple.iokit.IOSerialFamily 10.0.3
com.apple.driver.DspFuncLib 2.0.5f14
com.apple.iokit.IOAudioFamily 1.8.3fc2
com.apple.kext.OSvKernDSPLib 1.3
com.apple.driver.AppleSMBusController 1.0.10d0
com.apple.iokit.IOFireWireIP 2.0.3
com.apple.driver.AppleHDAController 2.0.5f14
com.apple.iokit.IOHDAFamily 2.0.5f14
com.apple.iokit.AppleProfileFamily 41
com.apple.iokit.IO80211Family 320.1
com.apple.iokit.IONetworkingFamily 1.10
com.apple.driver.IOPlatformPluginFamily 4.7.0a1
com.apple.driver.AppleSMBusPCI 1.0.10d0
com.apple.driver.AppleBacklightExpert 1.0.1
com.apple.driver.AppleSMC 3.1.0d5
com.apple.nvidia.nv50hal 6.3.6
com.apple.NVDAResman 6.3.6
com.apple.iokit.IONDRVSupport 2.2
com.apple.iokit.IOGraphicsFamily 2.2
com.apple.driver.BroadcomUSBBluetoothHCIController 2.4.5f3
com.apple.driver.AppleUSBBluetoothHCIController 2.4.5f3
com.apple.iokit.IOBluetoothFamily 2.4.5f3
com.apple.driver.AppleUSBMultitouch 207.7
com.apple.iokit.IOUSBMassStorageClass 2.6.7
com.apple.iokit.IOSCSIBlockCommandsDevice 2.6.8
com.apple.iokit.IOUSBHIDDriver 4.2.0
com.apple.iokit.IOSCSIMultimediaCommandsDevice 2.6.8
com.apple.iokit.IOBDStorageFamily 1.6
com.apple.iokit.IODVDStorageFamily 1.6
com.apple.iokit.IOCDStorageFamily 1.6.1
com.apple.driver.AppleUSBMergeNub 4.2.4
com.apple.driver.AppleUSBComposite 3.9.0
com.apple.driver.XsanFilter 402.1
com.apple.iokit.IOAHCISerialATAPI 1.2.6
com.apple.iokit.IOSCSIArchitectureModelFamily 2.6.8
com.apple.iokit.IOFireWireFamily 4.2.6
com.apple.iokit.IOUSBUserClient 4.2.4
com.apple.iokit.IOAHCIFamily 2.0.6
com.apple.iokit.IOUSBFamily 4.2.4
com.apple.driver.AppleEFIRuntime 1.4.0
com.apple.iokit.IOHIDFamily 1.6.6
com.apple.iokit.IOSMBusFamily 1.1
com.apple.security.TMSafetyNet 6
com.apple.kext.AppleMatch 1.0.0d1
com.apple.driver.DiskImages 289.1
com.apple.iokit.IOStorageFamily 1.6.3
com.apple.driver.AppleACPIPlatform 1.3.6
com.apple.iokit.IOPCIFamily 2.6.5
com.apple.iokit.IOACPIFamily 1.3.0

rigormortis · Dec 31, 2014

its been a while , but does disk utility show smart status?

if its "verified" then it can be salvaged by erasing ( a full 1 pass erase ) the hard disk and reinstalling or running disk warrior. if says "failing" or "bad" i forgot what the error was, then its bad, and it should be thrown out

if it says "not supported" then you need to run more tests to see if the drive is bad, like seagate's free sea tools utility on a long hard ware test

smart status also shows up on system report, if you call up system report and check the hard disks , you should see an entry for smart

when erasing the hard disk you want to do a single 1 pass erase of 0's . this is called a security erase and it will find bad sectors.

hard disks for the last 21 years lie to the operating system when it comes to bad sectors. all hardware disk errors on a computer's hard disk are fixed on the fly, and corrected and the operating system is never told.

if it was an actual hardware error , like bad sectors, and the operating system found out, then the drive is shot

if it just lost clusters, then you need to find some way of booting the computer maybe on a usb key, so the disk isnt mounted, so the lost clusters can be repaired

disk warrior costs a lot of money , its cheaper to just erase the hard disk and restore from time machine.

if you don't have a time machine backup , now would be a good time to make one

----------

if it finding new errors, then it did last time, then it means that the hard disk is completely shot and should be replaced.

please do us a favor and recycle your old hard disk and do not throw it in the trash, heh

don't buy any software to check the condition of the smart sensor. your mac should already tell you if its bad for free, and you don't need to know the reasons why. all you really need to know is the drive serial # and whether or not that drive is still under warranty. hard drive companies will cover a drive that has failed under warranty, (typically 1 to 5 years ) but they want you to run their hard disk tests, like sea tools

MagicBoy · Dec 31, 2014

There's a known issue with the GPU graphics switching on that machine. Requires a logic board replacement unfortunately, and the replacement program just expired.

http://support.apple.com/en-gb/HT203554

korobokkuru · Dec 31, 2014

Another update

It's not the hard drive.

I tried installing OS X onto my external hard drive and booting from there. Same exact issue.

Could be the RAM or another issue but the GPU Graphics Switching sounds likely to me. There was some good info about it on this thread: https://discussions.apple.com/thread/6486181

Search

Search

MacBook Pro Corrupt Disk... help??

korobokkuru

macrumors newbie

BrianBaughn

macrumors G3

korobokkuru

macrumors newbie

korobokkuru

macrumors newbie

DeltaMac

macrumors G5

korobokkuru

macrumors newbie

korobokkuru

macrumors newbie

BrianBaughn

macrumors G3

Fishrrman

macrumors Penryn

korobokkuru

macrumors newbie

rigormortis

macrumors 68000

MagicBoy

macrumors 68040

korobokkuru

macrumors newbie

Our Staff