Drive has reported a fatal error to Disk Utility, HELP ME PLEASE!!!

I'm a little worried my Macbook Pro has become an overpriced paperweight.
Here's what happened:
I had a spare 512MB RAM, which was taken out of my 24" iMac Intel Core 2 Duo when I replced it with a 1GB RAM and, after checking several sources on the web, successfully installed the extra RAM in the MBP.
I restarted the MBP and the new RAM was registered after checking in About this Mac. I then began using the MBP as normal and wrote and saved a Word document. I clicked on the email and Safari icons in the dock and they just kept bouncing in the dock without launching. Pressed Power button - nothing. Took out the battery and replaced it after 30secs and pressed power button. All I got was the grey screen with the Apple logo and the winding circle which stayed like that for 20 minutes.
First reaction was to remove the RAM and restart. Same endless grey screen and winding circle.
Rebooted from CD, checked disk and repaired and said everything was OK. Restarted without CD still nothing.
Tried Archive and Install and came back with an error during installation.
Tried Erase and Install - same error.
Tried to select startup disk and it no longer could find my HD yet Disk Utility could find it and told me everything was OK. Tried resetting PRAM nothing.
Tried to erase the HD and nothing happened. Erasing a HD takes some time, but everytime I hit erase 10 seconds later it was back to the same point where I began
Next tried to create one single partition and struck the message Drive has reported a fatal hardware error to disk utility. Even the lettering for the main drive is now in red.
Do I need to replace the hard drive altogether or is there a solution to this problem. Was it the RAM that brought me undone or was that just a coincidence?
PLEASE HELP ME!!!

make sure that you haven't used it yet as RAM can only be used in one machine, not transferred to another one (like you did).
Sorry, but that's completely untrue, and I don't know where you might have read or heard such a fallacy. RAM has no registration that even tells a system that it's been used, much less a key that would make it work only in one system. As long as the RAM is properly compatible and precautions are taken not to shock a system with static electricity while removing or inserting the component or causing mechanical damage, a RAM module can be swapped between systems as often as desired.

