Superdrive needs repair - should i do it in Belgium or the US?

hi,
i bought a macbook in the US in July. then i moved to Belgium. about a week ago my superdrive quit working - makes funny noises and won't read anything. I'm going back to the States for a couple of weeks for the holidays, so I'm wondering if I should just get it fixed there, as things seem to be slower in Europe... my defunct ipod earphones took two weeks to be replaced here... Anyone have turnaround times for repairs in Belgium / the US?
oh yes, and i've got the 3-yr warranty which is supposed to cover international repairs.
thanks!!
-Lucy

The U.S. turnaround is usually 7 to 10 business days when you go to an Apple retail store. Of course if parts aren't available, it won't matter what the usual turnaround time is. You should call the stores you are near to find out if parts are available.
http://www.apple.com/buy/
and equivalent link on
http://www.apple.com/be/

Similar Messages

"Volume needs Repair" -Disk Utility--what do i do?

So, my computer was freezing & I had the insight to run Disk Utility on the Repair part, everything comes up great, but on verify, under "Network"--Volume comes up needing repair. I looked it up under About the Mac & see that Volume is empty of info. Here is the report:
"Checking volume bitmap.
Volume bit map needs minor repair
Checking volume information.
Invalid volume free block count
(It should be 3922629 instead of 3922551)
The volume Macintosh HD needs to be repaired.
Error: The underlying task reported failure on exit"
Don't know if it matters but the indented portions of the report were in red, otherwise, in black.
What exactly am I to do with this information? Thanks!

