Issues with External Firewire Drive

I have a Lacie external 160G HD connected via Firewire to my multiple motherboard replacement Rev. A iMac G5. The drive worked fine until about a month ago, approximately the time I installed 10.4.6. It now can see the drive, I can open files on the drive, but cannot copy anything to or from the drive. It gives me a type 36 bad data message. I've run Disk Utility on it and the iMac and repair permissions. I also connected the drive to my Powerbook G4 and it works fine.
I contacted Mac support last night regarding this issue. Predictably, they suggestion I wipe the external and try it. If that fails, I reinstall the OS on the iMac. Obviously I'm hesistant to try either as a shot in the dark, and I think they're particularly dubious suggestions considering the drive is working fine on the Powerbook (which is also running 10.4.6.)
Any suggestions?

I think you need to call AppleCare again & carefully explain that the drive works fine with another Mac, & thus the advice to wipe the drive is inappropriate. If you still get resistance, politely but firmly ask to speak to the rep's superior. This usually will be a "Product Support Specialist" with more knowledge of proper troubleshooting procedures.
However, be aware that there may in fact be a problem with the iMac's install, so the advice to reinstall the OS is not unjustified. Also, Apple doesn't have to support third party devices by the terms of your AppleCare agreement, so concentrate on the fact that you have had multiple hardware replacement problems.
Running Apple Hardware Test might give you some indication of the problem's cause, so do that before calling again.

