Welcome, Guest
Username: Password: Remember me

Search Micromat Forum

Keyword
  • Page:
  • 1
  • 2

TOPIC: I think we need a "stop Checkmate button"

I think we need a "stop Checkmate button" 29 Dec 2012 17:20 #3480

I just tried to do a rather big backup with Synchronize ProX. (95G 6700 files)
The fact is that the "backup disk" has never been checked by Chekmate.
A lot of errors occurred

Here is a small part from Synchronize ProX log.


* An error occurred while writing a file.
File system I/O error.
Path: Sons XX:HR Wind_Gale_Force:HR_AMB003_WIND_GALE_FORCE_EXT:WIND GALE FORCE EXT in Wires Melrose 3 wind whistle MKH70.wav
* An error occurred while creating a temporary file.


* An error occurred while opening a file to be written.
The file was not found.
Path:
* An error occurred while creating a temporary file.
Current privileges do not allow the operation. Error # -35.


Three times I stopped the backup, do the copy of these file by hand with no issues.
I'm a Synchronize user for many years and never encounter those type of issues (in this case my files are simple media audio files) ......
So I suspected Checkmate to be the culprit but to stop it I was forced to uninstall it because of the lack of a Stop button.

Without Checkmate running the backup run smoothly .... any ideas?
Thanks in advance
JM
The administrator has disabled public write access.

Re: I think we need a "stop Checkmate button" 29 Dec 2012 17:39 #3482

The forums are moderated. New postings do not appear until they are approved by a moderator.

Thanks for your clear and detailed report.

We have plans to add the button you suggested.

Checkmate should not be running any tests while you are using your Macintosh. The CheckmateIdleDaemon launches tests when the Macintosh is not in use. The tests themselves are run by the CheckmateWorkerDaemon process, which quits when the tests are finished. We are aware of a problem in which the user sees too briefly a dialog box stating that the active started volume is about to be tested, and then, without any user intervention, that test begins. When the active startup volume is having its disk directory checked, the computer slows down.

While it is unlikely that Checkmate caused this problem, we can investigate it if you use the Send Report feature in the Checkmate menu of the Checkmate application. It automatically sends the proper log files. Please save the Synchronize ProX log. We need to compare any timestamps in that log and the All Messages log to timestamps in the CheckmateWorkerDaemon.log, at /Library/Logs/Checkmate. If you like, you can read that log using the Console application, located at /Applications/Utilities. Thank you. You will receive a reply by email. The company reopens on Wednesday, January 2.

Checkmate itself checks the All Messages log for i/o errors.

