Yosemite won't mount external encrypted disks!

HELP! Finally upgraded to Yosemite. Because my old SAS card is not working, I installed a Sonnet eSATA card. I have three drives connected to it via eSATA. One of them mounts just fine. that drive is not encrypted.
The other drives were encrypted using Disk Util back in Mountain Lion (or Lion even) and I've never had any issue. Now, when I power them on, I get asked for the password, and then the OS tells me they are unreadable! HELP!
I know this isn't the case. I'm about to revert to Mavericks, but this is ridiculous.
Anyone have any idea what could be going on, I've searched and cannot find any information.

Hi,
I'm having the same/similar problem. I have several external USB 3.0 drives, all were encrypted under 10.9, and I have to wait minutes before they are fully mounted and accessible using 10.10.
When connecting a (nearly full) 2TB external USB 3.0 drive today to my mid-2010 MBP for the first time post-upgrade, I was prompted for the password after waiting for minutes. Keychain has the password as saved when using 10.9, but I was still being prompted. I entered the password (the "remember in keychain" option was selected), but I was then prompted again and again for the same. I clicked "Cancel" and the drive mounted on the desktop.
Ejected the drive, reconnected, and the drive did not load. I was not prompted again for the password but the drive did not mount. I could see the drive in Disk Utilities, with the primary reference (poor terminology) appearing as normal, and the sub reference (the encrypted drive) appearing grayed out. I detected no activity via the light indicator on the face of the drive. The drive eventually mounted after ~5 more minutes. I was able to see the files, open the files, and copy files to the drive without trouble.
I then repaired permissions and repaired the drive. Disconnected, reconnected, and still waited minutes for it to ultimately mount.
Deleting the password from Keychain and re-saving through 10.10 does not fix the issue.
Clicking the "Unlock" button in Disk Utilities does not expedite the prompt for a password or expedite connecting the drive.
Using different USB ports makes no difference.
For comparison, I then attempted with a blank 64gb Sandisk USB 3.0 drive encrypted under 10.9. Same issues. Wiped it and applied no encryption, disconnected, reconnected and the drive mounted immediately. I then wiped it and encrypted it under 10.10, but minutes passed before prompting for a password and mounting the drive.
My passwords used during the above are 50 characters long. I wiped the 64gb drive again and applied a 4 character password, but the issues persisted.
I hope this helps someone identify a cause and develop a fix as soon as possible.

Similar Messages

External hard drive won't mount, even after disk repair.

My Toshiba external hard drive won't mount on my MacBook Pro 10.8.5. I can see it in my disk repair, and when I repair, "the partition map appears to be ok." But I can't access the icon to be able to open the hard drive contents on my desktop. Help!

Hello maccynicwhoalwayshasmacs,
Thanks for the question. After reviewing your post, it sounds like trouble with an external HD mounting. I would recommend that you read this article, it may be able to help you resolve or isolate the issue.
USB and FireWire Quick Assist
Thanks for using Apple Support Communities.
Have a nice day,
Mario

Mount External Hard Disk (connected in Windows Server) in Solaris 11

Hello Solaris Admins,
I have a 2 TB WD My Book External Hard Disk connected to a Windows 2008 Server and needs to mount it in Solaris 11 Server.
For mounting a directory in File Server i am using the following Command
mount -F smbfs "hostname;username:password@//hostname/<SharedFolderName>" /ext_storage
Can i use the smbfs option for mounting the External Storage also.
Thanks,
Salih Mohamed Yusuf
Oracle Database Administrator

Thanks Pascal for your reply.
I will confirm once the mounting is done.

Mounting external Hard Disk

Hello.
I have an external HDD (USB) that I use for moving large files between computers. I plugged it into my Mac and it mounted fine, worked great. Unfortunately, Spotlight immediately took over and started indexing the heck out of the drive. I tried adding the drive to Spotlight's Private pane, but it wouldn't add and kept on indexing. I killed mdimport, but the CPU was still through the roof and the drive wouldn't eject (dialogue said that it was in use). I didn't have time for any of this crap, so I did the only reasonable thing to get the Mac to quit working like crazy on the drive--I yanked the USB cord. Worked great, even if the computer bitched at me about not doing that. Yeah, I know it was a bad idea, but I didn't see any other choices in my immediate time frame.
So, now Finder won't mount the HDD. All the data appears to be there. The drive works fine. Windows has no issues mounting it. Is there some hidden file (like all those .ds_stores) that might be corrupted on the HDD, or some file on my Mac that I can trash that will get the HDD to mount like normal again? I haven't tried mounting the HDD on a different Mac. Any suggestions appreciated.

