Fsck mac how long

Depending on the size of your volume, it may take a while for this process to complete. This will mount the startup volume as a read-and-write file system. Since this feature is built into Intel-based Macs, you can use it to recover data even if the installed macOS volume is corrupted.

Select your startup disk, and click Start Sharing. Specify your external drive and start the process. You have the option to manually copy files. Then connect the external drive you want to use as a destination for your files.

Run the cp -r command. Here, cp is the copy command, and -r runs this command recursively. The first path is the location of the files.

Why not try one of the many other Mac backup tools available to backup your Mac. There are lots of Mac backup options out there, and many of them have features that Apple's default backup app just can't compete with.

Hi thanks for all the info here! I get to the root but then I cannot enter any text. Am I just not giving it enough time to process? I let it run for fifteen minutes.

When I ran the Fsck -fy this is the message I got:. However what I notice is that after ejecting my external HDD the permission problems reappear and I have to reinstall everything using safe boot and the last backup in time machine. Does anyone have any idea if the external HDD or the new ssd or ram creates the problem? Is something failing? Can you help me out with my MacBook Pro? I try to boot fsck on my mac according to your suggestion when it failed to show the HDD.

When I put fsck in, it said command not found. What should I do? Thank you. This was a splendid advice. I used it for a Yosemite system disk. Thank you very much! That was easy. The Mac is telling you that once in S. The trick is how you find the partitions names you might have and fsck them. You sound very impatient, not good for running disk repair.

Be patient, it can take a long time if the drive is large, slow, or failing. If you reboot in the middle of fsck running you can damage the disk and cause data loss. I hope you have a good backup handy. Name required. Mail will not be published required. All Rights Reserved. Reproduction without explicit permission is prohibited. Enjoy this tip?

Subscribe to our newsletter! Thank you! You have successfully joined our subscriber list. Rahul Dev says:. May 25, at pm. Tommy says:. March 28, at am. Luies says:. December 15, at am. Sandeep says:. November 19, at am. January 29, at am.

Jack Johnsman says:. December 29, at am. Jean says:. September 2, at pm. Audra says:. July 21, at pm. November 7, at am. Philippe says:. October 2, at am. Tim says:. August 26, at pm. Rui says:. June 26, at pm. Xavier says:. May 28, at pm. Daniel says:.

May 10, at pm. March 3, at am. Christian McCoy says:. January 5, at am. Candy says:. December 1, at am. Taz Ayafa says:. November 26, at pm. Kimberly Green says:. These signs include your drive suddenly being unrecognizable to your computer, sluggish performance, and random ejections. Common contributors to this issue include mechanical failures and excessive humidity. When you use your Mac, your device will store many of the apps and programs you use on your hard drive.

If this begins to fail, you may begin to notice that your programs stop running as smoothly. Your Mac may take longer to load, or you could struggle to open apps that you use regularly. Corruptions often occur during the writing phase. If a disk has stopped working properly, you may find that you can no longer use certain files or documents. And if left unaddressed over time, these could cause significant damage to the drive.

Locate the disk you want to run fsck on and find its device identifier. You can release the keys once you see white text start to appear on the startup screen. Some white text will scroll by quickly. That command will run the HFS sub-version of fsck on that drive. Quote: Quote: I think it's between 10 and 20 minutes. Did you format with the sparse superblock? Yeah, but your filesystem was unmounted cleanly. I don't know about Doug's or what situation Trevor was referring to.

My situation was caused by an emplode failure during re-synch lost network connection so it got corrupted while it was in RW mode. The manual fsck on each drive and manual database rebuild fixed everything.

Previous Topic Index Next Topic. Print Topic Switch to Threaded Mode. Generated in 0.