A sample from my own CheckmateWorkerDaemon.log, showing in the third line a disk directory error on the Time Machine volume H_G_Wells:
2012-12-27 18:17:56 Passed: Volume Structures test checked volume 'Macintosh HD' (disk0s2).
Volume Macintosh HD on disk0s2 mounted
2012-12-27 18:19:52 Passed: Volume Structures test checked volume 'G-Drive_Q_232' (disk1s2).
Volume G-Drive_Q_232 on disk1s2 mounted
[b]2012-12-27 22:40:06 Error: Found a directory structure error for volume "H_G_Wells". ::Use Disk Utility or TechTool Pro for repair.[/b]
Volume H_G_Wells on disk2s2 mounted
2012-12-27 22:40:08 Passed: Volume Structures test checked volume 'Recovery' (disk1s3).
Volume Recovery on disk1s3 mounted
2012-12-27 22:40:08 Passed: Volume Structures test checked partition map for disk '1 TB WDC WD1001FALS-40Y6A0 Media'.
2012-12-27 22:40:09 Passed: Volume Structures test checked partition map for disk '250 GB HDT72252 5DLA380 Media'.
2012-12-27 22:40:09 Passed: Volume Structures test checked partition map for disk '500 GB Hitachi HDT725050VLA360 Media'.
2012-12-28 00:05:35 Passed: Surface Scan test scanned up to 53.58% of the drive "1 TB WDC WD1001FALS-40Y6A0 Media (SN#WD-WCATR2452548)".
2012-12-28 00:07:54 Passed: Surface Scan test scanned up to 0.49% of the drive "500 GB Hitachi HDT725050VLA360 Media".
2012-12-28 00:07:54 Passed: Surface Scan test scanned up to 2.73% of the drive "250 GB HDT72252 5DLA380 Media".
2012-12-28 00:11:53 Passed: Surface Scan test scanned up to 4.22% of the drive "250 GB HDT72252 5DLA380 Media".
2012-12-28 00:13:19 Passed: Surface Scan test scanned up to 53.80% of the drive "1 TB WDC WD1001FALS-40Y6A0 Media (SN#WD-WCATR2452548)".
2012-12-28 00:15:22 Passed: Surface Scan test scanned up to 53.82% of the drive "1 TB WDC WD1001FALS-40Y6A0 Media (SN#WD-WCATR2452548)".
2012-12-28 00:16:25 Passed: Surface Scan test scanned up to 53.84% of the drive "1 TB WDC WD1001FALS-40Y6A0 Media (SN#WD-WCATR2452548)".
2012-12-28 00:20:21 Passed: Surface Scan test scanned up to 1.71% of the drive "500 GB Hitachi HDT725050VLA360 Media".
2012-12-28 00:22:30 Passed: Surface Scan test scanned up to 2.18% of the drive "500 GB Hitachi HDT725050VLA360 Media".
2012-12-28 00:24:06 Passed: Surface Scan test scanned up to 54.16% of the drive "1 TB WDC WD1001FALS-40Y6A0 Media (SN#WD-WCATR2452548)".
2012-12-28 00:40:28 Passed: Surface Scan test scanned up to 62.64% of the drive "1 TB WDC WD1001FALS-40Y6A0 Media (SN#WD-WCATR2452548)".
2012-12-28 00:46:43 Passed: Surface Scan test scanned up to 12.13% of the drive "250 GB HDT72252 5DLA380 Media".
2012-12-28 00:47:45 Passed: Surface Scan test scanned up to 12.15% of the drive "250 GB HDT72252 5DLA380 Media".
2012-12-28 00:48:53 Passed: Surface Scan test scanned up to 62.71% of the drive "1 TB WDC WD1001FALS-40Y6A0 Media (SN#WD-WCATR2452548)".
2012-12-28 00:50:07 Passed: Surface Scan test scanned up to 62.81% of the drive "1 TB WDC WD1001FALS-40Y6A0 Media (SN#WD-WCATR2452548)".
2012-12-28 00:59:09 Passed: Surface Scan test scanned up to 4.62% of the drive "500 GB Hitachi HDT725050VLA360 Media".
2012-12-28 01:01:15 Passed: Surface Scan test scanned up to 62.86% of the drive "1 TB WDC WD1001FALS-40Y6A0 Media (SN#WD-WCATR2452548)".
2012-12-28 02:19:45 Passed: Surface Scan test scanned the drive "1 TB WDC WD1001FALS-40Y6A0 Media (SN#WD-WCATR2452548)".
2012-12-28 06:23:21 Passed: Surface Scan test scanned the drive "500 GB Hitachi HDT725050VLA360 Media".
2012-12-28 07:34:09 Passed: Surface Scan test scanned the drive "250 GB HDT72252 5DLA380 Media".
2012-12-28 12:31:27 Passed: Power On Self-Test check passed.
2012-12-28 12:31:27 Passed: I/O error check passed.
2012-12-28 12:32:35 Passed: Memory test checked 6.1 GB of 8 GB total memory.
2012-12-28 20:59:50 Passed: Power On Self-Test check passed.
2012-12-28 20:59:50 Passed: I/O error check passed.
2012-12-28 21:00:07 Passed: Memory test checked 5.46 GB of 8 GB total memory.
2012-12-28 21:00:07 Passed: SMART test checked drive "1 TB WDC WD1001FALS-40Y6A0 Media (SN#WD-WCATR2452548)".
2012-12-28 21:01:07 Passed: File Structures test checked volume "Macintosh HD".
2012-12-28 21:01:07 Passed: File Structures test checked volume "Recovery".
2012-12-28 21:02:19 Passed: File Structures test checked volume "G-Drive_Q_232".
2012-12-28 21:02:21 Passed: File Structures test checked volume "H_G_Wells".
2012-12-28 21:04:43 Passed: Volume Structures test checked volume 'Macintosh HD' (disk0s2).
Volume Macintosh HD on disk0s2 mounted
2012-12-28 21:04:45 Passed: Volume Structures test checked volume 'Recovery' (disk1s3).
Volume Recovery on disk1s3 mounted
2012-12-28 21:06:36 Passed: Volume Structures test checked volume 'G-Drive_Q_232' (disk1s2).
Volume G-Drive_Q_232 on disk1s2 mounted
2012-12-28 21:08:36 Passed: Volume Structures test checked volume 'H_G_Wells' (disk2s2).
Volume H_G_Wells on disk2s2 mounted
2012-12-28 21:08:36 Passed: Volume Structures test checked partition map for disk '1 TB WDC WD1001FALS-40Y6A0 Media'.
2012-12-28 21:08:37 Passed: Volume Structures test checked partition map for disk '250 GB HDT72252 5DLA380 Media'.
2012-12-28 21:08:37 Passed: Volume Structures test checked partition map for disk '500 GB Hitachi HDT725050VLA360 Media'.
2012-12-29 00:29:39 Passed: Surface Scan test scanned the drive "1 TB WDC WD1001FALS-40Y6A0 Media (SN#WD-WCATR2452548)".
2012-12-29 01:48:22 Passed: Surface Scan test scanned the drive "250 GB HDT72252 5DLA380 Media".
2012-12-29 05:50:13 Passed: Surface Scan test scanned the drive "500 GB Hitachi HDT725050VLA360 Media".
2012-12-29 12:30:03 Passed: I/O error check passed.
2012-12-29 12:30:11 Passed: Memory test checked 4.19 GB of 8 GB total memory.
MicroMat Inc
Makers of TechTool
Last Edit: 29 Dec 2012 17:46 by micromattech3.
The administrator has disabled public write access.

Re: I think we need a "stop Checkmate button" 29 Dec 2012 18:03 #3483

Thanks for your quick reply.
Unfortunately I uninstalled Checkmate to stop it and then reinstalled after my backup so in the console the Checkmate logs are from the new install.
I checked in the "all messages" from the console at the time of Synchronize errors but it's really too tricky for me to understand them. I didn't find any mention of Checkmate at this period but some occurrences of Techtool pro deamon..... I don't know if it can be related...