Similar Messages

  • Issues with External Hard Drives

    I hope this is the right forum for this one - please give me a steer if not! I've also posted it in 'Dock and Finder', but this forum seems equally appropriate, if not more so.
    I'm getting repeated issues with External Hard Drives, including ones that I have been using successfully for months/years, suddenly failing to mount and then becoming 'unknown device' through the firewire branch of 'About This Mac'.
    I've just bought a new hard drive on the grounds that the others had somehow failed, and the same problems are emerging. I decided to Repair Permissions on my iMac's internal drive, and am copying the results below, from repair runs conducted yesterday and today:
    YESTERDAY'S REPAIR PERMISSIONS RESULTS
    Verifying volume “Macintosh HD”
    Performing live verification.
    Checking Journaled HFS Plus volume.
    Checking Extents Overflow file.
    Checking Catalog file.
    Checking multi-linked files.
    Checking Catalog hierarchy.
    Checking Extended Attributes file.
    Checking volume bitmap.
    Checking volume information.
    The volume Macintosh HD appears to be OK.
    Repairing permissions for “Macintosh HD”
    Reading permissions database.
    Reading the permissions database can take several minutes.
    Permissions differ on "private/var/log/secure.log", should be -rw------- , they are -rw-r----- .
    Permissions differ on "Library/Preferences", should be drwxrwxr-x , they are drwxrwxrwx .
    Permissions differ on "Applications/Utilities/AirPort Utility.app/Contents/Resources/lanArrow.png", should be -rwxrwxr-x , they are -rw-rw-r-- .
    Permissions differ on "Applications/Utilities/AirPort Utility.app/Contents/Resources/lanCheck.png", should be -rwxrwxr-x , they are -rw-rw-r-- .
    Permissions differ on "Applications/Utilities/AirPort Utility.app/Contents/Resources/lanDisabled.png", should be -rwxrwxr-x , they are -rw-rw-r-- .
    Permissions differ on "Applications/Utilities/AirPort Utility.app/Contents/Resources/wanArrow.png", should be -rwxrwxr-x , they are -rw-rw-r-- .
    Permissions differ on "Applications/Utilities/AirPort Utility.app/Contents/Resources/wanCheck.png", should be -rwxrwxr-x , they are -rw-rw-r-- .
    Permissions differ on "Applications/Utilities/AirPort Utility.app/Contents/Resources/wanDisabled.png", should be -rwxrwxr-x , they are -rw-rw-r-- .
    Permissions differ on "Library/Application Support/Apple/ParentalControls/ALRHelperJobs", should be drwxrwxr-x , they are drwxr-xr-x .
    ACL found but not expected on "System/Library/User Template/English.lproj/Sites".
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/DVD.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/FRSettings.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/FRSources.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Movies.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Music.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Photos.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Podcasts.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/TV.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
    Permissions differ on "System/Library/PrivateFrameworks/BackRow.framework/Versions/A/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
    ACL found but not expected on "System/Library/User Template/English.lproj/Desktop".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Application Support".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Assistants".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Audio/MIDI Drivers".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Audio/Plug-Ins/Components".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Audio/Plug-Ins/Digidesign".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Audio/Plug-Ins/VST".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Audio/Plug-Ins".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Audio/Sounds/Alerts".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Audio/Sounds/Banks".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Audio/Sounds".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Audio".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/ColorPickers".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Compositions".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Favorites".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/FontCollections".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Fonts".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/iMovie/Plug-ins".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/iMovie/Sound Effects".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/iMovie".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Input Methods".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Internet Plug-Ins".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Keyboard Layouts".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Preferences".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Printers".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Screen Savers".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Sounds".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Voices".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library".
    ACL found but not expected on "System/Library/User Template/English.lproj/Movies".
    ACL found but not expected on "System/Library/User Template/English.lproj/Music".
    ACL found but not expected on "System/Library/User Template/English.lproj/Pictures".
    ACL found but not expected on "System/Library/User Template/English.lproj/Public".
    Permissions differ on "Applications/iTunes.app/Contents/CodeResources", should be -rw-rw-r-- , they are lrwxr-xr-x .
    Permissions differ on "Applications/iTunes.app/Contents/Frameworks/InternetUtilities.bundle/Contents/ CodeResources", should be -rw-rw-r-- , they are lrwxr-xr-x .
    Permissions differ on "Applications/iTunes.app/Contents/Resources/iTunesHelper.app/Contents/CodeResou rces", should be -rw-rw-r-- , they are lrwxr-xr-x .
    Permissions differ on "System/Library/LaunchDaemons/com.apple.usbmuxd.plist", should be -rw-r--r-- , they are -rwxr-xr-x .
    Warning: SUID file "System/Library/Filesystems/AppleShare/afpLoad" has been modified and will not be repaired.
    Warning: SUID file "System/Library/PrivateFrameworks/DiskManagement.framework/Versions/A/Resources /DiskManagementTool" has been modified and will not be repaired.
    Warning: SUID file "sbin/umount" has been modified and will not be repaired.
    Warning: SUID file "bin/rcp" has been modified and will not be repaired.
    Permissions differ on "Library/Application Support/Apple/ParentalControls/ContentFiltering", should be drwxrwxr-x , they are drwxr-xr-x .
    Permissions differ on "Library/Application Support/Apple/ParentalControls", should be drwxrwxr-x , they are drwxr-xr-x .
    Permissions differ on "System/Library/PrivateFrameworks/iLifeMediaBrowser.framework/Versions/A/CodeRe sources", should be -rw-r--r-- , they are lrwxr-xr-x .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/CodeResourc es", should be -rw-r--r-- , they are lrwxr-xr-x .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/BlackAndWhiteEffect.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/CubeTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/DissolveTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/DropletTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/FadeThroughBlackTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/FlipTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/MosaicFlipTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/MosaicFlipTransitionSmall.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/PageFlipTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/PushTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/RevealTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/SepiaEffect.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/TwirlTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/WipeTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
    Warning: SUID file "usr/bin/quota" has been modified and will not be repaired.
    Warning: SUID file "usr/bin/rlogin" has been modified and will not be repaired.
    Warning: SUID file "usr/bin/rsh" has been modified and will not be repaired.
    Permissions repair complete
    TODAY'S PERMISSIONS REPAIR RESULTS
    Repairing permissions for “Macintosh HD”
    Reading permissions database.
    Reading the permissions database can take several minutes.
    Permissions differ on "Library/Application Support/Apple/ParentalControls/ALRHelperJobs", should be drwxrwxr-x , they are drwxr-xr-x .
    ACL found but not expected on "System/Library/User Template/English.lproj/Sites".
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/DVD.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/FRSettings.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/FRSources.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Movies.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Music.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Photos.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Podcasts.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/TV.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/BackRow.framework/Versions/A/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    ACL found but not expected on "System/Library/User Template/English.lproj/Desktop".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Application Support".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Assistants".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Audio/MIDI Drivers".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Audio/Plug-Ins/Components".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Audio/Plug-Ins/Digidesign".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Audio/Plug-Ins/VST".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Audio/Plug-Ins".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Audio/Sounds/Alerts".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Audio/Sounds/Banks".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Audio/Sounds".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Audio".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/ColorPickers".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Compositions".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Favorites".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/FontCollections".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Fonts".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/iMovie/Plug-ins".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/iMovie/Sound Effects".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/iMovie".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Input Methods".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Internet Plug-Ins".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Keyboard Layouts".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Preferences".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Printers".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Screen Savers".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Sounds".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library/Voices".
    ACL found but not expected on "System/Library/User Template/English.lproj/Library".
    ACL found but not expected on "System/Library/User Template/English.lproj/Movies".
    ACL found but not expected on "System/Library/User Template/English.lproj/Music".
    ACL found but not expected on "System/Library/User Template/English.lproj/Pictures".
    ACL found but not expected on "System/Library/User Template/English.lproj/Public".
    Permissions differ on "Applications/iTunes.app/Contents/CodeResources", should be -rw-rw-r-- , they are lrw-rw-r-- .
    Permissions differ on "Applications/iTunes.app/Contents/Frameworks/InternetUtilities.bundle/Contents/ CodeResources", should be -rw-rw-r-- , they are lrw-rw-r-- .
    Permissions differ on "Applications/iTunes.app/Contents/Resources/iTunesHelper.app/Contents/CodeResou rces", should be -rw-rw-r-- , they are lrw-rw-r-- .
    Warning: SUID file "System/Library/Filesystems/AppleShare/afpLoad" has been modified and will not be repaired.
    Warning: SUID file "System/Library/PrivateFrameworks/DiskManagement.framework/Versions/A/Resources /DiskManagementTool" has been modified and will not be repaired.
    Warning: SUID file "sbin/umount" has been modified and will not be repaired.
    Warning: SUID file "bin/rcp" has been modified and will not be repaired.
    Permissions differ on "Library/Application Support/Apple/ParentalControls/ContentFiltering", should be drwxrwxr-x , they are drwxr-xr-x .
    Permissions differ on "Library/Application Support/Apple/ParentalControls", should be drwxrwxr-x , they are drwxr-xr-x .
    Permissions differ on "System/Library/PrivateFrameworks/iLifeMediaBrowser.framework/Versions/A/CodeRe sources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/CodeResourc es", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/BlackAndWhiteEffect.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/CubeTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/DissolveTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/DropletTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/FadeThroughBlackTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/FlipTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/MosaicFlipTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/MosaicFlipTransitionSmall.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/PageFlipTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/PushTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/RevealTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/SepiaEffect.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/TwirlTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/WipeTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Warning: SUID file "usr/bin/quota" has been modified and will not be repaired.
    Warning: SUID file "usr/bin/rlogin" has been modified and will not be repaired.
    Warning: SUID file "usr/bin/rsh" has been modified and will not be repaired.
    Permissions repair complete
    My concerns are:
    * Some of the permissions repaired yesterday appear to have needed to be repaired again today
    * There are several files which carry a warning that they won't be repaired as they have been 'modified', and some of these clearly relate to disk management.
    Does anyone have any ideas what is going on???
    Thanks!!

    Many problems with the 10.5.7 update have been fixed by a Restart.
    If that doesn't help, something may have gone wrong with the update. Download and install the "combo" update, from: http://support.apple.com/downloads/MacOS_X_10_5_7_ComboUpdate
    If that doesn't help, try running the Apple Hardware Test, on the disc that came with your computer.
    1. Disconnect all external devices (including the Ethernet cable) except the keyboard and mouse.
    2. Insert the "Additional Software & Apple Hardware Test" disc that came with your computer.
    3. Restart while holding down the "C" key. When the list of available startup volumes appears, click Apple Hardware Test and the right arrow.
    4. When the Apple Hardware Test main screen comes up (after a moment), follow the on screen instructions.
    5. If it detects a problem, an error code will be displayed. Make a note of it.

  • Post-Install Problem with External Firewire drive

    I just installed Tiger 10.4.3 and the computer would not reboot. It would stop prior to the Starting Mac OS X progress bar and gray out letting me know that the computer needs to restart.
    I finally got it to boot successfully by unplugging or turning orr my external Maxtor Firewire drive. The external drive was plugged during the install process (mistake?)
    Via Software upgrade, I upgraded to 10.4.6 in the hopes that this would solve the issue. No luck and when turning the drive on, it immediately goes right to the gray screen and lets me know it will need to reboot.
    Is this a known problem with a known solution? Did I FUBAR my drive somehow? Any suggestions for righting to ship?
    Thanks!
    Rob P

    OK, last one before dinner. I found the panic log. here is what it says:
    Description: Panic (system crashes) log
    Size: 12.39 KB
    Last Modified: 5/25/06 6:39 PM
    Location: /Library/Logs/panic.log
    Recent Contents: ...
    panic(cpu 0): 0x400 - Inst access
    Latest stack backtrace for cpu 0:
    Backtrace:
    0x000857F4 0x00085C24 0x000287B4 0x0008F6A8 0x000927B8
    Proceeding back via exception chain:
    Exception state (sv=0x24051780)
    PC=0x00000020; MSR=0x40009030; DAR=0x11F23B98; DSISR=0x40000000; LR=0x16FE0DEC; R1=0x1227BB90; XCP=0x00000010 (0x400 - Inst access)
    Backtrace:
    0x16FE0C58 0x16FE08DC 0x16FE043C 0x0021FFAC 0x0021FDA8 0x002206F8 0x00220D54 0x002111D0
    0x00211194
    Kernel loadable modules in backtrace (with dependencies):
    com.maxtor.iokit.IOFireWireMxBt(2.0d1)@0x16fdf000
    dependency: com.apple.iokit.IOFireWireFamily(1.4.0)@0x233d3000
    Exception state (sv=0x22F58A00)
    PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)
    Kernel version:
    Darwin Kernel Version 6.8:
    Wed Sep 10 15:20:55 PDT 2003; root:xnu/xnu-344.49.obj~2/RELEASE_PPC
    Does this help anyone???
    Rob P

  • Windows Easy Transfer (WET) Issues with External Hard Drive - "Can't read from the source file or disk"

    I work for Office Depot, in the tech department. Basically, one of our associates was supposed to do a data backup, and re-install Windows 7, then transfer the files back. He used Windows Easy Transfer and compacted everything into a 163 GB file. 
    Now comes the hard part. When we try to put it back on his computer ((drag-and-drop to the desktop) which has been wiped back to factory settings using the recovery partition), it stops at 79.5 GB remaining (you know how it doesn't give you a % of completion,
    it just shows how many GB are remaining) and then says "Can't read from the source file or disk" and gives you an option to try again, or cancel. It gets hung up on the same point each time.
    Normally, this wouldn't be a huge issue, but the contents on the drive are his wife's architect blueprints and interior design stuff, along with wedding photos, etc, which are the only copies they have. On top of those, they have court documents and other
    important files that we are unable to access now.
    I wasn't involved with this transfer, so I'm trying to clean up the mess as best I can. I remembered that the customer's wife was Russian, and had some files typed with a Russian keyboard, so on and so forth. I wonder if that's the issue? If not, I really
    have no idea how to manually extract things from a ".mig" file, or how to diagnose what area is potentially corrupted.
    In light of this situation, we tried using "Recuva" to recover the files post-wipe, but everything was corrupted or unable to be opened, and it also extracted and recovered all of the "useless" photos, such as the skype logos, up and
    down arrows for browsers, etc (it was 160,000+ photos).
    Trying to avoid a potential lawsuit, unhappy customer, and costing the company lots of money to see if professionals can get into this external hard drive.
    Other relevant information:
    We used a Toshiba 500 GB (465 GB) external hard drive.
    Customer's computer is an HP Pavilion P6000 Series (Model No. p6520y) running Windows 7 Home Premium 64-bit Service Pack 1.
    Any other information that is needed can be provided, thanks in advance, and hopefully we can find a solution to this issue quickly!
    -John

    I think there's a lack of understanding somewhere.
    "If you even can't start the process, please unplug it from your new PC. Then head back to your new computer and plug
    the external drive back in to your new computer. "
    Unplug from new, head back to new, plug it back in? That doesn't make much sense! Haha.
    I knew what you meant though, somewhat. When I search through the drives after clicking yes (Has windows easy transfer
    already saved your files blah blah blah) I click on the transfer file and it says "Windows Easy Transfer could not open the file".
    Rather than drag-and-drop the file to the desktop, I now tried to double-click on the file itself while it was plugged
    into the computer. It opened, and it started transferring until it was about 70% completed, and then an error popped up saying "WET can't open the easy transfer file, make sure your USB device is plugged in or check your internet connection". 
    I checked, and the USB hard drive's light wasn't on. Now, I unplug it and plug it back in, and the light comes back on,
    so I click Retry, and it resets the bar back to nothing and says "Transfer time: 1 minute".
    Rather than continue trying, I clicked "Cancel" instead of Retry, and it says "Your transfer did not complete successfully."
    It says to click "view report" for more information, but there's no "view report button".
    At the moment, I am scanning the External Drive for bad sectors using the check disk tool in properties. It's frozen
    at "0 USN bytes processed".

  • Issues with external hard drive

    hello, i recently purchased a seagate external hard drive 2TB. i am trying to copy videos onto the external hard drive from my macbook( mac osx version 10.6.3 but the files wont copy. i checked the details of the external hard drive, formatted for windows nt file system (NTFS). also, when i click info on the external hard drive and click on sharing and permissions it says "You can only read". What do i need to do to use the external hard drive with my mac. I should note that i want to interchange the external hard drive both with my mac and windows if possible. can anyone point me in the right direction... thanks

    Macs can't write to NTFS, only read. Here's a post with some background information on your problem if you really need to use this with Windows: http://discussions.apple.com/message.jspa?messageID=11547287 As you can see there's a few potential solutions. How big are these files? If under 4GB you could use FAT32. Note that sometimes file copying to and from FAT, especially large files, seems to be an issue I see not infrequently on these fora.
    If you don't need to use it with Windows, or can install software on the PC to allow it to read Mac drives, then format the drive to Mac Extended.
    [Kappy's extensive hard drive formatting post|http://discussions.apple.com/thread.jspa?messageID=8340551] - note that instructions at end are for zeroing data.
    Message was edited by: Limnos

  • FSCK and reboot issues with external USB drive

    I'm having an issue with an external USB hard drive I'm using.  I've always had issues with this drive cause my reboot to "freeze" when it's mounted.  Basically the system message with be sent out, but it doesn't actually proceed with the reboot.  No switch to init 6 or anything, but the shutdown process is still active.  I can continue to use the computer as usual, but I can't cancel the existing shutdown or try to enter init level 6 by hand.  So I just got around this by unmounting the drive before I shutdown.  However, lately when I try to unmount the drive I get an error saying that the drive is in use and I should check to see what processes are using it by runing lsof or fuser. 
    Yesterday I tried copying dsome files from the drive but there wasn't and activity on the drive. cp didn't report any errors though, it just sat there and did nothing.  I tried running fsck on the drive, but didn't get much farther.  I'll see some activity on the drive for about a second, then all activity stops and fsck just sits there. When I try to kill fsck, it won't.  Even with a kill -9. 
    I'm really confused as to what is going on.  Has anyone else had this problem?  Anyone have any ideas what could be causing all this or what I can do to stop this?  Thanks in advance!
    David
    [email protected]

    Press the reset button on the device. It is located between the USB and power ports. Make sure to take-out the external USB drive before you reset the device. Or you can also restore the defaults by accessing the Administration tab > Factory Defaults sub-tab in the router’s web-based setup page. Check out this link for the set up; http://www6.nohold.net/Cisco2/ukp.aspx?vw=1&docid=32cffead811249aea7e9fc6730bf59ad_KB25681_EN_v1.xml...

  • Permission issue with external hard drive

    Hi,
    I have an external hard drive that has a bunch of video and audio files on it. Any time I try to open any file from the drive, regardless of file type, the application it's supposed to open it says it can open. Most of the people I have talked to have said that it's a permission issue and have not had a solution for this. Looking for any suggestions on how to repair these permissions. Disk utility has been no help and when running recovery software like Data Rescue the files come out in the end with the same issues.
    Thanks.

    Drive was shot and could not rescue the information

  • Issues with external hard drive enclosure

    I've been having these issues with my external hard drive since I got it, it seems to be the enclosure
    These issues sometimes occur if the hard drive is off but plugged in
    -boot will stall after post, before grub
    -usb mouse won't work unless I unplug it and plug it back in
    -dmesg gives errors about failure to enumerate device
    -stalling at other points during boot (continues as soon as I unplug enclosure)
    And today, both windows and linux stopped detecting it properly
    dmesg said something about a read error.
    Then it started working again as suddenly as it started, when I unplugged it and plugged it back in.
    Does this sound like a deffective enclosure?

    R00KIE wrote:
    I'd say bad power supply (if it has an external power supply).
    Two external enclosures have done that to me already (but one is almost certain to do it while the other just started to do it recently), if the HD I have in the enclosure is a bit older (and noisier) I can even hear the HD spin down a little and spin up again, of course that whatever I was doing explodes in the process.
    Mind you that the HD is confirmed to be working properly by connecting it inside a desktop pc.
    I have couple other power adapters I can try. I got the same enclosure for my dad. I have a brick for a LaCie drive too. (I bought the lacie drive a year ago, but the power supply buzzed loudly. I put in a support request, but ended up returning the drive, and they sent me a new power after that)

  • Problem with external FireWire drive

    Two weeks ago I purchased a 1 tb Iomega ultra drive with FireWire 800/Firewire 400/USB 2/ESATA to use for back ups. I plugged it in the Firewire 800 port of my iMac. It worked fine until early this morning. I noticed there was a problem first because it was taking forever to log off or restart the computer with the drive connected and second that Time Machine had stopped doing backups a few hours previously and the drive was no longer recognized by OSX. I can plug it into a USB 2 port and it works fine. I have two Lacie drives daisy chained from the same Firewire 800 port - so the port is just fine. Thus it appears that the problem is with the Firewire 800 connection on the Iomega drive. Time Machine works with USB but I bought the drive for its flexibility. In future I might want use it as a bootable drive plus Firewire 800 is faster than USB 2. Any idea if this could be a software problem? I hate to return this drive since a) I would need to securely erase it first; b) I would have no time machine backup until I received a replacement (though I am doing less frequent conventional backups on 3 other drives (ie subsets of my files since none of the other drives are large enough for a single time machine backup plus I like redundancy); c) it is a pain to pack up and return.
    So my question is: should I bother or just live with USB 2 and hope that the FireWire problem does not mean the drive is a piece of junk and should not be trusted for anything?

    I called the store where I bought the drive and was told I have up to 30 days to return it. So I tried plugging it into the firewire 800 daisy chain (at the end) and now it's working again. So I will watch it closely over the next few days to see if this happens again within the 30 day return period. Also by registering online at the Iomega website, I now have 3 year warranty.
    Also from reading other threads about firewire issues, it appears that intermittent firewire problems may be more prevalent than I would expect (based on previous experience with a variety of firewire drives from many vendors).

  • Multiple (related?) issues with external hard drive connectivity

    Apologies if this has been discussed but I have been unable to find a solution or explanation after searching here and on other forums.
    I recently purchased an external hard drive (1TB Iomega Select Portable, bus powered, 2.5", USB 2.0). After formatting with two HFS+ partitions the device began disconnecting unexpectedly and afterwards was often not recognisable by my mac until I rebooted. I returned the product and had it replaced by another of the same model.
    The replacement external hard drive worked fine at first but hours later began showing the same symptoms. _It now connects briefly then a few seconds later disconnects._ Occasionally it seems to mount and work fine, but the problem always comes back. In the times when it is working, _Time Machine recognises the drive but only backs up at a rate of about 1KB/s!_
    _I don't know if this is a problem with the external hard drive, my USB ports, or settings on my mac._ Any advise you could offer would be greatly appreciated as I've run out of troubleshooting options with my limited knowledge of computers.
    _**Some tests I've done:_
    1) When it's not being recognised in Finder, it's also not recognised in either Disk Utility or System Profiler
    2) At one stage after repeatedly disconnecting, two other external hard drives and two thumb drives that I know work fine normally also failed to mount, but strangely two wireless mouse USB receivers worked fine. Both thumb drives were formatted as FAT32, one of the external hard drives had one HFS+ and one NTFS partition, and the other was entirely NTFS. When they weren't recognised in OS X, the two FAT32 drives and the NTFS partitions of the external hard drives were all recognised in Windows 7 via VMWare Fusion. After restarting the computer all of them now work on both Windows 7 and Mac OS X.
    3) I tried the external hard drive on another computer (a PC) and it was recognised in Vista's 'Disk Management' with both partitions marked as 'healthy', but it just called it 'Disk 1' rather than showing the names I'd given each partition.
    4) When I first started transferring files onto the drive I often got 'error code -36', but found a solution that seemed to fix that by deleting the '._' files from the source folder through Terminal.
    5) I've tried different USB cables, both USB ports on my mac, and also connecting with and without the secondary part of the 'y' cable that was supplied with it.
    Thanks very much,
    Andrew
    Message was edited by: andrewcarter

    I have the same problem with some 2.5 drives. My iMac on 10.5.8 sees the drive fine but my older 2007 Mac Book Pro 10.6.6 would not see it and now my new Mac Book Pro had problems seeing the drive from my old Mac Book Pro in that box. I had to use migration utility over the network that took 18 hours to copy my user over. I bought a new drive box and now the drive seems to work fine. I have ejected it a couple times and all seems well. I hope it continues to function properly.

  • HELP:  Sync Issues with External Hard Drive

    Since I have moved all my music to an external hard drive I am having issues syncing. My Next Gen Ipod syncs, but never gets rid of the syncing notification. I have to disconnect it and restart it. Also, when it syncs it leaves two copies of the songs on my library, one copy has the explanation mark on it. Can anyone help me stop this?

    R00KIE wrote:
    I'd say bad power supply (if it has an external power supply).
    Two external enclosures have done that to me already (but one is almost certain to do it while the other just started to do it recently), if the HD I have in the enclosure is a bit older (and noisier) I can even hear the HD spin down a little and spin up again, of course that whatever I was doing explodes in the process.
    Mind you that the HD is confirmed to be working properly by connecting it inside a desktop pc.
    I have couple other power adapters I can try. I got the same enclosure for my dad. I have a brick for a LaCie drive too. (I bought the lacie drive a year ago, but the power supply buzzed loudly. I put in a support request, but ended up returning the drive, and they sent me a new power after that)

  • Issues with external hard drive/airport utility with Windows PC

    Okay, here's my situation:
    I'm using the Airport Extreme and my network is currently laid out like this:
    1.) Macbook connected wirelessly
    2.) Windows XP SP2 PC w/ wired connection (ethernet)
    My problem is this:
    Just plugged in a brand new Western Digital hd to the usb port on the back of the Airport Extreme. My Macbook recognized it (had to use the shared disk password) and it works fine.
    But my Windows PC won't let me connect to the external hd or recognize it. Even when it asks me for the shared disk password, it tells me failed login or whatever. I installed the software (Bonjour/Airport Utility), but I'm confused on how to let my Windows PC find the hard drive or connect to it...
    I setup/configured my Airport Extreme on my Mac... am I suppose to configure my external hd's sharing abilities on my Windows PC using the Airport Utility, also?
    And when I open up the Base Station utility on my Windows PC, it continually keeps asking for my Base Station password as it tries to scan its configuration. Is that normal?
    Thanks
    PS: if you need more info regarding my problem, I'll be happy to supply it.
    MacBook 13 inch Mac OS X (10.4.8)

    R00KIE wrote:
    I'd say bad power supply (if it has an external power supply).
    Two external enclosures have done that to me already (but one is almost certain to do it while the other just started to do it recently), if the HD I have in the enclosure is a bit older (and noisier) I can even hear the HD spin down a little and spin up again, of course that whatever I was doing explodes in the process.
    Mind you that the HD is confirmed to be working properly by connecting it inside a desktop pc.
    I have couple other power adapters I can try. I got the same enclosure for my dad. I have a brick for a LaCie drive too. (I bought the lacie drive a year ago, but the power supply buzzed loudly. I put in a support request, but ended up returning the drive, and they sent me a new power after that)

  • 10.4.4 corrupts external Firewire drives

    I had now twice corruption with external firewire drives after a hardreset (not normal shutdown, but holding the powerbutton until the mac turns off).
    The first time I was forced to do this, because the whole Mac froze after a program run (not from Apple). At that time I had two external FW harddisks. One older 200GB Maxtor and one newer 250GB Maxtor, the newer one was backup, the old one master.
    Because at that time I thought the old harddisk might be bad, I bought another 250GB Maxtor same as the backup drive and synced (with rsync on the terminal) all data there. I tried to recover data before that, but Disk Utility completly failed, it just ejected the disk, same with DiskWarrior.
    Now, after another hard reset (Suddenly all programs locked up, and I couldn't do anything else) I had two corrupted. both the 250GB backup and the 250GB new master.
    Again Disk Utility failed, although it didn't eject the disk. DiskWarrior also failed to do anything. After I tried to repair it diskwarriro said it had an error. Then I could repair it with Disk Utility, but the luck was short. soon after I couldn't read some files, and then again I had the same errors on both disks.
    Right now I sync all my data from my master disk to the old 200GB Maxtor (which I reformated in between).
    I am just really scared if all hard resets will corrupt my external FW harddisks. I rely on them as I only have 40GB internal data. And what good does a backup do, if it also gets corrupted.
    Anybody with similar problems?
    Mac Mini   Mac OS X (10.4.4)  

    Yes, I have seen this twice now. It has happened to two of my external VFAT drives when used on the firewire port. The drives are in BYTECC firewire/usb chassis that use this Prolific device: 067b:3507 Prolific Technology, Inc.
    The drives mount fine once, but on dismount OS X trashes the VFAT boot sector. The drive will not remount on OS X after this happens. I have one mounted now in Linux, apparently on the backup copy of the partition table. The primary is completely blown away.
    The signature looks like this:
    from sector offset 0 on the disk:
    0x00000000 45 52 02 00 1d 38 63 80 | 00 00 00 00 00 00 00 00
    and all zeros down to 0x200.
    At 0x00000230 the ASCII string "Applepartitionmap" pops up.
    I don't see why this would be a vendor's driver problem.
    It's just another silly OS X firewire trick. Firewire has been a nightmare on my iMac G5, and it just keeps getting better.
    This happened once at 10.4.4 and again at 10.4.5, so falling back probably won't be worth it...
    Apple, have you tried regression testing the firewire disk drives? It's really uncool to detroy our data like this.
    There is no valid reason to write to any drive's partition table on exit unless specifically told to do so by me via the disk utility, so stop it already.
    iMac G5 20 Mac OS X (10.4)

  • Disappearing external Firewire drive.

    Hi friends.
    My wife's mini has a LaCie external firewire drive attached. She uses it with Backup and it just suddenly disappeared.
    It appears to be on and working- but not showing up on her desktop. Is there a way on restart-- to force her mini to look for peripherals it's not seeing? I always get such great help on this forum. Thanks in advance. Dan

    I'm curious if/how that link worked out for you. I have been observing problems with Firewire/USB for the past month or more that I allowed my clients to upgrade to 10.4.9 and 10.4.10.
    I am finally starting to cross over into the belief that an update within 10.4.9/10.4.10 caused a failure with external Firewire drives -- now I will include USB drives in that belief. I was skeptical for a long while but the coincidences don't line up.
    My guess is that Apple updated the Firewire/USB bridge -- perhaps they even made it more efficient. The cost may be that various external drive enclosure manufacturers who coexisted (or even accommodated) Apple's previous bridge, now fail. I don't know if you recall the 10.3.x update that took down Firewires for quite some time to come. The only solution that worked for me then was to boot into OS 9, mount the drive there, and then restart in OS X. A very round-about solution.
    So far, I have observed the following failures in the past couple months:
    Powerbook G4 1.4Ghz (or so): failed USB LaCie hard drive, no clicking/non-harddrive malfunction
    Mac Pro -- Intel Core Duo: two failed Firewire enclosures (Nexstar Vantecs). The drives inside were perfect but the enclosures ceased functioning first on an iMac G5 and then continued to disappear on a Mac Pro tower.
    One of these enclosures had also disappeared from a new iMac - Intel. I could get the thing to mount and then it would disappear overnight -- my thought is that perhaps the drives don't remount after sleep? I did not do extensive tests.
    I have had another client on an as-of-yet-unknown machine (purchased in last couple years) lose a LaCie Firewire drive... no clicks or hardware failure indications. I will investigate this week.
    I had yet another client lose two LaCie drives connected to a Dual 1.0 Ghz G4 Tower. One LaCie drive enclosure seemed to fail completely at Firewire 800 speed and transfer slowly but reliably when dumbed down to Firewire 400. The other LaCie was unreadable even when I transferred the drive to another enclosure. I am still investigating.
    On a Mac Mini (Intel) new enclosures from PPA Galaxy Metal Gear would not daisy chain without disappearing.
    I admit that I don't want to believe that the recent OS updates could have caused this -- especially after the debacle of 10.3.x. But it is definitely possible and not altogether unlikely. Consider this discussion about a LaCie firmware update tool meant to make them compatible: http://lovemac.org/2007/04/28/external-lacie-firewire-disappeared-from-the-deskh elp/
    Not having attempted the Firmware update yet myself, I cannot vouch for it. Firmware updates are not to be taken lightly but they are just the sort of thing that might make the Firewire/USB bridge in the LaCie's compatible with Apple's updates/fixes. Of course, that leaves the other vendors' drives high-and-dry.
    Usually, Apple or Apple defenders like to say that the vendors should be writing perfect code and it's not Apple's fault if they optimize or fix code which breaks the vendors' equipment. I think this is a ridiculous argument. Granted, in our legal system, Apple would not usually be obliged to accommodate "faulty" code (even if they might happen to have been the originators of it). But what is the true definition of faulty code? In the realm of technology and computers, there are likely countless kludges and fixes and patches. The whole idea and goal is FUNCTION (ideally). Optimizing or standardizing code is important of course. It means that future authors can rely on the accuracy of the previous authors. But the world -- especially the tech world -- stands to gain more from consistency... from the language of the vernacular. If all the equipment and all the operating systems up to a point have deigned to speak in a consistent kind of pidgin, then it doesn't make complete sense to "fix" it to be some more "accurate" or "refined" grammar. Language works because it's locally consistent, not because it's accurate to some holy grail of grammar.
    Specifically: Apple can't switch code midstream and say "oh, I made the code 'accurate,' not my fault if your stuff was built on bad code." Up until that point THEIR stuff was built on "bad" code too! It's a ridiculous argument but what can you do.
    At this point, I imagine that Apple attempted to fix something with 10.4.9 and 10.4.10 that it had tried to fix before with OS 10.3.X. Instead, I believe it created an intermittent failure in Firewire/USB drives that leaves the drives inoperable as often as unmountable. It's just a theory based on having seen enough updates and upgrades have a really bad effect. I think people think we live in some future where we can trust our technology and tech manufacturers to get things right (or at least get things right often enough). Surely they're doing the best they can...no doubt.
    I'm a little frustrated I should ramp down my expectations. I know. It's not like this is 2020 or 2050. It's really only 2007.
    Good luck to us all.

  • External Firewire Drive Has Now Showing mounting with Intilize

    i have a seagate 1tb external firewire drive. its been working and has about 500gigs of info on it. today it is showing up as a unformatted drive. disk warrior is not seeing it. is there another program that could repair maybe tech tool or any other suggestions
    thanks

    If Disk Warrior won't see it.....ouch.
    Data Rescue II is good, but again, if DW won't see, it might be toast, sorry.
    As well, here is Apple doc.#88338 on getting FireWire to work.
    http://support.apple.com/kb/HT1317?viewlocale=en_US
    ...perhaps it is a bus issue and the drive itself is ok. Do you have another computer/cable etc. to test it with...

Maybe you are looking for