Previous 1 2 Next 29 Replies Latest reply: Jan 9, 2014 12:19 AM by Beautje Go to original post
  • Pondini Level 8 Level 8 (38,720 points)

    Beautje wrote:

    . . .

    So I hooked up my original drive, in a usb enclosure, and verified it. I got scary red letters saying that the filesystem needs repair!

    Then repair it before trying to back it up. 

     

    Are both my HD's broken, or is something wrong with my OS, or disk utility or.. ???

    Hard to tell, yet.  See if the (repaired) original drive will back up correctly.  If so, the problem is with the new one.

     

    If not, it could be OSX or the TM drive. 

  • Beautje Level 1 Level 1 (0 points)

    Then repair it before trying to back it up. 


    Good point
    I'd verified it before I took it out of the computer, so I just assumed it would be ok.

     

    I tried (to repair it) just now, but I get a message that the volume could not be unmounted.

  • Pondini Level 8 Level 8 (38,720 points)

    That usually means something else is trying to use it.  Make sure any other apps that might be using it aren't. 

     

    If that doesn't help, try to eject and remount it.  If still no help, try a Restart.   Last resort, start from your Leopard Install disc and repair it from there.

  • BDAqua Level 10 Level 10 (119,115 points)

    Likely Spotlight if nothing else, make sure to add that drive to Spotlight's Privacy Pane.

  • Beautje Level 1 Level 1 (0 points)

    Tx, that worked, didn't  even need to exclude in spotlight.

    it almost immediately stuck on 1.49 gb, with the same mdworker importer force killed messages.

    Widget says waiting for index.

    Only running for 20 min now so  I'll leave it on for a while longer but it looks the same as before.

  • Pondini Level 8 Level 8 (38,720 points)

    Beautje wrote:

    .  .  .

    it almost immediately stuck on 1.49 gb, with the same mdworker importer force killed messages.

    Sounds like it's having a problem with a file.  That could be a problem with the file itself, or a problem with the "importer". 

     

    If it's a problem with the importer (a program or template that's used to index a certain type of file), try installing the "combo" update, per Installing the "combo" update and/or Reinstalling OSX.  If that doesn't help, try reinstalling OSX, per the same article.  As long as you pick the Archive and Install option and the Preserve Users and Network Settings box is checked, that won't disturb anything else.

  • Beautje Level 1 Level 1 (0 points)

    ok, thanks!

  • Beautje Level 1 Level 1 (0 points)

    I did the combo backup, didn't help, then the reinstall, didn't help either. Verify says all disks are ok.

    Both times backup gets stuck on 26 GB and I get this message in system log over and over:

     

    Dec 16 17:35:20 BeautjeBook-2 mdworker[415]: (Error) Import: Importer force killed!

    Dec 16 17:35:20 BeautjeBook-2 com.apple.launchd[1] (0x109ea0.mdworker[415]): Exited with exit code: 1

     

    (the -2 after my computer name appeared when I installed the combo update)

     

    I did everything exactly as the manual said. Could there be a problem with a programme I installed or a virus or something?

  • Pondini Level 8 Level 8 (38,720 points)

    Beautje wrote:

    . . .

    Both times backup gets stuck on 26 GB and I get this message in system log over and over:

     

    Dec 16 17:35:20 BeautjeBook-2 mdworker[415]: (Error) Import: Importer force killed!

    Dec 16 17:35:20 BeautjeBook-2 com.apple.launchd[1] (0x109ea0.mdworker[415]): Exited with exit code: 1

    There must be a problem with a file, that Disk Utility can't find (it only looks at the directories, etc., not the content of the files).  So when OSX tries to index it, the "importer" can't deal with it and crashes. 

     

    I'm assuming you get those messages only when a backup is not running?

     

    It's going to be rather tedious to find it, since the message doesn't show the file name. 

     

    We can probably slog through that, but I'm wondering . . . are you anywhere near an Apple Store?  The Genius Bar may be able to do it much quicker. 

     

    (the -2 after my computer name appeared when I installed the combo update)

    That's not a problem; it's a naming conflict of some sort on your network.  You should be able to reset it via System Prefs > Sharing.

     

    I did everything exactly as the manual said. Could there be a problem with a programme I installed or a virus or something?

    Highly, enormously unlikely. 

  • Beautje Level 1 Level 1 (0 points)
    There must be a problem with a file, that Disk Utility can't find (it only looks at the directories, etc., not the content of the files).  So when OSX tries to index it, the "importer" can't deal with it and crashes. 

     

    I'm assuming you get those messages only when a backup is not running?

    In a manner of speaking.. I get those only the moment the backup hangs, then every 5 minutes up to the moment I stop the backup.

     

    It's going to be rather tedious to find it, since the message doesn't show the file name. 

     

    We can probably slog through that, but I'm wondering . . . are you anywhere near an Apple Store?  The Genius Bar may be able to do it much quicker. 

     

     

    Only premium resellers in my corner of the world, no genius bars

    Glad to know that it's probably a single file though. Should I try excluding folders to see where abouts it is? I've made copies of the system log during the backups.

     

     

    (the -2 after my computer name appeared when I installed the combo update)

    That's not a problem; it's a naming conflict of some sort on your network.  You should be able to reset it via System Prefs > Sharing.

     

    Fixed it!

  • Beautje Level 1 Level 1 (0 points)
    Things are copied from your HD in the default order:  /Applications, /Library, /private (hidden) /System, then your Users folders.

     

    I took a look at the size of my folders, and I think the file should be in /private.

    Apps + library = 19 GB, and if I add up everything else the /private folder should be about 24 GB.

  • Beautje Level 1 Level 1 (0 points)

    update: I get the mdworker message right now as well, so I also when the backup is not running.

  • Pondini Level 8 Level 8 (38,720 points)

    Beautje wrote:

    . . .

    I took a look at the size of my folders, and I think the file should be in /private.

    Apps + library = 19 GB, and if I add up everything else the /private folder should be about 24 GB.

    Aha!  Yes, I'd start by excluding the whole /private folder.

     

    But a lot of it is excluded automatically (most of the log files in /private/var/log; and the vm and sleepimage files in /private/var/vm), so the problem may be past /private. 

     

    Sounds like you're on the right track!

  • Pondini Level 8 Level 8 (38,720 points)

    Beautje wrote:

     

    update: I get the mdworker message right now as well, so I also when the backup is not running.

    (This came in after my previous response.)

     

    That may complicate things a bit, but if you exclude the right thing(s), the backup should run ok (perhaps a bit slowly, depending on how much of your resources mds/mdworker is using trying to deal with the problem).

  • Beautje Level 1 Level 1 (0 points)

    Just logged on to ask another question and realized I never posted the solution:

     

    I had to switch the mac off, then press a couple of keys while booting (I remember one of them was shift), wait for the mac to do what it was doing, then restart.

     

    A big thank you to Pondini for all your help!

Previous 1 2 Next