You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

MacBook pro late 2011 not booting after smc reset and pram reset

My MacBook Pro late 2011 doesn't boot. It turns of about halfway through the progress bar in the boot screen

I'm not sure if me resetting the SMC and pram caused this but before I did it the Mac worked fine

I can boot into recovery mode and single user mode but not into safe mode

Ive tried repairing the disk through recovery mode but it spits out errors

The same errors are found when I run fsck in single user mode


MacBook Pro 13", macOS 10.13

Posted on Jun 4, 2019 3:20 AM

Reply
Question marked as Top-ranking reply

Posted on Jun 5, 2019 5:21 PM

To install macOS to an external drive see if the laptop will boot into Internet Recovery Mode using Command + Option + R since local Recovery Mode may not work if you have file system issues or a failing drive.


If you are able to install macOS to the external drive, I would suggest running DriveDX to check the health of the internal hard drive especially if you have trouble retrieving your data. If you have a failing drive and have trouble transferring your files, then you should stop and find a better method perhaps using Carbon Copy Cloner or maybe cloning the drive using GNU ddrescue which can work around the errors.

7 replies
Question marked as Top-ranking reply

Jun 5, 2019 5:21 PM in response to Pranav1203

To install macOS to an external drive see if the laptop will boot into Internet Recovery Mode using Command + Option + R since local Recovery Mode may not work if you have file system issues or a failing drive.


If you are able to install macOS to the external drive, I would suggest running DriveDX to check the health of the internal hard drive especially if you have trouble retrieving your data. If you have a failing drive and have trouble transferring your files, then you should stop and find a better method perhaps using Carbon Copy Cloner or maybe cloning the drive using GNU ddrescue which can work around the errors.

Jun 4, 2019 8:18 AM in response to Pranav1203



I dearly hope you have a backup.


If not, you need to NOT erase that drive and keep that drive inside your Mac to use its Recovery HD and to attempt to rescue any files you can.


Buy a new drive. I suggest an SSD drive of at least the 500-ish GB size you have now. You will also need an external enclosure, adapter, or toaster-style enclosure to hold the NEW drive while you work on it.


Install MacOS on it using the external enclosure, boot from it, bring its MacOS up to date, and get it completely ready to be your new drive BEFORE attempting surgery.



Jun 4, 2019 3:46 AM in response to Pranav1203

Verifying storage system

Performing fsck_cs -n -x --lv --uuid D6B008B4-C16A-40E2-BF37-3E973091FAA3

Checking volume

disk0s2: Scan for Volume Headers

disk0s2: Scan for Disk Labels

Logical Volume Group D6B008B4-C16A-40E2-BF37-3E973091FAA3 on 1 device

disk0s2: Scan for Metadata Volume

Logical Volume Group has a 24 MB Metadata Volume with double redundancy

Start scanning metadata for a valid checkpoint

Load and verify Segment Headers

Load and verify Checkpoint Payload

Load and verify Transaction Segment

Incorporate 0 newer non-checkpoint transactions

Load and verify Virtual Address Table

Load and verify Segment Usage Table

Load and verify Metadata Superblock

Load and verify Logical Volumes B-Trees

Logical Volume Group contains 1 Logical Volume

Load and verify A863F28B-97A8-4498-9AE6-19A723B65FB7

Load and verify 2E38B9D8-E92F-485B-A338-33D84B6B7E30

Load and verify Freespace Summary

Load and verify Block Accounting

Load and verify Live Virtual Addresses

Newest transaction commit checkpoint is valid

Load and verify Segment Cleaning

The volume D6B008B4-C16A-40E2-BF37-3E973091FAA3 appears to be OK

Storage system check exit code is 0.

Repairing file system.

Volume was successfully unmounted.

Performing fsck_hfs -fy -x /dev/rdisk2

Checking Journaled HFS Plus volume.

Checking extents overflow file.

Invalid leaf record count

(It should be 12224 instead of 12225)

Checking catalog file.

Invalid sibling link

Rebuilding catalog B-tree.

The volume Macintosh HD could not be repaired.

File system check exit code is 8.

Restoring the original state found as mounted.

Problem -69842 occurred while restoring the original mount state.

File system verify or repair failed.

Operation failed…


Jun 5, 2019 5:10 AM in response to Grant Bennet-Alder

Ohh ****!! my backup driver died a couple of weeks ago. Is there any way I can keepy data on the drive?? Like maybe try and install Mac os on an external drive to boot from it and try to recover my stuff?

If I can, how can I install High Sierra to an external drive??

If needed to I can borrow my sister's Mac for installing or whatever just as long as I can recover the data cause honestly the data is worth more to me than the laptop


Jun 5, 2019 6:54 PM in response to Pranav1203

Years ago, a 1,000 Megabyte drive was a thousand dollars. In that case, the Drive working again was the prize.


Today, a 1,000 Gigabyte drive can be had for under US$100, and retrieving your DATA, if possible, is the prize.


If you had to pay a technician to do this work, they could spend all afternoon fiddling with your drive and still end up with nothing.


So I have very slowly come around to the recommendation that you just replace the boot drive (but use an external enclosure to do the work). Once you have done everything you can: rescued all the files you can, and waited a little while, and re-initialized that drive, if it works -- Merry Christmas, you have a working drive for various uses.


Use an external enclosure and do the work OUTSIDE your Mac so as to not make even more problems. If you want to just use a "found" drive in an external enclosure to do the same work, that will work almost as well, but at the end when you erase the old Boot drive, it may not be savable.


Remember:

• Over 350,000 of the files on a Boot drive are MacOS, which can be perfectly replicated (it does not modify itself) by a new Install on a different drive.

• it is far easier to Mount a drive and copy some files off than to Boot from that same drive.

• If the drive won't Mount, the techniques HWTech posted just above, along with software like Data Rescue from Prosoft can make excursions onto a damaged drive and find some stuff -- but It insists on salvaging those files to a different drive. Writing to that drive could clobber parts of existing files.

MacBook pro late 2011 not booting after smc reset and pram reset

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.