MacBook Pro 2009 starting in Recovery mode (after stop sign) - how to back up data?

Hello,


I have an old Macbook pro from 2009 and it's survived till now, which is unbelievable. However it's time I guess for the hard drive to show its age, and when I was using the browser the MBP froze and when I forced the restart I initially saw the stop sign and then I was taken to the recovery mode.


I haven't backed up my data since a couple of years ago and would like to try whatever I can to get the data back, but not sure what to do to minimize the chances of risking losing the data.


I have tried creating a disk image both from the internal disk or from a folder. Both operations failed with status 5.

While selecting the folder to create the image from, I could see all the folder structure when asked to select the folder, so I am thinking the data is still recoverable?


Could you please help me suggest what to do first to try save the data? I have bought a new MBP so my focus is on the data.


From this question I read I could be able to back up data using command line. Could someone walk me through how to do that?


Thank you to whoever can help!

Arya

Posted on Oct 29, 2022 7:24 PM

Reply
Question marked as Top-ranking reply

Posted on Oct 31, 2022 4:37 PM

If you create and boot from a Knoppix USB stick, then you can easily check the health of the drive. Download the Knoppix Linux DVD .iso file with "EN" in the name for ENglish. Use the Knoppix .iso file as a source for Etcher (Mac/Windows/Linux) which will push the image onto a USB stick to create a bootable Knoppix USB stick. Option Boot the Mac and select the orange icon labeled "EFI" to boot from the Knoppix USB stick. While Knoppix is booting the laptop may appear frozen on the Apple boot picker menu so make sure to give Knoppix lots of time to finish booting.


Once Knoppix boots to the desktop, click the "Start" menu icon on the lower left of the Taskbar and navigate the menus to "System Tools --> GSmartControl". Within the GSmartControl app, double-click on the drive icon to access the drive's health information. Post the complete report here. You should also check the "Error" tab within GSmartControl and post any errors listed there in case the main health report doesn't indicate any issues.


Until the drive's health report is analyzed I suggest not using this laptop & drive in order to keep any potential drive failure from getting worse. If the drive is healthy, then you have several things to try to access the data.

Similar questions

21 replies
Question marked as Top-ranking reply

Oct 31, 2022 4:37 PM in response to arya-md

If you create and boot from a Knoppix USB stick, then you can easily check the health of the drive. Download the Knoppix Linux DVD .iso file with "EN" in the name for ENglish. Use the Knoppix .iso file as a source for Etcher (Mac/Windows/Linux) which will push the image onto a USB stick to create a bootable Knoppix USB stick. Option Boot the Mac and select the orange icon labeled "EFI" to boot from the Knoppix USB stick. While Knoppix is booting the laptop may appear frozen on the Apple boot picker menu so make sure to give Knoppix lots of time to finish booting.


Once Knoppix boots to the desktop, click the "Start" menu icon on the lower left of the Taskbar and navigate the menus to "System Tools --> GSmartControl". Within the GSmartControl app, double-click on the drive icon to access the drive's health information. Post the complete report here. You should also check the "Error" tab within GSmartControl and post any errors listed there in case the main health report doesn't indicate any issues.


Until the drive's health report is analyzed I suggest not using this laptop & drive in order to keep any potential drive failure from getting worse. If the drive is healthy, then you have several things to try to access the data.

Nov 3, 2022 7:15 PM in response to arya-md

Sorry about the delay as I wanted to ponder my response a bit to separate out what I would do versus what you should do since data recovery of a failing device also requires some intuition from noticing the tiniest things. Every failing device is handled a bit differently depending on what is seen in addition to the severity of the failure.


Like I mentioned before the safest option would be to have a professional data recovery service such as Drive Savers attempt to retrieve the data. They provide free estimates and are recommended by Apple and other OEMs.


The drive failure is just beginning, but it is also starting to get enough bad blocks that extreme care must be taken. Currently in the report there are 18 blocks pending reallocation. These 18 blocks will be ones which will cause problems with transferring the data, plus any other bad blocks which have not yet been marked for reallocation yet (the latter unknown bad blocks are the biggest concern). Already 19 blocks have been reallocated and are no longer a concern except for the fact that we know at least 37 blocks have already gone bad. And the report shows some uncorrectable errors which mean some blocks will have data loss. A lot of things go into determining whether to try using the Finder, or some other macOS app to attempt to transfer files to external media, or to first perform a low level bit for bit clone. Also a lot of careful observation needs to be done throughout the whole process as well as monitoring the drive's health to see if the failure is getting worse and how quickly the failure is increasing.


If you just need to recover a small number of extremely critical files, then it may be worth trying to use the Finder or the third party app Carbon Copy Cloner to attempt to transfer a small number of critical files. CCC allows you to select just the files you want to transfer and if it starts to have errors CCC will prompt you if it should skip files which start to produce errors (yes), however, if this transfer is taking too long, then it should be aborted immediately so as not to make the drive failure worse.