Similar Messages

  • Problems with External Hard drive, will not mount and errors in disk utilit

    i have a powerbook g4 aluminum. i have an external hard drive for it. a simple tech 100gig portable drive, almost brand new. i dont know what happened to it, but one day i was starting my computer up with it attached. it wounldnt fully start up, said "waiting for local disks" so i uplugged the external hard drive. now it wont mount and will only show up in the disk utility of my friends macbook. i tried to verify and repair, and this is the message i got.
    Verify and Repair disk “UNTITLED”
    ** /dev/disk1s1
    could not read boot block (Input/output error)
    Error: The underlying task reported failure on exit
    1 non HFS volume checked
    1 volume could not be repaired because of an error
    Im in mexico writing a book and so i really need help on this one guys.

    Hi, hjbugs, and welcome to Apple Discussions. Disconnecting the drive while your Powerbook was accessing it probably caused your problem. It may be repairable using DiskWarrior or TechTool Pro, but if you don't have access to one of those and aren't going to buy one, reformatting the drive with Disk Utility may be the only other way to make it usable again. If it contains data you need to recover first (i.e., data that isn't also stored on your internal HD or other storage media), download the free demo version of one of the data recovery utilities mentioned in this thread and use it to see what is recoverable. If the files you need are recoverable, buy the full version of one of the utilities and recover them.

  • Reported Fatal Hardware Error to Disk Utility

    I see the following message in my Power Book G4 Disk Utility:
    "This drive has Reported Fatal Hardware Error to Disk Utility. If drive has not failed completely, back up as much data as you can and then replace it with a new drive."
    I already made a back up my Home folder to my external HD. The install disk utility reports the same and has grey the repair uptions.
    The spinning beachball appears constantly when using Safari and iTunes. What should I do?

    If your Mac is no longer under the standard 1-yr warranty period or under the 3-yr extended warranty if you purchased the AppleCare extended warranty for your PB, you need to purchase a new internal hard drive that is compatible with your Mac model. This is something you can install yourself or take your Mac to an Apple authorized repair facility to purchase and have a new internal hard drive installed.
    The repair facility should include re-installing whichever OX version and all software that was pre-installed and shipped with this Mac when purchased new. If this wasn't Tiger and you purchased a Tiger retail install package, you can re-install the Tiger upgrade yourself and then replace all data from your backup on the new hard drive.

  • Py2app stub executable has encountered a fatal error, and will now terminate. How do I fix this?

    I can't get rid of the following startup error message:
    py2app stub executable has encountered a fatal error, and will now terminate.
    How do I fix this?
    It started after my G5 PowerPC crashed while watching an iTunes Podcast.
    Thanks.

    Are you using Google Drive, Dropbox, or such?
    https://discussions.apple.com/thread/5286185?start=0&tstart=0
    http://productforums.google.com/forum/#!msg/drive/OxB-qAsRQS4/Txvcg18ATCMJ

  • Audition has encountered a fatal error and needs to shutdown

    All of a sudden, Audition has been frequently giving me this error "audition has encountered a fatal error and needs to shutdown" and shutting down when I select an area using the Paint Brush selection Tool in the Spectral Display. I have made lots of use of this tool in the recent past, editing out noise in recordings. But, this error now makes that tool almost useless.
    How can I fix whatever is wrong?
    1) MacBookPro with Lion 10.7.4
    2) Audition CS6, v5.0 build 708
    3) Editing wave files using the Paintbrush tool to select small areas to reduce the level.
    4) Does NOT seem file dependent, since this problem has occurred on brand new wave files and previously edited wave files. I do not know if it is restricted to wave files. That is just all record - wave 24/96.
    5) The problem generally occurs when I simply select an area. I think sometimes it doesn't surface, until I try to adjust the level.
    6) I have used this tool a lot, prior to this problem surfacing. I' had no troubles. then, on a file I hade been making lots of little edit to, to clean up the noise, it suddenly started giving me this error. Since then, any file I have tried to use the Paint Brush tool give me this error. Forces me to save  VERY frequently.
    Any ideas?
    Mike

    Hi Mike,
    First, let me ask that the next time this crash occurs, please locate and send the corresponding OS X Crash log.  To locate this file, do the following:
    Open Finder
    From the menu bar, choose Go > Go To Folder...
    In the "Go to the Folder" box that pops up, type: ~/Library/Logs/Diagnostic Reports/ and click Go
    Locate the Adobe Auudition CS6_2012... file that is most recently dated and send it as an attachment to [email protected]
    I would then suggest two steps to resolve this:
    Update Audition:
    Click Help > Updates in the menu bar and update Audition CS6 to v5.0.2
    If you still experience a crash after updating Audition, let's temporarily reset the preference files for Audition and see if that makes a difference.
    Open Finder
    From the menu bar, choose Go > Go To Folder...
    In the "Go to the Folder" box that pops up, type ~/Library/Preferences/Adobe/Audition/ and click Go
    Rename the "5.0" folder to something else, such as "5.0_OLD"
    Audition will rebuild these preference files to its defaults on the next launch.  See if this crash is still a problem.
    Thanks!

  • The ODBC driver has returned a SQL error.

    Getting the error in Report Generation:
    The ODBC driver has returned a SQL error.
    Error class: com.sybase.jdbc.SybSQLException
    Error message: ASA Error-141: Table 'SystemSite' not found
    ODBC was set up according to the readme. What else do I have to do to get
    Inventory Reports working.
    Thanks,

    Hwbranson,
    It appears that in the past few days you have not received a response to your
    posting. That concerns us, and has triggered this automated reply.
    Has your problem been resolved? If not, you might try one of the following options:
    - Do a search of our knowledgebase at http://support.novell.com/search/kb_index.jsp
    - Check all of the other support tools and options available at
    http://support.novell.com.
    - You could also try posting your message again. Make sure it is posted in the
    correct newsgroup. (http://support.novell.com/forums)
    Be sure to read the forum FAQ about what to expect in the way of responses:
    http://support.novell.com/forums/faq_general.html
    If this is a reply to a duplicate posting, please ignore and accept our apologies
    and rest assured we will issue a stern reprimand to our posting bot.
    Good luck!
    Your Novell Product Support Forums Team
    http://support.novell.com/forums/

  • HT1657 my rental has reported a download error and cannot be downloaded or deleted - any suggestions?

    my rental has reported a download error and cannot be downloaded or deleted - any suggestions on how to fix it one way or another?

    Hello there, asim01.
    The following Knowledge Base articles offer a few pointers with troubleshooting issues with downloads from iTunes. First thing to try is verifying connectivity to the iTunes Store:
    Can't connect to the iTunes Store
    http://support.apple.com/kb/ts1368
    If the issue is related to an interrupted download:
    iTunes: How to resume interrupted iTunes Store downloads
    http://support.apple.com/kb/ht1725
    Ultimately, if you are still unable to download your purchase, feel free to report the issue using the following information:
    How to report an issue with your iTunes Store, App Store, Mac App Store, or iBooks Store purchase
    http://support.apple.com/kb/ht1933
    Thanks for reaching out to Apple Support Communities.
    Cheers,
    Pedro.

  • The parsing engine has encountered a fatal error condition......

    I am creating a new Entitilement Segment. When I sync, I get a parsing
    exception. The error stack is described below. The same error message
    is displayed while starting the server.
    Any help is appreciated.
    Kumar
    URI : /contentselectors/GlobalContentSelectors.rls
    Cause : Exception raised when executing create, please see the embedded
    exception.
    StackTrace :
    Exception[com.bea.p13n.expression.internal.parser.ParseException: The
    parsing engine has encountered a fatal error condition; see embedded
    exception for details.]
    at
    com.bea.p13n.expression.internal.parser.ExpressionParserImpl.parse(ExpressionParserImpl.java:175)
    at
    com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.createRuleSet(RuleSetPersistenceManager.java:489)
    at
    com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.createDataItem(RuleSetPersistenceManager.java:168)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.handleDataItemMessage(AbstractDataRepository.java:814)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:990)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestResultMessage(AbstractDataRepository.java:1185)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:261)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestMessage(AbstractDataRepository.java:1086)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:257)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepository(AbstractDataRepository.java:706)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:658)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:606)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:994)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestResultMessage(AbstractDataRepository.java:1185)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:261)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestMessage(AbstractDataRepository.java:1086)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:257)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepository(AbstractDataRepository.java:706)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:658)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:606)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:994)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.transport.servlets.DataSyncServlet.dispatchMessage(DataSyncServlet.java:351)
    at
    com.bea.p13n.management.data.transport.servlets.DataSyncServlet.doPost(DataSyncServlet.java:276)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at
    weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1058)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:401)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
    at
    weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5412)
    at
    weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:744)
    at
    weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3086)
    at
    weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2544)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
    Caused by: org.xml.sax.SAXParseException: Valid documents must have a
    <!DOCTYPE declaration.
    at org.apache.crimson.parser.Parser2.warning(Parser2.java:3074)
    at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:491)
    at org.apache.crimson.parser.Parser2.parse(Parser2.java:305)
    at
    org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:433)
    at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:371)
    at
    com.bea.p13n.expression.internal.parser.ExpressionParserImpl.parse(ExpressionParserImpl.java:161)
    at
    com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.createRuleSet(RuleSetPersistenceManager.java:489)
    at
    com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.createDataItem(RuleSetPersistenceManager.java:168)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.handleDataItemMessage(AbstractDataRepository.java:814)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:990)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestResultMessage(AbstractDataRepository.java:1185)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:261)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestMessage(AbstractDataRepository.java:1086)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:257)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepository(AbstractDataRepository.java:706)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:658)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:606)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:994)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestResultMessage(AbstractDataRepository.java:1185)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:261)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestMessage(AbstractDataRepository.java:1086)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:257)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepository(AbstractDataRepository.java:706)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:658)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:606)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:994)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.transport.servlets.DataSyncServlet.dispatchMessage(DataSyncServlet.java:351)
    at
    com.bea.p13n.management.data.transport.servlets.DataSyncServlet.doPost(DataSyncServlet.java:276)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at
    weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1058)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:401)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
    at
    weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5412)
    at
    weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:744)
    at
    weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3086)
    at
    weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2544)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
    Resource key "Corrective Action" not found for class
    com.bea.commerce.tools.server.SynchronizationProgress. null
    ==================================================================
    URI : /entitlements/GlobalEntitlements.rls
    Cause : Exception raised when executing create, please see the embedded
    exception.
    StackTrace :
    Exception[com.bea.p13n.expression.internal.parser.ParseException: The
    parsing engine has encountered a fatal error condition; see embedded
    exception for details.]
    at
    com.bea.p13n.expression.internal.parser.ExpressionParserImpl.parse(ExpressionParserImpl.java:175)
    at
    com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.createRuleSet(RuleSetPersistenceManager.java:489)
    at
    com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.createDataItem(RuleSetPersistenceManager.java:168)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.handleDataItemMessage(AbstractDataRepository.java:814)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:990)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestResultMessage(AbstractDataRepository.java:1185)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:261)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestMessage(AbstractDataRepository.java:1086)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:257)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepository(AbstractDataRepository.java:706)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:658)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:606)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:994)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestResultMessage(AbstractDataRepository.java:1185)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:261)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestMessage(AbstractDataRepository.java:1086)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:257)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepository(AbstractDataRepository.java:706)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:658)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:606)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:994)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.transport.servlets.DataSyncServlet.dispatchMessage(DataSyncServlet.java:351)
    at
    com.bea.p13n.management.data.transport.servlets.DataSyncServlet.doPost(DataSyncServlet.java:276)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at
    weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1058)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:401)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
    at
    weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5412)
    at
    weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:744)
    at
    weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3086)
    at
    weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2544)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
    Caused by: org.xml.sax.SAXParseException: Valid documents must have a
    <!DOCTYPE declaration.
    at org.apache.crimson.parser.Parser2.warning(Parser2.java:3074)
    at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:491)
    at org.apache.crimson.parser.Parser2.parse(Parser2.java:305)
    at
    org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:433)
    at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:371)
    at
    com.bea.p13n.expression.internal.parser.ExpressionParserImpl.parse(ExpressionParserImpl.java:161)
    at
    com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.createRuleSet(RuleSetPersistenceManager.java:489)
    at
    com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.createDataItem(RuleSetPersistenceManager.java:168)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.handleDataItemMessage(AbstractDataRepository.java:814)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:990)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestResultMessage(AbstractDataRepository.java:1185)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:261)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestMessage(AbstractDataRepository.java:1086)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:257)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepository(AbstractDataRepository.java:706)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:658)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:606)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:994)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestResultMessage(AbstractDataRepository.java:1185)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:261)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestMessage(AbstractDataRepository.java:1086)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:257)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepository(AbstractDataRepository.java:706)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:658)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:606)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:994)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.transport.servlets.DataSyncServlet.dispatchMessage(DataSyncServlet.java:351)
    at
    com.bea.p13n.management.data.transport.servlets.DataSyncServlet.doPost(DataSyncServlet.java:276)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at
    weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1058)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:401)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
    at
    weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5412)
    at
    weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:744)
    at
    weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3086)
    at
    weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2544)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
    Resource key "Corrective Action" not found for class
    com.bea.commerce.tools.server.SynchronizationProgress. null
    ==================================================================
    URI : /segments/GlobalClassifications.rls
    Cause : Exception raised when executing create, please see the embedded
    exception.
    StackTrace :
    Exception[com.bea.p13n.expression.internal.parser.ParseException: The
    parsing engine has encountered a fatal error condition; see embedded
    exception for details.]
    at
    com.bea.p13n.expression.internal.parser.ExpressionParserImpl.parse(ExpressionParserImpl.java:175)
    at
    com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.createRuleSet(RuleSetPersistenceManager.java:489)
    at
    com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.createDataItem(RuleSetPersistenceManager.java:168)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.handleDataItemMessage(AbstractDataRepository.java:814)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:990)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestResultMessage(AbstractDataRepository.java:1185)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:261)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestMessage(AbstractDataRepository.java:1086)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:257)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepository(AbstractDataRepository.java:706)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:658)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:606)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:994)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestResultMessage(AbstractDataRepository.java:1185)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:261)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestMessage(AbstractDataRepository.java:1086)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:257)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepository(AbstractDataRepository.java:706)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:658)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:606)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:994)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.transport.servlets.DataSyncServlet.dispatchMessage(DataSyncServlet.java:351)
    at
    com.bea.p13n.management.data.transport.servlets.DataSyncServlet.doPost(DataSyncServlet.java:276)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at
    weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1058)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:401)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
    at
    weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5412)
    at
    weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:744)
    at
    weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3086)
    at
    weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2544)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
    Caused by: org.xml.sax.SAXParseException: Valid documents must have a
    <!DOCTYPE declaration.
    at org.apache.crimson.parser.Parser2.warning(Parser2.java:3074)
    at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:491)
    at org.apache.crimson.parser.Parser2.parse(Parser2.java:305)
    at
    org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:433)
    at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:371)
    at
    com.bea.p13n.expression.internal.parser.ExpressionParserImpl.parse(ExpressionParserImpl.java:161)
    at
    com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.createRuleSet(RuleSetPersistenceManager.java:489)
    at
    com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.createDataItem(RuleSetPersistenceManager.java:168)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.handleDataItemMessage(AbstractDataRepository.java:814)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:990)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestResultMessage(AbstractDataRepository.java:1185)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:261)
    at
    com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
    at
    com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestMessage(AbstractDataRepository.java:1086)
    at
    com.bea.p13n.management.data.reposit

    Hi kumar,
    did you find what was the resolution for this.
    thanks

  • Adobe Downloading Adobe Photoshop Elements 13 MultipleLanguages Windows  The Akamai Download Manager has encountered an fatal error: File not found.

    I am trying to download the trial of PSE 13 which consists of two files. The first downloads ok but on the second I get this message:
    Downloading Adobe Photoshop Elements 13 MultipleLanguages Windows
    The Akamai Download Manager has encountered an fatal error: File not found.
    Same thing happens if I try to download the files individually and also in different browsers. Any ideas?

    Me three.   I have been trying for hours, and have used three different browsers. 
    I have just noticed that the URL it is trying to use is looking for ...win32.exe under a directory called win64. That sounds like a stupid typo mistake.  I manually modified the URL to this instead (and it downloaded something)...
    http://trials3.adobe.com/AdobeProducts/PSE/13/win32/PhotoshopElements_13_LS25_win32.exe
    Now I just need to figure out how to install the product manually using the two downloaded files!?!

  • Disk Management Tool error in Disk Utility

    Update: (first, reviewing problem that I and others have been having, including on 10.4.x systems):
    When I attempt to repair permissions on my HD with Disk Utility, I get this specific error message: "Disk Utility internal error -- Disk Utility has lost its connection with the Disk Management Tool and cannot continue. Please quit and relaunch Disk Utility" and the repair-permissions will not proceed. It fails to get the proper "correct" permissions info for that drive to allow the repair. The error log points to a file in the Library called "DiskManagementToll" The path is ~/System/Library/PrivateFrameworks/DiskManagement.framework/Resources/DiskManag ementTool)
    This problem is appearing in many forums here and elsewhere, including 10.4.x systems (like mine) and persists in a few after deleting suggested files. Is there a sophisticated solution that addresses the problem through the DiskManagementTool file by replacing some values or replacing the file from a backup vis SUDO or Root?
    Previous posts have focused on Macs running 10.3.x and with iTunes 6.0x installed. Not here, so the problem is more general. None of the "delete iTunes / plists / Chess.app" suggested fixes have worked for me. Also tried running DU from my Tiger install disk; no luck! -- still fails when it tries to determine the correct permissions.
    The "DiskManagementTool" file apparently either stores the correct file permissions or handles reading them from the receipts in the Library. If I understand things right, Disk Utility is actually a (user)-permissioned graphic front end, while DiskManagementTool is a Root-user-level tool that actually does the heavy lifting. Can I replace -- and any benefit to that -- or rewrite it with proper access?
    There is a complete crash log report in Crash Reporter, by the way. Anyone want the text, and would it help figure out what's happening?
    I've tried the suggested deletion of iTunes 6.0.2 or Chess.app and their plists (these and other steps were suggested on MacFixIt at http://www.macfixit.com/article.php?story=20060111090035797 the advice is, basically, to delete iTunes 6.0.2 and/or Chess.app and related plist files.) As I said, no luck!
    Everyone that I talk to says it MUST be the fault of some other 3rd-party disk utility software.
    For what it's worth, I HAVE run Disk Warrior -- and, the drive that's having the problem is a recent reinstall from a backup using Carbon Copy Cloner. The original disk is NOT having such a problem, only the hard drive on my iBook after the reinstall. Don't know if that gives any clues (or to how the link gets somehow disengaged between Disk Utility and the Disk Management Tool file / software).
    Any thoughts on that? What about replacing the Disk Management Tool file in the Library or forcing some kind of re-link to it? some Unix guru MUST know a fix!
    Obviously, the big worry for me is that I can't update my System to 10.4.5 or anything else without repairing permissions first. This IS a big deal. And others are having the same problem. Help?!?
    New 2 GHz dual g5 , Dual g4, & iBook G4 (recent) Mac OS X (10.4.4)

    A system problem was involved that became, briefly, a "known issue" that was solved in the next minor update. Solved, anyway, by the advice given by the last poster. Thanks! SJ

  • Hard drive will not mount shows up in Disk Utility

    I have an external drive with a bootable OS X 10.6.8. I was in a transition between building up a SSD swapped drive. The SSD is installed in the CPU box but I have my old installation running from an external.
    I have several external hard drives. They are all Firewire. Some have USB 3.0 and or eSATA options but my MacMini only talks to Firewire and USB 2.0.
    I understand that you daisy chain Firewire drives and turn them on and off in sequence as they fall from the CPU box/case.
    Firewire is a power source. I run the external with the OS using an AC adapter but one Firewire drive is powered through Firewire.
    I have had as many as 4 external drives running along with the internal drive without a glitch while I was reorganizing files.
    Today I booted off the external drive. It was running fine. I turned on one Firewire drive (the one that runs on Firewire power). That drive stumbled. I recognized the sound when there is an interruption in power. This cause the external boot drive to stall. I had to force a reboot.
    Now the external boot drive will not boot up. It does not mount but Disk Utility sees it. The drive itself is bright and clear in Disk Utility but the partition (single) is faded out. I can run Verify and repair in DU. DU says it doesn't see anything to repair. It will not mount on its own or when I click the Mount button in DU. It does not produce an icon on the Desktop (because it is not mounting).
    I also have SpeedTools. But although it sees the drive I cannot do anything with it. None of its tools run more than a spli second before they fail.
    This drive has USB 3.0 and I see everything through USB that I see through Firewire. Connecting the other way did not get around the problem.
    Of course I will buy an AC adapter for every external drive and never run them using Firewire again but the horse is out of the barn.
    I have the original installation disks and could run the Archive and Install option but it would require physically swapping drives with the internal. I'd like to avoid it if possible. It is a MacMini and tedious.
    Any suggestions?

    I took the problematic hard drive and installed it in my Mac Mini so I could attempt a Safe Boot and then Archive and Install if necessary.
    Safe Mode didn't work. The drive produced the circle with a slash symbol.
    I reset the PRAM which was part of a list of steps to work through I found created by Apple Support.
    I was able to boot up to Verbose Mode and view the text of the boot process. I wrote it all down. I can answer questions about the content better than typing it all out exactly. It includes, "...journal magic is bad..." "...failed to open..." and ends with "...cannot mount root, errno = 19"
    I attempted Archive and Install however when it went to show what target drives were available it was a blank box and all buttons were grayed out.
    I rebooted and opened Disk Utility from the DVD. The drive appeared the same with the top main line bright and the partitioned volume faded. Still was unable to mount. I ran Verify and this time a red line of text appeared "Invalid content in Journal" and at the end I ran Repair. When running I could read line by line and at one point it showed "checking volume information" then the following line "Repairing volume" the following line "Rechecking volume" more line of checking then it ended with "The volume was repaired successfully."
    It still would not mount. I ran Verify again and again said "Invalid content in Journal" and this time it stopped midway saying "The volume was found corrupt and needs to be repaired. Error: This disk needs to be repaired. Click Repair Disk."
    I clicked Repair and it ended with The vol. was repaired successfully."
    Still unable to mount I began repeating Repair over and over. Each time it found something to repair and ended with a success message. After several more Repairs I tried Verify and it stopped midway saying to Repair the disk.
    Question: Does running Repair multiple times continue to correct bits and pieces little by little or is this a generic message and we should treat it as a problem Disk Utility cannot pinpoint and is just beating its head against the wall?
    The step by step instructions I downloaded mentioned running Repair more than once but it did not say that running it 20 times would erode some problems and eventually lead to a fully repaired disk (if the problem was something DU could take care of in the first place). At this point I have run Repair about 20 times total with a series of 10 back to back skipping Verify. I keep seeing the lines about invalid content in a journal and that it repaired something successfully. Yet I still cannot mount the disk.

  • My hard drive is damaged. I'm using disk utility; can I safely use CHECKSUM? will it help or give me info?

    my hard drive is damaged. I'm using disk utility; can I safely use CHECKSUM? will it help or give me info?

    Repair the Hard Drive and Permissions
    Boot from your Snow Leopard Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list.  In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive.  If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer.
    If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.

  • Endless errors on disk utility

    My 2nd internal hard drive in 2.5 years just died on my iMac G5. Apple is coming on-site to fix. During the 1st hard drive death, I installed the operating system on an external drive and was able to work from that drive. I assume this was legal since I was discussing all these things with AppleCare as the int harddrive died (over the course of a week of AppleCare calls). Doing this allowed me to save a substantial amt of data. Since then I have used this drive as a backup drive, rathern than as an operating system.
    Now, I'm trying the same thing with the 2nd internal hard drive death. After booting up to the external drive, the first thing I did was upgrade from 10.4 to 10.4.8. I restarted the computer using the exteral drive. The Mac OSX setup assistant wouldn't connect. I tried to disconnect and it wouldn't disconnect, either. I Force Quitted out of the setup assistant. The 2nd thing I did was run disk utility and verify permissions. It said I had no valid packages. I copied BaseSystem.pkg and Essentials.pkg into the Library. Now disk utility gives me absolutely endless errors, all of them "User differs on..." followed by "Group differs on..."
    Since this is mainly a backup disk, all my files are under ExtHD/ rather than a user. I don't know anything about packages--I read the above on an earlier post and it got rid of the "No valid packages" error on Disk Utility when I first ran it. I don't know anything about receipts, etc. About the only thing I know is that I have two libraries, one for the main hard drive and one for the user.
    I'd like to keep this external drive as a bootable system. I want to be able to run Disk Utility to clean it up. Any suggestions?
    iMac G5, MacBook   Mac OS X (10.4.8)  
    iMac G5, MacBook   Mac OS X (10.4.8)  

    So I can do an archive and install, and then when the fresh Tiger is on there, would I upgrade to 10.4.8 right then? Then I suppose I copy all my backed up files to the correct user directories?
    How much memory do I need on that hard drive to archive and install? I'm assuming it archives on the same hard disk. Does that mean I have to have less than 1/2 of the memory used, so it can back itself up, or does it erase old data as it archives, freeing up memory space?
    Thanks for your input!

  • How do I get finder to recognize my hard drive after pulling my hard drive out without eject...? Is my hard drive dead? I see it in disk utility... Can I get my info back?

    I have a seagte back up plus. I pulled my hard drive out without ejecting it and now finder dosn't find it but I see it in disk utility (although I cant repair permissions) How do I get finder to recognize my hard drive after pulling my hard drive out without eject...? Is my hard drive dead? I see it in disk utility... Can I get my info back?
    Thank you so much for any help

    In Disk Utility you need to see a volume or partition in addition to the drive.
    If all you see is the drive, then when you ejected it you proably corrupted the volume or partition on the drive.
    If that is true then your chances of getting anything back are slim at best.
    About the only thing I know that might work not is to send the disk out to a service for recovery. This is going to cost like $$$$.
    Is the data worth that much?
    Allan

  • Errors in Disk Utility

    Hello. I was wondering for some opinions. i was having some problems with permission errors in disk utility so they wanted me to erase and install with a new disc set. So I completely erased the disc and reinstalled just the software on the mac os x discs. Now, after running typical software update and now I have 492 pages of permission errors. I ran it three times so far and it is still coming up with 492 errors on it.
    What could be causing this?

    Hi,
    *"i was having some problems with permission errors in disk utility so they wanted me to erase and install with a new disc set."*
    Who is they? Apple?
    You have 492 pages of permissions messages or 492 messages?
    It won't do any good to keep running it. Go here for information on permissions you can ignore. http://support.apple.com/kb/TS1448
    Carolyn