So, Checkmate is running again. I'll check the logs if such errors occur again.

JM
The administrator has disabled public write access.

Re: I think we need a "stop Checkmate button" 29 Dec 2012 18:47 #3484

You are welcome, and thanks for the update.

The TechToolProDaemon has not been involved in any reported conflicts with Checkmate or Synchronize ProX.

If we receive other reports of a conflict between Sychronize ProX and Checkmate, we can easily fix the problem by adding Synchronize ProX to the list of programs that prevent Checkmate from running tests. Right now, having either Disk Utility or the TechTool Pro application open prevents Checkmate from running tests.
MicroMat Inc
Makers of TechTool
The administrator has disabled public write access.

Re: I think we need a "stop Checkmate button" 31 Dec 2012 16:57 #3506

I have also had Checkmate interrupt a hard drive back up (using Super Duper, a program that has always worked fine for me, and OS 10.6.8). I opened Checkmate and turned it off ans restarted the backup, and it worked fine.

I also get reports from Checkmate about Power On Self-test failure, but there is no other sign of this. The log says to check it with Tech Tool, but Tech Tool doesn't seem to have a way of checking this. No other diagnostic program indicates a problem. Since this has been constant since I installed Checkmate-which also occasionally asks me to relaunch the finder, in the middle of nothing--basically, this program has been pretty annoying since it was installed.

Thanks...
The administrator has disabled public write access.

Re: I think we need a "stop Checkmate button" 31 Dec 2012 17:11 #3507

Thanks for your report, which is the second one mentioning the Finder problem with Mac OS X 10.6.

Please use the Send Report feature in the Checkmate application's Checkmate menu. I know that the Power On Self-test is simply reading from the system log entry at startup. It is not performing that test itself, which the firmware and hardware perform before Mac OS X is loaded. The Send Report feature automatically sends us all of the Checkmate logs, so we can see what data the program was reading to provide that diagnosis. You will receive a reply by email after the company reopens on January 2. Thank you.

You might consider shutting down your Macintosh completely, waiting a few minutes, rebooting, and listening to see if any beeps occur at reboot. Here is what the Checkmate manual states about the Power-On Self Test, on page 13:

Power-On Self Test

The Power-On Self Test (POST) is an automatic test that is run by your Mac’s hardware each time your Mac powers up, before Mac OS X is loaded. The test is not performed in the case of a restart. POST checks the basic functioning of RAM, Processor and boot ROM.

Checkmate gathers the results of this test and displays them. If a failure result is reported, it is likely you would have heard a number of system beeps instead of the normal startup chime. The number of beeps indicates the potential issue with your Macintosh:

1 beep = No RAM installed.

2 beeps = Incompatible RAM types installed.

3 beeps = No good banks.

4 beeps = No good boot images in the boot ROM or bad system configuration block.

5 beeps = Processor is not usable.
MicroMat Inc
Makers of TechTool
The administrator has disabled public write access.

Re: I think we need a "stop Checkmate button" 31 Dec 2012 17:18 #3508

As for Checkmate interrupting Super Duper, opening the Checkmate application, and then quitting it, has no effect on the Checkmate background processes, which perform the tests and record the results in logs. The application is simply an interface to the logs. You can see the background processes in Activity Monitor, located in /Applications/Utilities.

I am using Mac OS X 10.7.5 myself, because my graphics card is not yet properly supported by Mountain Lion, so I would get no animations in TechTool Pro. I have not had Checkmate interfere with my Super Duper backups (I use both Super Duper and Time Machine, and would not want to be without either).
MicroMat Inc
Makers of TechTool
The administrator has disabled public write access.

Re: I think we need a "stop Checkmate button" 31 Dec 2012 17:32 #3509

If this occurs again, I will send in the report. As far as restarting and listening for the beeps, I've done that, more than once--no issues at all.

I did pick up from the answer to someone else--maybe in another topic--that idea of purging the log--So I've done that; I'll see what happens.

Thanks.
The administrator has disabled public write access.

Re: I think we need a "stop Checkmate button" 31 Dec 2012 17:37 #3510

You are welcome.

The Status window in Checkmate 1.0.1 will continue to show a result of "failure" for a test that has ever produced that result, even if a more recent running of the test produces a diagnosis of "pass". Since the Power-On Self Test is performed by the Macintosh itself at boot (not restart) time, there will be no further data for Checkmate to read about that topic until a reboot occurs.
MicroMat Inc
Makers of TechTool
The administrator has disabled public write access.

Re: I think we need a "stop Checkmate button" 04 Jan 2013 13:16 #3533

Checkmate seems to be an incurable alarmist. Even if I purge the logs, so the program starts with all areas reading “pending,” after powering off and powering on, Checkmate insists on telling me that that the Power On Self-Test Failed. I check with System Profiler, which says it passed. And, of course, when I power on, I get a normal chime, and none of the alert sounds. This has happened many times—I have to characterize it as a permanent condition.

At the same time it gives me the false warning about the Power On Self-Test, Checkmate insists after each power on telling me that: A disk related I/O error was found on disk “disk3.” The problem with this is that there is no disk called “disk3.” I can't find it, and neither can any of the diagnostic/maintenance programs. There is only the HD drive installed in the MacBook. This warning keeps getting repeated, even after several power offs and power ons. Earlier, I was also getting a warning about “disk4”.

