Fantom 500GB USP 2.0 won't mount

I plugged the drive into a friend's Core Duo machine, it worked fine.
I plugged it into mine, which is an Intel Core 2, and it would not mount (not showing up on the desktop, Finder, or DU)
After that, it won't mount to ANYTHING, including PC.
Does anyone have any solutions/advice? I've got a ton of valuable stuff on this drive that I can't afford to lose.
Thanks!

Per here:
http://libiphone.lighthouseapp.com/proj … ion-failed
Add a --without-swig to the ./configure and it should work...

Similar Messages

  • USB LaCie Porche 500gb usb external drive won't mount

    Here is the scoop.
    A few days ago I was using my LaCie 500gb external drive and the usb chord was accidently yanked out whilst adding a photo to iphoto.
    So i thought uh oh better close everything disconnect wait a while then restart.
    So I did...plugged it back in...it made all the normal start up noises little amber light came on but it didn't appear on the desktop..nor in disk utility. But it did appear in system profiler.
    Yesterday after resetting the "pram" or whatever it is that happens when you hold p + r + the apple key and alt....or ctrl and still no relief.
    So i leave it plugged in over night to see if it is merely slow for some reason. When i awake this morning it is in disk utility even with the "time machine" volume...so presumably all the files are more or less still intact. But it still isn't mounting. So after clicking repair disk ....three or more hours later i get this in the log
    2008-07-18 10:07:22 +0100: Verify and Repair volume “Time Machine Backups”
    Starting repair tool: 2008-07-18 10:07:22 +0100
    2008-07-18 10:07:22 +0100: Checking Journaled HFS Plus volume.
    2008-07-18 10:07:22 +0100: Detected a case-sensitive catalog.
    2008-07-18 10:07:22 +0100: Checking Extents Overflow file.
    2008-07-18 10:07:22 +0100: Checking Catalog file.
    2008-07-18 10:14:21 +0100: Checking multi-linked files.
    2008-07-18 10:23:17 +0100: Checking Catalog hierarchy.
    2008-07-18 10:42:25 +0100: Checking Extended Attributes file.
    2008-07-18 10:42:46 +0100: Invalid sibling link
    2008-07-18 10:42:46 +0100: Repairing volume.
    2008-07-18 10:42:46 +0100: Rechecking volume.
    2008-07-18 10:42:46 +0100: Checking Journaled HFS Plus volume.
    2008-07-18 10:42:46 +0100: Detected a case-sensitive catalog.
    2008-07-18 10:42:46 +0100: Checking Extents Overflow file.
    2008-07-18 10:42:46 +0100: Checking Catalog file.
    2008-07-18 10:49:46 +0100: Checking multi-linked files.
    2008-07-18 10:58:37 +0100: Checking Catalog hierarchy.
    2008-07-18 11:17:59 +0100: Checking Extended Attributes file.
    2008-07-18 11:18:20 +0100: Invalid sibling link
    2008-07-18 11:18:20 +0100: Repairing volume.
    2008-07-18 11:18:20 +0100: Rechecking volume.
    2008-07-18 11:18:20 +0100: Checking Journaled HFS Plus volume.
    2008-07-18 11:18:20 +0100: Detected a case-sensitive catalog.
    2008-07-18 11:18:20 +0100: Checking Extents Overflow file.
    2008-07-18 11:18:20 +0100: Checking Catalog file.
    2008-07-18 11:25:15 +0100: Checking multi-linked files.
    2008-07-18 11:34:06 +0100: Checking Catalog hierarchy.
    2008-07-18 11:53:38 +0100: Checking Extended Attributes file.
    2008-07-18 11:54:01 +0100: Invalid sibling link
    2008-07-18 11:54:01 +0100: Repairing volume.
    2008-07-18 11:54:01 +0100: Rechecking volume.
    2008-07-18 11:54:01 +0100: Checking Journaled HFS Plus volume.
    2008-07-18 11:54:01 +0100: Detected a case-sensitive catalog.
    2008-07-18 11:54:01 +0100: Checking Extents Overflow file.
    2008-07-18 11:54:01 +0100: Checking Catalog file.
    2008-07-18 12:01:19 +0100: Checking multi-linked files.
    2008-07-18 12:10:29 +0100: Checking Catalog hierarchy.
    2008-07-18 12:28:25 +0100: Checking Extended Attributes file.
    2008-07-18 12:28:46 +0100: Invalid sibling link
    2008-07-18 12:28:46 +0100: 2008-07-18 12:28:46 +0100: The volume Time Machine Backups could not be repaired after 3 attempts.
    it would appear that the problem is "invalid sibling link"
    Any ideas people.

    nonononon...
    Every tech will offer to reformat the HDD or suggest its broken.
    The table of contents are corrupted.
    What I do is remove the drive from the case and put it in a PC and run "mac drive" software then choose repair volume and your good to go.
    Iv done this as a PC tech for several of my mac customers.
    But for the life of me I cant appear to reproduce the issue and don't know what the issue is.
    Several macbook guys have given me their "broken" USB drive and the TOS is corrupted. Its really a royal pain in the back side.
    What is the issue, how to make it stop?

  • Fantom external hard drive won't mount

    I am using an imac G3 with OS 10.3.9. Until yesterday my Fantom external hard drive mounted. I dismounted it and turned it off. I went to turn it back on later and it won't mount. I selected initialize from the dialogue box that says it won't mount and when disk utility comes up it show the two icons for the internal hard drive and just one for the external so I can't do anything with it. Thanks for your help.
    imac Mac OS X (10.3.9)
    imac Mac OS X (10.3.9)
    imac   Mac OS X (10.3.9)  

    Thought you could use this info about getting FireWire to work!
    First, you should always Repair Permissions in Disk Utility before and after any update; I would do that now. If you installed your update with FireWire plugged in, your Mac may not recognize it anymore.
    Try resetting your FireWire ports by disconnecting all FW devices, shut down your Mac and unplug it from AC power (wall socket) for 30 minutes. plug it back in and try FW.
    If that did'nt work, download the combo update from this site (yours may be corrupt), not Software Update, disconnect all firewire + USB devices except keyboard + mouse, Repair Permissions, re-install update, Repair Permissions again + try. Yours is the 10.3.9 Combo update. Others reading, download the Combo that applies to your system.
    If that still did'nt get it Zap the PRAM. While restarting Mac hold down the following key combo Command-Option-P-R. Keep holding those keys down till you hear the second start-up chime, then release.
    For those of you with Macs that are not PowerBooks or iBooks, a bad internal battery can cause FireWire to not be recognized, so make sure it's good!
    Good Luck!
    Cheers!
    DALE
    p.s. Hi to you too Sherry! Keep up the good work!

  • My external hard drive (G-DRIVE Slim 500GB) won't mount?

    My external hard drive (G-DRIVE Slim 500GB) won't mount?
    All of a sudden my hard drive didn't show up in my finder. I checked in disk utility and it was there but greyed out. If I tried mounting it told me that could not be mounted and that I should try 1st aid.
    When I try to verify disk I get a message to tell me that the disk needs to be repaired with the information shown below.
    Verifying volume “G-DRIVE slim”
    Checking file systemChecking 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.
    The volume G-DRIVE slim could not be verified completely.
    Error: This disk needs to be repaired. Click Repair Disk.
    When I perfrom the disk repair it tells me that the disk cannot be repaired and I should back up as much of my files as possible, reformant the disk, and restore my backed up files. The information shown is below:
    Verify and Repair volume “G-DRIVE slim”
    Checking file systemChecking 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.
    The volume G-DRIVE slim could not be verified completely.
    Volume repair complete.Updating boot support partitions for the volume as required.Error: Disk Utility can’t repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.
    When I try the same thing on another Mac Book Pro I have the same situation but it tells me the disk is ok and still won't mount after.
    I'm not sure what to do..........

    You need to make your own decision on which to purchase.  Read up on them on their websites because each do something a little different.
    Techtool Pro
    DiskWarrior (Highly Recommended for Directory Damage Repair)

  • 500GB Seagate drive in an external FW enclosure won't mount

    Hi-
    I have the latest MacPro with one internal HD 250 GB. I found a great deal on a an ATA drive by Seagate 500GB and bought an external FW enclosure, as I've done many times in the past with smaller drives 160GB, 40GB and so on.
    I connected everything and it won't mount. This case says it will handle larger drive sizes. I swapped an older drive from another case and it worked fine. Is there a step I'm missing, or do I have a bad drive?
    I'm want to use the 500Gb for FCE editing.
    Thanks,
    Anne Z

    Unfortunately, all cases are not made equal. Depending on the chipset used in the external case, it may not be compatible with your 500GB drive. Some chipsets can not handle that big of a drive. I have one firewire drive that can't handle a 250GB drive, but it can a 200GB drive. This seems to be your case since you are able to put a smaller drive in the case and it works. You might want to see if you can return the case and find one that specifically states it can handle a 500GB drive.
    Glor

  • External drive won't mount. Options?

    Hi everyone. I've used a LaCie 250GB D2 external hard drive for a little over two years with no problems. A few days ago, I bought a Western Digital 500GB drive to serve as my main external drive, so I decided to erase and reformat the LaCie drive, which I had previously partitioned into two volumes, to serve as an archive drive.
    That's where my trouble started.
    I deleted all my files off the drive and then selected Erase in Disk Utility. I checked the option to eight way random write over format the disk for increased security, but that seemed to be taking so long I just quit Disk Utility. I figured since I didn't have any data I was afraid of losing, it wouldn't be a problem.
    The next day I tried to erase it again, but I got an error message that said something about my partition (sorry but I can't recall what the message was; at this point I still didn't think there would be any problem).
    Yesterday night, I tried again to erase and reformat the disk. I selected the option to zero all data because I thought that might solve any hard-to-fix problems. I left Disk Utility running overnight and all day today--about 20 hours in all-- but the progress bar showed no progress. None.
    Now, as of this evening, I can't get the drive to mount at all. When I plug the drive in (and I've tried all three interfaces), the blue activity light starts blinking and I can hear it spin for a little while. It eventually stops spinning but the light keeps blinking.
    I've tried unplugging the drive and plugging it back in. Nothing. I own DiskWarrior, but as far as I can tell there's nothing DiskWarrior can do if the drive won't mount.
    I'm wondering if disconnected the drive while it was running could have caused this problem. I might have done that inadvertently when it was taking so long to format. I figured that might result in loss of data, but I wouldn't think it would render a drive completely non functional.
    I'm guessing the problem is probably a failure of the drive, but the fact that this only cropped up when I tried to reformat it seems suspicious to me.
    If anyone has any suggestions for ways to get the drive to mount or format it, I'd sincerely appreciate hearing them. Thanks.

    Thanks for quick reply. Boy, I really screwed up. I guess I didn't think I could permanently ruin a drive that way. I just assumed as long as the drive could spin and wasn't going bad, you could always reformat it.
    Just so you know, I let my iBook run untouched for literally 20 hours in the zero out erase mode, but the progress bar showed no progress at all, so I think the drive must have already been broken by that point. I was prepared for it to take a day or more, but with no visible progress in 20 hours it would have taken weeks.

  • External Firewire drives power up, but won't mount.

    I wanted to see if anyone else is having this problem. I recently upgraded my mom's laptop to OSX Lion after she experienced a lot of problems with Snow Leopard. All updates available from Software Update have been installed. Now 2 issues have arisen after the new install: 1) the FW 800 and 400 ports appear to be non-functional, and 2) the OS takes about 10 minutes to boot up to the desktop.
    1) Regarding the FW ports: I have a couple external Firewire 800 hard drives that I use on other Macs so I know they're fully operational and mount without any issues. They're both 5400RPM drives that have been inserted into Macally external enclosures, and are of different capacities - one is 320GB and the other is 500GB. The enclosures offer FW 800, 400, USB 2.0 and mini-USB connectivity. But after upgrading the laptop I mentioned, neither of the drives will mount when using the FW 800 or 400 cables. They power up but won't mount, and they don't show up in the list in Disk Utility. However, the drives will power up and mount via USB.
    I realize the laptop may have a hardware/port problem - but both 800 and 400 ports? Seems unlikely.
    2) Any idea why it's taking the OS 10 minutes to boot up? I've shut down the laptop and rebooted it twice since the OS install, and both times took 10 minutes.
    I may just install Lion on one of the hard drives, pull it and then pop it into the laptop to see if that makes any difference. Before I do that, can anyone recommend a hardware utility that can check the ports?
    I welcome your suggestions.
    Thank you.

    Thanks for responding. Here's the info you requested. I'm not a systems guy so hopefully I've pasted in something that helps.
    system.log report, after searching BOOT_TIME, here's one of the timestamps:
    May 25 22:04:58 localhost bootlog[0]: BOOT_TIME 1337997898 0
    Here's a chunk of the log after that timestamp:
    May 25 22:05:00 localhost com.apple.launchd[1]: *** launchd[1] has started up. ***
    May 25 22:05:13 localhost com.apple.launchd[1] (com.apple.powerd): Unknown value for key POSIXSpawnType: Interactive
    May 25 22:05:13 localhost com.apple.launchd[1] (com.apple.sandboxd): Unknown value for key POSIXSpawnType: Interactive
    May 25 22:05:18 localhost com.apple.pfctl[34]: No ALTQ support in kernel
    May 25 22:05:18 localhost com.apple.pfctl[34]: ALTQ related functions disabled
    May 25 22:05:18 localhost UserEventAgent[11]: starting CaptiveNetworkSupport as SystemEventAgent built May 25 2011 12:27:35
    May 25 22:05:18 localhost UserEventAgent[11]: CaptiveNetworkSupport:CaptiveSCCopyWiFiDevices:388 WiFi Device Name == NULL
    May 25 22:05:19 localhost com.apple.ucupdate.plist[28]: ucupdate: Checked 1 update, no match found.
    May 25 22:06:14 localhost configd[14]: InterfaceNamer: timed out waiting for IOKit to quiesce
    May 25 22:06:14 localhost configd[14]: Busy services :
    May 25 22:06:14 localhost configd[14]:   MacBookPro3,1 [76967, 4375662836 ms]
    May 25 22:06:15 localhost mDNSResponder[37]: mDNSResponder mDNSResponder-320.16 (Mar 17 2012 21:31:16) starting OSXVers 11
    May 25 22:06:15 localhost com.apple.locationd[40]: ERROR,Time,359690775.485,Function,"_Apple80211* CLWifiService::createApple80211()",Apple80211GetIfListCopy failed, error -3903 (Unknown error: -3903)
    May 25 22:06:15 localhost com.apple.locationd[40]: STACK,Time,359690775.485,1   locationd                           0x00000001077fe583 locationd + 624003
    May 25 22:06:15 localhost com.apple.locationd[40]: STACK,Time,359690775.485,2   locationd                           0x00000001077fe719 locationd + 624409
    May 25 22:06:15 localhost com.apple.locationd[40]: STACK,Time,359690775.485,3   libdispatch.dylib                   0x00007fff85f46c79 _dispatch_barrier_sync_f_invoke + 33
    May 25 22:06:15 localhost com.apple.locationd[40]: STACK,Time,359690775.485,4   locationd                           0x00000001077fe9b0 locationd + 625072
    May 25 22:06:15 localhost com.apple.locationd[40]: STACK,Time,359690775.485,5   locationd                           0x00000001077fea10 locationd + 625168
    May 25 22:06:15 localhost com.apple.locationd[40]: STACK,Time,359690775.485,6   libsystem_c.dylib                   0x00007fff85e96e06 pthread_once + 86
    May 25 22:06:15 localhost com.apple.locationd[40]: STACK,Time,359690775.485,7   locationd                           0x00000001077fea47 locationd + 625223
    May 25 22:06:15 localhost com.apple.locationd[40]: STACK,Time,359690775.485,8   locationd                           0x00000001077f33ac locationd + 578476
    May 25 22:06:15 localhost com.apple.locationd[40]: STACK,Time,359690775.485,9   locationd                           0x00000001077f353f locationd + 578879
    May 25 22:06:15 localhost com.apple.locationd[40]: STACK,Time,359690775.485,10  libsystem_c.dylib                   0x00007fff85e96e06 pthread_once + 86
    May 25 22:06:15 localhost com.apple.locationd[40]: STACK,Time,359690775.485,11  locationd                           0x00000001077f3509 locationd + 578825
    May 25 22:06:15 localhost com.apple.locationd[40]: STACK,Time,359690775.485,12  locationd                           0x00000001077b052a locationd + 304426
    May 25 22:06:15 localhost com.apple.locationd[40]: STACK,Time,359690775.485,13  locationd                           0x0000000107791653 locationd + 177747
    May 25 22:06:15 localhost com.apple.locationd[40]: STACK,Time,359690775.485,14  locationd                           0x0000000107791a08 locationd + 178696
    May 25 22:06:15 localhost com.apple.locationd[40]: STACK,Time,359690775.485,15  locationd                           0x00000001077921b2 locationd + 180658
    May 25 22:06:15 localhost com.apple.locationd[40]: STACK,Time,359690775.485,16  locationd                           0x00000001077c332c locationd + 381740
    May 25 22:06:15 localhost com.apple.locationd[40]: STACK,Time,359690775.485,17  locationd                           0x0000000107767fd8 locationd + 8152
    May 25 22:06:15 localhost com.apple.locationd[40]: STACK,Time,359690775.485,18  ???                                 0x0000000000000001 0x0 + 1
    May 25 22:06:15 localhost com.apple.usbmuxd[27]: usbmuxd-268.5 on Jan  5 2012 at 03:34:01, running 64 bit
    May 25 22:06:15 localhost UserEventAgent[11]: CaptiveNetworkSupport:CaptiveSCCopyWiFiDevices:388 WiFi Device Name == NULL
    May 25 22:06:15 localhost UserEventAgent[11]: ServermgrdRegistration cannot load config data
    May 25 22:06:15 localhost UserEventAgent[11]: get_backup_share_points no AFP
    May 25 22:06:15 localhost systemkeychain[59]: done file: /var/run/systemkeychaincheck.done
    May 25 22:06:15 localhost configd[14]: ioctl(SIOCGIFCAP) failed: Device not configured
    May 25 22:06:16: --- last message repeated 1 time ---
    May 25 22:06:16 localhost mDNSResponder[37]: D2D_IPC: Loaded
    May 25 22:06:16 localhost mDNSResponder[37]: D2DInitialize succeeded
    If you want me to post the kernal log, I can do that next if nothing in here points anyone in the right direction. FYI - the system booted normally this morning after shutting it down overnight.

  • Drive Suddenly Won't Mount

    I've had a 500GB Seagate external drive connected via firewire for my Time Machine for awhile now. I've used time machine with it to recover files, it always mounted and ejected fine, never had any problems, etc.
    Today, all of a sudden, it won't mount. The weird part is the drive is operating. Something is writing to it - it's write light is blinking and I can hear it working. Still won't mount. I tried it on a different mac, same deal. It shows up in Disk Utility, but all of the buttons are grayed out. I can't verify or repair it. When I try to erase the drive via Disk Utility, it says it failed because "Resource Busy". Time machine is not writing to it. What the **** could be writing to it without me knowing?!
    Anyone experience this before?

    For some reason, with my WD 160GB drive, when I plug it in and it turns on, but it never mounts. I have to go into disk utility and wait, and wait, and wait, until it shows up in disk utility (a few minutes) then I have to select the drive and click on mount. It started doing this within the past few months. I have no idea why, but it's a pain.

  • External Backup Disk Suddenly Won't Mount...

    Tried to shut down, restart and repair the disk with Disk Utility...but it won't mount. Any suggestions? It's a WD 500GB external backup disk...I use it for Time Machine.
    Thanks!

    The only other thing that I can suggest at this point is to turn Time Machine off and try reseting the partition map scheme +(GUID Partition Table)+ and the format +(Mac OS Extended)+ again to see if it repairs the drive. Unfortunately that will erase all of your previous TM backups, but might get the drive working correctly again. Then if and when you get the drive working correctly go to the Time Machine Preference and reselect the drive to Use for Backup.

  • FireWire drives won't mount

    Neither of my FireWire drives will mount on either my iMac 20" G5 or my iBook G4...I have a 500GB WD MyBook and a La Cie 80G. I've gone through all the suggested tips, and still nothing. I've reset the PRAM several times, reset the firewire bus by turning off the computer and unplugging it and the drives for a while, etc. I've tried different cables, too.
    The drive shows up in the system profiler as an unknown device but not in the Finder. I have a USB hub with a card reader and 4G SD card that shows up just fine. I tried the MyBook in the USB port but it didn't show up there either.
    The power supplies are working, as the indicator lights are on for both drives.
    The MyBook was working fine until recently; not sure when it stopped working. I hadn't used the La Cie for a while but hooked it up to store iMovie files.
    I plugged a Canopus ADVC-55 analog-to-digital convert into the FW port on both computers and it showed up as a named device in System Profiler. That tells me the port is OK and the problem is with the HDs--right?
    Very frustrating! Hope someone can help.
    Thanks in advance.

    For what it's worth... I'm having the exact same issue and so are many others on the forums since 10.5.6.
    See:
    http://discussions.apple.com/thread.jspa?messageID=9206734
    http://discussions.apple.com/thread.jspa?messageID=9206635
    http://discussions.apple.com/thread.jspa?messageID=9043830
    http://discussions.apple.com/thread.jspa?messageID=8917764
    ---cross posted---
    I'm having a very similar issue as of the last few weeks at least. Periodically I'll turn my FW drive on and it won't mount and isn't visible in Disk Utility. This is usually after waking the computer from sleep.
    The only way to get it back is to restart.
    Also the console shows a long running list of errors that seem to occur non-stop when the drive is on, connected, but not mounting.
    AppleFWOHCI_AsyncTransmit::waitForDMA
    AppleFWOHCI_AsyncReceive::waitForDMA
    I've also noticed that the system occasionally will not boot up and instead freezes on the Apple logo on startup. Not sure if this is related however.
    ---

  • 2TB Western Digital Drive won't mount in my Mac Pro. Please Help

    Hello, everyone. I have a Mac Pro (MacPro1,1) with an internal drive that won't mount. I bought it used last year with 12GB RAM and 1TB hard drive and SuperDrive. I have since upgraded storage with an internal 2TB drive from Seagate (no problem), and a 500GB drive (no problem) from Western Digital, and installed a second optical drive from an old Power Mac G5. I had an additional newer 2TB drive from WD that I bought as an external. I took it out of its case and put it in a carrier and then in Bay 4 of my Mac Pro. It's the only drive I've had problems with, and I don't know why. The drive is immediately rejected by OS X upon startup. The options include "Eject" and "Initialize..." but I've clicked initialize every time. Disk Utility opens and I can see the drive but for whatever reason, it will not mount. There is one partition on it, and I think when I bought it, I formatted it with GUID and Mac OS Extended (Journaled). I haven't used it as a Time Machine drive, but I've backed up some files on it. I've restarted several times, and I'm not sure if I can hear it spinning inside my computer.
    Should I pull it out and see if the partition is still on the disk? Wha

    When DU launches or launch it yourself, that is the most useless "eject, ignore" and there is no real initialize command anyway anymore.... Click on raw drive WDxxxx and goto Partition tab, change the number of partitions to anything (another silly item) so you can go to the Advanced Options finally
    WD MyBook drives are often not standard SATA drives with power and data connectors.
    Does it look like one?
    It should be GUID but make sure, you can also tell from the status below.
    Might even change it to something else, erase, then set it back to GUID.
    Apply.  And only then does it matter what user partitions you create.
    Jump through hoops for no reason.
    If you have Windows or a PC, use WD Lifebuard. Great at testing any SATA drive.
    Quick format with zeroes. Then Extended Test. Maybe even Full Format with zeroes to insure no bad sectors.
    When and where, at what point in time, did you use it and write files to it?
    By "carrier" I assume you mean the drive sled to go inside the Mac Pro.
    Did you ever use it in an SATA external other than WD? some of their MyBooks are moled into and drive and case cannot be used separated.

  • Can't install Snow Leopard on MacBook Pro - DVD won't mount

    I am unable to install Snow Leopard on my MacBook Pro as the DVD won't mount.  This is an early 2008 vintage MacBook Pro, intel core duo...
    I'm using a OS X Snow Leopard install DVD (family licensed).  This DVD has been used to install 3 other Macs in my house without a problem (about a year ago), but cannot be used to upgrade my MBP.  Actually, this disk mounted on the MBP exactly once - inserted with system up, the disk mounted.  Upon running the installed (a year ago), the computer restarted but hung in boot.  After getting the disk ejected and the computer restarted, the disk would never mount again.  I've defered upgrade for a year but at this point need to upgrade my MBP at least to Snow Leopard and possibly Lion.
    The problem doesn't seem to be with the DVD, since it continues to mount fine in other computers, and in fact a borrowed Snow Leopard DVD also will not mount on the MBP.
    BUT ... the problem also does not seem to be with the optical drive in my computer, as it can read & mount the install/restore disks that came with the computer as well as other CDs and DVD ROMs.  Only the Snow Leopard install DVDs fail to mount.
    I've also tried mounting the 10.6 install DVD on my Mac Pro desktop, making it available over the network (ethernet) with DVD/CD sharing.  I can mount the remote disk from my MBP that way, but when I launch the installer, the application launches (its own menus are displayed, I can quit from menu, for example) but does nothing -- no windows open, nothing.
    I've also tried "Remote Install" (again with the DVD made available with the Remote Install MacOS X application on my desktop), but when I boot the MBP with option held down, the remote disk is not available as a startup disk.
    Zapping the PRAM did not help.
    Am off to the store to get an optical drive cleaning kit and a blank DVD big enough to burn a new disk image, but would appreciate any further ideas at this point....

    Solution that worked: Copy the Install DVD to a USB flash drive and boot from that. 
    http://www.maciverse.com/install-os-x-snow-leopard-from-usb-flash-drive.html
    Up and running with Snow Leopard now and working on the updates.

  • I have a MacBook Pro and an 1TB WD my passport for mac. I bought a second hard drive to act as back up and when I went to do this the original passport won't mount. It is showing in disc utility but it will not repair. I am told the mac cannot repair it.

    I have a MacBook Pro and an 1TB WD my passport for mac. I bought a second hard drive to act as back up and when I went to do this the original passport won't mount. It is showing in disc utility but it will not repair. I am told the mac cannot repair it and I need to back up the files and then restore the hard drive. But I can't open the hard drive to move the files onto the new one!
    Help me please. I am not very technical so please answer as if I have no clue!! This hard drive has my iPhoto on it and all my pictures of my son, wedding and my current photography course so I  desperate to get it back!
    Any help will he appreciated!

    disk0s2: I/O error.
    disk0s2: I/O error.
    The MBP's disk is damaged and requires replacement.
    Genius Bar Reservations: http://www.apple.com/retail/geniusbar/

  • Thunderbolt external SSD won't mount

    I'm using the Elgato Thunderbolt SSD as an external hard disk with my 2013 MBP. Since I'm also using a Thunderbolt display, I usually daisy-chain the disk to the display.
    Recently I disconnected the Thunderbolt display from my computer without unmounting the external SSD. Since this also disconnected the disk, I got the usual ticking-off ("You should eject a disk before disconnecting it").
    However... since then, the external disk won't mount. It doesn't show up on the desktop or in Disk Utility, though it DOES show up ("Thunderbolt SSD") in System Information.
    Because the SSD gets warm when it's in use, I think it's still working. I just can't access it.
    Can anyone help?

    Is the Apple Thunderbolt Display at the END of the daisy-chain? That's where it should be - all other TB devices should be connected first, with the Display at the end of the chain.
    As to why you're having a problem getting the TB SSD to work, I'm stumped. It seems as if you've done everything that I would try to do to get everything working... and I'm assuming that you have powered down and unplugged the Display and all other devices for 15 minutes or so?
    Just make sure that the Display is at the end of the TB chain - that's really the only advice that I can offer.
    Clinton

  • Urgent - I think I just lost everything on my MacBook Pro. Hard drive won't mount and booting up shows "no" symbol

    My MacBook Pro (13" mid 2010, Yosemite) doesn't feel like booting up. It gives me the no symbol after the progress bar is about 1/4 of the way through.
    Additionally, it won't mount in the Recovery HD. It shows up as disk0s6 and clicking Mount does nothing. Can't seem to mount it in the Terminal either.
    The disk partition is encrypted, so unfortunately I can't pull the hard drive out of my MBP and pull the stuff off it with my PC.
    I tried First Aid - "no problems found" (such LIES!)
    I tried PRAM - didn't work
    I tried Verbose Mode - went fine for the first minute, then hung for a while before returning to the "No" screen and in the bottom right corner "Still waiting for root drive".
    I tried SMC - didn't work
    Most recently I did install rEFInd - which is a boot manager. I was afraid it screwed up the EFI partition -seemingly not, as it will boot to Recovery and external drives.
    The data still seems to be there, but the OS is having trouble accessing it.
    Do you know what would be causing this? I really need that data back :/

    It appears I can unlock the partition, using diskutil via the Terminal (diskutil coreStorage unlockVolume <UUID> -passphrase <passphrase>).
    However the volume doesn't have a UUID. It lists the partition type as "FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF" (which is a UUID) but using that doesn't work.
    Additionally when I use diskutil coreStorage list, it comes up with nothing. I'm at a loss here, the partition doesn't even know it's own UUID or that it's encrypted. It seems quite damaged to me but I don't have the slightest idea why, as I CAN boot to it and enter the password but it will stop at the "no" symbol part of the way along.

Maybe you are looking for