In this instance, "Volume" refers to the hard drive. (I quizzed my fiancée - she thought of speaker loudness too... )
10.1, 10.2 etc is the Mac Operating System version number. (ie My eMac is running Mac OS 10.4.9)
If you flip down the CD/DVD drive door on the front of your eMac, there is a sticker that has the serial number, a barcode, then a series of information.
In my case:
1.25G HZ/512MB/160GB HD/DVD-RW/CD-RW/56K MDM
Which means
1.25 GHz processor
512MB of RAM
160GB hard disk drive
DVD & CD burner
56k modem
Note that the "160GB" drive actually only holds 149GB of data - and will show up in Disk Utility as such, because of the difference between binary and actual bit sizes... (check out wikipedia...)
When looking at the list of drives to examine in Disk Utility, the internal hard drive will show up as "internal" in the list of attributes at the bottom of the page... (ie when you click on it, it then shows you
Disk Description - ST.......
Connection BUS - ATA
Connection Type - Internal
Connection ID - Device 0
SMART status should "work" (ie tell you if the drive is good/bad) because you're looking at the internal drive, not an external one.
All that said and done... I still strongly suggest looking inside the eMac's inspection hatch on the base of the computer... if your eMac is freezing up for no apparent reason, it's much more likely to be the capacitor issue than an error found by Disk Utility...

I need repair pst in my mail faster

I try to import pst file, but it says "invalid file format." File - .pst. Why I can't open file? I need repair pst in my mail faster.

Based on the error information, your PST file should be corrupt or damaged. You should first check the size of the PST file,
1. If PST file size is 0. Then your PST file does NOT contain any recoverable data. You should check the source of the PST file and make another copy, or obtain a backup from your backup media. If you cannot get another copy, then you can find
out the media where you have stored your PST file in the past, for example, an external USB drive, and try
DataNumen Outlook Drive Recovery to scan and recover the data from the drive directly.
2. If PST file size is not zero, then it is still possible that some data are existing in your PST file and you can recover them.
There are a lot of online resources discussing about how to recovering corrupt or damaged PST files.
First, the Microsoft offical tool scanpst, also called Inbox Repair Tool, can repair the PST file, you can refer the following articles:
http://office.microsoft.com/en-001/outlook-help/repair-outlook-data-files-pst-and-ost-HA010075831.aspx
http://support.microsoft.com/kb/272227
https://support.microsoft.com/kb/287497
Second, a lot of Outlook MVPs also discussing this topic on their own websites:
http://www.msoutlook.info/question/77
http://www.slipstick.com/problems/pst-repair/repair-a-damaged-personal-folders-pst-file/
Third, there are many third-party Outlook recovery tools you can try, below is a list of them:
http://www.datanumen.com/outlook-repair/compare.htm
Nearly all these tools provide a free trial so you can try first to see if a tool works before purchase it.
Good luck!

Computer says disk needs repair

My laptop keeps on saying the disk needs repair or back up. I have done the backup disk and the problem still continues.

Your hard disk may be starting to fail and will have to be replaced.
What model is your laptop?
Are you still under warranty?
******Clicking the Thumbs-Up button is a way to say -Thanks!.******
**Click Accept as Solution on a Reply that solves your issue to help others**

HT4522 WHAT should I do?-the message says "internal disc needs repair"

WHAT SHOULD I DO? THE MESSAGE re. MY TIME CAPSULE says "INTERNAL DISC NEEDS REPAIR"

Please check out the following Pondini Time Machine troubleshooting article.

Disk Utility - Partition map needs repair because a data partition needs loader space.

I just finished setting up both my OSX and Windows installs from scratch after fitting an SSD, which in-turn was right before my logic board died and Apple replaced it, now it looks like I have some sort of hard drive issue brewing.
This was my plan for the SSD, and how it currently displays in Disk Utility although that wasn't the case earlier:
And in Terminal:
My intention was to have two boot partitions for each OS, 'Macintosh HD' and 'Win 7 Pro' and a third shared data partition 'Projects' on the SSD, which I made in Drive Genius after installing Boot Camp. I don't want Macintosh HD accessible from Windows because I'll be using Paragon HFS+ or MacDrive to give write access and don't want OSs stomping on other OSs turf, hence needing three partitions. Everything looked fine until I just checked Disk Management under windows and realised it couldn't see the Projects volume. Even though it's fine in OS X, it was just marked black/unallocated space.
So I booted back into OSX, all my files look fine so I ran Disk Utility and the Partition tab looked really odd - unfortunately I didn't get a screenshot. All volumes reported their size correctly but visually, Macintosh HD took up most of the drive. I could see 'Windows 7 Pro' under this, but the Partition Layout section had a scrollbar, which if I scrolled down showed 'Projects' squished into a tiny gap at the bottom. I ran a Verify, which reported no problems, and at some time since the Partition Layout has reverted to how it should look (as in the screenshot above), with 'Projects' book-ended by "Macintosh HD' and 'Windows 7 Pro'.
Now when I run a Verify on Macintosh HD or Projects volumes, it says there's no problem, but if I run one on the drive, I get this message:
Volume Macintosh HD on disk0s2 has 0 bytes of trailing loader space and it needs 134217728 bytes
Problems were found with the partition map which might prevent booting
Error: Partition map needs repair because a data partition needs loader space.
I've only managed to find one other mention of this error here, but the fix is not relevant to me because I don't have Sophos installed. I've tried Single User/Safe Mode but it just boots into normal mode, so I can't do a fsck -fy.
** /dev/rdisk0s2 (NO WRITE)
Can't open /dev/rdisk0s2: Permission denied
That value in bytes is exactly 128mb, so I suspect the problem lies with one of the invisible partitions that show up in iPartition and Disk Management under Windows, but not in Disk Utility. I have backups and I suspect the root of the problem is partitioning in iPartition after installing Boot Camp, but I've never had issues with this approach in the past so I'm wary of just giving up and reinstalling Windows again will be massive hassle because I no longer have a SuperDrive and last time it refused to install from USB.
Anyone have any idea what's going on? It seems like the sort of issue Disk Utility should just handle, at least in Recovery mode, but it's not playing ball. It also doesn't seem like a massive problem since my files all look fine and performance is OK, so I'm reluctant to do anything major.
I'll update with a shot of the drive in Disk Management from Windows in a few minutes, in case that sheds light on anything. Thanks!

Similar issue here. I manually partitioned my hard disk for triple boot (using Gparted on Linux), then everything was just fine until I ran bootcamp, to do something as simple as create a boot USB.
I get the same error as a result and have to work my way into booting, by resorting first to a Linux live USB, then restarting from the live USB, to finally reach my rEFInd boot manager, or whichever boot manager should be initialized at startup.
I suppose that the cause in my case is that some operation "scratched" the protective MBR. See this:
http://www.mactech.com/articles/mactech/Vol.23/23.03/APMtoGPT/index.html
I am hoping to fix it using an external Yosemite installation media: see this guide -
http://www.macworld.com/article/2367748/how-to-make-a-bootable-os-x-10-10-yosemi te-install-drive.html
And as a last resort to reinstall.
I'll admit I am negatively surprised. I need this computer for professional reasons, and for the sake of "preserving the integrity of OSX", measures defined by Apple instead tend to make partitions far easier to damage. And this problem seems to affect a number of users.
As for what I have to go through to fix it: a 5GB download, during which I have to register my credit card to the Apple Store. "Pay first, get your free software next."
IF Disk Utility can fix it, from the external media, then fair enough. The hassle is unpleasant but it files as "a choice".
Otherwise you can file it safely under software design calamity.

Can I purchase Mountain Lion and make a flash drive bootable? I do not want to install it on my Macbook Pro. I have Snow Leopard on my Macbook Pro now, and due to my hard drive needing repair I need to boot off of another source, like my flash drive.

Can I purchase Mountain Lion and make a flash drive bootable? I do not want to install it on my Macbook Pro. I have Snow Leopard on my Macbook Pro now, and due to my hard drive needing repair, I need to boot off of another source, like my flash drive. I am in Paris and my Snow Leopard DVD is in Texas.

Mac OS X has a built-in disk diagnostic and repair program called fsck or file system consistency check. Here’s how to verify and repair your startup disk with fsck. As soon as you hear the startup tone, press and hold Command-S on the keyboard. Keep holding down those keys until you see a black screen with white lettering. This is called “booting into Single User Mode.” As the Mac boots in this mode, the screen reports each step of the process. The line should end in root#. Right after the root# prompt, enter the following: /sbin/fsck -fy
If repairing the disk in single user mode fails, it means one of two things. Either your hard drive itself is failing (a hardware failure), or the directory damage on your hard drive is beyond the capability of the built-in repair procedures in OS X.

Mac Pro Slow Shutting down Disk Ut says needs repair

Hi hope someone can help,
My mac pro has been taking a long time to shut down recently and this morning when i booted up all i had was a black screen with my mouse pointer (really weird).
I used Disk Utility to "verify disk" and it said that repairs were necessary. Here's the log:
Aug 24 08:31:55: Disk Utility started.
Verifying volume “Aygies Raid”
Checking HFS Plus volume.
Checking Extents Overflow file.
Checking Catalog file.
Incorrect block count for file PACESupport.plist
(It should be 0 instead of 1)
cking multi-linked files.",0)
Checking Catalog hierarchy.
Checking Extended Attributes file.
Checking volume bitmap.
Checking volume information.
@ needs to be repaired.",1)
Aygies Raid
Error: The underlying task reported failure on exit
Disk Utility stopped verifying “Aygies Raid” because the following error was encountered:
The underlying task reported failure on exit
1 HFS volume checked
Volume needs repair
I have a clone of my drive on an external drive so i booted from that i tried to repair permissions on mac pros drives but it said repairs weren't needed, Log:
Verifying volume “Aygies Raid”
Checking HFS Plus volume.
Checking Extents Overflow file.
Checking Catalog file.
Checking multi-linked files.
Checking Catalog hierarchy.
Checking Extended Attributes file.
Checking volume bitmap.
Checking volume information.
The volume Aygies Raid appears to be OK.
Mounting Disk
1 HFS volume checked
Volume passed verification
But then i booted from the mac pro again and it said that it needs repair! I used disk warriour and this is its log:
DiskWarrior scanned the disk named "Aygies Raid" checking all files and folders for damage and potential
compatibility problems.
Permissions:
Started verify/repair permissions on disk disk2 Aygies Raid
Determining correct file permissions.
The privileges have been verified or repaired on the selected volume
Verify/repair finished permissions on disk disk2 Aygies Raid
Disk: "Aygies Raid"
The Property List data was checked in 17,785 files.
The Resource Data was checked in 9,721 files.
The maximum Folder Depth on this disk is 17. This does not exceed the maximum recommended depth.
The System Symbolic Link Files were checked and no problems were found.
Location: "Desktop"
File: ".a23t.obdev.LSD.plist"
Detected that Property List data is damaged and cannot be repaired.
XML parser error:
Unexpected character
at line 1
Old-style plist parser error:
Unexpected character '0x4' at line 1
Location: "Aygies Raid/Users/aygie/Library/Preferences/"
File: "com.SysternatemsCorporation.StudioExcellence.plist"
Detected that Property List data is damaged and cannot be repaired.
XML parser error:
Unexpected character at line 1
Old-style plist parser error:
Unexpected character '0x0' at line 1
Location: "Aygies Raid/Users/aygie/Library/Preferences/"
File: "com.EtworataCorporation.Zonesys.plist"
Detected that Property List data is damaged and cannot be repaired.
XML parser error:
Unexpected character at line 1
Old-style plist parser error:
Unexpected character '0x0' at line 1
Location: "Aygies Raid/Users/aygie/Library/Preferences/"
File: "com.AppersEurope.Sickle.plist"
Detected that Property List data is damaged and cannot be repaired.
XML parser error:
Unexpected character at line 1
Old-style plist parser error:
Unexpected character '0x0' at line 1
Location: "Aygies Raid/Users/aygie/Library/Preferences/"
File: "com.Roverbetter.Eclecticism.plist"
Detected that Property List data is damaged and cannot be repaired.
XML parser error:
Unexpected character at line 1
Old-style plist parser error:
Unexpected character '0x0' at line 1
Location: "Aygies Raid/Users/aygie/Library/Preferences/"
File: "com.Hostcyte.Craziness.plist"
Detected that Property List data is damaged and cannot be repaired.
XML parser error:
Unexpected character at line 1
Old-style plist parser error:
Unexpected character '0x0' at line 1
Location: "Aygies Raid/Users/aygie/Library/Preferences/"
Explanations:
Folder Depth: This number indicates how many folders are nested inside each other. If a disk contains only three
folders and Folder A is inside Folder B and Folder B is inside Folder C, then this disk has a maximum folder depth of
three. Folders nested too deeply can cause software compatibility problems.
Property List: This is a standard file format for storing data and is often used to store preferences. The names of
these files normally end with a .plist file extension. Corrupt property list files can cause system instability.
Resource Data: This is an older file format for storing data and was often used to store preferences. The names of
these files normally end with a .rsrc file extension. Corrupt resource data files can cause system instability.
System Symbolic Link Files: These are files used by the operating system that are similar to aliases. If these files are
damaged it may prevent startup or cause system instability.
Time: 24/8/07 08:44:56
DiskWarrior Version: 4.0
Went back to Disk utility and now it says that my hard drive doesn't need repair! whats going on! can anyone help?!
Thank you

Two things off the top:
128MB are GUID partitions that are not user volumes.
There is also a 200MB EFI partition as well.
Drive Genius needs to get their program updated.
You need to work from an "emergency" boot drive to repair your boot drive, RAID or no. I hope you are and not from CD or DVDs.
Forget about Permissions. They are very minor. They only have to do with ownership and security and based on what is in
/Library/Receipts
Trying to verify? all you want to do is repair and rebuild.
If you ran DU and DW and did repair and rebuild and WROTE NEW DIRECTORY and the problem remains, erase and restore, or...
+I am useless with RAID and have no idea...+
Don't use it except to test, learn, experiment with. But not for system drive.
Above I asked, "are these a matched pair of drives" ie, same make, (looks like same size), vendor, model? they should be. Less chance of trouble if nothing else.
ON the boot volume, do a Get Info when you click on the drive, look for "Ignore Ownership on this Volume" and make sure it is NOT CHECKED. It can't be to repair permissions and be bootable.
The underlying cause of disk errors may be marginal or bad RAM. Test those FBDIMMs. Run Apple Hardware Test and Memtest (even Microsoft uses Memtest for Vista).
Drives rarely break. Systems do. Directory and btree catalogue and volume information blocks do.

Disk Utility: "Volume needs repair" - what to do?

I just ran Verify Disk and got this result:
Verifying volume “iBook HD”
Checking HFS Plus volume.
Checking Extents Overflow file.
Checking Catalog file.
Incorrect block count for file Database3_BROKEN-journal
(It should be 25 instead of 0)
0
Checking multi-linked files.
Checking Catalog hierarchy.
Checking Extended Attributes file.
Checking Extended Attributes file.
,1)
1733913 /Library/Logs/Console/501/console.log.0
Overlapped extent allocation (file 1734737)
Checking volume bitmap.
Volume Bit Map needs minor repair
Checking volume information.
Invalid volume free block count
(It should be 8593446 instead of 8593471)
The volume iBook HD needs to be repaired.
Error: The underlying task reported failure on exit
1 HFS volume checked
Volume needs repair
How do I repair this volume?
bob.m.