I have made a couple of attempts to “Send Report”. I think it has worked, but I have to say that the process of “gathering files” takes a long time—once I gave up and quit the program after 45 minutes—and during that process, it’s nearly impossible to use any other programs on the computer. Actually, just having Checkmate open seems to slow everything else down.

It’s also true that at one point Checkmate decided that my battery had failed its test, though the program changed its mind about that after a while.

So far, I have to characterize Checkmate as a real problem in my work—I’ve spent too much time chasing after non-existent problems that Checkmate “warns” me about. It’s been worse than a waste of money, since it has cost me a lot of fruitless time and effort.

So, in order to be able to post this to the forum, I’ll quit Checkmate and open Firefox.

Perhaps my next step will be to uninstall Checkmate and install it again, though I don’t feel optimistic about that either.
The administrator has disabled public write access.

Re: I think we need a "stop Checkmate button" 04 Jan 2013 14:01 #3535

Thanks for using the Send Report feature.

If you have a large system log, it could take a while for Checkmate to compress the log and send it to us.

Checkmate refers to volumes using the BSD (Unix) identifiers in some cases, because that is how the operating system and all programs must refer to them behind the scenes. You can see the BSD identifiers for your volumes by using Disk Utility, selecting a volume, and clicking the Info button at the top of the Disk Utility window. An easier way to see the BSD identifiers for all volumes at once is to open Terminal, located in /Applications/Utilities, and type:

df

then press the Return key:
Macintosh:~ MMT3$ df
Filesystem    512-blocks      Used  Available Capacity  Mounted on
/dev/disk0s2  1951845952 304980144 1646353808    16%    /
devfs                375       375          0   100%    /dev
map -hosts             0         0          0   100%    /net
map auto_home          0         0          0   100%    /home
/dev/disk2s2   976101344 257116376  718984968    27%    /Volumes/H_G_Wells
/dev/disk1s2   479912840 277780048  202132792    58%    /Volumes/G-Drive_Q_232
/dev/disk1s3     7550360     51328    7499032     1%    /Volumes/Recovery
Macintosh:~ MMT3$

The df command means "display filesystems".

The BSD identifiers specify a hard drive device first, then the volume (also called a parition, or slice) second. So what Unix calls disk2s2 refers the second hard drive device, and the second volume (or slice) on that device. Devices have invisible volumes on them. The only visible volume on that drive is my Time Machine volume, H_G_Wells, on disk2s2.

The active boot volume is always disk0 and mounted on /, and its volume name does not appear in the output of the df command. My active boot volume is:

/dev/disk0s2 1951845952 304980144 1646353808 16% /


We need to see the Checkmate logs to see why the Power On Self-Test is being reported as a failure.

The diagnosis of an i/o error is being read from the All Messages log. If you open the Console application, located in /Applications/Utilities, and search for:

i/o

and then for:

input/output

the Console will find the reference to the error, assuming the log is still current.

Here is an example of the operating system reporting an input/output error:

1/7/08 1:51:46 PM [0x0-0x534534].com.techtoolpro4.daemon[70842] # ReadRawBlock attempt to read 16777216 bytes at offset 278798336.000000 failed with Input/output error
1/7/08 1:51:46 PM [0x0-0x534534].com.techtoolpro4.daemon[70842] # ReadRawBlock CANNOT READ: blockNumber 544528.000000, numBlocks: 32768, errno: 5, Input/output error

That case, from Surface Scan turned out to be a bad block in the disk directory, which lead to a drive replacement.

Thanks for your cooperation.
MicroMat Inc
Makers of TechTool
Last Edit: 04 Jan 2013 14:14 by micromattech3.
The administrator has disabled public write access.

Re: I think we need a "stop Checkmate button" 04 Jan 2013 16:31 #3536

Okay, thanks for this information. I followed your instructions, which were clear, and here's what I found. The df command gave me this:

df
Last login: Fri Jan 4 07:42:30 on console
Steves-MacBook-2:~ stevecagan$ df
Filesystem 512-blocks Used Available Capacity Mounted on
/dev/disk0s2 976101344 888219664 87369680 92% /
devfs 215 215 0 100% /dev
map -hosts 0 0 0 100% /net
map auto_home 0 0 0 100% /home
/dev/disk1 408036 408036 0 100% /Volumes/SLIDE_SHOW_DVD_TEST_1
Steves-MacBook-2:~ stevecagan$


The dev/disk1 is actually a dmg file--so it's a volume, I guess.

Please note that there is no disk3, though Checkmate insists on finding an i/o error on it.

Checking for i/o and input/output errors in Console, both under "all messages" and "console message," I got a "not found" response.

I think I did manage to send in the report earlier this morning, so maybe that will help.

Thanks...
The administrator has disabled public write access.

Re: I think we need a "stop Checkmate button" 04 Jan 2013 16:48 #3537

You are welcome, and I hope we will be able to determine what disk3 was.

Your startup volume is way too full, with 92% of its space occupied by files. If the operating system needs to create a lot of swapfiles, the swapfiles will be likely to be extremely fragmented, because the remaining free space on the startup volume before the creation of the swapfiles was extremely fragmented. Such a situation leads to very poor performance, with slowdowns that can last many minutes.

The standard guideline for all Unix-based systems is to have at least 15% free space on the active startup volume. Many experienced users would not consider having less than 25% free space.