1. You wrote: " But my CPU usage goes to near 100%, and Activity Monitor does not list any processes to account for this (mdimport is not listed)."
1.1. Is that CPU utilization as reported by Activity Monitor?
1.2. Have you sorted the list of processes in descending order by %CPU? In Activity Monitor, click the %CPU column heading until the list is in descending order.
1.3. Before connecting and powering-on the drive, set up Activity Monitor as noted above. Additionally, in Activity Monitor, select View > Update Frequency > Very Often. Then connect the drive and power it on, watching Activity Monitor.2. Per your other questions re: Finder, if it was a Finder issue, Finder would be the process consuming the CPU per Activity Monitor. 100K files is nothing for Finder. Is the drive or a folder on the drive open in a Finder window when this happens?
3. Is this a new drive? If so, I'd contact the manufacturer or vendor: it may be defective. If not a new drive, what changes did you make to your system before this problem arose.
4. Have you tried a different USB cable? Different USB port?
5. See if an errant Startup or Login Item is causing the problem: see my "Troubleshooting Startup and Login Items" FAQ.
6. When the problem occurs, immediately check these Console logs for clues.
Good luck!
Dr. Smoke
Author: Troubleshooting Mac® OS X
Note: The information provided in the link(s) above is freely available. However, because I own The X Lab™, a commercial Web site to which some of these links point, the Apple Discussions Terms of Use require I include the following disclosure statement with this post:
I may receive some form of compensation, financial or otherwise, from my recommendation or link.

Upgraded to 10.4.9 on MBP 15", now, I can't mount external hard disk!

Hi all,
I have a LaCie 500GB drive that I've been using perfectly since I've gotten it, but alas, I upgraded to 10.4.9 and it no longer mounts either by it's USB interface or by its Firewire interface.
My machine is a MBP 15" (2.16 GHz, 2 GB Ram), which works perfectly in all other respects and is now running 10.4.9.
The symptoms are that when I plug it in, I usually get the message, "The disk you inserted was not readable by this computer" with the options "Initialize...", "Ignore", and "Eject". So far, I haven't pressed any buttons except Ignore or Eject. Sometimes, I do not get this message, but it still doesn't mount, it just silently does nothing.
So, after pressing "Ignore", I've opened Disk Utility and had a look. The physical drive appears and there is one volume named "disk2s6" which for all purposes is probably my normal, logical volume (partition). However, last time it mounted on this machine, it was named "Archive". This logical volume is grey and will not mount no matter how many times I press the "Mount" button. It just does nothing.
OK, so, while I'm in Disk Utility, I ran Verify Disk and, after the normal routine, it comes back with "No Repairs Necessary". I've also tried "Repair Disk" and this comes back "No repairs were necessary", again after the full, normal processing of the various things.
I also performed a Fix Permissions on my startup-volume, but this didn't help either.
Next test was to mount the disk on my MacMini (PPC) instead, also running 10.4.9. It mounts perfectly and it properly comes up with the name "Archive" as expected.
I've then tried to mount other devices on my MBP including a USB memory key, and another external Firewire drive. These both mount perfectly on my MBP.
While I was at this, I've also tried new USB and Firewire cables, this didn't affect my results in the least.
I've finally verified that there is nothing in /Volumes out of the ordinary that might prevent it from mounting by doing a "sudo ls -la" whilst in /Volumes/. There's not a thing that would affect the mount-point.
I then disabled my folder actions that I've been running on the directory /Volumes *I had an action used to backup my USB key). Unfortunately, I still have the same issue.
Finally, I downloaded the Combo 10.4.9 installer, booted into Safe Mode (to trigger an automatic fsck), then rebooted and installed the 10.4.9 Combo installer, in case there was some weirdness in the Software Update upgrade to 10.4.9.
What stone have I left unturned? Why won't this drive mount, but it works perfectly elsewhere? I want to get back to using Aperture on my MBP and my entire photo Library is on this disk (well, and backed up on another external drive, but it lives normally on my MBP).
MBP 15" 2.16GHz + LaCie 500GB Ext Firewire drive Mac OS X (10.4)
Mac OS X (10.4)

