please help :(((

Discussion in 'MacBook Pro' started by kdw877, Apr 3, 2017.

  1. kdw877, Apr 3, 2017
    Last edited by a moderator: Apr 4, 2017

    kdw877 macrumors newbie

    Joined:
    Feb 14, 2017
    #1
    i plugged my time machine into my new macbook pro tb and the macbook crashed, i think its corrupted my backup drive. Theres irreplaceable pics on it, this is what disk utlity gives me, is there any hope?

    Code:
    Repairing file system.
    Checking Journaled HFS Plus volume.
    Checking extents overflow file.
    Checking catalog file.
    Missing thread record (id = 2975085)
    Incorrect number of thread records
    Incorrect number of thread records
    Checking multi-linked files.
    Incorrect number of file hard links
    Checking catalog hierarchy.
    Invalid directory item count
    (It should be 30 instead of 31)
    Missing thread record (id = 2973740)
    Invalid directory item count
    (It should be 0 instead of 1)
    Invalid directory item count
    (It should be 0 instead of 1)
    Invalid directory item count
    (It should be 0 instead of 1)
    Missing thread record (id = 2973752)
    Invalid directory item count
    (It should be 0 instead of 1)
    Invalid directory item count
    (It should be 0 instead of 1)
    Invalid directory item count
    (It should be 0 instead of 1)
    Invalid directory item count
    (It should be 0 instead of 1)
    Invalid directory item count
    (It should be 0 instead of 1)
    Missing thread record (id = 2973786)
    Invalid directory item count
    (It should be 0 instead of 1)
    Invalid directory item count
    (It should be 0 instead of 1)
    Invalid directory item count
    (It should be 0 instead of 1)
    Invalid directory item count
    (It should be 0 instead of 1)
    Invalid directory item count
    (It should be 0 instead of 1)
    Invalid directory item count
    (It should be 0 instead of 1)
    Invalid directory item count
    (It should be 0 instead of 1)
    Invalid directory item count
    (It should be 0 instead of 1)
    Invalid directory item count
    (It should be 0 instead of 1)
    Missing thread record (id = 2973844)
    Invalid directory item count
    (It should be 0 instead of 1)
    Invalid directory item count
    (It should be 0 instead of 1)
    Invalid directory item count
    (It should be 0 instead of 1)
    Invalid directory item count
    (It should be 0 instead of 6)
    Invalid directory item count
    (It should be 0 instead of 2)
    Invalid directory item count
    (It should be 0 instead of 1)
    Invalid directory item count
    (It should be 6 instead of 23)
    Missing thread record (id = 2974375)
    Invalid directory item count
    (It should be 0 instead of 7)
    Invalid directory item count
    (It should be 0 instead of 23)
    Invalid directory item count
    (It should be 0 instead of 1)
    Invalid directory item count
    (It should be 0 instead of 3)
    Invalid directory item count
    (It should be 0 instead of 3)
    Invalid directory item count
    (It should be 0 instead of 3)
    Invalid directory item count
    (It should be 0 instead of 3)
    Invalid directory item count
    (It should be 0 instead of 3)
    Invalid directory item count
    (It should be 30560 instead of 30531)
    Invalid directory item count
    (It should be 25 instead of 281)
    Missing thread record (id = 2975528)
    Invalid directory item count
    (It should be 0 instead of 23)
    Invalid directory item count
    (It should be 6 instead of 32)
    Invalid directory item count
    (It should be 191946 instead of 191962)
    Invalid volume directory count
    (It should be 189148 instead of 189151)
    Invalid volume file count
    (It should be 1137379 instead of 1137414)
    Checking extended attributes file.
    Incorrect number of extended attributes
    (It should be 922946 instead of 922949)
    Incorrect number of Access Control Lists
    (It should be 912996 instead of 913001)
    Checking multi-linked directories.
    Invalid parent for directory inode (id = 2563643)
    (It should be 19 instead of 18)
    Invalid name for directory inode (id = 2563643)
    (It should be dir_2563643 instead of temp2563643)
    Incorrect number of directory hard links
    The volume Time Machine could not be verified completely.
    File system check exit code is 8.
    Updating boot support partitions for the volume as required.
    File system verify or repair failed.
    Operation failed…
     
  2. ZapNZs, Apr 3, 2017
    Last edited: Apr 3, 2017

    ZapNZs macrumors 68020

    ZapNZs

    Joined:
    Jan 23, 2017
    #2
    Could I ask for a little more information ...
    1. Is this MacBook Pro TB brand new? - specifically, were you attempting to migrate your files from the Time Machine hard drive to the TB MBP when this happened? Or did something happen to the MacBook Pro while it was connected (but not migrating or backing up), and this problem resulted in power loss to the external?
    2. If so, have you already used the Recovery HD on the MBP TB to reinstall OS X? (that is, do you currently have a working Mac?)
    3. Have you verified the SMART status of the drive? (checking for failure indicators that signify likely or imminent hardware failure - if the answer is yes, and the SMART status is failing, do NOT continue trying to use the drive before you examine the specific errors in detail and consider data recovery options as continuing to muck around with it could make things more difficult to recover)
      ----(After determining how likely this is hardware failure [and, if it is likely or near certain] determining how you want to proceed - i.e., professional data recovery services or attempting to troubleshoot on your own...)----
    4. If you simply plug the malfunctioning Time Machine disk into a working Mac, are you able to navigate through it in Finder? (and, if so, can you navigate to and copy any of the important files you need to a working destination? - you might get read errors, but you may be able to copy over at least some of the files?)
    5. Have you already tried the fsck_hfs repair command? (someone smarter than me would be better to explain this in detail and whether it is appropriate to try on an external drive in this instance)
    6. Do you by chance have access to a program called Disk Warrior?
     
  3. DeltaMac macrumors G3

    DeltaMac

    Joined:
    Jul 30, 2003
    Location:
    Delaware
    #3
    I absolutely agree that you can expect a good fix from the talented Disk Warrior.
     
  4. kdw877 thread starter macrumors newbie

    Joined:
    Feb 14, 2017
    #4
    its already set up but i just wanted to get some old pics from an old backup. I cant navigate it in finder it only shows up greyed out in disk utility as its on a partition on the HD. Ill read up on the fsck thing see what that brings up as i dont have $100 atm for disk warrior lol Ill be devastated if i cant retrieve the pics of my mom im the only one with copies of them :s
     
  5. DeltaMac macrumors G3

    DeltaMac

    Joined:
    Jul 30, 2003
    Location:
    Delaware
    #5
    As you likely did a good number on the disk directory when your Macbook crashed, Disk Warrior is the best at repairing crunched directories. Yes, a good chunk of cash for maybe a one-time need. But, it's a one-trick pony that makes $100 a not-too-expensive way to avoid possibly being "devastated"
    I would suggest, until you have a good plan (getting Disk Warrior would be part of that), that you put that drive aside. If there are problems with the actual data, you get more likely to lose everything each time you attempt, yet fail to fix it.
    You ALSO need to remember that a Time Machine backup has its own challenges, and you need to have a tool that will be able to handle the Time Machine files at the same time. (and again, Disk Warrior gets a star)
     
  6. ZapNZs, Apr 3, 2017
    Last edited: Apr 3, 2017

    ZapNZs macrumors 68020

    ZapNZs

    Joined:
    Jan 23, 2017
    #6
    I agree. If data loss stemming from directory damage would be devastating, Disk Warrior is arguably the tour de force of directory problems. Beyond having it for use in situations where Disk Utility cannot make the repair, I use it every now and then as preventive maintenance on my own drives (some people feel strongly that it is not a maintenance tool - I personally feel periodically rebuilding the directory has some positive benefit with absolute minimal risk.)

    You may be able to find an Apple Authorized service provider that both sells the DW software as well as the DW services, and would perform a rebuild on the drive for a lower fee than the price of buying the software outright. They could also pull detailed SMART health data on the drive if you haven't already, to get a better idea of whether this drive should be retired once you get your data from it.

    On a bright note, compared to the cost of most professional data recovery services, DW is dirt cheap! :)
     
  7. kdw877 thread starter macrumors newbie

    Joined:
    Feb 14, 2017
    #7
    thanks guys, youre right, the photos are worth much more to me. Ill try the fsck then warrior if no luck :)
     

Share This Page