2

Somebody has given me an Apple Macbook Air 1.1 to fix. Unfortunately I have very little experience with Macs.

Symptoms are:

*Computer runs incredibly slow to the extent that I have never seen one so bad. Boot up time is about 15-20 minutes then once logged into the GUI every move is agonisingly slow.

*Battery does not work/charge or is not being recognised

*Fans running super-fast

*When run in verbose mode very many I/O errors on disk0s2 are seen during startup

Things I have tried:

  • Reset VRAM - no change

  • Reset SMC - no change except keyboard backlight started working (didn't even realise there was one)

  • Checked available disk space - About 40GB out of 80GB available

  • Tried to run in safe mode - no change

  • Tried running Apple Hardware Tester at startup (by holding down D, also tried Option+D) but cannot seem to access it, possibly because the system is running so slow.

  • Used disk utility to repair hard disk - no errors/problems found

  • Checked SMART status of hard disk with Disk Util from the command line - SMART status reported as "verified".

Since there are continuous I/O errors but SMART status returns as OK should I presume that the motherboard is on its way out seeing as other things like battery are also not working? Or could there still be an issue with the hard drive / SSD?

  • Have you tried cleaning the fans? – Haroen Viaene Dec 22 '14 at 4:15
  • I ran an extended Apple Hardware Test on it and it came back with error code: 4SNS/1/40000000/TB2T-128.000 which apparently means battery thermal sensor TS2 error. That perhaps explains why the battery will not work but not why its running so slow. I think I might it take into an Apple store for a proper diagnosis. – leveller Dec 25 '14 at 0:48
1

There are only two causes of repeated I/O errors:

  • A logical failure of the drive due to a corrupted Filesystem

  • A physical failure of either the drive or a periphery component (connecting cable).

S.M.A.R.T. Status is not a reliable indicator for drive failure and is prone to false negatives. Remember, it’s a firmware function built-in to a drive checking itself.

Steps:

  • Boot into recovery mode. Use the repair disk function of Disk Utility to check the boot volume (disk0s2) from your recovery partition.
  • Use third party software such as Techtool Pro to scan for bad blocks on your HDD.

Best bet:

Here is your machine. More than likely, it’s a hardware issue. Specifically, either your drive is failing or the PATA cable is failing. The Apple Hardware Test, even if you were to access, does not test your HDD’s integrity. It would test, however, the input cable to the logic board (the PATA cable) - this is a much cheaper fix.

Bottom line: You can’t troubleshoot a hardware issue. Backup your data while the drive is still alive. Get a definitive diagnosis from Apple free of charge, and proceed from there. Once you know exactly what the issue is, decide whether you want to get the HDD/cable replaced by Apple, use a DIY option for a cheaper price, or purchase a new machine entirely.

BOL.

1

Ok, lets work on it.

When a battery is dead them Macs cut the CPU power in half.

So that's a reason 1 for slowness.

Next would be the Apple Hardware Test.

It is possible it is not installed, so you need to get it first.

Here is one possible place to find it for your model (it has to be specific to your model)

Fans running at max speed, so what is heating up? Use Activity Monitor to see.

Disk Check: Start in Single user mode holding down Command+S during system boot then use fsck -fy.

  • Just letting you know about CPU, and I do not know how slow it is. Did you try the fsck- fy. – Ruskes Dec 22 '14 at 21:30
  • OK I managed to get Apple Hardware test to work thanks to your link but the normal test returns no problems. The extended test just drags on for hours, I'm going to leave that running overnight later to see if it finishes or comes back with anything. Activity monitor does not show temps and usually when I check it the CPU activity is low and nothing abnormal. I also ran fsck and that came back with no problems found. If any further advice is given on diagnostics, I'd prefer cmdline to GUI because that's the only thing that is actually usable on any practical basis in single-user mode. – leveller Dec 22 '14 at 21:32
  • Sorry Buscar I hadn't finished typing and accidentally pressed enter when I posted the thing about the CPU! – leveller Dec 22 '14 at 21:35

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .