Want to highlight a helpful answer? Upvote!

Did someone help you, or did an answer or User Tip resolve your issue? Upvote by selecting the upvote arrow. Your feedback helps others! Learn more about when to upvote >

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

POSIX reports: The operation couldn’t be completed. Cannot allocate memory

Hi, I've got a HP SimpleSave 2Tb external hard drive that I'm trying to fix for a friend, they said it stopped working so I plugged it in to my iMac and Finder told me I needed to initialize the disk because there were no volumes on it, so I tried everything in Disk Utility, Partitioning, erasing, restoring, all the tricks and nothing worked. Every time I got the same error : "Disk Erase failed with the error: POSIX reports: The operation couldn’t be completed. Cannot allocate memory"
I tried some diskutil and fdisk commands in Terminal and still nothing works.
I was wondering if there's ANYTHING I can do to try and get it back? I don't even need to get the files back just the hard drive itself. Please help if you know anything.

Thanks in advance
Harry

iMac 20", Mac OS X (10.6.6)

Posted on Mar 8, 2011 3:46 AM

Reply
Question marked as Best reply

Posted on Mar 8, 2011 10:18 AM

Probably the partition table is corrupt. When it does this, it becomes difficult to
unmount (actually it gets stuck in a loop trying to mount the file system, to no avail
because the file system is corrupt).

This procedure forces a dismount, but does not eject the drive.
This breaks the loop and allows erasing the partition table:

open terminal.app

note: I wrote these instructions were for a boot volume
with that condition (booting from the install DVD), so the
disk numbers are not going to be accurate.

at the prompt:
diskutil list
(press enter)
that will give you the device name of your drive.
It most likely will be "disk0".

next command:
diskutil unmount force /dev/<disk_name>
example:
diskutil unmount force /dev/disk0

next command:
diskutil zeroDisk /dev/<disk_name>
example:
diskutil zeroDisk /dev/disk0
(press return)

After disk is zeroed, you may resume normal partitioning.
#

Bear in mind, since this is an external disk, the USB/ translation layer
may interfere with accessing the disk directly and foul up the procedure.

Looking at the drive specs, it says it only supports use under windows,
whatever that means. Perhaps it requires a proprietary USB driver or something.
Some folks claim it works on a Mac though.
http://techpatio.com/2010/reviews/hp-simplesave-2tb-usb-launcher-mac-blue-led

The USB interface (inside the unit) might be hosed.
Sales poop says it has a two year warranty. If still in warranty, send it back.

Kj
36 replies
Question marked as Best reply

Mar 8, 2011 10:18 AM in response to HJATKINS

Probably the partition table is corrupt. When it does this, it becomes difficult to
unmount (actually it gets stuck in a loop trying to mount the file system, to no avail
because the file system is corrupt).

This procedure forces a dismount, but does not eject the drive.
This breaks the loop and allows erasing the partition table:

open terminal.app

note: I wrote these instructions were for a boot volume
with that condition (booting from the install DVD), so the
disk numbers are not going to be accurate.

at the prompt:
diskutil list
(press enter)
that will give you the device name of your drive.
It most likely will be "disk0".

next command:
diskutil unmount force /dev/<disk_name>
example:
diskutil unmount force /dev/disk0

next command:
diskutil zeroDisk /dev/<disk_name>
example:
diskutil zeroDisk /dev/disk0
(press return)

After disk is zeroed, you may resume normal partitioning.
#

Bear in mind, since this is an external disk, the USB/ translation layer
may interfere with accessing the disk directly and foul up the procedure.

Looking at the drive specs, it says it only supports use under windows,
whatever that means. Perhaps it requires a proprietary USB driver or something.
Some folks claim it works on a Mac though.
http://techpatio.com/2010/reviews/hp-simplesave-2tb-usb-launcher-mac-blue-led

The USB interface (inside the unit) might be hosed.
Sales poop says it has a two year warranty. If still in warranty, send it back.

Kj

Mar 8, 2011 10:22 AM in response to KJK555

Thanks so much for your reply, it was very useful, I tried this method (which I had not yet tried) and I could force unmount the disk, and then zero it out in Terminal , it worked fine, but then still get the same error in Disk Utility when trying to partition, but I think what you said about the USB interface being faulty, I'll have to ask if it's still under guarantee .. but thank you.

Mar 8, 2011 12:31 PM in response to HJATKINS

Here is what one enterprising individual recommends:
#
HP Simplesave 500gb Disable "Virtual CD" SOLVED ! [ Edited ]
Options
09-18-2010 04:39 PM - last edited on 09-18-2010 04:41 PM

The Virtual CD is a pain when you are using it on a lot of different Machines.
I had the same problem with the WD 500gig Passport Drive,
and found WDSmartWareVirtualCDManagerforWindows-v1.0.7.4.zip that allows "YOU" to choose
whether "YOU" want the Virtual CD or not, unlike HP.
The WD500 Passport Drive uses a USB only internal Hard Drive with no SATA or IDE connection.
The HP SimpleSave uses a SATA internal Hard Drive.
So here is how to solve the PROBLEM
1. save all the data on the SimpleSave, MAKE SURE YOU DO THIS !
2. pull it apart gently with your fingernails and remove the SATA drive.
3. buy a cheap Generic SATA to USB enclosure.
4. right click on "My Computer" select "Manage" > "Disk Management" and make new partition(s)
and format.
or on Mac "Disk Utility"
5. copy all the data back on it.
6. take the leftover remains of the SimpleSave outside on the concrete (Wearing Eye Protection)
then proceed to smash it with a rather large hammer into very small pieces.
(you will feel a lot better after the **** it has put you through)