Here's some additional info...
When executing a manual mount: I get this:
sudo mount -v /dev/disk1s6 /Volumes/Archive
/dev/disk1s6 on /Volumes/Archive: Incorrect super block.
During a normal plug-in-the-disk-and-expect-it-to-mount-automatically, this is what diskarbitrationd reports:
22:45:40 iokit [0] -> diskarbitrationd [41]
22:45:40 created disk, id = /dev/disk1.
22:45:40 created disk, id = /dev/disk1s3.
22:45:40 created disk, id = /dev/disk1s4.
22:45:40 created disk, id = /dev/disk1s6.
22:45:40 created disk, id = /dev/disk1s2.
22:45:40 created disk, id = /dev/disk1s1.
22:45:40
22:45:40 diskarbitrationd [41] -> diskarbitrationd [41]
22:45:40 probed disk, id = /dev/disk1s6, with hfs, ongoing.
22:45:40
22:45:40 diskarbitrationd [41] -> SystemUIServer [289]:13363
22:45:40 dispatched callback, id = 914042DE:00000000, kind = disk peek, disk = /dev/disk1s1.
22:45:40 dispatched callback, id = 914042DE:00000000, kind = disk peek, disk = /dev/disk1s2.
22:45:40 dispatched callback queue.
22:45:40
22:45:40 SystemUIServer [289]:13363 -> diskarbitrationd [41]
22:45:40 dispatched response, id = 914042DE:00000000, kind = disk peek, disk = /dev/disk1s1.
22:45:40 dispatched response, id = 914042DE:00000000, kind = disk peek, disk = /dev/disk1s2.
22:45:40
22:45:40 diskarbitrationd [41] -> diskarbitrationd [41]
22:45:40 probed disk, id = /dev/disk1s6, with hfs, failure.
22:45:40 probed disk, id = /dev/disk1s6, no match.
22:45:40
22:45:40 diskarbitrationd [41] -> SystemUIServer [289]:13363
22:45:40 dispatched callback, id = 914042DE:00000000, kind = disk peek, disk = /dev/disk1s6.
22:45:40 dispatched callback queue.
22:45:40 dispatched callback, id = 914042DE:00000000, kind = disk peek, disk = /dev/disk1s4.
22:45:40 dispatched callback, id = 914042DE:00000000, kind = disk peek, disk = /dev/disk1s3.
22:45:40 dispatched callback, id = 914042DE:00000000, kind = disk peek, disk = /dev/disk1.
22:45:40
22:45:40 SystemUIServer [289]:13363 -> diskarbitrationd [41]
22:45:40 dispatched response, id = 914042DE:00000000, kind = disk peek, disk = /dev/disk1s6.
22:45:40
Mac OS X (10.4)
Mac OS X (10.4)

Macbook Pro won't mount during target disk mode

I don't know what to do.
I was using Safari today when the whole computer froze. Nothing was responding, so I had to force shut down.
When I went to restart, I got a gray screen with the apple logo and a progress bar; the bar will take a while to fill, then the computer shut down completely. Happens every time now.
I tried booting in safemode and it didn't work; the command prompt details said "Incorrect number of thread records. (4, 29503)" and "Incorrect number of extended attributes (It should be 381007 instead of 381008)"....... What does that mean????
I tried booting the backup drive and running disk utility to diagnose the problem, and it said the disk is unable to be repaired etc.
Now I'm trying to salvage my important files by using the firewire target disk mode with another mac. My macbook pro won't even mount; disk utility said it can't be mounted and is damaged.
Please help--what do I do to save these files???