The following text is an old posting from other forums from which I have had to remove some material, because the links no longer work:


The 15% free-space rule has been a standard rule-of-thumb for both the Macintosh when using Mac OS 8 and 9 and for Unix in general for years. It is mentioned in the source code for many Unix flavors, including Mac OS X. It is intended to keep users out of trouble without having to make a hobby out of disk space management. It works, and there is no question that it sometimes causes drives to provide less useful storage than they could.

Unfortunately, there is no simple way to calculate how much free space is really needed on a particular volume.

One important factor is whether the volume is bootable. Just to make virtual memory work correctly, you need free space for swapfiles equal to 4 times the amount of the installed RAM, or possibly 8 times, depending on the interpretation of something written by Amit Singh. It is true that starting in Tiger, swapfiles can be fragmented without causing a kernel panic as they did before. However, as one of our developers put it, when the swapfiles are fragmented, performance suffers, and “things get really ugly, really fast.” Your chances of having sufficient disk space that is both free and contiguous increase with the amount of free space on the volume. “Contiguous” here means “all in one piece.”

In addition to containing the swapfiles, the invisible folder at /private/var/vm contains the sleepimage file, which is the size of the installed RAM.

If the disk directory is to be rebuilt, the Catalog B-Tree and the Extents B-Tree must each be written to a piece of disk space that is free and contiguous. These files can become fragmented later, but must be created in a single piece, called an “extent”. You can see the size of the Catalog B-Tree and the Extents B-tree using hfsdebug, a free utility written by Amit Singh (now obsolete, and replaced by the commercial program fileXray, mentioned at the bottom of Singh's page). Their initial sizes are determined when the volume is created. The size of the Catalog B-Tree may increase if enough files are added to the volume, and the size of the Extents B-Tree may increase if enough files are fragmented. (Apple refers to the Extents B-Tree as the Extents Overflow file.)

Spotlight indexes can take up a lot of disk space. If the Spotlight indexes cannot grow, you cannot find any new files on the drive using Spotlight.

In Mac OS X 10.4, Apple introduced a new disk directory file called the Extended Attributes file. It requires disk space. Each system software upgrade tends to require more space for new features, with no advance warning.

Optimizers have a free and contiguous disk space requirement. Our optimizer requires that it have free, contiguous disk space at least the size of the largest file to be defragmented. The less free space there is on the drive, the greater the chance that this requirement will not be met.

One of the reasons we made it possible to alter the alert setting for our free space feature in TechTool Pro is that less free space is required for volumes that are not bootable, and are simply used for storage. I am not going to be able to advise people on how little free space is enough.

There are people in various forums who are simply annoyed at being told that they must have any free space on a volume. Why some people enjoy doing what our president (Jeff, not Barack) refers to as “stuffing a disk drive to its gills” has been a mystery to me since 1991, when I got my Macintosh IIsi 5/80. On the other hand, there are users with a lot of RAM and a relatively small boot volume who believe that leaving at least 20% of a boot volume free is prudent. A drive can quickly fill if an error is repeatedly recorded in a log file and there is not enough free space for the log. Where Disk My Disk Space Go? has a posting in which user thallock reports a 54 GB log file (archived page may take a few minutes to load).
MicroMat Inc
Makers of TechTool
Last Edit: 04 Jan 2013 16:57 by micromattech3.
The administrator has disabled public write access.

Re: I think we need a "stop Checkmate button" 04 Jan 2013 17:03 #3538

Here is the Get Info box for my startup volume:


Attachment ScreenShot2013-01-04at12.00.38PM.png not found

MicroMat Inc
Makers of TechTool
The administrator has disabled public write access.

Re: I think we need a "stop Checkmate button" 04 Jan 2013 17:04 #3539

Thanks--I am aware of the free space issue--unfortunately I travel a lot and in the course of those travels, the hard drive fills up--but I have already been in the process of transferring files to other disks.

Still, does that explain the problems with Checkmate? I just threw out the Checkmate log once again, and powered off and powered on. Finally, Checkmate has let go of the disk3 problem (but this is after nearly half-a dozen power-off, power-on cycles). But I'm still getting the Power On Self-Test warning in Checkmate, though System Profiler says it passed...

Thanks...
The administrator has disabled public write access.

Re: I think we need a "stop Checkmate button" 04 Jan 2013 17:11 #3540

You are welcome.

I do not know why you are getting odd results with Checkmate. We need to see the logs. I hope we will be able to explain your results. I would like to see the program report more details about the i/o errors.
MicroMat Inc
Makers of TechTool
The administrator has disabled public write access.

Re: I think we need a "stop Checkmate button" 04 Jan 2013 17:17 #3541

Have you received the logs I sent you? If not, I'll try again...
The administrator has disabled public write access.

Re: I think we need a "stop Checkmate button" 04 Jan 2013 17:23 #3542

Yes, we have received the logs. Thank you. It may take a while to figure out why you are getting these odd results. I have been told that the last Power On Self-Test was a pass, but an earlier one was a failure. (Recall that the operating system runs this test only during a boot, not a restart.) You will get a reply by email from This email address is being protected from spambots. You need JavaScript enabled to view it. , and thanks again for your cooperation.
MicroMat Inc
Makers of TechTool
The administrator has disabled public write access.

Re: I think we need a "stop Checkmate button" 04 Jan 2013 17:29 #3543

For people not familiar with the location of the Power On Self-Test results in Apple System Information:


Attachment ScreenShot2013-01-04at12.16.39PM.png not found

MicroMat Inc
Makers of TechTool
The administrator has disabled public write access.

Re: I think we need a "stop Checkmate button" 05 Jan 2013 14:48 #3549

I submitted a question in another post, but looking over this one, I wanted to pass on that I too have had Checkmate run when my computer is in use. I would be watching Netflix on a secondary monitor and my working in Safari on my main screen when both would freeze while Checkmate did its thing.

I have already submitted my logs in reference to my prior situation.
The administrator has disabled public write access.

Re: I think we need a "stop Checkmate button" 05 Jan 2013 17:18 #3551

Thanks for submitting the logs.

Checkmate was probably running the Volume Structures test on the active boot volume, which requires "freezing" it. A dialog box appears, too briefly, asking if you want the test to take place and warning about how the computer will slow down, but then the test begins without your confirming that you want it to take place. That should be fixed in the next version.
MicroMat Inc
Makers of TechTool
The administrator has disabled public write access.

Re: I think we need a "stop Checkmate button" 07 Jan 2013 14:26 #3556

I have uninstalled Checkmate because it insisted in checking the backup disk while it was being used by Superduper and reporting it faulty. Superduper abandoned the backup. I checked the backup up disk later ( a full surface scan etc ) with Techtool Pro and it found no problems.
I would need a way to stop Checkmate when Superduper starts its automatic backup.
The administrator has disabled public write access.

Re: I think we need a "stop Checkmate button" 07 Jan 2013 15:14 #3557

Thanks for your report.

The problem with Checkmate and Super Duper has been noted. I use Super Duper myself, but I supposed it is just a matter of timing that none of my backups were interrupted.
MicroMat Inc
Makers of TechTool
The administrator has disabled public write access.

Re: I think we need a "stop Checkmate button" 07 Jan 2013 20:27 #3558

I would appreciate it if those of you who have encountered the problem with Checkmate and Super Duper would send an email message to This email address is being protected from spambots. You need JavaScript enabled to view it. , including a link to this thread, and mentioning Super Duper. Thank you.

In the meantime, remember that having Disk Utility or the TechTool Pro application open prevents Checkmate from running its tests.
MicroMat Inc
Makers of TechTool
Last Edit: 07 Jan 2013 20:39 by micromattech3.
The administrator has disabled public write access.

Re: I think we need a "stop Checkmate button" 07 Jan 2013 23:14 #3559

I sent in the note ou sked for. Here's the whole text of my note:

Hello,

I am one of the people who has had Checkmate interfere with a SuperDuper backup. I usually let those backups run overnight. One time, the backup was interrupted—unfortunately, I didn’t record the error message form SuperDuper. But I turned off Checkmate and started the copy again, and it worked fine. (this has been discussed in this thread: www.micromat.com/index.php?option=com_ku...d=3480&Itemid=0#3508)

This particular error has not repeated, though Checkmate keeps insisting that the Power On Self test has failed, although it hasn’t. It has also identified errors on non-existent volumes or disks, and tagged errors in files that Tech Tool did not find. And every once in a while it asks me to relaunch the Finder

I have on the one hand wasted a lot of time trying to get Checkmate to run properly., and on the other hand I have come to the conclusion that an alert from Checkmate probably isn’t worth following up—it’s going to the the Power On Self test again...

I think the next step is to uninstall Checkmate. I’m trying to decide whether to ask for my money back or to wait to see if a new version works better.

Thank you,

Steve Cagan
The administrator has disabled public write access.

Re: I think we need a "stop Checkmate button" 07 Jan 2013 23:43 #3560

The fact that the Finder has to be relaunched is beyond our control. Some of the system software tools in Mac OS X 10.6 have features that are only fully implemented in Mac OS X 10.7 and 10.8. Only Apple can fix that problem, and that is unlikely.

The non-existent volume is probably a DVD that was ejected. The system log recorded the error, and then the disc was ejected, so there is no longer a disc with the specified BSD identifier. The program did not invent the disc. DVDs often produce i/o errors when a retry is needed to read a sector.

If you send one of the files that Checkmate flagged as suspect to This email address is being protected from spambots. You need JavaScript enabled to view it. , we can have the programmer take a look at how it gets examined by the File Structures test in both TechTool Pro and Checkmate. Thank you.
MicroMat Inc
Makers of TechTool
The administrator has disabled public write access.

Re: I think we need a "stop Checkmate button" 08 Jan 2013 00:14 #3561

No matter who the relaunches are caused by, the effect is that it makes the program more of an irritant than a help.

I never said that CM invented what it called "disk3." My problem is that after all eternal disks were disconnected, logs were purged, and the computer was powered off and on, CM continued to report the "error."

Unfortunately, I've purged the logs in which the "problems" were flagged.

Thanks.
The administrator has disabled public write access.

Re: I think we need a "stop Checkmate button" 08 Jan 2013 00:42 #3562

It would be helpful if people who have problems would contact us first before uninstalling the program, which causes the logs to be deleted. The logs have the only useful evidence.

I suspect that the customers who have been alerted to serious disk directory errors (such as a corrupted Time Machine volume) and diagnoses of bad blocks that turned out to be a failing disk controller would be willing to tolerate a mouseclick to relaunch the Finder in order to keep the benefits of Checkmate. I am sorry that you appear to have had the worst experience that anyone has had with the program.
MicroMat Inc
Makers of TechTool
The administrator has disabled public write access.

Re: I think we need a "stop Checkmate button" 08 Jan 2013 00:42 #3563

Sorry, one more question. I'm trying to uninstall Checkmate an have run into another problem, I trashed the program and the preferences files and whatever else I could find with the name of the program. But, after a couple of power off-power on cycles, the CM icon is still in the menu bar. When the computer goes on, the icon is flashing between red and black--if I go to it, it tells me there are two errors. but if I click on "About CM," "Open CM" or "View Log," I get nothing.

Can you tell me how to eliminate that icon from the menu bar?

Thanks.
The administrator has disabled public write access.

Re: I think we need a "stop Checkmate button" 08 Jan 2013 00:49 #3564

Checkmate, like most applications, cannot be completely removed by trashing files in the Finder. Please use the Checkmate installer to reinstall the program, and then use the installer's Customize button to remove the program. That is explained in the manual on page 3.


Attachment CheckmateInstallerCustomizebutton.png not found

MicroMat Inc
Makers of TechTool
Last Edit: 15 Feb 2013 23:20 by micromattech3. Reason: Added Screen Capture of Customize button
The administrator has disabled public write access.

Re: I think we need a "stop Checkmate button" 08 Jan 2013 00:52 #3565

I id, of course, contact you first--uninstalling is just the last step. And I sent you a couple of log reports.
The administrator has disabled public write access.

Re: I think we need a "stop Checkmate button" 08 Jan 2013 00:53 #3566

Thanks for this--I'll do it...
The administrator has disabled public write access.

Re: I think we need a "stop Checkmate button" 08 Jan 2013 00:55 #3567

You are welcome, and thanks for all the data you have sent. Someone will benefit from it.
MicroMat Inc
Makers of TechTool
The administrator has disabled public write access.

Re: I think we need a "stop Checkmate button" 04 Feb 2013 08:43 #3684

Hi all,

I like and use Tech Tool Pro 6. However, I have uninstalled Checkmate, and intend to ask for a refund. I have lost hours of work because it started up while I was working (I know it's not supposed to, but it did - more than once). It not only froze my machine, it made programmes choke, and close without saving, causing loss of work. I'll not take that risk again.

For me, this programme is a nice idea, but not yet ready for prime time.
The administrator has disabled public write access.

Re: I think we need a "stop Checkmate button" 04 Feb 2013 11:37 #3685

Before you request a refund, please send an email message to This email address is being protected from spambots. You need JavaScript enabled to view it. , including a link to this thread. Thank you.
MicroMat Inc
Makers of TechTool
The administrator has disabled public write access.

Re: I think we need a "stop Checkmate button" 04 Feb 2013 12:05 #3686

I also uninstalled and trashed the program. It seemed the only solution. The important concrete response that I got from Micromat to the problems I was having was that other people were not reporting the same problems. Which may have been true, of course, but did not resolve my difficulties, so uninstalling seemed the only option.

However, I did not ask for a refund, and now think that I should have. Please tell me how to do that.

Thank you.
The administrator has disabled public write access.

Re: I think we need a "stop Checkmate button" 04 Feb 2013 14:09 #3687

Please contact the sales department by sending an email message to This email address is being protected from spambots. You need JavaScript enabled to view it. .
MicroMat Inc
Makers of TechTool
The administrator has disabled public write access.

Re: I think we need a "stop Checkmate button" 06 Feb 2013 18:43 #3697

So I did contact the sales department--upon hearing that an update was about to be released, I decided to wait to give that a try. Once again, Checkmate insists that there was a POST failure, though I have no other indication of that. Once again I'm spending a lot of time pursuing apparent false positives. I have asked CM to send you a report, which it seems to be in the process of doing.

BTW, I had hoped to see the "stop CM button" in the update--am I missing it.

I'll wait to see if you can tell me why I'm getting this apparent false positive and what I can do to stop it. Here's the df file from Terminal, by the way;

Last login: Wed Feb 6 12:55:06 on console
dSteves-MacBook-2:~ stevecagan$ df
Filesystem 512-blocks Used Available Capacity Mounted on
/dev/disk0s2 976101344 636198328 339391016 66% /
devfs 213 213 0 100% /dev
map -hosts 0 0 0 100% /net
map auto_home 0 0 0 100% /home
Steves-MacBook-2:~ stevecagan$
The administrator has disabled public write access.

Re: I think we need a "stop Checkmate button" 06 Feb 2013 20:05 #3698

Thanks for your patience and cooperation.

As for the stop button, please send a message to This email address is being protected from spambots. You need JavaScript enabled to view it. , including a link to this thread. Thank you.
MicroMat Inc
Makers of TechTool
The administrator has disabled public write access.

Re: I think we need a "stop Checkmate button" 11 Feb 2013 20:40 #3724

Seems that people are having problems with this. I would like to take advantage of the discount offered but hesitate if Checkmate is going to cause more problems than it's worth.... Anyone have positive comments about the product as forums usually bring out only the bad....
The administrator has disabled public write access.

Re: I think we need a "stop Checkmate button" 11 Feb 2013 21:13 #3725

Most of the reported problems are references to the first release, version 1.0.2. Checkmate is now at version 1.0.3, released last week:


Changes:

• Fixed reported runtime issue where Checkmate would not automatically test.

• Fixed memory allocation issues while testing was being performed.

• Updated reporting for File Structures issues to avoid truncating file names.

• Addressed issue for Surface Scan test in which same disk was tested multiple times.

• Updated Send Report mechanism to require an email address prior to submitting.

• Added ToolTip support for the date column in Logs.

• Added support to cancel Memory Test during testing.

• Added German and Japanese localization.

• Many other fixes and enhancements.
MicroMat Inc
Makers of TechTool
Last Edit: 11 Feb 2013 21:14 by micromattech3.
The administrator has disabled public write access.

Re: I think we need a "stop Checkmate button" 15 Feb 2013 15:55 #3734

I also tried to trash Checkmate due to the following reasons:

1. The pop up that has the "Skip" button only appears for 1 - 2 seconds so I don't have time to react.
2. When Checkmate runs, it locks up my iMac for at least 30 seconds and I can't scroll, type, etc. I understood that Checkmate would only run when I was NOT doing anything.

Now I've trashed AND emptied the trash of ALL items that reference Checkmate in Spotlight, restarted my iMac, and it STILL pops up and then locks my iMac How do I get this piece of crappy software OFF permanently?
Cogito Ergo Mac
The administrator has disabled public write access.

Re: I think we need a "stop Checkmate button" 15 Feb 2013 16:04 #3735

We expect to have a better means of skipping the testing of the active startup volume in a future version.

Removal of Checkmate is explained in posting 3564 in this thread, and in the Checkmate manual on page 3.
MicroMat Inc
Makers of TechTool
The administrator has disabled public write access.

Re: I think we need a "stop Checkmate button" 15 Feb 2013 17:17 #3736

Tried that procedure - when it was "done" it said: "The installation was successful. The software was installed."

I want to UNINSTALL it. Instead even after running your "uninstaller", I'm being told that the software is INSTALLED.
Cogito Ergo Mac
The administrator has disabled public write access.

Re: I think we need a "stop Checkmate button" 15 Feb 2013 18:04 #3737

You need to use the Customize button in the Installer to remove the program, as was explained in posting 3564 above. If you used the Customize button, and that did not work, please send an email message to This email address is being protected from spambots. You need JavaScript enabled to view it. , including a link to this thread. Thank you.
MicroMat Inc
Makers of TechTool
The administrator has disabled public write access.

Re: I think we need a "stop Checkmate button" 16 Feb 2013 05:57 #3740

I DID use the "Customize" button; deselected all but the "Uninstall option" Even after doing that, when the progress thermometer finishes, the message still states "The installation was successful. The software was installed."
Cogito Ergo Mac
The administrator has disabled public write access.

Re: I think we need a "stop Checkmate button" 16 Feb 2013 14:10 #3741

In case there is something wrong with your Checkmate installer, please use the Login/Register link at the top of this page, then go to your available downloads at the bottom of the new page and download the Checkmate installer again. Repair permissions using Disk Utility before using the installer. If that does not work, please send a message to This email address is being protected from spambots. You need JavaScript enabled to view it. . You will receive a reply by email on Monday. There are no other reports of the Customize button failing to remove the program.
MicroMat Inc
Makers of TechTool
The administrator has disabled public write access.

Re: I think we need a "stop Checkmate button" 16 Feb 2013 14:17 #3742

I just ran the Checkmate installer to remove the program. The action column says "install" before the user begins, and the message at the end does say ""The installation was successful. The software was installed." However, the program was in fact removed. The application package is gone from /Applications, the icon is gone from the menu bar, and the background processes are no longer running.
MicroMat Inc
Makers of TechTool
The administrator has disabled public write access.

Re: I think we need a "stop Checkmate button" 16 Feb 2013 16:27 #3743

Yes, after I posted last I did a THOROUGH Spotlight search and made sure that only the Checkmate.dmg file showed up. So there is a bug in the Uninstaller procedure that says the software was successfully INSTALLED instead of successfully UN-INSTALLED.

Based on my long experience with MicroMat products, Checkmate is very poorly thought out and written - it should be pulled and not re-released until it meets the quality of TechTool Pro. I will not recommend it to anyone.
Cogito Ergo Mac
The administrator has disabled public write access.

Re: I think we need a "stop Checkmate button" 16 Feb 2013 16:44 #3744

There is clearly a problem with the way the uninstall routine reports the results. That will be easy to fix.

The people who have been alerted to S.M.A.R.T. failures, unremapped bad blocks, and corrupted Time Machine disk directories have a different perspective on the worth of Checkmate.

You cannot uninstall programs that involve background processes by using Spotlight to search for their files. There are references to the background processes that are inside plist files, and the launchctl command needs to be run to unload the background processes, so they will not be launched by launchd at login time. That is why a program that uses background processes should have an uninstall feature. Otherwise, when launchd tries to launch the background process that the user removed with the Finder, an error message referring to "throttling respawn" appears in the All Messages log many times:

"Throttling respawn" running every ten seconds.
MicroMat Inc
Makers of TechTool
Last Edit: 16 Feb 2013 16:55 by micromattech3.
The administrator has disabled public write access.
  • Page:
  • 1
  • 2
Time to create page: 0.434 seconds