Tech tool issues

I got the apple care package and installed the Tech tool program. It asks me to put in the password when I run the app, but i don't have a password. I un-installed and re-installed tech tool but it still asks for the passwrod. Pls tell me how can I resolve the password issue so that i can get into Tech tool and start using it?

I'm not sure if this applies to the current AppleCare Tech Tools, but I think mine needed the serial number that was printed on the TechTools' CD sleeve. (Haven't used it for years, since I got Disk Warrior.)

Similar Messages

Internal hard drive/repair: SMART status; Disk Utility, Tech Tool & More

machine: 12" PowerBook 1.5 GHz PowerPC G4 (Aluminium) with 80GB internal HD
internal hard drive (original): Hitachi Travelstar 5K100 series HTS541080G9AT00
hard drive firmware: MB4AA5AJ
ATA version: 6
ATA standard: ATA/ATAPI-6 T13 1410D revision 3a
I have monitored the SMART status etc. of my internal drive with smartmontools for some time. Occasionally, I would see an error or a failed self-test but later testing always succeeded and things did not seem to be problematic.
At the beginning of this week, I started to see a lot of failed self-tests (though some still passed), a rising number of bad ("pending") sectors and reallocation attempts (though no reallocated sectors) and various other errors. The computer seemed to have trouble reading from the disk at times and Carbon Copy Cloner reported two I/O errors when cloning (a later clone succeeded). fsck showed errors although running fsck -fy repeatedly seemed to resolve them.
The Apple hardware tests initially reported an error (2STF/8/3:ATA-100 ata-6-Master) but I hadn't realised I should disconnect peripherals before running it so I did that and repeated the test which found no issues. I ran the extended test a total of three times with no errors.
As I continued to have problems, I booted from my clone and had Disk Utility wipe the drive by writing zeros to it. (I thought trying to get it to write everywhere would either finish the drive off or force it to reallocate the bad blocks. As I understand it, in normal use, the drive won't reallocate the blocks unless it can recover the data in the hopes of reading it at a later time.)
I then continued monitoring the disk using smartmontools. At this point, short self-tests succeed but extended self-tests "disappear". They don't fail, they simply vanish. They begin and smartctl shows the test in progress but then no error or result is logged - it is as if the test was never run. The first time I did this, I got an error saying the SMART attributes could not be read but subsequent tests do not trigger even an error. Short self-tests continue to pass.
There are now (according to SMART) zero bad ("pending") sectors but zero reallocated sectors, which seems odd. The raw read error rate fluctuates (zero one minute, many thousands a while later) although I am not sure it did not do this before.
Disk Utility claims the disk does not support SMART status even though smartctl clearly shows it does. Disk Utility claims the volume is "OK".
I ran Tech Tool Deluxe 3.04 from CD and 3.1.1 from my clone. In both cases, I ran all available tests on the drive. No problems were found.
I am seeing some problems even while booted from my clone - yesterday, the system froze completely and I had to force a shut-down by switching off the power (fsck then found a minor error but repaired it). Just before this happened, I was unable to mount a disk image and was trying to rectify the situation when the system froze. It is possible that the errors fsck corrected were implicated in the freeze, rather than caused by it, since Disk Utility found and repaired similar errors for the other two clones I have (on different partitions of my external drive - yes, I know this is sub-optimal).
Here is some current output from smartmontools:
---output: smartctl -q noserial -a disk0---
smartctl version 5.38 [powerpc-apple-darwin8.11.0] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
=== START OF INFORMATION SECTION ===
Model Family: Hitachi Travelstar 5K100 series
Device Model: Hitachi HTS541080G9AT00
Firmware Version: MB4AA5AJ
User Capacity: 80,026,361,856 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 6
ATA Standard is: ATA/ATAPI-6 T13 1410D revision 3a
Local Time is: Sat Jul 3 20:28:52 2010 BST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 645) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 55) minutes.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 RawRead_ErrorRate 0x000b 100 100 062 Pre-fail Always - 0
2 Throughput_Performance 0x0005 100 100 040 Pre-fail Offline - 0
3 SpinUpTime 0x0007 142 142 033 Pre-fail Always - 2
4 StartStopCount 0x0012 097 097 000 Old_age Always - 5793
5 ReallocatedSectorCt 0x0033 100 100 005 Pre-fail Always - 0
7 SeekErrorRate 0x000b 100 100 067 Pre-fail Always - 0
8 SeekTimePerformance 0x0005 100 100 040 Pre-fail Offline - 0
9 PowerOnHours 0x0012 039 039 000 Old_age Always - 26720
10 SpinRetryCount 0x0013 100 100 060 Pre-fail Always - 0
12 PowerCycleCount 0x0032 098 098 000 Old_age Always - 4168
191 G-SenseErrorRate 0x000a 100 100 000 Old_age Always - 0
192 Power-OffRetractCount 0x0032 100 100 000 Old_age Always - 201877487644
193 LoadCycleCount 0x0012 001 001 000 Old_age Always - 2209599
194 Temperature_Celsius 0x0002 141 141 000 Old_age Always - 39 (Lifetime Min/Max 16/46)
196 ReallocatedEventCount 0x0032 100 100 000 Old_age Always - 194
197 CurrentPendingSector 0x0022 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0
199 UDMACRC_ErrorCount 0x000a 200 200 000 Old_age Always - 0
SMART Error Log Version: 1
ATA Error Count: 2138 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
PoweredUpTime is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 2138 occurred at disk power-on lifetime: 26716 hours (1113 days + 4 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
10 51 00 09 4f c2 a0 Error: IDNF
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC PoweredUpTime Command/Feature_Name
b0 d6 01 09 4f c2 a0 00 08:30:04.500 SMART WRITE LOG
b0 d5 01 09 4f c2 a0 00 08:30:04.300 SMART READ LOG
b0 d1 00 00 4f c2 a0 00 08:30:04.000 SMART READ ATTRIBUTE THRESHOLDS [OBS-4]
b0 d0 00 00 4f c2 a0 00 08:30:04.000 SMART READ DATA
b0 da 00 00 4f c2 a0 00 08:30:04.000 SMART RETURN STATUS
Error 2137 occurred at disk power-on lifetime: 26682 hours (1111 days + 18 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 51 28 18 95 98 e4 Error: UNC 40 sectors at LBA = 0x04989518 = 77108504
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC PoweredUpTime Command/Feature_Name
25 00 80 c0 94 98 e0 00 1d+01:30:37.600 READ DMA EXT
25 00 80 c0 94 98 e0 00 1d+01:30:30.600 READ DMA EXT
25 00 80 c0 94 98 e0 00 1d+01:30:22.600 READ DMA EXT
25 00 80 c0 94 98 e0 00 1d+01:30:16.300 READ DMA EXT
25 00 80 40 94 98 e0 00 1d+01:30:14.700 READ DMA EXT
Error 2136 occurred at disk power-on lifetime: 26682 hours (1111 days + 18 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 51 21 1f 95 98 e4 Error: UNC 33 sectors at LBA = 0x0498951f = 77108511
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC PoweredUpTime Command/Feature_Name
25 00 80 c0 94 98 e0 00 1d+01:30:30.600 READ DMA EXT
25 00 80 c0 94 98 e0 00 1d+01:30:22.600 READ DMA EXT
25 00 80 c0 94 98 e0 00 1d+01:30:16.300 READ DMA EXT
25 00 80 40 94 98 e0 00 1d+01:30:14.700 READ DMA EXT
25 00 80 c0 93 98 e0 00 1d+01:30:14.100 READ DMA EXT
Error 2135 occurred at disk power-on lifetime: 26682 hours (1111 days + 18 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 51 22 1e 95 98 e4 Error: UNC 34 sectors at LBA = 0x0498951e = 77108510
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC PoweredUpTime Command/Feature_Name
25 00 80 c0 94 98 e0 00 1d+01:30:22.600 READ DMA EXT
25 00 80 c0 94 98 e0 00 1d+01:30:16.300 READ DMA EXT
25 00 80 40 94 98 e0 00 1d+01:30:14.700 READ DMA EXT
25 00 80 c0 93 98 e0 00 1d+01:30:14.100 READ DMA EXT
25 00 80 40 93 98 e0 00 1d+01:30:13.500 READ DMA EXT
Error 2134 occurred at disk power-on lifetime: 26682 hours (1111 days + 18 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 51 28 18 95 98 e4 Error: UNC 40 sectors at LBA = 0x04989518 = 77108504
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC PoweredUpTime Command/Feature_Name
25 00 80 c0 94 98 e0 00 1d+01:30:16.300 READ DMA EXT
25 00 80 40 94 98 e0 00 1d+01:30:14.700 READ DMA EXT
25 00 80 c0 93 98 e0 00 1d+01:30:14.100 READ DMA EXT
25 00 80 40 93 98 e0 00 1d+01:30:13.500 READ DMA EXT
25 00 80 c0 92 98 e0 00 1d+01:30:12.100 READ DMA EXT
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBAof_firsterror
# 1 Short offline Completed without error 00% 26717 -
# 2 Short offline Completed without error 00% 26717 -
# 3 Short offline Completed without error 00% 26717 -
# 4 Short offline Completed without error 00% 26717 -
# 5 Short offline Completed without error 00% 26716 -
# 6 Short offline Completed without error 00% 26715 -
# 7 Short offline Completed without error 00% 26714 -
# 8 Short offline Completed without error 00% 26697 -
# 9 Extended offline Completed: read failure 10% 26692 75071682
#10 Short offline Completed without error 00% 26687 -
#11 Extended offline Completed: read failure 10% 26676 77108511
#12 Short offline Completed: read failure 40% 26663 296917
#13 Short offline Completed without error 00% 26657 -
#14 Short offline Completed: read failure 10% 26646 296918
#15 Short offline Completed: read failure 70% 26645 296905
#16 Short offline Completed: read failure 10% 26644 296910
#17 Short offline Completed: read failure 10% 26644 296910
#18 Short offline Completed: read failure 40% 26643 296916
#19 Short offline Completed: read failure 20% 26643 296909
#20 Extended offline Completed without error 00% 26620 -
#21 Short offline Completed without error 00% 26618 -
Warning! SMART Selective Self-Test Log Structure error: invalid SMART checksum.
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENTTESTSTATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
---end output---
Self-tests 1-8 were all run after I erased the disk. The others were run before I did so. Not listed are the extended self-tests I've started since erasing which, as I say, have simply disappeared.
The checksum error regarding the log is normal for this disk. At least, I've got that error ever since I started using smartmontools for monitoring so I assume it is normal. (I installed this version of the software in about April 2008 and have used it since.) Also, starting offline testing has never succeeded on this disk (I think I checked into this at the time but can't quite remember - this is not new, anyway).
Questions
how should I interpret all this? (Why does Disk Utility say SMART is not supported while smartctl clearly shows it is at the same time? Why do the extended tests simply vanish? Is the drive definitely dying?) I do not want to replace the disk unless I absolutely have to because I understand that replacing disks in 12" PBs is no small matter and cost is an issue. I do not want to replace the machine unless I have to because cost is an issue and, also, I really like this computer and have no idea what I would want in its place, even if expense were no obstacle.
if it isn't clear whether the drive is dying or not, is there some further strategy I can use to establish this?
if the drive is dying, is a machine of this age worth repairing and, if it is, under what circumstances is it worth doing so? For example, it might be worth doing if you can do the job yourself, but that might be quite impractical for non-expert (not to mention, inexpert) users.
if there is a hardware problem (which I obviously think is very, very probable at this point), is it definitely a dying hard drive? (I've seen people write ominous things about disk controllers etc. which I gather are more serious - or less repairable - than a "mere" dying disk.)
what questions should I be asking you and what are the answers to those questions?!
Many thanks for your patience in reading this far.
- cfr

The 12" PB internals are a bit more complex, for PB's. If you don't want to replace the hard drive yourself or pay someone to install it, you could always get an external firewire hard drive, and use it to boot from and for general usage. Would have to be firewire, since the PB won't book from a USB device. One example of what you could get is a 160GB external hard drive: http://eshop.macsales.com/item/Other%20World%20Computing/MS4U5160GB8/ . All the choices with that case are listed here: http://eshop.macsales.com/shop/firewire/on-the-go
Have you called any Apple Authorized Service Providers to see what they would charge to install a drive for you? Whether you bought it or they supplied it? You can find a local one in the US at http://www.apple.com/buy/locator/service/

G5 will not boot from system disk or from Tech Tool Pro 5

Hi everyone - Having a bit of trouble and hoped I might find some answers here.
I suspect my system drive was having some issues as it sounded like it was being taxed and strained as I would open up applications from it. Upon verifying the disk using Disk Utilities, the test would stop short with the following message:
First Aid Failed
Disk Utility stopped verifying "Macintosh HD" because the following error was encountered
Filesystem verify or repair failed
In addition, an error message came up (in red) on the disk utility screen as well saying:
Volume header needs minor repair
The volume Macintosh HD needs to be repaired
Error: Filesystem verify or repair failed
Normally from here, I'd start up the computer from the Tech Tool Pro 5 disk (holding down C key upon restart). But when I did this, the computer never responded. Instead, the power was on but the screens went black and the computer went into a very quiet "idle" mode.
After about a minute, the fans began ramping up pretty high (and loud). This went on until I finally had to manually shut down the computer by holding the power switch down for a few seconds. I didn't know what else to do. Those fans were not coming down (not even after 10 minutes).
Anyway, I pushed the power button again and held the C key down. Still, nothing.... The fans stayed idle, for a little while and then ramped up again just like last time. I hit that same dead end and powered down the computer via the power button.
Is there an alternate way to boot the computer from Tech Tool Pro or the original start up disks? I'm having no luck, here.
I'm on my way into town to purchase a new internal drive (something with about 1TB of space) so that my pro apps can swim a little instead of being being bogged down on a 250G drive.
Thanks for any assistance, folks!
Oh yeah.... Happy New Year to everyone!!
Steve

The Install disk has version 10.4 on it. I have also tried booting from my OS 10.5 disk but with no avail.
However, here is an update on my plight.
Apple tech says that after hearing the symptoms, he thinks that one of the processors is shot. Being that my particular model of G5 (dual 2.7 processors) is a liquid cooled machine, it's possible that some sort of leak has formed and has either taken out a processor or has caused a processor to overheat. He says that this model of G5 has been known to do that. In this case, nothing will boot which makes me think that my original system drive may actually be okay. I'm taking it in for the tech to look at it and just be sure that's the problem. However, if it is a dead processor, the part alone would run $799 plus labor to install it. Frankly, that's just too much for me to pay to keep this old G5. I'd rather put that money towards a new or reconditioned Mac Pro 8 core or quad core machine.
I've owned several Mac computers in the past and perhaps this is the frustration talking but it seems that no matter how diligent you are in maintaining your Macintosh, these machines only seem to last about 5 years before something majorly wrong happens (mother board, processor, etc). Can I expect this same, limited time frame from a new Mac Pro? I mean, am I just being paranoid?

Problems restarting from C drive with Tech Tools 3.0.4 -OS 10.4.7

I have a TechTools CD sent to me by Apple for purchasing the protection plan. When i attempt to start up with that disk by holding C, the drive does not recognize the disk and i get the "no smoking sign" where the apple goes on the gray screen. I also have a Disk Warrior CD and it also is not recognized. I've also tried other methods of choosing both disks and neither are recognized. I've called Apple 3 times on this, and no one has been able to tell me why. They have sent me a new Tech Tools disk which still doesnt work, and now they are telling me it is a compatibility issue. What i want to know is, if it's a computability issue then is there anyone else in here who has this problem?? The lady at Apple had said she'd never heard of it so my thinking is the answer she gave me is b.s.
My mac is version 10.4.7 and my Tech Tools is version 3.0.4
HELP PLEASE??
iMac G5 iSight Mac OS X (10.4.7)
iMac G5 iSight Mac OS X (10.4.7)

But my question is, if this is a compatibility issue then why doesnt EVERYONE who bought my computer and got the TechTools disk from apple having the same problem?? I don't understand why they would send me a disk that was useless to me. Shouldn't someone know that this disk is supposedly incompatible??
I agree that it reduces the value of the TTD disk substantially, TrtlAtak.
Essentially the problem occurs because the disc contained in the Applecare package is often out of date, containing a system too old to start your computer. Sometimes the software itself is also out of date and should not be used until it has been updated. It depends partly on how long the particular package you receive has been sitting on the shelf, and partly on how long since a new version of the update has been provided.
The problem with the software occurs because Micromat often take a long time to update TechToolDeluxe for use with new systems. (As you have probably guessed, I'm not overly impressed with the TTD compnent of Applecare)
Remember there are TWO issues here, not just one. Firstly the CD has to have an appropriate operating system on it to start your computer. Secondly it has to have a version of TTD on it which is compatible with the OS on your computer.
In your case , the link to https://support.apple.com/techtooldeluxe/main?id=dl SHOULD , however, provide you with a disc which is capable of starting up your iMac G5 iSight (and with an appropriate version of TTD for use with it).
Any chance the caps lock key was down when you attempted to startup using the c key? This will prevent bootup from CD. (Its "c" that needs to be held down , not "C").
Secondly, you could try holding down the "option" key instead while you start up, with the CD in the drive. This should allow you to select which particular drive you wish to start from (the HD or the optical drive).
Thirdly, with the Disc in the drive, you could see if it appears as a "startup disc" choice whe you go to SystemPreferences / StartupDisc. If so, select it, and restart your computer.
There are other things that can prevent your Mac startingup from a CD or DVD. If you have an "open firmware" password installed on the computer, for example, it can't be started from an optical drive. Some third party keyboards also will not let you start up in this fashion.
Cheers
Rod

Tech Tool Deluxe Volume Structure test query

Hi,
Sorry if this is elsewhere, but my searches have not supplied a definitive answer.
As part of my regular maintenance routine on my iMac (mid 2010 i7 quad core) that I purchased just before Christmas, I have run the AppleCare Tech Tool Deluxe scans at regular monthly intervals with no problems, until about a month ago.
When the program does it's stuff, all tests pass, except the volume structure one (in the window showing the image of the volume structure, it says fail! above the "icon"). The final report that Tech Tool Deluxe comes out with says everything has passed. What's going on?
Because of this, I''ve also done a surface scan in the program and it was OK, as was verifying the disk in Disk Utility from the Snow Leopard DVD. I've repaired permissions and even reformatted the Macintosh HD and done a complete reinstall of the OS (not from backup), all of which come up with the same result in Tech Tool Deluxe - volume structure fails, but final report passes.
The version of Tech Tool Deluxe I have installed from the AppleCare disc is 3.1.3, which according to Micromat is the current one, but this is from 2009.
So my question is this:
Has the updated Snow Leopard (10.6.6) changed it's volume structure slightly meaning that Tech Tool Deluxe thinks there's a problem as it's scanning, but then ignores it for the final report, or is my HDD failing?
I've not noticed any issues whatsoever with the iMac and I have both Time Machine and bootable SuperDuper backups, so I'm not worried about my data.
Would you guys recommend ignoring it for now, or should I get Diskwarrior to check it out further?
Thanks for any help, or light that can be shed on this issue.

Hi Den,
Thanks for this, I emailed them and they are giving the usual story of "this product was developed for Apple, so you'll need to speak to them".
I've bit the bullet and purchased DiskWarrior 4.3 and by installing it onto my SuperDuper backup drive, I was able to check out the iMac's internal HD.
DiskWarrior was able to find errors in file structure and permissions etc (it didn't give details) and was able to repair them. After rebooting into the internal HDD, I ran TechTool Deluxe 3.1.3 again, and this time it said that it failed the volume structure during the test and then in the final report. It tried to get me to download the repair version of the software, but the web page that opened had nothing to do with TechTool's download. As a little self test, I ignored it and ran the test again. This time, it failed during the test (as normal) and then said that it passed in the final report.
I have therefore come to the conclusion that if Disk Utility AND DiskWarrior say that it's fine, then the issue must be with TechTool Deluxe. At least it doesn't seem to be an issue with the actual drive.
I admit that I was getting suspicious of TechTool when a fresh install on a reformatted HDD said that the volume structure failed and then passed. There must be something different about the current version of Snow Leopard comared to that at the time of release of version 3.1.3 of Tech Tool Deluxe.
Thanks for all your help guys.
Obviously, if someone can prove me wrong, that would help me ascertain as to what is going on.
Message was edited by: pdscott

Tech-tool/volume

My macpro is running slow ever since I installed leopard! I checked HD w/tech-tool and was told to download the disk.
Ran disk at which point it showed discrepancies in catalogue B info and catalogue B extents. I then ran repair, at which it showed no problems.
Still slow, for a few days tech tooled again /Dev/disk1s2 came up, followed instructions to resolve those same problems as on main disk.
Still shows volume structure failed!
any help would be appreciated
Thanks Gary

Problem solved thanks to Klaus1! she runs like new now.
If you were having any serious problems with your Mac you might as well complete the exercise by repairing your hard disk as well. You cannot do this from the same start-up disk. Reboot from your install disk (holding down the C key). Once it opens, select your language, and then go to Disk Utility from the Utilities menu. Select your hard disk as before and click Repair.
Once that is complete reboot again from your usual start-up disk.
More useful reading here:
Resolve startup issues and perform disk maintenance with Disk Utility and fsck
http://support.apple.com/kb/TS1417

Tech Tool Deluxe 'Surface Scan Failed-'

Surface scan repeatedly failing, no recent change to iBook settings, I suspect that this problem may have been caused by m-audio software, however I believe it has been properly uninstalled. Advice?
Error message reads;
'Surface Scan Failed - 212 errors
The Surface Scan test will scan the disk for bad blocks.
Media defects cause this test to fail. You should consider backing up the device, reformatting the media, replacing the data, and then testing again.'
I am unsure as what this report is prompting me to do. What does the term 'media' mean in this context? Which data should I be trying to replace?
Please forward any tips on how to resolve this issue.
<Post Relocated by Moderator>

When I use the disk utility application the volume passes verification, is this contrary to Tech Tools or are they analyzing different elements of the drive?
Yes, different, DU is just basically checking part of the drive, where Directory info is stored & such.
Laptop drives are generally a lot shorter lived than regular drives, which now seem to last 3 to 5 tears.
Although these errors are present it doesn't seem to be effecting my day to day running of things at the moment...
There's a Train Wreck coming up ahead though, you can avoid it, or wait 'till it hits!
Not certain which iBook G4 you have, but here's some ideas on HD replacements...
http://eshop.macsales.com/MyOWC/Upgrades.cfm?sort=pop&model=198&type=DataStorage&TI=5904&shoupgrds=ShowUpgrades

Help! Tech Tool Scan shows failures

Tech Tool Deluxe show that Format Check failed, Directory Scan failed, Surface Scan was skipped and Volume Structure failed. Can someone help me understand what is going on and what I should do to fix these problems. I called Apple Support yesterday. The advisor told me to insert the install disk, go into Disk Utility and click repair and yet today when I put in the Tech Tool just to check if things were working properly, it showed the same issues are still happening.

I don't have a copy of TTD, so I'm not familiar with it, but were you just scanning from problems, or did you try to have TTD repair the issues? Did you have Disk Utility repair the disk as instructed? If repairs are failing with both TTD and DU, then your drive may be in the process of failing, or it may be so badly corrupted that it can't be repaired. In the former case, you will simply have to replace the drive. In the latter, repartitioning it with Disk Utility and then reinstalling the system and all your data may bring it back to life.
Note that your first order of business regardless should be ensuring that you have a good set of backups (a minimum of two backups). See my [Mac Backup Guide|http://www.reedcorner.net/guides/backups>.

ISight not working with mac programs, functional with Tech Tool Deluxe

MBP 15 (late 2008)
iSight not functional, ie "no camera connected" when using photobooth, imovie, ichat, skype, but when I fire up tech tool deluxe 5, it's working - I can see myself and it is functional. Tried all the restarts, etc. Can I fix this myself or is this an applecare issue?
Thanks

Welcome to Discussions, johnnychickenfoot
One of the relevant suggestions from http://support.apple.com/kb/HT2090 will get it working.
If you can make your iSight work properly and repeatedly with any app in any user account you test, your problem is software related.
A properly performed reset as suggested in the Troubleshooting article often restores function to built-in iSights. If that continues not to work for you in any user account, consider software troubleshooting like the relevant ideas from here:
http://support.apple.com/kb/TS1388
Because your iSight works with TTD, your System Profiler should recognize your built-in iSight as a USB device. If you need to post back for other suggestions, please confirm that System Profiler can see your iSight when TTD is not running.
EZ Jim
G5 DP 1.8GHz w/Mac OS X (10.5.8) PowerBook 1.67GHz (10.4.11) iBookSE 366MHz (10.3.9) External iSight

Tech Tool Deluxe won't install

I got Applecare for my dual G5 1.8 GHz (Running Tiger) and it came with this spiffy CD of Tech Tool Deluxe.
I tried to install it from the CD. It got all the way through the installation, then it was "searching the HD." I let it search. It searched all night. And all day. After about 18 hours of searching, I quit the installer.
I then ran disk utility to clean up permissions. I tried reinstalling Tech Tool Deluxe. Same issue.
I booted from the Tech Tool CD. Ran Tech Tool. No issues found.
I then rebooted into Tiger and tried, again, to install Tech Tool Deluxe. Same problem.
The version on the CD is 3.0.4, which is the most up to date version on Micromat's website.
Any thoughts on what's going on?
Thanks,
csayre
DP G5 @ 1.8 GHz Mac OS X (10.4.4)

The problem is probably that Tech Tool is now at 4.1.1. - check their site again. This (4.1.1) is the first version to be Tiger compatable - 3.0.4 is NOT Tiger friendly and probably isn't even OS X compatible - when Mac went to OS X Micromat offered 4.0.1 to us registered users as a free upgrade to get OS X compatability - the disk I bought 3 years ago for OS 9 was actually 3.0.9 so I'd say upgrade to 4.1.1 and back up your drive as they recommend until you know it isn't going to be glitchy with Tiger in this version. I would advise caution however with Tiger usage. I have 4.1.1 from an upgrade download to the disk version of 4.0.1 and the CD will not allow me to boot from it for repairs. I will need the disk of 4.1.1 to do this. I also know of two people who have lost their data and drive functionality after doing routine repairs. This may be a Quad issue - both instances were on Quads - and may not affect Duals but I'm waiting for the next upgrade before using this fix any drive issues on my Quad. I will stick with Disk Utilities on the Tiger boot disk untill then.
P.S. I was able to load 4.0.1 no sweat from the disc which does allow inspection and you can still repair all externals , just not the system drive from the desktop...
G5 Quad Mac OS X (10.4.4) 4 GB RAM, 500GB ATA HD, NVIDEA GeForce 7800 GT, 23" HD Cinema Display

Tech Tool Deluxe v3.1.2

I apologize if this question is in the incorrect category; I was unable to find one for issues concerning Tech Tool Deluxe which is available at N/C to owners of systems still in warranty.
I downloaded v3.1.2. and this executes from within the O/S. Is there not a version that one can run at boot and thereby not have to contend with drivers, allocated memory, etc? I seem to recall that the version prior to this did....
Thanks,
Lyman

Well, if you have a bootable CD with the latest version of TechTool, you can then startup from the CD and go directly into TechTool. The problem is the frequent need for updates, which makes the CD obsolete quickly. Micromat will probably sell you another updated CD, but it too will become obsolete quickly. Or you can create a boot disk (as a partition or separate drive) with the tools you need for maintenance and trouble-shooting. I like it better than using the CD because it runs faster, I have access to Apple's Disk Utility and other tools in addition to TechTool, and it's easy to keep updated (both for the OS and the tools).

Tech Tool vs Disk Warrior

I recently bought a new iMac and have updated SL. My old DW no longer works according to all the posts I have read. So I am in the process of making up my mind as to which one utility would be best to buy, Tech Tool or Disk Warrior and the compatibility issue with SL.
Those of you who have experience, any recommendations?
Thank you,
Glen

Disk Warrior's unfailing ability to reliably repair a disk's index when other means fail has meant my copy of TT mostly sits on the shelf.
Get DW only or go ahead and get them both.

Kernal Panic when booting from AC Tech Tool disc

Okay, here's one to stump y'all:
I have talked to Apple Support, brought the machine to the best service center (Springboard Media in Philly) and no solution yet. Here's what happens:
Whenever I try to boot up from the Tech Tools Deluxe disc that came with my Apple Care Plan, Tech Tools Pro or Disk Warrior, the G5 panics about two seconds after I get to the grey apple screen. This happens every time. Now the interesting thing is that this did not happen when Springboard tried the same thing. Could this be a hardware issue that just wasn't found? I was assured that Springboard ran extensive hardware and software tests and came up with nothing.
I am at a loss. When I called Apple about this initially, the dude I spoke with decided that it must have been the media and promptly sent me a replacement Tech Tools Deluxe disc. Of course this did nothing. I am hoping someone on the forums will have some insight on this...
Cheers,
Matt
MDD Dual 867 | G5 Quad 2.5 Mac OS X (10.4.8) Sam Smith's Oatmeal Stout, Maker's Mark bourbon and a whole lotta RAM

Hi- Thanks for the comments.
Yes, non-Apple RAM is installed. I had faulty RAM and found it and it was replaced by a very reputable third party company. I should have mentioned all the steps I have gone through (prior to bringing it into Springboard):
First noticed something was wrong when the machine was just shutting off w/o warning (ie like I pulled the plug). This happened a few times over the first two months of owning the machine, but seemed to progress (the G5 is only 4 months old). So that's when I initially tried booting from the TTD and TTP discs, to no avail. Then I went on to Apple Hardware test, which I could boot to fine w/o any problems. Ran the test in Loop Mode. The test would pass the everything up to the memory and then the machine would shut down. This happened quite a few times, so I know it wasn't a fluke. Finally got the AH test to confirm that one of my 2GB DIMMs was shot. That's when I sent it back, and continued testing with the stock 512MB (ugh) with no problems. However, even with the stock 512 in the machine failed to boot from TTD or TTP or DiskWarrior. Which made me think it was the optical drive. (And consequently when I started thinking this was above my head.)
So called Apple, and we reset the PRAM, the NVRAM, unplugged the machine for two minutes etc. Standard reading from a script Tier One. All to no avail.
Got the RAM back from the 3rd party (OWC), called them to confirm that the RAM I had sent back was faulty and that they had personally tested the DIMMs they sent back to me, which they confirmed had passed AH test. I then installed the 4GB, ran AH again - no problems. But, the booting from a CD/DVD problem still persisted.
I really doubt whether it is the OWC RAM at this point, as I successfully tested it, as did Springboard. I must reiterate that Springboard had no problems booting from TTD, TTP, etc.
I wish I could get a good photo of the KP when I boot from the TTD, cos the system profiler doesn't record it in the logs.
I think this covers pretty much everything I have done so far... I look forward to your responses.
And thanks for the luck!
MDD Dual 867 | G5 Quad 2.5 Mac OS X (10.4.8) Sam Smith's Oatmeal Stout, Maker's Mark bourbon and a whole lotta RAM

Working with my 2 FireWire HD i had a crash. the only way to start was a safe start. then id maged to start from a DVD and install a MAC OS 10.3 wich ran 4 some time then the same problem only safeMode. kernel panic inserted the tech tool DVD

working with my 2 FireWire HD i had a crash. the only way to start was a safe start. then id maged to start from a DVD and install a MAC OS 10.3 wich ran 4 some time then the same problem only safeMode. kernel panic by inserting the tech tool DVD, wich produces the following highligted text:
panic(cpu 0 caller =xffff0003): 0x300 - Data access
latest stack backtrace for CPU 0:
Backtrace:
0x0009CC88 0x00D63C 0x00029DAO 0x000BOA10 0x000B4270
proceeding back via exception chain:
Exception state (sv=0x26acd700)
PC=0x2717E900; MSR=0x00009030; DAR=0x00000000; DSISR=0x40000000; LR=0x2717EBE4; R1=0x26AD3AE0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x27178B0 0x00344ACB 0x00345970 0x2717EC08 0x2718458 0x00340590
0x003496EC 0x0034B59C 0x0034A6BC 0x000B1DD4
Kernel Loadable modules in backtrace (with dependencies):
com.apple.driver.AppleFWDHC1(3.9.5)00x2717c000->0x271aafff
dependency: com.apple.iokit.10PCIFamily(2.6)00x1e840000
dependency: com.apple.iokit.I0FireWireFamily(3.4.7)00x270dd000
Exception state (sv=0x26abd280)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000;R1=0x00000000; XCP=0x00000000 (unknown)
BSD process name corresponding to current thread: kernel_task
so what
greetings from berlin

Greetings,
It appears to be a FW problem, possibly flaky case, or drive problem.
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 (Users & Groups in later OSX versions)>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

Internal hard drive won't mount after running Tech Tools Pro 5

HELP.
We have an imac 2ghz Intel Core 2 running OS 10.6.8.
I ran Tech Tools Pro 5 to rebuild directory, optimize files, optimize volume. It ran over nightbut seemed to hang up optimizing the volume.
Now the HD doesn't mount.
I've tried a few fixes. Including running disk utility from a CD. The disk utility says the directory is okay but doesn't see the HD to verify or repair permissions.
I've tried zapping the pram and safe boot, neither of which worked.
I've been able to use the computer by booting from an external start up hd.
Oddly, I ran a Time Machine back up prior to running TTP, but for some reason the only back up I see is from 3 months ago.
Not sure why the recent back up didn't happen, but were missing some very important recent docs.
I downloaded a trial version of Stellar Pheonix Mac Data Recovery and it seems to be able to see all of the data on the main HD.
I'm wondering whether or not to spend $100 for full version to attempt to restore content of HD to an external.
If I do this, I assume I'll have to erase the HD and reinstall data from the Stellar Pheonix collection, hoping that it's all intact.
Does anyone have any other suggestions to get the HD mounted????

Hi, never "Optimize" a drive before Repairing it AND having a backup clone to boot from.
I assume I'll have to erase the HD and reinstall data from the Stellar Pheonix collection, hoping that it's all intact.
No, I don't think you want an erase at all, you want a freah external drive to recover to first off.

Tech tool issues

Similar Messages

Maybe you are looking for