My workflow was like this:
Partitioned fresh hard drive into 2 partitions: 1 for OS clone, 1 for data recovery
Used Carbon Copy Cloner (an excellent tool) to clone working OS to 1st partition
Attached harddrive to malfunctioning MBA
Held Option on malfunctioning MBA and booted to cloned drive
Once booted, I used old-school Data Rescue II to salvage data from MBA internal drive to my data recovery partition. (Probably need a newer / better data recovery program, as this one changed file names, moved things around, was generally not that awesome...)
Used Disk Util from booted clone to format MBA internal drive.
Used Carbon Copy Cloner to clone to formatted MBA internal drive.
Shut down, disconnected external drive, MBA booted normally.
Think that's everything. I've been touting the excellence of Carbon Copy Cloner for a while now for backups. In my opinion it's much more thorough than Time Machine backups, as you don't need a functioning OS. You can boot to a clone -- time / life saving!

Mac won't mount external HDD since 10.8.4 update

Hi All
I'm fairly new to Mac (3mths) so still finding my feet...hopefully someone is able to help me here!
Hardware:
MBP 2.7Ghz running (now) Os 10.8.4
WD HD5000D032-000 (the old drive)
3TB WD Red (the new drive)
Solutions tried to the problem (described in detail below):
- restart Mac
- restart eHDD
- different USB and power cables for eHH
- different Mac(mini)
- removed eHDD from stock housing and used SATA docking station
- bought new HDD and used with SATA docking station
Now to the detail of my problems:
I've had a WD 500GB external HDD for about 8yrs. Formatted FAT32. Used with PC/Win laptop no issues.
Switched to Mac and no issues at all. However after a recent trip to Japan I plugged in the HDD to back up all the photos and vids I'd taken (I took my Mac with me to download off the the various SD cards,etc), the HDD plugged in and booted fine as normal and file transfer was initiated. The folder was large (don't recall how much but a few GB at least). Everything seemed to be progressing fine so left both Mac and HDD plugged in and carried on watching tv. Noticed a few mins later that an error message had popped up saying disk could not be found (or something similar).
HDD was no longer visible. Therefore I unplugged and reconnected and.... nothing. I can see the HDD in Disk Utility but it's not mounted. Options to verify/repair disk are greyed out. At this point I tried using different cables and USB ports and still no improvement. I've also tried restarting both Mac and HDD.
A few hours of reading forum posts suggested the HDD housing may be the culprit as it was quite old and prone to failing. As I'd tried all else, I went out and bought a SATA docking station and removed the HDD from its stock housing. This yielded the same results - I can see the HDD clearly in Disk utility but can't mount or verify/repair.
I then tried plugging into mate's Macmini running and older Osx and this time, the verify/repair options are available. Tried them and result was disk could not be repaired by Disk Utility. I still couldn't mount the drive and access any files though.
I had been planning on setting up a NAS anyway so ordered a new 3TB eHDD (WD Red) which arrived yesterday. I plugged it in using the docking station ni order to format it to FAT32 so that I could at least download my data from my Mac (and then subsequently look to recover all the data from the old eHDD) but the option 'MS-DOS File System' isn't available in the drop down in Disk Utility/Erase.
All the steup guides on formatting HDDs using Mac suggest that I should have this option in order to format as FAT32. All I see are 3 types of 'MS-DOS (extended)' and 'exFAT'.
The twist:
All this time I just assumed that it was the hardware acting up but the fact that the new HDD isn't recognised properly either made me wonder. I remember updating the OS to 10.8.4 whilst I was away in Japan and connected to wifi. I presumed that any update that was pushed down to me was good to go - could I be wrong??
I've also noticed that my wifi sometimes takes a while to connect / disconnects by itself and skype repeatedly drops calls. From more reading around, I see that these are some issues people have experienced since updating to 10.8.4.
So could my HDD issues be being caused by 10.8. 4 as well?!
I'm out of ideas so now wondering whether I should try and roll back the 10.8.4 update but I've not idea whether this is safe/easy to do, etc...
Any help would be VERY much appreciated!!
Thanks in advance!
Vig

Duplicate post. Answered here: http://forums.macrumors.com/showthread.php?t=1614533

Won't Mount Windows Install Disk