If a large amount of data (large size files) need to be transferred, then performing a low level bit for bit (block for block) clone is best. However, this requires using a special command line utility best used from a Linux boot drive since macOS interferes with the process and does not have a precompiled binary version of the utility available. Even if you are familiar with the command line, it is very easy to make a mistake in marking the source & destinations of the clone. When performing this clone you must usually make a decision on when it stop it since there will usually still be blocks that has trouble transferring. Those blocks may be empty space, or contain OS system files, but they may also contain your actual data file....there is no way to know and no one can really advise you on when to give up on the clone.


After you decide the cloning has gotten as many blocks as possible, you will need to see if you can access the clone normally. Sometimes you may need to run Disk Utility to repair the file system, while other times you may need to use a standard data recovery app to locate your files on the clone. It is important to realize, that once you attempt to access the clone, then you will not be able to resume the clone because macOS will likely have made some changes to the clone and resuming the clone will further damage the possibly already damaged file system. I can provide some instructions if you are interested. I have posted them on these forums several times many years ago, so I will likely try to find one of them to link here which may take a bit of time to locate since they were difficult to write up the first time and I haven't performed data recovery in a few years so I'm a bit rusty when trying to provide the specific details to guide you.


The cloning method requires another drive the same size or larger than the failing drive. You will also need yet another drive with sufficient space for storing the data recovered from the clone. You don't want to use the clone for more than accessing the files since you cannot be sure of the integrity of the file system or the OS on it (if it happens to bootable).


Sometimes I may employ both methods on a drive such as this if someone had a few critical files. I would try to pull just those specific files first. Then depending on the importance of the remaining files and the amount of data, and the health of the drive I may continue attempting a standard file transfer, or I may employ the cloning method. It is a very delicate balance with no guarantees on any method and no way to know which path is the correct one until after it is done.


You do have a very important decision to make because you usually only get one chance at recovering data from a failing drive. So be sure to choose wisely.


Dec 6, 2022 5:04 PM in response to arya-md

Unfortunately the Finder is not available from the macOS installer. You can use the Finder if the laptop is able to boot normally or into Safe Mode. Target Disk Mode is another option if you have access to another Mac, but this is an expensive option as you need to proper adapters & cables to connect the two Macs.


You can remove the failing hard drive from laptop and connect it to another Mac using a USB to SATA Adapter.


Another option is to use the Knoppix USB stick to attempt to transfer files from the failing drive to an external drive. As long as Filevault was not enabled, this option should be easy as you can use one of the file manager GUI apps on the Knoppix boot disk. The only difficulty is the external drive needs to be formatted with either the NTFS file system or an HFS (non-journaled) file system. While a drive can be formatted using Knoppix, it will be easier if the drive is formatted as NTFS using a Windows system or the HFS (non-journaled) file system using a Mac. Linux cannot safely write to a journaled HFS volume. HFS is called "MacOS Extended" in macOS.


This all assumes the files can be transferred which is risky.


Oct 30, 2022 6:44 PM in response to arya-md

If the hard drive is failing, then you have a very important decision to make. How important is this data to you? If it is really important, then contact a professional data recovery service such as Drive Savers. Drive Savers provides free estimates and is recommended by Apple and other OEMs.


Keep in mind if the hard drive is failing, then the more you have the drive powered on and the more you attempt to access the data on the failing drive, the worse the drive failure will become where even a professional data recovery service will be unable to recover any data. macOS and most apps (even data recovery apps) are not able to handle the errors produced by a failing drive. The only way to attempt recovery of data from a failing hard drive without using a professional data recovery service is by performing a low level bit for bit clone using a special Linux command line utility which is able to deal with errors produced by a failing drive. However, by the time the clone is complete, many times the failing drive will be dead. Plus it is risky using the command line as it is very easy to make a mistake and destroy the data on the drive you are trying to recover.


You can confirm a drive failure and its severity by checking the health of the hard drive by booting a Linux USB stick. I can provide instructions if you are interested. If the failure is minor & just beginning, then it may be possible to use an app such as Carbon Copy Cloner to attempt transferring the important & critical files, but this is still very risky since some drive failures can progress very quickly.


You may only get one chance at recovering data from a failing drive, so be sure to choose wisely with how you proceed.


I am not a professional data recovery expert, just an advanced one who has successfully recovered data from hundreds of failing drives. I've only ever attempted to recover data from drives where the user was unwilling to pay for a professional data recovery service and was willing to risk my amateur attempts.


Take this as a valuable lesson and don't skimp on your backups. With SSDs in general and especially with the USB-C Macs, you never want to be lax with your backups since it is at best very difficult/nearly impossible to actually impossible to recover any data from an SSD if there is any hardware issues...sometimes corrupt firmware or security enclave is all it takes to permanently lose data on a USB-C Mac. It is impossible to recover accidentally deleted data from an SSD after the Trash has been emptied, plus an SSD can fail at any time without any warning signs (even a brand new SSD). At least with older hard drives there was usually a good chance at recovering some data from a failing drive, although later hard drives this has become more difficult as well even for a professional data recovery service.

