Welcome, Guest
Username: Password: Remember me

Search Micromat Forum

Keyword

TOPIC: All 4 of my internal drives passed Checkmate's first pass, but I received an error message

All 4 of my internal drives passed Checkmate's first pass, but I received an error message 18 Feb 2013 16:05 #3751

All 4 of my internal drives passed Checkmate's first pass, but I received the following error messages

A disk related I/O error was found on disk "disk4s0".
A disk related I/O error was found on disk "disk5s0".

I had previously turned my start up sound off with a Terminal command. As a first time user of Checkmate, didn't know that Checkmate informs of errors by a series of beeps. Is there a way to access this 'beep #' info or is this info the same as reported in the log?

I don't know these 'disks'... disk4s0 or disk5s0. I thought they might be disk images or burn folders. I ran Disk Utility and it reported all 4 of my drives within normal operating spec.
The administrator has disabled public write access.

Re: All 4 of my internal drives passed Checkmate's first pass, but I received an error message 18 Feb 2013 16:46 #3752

I will have to ask about whether Checkmate beeps when errors are detected. The results of all of the tests are in the Logs.

A reference to disk4s0 is to disk number 4, partition, volume, or slice (as it was known for the UFS format disks used in the original Unix systems) number 0. You can see the current disks and their volumes by opening the Terminal application, located in /Applications/Utilities, and typing:

df

Press the Return key.

You can also see this information in Disk Utility if you select volumes and use the Info button.

The i/o errors are input/output errors, something that went wrong during an attempt to read from or write to a volume. Disk Utility is not able to detect them. If you open the Console application, located in /Applications/Utilities, and search in the All Messages log (near the top of the logs list) for

i/o

and

input/output

you might find the original i/o error message. By going back in time in the All Messages log, you might be able to determine what the volumes were.

As long as the 1/o error messages are not referring to hard drive volumes, SSD voolumes, or USB memory sticks, I would not be alarmed. It is not unusual for CDs and DVDs to have misreads. In fact, it is unfortunate that Mac OS X no longer reports the sector numbers for sectors that failed to be read on a DVD. It provided credibility when reporting defective DVDs to Amazon.
MicroMat Inc
Makers of TechTool
Last Edit: 18 Feb 2013 16:53 by micromattech3.
The administrator has disabled public write access.

Re: All 4 of my internal drives passed Checkmate's first pass, but I received an error message 18 Feb 2013 18:50 #3753

I'm checking my attached drives and will input the info you've provided to help identify the drives. The Icon in my menu bar has changed from Red back to Black. Is this any indication that the I/O issues were repaired?
The administrator has disabled public write access.

Re: All 4 of my internal drives passed Checkmate's first pass, but I received an error message 18 Feb 2013 18:59 #3754

I will ask about the color change in the menu bar. I have had only one error myself, so I am not sure about either the beeps or the color change.

i/o errors are unique events that take place in time. They themselves are not a piece of data that can be fixed. When they occur on a hard drive volume, an SSD volume, or a USB memory stick, there is usually either a problem with the disk directory or the hardware itself, including the media.

Here is what one type of report of an i/o error looks like, from the thread Surface Scan:

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

This error turned out to be caused by an unremapped bad block in the disk directory.
MicroMat Inc
Makers of TechTool
The administrator has disabled public write access.

Re: All 4 of my internal drives passed Checkmate's first pass, but I received an error message 18 Feb 2013 23:32 #3760

Here is an example of the output of the df (display filesystems) command. The active startup volume is a volume on disk0 (it is disk0s2), and is mounted on /. The name of the active startup volume does not appear.

Macintosh:~ MMT3$ df
Filesystem    512-blocks      Used  Available Capacity  Mounted on
/dev/disk0s2  1951845952 300276120 1651057832    16%    /
devfs                378       378          0   100%    /dev
map -hosts             0         0          0   100%    /net
map auto_home          0         0          0   100%    /home
/dev/disk1s3     7550360     51592    7498768     1%    /Volumes/Recovery
/dev/disk1s2   479912840 280029224  199883616    59%    /Volumes/G-Drive_Q_232
/dev/disk2s2   976101344 276293960  699807384    29%    /Volumes/H_G_Wells
/dev/disk3      13332668  13332668          0   100%    /Volumes/Virgin Cendrillon DVD1

The text in the window above can be scrolled horizontally.

Note that the DVD, Cendrillon, is a single-partition disk (disk3) that is 100% full.
MicroMat Inc
Makers of TechTool
Last Edit: 18 Feb 2013 23:38 by micromattech3.
The administrator has disabled public write access.

