13 Replies Latest reply: Dec 22, 2012 5:23 PM by roam Branched to a new discussion.
Steve Thompson Level 2 Level 2 (405 points)

Hello all

 

I'm getting the spinning wheel in all applications, even when writing this.

 

My console is reading like this

 

10/11/2012 08:57:56          com.apple.launchd[1]          (0x10ab00.mdworker[3058]) Exited abnormally: Bus error

10/11/2012 08:58:30          com.apple.launchd[1]          (0x10ab00.mdworker[3061]) Exited abnormally: Bus error

10/11/2012 08:59:03          com.apple.launchd[1]          (0x10ab00.mdworker[3066]) Exited abnormally: Bus error

10/11/2012 08:59:40          com.apple.launchd[1]          (0x10ab00.mdworker[3068]) Exited abnormally: Bus error

10/11/2012 09:00:13          com.apple.launchd[1]          (0x10ab00.mdworker[3070]) Exited abnormally: Bus error

10/11/2012 09:00:46          com.apple.launchd[1]          (0x10ab00.mdworker[3073]) Exited abnormally: Bus error

10/11/2012 09:01:21          com.apple.launchd[1]          (0x10ab00.mdworker[3075]) Exited abnormally: Bus error

10/11/2012 09:01:57          com.apple.launchd[1]          (0x10ab00.mdworker[3079]) Exited abnormally: Bus error

10/11/2012 09:02:31          com.apple.launchd[1]          (0x10ab00.mdworker[3085]) Exited abnormally: Bus error

10/11/2012 09:03:04          com.apple.launchd[1]          (0x10ab00.mdworker[3089]) Exited abnormally: Bus error

10/11/2012 09:03:37          com.apple.launchd[1]          (0x10ab00.mdworker[3091]) Exited abnormally: Bus error

10/11/2012 09:04:10          com.apple.launchd[1]          (0x10ab00.mdworker[3093]) Exited abnormally: Bus error

10/11/2012 09:04:43          com.apple.launchd[1]          (0x10ab00.mdworker[3095]) Exited abnormally: Bus error

 

 

Can someone tell me how to stop this little devil please?

 

 

regards

Steve


