11 Replies Latest reply: May 4, 2011 3:22 AM by danfromlutherville
danfromlutherville Level 1 (0 points)

I have a Power Mac G5 with two internal hard drives. I recently started having problems with the machine crashing and getting messages on restart that "the disk you inserted was not readable by this computer". Eventually, the second hard disk stopped showing up at all and would not show up when I tried Disk Utility, R-Studio or Disk Warrior.

 

After the hard drive stopped mounting the error messages stopped and I thought the problem was with the drive. I removed the drive and sent it off for data retrieval and bought a new Seagate Barracuda 1TB drive.

 

I installed the new drive and upon restarting the machine crashed again. I was able to bring it up and using Disk Utility partition the new drive but whenever I restart I still get the "The disk you inserted was not readable by this computer" screen with options to Ignore or Eject.

 

The partitions appear on my desktop as I named them but now I'm wondering if it's not a drive issue but maybe an issue with the connections to that drive bay. Should I replace the cables with the ones that came with the drive?

 

Any help would be greatly appreciated.


PowerMac, Mac OS X (10.4.11)
  • BDAqua Level 10 (122,252 points)

    Open Console in Applications>Otilities, check the sytem log for the date/time of the last  of the last bootup, look for clues.

     

    Highlight the Driv then it's Partitions in Disk Utility and click on the blue Info icon.

  • lostinthesound Level 1 (65 points)

    Forgive the dumb question, but did you reinstall your OS from scratch after you installed the new drive? If so and you're still having issues, I would contact Apple support prior to replacing any cables just to err on the side of caution.

  • danfromlutherville Level 1 (0 points)

    Thanks... have never even used that utility. Here's what I get... anything jump out about those kernel extensions?

     

    Mac OS X Version 10.4.11 (Build 8S165)

    2011-05-03 14:38:09 -0400

    2011-05-03 14:38:10.173 HPEventHandler[128]: DebugAssert: Third Party Client: (NULL != m_lock && 0 == errno)  Can't create semaphore lock[/Volumes/Development/Projects/mac-software/mac-software/components/HPEvent Handler/Sources/Core/HPTMNotificationManager.cpp:62]

    2011-05-03 14:38:11.745 SystemUIServer[105] lang is:en

    Workaround Bonjour: Unknown error: 0

    May  3 15:09:37 dan-taylors-power-mac-g5 kextd[25]: cannot resolve dependencies for kernel extension /System/Library/Extensions/Seagate Storage Driver.kext/Contents/PlugIns/SeagateLeafPowSecDriver_10_5.kext

    May  3 15:09:37 dan-taylors-power-mac-g5 kextd[25]: cannot resolve dependencies for kernel extension /System/Library/Extensions/Seagate Storage Driver.kext/Contents/PlugIns/SeagateLeafPowSecDriver_10_5.kext

    2011-05-03 15:12:59.516 QuarkXPress[266] No Offer is available for "com.quark.quarkxpress:8:XPR3"

  • danfromlutherville Level 1 (0 points)

    No, I'm just using it as a storage/backup drive so I'm not installing OSX on it. (And there are no dumb questions!) Thanks for the input.

  • BDAqua Level 10 (122,252 points)

    Dod you install some Seagate Software?

     

    Is that a "Green" drive?

     

    Try a Safe Boot from the HD, (holding Shift key down at bootup),  it will try to repair your Disk Directory while the spinning radian is happening, so let it go, run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions.

     

    Do you get the error with a Safe Boot?

  • danfromlutherville Level 1 (0 points)

    No, it's not a green drive nor did I install any Seagate software. The disc that came with it appears to only have software that will run on a PC.

     

    I tried a safe boot, reapired permissions and verified my boot up drive. Still get the same error.

  • danfromlutherville Level 1 (0 points)

    I went into System > Library > Extensions and found something called Seagate Storage Driver.kext, deleted it from the folder, emptied the trash and restarted... and didn't get the error message.

     

    Does that make sense?

  • BDAqua Level 10 (122,252 points)

    Yes, it makes sense, I believe the Seagate SW was/is the problem, does it have a complete Uninstaller?

     

    Seems something installed it, did you install any Backup SW? Could it have been installed in the past?

  • old comm guy Level 4 (2,240 points)

    danfromlutherville wrote:

     

    I went into System > Library > Extensions and found something called Seagate Storage Driver.kext, deleted it from the folder, emptied the trash and restarted... and didn't get the error message.

     

    Does that make sense?

     

    Actually, it does, in another possible vein.  Peek now in your /System/Library folder and look at the modification times for these two files:

     

    Extensions.mkext

    Extensions.kextcache

     

    My guess is that they will have the about same mod time as when you restarted (as will the Extensions folder).  At boot, if the mod time on the Extensions folder is later than the mod time on those files (which it would have been after you trashed the file), they are supposed to be rebuilt.  Otherwise, they will be used to load kexts as needed by the system, which is how you get a (sometimes) damaged kext loaded.  Usually it causes more catastrophic problems, but sometimes it may be a kext that is just incompatible for whatever reason, and you get strange but not catastrophic behavior.

     

    More MacOS voodoo.

  • danfromlutherville Level 1 (0 points)

    No, I didn't install any backup software and I don't ever recall installing any Seagate SW, though I believe my boot drive is Seagate as was the drive I just sent off for data recovery. I don't see a complete uninstaller on their disc but I'll check their site.

     

    Thanks for the input... it has been VERY helpful!

  • danfromlutherville Level 1 (0 points)

    I checked those files and yes, they have the same mod time as the Extensions folder from right about when I restarted. First time I've run into any Extensions issues with OSX ... I appreciate the input.