bob:
Disk Utility reports "Underlying task reported failure" when repairing a volume is a serious directory error which Disk Utility cannot repair.
•I suggest you read through the article.
•Then, if you do not have an up-to-date backup, it will be a good idea to try to save as much as you can of your data.
•The article suggests using a third party utility. Disk Warrior and Tech Tool Pro are the best utilities for this job. You will need to get one of them and run it, by booting from the CD, or installing it on an external firewire drive or on a second Mac which you can then run in Firewire Target Disk Mode.
Please do post back with further questions or comments.
Good luck.
cornelius

Hard Drive needs repair? - if so, how?

Dear all,
I have used the Disk Utility software to check my hard drive and it gave me an error message. I used "Verify Disk" and the message was the following: "Disk Utility stopped verifying Macintosh HD" because the following error was encountered: "Filesystem verify or repair failed." In addition to this, in the details shown in the little window under "First Aid" the following message came up: "The volume Macintosh HD needs to be repaired."
Since the button "Repair Disk" was unavailable, I tried the "Verify Disk Permissions" button. Once permissions verification was completed (although a number of errors were reported in the detailed report given), I tried the "Repair Disk Permissions" button. The result of this latest action was again a series of error messages in the detailed report but at the end the permissions repair was completed. At the end of this process I was still not able to "Repair Disk."
I am writing to see based on your experiences what is the likely problem in my HD and secondly how I can fix the HD. What should I do to repair the HD?
Any suggestions and thoughts would be most appreciated.
Regards,
R