iMac (ALS) G5 (2GB ram), Mac OS X (10.5.8), BondiG3 (10.3.9) 1 extreme/5 expresses/3 ipods/tv
  • 1. Re: cpu getting hogged
    roam Level 6 Level 6 (13,545 points)

    Hi Steve,

    You have a problem with Spotlight indexing. If you can open System Preferences > Spotlight > click Privacy tab and drag your Hard Drive (HD) icon into the window. This should stop that activity by excluding your HD.

     

    Afterwards, log out / in again and then repeat the sequence but select the HD and click the minus sign - to remove it from the window, thus restoring Spotlight indexing. This may take some time to reindex, but after it has finished, hopefully that error you experienced before will no longer be there.

  • 2. Re: cpu getting hogged
    Steve Thompson Level 2 Level 2 (405 points)

    Hello Roam

     

    Thanks for replying, unfortunately your suggestion hasn't worked.

     

    Spotlight is still indexing, should I wait until that finishes?

     

    I still have spinning wheel and console reading as before.

     

    Cheers

    Steve

  • 3. Re: cpu getting hogged
    roam Level 6 Level 6 (13,545 points)

    Oh, well let's get serious and disable it.

    Open Terminal and copy and paste the following line, enter your Admin password which will not be shown as asteriks, just enter it carefully and press return.

    sudo mdutil -a -i off

     

    To reverse the procedure the same command is used except change off back to on.

  • 4. Re: cpu getting hogged
    Steve Thompson Level 2 Level 2 (405 points)

    Hi Roam

    sorry for taking so long on this.

    but that idea hasn't worked either

     

    any other thoughts?

     

    Steve

  • 5. Re: cpu getting hogged
    BDAqua Level 10 Level 10 (116,480 points)

    Steve, might try that terminal coomand while in Safe Mode...

     

    One way to test is to Safe Boot from the HD, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, Test for problem in Safe Mode...

     

    PS. Safe boot may stay on the gray radian for a long time, let it go, it's trying to repair the Hard Drive

     

    Reboot, test again.

     

    If it only does it in Regular Boot, then it could be some hardware problem like Video card, (Quartz is turned off in Safe Mode), or Airport, or some USB or Firewire device, or 3rd party add-on, Check System Preferences>Accounts>Login Items window to see if it or something relevant is listed.

     

    Check the System Preferences>Other Row, for 3rd party Pref Panes.

     

    Also look in these if they exist, some are invisible...

     

    /private/var/run/StartupItems

    /Library/StartupItems

    /System/Library/StartupItems

    /System/Library/LaunchDaemons

    /Library/LaunchDaemons

  • 6. Re: cpu getting hogged
    Steve Thompson Level 2 Level 2 (405 points)

    Thanks for spending time on this.

    i tried safe bootup, repaired permissions and tested with no notable improvement.

    After restart I went into the startup files mentioned and pretty well cleared everything out, again no change.

    After reading up on private/var I'm a bit wary of messing with him!

    I have now turned spotlight back on and have copied the following line from the console from the last startup that I can't see in previous logs

     

     

    18/12/2012 19:41:39 SyncServer[180] ISyncDataDirectoryCorruptedException: can't execute statement: 11 (database disk image is malformed)

     

    there's loads of other stuff before it goes into the mdworker issues as posted previously but do you think this is a worry?

     

    Any thoughts will be much appreciated

  • 7. Re: cpu getting hogged
    BDAqua Level 10 Level 10 (116,480 points)

    Hmmm, just wondering, do you maybe still have MobileMe or ,mac login info in System Preferences>MobileMe or .mac?

     

    If so erase the entries.

     

    Or what might be trying to Sync?

  • 8. Re: cpu getting hogged
    roam Level 6 Level 6 (13,545 points)

    Another thought, it could be insufficient RAM that is causing a general slowdown in all applications. Activity Monitor will show RAM, and as well as all current running processes which might be worth a look as well.

  • 9. Re: cpu getting hogged
    Steve Thompson Level 2 Level 2 (405 points)

    Roam, BDAqua

    Thank you for staying with this

    I thought you'd got it with Mobileme but sadly not, deleted all of that and everything in iSync without success.

     

    Not quite sure how to see RAM but space utilised is 76.63 GB against 295.86 free in disk usage.

     

    incidentally a thing called aslmanager seems to be top of the charts frequently up there with 80%+ cpu with report crash close behind.

     

    I've copied a section of what the consoe looks like at the moment as well

     

    22/12/2012 10:27:28 ReportCrash[679] Saved crashreport to /Library/Logs/CrashReporter/mdworker_2012-12-22-102725_Macintosh.crash using uid: 0 gid: 0, euid: 0 egid: 0

    22/12/2012 10:27:28 com.apple.launchd[1] (0x10a870.mdworker[678]) Exited abnormally: Bus error

    22/12/2012 10:27:28 com.apple.launchd[1] (0x10a870.mdworker[678]) Exited abnormally: Bus error

    22/12/2012 10:27:58 kernel disk0s3: I/O error.

    22/12/2012 10:27:58 kernel disk0s3: I/O error.

    22/12/2012 10:28:01 ReportCrash[682] Formulating crash report for process mdworker[681]

    22/12/2012 10:28:01 ReportCrash[682] Saved crashreport to /Library/Logs/CrashReporter/mdworker_2012-12-22-102758_Macintosh.crash using uid: 0 gid: 0, euid: 0 egid: 0

     

    Thanks again

    Further advise gratefully received

    Steve

  • 10. Re: cpu getting hogged
    roam Level 6 Level 6 (13,545 points)

    22/12/2012 10:27:58 kernel disk0s3: I/O error.

    It seems one of your partitions on your startup drive is faulty in some way.

     

    You can pinpoint this partition by opening Terminal and pasting this command.

    diskutil list

     

    (You could post the results here just for the record.)

     

    You could check the drive's S.M.A.R.T. status in Disk Utility and even if it says it is verified, I'd run a Repair Disk opertaion on the drive. Have you done this before?

  • 11. Re: cpu getting hogged
    BDAqua Level 10 Level 10 (116,480 points)

    roam seems to be onto your problem.

  • 12. Re: cpu getting hogged
    Steve Thompson Level 2 Level 2 (405 points)

    Thank you both

    here's the terminal results

     

    Macintosh:~ Steve$ diskutil list

     

     

    /dev/disk0

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:     Apple_partition_scheme                        *372.6 Gi   disk0

       1:        Apple_partition_map                         31.5 Ki    disk0s1

       2:                  Apple_HFS mac                     372.5 Gi   disk0s3

    /dev/disk1

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:     Apple_partition_scheme                        *1.8 Ti     disk1

       1:        Apple_partition_map                         31.5 Ki    disk1s1

       2:                  Apple_HFS external                351.6 Gi   disk1s3

       3:                  Apple_HFS time machine            1.5 Ti     disk1s5

    /dev/disk2

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:        CD_partition_scheme                        *767.2 Mi   disk2

       1:     Apple_partition_scheme                         668.0 Mi   disk2s0

       2:        Apple_partition_map                         31.5 Ki    disk2s0s1

       3:                  Apple_HFS WD SmartWare            305.9 Mi   disk2s0s2

    Macintosh:~ Steve$

     

    any chance of a translation?!

    I've only ever done repair permissions

     

    I must admit I thought it may come to this but have tried to avoid repair disk.

     

    cheers

    Steve

  • 13. Re: cpu getting hogged
    roam Level 6 Level 6 (13,545 points)

    I've only ever done repair permissions.... have tried to avoid repair disk.

     

    Repair your startup drive Steve.

     

    The startup drive can only be repaired from another drive. Unless you have a working clone (not Time machine) you have to boot from the 10.5 install disk.

     

    To do this: Insert the Install Disk 1 into the drive and then select Restart; when you hear the chime hold down C key until the apple logo appears.

    This will take you to the installation software, but you do not want to install.

    Select your language, then go up to the top menu bar  where it says Utilities and navigate to the Disk Utility application.

    Select your internal hard drive on the left, then go to the First Aid pane where you can click on Repair Disk.

    If it finds errors, repeat the process until it reports no errors, otherwise note down the error.

    After these repairs, quit the Installer, and restart normally.

     

    Once restarted normally run Repair Permissions from the Disk Utility application found on your hard drive in Application/Utilities. Whatever errors are reported in this instance of running Repair Permissions can be ignored. Ie. Repair Disk errors are to be noted. Repair Permissions errors are to be ignored.