Maybe you are looking for

  • Windows 7 on iMac using Bootcamp**HELP**

    I've been trying to install Windows 7 on my 2011 iMac (i3 core). The internal superdrive no longer works - it only accepts CDs - when ever I insert a DVD it gets ejected after a few moments. This iMac is out of warranty and no AppleCare was ever purc

  • ActiveSync dead after update to 10.2.2.932

    I use my Q10 to sync with Tine20 groupware, which worked flawlessy until the rollout of the update to 10.2.2.932 for  Telekom Subscribers (D1, 262-01) network in germany, which was 2014/08/09 in my case. The device does not complain in any respect, i

  • Software Development Standards?

    hi, according to what software development standards (FDA, ISO, IEC 62305, ...) is the Oracle database (10g XE) developed - does anyone know? sorry, if this does not belong in this forum, but i couldn't find a better place... thanks, andrea

  • Help BAPI_MATERIAL_SAVEDATA !?!?

    Hi Friends, I've created a program that allow to change the <b>unit of measure</b> of a material master (add new  unit <b>USE</b>). But  wrong when I used BAPI  BAPI_MATERIAL_SAVEDATA to do it. The message error as below: "specify the conversion fact

  • Pricing In invoicing

    Hello, I have a scenario wherein , we do all the pricing in the sales order & it is copied all the wy through the billing. We have a requirement, where in we have to to determine some prices automatially in the invoice. Could we do addtional pricing