Delete

Disk Utility's "Repair Disk" or "Check Disk" function should only be done while NOT booted from the drive you want to check -- in other words, you should boot from your OS X Install/Restore CD/DVD and run Disk Utility's "Check Disk" and/or "Repair Disk" on your internal hard drive.

Running a "Verify" or "Repair Disk" from Disk Utility while you're booted from the drive you wish to check will produce some errors that can be safely ignored, and you also won't be able to repair certain types of errors unless you boot from an alternate boot disk.

Are you running the repair while booted from the disk you're checking, or are you, in fact, repairing the disk while booted from another disk?
 
The "orphaned blocks" is a relatively minor issue in your directory, and doesn't, by itself, indicate a potential hardware problem of some kind. It's just a software issue in the directory structure, and is also showing a minor error in free block count, which also makes sense because of the orphaned blocks report. The time to get concerned is if Disk Utility does not repair the issue - so, repair the drive (booted to your Recovery partition.) It does little good to run a Verify Disk at that point, as the Repair Disk simply runs the verify procedure anyway, and you already know that error will be reported during a verify.

I expect that the orphaned blocks are more related to some action that you continue with the replacement drive (that is, the nature of how you typically use your software, and your MacBook Pro), and not particularly pointing to the future demise of your hard drive. This is not to say that it's your fault! But, simply a side effect of your normal use, and a file system that is not perfect (and none are!). As a service tech, I nearly always do an fsck at first boot when troubleshooting a variety of problems. Sometimes you see 'orphaned blocks', and there's no way to predict that. You mount the disk, and that clears the orphaned blocks. If that's your only issue, then you just clear it, and move on...

I would also check at Seagate occasionally for firmware updates for your hybrid drive.
 
I did not (and would not) say the issue is "harmless", but I did say it's a "relatively minor" issue that you can easily manage.
 
Mario maybe you could do a fsck -fy on that drive.

Plus are you running any major third system modifier that modify the Finder or something? Some old or bad programming might be messing up, just a thought.
 
You must log in or register to reply here.
Back
Top