Daughters' Brand New MBP Dual Core 2 will not mount my Original Windows XP Install CD.
Inserts, runs, buzzs and spits it out. Can't even start to run Parallels since I can't install the OS.
Tried the same exact disk on an older G5.....mounted on the desktop just fine.
Same disk worked fine on my MacPro and had no issues with the towers' optical drive.
Any suggestions and has anyone else had a mount/read failure of a windows CD?

After 90 minutes of discussing the problem with the Parallels support rep, I was still without a solution. He hadn't tried to get Parallels to see the XP disc in the external drive, but instead gone the ISO route yet even that wasn't being recognized by the program when trying to set up Windows. After beating my head on the desk in frustration, I was finally able to fix it myself. I created a virtual machine that had almost no components to it (don't know if this was part of the problem or not) outside of memory, the CD/DVD-ROM pointed at the ISO image of the XP install disc, and a hard drive. I then went thru the Install VM button and prepared to install, but instead of using the Recommended settings, I used the one below it. I wish I could say with certainty what I actually chose, but I can't. I tried too many things in rapid succession to know which one was actually a hit. When I didn't choose the recommended settings, to my amazement, I finally got the Windows setup boxes to appear. This was quickly followed by a panic attack as I realized that hitting F8 to accept the license agreement wasn't working, but attaching a keyboard from another machine fixed that and I'm now happy to report that all is working perfectly. I just wish the disc drive would have read the disc correctly in the first place.

Pismo running Panther won't mount retail install disk

I'm appealing to the vast wisdom of the collective--cuz, man, I'm stumped...
I just inherited a Pismo, which is currently running Panther 10.3.8. I don't have the original disks that came with it. I DO have a retail version of Panther, which I purchased for my G4 desktop.
What I want to do is do a clean install of Panther on the Pismo's current hard drive (get rid of all old files & get it ready to sell), plus I've got a new hard drive on order, which I'll want to install Panther on, too.
The problem is the Pismo just flat out won't recognize the Panther install disks. I hear it spinning and whirring away, bless its little heart, but then it just gives up. No joy. The Combo drive will recognize/mount/play any and all CDs and DVDs I've thrown into it--just not the Panther install disks.
I've upgraded the firmware. I've tried running the disks in OS 9 (which gives me a "this disk is unreadable" message). The Pismo meets all the system requirements (which it had to, since someone before me got Panther to install somehow!)
Any ideas?

The Panther CDs are practically new & spotless, no peripherals are connected, and the PRAM got reset when I updated the firmware.
It's quite possible I have a failing DVD-ROM drive, but unless I'm reading it wrong, it's not made by LG. My Combo drive says it's a Matsushita SR-8174.
So, great suggestions, but I don't think we've quite dialed it in yet...
In my travels through the Googlesphere, I found one woman's posting in some forum with the exact same problem. Unfortunately, no one could help her and she seems to have given up. Also, a few references to vaguely similar problems that might have been solved by removing the non-original RAM (I have a 64 MB and a 128 MB in the two slots--within Panther's requirements, but I am ordering a 512 MB).
So on my end, I'll try it with more RAM (though, as I mentioned earlier, someone managed to install and run Panther just fine originally) and I'll head to our local independent Mac repair specialists to see if they can swap out the optical drive & see if that's the problem. But I'd still like it if the solution came from the wisdom of this incredible resource. Y'all rarely let me down--thanks.
A related question: if I connect the Pismo to my G4 desktop & start it up in Target Disk Mode, can I put the Panther disks in my G4 and wipe the Pismo & install Panther from there...?

OS Yosemite won't read external HD

I updated my OS to Yosemite last night, and I plugged by WD for Mac external hard drive in, and it read it briefly then ejected on its own. I go to disk utility when it's plugged in, and doesn't show up at all. Any suggestions??
Thank You

how in the world do i do that lol...

.dmg's won't mount or create disk image

I'm using a 17" powerbook. I've had no issues in the past year of ownership with downloads (from Apple site or other). Recently, when I attempt to download a .dmg, the image won't appear on the desktop, however it did download. The download file show's it did download but failed to mount. The desktop shows the failed download as shaded out.
I am not using any download accelerator or similar product. This problem appears to have started with my most recent system software update from Apple.
Help and suggestions are appreciated.
PS - this only seems to apply to .dmg's