First off: Back up any and all critical data right away.
You need to start up from your Leopard disc and use Disk Utility (from the Installer Menu) to repair your hard drive. If any errors can't be repaired, try again. If they still can't be repaired, your options are to invest in Disk Warrior (about $100) or erase your hard drive, reinstall the OS and restore your data.
~Lyssa

Message from Disk Utility: iBook HD "Volume needs repair"

I just ran the "Verify Disk" routine and got this error message: "First Aid Failed" because "the underlying task reported failure on exit".
In verifying my "iBook HD" volume, the following errors were reported:
(1) "incorrect number of thread records" in the Catalog file.
(2) "Volume Bit Map needs minor repair"
(3) "Invalid volume free block count (should be 7719070 instead of 7719077)"
(4) The volume iBook HD needs to be repaired.
I would have run the "Repair Disk" routine, but its button wasn't highlighted, so I couldn't do this.
What to do now?
(by the way, the Disk Permissions are all OK)

If I were buying one, I think I'd hit Amazon (solely because of price):
http://www.amazon.com/gp/offer-listing/B0028Z1J32/ref=dpolpnew?ie=UTF8&condition=new
Some info on NewerTech NuPower batteries:
http://www.newertech.com/products/ibookg414_batt.php
http://www.newertech.com/tech_support/newerbatteryconditioning.php
Apple's recommendations for battery usage for optimal battery life and lifespan:
http://www.apple.com/batteries/notebooks.html

