Verify Disk Log shows problems

OK Rookie here (again!) -
Stupid question(s) No.4:
I've partitioned my new external and successfully made a bootable clone of the complete HD (which I've tested and it seems to work fine).
I've deleted the "manually added" Folder within my Users folder and added all files that were not of an older date (only two) to my actual Admin Account Folder.
Then I ran "Repair Disk Permissions" and "Verify Disk" from Apple DU and got the following:
(Red comments in bold)
+Verifying volume “Macintosh HD”+
Checking HFS Plus volume.
Checking Extents Overflow file.
Checking Catalog file.
*Illegal name*
*Illegal name*
Checking multi-linked files.
Checking Catalog hierarchy.
Checking Extended Attributes file.
Checking volume bitmap.
Checking volume information.
*Volume Header needs minor repair*
*The volume Macintosh HD needs to be repaired.*
*Error: The underlying task reported failure on exit*
1 HFS volume checked
*Volume needs repair*
There was also a strange box in the top RH corner of the window that said "LOG" underneath, it had some yellow writing on a black BG that seemed to say "WARNING" on the first line and a number on the second which I could not read.
I clicked it and it seems to only be a copy of the dialogue above but I've added it here in case it's important:
The privileges have been verified or repaired on the selected volume
Verifying volume “Macintosh HD”
Checking HFS Plus volume.
Checking Extents Overflow file.
Checking Catalog file.
Illegal name
Illegal name
Checking multi-linked files.
Checking Catalog hierarchy.
Checking Extended Attributes file.
Checking volume bitmap.
Checking volume information.
Volume Header needs minor repair
The volume Macintosh HD needs to be repaired.
Error: The underlying task reported failure on exit
Disk Utility stopped verifying “Macintosh HD” because the following error was encountered:
The underlying task reported failure on exit
1 HFS volume checked
Volume needs repair
==============================
How should I proceed?
I still have the original untouched clone of my HD on the external, are any of the comments attributable to the moving and deleting of files and folders that I have done since or is it all more worrying and a problem with my Mac?
I'll do nothing before I hear from someone - any help greatly appreciated.
Regards - Deano
PS: I've opened all files and games from my reconfigured HD since moving everything around with no problem at all

Hi Deano-
Glad to hear things worked out.
The report looks good, and S.M.A.R.T. status reporting as verified is always good. Loss of S.M.A.R.T. status is often times a sign of impending doom, except in the case of external firewire drives. These aren't S.M.A.R.T. supported. S.M.A.R.T. reporting as verified, though, is not a panacea, just one of several tools to gauge a drives health. More info on S.M.A.R.T.
As for the update of the clone... My thoughts are, that since both are currently working, for the time being, leave them both as is. When it comes time to backup- daily, every two days, weekly, what ever your workload demands, by then you will know, +for sure+ that the main drive is as healthy as now appears. So, when it's time to backup, do it then. Either Erase and Copy, or, Smart update will be fine.
Oh, and the CS2 files are for Vietnamese language support in CS2. So, unless you need Vietnamese, the absence of the files will cause no harm.
You're getting through your learning curve just fine, and gaining valuable experience. Always remember to verify/repair a hard drive from a seperate volume or install disk. Permissions don't require such. Now that you have the room and the tools, keep that valuable data backed up!
Post anytime you need help, or reinforcement. That's what the forums are for. I enjoy helping, as I can, and appreciate the show of appreciation with the stars! You're welcome!