Re: All 4 of my internal drives passed Checkmate's first pass, but I received an error message 19 Feb 2013 14:31 #3761

Prior to retiring last night, I ran checkmate and it again showed the same two I/O errors. When I started up the computer today, I worked a while before launching Checkmate. It now shows the system passed the most recent scan. Files evaluation is still pending.
The administrator has disabled public write access.

Re: All 4 of my internal drives passed Checkmate's first pass, but I received an error message 19 Feb 2013 14:52 #3762

Thanks for the update.

Use the Console application, located in /Applications/Utilities, to search the All Messages log (or the System and Console logs in older versions of Mac OS X) for:

i/o

and

input/output

Use the df command, as described above, to identify the relevant disks.

Checkmate is simply checking the All Messages log (or the System and Console logs) to see if any i/o errors have been logged. The next time it runs the i/o test, it is looking for new i/o errors recorded in those logs.
MicroMat Inc
Makers of TechTool
The administrator has disabled public write access.

Re: All 4 of my internal drives passed Checkmate's first pass, but I received an error message 19 Feb 2013 15:03 #3763

Geez.. I forgot to add that I burned all unnecessary installer and program files off my drives last night, in anticipation of a drive failure due to the Checkmate report. One of these installers might have been corrupt.
The administrator has disabled public write access.

Re: All 4 of my internal drives passed Checkmate's first pass, but I received an error message 19 Feb 2013 15:42 #3764

I would not be alarmed about this i/o error until you determine what disk4 and disk5 are.

The disk numbers are assigned at boot time for drives available then, starting with zero for the disk containing the active boot volume; disk4 and disk5 are unlikely to be hard drives unless you have a lot of drives. You have reported that your four internal drives passed the i/o test. They are probably disk0, disk1, disk2, and disk3. We need to find out what disk4 and disk5 are.
MicroMat Inc
Makers of TechTool
Last Edit: 19 Feb 2013 15:44 by micromattech3.
The administrator has disabled public write access.

Re: All 4 of my internal drives passed Checkmate's first pass, but I received an error message 19 Feb 2013 16:52 #3767

Here is the answer I got about the Checkmate, sounds, and the menubar icon:

At this time, Checkmate doesn't make an audible sound when errors are discovered. The Checkmate icon in the menu bar will flash yellow or red, if it finds a warning or failure, respectively. It will continue to flash until the application is opened or brought to the front and the error viewed by the user, regardless if other tests have passed since the warning/failure was discovered.
MicroMat Inc
Makers of TechTool
The administrator has disabled public write access.

Re: All 4 of my internal drives passed Checkmate's first pass, but I received an error message 19 Feb 2013 17:03 #3768

I ran the df command in Terminal and got this result:
Filesystem    512-blocks       Used  Available Capacity  Mounted on
/dev/disk1s2  1952853344 1066969608  885371736    55%    /
devfs                227        227          0   100%    /dev
/dev/disk3s3  1953262944 1213337752  739925192    63%    /Volumes/1TbTunes
/dev/disk2s2  1952853344  855440384 1097412960    44%    /Volumes/1TbTunes3
/dev/disk0s2  3906357344 2184010664 1722346680    56%    /Volumes/Luckydog
map -hosts             0          0          0   100%    /net
map auto_home      0          0          0   100%    /home
Once the File test (file structures) changes from Pending to Passed, I'll start adding external drives in an attempt to get the original error messages. I'm thinking that one or more of the disk images I burned off the computer last night caused the I/O error readings. One was the Mountain Lion Installer.
Last Edit: 19 Feb 2013 17:47 by micromattech3. Reason: Added code tags for Terminal output
The administrator has disabled public write access.

Re: All 4 of my internal drives passed Checkmate's first pass, but I received an error message 19 Feb 2013 17:46 #3769

Thanks for posting the output of the df command. I have added code tags to it, to improve the display of the data.

It is odd that your active startup volume (disk1s2)is not on disk0, but that is not cause for alarm. I think you have a good plan for further investigation.
MicroMat Inc
Makers of TechTool
Last Edit: 19 Feb 2013 17:47 by micromattech3.
The administrator has disabled public write access.

Re: All 4 of my internal drives passed Checkmate's first pass, but I received an error message 21 Feb 2013 00:50 #3780

Try searching the kernel.log file (also visible in the Console application) for:

i/o

and

input/output
MicroMat Inc
Makers of TechTool
The administrator has disabled public write access.
Time to create page: 0.303 seconds