A crash, volume needs repair?

Hi, I have no idea what has happened. It's embarrassing but I can't even tell you accurately what OS X I was using but all my software was up to date. When I try to open applications like Safari, it says "you cannot use the application Safari with this version of Mac OS X" The same goes for iTunes and other apps. Some programs just quit unexpectedly when I try to open them. Seems like it reverted back to a very old operating system I didn't even know existed. Even the JPEGs open with a different program I don't use. When I click "about this mac" it says the memory capacity is 512 MB when I know it usually 250 GB and I currently have 25 GB free. I tried Disk Utility and the error messages read exactly as followed: Volume bitmap needs minor repair. Invalid volume free block count (it should be 6873884 instead of 6873859) The volume Machintosh HD needs to be repaired. Error: the underlying task reported failure on exit. First Aid failed. Disk Utility stopped verifying "Machintosh HD" because the following error was encountered: The underlying task reported failure on exit. HFS volume checked volume needs repair.
I stopped messing with it because I have no idea what to do and I don't want to make it any worse. I have installation disks buried in storage but I'll get replacements if that's what it is. I'm panicked. Please help

Welcome to Discussions - boot from your install disc and use Disk Utility to repair your volume. If that fails, get hold of DiskWarrior and use that.
1. Insert the Mac OS X Install disc that came with your computer, then restart the computer while holding the C key.
2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu. (In Mac OS X 10.4 or later, you must select your language first.)
Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.
3. Click the First Aid tab.
4. Click the disclosure triangle to the left of the hard drive icon to display the names of your hard disk volumes and partitions.
5. Select your Mac OS X volume.
6. Click Repair. Disk Utility checks and repairs the disk.
When you have finished, reboot and repair permissions from your hard drive.