Now that is "SIMPLE"
#
http://h30434.www3.hp.com/t5/Other-Desktop-PC-questions/HP-Simplesave-500gb-USB- 2-0/m-p/305812

Apr 15, 2011 6:39 PM in response to HJATKINS

I have a similar problem, only my issue pertains to my internal drive.
I have been searching for a solution for about 5 hours and have tried just about everything, but have not found a concrete solution. I have attempted both the prescribed solutions in this topic as well as at least a dozen others, and I have seen a lot of promise but not like I previously reported, not very many results.

Not to spawn a new thread inside of this one, but let me describe my situation.

I opened my MBP to wake it from sleep mode when I woke up this morning, and it pinwheeled at my password authentication screen. After waiting 10 minutes for this to subside, I closed my laptop, waited 5 minutes, and tried to wake it up again. This time, after 5 minutes my computer allowed me to authenticate my password, and I was capable of opening disk utility and immediately repaired disk permissions on my hard disk (I have been having to do that when I turn my computer on in order to prevent it from locking up almost since i received the product).

Anyway, my computer locked up again after the permissions repair completed, and I needed to do a hard shut down. After the hard shut down I was unable to boot into neither OS X nor Windows.

This being suspicious, I grabbed my Snow Leopard install disk and booted with that. I opened Disk utility and was unable to repair my Macintosh HD.

After that, I followed the instructions that Disk Utility gave me and attempted to erase and reformat my Macintosh HD drive, but received the error,

"Posix reports: the operation couldn't be completed. Cannot allocate memory."

So, in response to that, My attitude was, "I have everything backed up, ill just erase the whole drive and restore, or reinstall everything" So, I attempted to repartition the disk so it would have only one partition. I was given the error,

"Posix reports: the operation couldn't be completed. Cannot allocate memory."

After this happened, I decided to attempt to erase the whole volume, and was shown the error

"Posix reports: the operation couldn't be completed. Cannot allocate memory."

After THAT happened, I used terminal to zero the drive, but have been unable to repartition or create a partition map for the drive because I keep getting the error,

"Posix reports: the operation couldn't be completed. Cannot allocate memory."

In terminal the error is not Posix, but still reports that it "Cannot allocate memory" after 60% of the way through formatting.

I cannot figure out my problem. I am half way considering buying a new drive..

Does anyone have any solutions??

Apr 17, 2011 10:17 AM in response to HJATKINS

I receive the same error and a 500GB WD drive in and external enclosure.


"Disk Erase failed with the error: POSIX reports: The operation couldn’t be completed. Cannot allocate memory"


The only way I can get around it is to format it in Windows, then reformat it on my MacMini with 10.6.7.


I have no problem formatting other drives.

Apr 20, 2011 11:37 PM in response to CitizenX

Yep! This is a glitch in the disc utility of Snow Leopard, which has so far been ignored by Apple. I too had the same issues trying to format a 200GB WD drive from a Firewire enclosure, which I pulled out of a broken HDD/DVD TV recorder. A Google search confirmed my opinion by showing hundreds of other 10.6 users with the same issues. Luckily, I have a few firewire drives and was able to get around the issue. What I did was, installed Tiger onto one of my empty drives, booted from it and used the disc utility in Tiger to format the disc, worked like a charm.



One of the reasons I gave up on Leopard was cos of issues with the disc utility, now it seems Snow Leopard also has the disc utility disease. C'mon Apple! Get your crap together! This is terrible! 😠

May 28, 2011 8:30 PM in response to HJATKINS

I just had THREE external disks disappear and go bad on me this week! just backed up to one last night, then it wouldn't mount this mornkng. Earlier in the week a LaCie D2 Quadra disappeared and won't mount, tried disk util, pc, and another mac as well as the terminal route of formatting - get the POSIX error, or cannot allocate memory and it won't initialize.


I am screwed. THREE externals gone - 15 years of work vanished in one week.


I bought a new 1 TB drive WD tonight to install tomorrow to get some back up in place, but looks like i cannot count of this for an length of time!


Running SL 10.6.7 which I updated with the lasted combo package.


As of tonight, NONE of the 3 existing hard drives that worked on Monday are able to mount on mac or PC.

Jun 4, 2011 9:15 PM in response to KJK555

"MacBook-Pro:~ devingabriel$ diskutil eraseDisk JHFS+ macintoshhd disk2

Started erase on disk2

Unmounting disk

Error: 12: POSIX reports: Cannot allocate memory"


I tried your advice and ended up with the same result. This is happening while trying to format a replacement 500GB drive that is OSX compatible, that I just purchased today. It's a replacement because the OS had locked up and I powered down. Upon reboot it would simply 'spin the wheel.' I was unable to format the drive - I can't remember the specific error, but it was different and occurred well into the format process.


Pulled the original drive, popped in an external case, and was able to erase/format it on PC. Tried formatting it back in my MacBook Pro and ... same problem, same error. Figured I'd try a new drive.


That brings me back to where I am now - with a new hard drive that I still cannot use. Any suggestions? 😟

Aug 14, 2011 5:48 PM in response to HJATKINS

Hi all, I have found a workaround for this problem and it works, you do not need to bin your drive. Although the data on the disk has been totally erased (have a mirrored drive set up, so all ok) I have a old mac G3 bronze keyboard laptop ( lombard I think) has OS 9.3 I reformatted my 1TB Maxtor using this "it mounted pronto" Then I moved to my Macbook Pro and the drive mounted no problems, I did re-format the drive again in disk utility just to be safe (no POSIX errors), and she is fine. I appreciate not all of you have OS9.3 on old laptops but it does work, hope it helps.

POSIX reports: The operation couldn’t be completed. Cannot allocate memory

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.