Oct 31, 2022 1:35 PM in response to HWTech

@HWTech, thank you for the detailed reply.


I *think* it's hard disk failure but I actually don't know for sure, I probably jumped to conclusions after reading a few other thread, but will need to check hard disk heath, so happy to verify that following your instructions, being aware of the risks.


I should probably also say that I haven't tried anything from the recovery mode (like First Aid).

Once I got the stop sign I tried to restart again and when I got again the same stop sign I tried to make a copy of the disk, getting a different error after the attempts. When I tried to create a disk image and save to a external drive which was not formatted as required I got a different error status than when I tried to save to a drive that was correctly formatted.


So just to say I haven't tried much, so happy to be guided through the process.


Also thank you for the advice concerning SSDs and USB-C Mac, as I actually didn't know that, so one more reason to learn from this.


Nov 1, 2022 4:25 PM in response to HWTech

I have got into an issue when I flash the .iso to a USB drive. I first formatted a brand new drive with a Apple M1 MBP.


After formatting the drive it all looked ok, with Mac OS Extended (Journaled) as format. Once I use Etcher to flash the iso, at the end of the operation the disk turns into an unreadable drive.


I tried a few times, with same outcome. What am I doing wrong?


Nov 1, 2022 7:06 PM in response to arya-md

arya-md wrote:

After formatting the drive it all looked ok, with Mac OS Extended (Journaled) as format. Once I use Etcher to flash the iso, at the end of the operation the disk turns into an unreadable drive.

I tried a few times, with same outcome. What am I doing wrong?

You are doing nothing wrong if Etcher did not report any errors. macOS does not understand the drive layout of the USB stick created this way as it is using a Linux file system (sort of -- its a bit complicated to explain). If you Option Boot the USB stick, you will see the USB stick appear as a boot option on the Apple boot picker menu with an orange icon with a label of "EFI". Option Boot means holding the Option key down immediately after hearing the startup chime.


Nov 2, 2022 7:24 AM in response to HWTech

Oh right, it makes sense! I was able to boot from the Knoppix drive and use GSmartControl app.


I have proceeded with the health check, and I am attaching (picture are not high quality, sorry about that):

report outcome which basically seems to say health check basic test is passed

errors: there are 4 listed, in the picture you can see the data for one of the errors listed, but all the others are exactly the same.


I am hoping that error is not very bad news, if the health check test passed.


I need to add pictures separately, I keep getting an error when adding them.

Nov 2, 2022 8:08 AM in response to arya-md

You need to post the entire report. It has been a while since I used GSmartControl, but I believe you can use the "View Output" or even the "Save As" which will gather information from all the tabs. The "Attributes" tab is really the most important tab as it contains the bulk of the health information.


The error tab reveals the last error was uncorrectable which means there is going to be data loss, but the full report will provide a better picture of the extent of the failure.


As for the picture orientation, iPhones & iPads tend to rotate pictures so it is best to "Edit" the picture on the iPhone/iPad by clicking the "Edit" option when viewing the photo on the iPhone/iPad and selecting rotate and confirm to save the changes. Definitely rotate the pictures before uploading even if you must use the Windows system to do so.

Nov 14, 2022 2:29 PM in response to HWTech

Hi HWTech,


Thank you for the very clear and detailed answer, and sorry for disappearing from this conversation.


If you just need to recover a small number of extremely critical files,
then it may be worth trying to use the Finder or the third party app
Carbon Copy Cloner to attempt to transfer a small number of critical
files. CCC allows you to select just the files you want to transfer
and if it starts to have errors CCC will prompt you if it should skip
files which start to produce errors (yes), however, if this transfer is
taking too long, then it should be aborted immediately so as not to make
the drive failure worse.

I am ok to try to recover the data, even if that means losing it. I don't have many files to save, and they are small in size, so these options you mentioned should be feasible.

When you say "use the Finder" to transfer files, do I need another MBP to use it, or is something I could do from the recovery mode?


When I found out about the problem in booting the system, and I tried to "create disk image from a folder" I could see all the folders. Could that mean that since the issue came up when booting the laptop, the bad blocks are affecting the OS portion of the data, and that's why the boot couldn't be done? Thinking whether that means I have more chances my data is unaffected.


Sometimes I may employ both methods on a drive such as this if someone
had a few critical files. I would try to pull just those specific files
first. Then depending on the importance of the remaining files and
the amount of data, and the health of the drive I may continue
attempting a standard file transfer, or I may employ the cloning method.
It is a very delicate balance with no guarantees on any method and no
way to know which path is the correct one until after it is done.

Using both method is what I was thinking of when reading your explanation about block for block cloning. Once I am sure I got the files I needed (not many) I can then attempt to recover also files that it would be nice if I could save them.


I'll try to find the posts you have written in the past regarding the cloning via command line, to "prepare" for what I will need to do for the recovery.


Thank you!

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

MacBook Pro 2009 starting in Recovery mode (after stop sign) - how to back up data?

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