HD constantly needs repair

If I were to run VERIFY DISK every day on my MacBook I would get the same results: files differ by one file and folders differ by one folder...requiring a REPAIR DISK. This is getting old...how can I determine which file is the culprit here?
I obviously don't run REPAIR DISK every day, but I've verified it may days in a row and it always needs it. It seems to hold for maybe 8-10 hours before something goes wrong with this one mystery file.

Larry McJunkin wrote:
V.K....I know I have to repair from the OS disk...been in the computing business since 1983 Just thought there might be some trick to finding the offensive file, since there is always just one file and one directory. Every other Mac I've had has never given me this specific problem.
I'll try Disk Warrior, but won't hold my breath. If I end up having to reformat, I'll just move off my data, reinstall SL and updates, then all 97 app (yuck) as bringing back a clone just might bring back the problem. Remember, it's a "file" causing the problem...not a sector on the drive.
what is the exact error message? does it say that the number of files is different by one? then reformatting (not just erasing ) the drive and cloning the clone back will fix the problem and won't reintroduce any back. file system error of that sort generally means one of two things
1. an orphaned file that lost its place in the directory. running disk repair should fix that and the orphaned file will be placed in the lost+found folder at the top level of the drive.
2. a leaking inode that's pointing to a nonexistent file or folder. this again ought to be fixed by disk repair. but either way doing a file level cloning can't carry over problems like this to the clone. just don't do a block level cloning and you'll be fine.
Message was edited by: V.K.

TM disk needs repair but won't unmount.

Hi,
I've been having problems with this TM disk since new but I can't work out what to do. The disk is a Seagate 1.5TB with my MacPro backed up to it and a sparse image on it as my MacBook backup.
The disk only has one volume on it. It has done strange things in the past like return an error on the initial backup of the MacPro after about 900GB of data and when I wiped the drive and tried backing up again it returned an error at about the same stage. Subsequent incremental backups worked so I continued to use it but I have never been able to eject the drive. I have always got the "something is using it" dialog box. I could only safely power it off by restarting the MacPro and turning it off before it booted. I checked the disk in disk utility and it said it needed repair but could not be repaired. After hearing about trouble with these drives I returned it for a replacement. I got an error on the first backup again with the new drive but subsequent incremental backups were OK so I left it. I checked it in disk utility yesterday and it said it needed repair but would not unmount for the repair. I have reset the FW800 port in the past and that didn't seem to make any difference. Other drives in this enclosure (SOHO Tank, Oxford chip) work and unmount OK. I don't know whether this is a TM issue or I've got another flakey drive. I'm tempted to send the drive back to Seagate again as I don't feel secure with this as my backup.
Also, occasionally when I go into TM via the TM icon in the dock, I only see backups up to the day before yesterday in the timeline at the side. If I cancel TM and relaunch I get the full set in the sidebar (yesterday and hourlies for today).
Any thoughts?
Thanks,
Brian

Magicpony wrote:
Hi,
I've been having problems with this TM disk since new but I can't work out what to do. The disk is a Seagate 1.5TB with my MacPro backed up to it and a sparse image on it as my MacBook backup.
If possible, you should partition the drive, so the MacPro's backups are in their own, exclusive space. If you ever want or have to delete them, it will be extremely difficult and take a very long time. See #4 in the Frequently Asked Questions *User Tip,* also at the top of this forum.
Other drives in this enclosure (SOHO Tank, Oxford chip) work and unmount OK.
Try repairing it from the copy of Disk Utility on your Install disc. (Boot up from it, select your language, then on the next screen select Utilities from the menubar, then +Disk Utility.)+
Also, occasionally when I go into TM via the TM icon in the dock, I only see backups up to the day before yesterday in the timeline at the side. If I cancel TM and relaunch I get the full set in the sidebar (yesterday and hourlies for today).
Try the things in #E4 of the Time Machine - Troubleshooting *User Tip,* also at the top of this forum.
It's rather odd, but renaming your computer may help: http://docs.info.apple.com/article.html?path=Mac/10.6/en/21208.html

Disk Permissions constantly need Repair

