Welcome, Guest
Username: Password: Remember me

Search Micromat Forum

Keyword

TOPIC: Disc Utility is produces inconsistent results with TTP 8 (eDrive) & Checkmate

Disc Utility is produces inconsistent results with TTP 8 (eDrive) & Checkmate 09 Jul 2015 05:26 #6540

My System: iMac (24" early 2008); 2.8 GHZ, Intel Core 2 Duo; 6GB 800MHz DDR2 SDRAM
with: OSX 10.10.4 (Yosemite);
TechTool Pro 8.0.2
Checkmate 1.1.4
Maxtor USB/Firewire: 149GB

On my main HD I was running a Checkmate 1.1.4 which was supposed to make me aware of HD failures before they occur. Checkmate is not running on my eDrive which is mounted on an external (Maxtor) drive connected to my computer via firewire. Checkmate indicated there are Partition Structure errors on each of the hard drives associated with my computer (One internal Drive, and 2 external Drives). The solution, supposedly (according to Checkmate), is to run Disk Utility (DU) to repair the drives. So, although I don't see how all 3 drives could have failed simultaneously. I ran DU on my main drive which provided the following results. (See attached pics -- I am also finding there are many files which longer open on my main drive and which have become corrupted, so I took the bait.)

(1) When Verifying and Repairing the DISK (i.e. not the volume) - Message: "Verifying partition map for "WDC WD32 ...... Problems were found with the partition map which might prevent rebooting. Error/Alert: Couldn't create temporary directory. ("Partition Map Scheme: GUID Partition Table")

(2) When I ran DU to Verify and Repair the VOLUME, I get the message (in green) "The Volume ... appears to be OK."

BUT - when I run the same version of OSX and DU from my eDrive (created with TechTool Pro v8.0.2) on an external USB Drive, DU gives all drives a clean bill of health with no error messages.

I have reformatted and repartitioned the main HD (but not the other drives). This has made no difference. The test results are the same. I have also tried changing the size of the partitions, again to no avail.

When I copied the main HD to another (3rd) external drive (via TTP Volume Cloning) and ran DU, I got the same result as for the first (main) drive. Copying over DU from the eDrive onto the 3rd Drive (Drag & Drop), also did not change the result. The message remains as per number 1 above. But then too, all drives appear to be working normally, and I don't see how 3 separate drives can fail at once. Should I replace the internal drive, or is there another solution? Is there a problem with DU in OS X, or the eDrive? THANKS for your help. I am stumped.

Ron
Attachments:
The administrator has disabled public write access.

Disc Utility is produces inconsistent results with TTP 8 (eDrive) & Checkmate 09 Jul 2015 10:41 #6541

Thanks for your clear and detailed report.

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. You will receive a reply by email.

I have never seen the error message you got when you selected the drive mechanism and tried to verify or repair the disk. The output of such a command should look like this:


Verifying partition map for “WDC WD1001FALS-40Y6A0 Media”
Checking prerequisites
Checking the partition list
Checking for an EFI system partition
Checking the EFI system partition’s size
Checking the EFI system partition’s file system
Checking the EFI system partition’s folder content
Checking all HFS data partition loader spaces
Checking booter partitions
Checking booter partition disk0s3
Verifying file system.
Checking Journaled HFS Plus volume.
Checking extents overflow file.
Checking catalog file.
Checking multi-linked files.
Checking catalog hierarchy.
Checking extended attributes file.
Checking volume bitmap.
Checking volume information.
The volume Recovery HD appears to be OK.
File system check exit code is 0.
Checking Core Storage Physical Volume partitions
The partition map appears to be OK

I have had in the last few weeks cases on my own iMac in which Checkmate reported a partition map failure on my usual startup volume. If I ran Disk Utility while booted from the same volume, it found no problem with the partition map. If I booted from the Recovery HD volume and ran Disk Utility, it said that it was adjusting the partition map to fit the size of the device. If your devices are working properly, I suspect that the problem being found by Checkmate is that the sum of the sizes of the partitions does not equal the size of the device. I have seen cases in which this problem is addressed by the operating system itself during a reboot. The relevant message is in the All Messages log, which can be read by the Console application, locate in /Applications/Utilities.
Attachments:
MicroMat Inc
Makers of TechTool
Last Edit: 09 Jul 2015 11:00 by micromattech3.
The administrator has disabled public write access.

Disc Utility is produces inconsistent results with TTP 8 (eDrive) & Checkmate 10 Jul 2015 23:04 #6548

Thanks for the prompt response. I will follow up on your recommendation.

I've been told the Checkmate gets it's source date from Disc Utility's analysis and output. As stated previoulsy, I've reformatted the drive but that's made no difference. I can't see that all 3 drives would have crashed at once, particularly not when they appear to be working OK, except for the file corruption and the inability to get rid of Disc Utility's error messages, which do not show up when DU is run off the eDrive.

Thanks again! Let's see where it goes.
The administrator has disabled public write access.

Disc Utility is produces inconsistent results with TTP 8 (eDrive) & Checkmate 11 Jul 2015 00:15 #6549

You are welcome.

If the error being reported by Checkmate is the fact that the sum of the sizes of the partitions does not equal the size of the device, then reformatting may not help. The operating system may be inconsistent in what it wants, and make minor adjustments during a reboot.

The gpt Terminal command shows that the starting and ending blocks of the various partitions of my startup device are unchanged after Disk Utility repaired the partition map, stating that it was adjusting the partition map to fit the size of the device.

Start by launching Terminal, located in /Applications/Utilities. Type:

df

then press the Return key. You see a list of volumes and their BSD identifiers (such as /dev/disk2s2):
Macintosh:/ mmt3$ df
Filesystem    512-blocks      Used  Available Capacity   iused     ifree %iused  Mounted on
/dev/disk0s2  1951583808 380416448 1570655360    20%  47616054 196331920   20%   /
devfs                373       373          0   100%       646         0  100%   /dev
map -hosts             0         0          0   100%         0         0  100%   /net
map auto_home          0         0          0   100%         0         0  100%   /home
/dev/disk2s2   976101344 844483528  131617816    87% 105560439  16452227   87%   /Volumes/H_G_Wells
/dev/disk1s2   479912840 373164008  106748832    78%  46645499  13343604   78%   /Volumes/G-Drive_Q_232

Despite using the "code" tag for the output of the df command, the output in the Mounted On column is not displaying correctly. With more data and worse formatting:

Macintosh:/ mmt3$ df
Filesystem 512-blocks Used Available Capacity iused ifree %iused Mounted on
/dev/disk0s2 1951583808 380416448 1570655360 20% 47616054 196331920 20% /
devfs 373 373 0 100% 646 0 100% /dev
map -hosts 0 0 0 100% 0 0 100% /net
map auto_home 0 0 0 100% 0 0 100% /home
/dev/disk2s2 976101344 844483528 131617816 87% 105560439 16452227 87% /Volumes/H_G_Wells
/dev/disk1s2 479912840 373164008 106748832 78% 46645499 13343604 78% /Volumes/G-Drive_Q_232



Then type:

diskutil list

Press the Return key:
Macintosh:/ mmt3$ diskutil list
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                  Apple_HFS Macintosh HD            999.2 GB   disk0s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *250.1 GB   disk1
   1:                        EFI EFI                     209.7 MB   disk1s1
   2:                  Apple_HFS G-Drive_Q_232           245.7 GB   disk1s2
   3:                 Apple_Boot Recovery HD Experiment  3.9 GB     disk1s3
/dev/disk2
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk2
   1:                        EFI EFI                     209.7 MB   disk2s1
   2:                  Apple_HFS H_G_Wells               499.8 GB   disk2s2


Partition map after diagnosis from Checkmate, but before repair:
Macintosh:/ mmt3$ sudo gpt -rvvv show -l /dev/disk0
Password:
gpt show: /dev/disk0: mediasize=1000204886016; sectorsize=512; blocks=1953525168
gpt show: /dev/disk0: PMBR at sector 0
gpt show: /dev/disk0: Pri GPT at sector 1
gpt show: /dev/disk0: GPT partition: type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, start=40, size=409600
gpt show: /dev/disk0: GPT partition: type=48465300-0000-11AA-AA11-00306543ECAC, start=409640, size=1951583808
gpt show: /dev/disk0: GPT partition: type=426F6F74-0000-11AA-AA11-00306543ECAC, start=1951993448, size=1269536
gpt show: /dev/disk0: Sec GPT at sector 1953525167
       start        size  index  contents
           0           1         PMBR
           1           1         Pri GPT header
           2          32         Pri GPT table
          34           6         
          40      409600      1  GPT part - "EFI System Partition"
      409640  1951583808      2  GPT part - "Customer"
  1951993448     1269536      3  GPT part - "Recovery HD"
  1953262984      262151         
  1953525135          32         Sec GPT table
  1953525167           1         Sec GPT header



I restarted from the Recovery HD volume and used Disk Utility to repair the partition map on my usual startup device. I got the message:

Adjusting partition map to fit whole disk as required.

Yet the partition map as shown in Terminal is unchanged by the repair.

(The Recovery HD volume does not permit screen captures.)

Partition map after repair.
[Restored]
Last login: Sat Jun 27 11:44:14 on console
Macintosh:/ mmt3$ sudo gpt -rvvv show -l /dev/disk0
Password:
gpt show: /dev/disk0: mediasize=1000204886016; sectorsize=512; blocks=1953525168
gpt show: /dev/disk0: PMBR at sector 0
gpt show: /dev/disk0: Pri GPT at sector 1
gpt show: /dev/disk0: GPT partition: type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, start=40, size=409600
gpt show: /dev/disk0: GPT partition: type=48465300-0000-11AA-AA11-00306543ECAC, start=409640, size=1951583808
gpt show: /dev/disk0: GPT partition: type=426F6F74-0000-11AA-AA11-00306543ECAC, start=1951993448, size=1269536
gpt show: /dev/disk0: Sec GPT at sector 1953525167
       start        size  index  contents
           0           1         PMBR
           1           1         Pri GPT header
           2          32         Pri GPT table
          34           6         
          40      409600      1  GPT part - "EFI System Partition"
      409640  1951583808      2  GPT part - "Customer"
  1951993448     1269536      3  GPT part - "Recovery HD"
  1953262984      262151         
  1953525135          32         Sec GPT table
  1953525167           1         Sec GPT header
MicroMat Inc
Makers of TechTool
Last Edit: 11 Jul 2015 00:21 by micromattech3.
The administrator has disabled public write access.

Disc Utility is produces inconsistent results with TTP 8 (eDrive) & Checkmate 11 Jul 2015 01:38 #6550

So how did you run a diagnosis with Checkmate? I only get the log information, and don't see any access to tools.

In Terminal, my 'Capacity' column shows several descriptors as substantially less than what you are showing, with two entries of 1%, and one at 30%, and % used is typically about 1% below capacity. (I have no idea what all these numbers mean.)

As an aside, I am running my system now from a 2GB volume on the 3TB back-up drive connected via USB. My 320_GB drive has been formatted into two volumes, but the drive contains no data. (What would happen if I tried to restore this drive with the original installation CD that came with the computer? Since there is not data on the drive, I guess it can't hurt, although i doubt it will make a difference.)

Based on the foregoing, Terminal gives the following report:
Last login: Fri Jul 10 15:44:00 on console
Tanya:~ RAP$ df
Filesystem    512-blocks       Used Available Capacity   iused    ifree %iused  Mounted on
/dev/disk2s2  1953904168 1239540160 713852008    64% 155006518 89231501   63%   /
devfs                382        382         0   100%       661        0  100%   /dev
/dev/disk0s2    43619016     226440  43392576     1%     28303  5424072    1%   /Volumes/OSX-bak
/dev/disk0s3   580589464     830584 579758880     1%    103821 72469860    0%   /Volumes/Macintosh HD
map -hosts             0          0         0   100%         0        0  100%   /net
map auto_home          0          0         0   100%         0        0  100%   /home
/dev/disk1s2   289948400   85342200 204606200    30%  10667773 25575775   29%   /Volumes/Maxtor-FW
/dev/disk2s3  1952191032 1386399640 565791392    72% 173299953 70723924   71%   /Volumes/HD-GDU3-1tBAK

Tanya:~ RAP$ diskutil list
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *320.1 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                  Apple_HFS OSX-bak                 22.3 GB    disk0s2
   3:                  Apple_HFS Macintosh HD            297.3 GB   disk0s3
/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *163.9 GB   disk1
   1:                        EFI EFI                     209.7 MB   disk1s1
   2:                  Apple_HFS Maxtor-FW               148.5 GB   disk1s2
   3:                  Apple_HFS eDrive                  15.0 GB    disk1s3
/dev/disk2
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *2.0 TB     disk2
   1:                        EFI EFI                     209.7 MB   disk2s1
   2:                  Apple_HFS HD-GDU3-1tb             1.0 TB     disk2s2
   3:                  Apple_HFS HD-GDU3-1tBAK           999.5 GB   disk2s3
Tanya:~ RAP$

I no longer have access to the Recovery HD volume as it was erased when i tried to repair the main drive. However when I run DU from the back-up drive (via USB) I get the messages I had before. (See attached.) I don't seem to get a repair process happening. Instead DU instantly goes to, "Alert, Couldn't create temporary directory." Although, DU on TTP's eDrive continues to show a clean bill of health. Is there a diagnostic tool in Checkmate?

Thanks!
Attachments:
Last Edit: 11 Jul 2015 02:49 by micromattech3. Reason: Added code tags for Terminal output.
The administrator has disabled public write access.

Disc Utility is produces inconsistent results with TTP 8 (eDrive) & Checkmate 11 Jul 2015 02:48 #6551

Checkmate run the diagnosis of the partition map automatically once a week. There is no way that you can force it to run at a particular time. The Logs show when it was last run.

If you install the system software onto an empty volume, you should be able to boot from that volume and then the system will prompt you to import users and applications from another bootable volume or from a Time Machine backup.

If you use the mouse pointer to grab the Terminal output in your posting, you can move it horizontally to see more text.

I do not think we will be able to make progress with this problem until you get a reply from This email address is being protected from spambots. You need JavaScript enabled to view it. . We will probably have to ask one of the programmers about the "Alert, Couldn't create temporary directory." error message.

Once you get system software from the CD installed, and have your users and applications and data files imported, if you install Yosemite, it should create the Recovery HD volume. If you have a small USB memory stick, you can make a backup of the Recovery HD volume using TechTool Protogo.
MicroMat Inc
Makers of TechTool
Last Edit: 11 Jul 2015 03:02 by micromattech3.
The administrator has disabled public write access.
The following user(s) said Thank You: rprochot

Disc Utility is produces inconsistent results with TTP 8 (eDrive) & Checkmate 18 Jul 2015 22:13 #6562

Thanks for your help.

I finally resorted to erasing the hard drive and restoring my system back to the original installed software as of the day I brought the computer (Sep. 2008), and bringing it up to date from there (July 15, 2015). Other than a minor irritation of the menu showing the user name at the top of the screen, everything else appears to be be functioning well, and the hard drive (and other attached drives) appears to have been restored to good condition no matter which version version of Disc Utility I am running. (Currently OSX v10.10.4) I have also been able to restore the OS X recovery partition. Once I work up the nerve, I will reinstall Check-mate, although TechTool Pro v8.0.2 appears to be running with no problems (TOUCH WOOD!).

Once again thank for your assistance!

Ron Prochot
The administrator has disabled public write access.

Disc Utility is produces inconsistent results with TTP 8 (eDrive) & Checkmate 18 Jul 2015 23:07 #6563

You are welcome. Thanks for the update, and it is good to see so much progress.

As a rule, you should use only the version of Disk Utility that is part of OS X 10.10.4 on volumes to which it has written. Earlier versions of Disk Utility would not take into account any changes that Apple introduced with OS X 10.10.4.
MicroMat Inc
Makers of TechTool
The administrator has disabled public write access.
Time to create page: 0.314 seconds