Similar Messages

  • Server log showing problems with Mail Server

    Ok, so I followed the instructions in that PDF about how to make virtual mail users in 10.5.1 since they are broken. So I did it in the WGM and the Postfix stuff as the document said. Now I get all these errors in the server log and I have no idea how to fix the problem or if what I did was even done right. Here is the error log below:
    Jan 30 23:33:26 xpmedia1 postfix/master[49308]: warning: /usr/libexec/postfix/cleanup: bad command startup -- throttling
    Jan 30 23:34:03 xpmedia1 postfix/smtpd[53603]: warning: database /etc/postfix/virtual.db is older than source file /etc/postfix/virtual
    Jan 30 23:34:03 xpmedia1 postfix/smtpd[53603]: fatal: open database /var/mailman/data/virtual-mailman.db: No such file or directory
    Jan 30 23:34:04 xpmedia1 postfix/master[49308]: warning: process /usr/libexec/postfix/smtpd pid 53603 exit status 1
    Jan 30 23:34:04 xpmedia1 postfix/master[49308]: warning: /usr/libexec/postfix/smtpd: bad command startup -- throttling
    Jan 30 23:34:26 xpmedia1 postfix/cleanup[53611]: warning: database /etc/postfix/virtual.db is older than source file /etc/postfix/virtual
    Jan 30 23:34:26 xpmedia1 postfix/cleanup[53611]: fatal: open database /var/mailman/data/virtual-mailman.db: No such file or directory
    Jan 30 23:34:27 xpmedia1 postfix/master[49308]: warning: process /usr/libexec/postfix/cleanup pid 53611 exit status 1
    Jan 30 23:34:27 xpmedia1 postfix/master[49308]: warning: /usr/libexec/postfix/cleanup: bad command startup -- throttling
    Jan 30 23:35:04 xpmedia1 postfix/smtpd[53615]: warning: database /etc/postfix/virtual.db is older than source file /etc/postfix/virtual
    Jan 30 23:35:04 xpmedia1 postfix/smtpd[53615]: fatal: open database /var/mailman/data/virtual-mailman.db: No such file or directory
    Jan 30 23:35:05 xpmedia1 postfix/master[49308]: warning: process /usr/libexec/postfix/smtpd pid 53615 exit status 1
    Jan 30 23:35:05 xpmedia1 postfix/master[49308]: warning: /usr/libexec/postfix/smtpd: bad command startup -- throttling
    Jan 30 23:35:16 xpmedia1 sudo[53616]: root : TTY=unknown ; PWD=/ ; USER=_cyrus ; COMMAND=/usr/bin/cyrus/bin/cyrus-quota -r
    Jan 30 23:35:27 xpmedia1 postfix/cleanup[53625]: warning: database /etc/postfix/virtual.db is older than source file /etc/postfix/virtual
    Jan 30 23:35:27 xpmedia1 postfix/cleanup[53625]: fatal: open database /var/mailman/data/virtual-mailman.db: No such file or directory
    Jan 30 23:35:28 xpmedia1 postfix/master[49308]: warning: process /usr/libexec/postfix/cleanup pid 53625 exit status 1
    Jan 30 23:35:28 xpmedia1 postfix/master[49308]: warning: /usr/libexec/postfix/cleanup: bad command startup -- throttling
    Jan 30 23:36:05 xpmedia1 postfix/smtpd[53633]: warning: database /etc/postfix/virtual.db is older than source file /etc/postfix/virtual
    Jan 30 23:36:05 xpmedia1 postfix/smtpd[53633]: fatal: open database /var/mailman/data/virtual-mailman.db: No such file or directory
    Jan 30 23:36:06 xpmedia1 postfix/master[49308]: warning: process /usr/libexec/postfix/smtpd pid 53633 exit status 1
    Jan 30 23:36:06 xpmedia1 postfix/master[49308]: warning: /usr/libexec/postfix/smtpd: bad command startup -- throttling
    Jan 30 23:36:28 xpmedia1 postfix/cleanup[53646]: warning: database /etc/postfix/virtual.db is older than source file /etc/postfix/virtual
    Jan 30 23:36:28 xpmedia1 postfix/cleanup[53646]: fatal: open database /var/mailman/data/virtual-mailman.db: No such file or directory
    Jan 30 23:36:29 xpmedia1 postfix/master[49308]: warning: process /usr/libexec/postfix/cleanup pid 53646 exit status 1
    Jan 30 23:36:29 xpmedia1 postfix/master[49308]: warning: /usr/libexec/postfix/cleanup: bad command startup -- throttling
    Jan 30 23:37:06 xpmedia1 postfix/smtpd[53650]: warning: database /etc/postfix/virtual.db is older than source file /etc/postfix/virtual
    Jan 30 23:37:06 xpmedia1 postfix/smtpd[53650]: fatal: open database /var/mailman/data/virtual-mailman.db: No such file or directory
    Jan 30 23:37:07 xpmedia1 postfix/master[49308]: warning: process /usr/libexec/postfix/smtpd pid 53650 exit status 1
    Jan 30 23:37:07 xpmedia1 postfix/master[49308]: warning: /usr/libexec/postfix/smtpd: bad command startup -- throttling
    Jan 30 23:37:29 xpmedia1 postfix/cleanup[53662]: warning: database /etc/postfix/virtual.db is older than source file /etc/postfix/virtual
    Jan 30 23:37:29 xpmedia1 postfix/cleanup[53662]: fatal: open database /var/mailman/data/virtual-mailman.db: No such file or directory
    Jan 30 23:37:30 xpmedia1 postfix/master[49308]: warning: process /usr/libexec/postfix/cleanup pid 53662 exit status 1
    Jan 30 23:37:30 xpmedia1 postfix/master[49308]: warning: /usr/libexec/postfix/cleanup: bad command startup -- throttling
    Jan 30 23:38:07 xpmedia1 postfix/smtpd[53666]: warning: database /etc/postfix/virtual.db is older than source file /etc/postfix/virtual
    Jan 30 23:38:07 xpmedia1 postfix/smtpd[53666]: fatal: open database /var/mailman/data/virtual-mailman.db: No such file or directory
    Jan 30 23:38:08 xpmedia1 postfix/master[49308]: warning: process /usr/libexec/postfix/smtpd pid 53666 exit status 1
    Jan 30 23:38:08 xpmedia1 postfix/master[49308]: warning: /usr/libexec/postfix/smtpd: bad command startup -- throttling
    Jan 30 23:38:30 xpmedia1 postfix/cleanup[53678]: warning: database /etc/postfix/virtual.db is older than source file /etc/postfix/virtual
    Jan 30 23:38:30 xpmedia1 postfix/cleanup[53678]: fatal: open database /var/mailman/data/virtual-mailman.db: No such file or directory
    Jan 30 23:38:31 xpmedia1 postfix/master[49308]: warning: process /usr/libexec/postfix/cleanup pid 53678 exit status 1
    Jan 30 23:38:31 xpmedia1 postfix/master[49308]: warning: /usr/libexec/postfix/cleanup: bad command startup -- throttling
    Jan 30 23:39:08 xpmedia1 postfix/smtpd[53682]: warning: database /etc/postfix/virtual.db is older than source file /etc/postfix/virtual
    Jan 30 23:39:08 xpmedia1 postfix/smtpd[53682]: fatal: open database /var/mailman/data/virtual-mailman.db: No such file or directory
    Jan 30 23:39:09 xpmedia1 postfix/master[49308]: warning: process /usr/libexec/postfix/smtpd pid 53682 exit status 1
    Jan 30 23:39:09 xpmedia1 postfix/master[49308]: warning: /usr/libexec/postfix/smtpd: bad command startup -- throttling
    Jan 30 23:39:31 xpmedia1 imap[53683]: TLS server engine: cannot load CA data
    Jan 30 23:39:31 xpmedia1 imap[53683]: TLS server engine: No CA file specified. Client side certs may not work
    Jan 30 23:39:31 xpmedia1 imap[53683]: STARTTLS negotiation failed: host-12-152-82-88.orbitelcom.com [12.152.82.88]
    Jan 30 23:39:31 xpmedia1 postfix/cleanup[53695]: warning: database /etc/postfix/virtual.db is older than source file /etc/postfix/virtual
    Jan 30 23:39:31 xpmedia1 postfix/cleanup[53695]: fatal: open database /var/mailman/data/virtual-mailman.db: No such file or directory
    Jan 30 23:39:32 xpmedia1 postfix/master[49308]: warning: process /usr/libexec/postfix/cleanup pid 53695 exit status 1
    Jan 30 23:39:32 xpmedia1 postfix/master[49308]: warning: /usr/libexec/postfix/cleanup: bad command startup -- throttling
    Jan 30 23:39:46 xpmedia1 imap[53683]: starttls: TLSv1 with cipher AES128-SHA (128/128 bits new) no authentication
    Jan 30 23:39:46 xpmedia1 imap[53683]: login: host-12-152-82-88.orbitelcom.com [12.152.82.88] postmaster CRAM-MD5+TLS User logged in
    Jan 30 23:40:09 xpmedia1 postfix/smtpd[53699]: warning: database /etc/postfix/virtual.db is older than source file /etc/postfix/virtual
    Jan 30 23:40:09 xpmedia1 postfix/smtpd[53699]: fatal: open database /var/mailman/data/virtual-mailman.db: No such file or directory
    Jan 30 23:40:10 xpmedia1 postfix/master[49308]: warning: process /usr/libexec/postfix/smtpd pid 53699 exit status 1
    Jan 30 23:40:10 xpmedia1 postfix/master[49308]: warning: /usr/libexec/postfix/smtpd: bad command startup -- throttling
    Jan 30 23:40:32 xpmedia1 postfix/cleanup[53700]: warning: database /etc/postfix/virtual.db is older than source file /etc/postfix/virtual
    Jan 30 23:40:32 xpmedia1 postfix/cleanup[53700]: fatal: open database /var/mailman/data/virtual-mailman.db: No such file or directory
    Jan 30 23:40:33 xpmedia1 postfix/master[49308]: warning: process /usr/libexec/postfix/cleanup pid 53700 exit status 1
    Jan 30 23:40:33 xpmedia1 postfix/master[49308]: warning: /usr/libexec/postfix/cleanup: bad command startup -- throttling
    Jan 30 23:41:10 xpmedia1 postfix/smtpd[53719]: warning: database /etc/postfix/virtual.db is older than source file /etc/postfix/virtual
    Jan 30 23:41:10 xpmedia1 postfix/smtpd[53719]: fatal: open database /var/mailman/data/virtual-mailman.db: No such file or directory
    Jan 30 23:41:11 xpmedia1 postfix/master[49308]: warning: process /usr/libexec/postfix/smtpd pid 53719 exit status 1
    Jan 30 23:41:11 xpmedia1 postfix/master[49308]: warning: /usr/libexec/postfix/smtpd: bad command startup -- throttling
    Jan 30 23:41:33 xpmedia1 postfix/cleanup[53720]: warning: database /etc/postfix/virtual.db is older than source file /etc/postfix/virtual
    Jan 30 23:41:33 xpmedia1 postfix/cleanup[53720]: fatal: open database /var/mailman/data/virtual-mailman.db: No such file or directory
    Jan 30 23:41:34 xpmedia1 postfix/master[49308]: warning: process /usr/libexec/postfix/cleanup pid 53720 exit status 1
    Jan 30 23:41:34 xpmedia1 postfix/master[49308]: warning: /usr/libexec/postfix/cleanup: bad command startup -- throttling
    Jan 30 23:42:11 xpmedia1 postfix/smtpd[53735]: warning: database /etc/postfix/virtual.db is older than source file /etc/postfix/virtual
    Jan 30 23:42:11 xpmedia1 postfix/smtpd[53735]: fatal: open database /var/mailman/data/virtual-mailman.db: No such file or directory
    Jan 30 23:42:12 xpmedia1 postfix/master[49308]: warning: process /usr/libexec/postfix/smtpd pid 53735 exit status 1
    Jan 30 23:42:12 xpmedia1 postfix/master[49308]: warning: /usr/libexec/postfix/smtpd: bad command startup -- throttling
    Jan 30 23:42:34 xpmedia1 postfix/cleanup[53736]: warning: database /etc/postfix/virtual.db is older than source file /etc/postfix/virtual
    Jan 30 23:42:34 xpmedia1 postfix/cleanup[53736]: fatal: open database /var/mailman/data/virtual-mailman.db: No such file or directory
    Jan 30 23:42:35 xpmedia1 postfix/master[49308]: warning: process /usr/libexec/postfix/cleanup pid 53736 exit status 1
    Jan 30 23:42:35 xpmedia1 postfix/master[49308]: warning: /usr/libexec/postfix/cleanup: bad command startup -- throttling
    Jan 30 23:43:12 xpmedia1 postfix/smtpd[53752]: warning: database /etc/postfix/virtual.db is older than source file /etc/postfix/virtual
    Jan 30 23:43:12 xpmedia1 postfix/smtpd[53752]: fatal: open database /var/mailman/data/virtual-mailman.db: No such file or directory
    Jan 30 23:43:13 xpmedia1 postfix/master[49308]: warning: process /usr/libexec/postfix/smtpd pid 53752 exit status 1
    Jan 30 23:43:13 xpmedia1 postfix/master[49308]: warning: /usr/libexec/postfix/smtpd: bad command startup -- throttling
    Jan 30 23:43:35 xpmedia1 postfix/cleanup[53753]: warning: database /etc/postfix/virtual.db is older than source file /etc/postfix/virtual
    Jan 30 23:43:35 xpmedia1 postfix/cleanup[53753]: fatal: open database /var/mailman/data/virtual-mailman.db: No such file or directory
    Jan 30 23:43:36 xpmedia1 postfix/master[49308]: warning: process /usr/libexec/postfix/cleanup pid 53753 exit status 1
    Jan 30 23:43:36 xpmedia1 postfix/master[49308]: warning: /usr/libexec/postfix/cleanup: bad command startup -- throttling

    I did what you said and I don't see all those weird messages anymore, but we switched over our MX records today to our mail server in hopes that it would all work and now no one can get their mail. I can log into the mail server no problem via IMAP, but to send messages is not working. And those using POP don't seem to work at all. Even to send messages the Server is rejecting saying that my messages isn't addresed right. Which it is. I can't even send something to myself. I'm trying not to be frustrated with this thing. I'm just not sure what to do since we have a whole bunch of people needing mail and it doesn't seem to be working and I'm not a mail server expert. Any help would be appreciated.
    Here is what I with postconf -n:
    command_directory = /usr/sbin
    config_directory = /etc/postfix
    content_filter = smtp-amavis:[127.0.0.1]:10024
    daemon_directory = /usr/libexec/postfix
    debugpeerlevel = 2
    enableserveroptions = yes
    html_directory = no
    inet_interfaces = all
    localrecipientmaps =
    luser_relay = postmaster
    mail_owner = _postfix
    mailboxsizelimit = 0
    mailbox_transport = cyrus
    mailq_path = /usr/bin/mailq
    manpage_directory = /usr/share/man
    mapsrbldomains =
    messagesizelimit = 10485760
    mydestination = $myhostname,localhost.$mydomain,localhost
    mydomain = xpmedia.com
    mydomain_fallback = localhost
    myhostname = mail.xpmedia.com
    mynetworks = 98.173.129.235,98.173.129.238
    newaliases_path = /usr/bin/newaliases
    queue_directory = /private/var/spool/postfix
    readme_directory = /usr/share/doc/postfix
    relayhost =
    sample_directory = /usr/share/doc/postfix/examples
    sendmail_path = /usr/sbin/sendmail
    setgid_group = _postdrop
    smtpdclientrestrictions = permit_mynetworks zen.spamhaus.org permit
    smtpdpw_server_securityoptions = login,cram-md5
    smtpdrecipientrestrictions = permitsasl_authenticated,permit_mynetworks,reject_unauthdestination,permit
    smtpdsasl_authenable = yes
    smtpduse_pwserver = yes
    unknownlocal_recipient_rejectcode = 550
    virtualaliasdomains = hash:/etc/postfix/virtual_domains
    virtualaliasmaps = hash:/etc/postfix/virtual
    virtualmailboxdomains = hash:/etc/postfix/virtualdomainsxp
    virtual_transport = lmtp:unix:/var/imap/socket/lmtp
    Here is what I got in the system log:
    11:29:53 xpmedia1 loginwindow[57389]: received ATSServer died message. (old server pid = 58904, new pid = 58934, session ID = 256)
    Jan 31 11:29:53 xpmedia1 /System/Library/CoreServices/SystemUIServer.app/Contents/MacOS/SystemUIServer[5 7421]: received ATSServer died message. (old server pid = 58904, new pid = 58934, session ID = 256)
    Jan 31 11:29:53 xpmedia1 /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder[57422]: received ATSServer died message. (old server pid = 58904, new pid = 58934, session ID = 256)
    Jan 31 11:29:54 xpmedia1 com.apple.launchd[1] (0x10f510.login[58959]): Could not setup Mach task special port 9: (os/kern) no access
    Jan 31 11:29:54 xpmedia1 login[58959]: USER_PROCESS: 58959 ttys000
    Jan 31 11:30:03 xpmedia1 login[58959]: DEAD_PROCESS: 58959 ttys000
    Jan 31 11:30:22 xpmedia1 master[58971]: process started
    Jan 31 11:30:22 xpmedia1 org.clamav.clamd[58975]: clamd daemon 0.91.2 (OS: darwin9.0, ARCH: i386, CPU: i386)
    Jan 31 11:30:22 xpmedia1 org.clamav.clamd[58975]: Log file size limited to 1048576 bytes.
    Jan 31 11:30:22 xpmedia1 org.clamav.clamd[58975]: Reading databases from /var/clamav
    Jan 31 11:30:22 xpmedia1 org.clamav.clamd[58975]: Not loading PUA signatures.
    Jan 31 11:30:23 xpmedia1 postfix/postfix-script[58983]: fatal: the Postfix mail system is not running
    Jan 31 11:30:23 xpmedia1 ctl_cyrusdb[58973]: verifying cyrus databases
    Jan 31 11:30:23 xpmedia1 ctl_cyrusdb[58973]: skiplist: recovered /Volumes/Kingdom/Mail_Database/imap/mailboxes.db (29 records, 5640 bytes) in 0 seconds
    Jan 31 11:30:23 xpmedia1 ctl_cyrusdb[58973]: skiplist: recovered /Volumes/Kingdom/Mail_Database/imap/annotations.db (0 records, 144 bytes) in 0 seconds
    Jan 31 11:30:24 xpmedia1 org.clamav.clamd[58975]: Loaded 198723 signatures.
    Jan 31 11:30:25 xpmedia1 org.clamav.clamd[58975]: Unix socket file /var/amavis/clamd
    Jan 31 11:30:25 xpmedia1 org.clamav.clamd[58975]: Setting connection queue length to 15
    Jan 31 11:30:25 xpmedia1 org.clamav.clamd[58975]: Archive: Archived file size limit set to 10485760 bytes.
    Jan 31 11:30:25 xpmedia1 org.clamav.clamd[58975]: Archive: Recursion level limit set to 8.
    Jan 31 11:30:25 xpmedia1 org.clamav.clamd[58975]: Archive: Files limit set to 1000.
    Jan 31 11:30:25 xpmedia1 org.clamav.clamd[58975]: Archive: Compression ratio limit set to 250.
    Jan 31 11:30:25 xpmedia1 org.clamav.clamd[58975]: Archive support enabled.
    Jan 31 11:30:25 xpmedia1 org.clamav.clamd[58975]: Algorithmic detection enabled.
    Jan 31 11:30:25 xpmedia1 org.clamav.clamd[58975]: Portable Executable support enabled.
    Jan 31 11:30:25 xpmedia1 org.clamav.clamd[58975]: ELF support enabled.
    Jan 31 11:30:25 xpmedia1 org.clamav.clamd[58975]: Mail files support enabled.
    Jan 31 11:30:25 xpmedia1 org.clamav.clamd[58975]: Mail: Recursion level limit set to 64.
    Jan 31 11:30:25 xpmedia1 org.clamav.clamd[58975]: OLE2 support enabled.
    Jan 31 11:30:25 xpmedia1 org.clamav.clamd[58975]: PDF support disabled.
    Jan 31 11:30:25 xpmedia1 org.clamav.clamd[58975]: HTML support enabled.
    Jan 31 11:30:25 xpmedia1 org.clamav.clamd[58975]: Self checking every 1800 seconds.
    Jan 31 11:30:25 xpmedia1 org.clamav.clamd[58975]: Set stacksize to 1048576
    Jan 31 11:30:25 xpmedia1 com.apple.launchd[1] (edu.cmu.andrew.cyrus.master[58971]): Stray process with PGID equal to this dead job: PID 58973 PPID 1 ctl_cyrusdb
    Jan 31 11:30:25 xpmedia1 com.apple.launchd[1] (edu.cmu.andrew.cyrus.master[58971]): Exited abnormally: User defined signal 1
    Jan 31 11:30:25 xpmedia1 com.apple.launchd[1] (edu.cmu.andrew.cyrus.master): Throttling respawn: Will start in 8 seconds
    Jan 31 11:30:33 xpmedia1 master[59034]: process started
    Jan 31 11:30:34 xpmedia1 ctl_cyrusdb[59035]: verifying cyrus databases
    Jan 31 11:30:34 xpmedia1 ctl_cyrusdb[59035]: skiplist: recovered /Volumes/Kingdom/Mail_Database/imap/mailboxes.db (29 records, 5640 bytes) in 0 seconds
    Jan 31 11:30:34 xpmedia1 ctl_cyrusdb[59035]: skiplist: recovered /Volumes/Kingdom/Mail_Database/imap/annotations.db (0 records, 144 bytes) in 0 seconds
    Jan 31 11:30:35 xpmedia1 com.apple.launchd[1] (edu.cmu.andrew.cyrus.master[59034]): Stray process with PGID equal to this dead job: PID 59035 PPID 1 ctl_cyrusdb
    Jan 31 11:30:35 xpmedia1 com.apple.launchd[1] (edu.cmu.andrew.cyrus.master[59034]): Exited abnormally: User defined signal 1
    Jan 31 11:30:35 xpmedia1 com.apple.launchd[1] (edu.cmu.andrew.cyrus.master): Throttling respawn: Will start in 9 seconds
    Jan 31 11:30:43 xpmedia1 postfix/smtpd[59036]: warning: unknown smtpd restriction: "zen.spamhaus.org"
    Jan 31 11:30:44 xpmedia1 master[59041]: process started
    Jan 31 11:30:45 xpmedia1 ctl_cyrusdb[59042]: verifying cyrus databases
    Jan 31 11:30:45 xpmedia1 ctl_cyrusdb[59042]: skiplist: recovered /Volumes/Kingdom/Mail_Database/imap/mailboxes.db (29 records, 5640 bytes) in 0 seconds
    Jan 31 11:30:45 xpmedia1 ctl_cyrusdb[59042]: skiplist: recovered /Volumes/Kingdom/Mail_Database/imap/annotations.db (0 records, 144 bytes) in 0 seconds
    Jan 31 11:30:46 xpmedia1 postfix/smtpd[59036]: warning: unknown smtpd restriction: "zen.spamhaus.org"
    Jan 31 11:30:47 xpmedia1 ctl_cyrusdb[59042]: done verifying cyrus databases
    Jan 31 11:30:47 xpmedia1 master[59041]: Cyrus POP/IMAP Server v2.3.8 ready for work
    Jan 31 11:30:47 xpmedia1 ctl_cyrusdb[59045]: checkpointing cyrus databases
    Jan 31 11:30:47 xpmedia1 ctl_cyrusdb[59045]: done checkpointing cyrus databases
    Jan 31 11:31:09 xpmedia1 postfix/smtpd[59036]: warning: unknown smtpd restriction: "zen.spamhaus.org"
    Jan 31 11:31:13 xpmedia1 pop3[59050]: login: host-12-152-82-113.orbitelcom.com [12.152.82.113] jsowerby APOP User logged in
    Jan 31 11:31:13 xpmedia1 pop3[59051]: login: host-12-152-82-113.orbitelcom.com [12.152.82.113] rsowerby APOP User logged in
    Jan 31 11:31:14 xpmedia1 imap[59053]: login: [66.182.118.39] bcorbin CRAM-MD5 User logged in
    Jan 31 11:31:14 xpmedia1 imap[59052]: login: [66.182.118.39] postmaster CRAM-MD5 User logged in
    Jan 31 11:31:14 xpmedia1 imap[59054]: login: [66.182.118.39] bcorbin CRAM-MD5 User logged in
    Jan 31 11:31:14 xpmedia1 imap[59055]: login: [66.182.118.39] postmaster CRAM-MD5 User logged in
    Jan 31 11:31:15 xpmedia1 imap[59055]: skiplist: recovered /Volumes/Kingdom/Mail_Database/imap/user/p/postmaster.seen (0 records, 144 bytes) in 0 seconds
    Jan 31 11:31:15 xpmedia1 imap[59054]: skiplist: recovered /Volumes/Kingdom/Mail_Database/imap/user/b/bcorbin.seen (2 records, 572 bytes) in 0 seconds
    Jan 31 11:31:15 xpmedia1 imap[59053]: login: [66.182.118.39] postmaster CRAM-MD5 User logged in
    Jan 31 11:31:15 xpmedia1 imap[59056]: login: [66.182.118.39] bcorbin CRAM-MD5 User logged in
    Jan 31 11:31:16 xpmedia1 imap[59052]: login: [66.182.118.39] postmaster CRAM-MD5 User logged in
    Jan 31 11:31:17 xpmedia1 imap[59057]: login: [66.182.118.39] postmaster CRAM-MD5 User logged in
    Jan 31 11:31:17 xpmedia1 imap[59058]: login: [66.182.118.39] bcorbin CRAM-MD5 User logged in
    Jan 31 11:31:18 xpmedia1 imap[59059]: login: [66.182.118.39] bcorbin CRAM-MD5 User logged in
    Jan 31 11:31:25 xpmedia1 pop3[59050]: no secret in database
    Jan 31 11:31:25 xpmedia1 pop3[59050]: badlogin: 71-223-32-176.phnx.qwest.net [71.223.32.176] CRAM-MD5 user not found
    Jan 31 11:31:25 xpmedia1 postfix/smtpd[59036]: warning: unknown smtpd restriction: "zen.spamhaus.org"
    Jan 31 11:31:25 xpmedia1 pop3[59051]: login: [66.182.125.209] cbrundidge APOP User logged in
    Jan 31 11:31:30 xpmedia1 pop3[59051]: login: 71-223-32-176.phnx.qwest.net [71.223.32.176] kbarr APOP User logged in
    Jan 31 11:31:44 xpmedia1 postfix/smtpd[59036]: warning: unknown smtpd restriction: "zen.spamhaus.org"
    Jan 31 11:31:44 xpmedia1 postfix/smtpd[59063]: warning: unknown smtpd restriction: "zen.spamhaus.org"
    Jan 31 11:32:07 xpmedia1 imap[59069]: login: [66.182.118.39] postmaster CRAM-MD5 User logged in
    Jan 31 11:32:07 xpmedia1 imap[59068]: login: [66.182.118.39] bcorbin CRAM-MD5 User logged in
    Jan 31 11:32:25 xpmedia1 pop3[59050]: login: [66.182.125.209] cbrundidge APOP User logged in
    Jan 31 11:32:29 xpmedia1 postfix/smtpd[59063]: warning: unknown smtpd restriction: "zen.spamhaus.org"
    Jan 31 11:33:01 xpmedia1 postfix/smtpd[59036]: warning: unknown smtpd restriction: "zen.spamhaus.org"
    Jan 31 11:33:25: --- last message repeated 1 time ---
    Jan 31 11:33:25 xpmedia1 pop3[59050]: no secret in database
    Jan 31 11:33:25 xpmedia1 pop3[59050]: badlogin: 71-223-32-176.phnx.qwest.net [71.223.32.176] CRAM-MD5 user not found
    Jan 31 11:33:25 xpmedia1 postfix/smtpd[59086]: warning: unknown smtpd restriction: "zen.spamhaus.org"
    Jan 31 11:33:26 xpmedia1 pop3[59091]: login: [66.182.125.209] cbrundidge APOP User logged in
    Jan 31 11:33:30 xpmedia1 pop3[59091]: login: 71-223-32-176.phnx.qwest.net [71.223.32.176] kbarr APOP User logged in
    Jan 31 11:34:12 xpmedia1 postfix/smtpd[59063]: warning: unknown smtpd restriction: "zen.spamhaus.org"
    Jan 31 11:34:23: --- last message repeated 7 times ---
    Jan 31 11:34:23 xpmedia1 pop3[59050]: login: [66.182.118.39] jrossilli APOP User logged in
    Jan 31 11:34:25 xpmedia1 pop3[59091]: login: [66.182.125.209] cbrundidge APOP User logged in
    Jan 31 11:34:31 xpmedia1 postfix/smtpd[59086]: warning: unknown smtpd restriction: "zen.spamhaus.org"
    Jan 31 11:34:50 xpmedia1 sudo[59121]: root : TTY=unknown ; PWD=/ ; USER=_cyrus ; COMMAND=/usr/bin/cyrus/bin/cyrus-quota -r
    Jan 31 11:34:52 xpmedia1 sudo[59127]: root : TTY=unknown ; PWD=/ ; USER=_cyrus ; COMMAND=/usr/bin/cyrus/bin/cyrus-quota -r
    Jan 31 11:35:18 xpmedia1 pop3[59050]: login: host-12-152-82-113.orbitelcom.com [12.152.82.113] rsowerby APOP User logged in
    Jan 31 11:35:18 xpmedia1 pop3[59091]: login: host-12-152-82-113.orbitelcom.com [12.152.82.113] jsowerby APOP User logged in
    Jan 31 11:35:25 xpmedia1 pop3[59091]: no secret in database
    Jan 31 11:35:25 xpmedia1 pop3[59091]: badlogin: 71-223-32-176.phnx.qwest.net [71.223.32.176] CRAM-MD5 user not found
    Jan 31 11:35:25 xpmedia1 pop3[59050]: login: [66.182.125.209] cbrundidge APOP User logged in
    Jan 31 11:35:26 xpmedia1 postfix/smtpd[59063]: warning: unknown smtpd restriction: "zen.spamhaus.org"
    Jan 31 11:35:30 xpmedia1 pop3[59050]: login: 71-223-32-176.phnx.qwest.net [71.223.32.176] kbarr APOP User logged in
    Jan 31 11:35:35 xpmedia1 pop3[59091]: badlogin: 32-109-248-206-catv.choicecable.net [206.248.109.32] APOP (<[email protected]>) Error: -6

  • Repair disk permissions shows problem

    trying to get a printer installed I ran repair disk permissions and came up with a problem.
    Question, how do I resolve it?
    message is: System/Library/CoreS cannot be repaired.
    I need advise from someone a lot smarter than me.
    I have not noted any problems with any component or aspect of the os other than this one Epson printer which will not install.
    Not sure if re-install of SL would correct problem or cause changes to current setup.

    no, this is not the full message. it's still truncated. there is no such thing as "System/Library/CoreS". there is a directory "System/Library/CoreServices" which contains a lot of stuff. the message likely refers to something in that directory. but as I said, all such SUID messages are harmless and should be ignored.

  • Verify disk failure - how to repair?

    I verified disk permissions no problem on my hard drive. Then when I try to "verify" the hard disk, I get this error message (should I be concerned?):
    Verifying volume “Macintosh HD”
    Checking 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.
    Volume Header needs minor repair_
    The volume Macintosh HD needs to be repaired.
    Error: The underlying task reported failure on exit
    1 HFS volume checked
    Volume needs repair
    --If the volume needs repair, why won't it let me repair it? (The "repair" button is gray and won't work) Is there a way to repair from one of the disks that came with the computer?

    Hi Time is NOW , and a warm welcome to the forums!
    You cannot repair the Disk you are booted from.
    "Try Disk Utility
    1. Insert the Tiger Mac OS X Install disc that came with your computer, then restart the computer while holding the C key.
    2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu. (In Mac OS X 10.4 or later, you must select your language first.)
    Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.
    3. Click the First Aid tab.
    4. Select your Mac OS X volume.
    5. Click Repair. Disk Utility checks and repairs the disk."
    http://docs.info.apple.com/article.html?artnum=106214

  • Does this mean i have a Problem? Permissions won't verify/Disk won;t repair? Do I need to reformat my entire system?

    ##
    # User Database
    # Note that this file is consulted directly only when the system is running
    # in single-user mode.  At other times this information is provided by
    # Open Directory.
    # This file will not be consulted for authentication unless the BSD local node
    # is enabled via /Applications/Utilities/Directory Utility.app
    # See the DirectoryService(8) man page for additional information about
    # Open Directory.
    nobody:*:-2:-2::0:0:Unprivileged User:/var/empty:/usr/bin/false
    root:*:0:0::0:0:System Administrator:/var/root:/bin/sh
    daemon:*:1:1::0:0:System Services:/var/root:/usr/bin/false
    _uucp:*:4:4::0:0:Unix to Unix Copy Protocol:/var/spool/uucp:/usr/sbin/uucico
    _lp:*:26:26::0:0:Printing Services:/var/spool/cups:/usr/bin/false
    _postfix:*:27:27::0:0:Postfix Mail Server:/var/spool/postfix:/usr/bin/false
    _mcxalr:*:54:54::0:0:MCX AppLaunch:/var/empty:/usr/bin/false
    _pcastagent:*:55:55::0:0:Podcast Producer Agent:/var/pcast/agent:/usr/bin/false
    _pcastserver:*:56:56::0:0:Podcast Producer Server:/var/pcast/server:/usr/bin/false
    _serialnumberd:*:58:58::0:0:Serial Number Daemon:/var/empty:/usr/bin/false
    _devdocs:*:59:59::0:0:Developer Documentation:/var/empty:/usr/bin/false
    _sandbox:*:60:60::0:0:Seatbelt:/var/empty:/usr/bin/false
    _mdnsresponder:*:65:65::0:0:mDNSResponder:/var/empty:/usr/bin/false
    _ard:*:67:67::0:0:Apple Remote Desktop:/var/empty:/usr/bin/false
    _www:*:70:70::0:0:World Wide Web Server:/Library/WebServer:/usr/bin/false
    _eppc:*:71:71::0:0:Apple Events User:/var/empty:/usr/bin/false
    _cvs:*:72:72::0:0:CVS Server:/var/empty:/usr/bin/false
    _svn:*:73:73::0:0:SVN Server:/var/empty:/usr/bin/false
    _mysql:*:74:74::0:0:MySQL Server:/var/empty:/usr/bin/false
    _sshd:*:75:75::0:0:sshd Privilege separation:/var/empty:/usr/bin/false
    _qtss:*:76:76::0:0:QuickTime Streaming Server:/var/empty:/usr/bin/false
    _cyrus:*:77:6::0:0:Cyrus Administrator:/var/imap:/usr/bin/false
    _mailman:*:78:78::0:0:Mailman List Server:/var/empty:/usr/bin/false
    _appserver:*:79:79::0:0:Application Server:/var/empty:/usr/bin/false
    _clamav:*:82:82::0:0:ClamAV Daemon:/var/virusmails:/usr/bin/false
    _amavisd:*:83:83::0:0:AMaViS Daemon:/var/virusmails:/usr/bin/false
    _jabber:*:84:84::0:0:Jabber XMPP Server:/var/empty:/usr/bin/false
    _xgridcontroller:*:85:85::0:0:Xgrid Controller:/var/xgrid/controller:/usr/bin/false
    _xgridagent:*:86:86::0:0:Xgrid Agent:/var/xgrid/agent:/usr/bin/false
    _appowner:*:87:87::0:0:Application Owner:/var/empty:/usr/bin/false
    _windowserver:*:88:88::0:0:WindowServer:/var/empty:/usr/bin/false
    _spotlight:*:89:89::0:0:Spotlight:/var/empty:/usr/bin/false
    _tokend:*:91:91::0:0:Token Daemon:/var/empty:/usr/bin/false
    _securityagent:*:92:92::0:0:SecurityAgent:/var/empty:/usr/bin/false
    _calendar:*:93:93::0:0:Calendar:/var/empty:/usr/bin/false
    _teamsserver:*:94:94::0:0:TeamsServer:/var/teamsserver:/usr/bin/false
    _update_sharing:*:95:-2::0:0:Update Sharing:/var/empty:/usr/bin/false
    _installer:*:96:-2::0:0:Installer:/var/empty:/usr/bin/false
    _atsserver:*:97:97::0:0:ATS Server:/var/empty:/usr/bin/false
    _ftp:*:98:-2::0:0:FTP Daemon:/var/empty:/usr/bin/false
    _unknown:*:99:99::0:0:Unknown User:/var/empty:/usr/bin/false
    _softwareupdate:*:200:200::0:0:Software Update Service:/var/empty:/usr/bin/false
    _coreaudiod:*:202:202::0:0:Core Audio Daemon:/var/empty:/usr/bin/false
    _screensaver:*:203:203::0:0:Screensaver:/var/empty:/usr/bin/false
    _locationd:*:205:205::0:0:Location Daemon:/var/empty/usr/bin/false
    _carddav:*:206:206::0:0:CardDAV Service:/var/empty/usr/bin/false
    _trustevaluationagent:*:208:208::0:0:Trust Evaluation Agent:/var/empty:/usr/bin/false
    _timezone:*:210:210::0:0:AutoTimeZoneDaemon:/var/empty:/usr/bin/false
    _lda:*:211:211::0:0:Local Delivery Agent:/var/empty:/usr/bin/false
    _cvmsroot:*:212:212::0:0:CVMS Root:/var/empty:/usr/bin/false
    _usbmuxd:*:213:213::0:0:iPhone OS Device Helper:/var/db/lockdown:/usr/bin/false
    _dovecot:*:214:6::0:0:Dovecot Administrator:/var/empty:/usr/bin/false

    My system got a gray screen a week ago.  I started open windows and files when i wasn't touching system.  then I went into system to see logs and found all this info was getting sent out - and a history of log showed I had changed print share file share-- which i never use.  //  OK after getting gray screen - it wouldn't reboot.  I put in disk for repair (Utilities Disk) and it shows that permissions wrong and that the "volume" has a error but that it couldn't fix.  When I tried to go back to old backup - there is none YET I have it turned on...
    system.  ERRORS RECEIVED - PERMISSIONS are all wrong - in logs apple can't find the correct paths to files.  I have Library out of my system Library.  I have folders that are titles
    MAC OS10.6.8
    processor 2 ghz core 2 duo
    2gb 667 mhz ddr2 sdram
    From what I can tell NO backups can I access from disk recovery. all this started when I updated APril 12, 2012 Java.  It has changed everything to Alais "A" and "B".  If I delete scripts because they are running -- they appear 2 & 3 times more.  Call me parnoid - but also my sound keeps getting turned on and so does my camera...If I need to reformate - how if I back up will it not effect newly reformated system?  I just know my MAc is doing weird things.  Also On my other system it has users with same names but different numbers after it -- example: user, user1, user 2 user 3, etc. up to over 100 BUT I am unable to access...
    I feel Like I am on a PC not a MAC.

  • Startup Problems : Verify Disk (Disk Utility) Problems

    •Round 1 : Okay...So, here's my newest problem. Occasiionally I'll start my MacBook and sometimes it'll boot just as normal as it always does...or sometimes it will start to boot normally...passing through the grey screen and on to the blue screen with the progress bar...but once it gets to the blue screen...it just sits there. After a few minutes of pushing random buttons...I finally have to hold down the power button and force it to shut down. Then I start it back up and off we go...just like nothing ever happened. Any ideas / suggestion?
    •Round 2 : Sometimes I will start my MacBook and the light on the front with come on to say "Hey, I'm On" ... the CD-ROM will make it's usual noise...the screen will be black...and the "Hey, I'm On" light just remains on for a few then it boots. Just a really slow process. Any ideas / suggestions?
    •Round 3 : In Regards to Round 1 : I tried to do a Verify Disk to see if anything came up and sure enough...something did alright. I've pasted below what it tells me:
    Verifying volume “Macintosh HD”
    Checking HFS Plus volume.
    Checking Extents Overflow file.
    Checking Catalog file.
    Checking multi-linked files.
    Checking Catalog hierarchy.
    Checking Extended Attributes file.
    Checking volume bitmap.
    Volume Bit Map needs minor repair
    Checking volume information.
    Invalid volume free block count
    (It should be 6024381 instead of 6001488)
    The volume Macintosh HD needs to be repaired.
    Error: The underlying task reported failure on exit
    1 HFS volume checked
    Volume needs repair
    •Round 3 (CONT) : From there it does not give the option to repair. If I do Verify Disk Permission & Repair Disk Permissions...it runs through like a fat kid with a pack of Oreo's. Any idea / suggestions. Thanks as usual fellow Apple Nuts

    Well...last night immediately after I made this post...I backed everything up to a FireWire HD and more or less did what you said. Booted from the CD and ran Disk Utility and did a repair. Double checked that repair and rebooted as normal. Came up and tried to run a few things that I had noticed that would slow / bog down my machine...Now everything seems to be great. Thanks for the help!

  • Verify Disk problem

    Hihi! Just did a "Verify Disk" in Disk Utility and had the following error:
    Verifying volume “Macintosh HD”
    Checking 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.
    Volume Header needs minor repair
    The volume Macintosh HD needs to be repaired.
    Error: The underlying task reported failure on exit
    1 HFS volume checked
    Volume needs repair
    Question is, what should I do? I can't even click on the "Repair Disk" option! Help!

    The first thing to do would be to boot from the Install & Restore disc that came with your machine by:
    1. Inserting the disc, pressing the power button, and immediately after the startup chime, press and hold the C key until you see the spinning gear icon appear on the grey splash screen.
    2. After the machine has booted, pick your language, and when the Installer window appears, do not press Continue, but go to the Utilities menu in the menubar and open Disk Utility.
    3. In Disk Utility, choose your normal startup volume in the pane on the left and then click Repair Disk. If any errors show in the window, run Repair Disk again until you see 'The volume appears to be OK' in green.
    4. Quit Disk Utility, quit the installer and attempt to restart into your regular startup volume.
    Joe

  • Repair/verify disk permissions and Preview problem.

    The preview problem is yet to be solved + is outlined here:
    http://discussions.apple.com/thread.jspa?threadID=298858&tstart=0
    Also:
    I decided to open up disk utility and verify disk permissions, this went fine. I then went on to 'verify disk' and it told me:
    Volume Header needs minor repair
    The volume Macintosh HD needs to be repaired.
    Error: The underlying task reported failure on exit
    1 HFS volume checked
    Volume needs repair
    What's the solution? start up from OSX install disc? is this hard to do?

    I am also having trouble with "verify disk permissions".
    I have had frequent crashes recenlty and as a result upgraded to Tiger. The system crashes sometime when recovering from sleep (twice yesterday) and was crashing ferquently in Panther OS when hitting the odd key here and there.
    Since upgrading to Tiger, I have apparrently successfully "repaired the disc permissions" on the start up volume, but then when I come to check them again, there are still the same problems, even though the "disk utility" has been run successfully. Have run disc warrior and "Verify disk" and still not convinced.
    I also notice that the machine seems to be much slower running Tiger than before.
    I avoided a complete install of the new OS because of all the aggro that involves, but it may be my only option if no one can help.
    All thoughts appreciated.
    Thanks
    Powerbook 12   Mac OS X (10.4.5)  

  • Disk utility/repair problem - can't verify disk

    i am trying to run disk utility to clean up my hard drive. i was able to verify and repair permissions without a problem. i have run into 2 problems with disk repair:
    1 - i can't complete the verify disk portion. i get this error message, "Error: The underlying task reported failure on exit." the next line in the box reads, "1 HFS volume checked - Volume needs repair." this leads to the next problem ...
    2 - the repair disk button is nonoperable (doesn't light up) so there is nothing to push for the repair.
    i could use any help you can offer. screen shots are available upon request.
    thanks,
    j

    Hi Dr,g
    The startup drive can only be repaired from another drive. You cannot repair the boot drive from your HD (which is your boot drive). You have to boot from the install disk.
    To do this: Insert the Install Disk 1 into the drive and then select Restart; when you hear the chime hold down C key until the apple logo appears.
    This will take you to the installation software, but you do not want to install.
    Select your language, then go up to the top menu bar to Utilities and navigate to the Disk Utilities application.
    Select the start up drive, then follow the instructions in the First Aid pane where you can click on Repair Disk.
    If it finds errors, repeat the process until it reports no errors.
    After these repairs, quit the application, and restart normally.
    Once restarted normally run Repair Permissions. from the Disk Utility application found on your hard drive in Application/Utilities.
    regards roam

  • Verify Disk Permissions problem

    When I use disk utility and try to perform a Verify Disk Permissions I get the message first aid failed, No valid packages. What pagkages am I missing and how do I get them back if at all possible.

    Hello Dave.
    Check these links.
    http://docs.info.apple.com/article.html?artnum=25704
    http://docs.info.apple.com/article.html?artnum=25751

  • Installed mavericks - restarted, but didn't finish iphoto update - force quit - restart gray screen stall, powers off - safe mode says disk full - recovery mode says mac and recovery HDs locked - verify disk says recovery ok - repair says no live support?

    Installed Mavericks - restarted, but didn't finish iphoto update - force quit - restart gray screen stall, powers off - safe mode says disk full -recovery mode says mac and receovery HDs locked - verify disk says - recovery ok - repair says no live support?

    When you see a beachball cursor or the slowness is especially bad, note the exact time: hour, minute, second.  
    These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.
    Launch the Console application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad and start typing the name.
    The title of the Console window should be All Messages. If it isn't, select
              SYSTEM LOG QUERIES ▹ All Messages
    from the log list on the left. If you don't see that list, select
              View ▹ Show Log List
    from the menu bar at the top of the screen.
    Each message in the log begins with the date and time when it was entered. Scroll back to the time you noted above.
    Select the messages entered from then until the end of the episode, or until they start to repeat, whichever comes first.
    Copy the messages to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
    The log contains a vast amount of information, almost all of it useless for solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.
    Please don't indiscriminately dump thousands of lines from the log into this discussion.
    Please don't post screenshots of log messages—post the text.
    Some private information, such as your name, may appear in the log. Anonymize before posting.

  • Crashing while using Verify Disk

    Repair Disk Permissions works fine but verify (or repair disk) causes system to crash.
    Verify / Repair worked fine when i started up from Tiger Install Disk (and showed no errors).
    Anyone else having this problem?
    p.s. I ran repair disk permissions and then tried it again
    G4 Powerbook   Mac OS X (10.4.6)  

    Sorry that it's taken me so long to report back.
    - Journaling is enabled.
    - logged in using root user; ran verify boot volume; it worked without crashing
    - logged back in with my regular user account; reran verify boot volume. it took several minutes but it reported back that volume was fine. (when i first posted I let verify boot volume run for a good 15 to 20 minutes before deciding it had crashed.
    - not sure why it's working now when it didn't before but thanks

  • Verify Disk Fails on 11" Mid-2011 MBA

    Hi,
    When using Disk Utility to Verify Disk, I get the following error:
    Unable to bootstrap transaction group 1877: invalid field value
    No valid commit checkpoint found
    The volume 5E475AC6-27BF-4533-89F3-A1E555405EDA was found corrupt and needs to be repaired.
    Problems were found with the partition map which might prevent booting
    Error: Storage system verify or repair failed.
    I tried searching, but didn't seem to be able to find anything related. Anybody have any ideas?
    Thanks!

    I have the same problem and my drive is encrypted with Filevault 2.  Here is a copy of my Disk Utility results-
    Verifying partition map for “TOSHIBA MK7559GSXF 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 all HFS data partition loader spaces
    Checking Core Storage Physical Volume partitions
    Checking storage system
    Checking volume.
    disk0s2: Scan for Volume Headers
    disk0s2: Scan for Disk Labels
    Logical Volume Group D6C6B140-FF84-4215-A23B-2F338FDB07DE spans 1 device
    Logical Volume Group has a 16 MB Metadata Volume with double redundancy
    Start scanning metadata for a valid checkpoint
    Load and verify Segment Headers
    Load and verify Checkpoint Payload
    Load and verify Transaction Segment
    Load and verify Transaction Segment
    Incorporate 1 newer non-checkpoint transactions
    Load and verify Virtual Address Table
    Load and verify Segment Usage Table
    Load and verify Metadata Superblock
    Load and verify Logical Volumes B-Trees
    Logical Volume Group contains 1 Logical Volumes
    Load and verify BFACC386-1738-482F-B4C8-438DC4A8850E
    Load and verify F8E6D497-E9AC-41A4-9917-AD101492A4C9
    Load and verify Freespace Summary
    Load and verify Block Accounting
    Load and verify Segment Cleaning
    Unable to bootstrap transaction group 5720: invalid field value
    Continue scanning metadata for an older checkpoint
    Load and verify Segment Headers
    Load and verify Checkpoint Payload
    Load and verify Transaction Segment
    Incorporate 0 newer non-checkpoint transactions
    Load and verify Virtual Address Table
    Load and verify Segment Usage Table
    Load and verify Metadata Superblock
    Load and verify Logical Volumes B-Trees
    Logical Volume Group contains 1 Logical Volumes
    Load and verify BFACC386-1738-482F-B4C8-438DC4A8850E
    Load and verify F8E6D497-E9AC-41A4-9917-AD101492A4C9
    Load and verify Freespace Summary
    Load and verify Block Accounting
    Load and verify Segment Cleaning
    Unable to bootstrap transaction group 5719: invalid field value
    Continue scanning metadata for an older checkpoint
    Load and verify Segment Headers
    Load and verify Checkpoint Payload
    Load and verify Transaction Segment
    Incorporate 0 newer non-checkpoint transactions
    Load and verify Virtual Address Table
    Load and verify Segment Usage Table
    Load and verify Metadata Superblock
    Load and verify Logical Volumes B-Trees
    Logical Volume Group contains 1 Logical Volumes
    Load and verify BFACC386-1738-482F-B4C8-438DC4A8850E
    Load and verify F8E6D497-E9AC-41A4-9917-AD101492A4C9
    Load and verify Freespace Summary
    Load and verify Block Accounting
    Load and verify Segment Cleaning
    Unable to bootstrap transaction group 5718: invalid field value
    Continue scanning metadata for an older checkpoint
    Load and verify Segment Headers
    Load and verify Checkpoint Payload
    Load and verify Transaction Segment
    Incorporate 0 newer non-checkpoint transactions
    Load and verify Virtual Address Table
    Load and verify Segment Usage Table
    Load and verify Metadata Superblock
    Load and verify Logical Volumes B-Trees
    Logical Volume Group contains 1 Logical Volumes
    Load and verify BFACC386-1738-482F-B4C8-438DC4A8850E
    Load and verify F8E6D497-E9AC-41A4-9917-AD101492A4C9
    Load and verify Freespace Summary
    Load and verify Block Accounting
    Load and verify Segment Cleaning
    Unable to bootstrap transaction group 5717: invalid field value
    No valid commit checkpoint found
    The volume D6C6B140-FF84-4215-A23B-2F338FDB07DE was found corrupt and needs to be repaired.
    Problems were found with the partition map which might prevent booting
    Error: Storage system verify or repair failed.
    This is a brand spanking new Macbook Pro 8,2 with a clean install of lion with my user account migrated from a time machine backup.  The weird thing is that if I boot to the recovery partition and verify the disk, it comes back clean with no errors.  When I log in again and run disk utility immediately after logging in, disk utility shows no errors.  I only get these errors after the machine has been on for a while.
    I have tried just doing a repair disk in the recovery partition to see if it would help but I still get the same errors after a few hours of use.  I think there is a bug with Filevault.
    I am using 10.7.1

  • Disk Utility 13 problem with USB drives

    There appears to be a problem with Disk Utility 13 (part of OS X 10.9). At least, so far as I can tell, everything traces back to this app, or possibly OS X 10.9 itself.
    I recently upgraded my MacBook Air to OS X 10.9 (reformatted hard drive, installed system from scratch, updated with all the latest Apple updates). I pre-checked all my third party software to make sure it was 10.9 compatible before installing it after the system cleanup, so everything I’m running supposedly has been approved as safe for 10.9. But I’m seeing a problem formatting USB drives that I do not encounter when running under 10.8.
    I have a Seagate STAA500101 (“FreeAgent GoFlex”) drive connected via Seagate’s USB3 adapter that I’ve used for some time as a Time Machine backup. Post-overhaul, I decided to erase the backup and start fresh. When I attempt to format it (single GUID partition) with Disk Utility, I see the following messages go by:
    Formatting disk1s2 as Mac OS Extended (Journaled) with name Untitled 1
    Could not mount disk1s2 with name (null) after erase
    Then there’s a pause, and the format appears to conclude fine. But if I run a “Verify Disk” immediately, I get this:
    Verifying partition map for “Seagate FreeAgent GoFlex 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 all HFS data partition loader spaces
    Volume  on disk1s2 has 0 bytes of trailing loader space and it needs 134217728 bytes
    Problems were found with the partition map which might prevent booting
    Error: Partition map needs repair because a data partition needs loader space.
    As the drive has just been formatted, that seemed odd. I took it over to another Mac still running 10.8.5 and formatted it there — it worked just fine. Verified just fine. Took the drive back to my MacBook Air and tried to verify the disk — same failure.
    I wanted to rule out bad media, so I took a Lexar 16GB USB flash drive and tried to format it with Disk Utility 13 — got the same problem.
    The only success I’ve had formatting USB drives under 10.9 is to boot up into OS X Recovery. Disk Utility there formatted my Seagate drive without an error. But once I booted back into normal 10.9 operating mode, the drive once again fails to verify; it makes me leery about using it as a Time Machine backup.
    I suppose it’s possible there could be some background component like Sophos causing problems when formatting drives, but if I format a drive via OS X Recovery or another Mac under 10.8, that wouldn’t explain why the drives fail to verify.
    Anyone got any other observations on this issue?

    Problem resolved. I'm posting this note for anyone else who might run into this situation and come across this discussion.
    It actually did turn out to be Sophos -- Cloud, that is. I'd been using Sophos' free Mac antivirus software on a variety of systems but forgot that I was now testing out Sophos Cloud on my own MacBook, which is their new endpoint solution, and supposed to be compatible with OS X 10.9 (although the Mac version is listed as "beta") Sophos Cloud includes a new feature called Device Control which allows you to create a company-wide policy to control access to hardware such as USB drives, optical drives, etc. But apparently it's still pretty buggy. I had my Device Control configured with the default setting of "monitor but do not block" but it was most definitely gumming up the system. With Sophos Cloud installed, here's what happens if I try to run "Verify Disk" on any attached drive. Note on the left side how "disk2s2" shows as a sub-volume for each hard drive.
    So if I uninstall Sophos Cloud, reboot and rescan, here's what I get:
    Works fine. Note that the "disk2s2" subvolumes are also gone. This is the way Disk Utility also appears on a 10.8 or 10.9 system, even if you have the standard free Sophos for Mac software installed. It's only Sophos Cloud that's not playing nice. It also appears to have stopped me from being able to play DVDs from an attached Apple USB SuperDrive -- that problem was likewise solved by removing Sophos Cloud.

  • After clean install of Mountain Lion 10.8.5 no Gate Keeper and a ton a long list of differences in verify disk permissions after updating to Itunes 12.1

    HI everybody.
    I have a MacBopok Prop 15" from mid 2012, 2.6Ghz, Intel Core i7, 16GB RAM 1 TB SSD.
    As my Mac was running as fast as possible it  was getting slower down during start and shutdown, from 2 secopnds to 15 secconds during start and shutdown . Apps were crashing sometimes a freeze, total crash which made me go directly to Recovery HD and not my log in page after all the tricks I know I took it to service center where they zeroed my SSD HD and reinstalled Mountain Lion 10.8.5. Strangly enough Gate keeper was not in my preferences and a old version of Itunes 10.4 if I recall. The Mac is still slow while I reinstall all apps from App store and one for one documents and folders from my latest TM back up.
    Updated the Security update, and other updates had the same problem as many updating Iphoto 9.4.3 error 102, still have not been able.
    But running verify disk permissions there is a massive list of Itunes differences while I have not  even added one song. At least 60 to 70 differences. I know a lot of these differences are nothing to worry about but a clean install without Gate keeper and an old Itunes which after update to 12.1 has so many disk differences, this can not as it should be also as I have not added anything from my Itunes library. Any feedback or advice would be very much appreciated.
    Greetings
    Matt

    Do a backup. Boot to the Recovery Volume (command - R on a restart or hold down the option/alt key during a restart and select Recovery Volume). Run Disk Utility Verify/Repair and Repair Permissions until you get no errors. Then re-install the OS.
    OS X Recovery
    OS X Recovery (2)

Maybe you are looking for

  • Installing 8i Personal Edition

    I am installing Oracle 8i Personal Edition on windows 98 and I ran into a problem. I couldn't install the Database Configuration Asistant. The log reads: Documents\Downloads\Oracle8i\starterdb is an invalid command line argument So it is looking in D

  • Invoices   posting

    HI how to block invoices posting to accounting in sd process not in FI   but i know regading biiling controls posting block but i want know the if  any other process for po blocking

  • My safari did not change after downloading mountain lion

    I thought everying was suppose to look the same on all devices with Mountain Lion? on my ipad and iphone safari did not change.

  • Advanced Planning for the retail industry

    Hi, First, I would like to know the best solutions for planning in the retail industry and if you can share with me more detail about these solutions. Second, I want to understand the SCM menu....I know that under the point Advanced Planner and Optim

  • Feature request: modifier key to enable snap when working with lines

    In order to connect lines and close shapes more quickly, I would like to use a modifier key to get a point to snap. Otherwise it's an extra step to use keyboard shortcut or clicking the toolbar icon (which doesn't always display). I would like to clo