Hi,
I've just upgraded to 10.6.5 and noticed that each time I log in, my disk permissions need repair. I've updated everything, but still seem to have permissions problems. Any help would be appreciated. These are the errors.
Many thanks!
Permissions differ on "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Classes/dt.jar", should be lrwxr-xr-x , they are lrw-r--r-- .
Repaired "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Classes/dt.jar".
Permissions differ on "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Classes/jce.jar", should be lrwxr-xr-x , they are lrw-r--r-- .
Repaired "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Classes/jce.jar".
Permissions differ on "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Classes/jconsole.ja r", should be lrwxr-xr-x , they are lrw-r--r-- .
Repaired "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Classes/jconsole.ja r".
Permissions differ on "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Classes/management- agent.jar", should be lrwxr-xr-x , they are lrw-r--r-- .
Repaired "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Classes/management- agent.jar".
User differs on "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib", should be 0, user is 95.
Repaired "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib".
Permissions differ on "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib/dt.jar", should be -rw-r--r-- , they are -rwxr-xr-x .
Repaired "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib/dt.jar".
Permissions differ on "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib/jce.jar", should be -rw-r--r-- , they are -rwxr-xr-x .
Repaired "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib/jce.jar".
Permissions differ on "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib/management -agent.jar", should be -rw-r--r-- , they are -rwxr-xr-x .
Repaired "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib/management -agent.jar".
Permissions differ on "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib/security/b lacklist", should be lrwxr-xr-x , they are lrw-r--r-- .
Repaired "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib/security/b lacklist".
User differs on "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Libraries", should be 0, user is 95.
Repaired "System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Libraries".
Permissions differ on "System/Library/Java/Support/Deploy.bundle/Contents/Resources/JavaPluginCocoa.b undle/Contents/Resources/Java/deploy.jar", should be lrwxr-xr-x , they are lrw-r--r-- .
Repaired "System/Library/Java/Support/Deploy.bundle/Contents/Resources/JavaPluginCocoa.b undle/Contents/Resources/Java/deploy.jar".
Permissions differ on "System/Library/Java/Support/VisualVM.bundle/Contents/Home/profiler3/lib/deploy ed/jdk15/hpux-pa_risc2.0/libprofilerinterface.sl", should be -rw-r--r-- , they are -rwxr-xr-x .
Repaired "System/Library/Java/Support/VisualVM.bundle/Contents/Home/profiler3/lib/deploy ed/jdk15/hpux-pa_risc2.0/libprofilerinterface.sl".
Permissions differ on "System/Library/Java/Support/VisualVM.bundle/Contents/Home/profiler3/lib/deploy ed/jdk15/hpux-pa_risc2.0w/libprofilerinterface.sl", should be -rw-r--r-- , they are -rwxr-xr-x .
Repaired "System/Library/Java/Support/VisualVM.bundle/Contents/Home/profiler3/lib/deploy ed/jdk15/hpux-pa_risc2.0w/libprofilerinterface.sl".
Permissions differ on "System/Library/Java/Support/VisualVM.bundle/Contents/Home/profiler3/lib/deploy ed/jdk16/hpux-pa_risc2.0/libprofilerinterface.sl", should be -rw-r--r-- , they are -rwxr-xr-x .
Repaired "System/Library/Java/Support/VisualVM.bundle/Contents/Home/profiler3/lib/deploy ed/jdk16/hpux-pa_risc2.0/libprofilerinterface.sl".
Permissions differ on "System/Library/Java/Support/VisualVM.bundle/Contents/Home/profiler3/lib/deploy ed/jdk16/hpux-pa_risc2.0w/libprofilerinterface.sl", should be -rw-r--r-- , they are -rwxr-xr-x .
Repaired "System/Library/Java/Support/VisualVM.bundle/Contents/Home/profiler3/lib/deploy ed/jdk16/hpux-pa_risc2.0w/libprofilerinterface.sl".
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Classes/dt.jar", should be -rw-r--r-- , they are lrwxr-xr-x .
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Classes/dt.jar".
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Classes/jce.jar", should be -rw-r--r-- , they are lrwxr-xr-x .
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Classes/jce.jar".
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Classes/jconsole.jar ", should be -rw-r--r-- , they are lrwxr-xr-x .
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Classes/jconsole.jar ".
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Classes/management-a gent.jar", should be -rw-r--r-- , they are lrwxr-xr-x .
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Classes/management-a gent.jar".
User differs on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/lib", should be 95, user is 0.
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/lib".
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/lib/dt.jar", should be lrwxr-xr-x , they are -rw-r--r-- .
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/lib/dt.jar".
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/lib/jce.jar", should be lrwxr-xr-x , they are -rw-r--r-- .
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/lib/jce.jar".
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/lib/management- agent.jar", should be lrwxr-xr-x , they are -rw-r--r-- .
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/lib/management- agent.jar".
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/lib/security/bl acklist", should be -rw-r--r-- , they are lrwxr-xr-x .
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/lib/security/bl acklist".
User differs on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Libraries", should be 95, user is 0.
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Libraries".
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Resources/JavaPlugin Cocoa.bundle", should be drwxr-xr-x , they are lrwxr-xr-x .
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Resources/JavaPlugin Cocoa.bundle".
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Resources/JavaPlugin Cocoa.bundle/Contents/Resources/Java/deploy.jar", should be -rw-r--r-- , they are lrwxr-xr-x .
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Resources/JavaPlugin Cocoa.bundle/Contents/Resources/Java/deploy.jar".
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Resources/JavaPlugin Cocoa.bundle/Contents/Resources/Java/libdeploy.jnilib", should be -rwxr-xr-x , they are lrwxr-xr-x .
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Resources/JavaPlugin Cocoa.bundle/Contents/Resources/Java/libdeploy.jnilib".
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/A/Resources/VisualVM.bundl e/Contents/Home/profiler3/lib/deployed/jdk15/hpux-pa_risc2.0/libprofilerinterfac e.sl", should be -rwxr-xr-x , they are -rw-r--r-- .
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/A/Resources/VisualVM.bundl e/Contents/Home/profiler3/lib/deployed/jdk15/hpux-pa_risc2.0/libprofilerinterfac e.sl".
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/A/Resources/VisualVM.bundl e/Contents/Home/profiler3/lib/deployed/jdk15/hpux-pa_risc2.0w/libprofilerinterfa ce.sl", should be -rwxr-xr-x , they are -rw-r--r-- .
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/A/Resources/VisualVM.bundl e/Contents/Home/profiler3/lib/deployed/jdk15/hpux-pa_risc2.0w/libprofilerinterfa ce.sl".
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/A/Resources/VisualVM.bundl e/Contents/Home/profiler3/lib/deployed/jdk16/hpux-pa_risc2.0/libprofilerinterfac e.sl", should be -rwxr-xr-x , they are -rw-r--r-- .
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/A/Resources/VisualVM.bundl e/Contents/Home/profiler3/lib/deployed/jdk16/hpux-pa_risc2.0/libprofilerinterfac e.sl".
Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/A/Resources/VisualVM.bundl e/Contents/Home/profiler3/lib/deployed/jdk16/hpux-pa_risc2.0w/libprofilerinterfa ce.sl", should be -rwxr-xr-x , they are -rw-r--r-- .
Repaired "System/Library/Frameworks/JavaVM.framework/Versions/A/Resources/VisualVM.bundl e/Contents/Home/profiler3/lib/deployed/jdk16/hpux-pa_risc2.0w/libprofilerinterfa ce.sl".

Yeah, that advice is all over the place. It certainly won't hurt. But the benefits of doing it are, IMO, greatly exaggerated.
Repairing permissions can be a useful task if you are having a problem that can be traced to incorrect permissions on an application, folder, or file that is installed with the Mac OS X installer. Because those are the only things (and only a subset of those at that) that repairing permissions fixes.
But somewhere along the line, people starting using Repair Permissions as some sort of magic pill that can fix any ailment. Computer slow? Repair permissions. Screen flickering? Repair permissions. E-mail message won't go on the trash? Repair permissions. That advice is handed out (ill-advisedly IMO) on a daily basis on these forums. And, of course, there are those who advocate repairing permissions both before and after any system update. IMO that advice too is based on urban legend. I never do it.
If you do repair permissions, and it finishes with "Permissions repair complete", then it's done and you don't need to worry. The "errors" it returns are not errors at all and nothing needs to be fixed. They're just "messages", not errors. If you don't want to see them, simply uncheck the "show details" box.
If Repair Permissions finishes with "permissions repair failed", or "the "underlying task reported failure on exit", then worry.

Superdrive needs repair - should i do it in Belgium or the US?

Similar Messages

Maybe you are looking for