Do you still have some older dmg files that you can check? Will one that worked in the past still work? When you do GetInfo under the section for "Open with" is the application specified as DiskImageMounter? If not, is that application in the drop down list and can you select it? Finally, do you have the application here:
"/System/Library/CoreServices/DiskImageMounter.app"
If the application for mounting dmg files is there and you can choose it to open the dmg files, or it is already listed as the choice, you might try using Disk Utility to repair permissions. If the older dmg files work correctly, but the new one doesn't, then something is wrong with the new downloads.
Francine
Francine
Schwieder

Won't mount external HD

My MBP suddenly is no longer mounting my external HD's. Both will mount on my G4 desktop and my old PowerBook G4 and will mount on Windows machines as well. So I know the drives and the connecting cables are ok.
Both drives are receiving power from both USB ports and the FW800 port (neither drive has a FW400 port) so at least power is getting to the ports on the MBP.
My best guess right now is some type of corrupted preference file, but I have no idea which preference file it might be and I don't want to start trashing preference files.
This message is repeated 100s of times in my system.log:
May 2 17:04:12 adwMacBookPro kernel[0]: ERROR: FireWire (OHCI) TI ID 8025 built-in: handleUnrecoverableErrorInt
May 2 17:04:15 adwMacBookPro kernel[0]: FireWire GUID 1019e3fffe1b6e30 is invalid!
Any ideas?
Thanks
Anthony

Already repaired permissions and zapped PRAM. Also ran cron jobs and cleared caches.
Am trying to startup from Hardware Diagnostics disk, but now I'm even having startup issues. This is starting to look more and more like a hardware problem.

Imac running Yosemite won't detect external display

I previously was using a 2008 iMac desktop and running OS X Yosemite. I was using dual monitors (other monitor being Insignia brand) and everything worked fine. Since this was an earlier mac version, I was using the Mini DVI to VGA Adapter to connect. Last week, I got a brand new iMac (Mid 2014 version). I am running OS X Yosemite as well, but now it won't detect any displays. I'm now using the Thunderbolt cable to connect so I wonder if that has anything to do with it. But I have used that same Thunderbolt cable before on my macbook and it worked just fine.
I've tried restarting, resetting the PRAM and everything. I don't know what else to do. Help!

Thanks for the reply, but tried everything and it still won't work. Rebooted, installed updates, cleared PRAM, everything. It will not detect the displays at all. Maybe there is something wrong with my VGA cable.

Hard drive won't mount after running disk utility repair

I have an iMac with a 320gb hard drive. It will not mount. The small horible wheel started sining so I retared. It could not find the start-up disk. I restared with the CD, after doing this twice the disk was visible in disk untility. I have ran this 3 times and it says the node is incorrect and it cannot be reapired by Disk Untility. It will not mount.
Is there any other way to save the disk so I can get my files off.
Any help is welcomed

You would need the Firewire cable. If you get one then you can use Target Disk Mode - Transferring files between two computers using FireWire to transfer your files to another drive.

Air/Retina Mac's Won't Mount External Optical Drives

Please Help. I recently upgraded hardware from a 2009 MBP and a 2007 MBP. My current problem is that on the i7 Air and i7 MBP w/ Retina it will no longer recognize USB Optical Drives on 10.8.2. It was crashing my i7 Air (panic attack-grey screens), so I returned and went with the Pro after store consult. I take the same hardware and plug it into my old machines and it works fine, running the same 10.8.2.
I have read many forum posts around the net and shown various solutions (flashing RAM, etc.). All of which have not worked on my setup, and the drive will still not mount. I have tried 2 seperate optical drives, 1 Blu-Ray and 1 DVD (Apple Superdrive - now returned).
Is there some tie to this issue and the fact that both the Air and MBP w/ Retina do not natively have optical drives? If so, is there some solution that can be performed to properly address this issue. This is a reasonable use case and I do not want the models with optical drives. Kinda surprised considering that Apple is pushing us to this no optical drive world that they would not support external ones inclduding their superdrive, which doesn't work in this case.

Duplicate post. Answered here: http://forums.macrumors.com/showthread.php?t=1614533

Yosemite won't mount external encrypted disks!

Similar Messages

Maybe you are looking for