Disk Erase failed with the error- Operation timed out

I've checked my computer- Mac Book White in Apple store, everything is fine just the hard disk has been corrupted. Needed to erase and reinstall. By the time I wanted to erase it, I can't erase and appears "Disk Erase failed with the error- Operation timed out".
Anyone knows how to solve this question would be nice.
Thanks

Well give this a try:
Repairing the Hard Drive and Permissions
Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger, Leopard or Snow Leopard.) After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer. Now restart normally.
If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
Now download a utility like TinkerTool System or Leopard Cache Cleaner - VersionTracker or MacUpdate - and use it to clear out your system, user, and font caches.
And, try this for the software update issue:
Fix for Software Update
See Troubleshooting Automatic Software Update in Mac OS X.
Delete the following files:
/Library/Preferences/com.apple.SoftwareUpdate.plist
/Home/Library/Preferences/com.apple.SoftwareUpdate.plist
/Home/Library/Preferences/ByHost/com.apple.SoftwareUpdate.xxx.plist
"xxx" is a number.
/Home/Library/Caches/com.apple.SoftwareUpdate/ (delete entire folder)

Similar Messages

Is my HD Dead? Reformat Disk Utility Error: secure disk erase failed with the error could not open disk.

Hi,
Fed up with seeing the spinning beach ball I decided to reformat my MacBook Pro...
After backing up everything on an external hard drive I put in the OSX install DVD, restarted the machine and held down 'C'.
I followed the install prcedure, clicking next a few times etc...
I then went into Utilities > Disk Utility. I chose 7-Pass to erase the Macintosh HD and set it off erasing.
I checked the process an hour in and message on screen read:
Secure disk erase failed with the error:
could not open disk
The internal hard drive no longer exists in the disk utility so I cant retry erasing it.
The only thing that appears in disk utility is the OSX install DVD.
I can't even shut down the mac as everything under the apple tab is greyed out!
I'm guessing this means my hard drive is broken right?
If anyone has any other ideas of what to try I'd really appreciate that.
How do I turn the machine off?
If my hard drive is gone then should I consider getting an SSD drive?
Any recommendations for such a drive would be great.
Hope you can help!

Did you partition the drive?
Extended Hard Drive Preparation
1. Open Disk Utility in your Utilities folder. If you need to reformat your startup volume, then you must boot from your OS X Installer Disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger or Leopard.)
2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area. If it does not say "Verified" then the drive is failing or has failed and will need replacing. SMART info will not be reported on external drives. Otherwise, click on the Partition tab in the DU main window.
3. Click on the Options button, set the partition scheme to GUID (only required for Intel Macs) then click on the OK button. Set the number of partitions from the dropdown menu (use 1 partition unless you wish to make more.) Set the format type to Mac OS Extended (Journaled.) Click on the Partition button and wait until the volume(s) mount on the Desktop.
4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
5. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, check the button for Zero Data and click on OK to return to the Erase window.
6. Click on the Erase button. The format process can take up to several hours depending upon the drive size.
Steps 4-6 are optional but should be used on a drive that has never been formatted before, if the format type is not Mac OS Extended, if the partition scheme has been changed, or if a different operating system (not OS X) has been installed on the drive.

External Drive Disk Erase Failed with the Error Input/Output Error

I have 2 hard drives in an external FW800 enclosure that I am unable to format. When I go to initialize the drives in Disk Utility, I get the following error message: "Disk Erase failed with the error: Input/output error."
The drives show up in Disk Utility, but I can't repair them (that option is grayed out). Disk Utility correctly ID's the manufacturer of the drives (Maxtor), their size (200gb each), so it's obviously seeing that the drives are there. But it won't let me format them.
The drives are new, by the way; they don't have any data/files on them. I have Disk Warrior, but the drives don't show up there to be repaired -- probably because they aren't formatted yet.
After looking at other posts, I tried switching the jumper settings around on the drives -- from Master/Slave to cable select and back again, but it didn't help. I also tried doing a zero erase (even though the drives are new), zapping the PRAM -- again, no help.
One question I had is whether this could be a bad FW800 cable? The cable is new -- it came with the enclosure, which is an OWC Dual FW 800 enclosure. Other than that, does anyone have any other thoughts about what's causing this? Any help would be greatly appreciated.
Matthew

SOLUTION!!!!
I had the exact same problem. I have the original 20 GB hard drive that came in my Powerbook G4 550MHz and a couple of years ago I traded up for a 60 GB drive and bought a FW/USB enclosure for my original drive to use it to backup my important files. I hadn't backed up in over a year (shame on me!) and I decided maybe I should erase the drive and start from scratch. It was connected via USB.
At that point DiskUtility gave me the exact same Input/Output error. I tried partitioning the drive into 1 or more partitions but came up with the same error. I couldn't figure out what was wrong so I decided to startup in OS 9.2.2, I did that and let it start up, then plugged in the hard drive and it gave me the standard "This disk is unrecognizable, do you want to eject or erase?" so I clicked Initalize. It worked!
Just make sure you choose the MacOS Extended option when initializing out of OS 9 (instead of the MacOS Standard option) so it can be read and viewed in OS X.
If your computer is too new to be able to boot from an OS 9 folder on your drive or an OS 9 CD, then see if a friend or a local library has older computers that are running OS 9 or can boot from it. If not let me know and you can send me your drive and I'll reformat it.
Kind of crazy...I haven't used the OS 9 partition on my HD in YEARS...was even thinking about erasing it since I don't use any Classic applications anymore...good thing I didn't!
Nick
Powerbook G4 550Mhz Mac OS X (10.4.6)

Disk Utility _ Disk Erase failed with the error

I have a 1GB Kingmax USB Stick which I am trying to erase or restore. I used in a PC at uni and it no longer works. When I try to erase or restore with Disk Utility I get an error message 'Disk Erase failed with the error:
Input/output error'
I have tried also with Windows, but to no avail. The System Profiler recognises the USB stick.
Any ideas?
Cheers!
iMac G5, iBook G3 Mac OS X (10.4.8)

Shutdown the computer and remove the USB drive.

Help!! "Volume erase failed with the error"

I have no idea what to do ! My computer was running a bit slow and I wanted to get rid of any unwanted apps and files, so I backed up the files that I did want on an external drive. I then erased everything on my HD. Then I restarted it and attempted to reinstall the old apps from the cd that came with my computer but I couldn't. It takes me to the Utility Dock every time I restart it and when I try to install Lion back on, I can't click on the HD and it says it's 'locked'. When I try to reset it again or do anything at all it gives me a "Volume erase failed with the error" message. I can't do anything! Can anyone help???

Replace the hard drive.
If it can't be erased, that usually means something is seriously wrong with it.

Partition Failed Partition failed with the error: POSIX reports: The operation couldn't be completed. CAN NOT ALLOCATE MEMORY

I plug usb mass storage device to my macbook pro i7 than every thing is stack and i reinforce to shutdown and than I start again but mac fail to boot again.
I tried different optiones in disk utility in mac os startup disk. but still fail to repair, erase and partition. I try to fix with the steps listed in
https://discussions.apple.com/message/13288923#13288923
but it fail to partition with the msg:
Partition Failed
Partition failed with the error: POSIX reports: The operation couldn’t be completed.cannot allocate memory
pls pls pls help urgentely on this matter I stop working.
Kind Regards,
pe

Hi again OGELTHORPE.
I've already run two hardware tests. One quick one and one extended one. It was unable to pick anything up.
It's like everything is running perfectly, but when I go to erase the HDD or partition it, it pops up with the error message. Even when I try to erase and partition using "Terminal", I received the same error message.
It's beginning to do my head in, but will see if replacing the SATA cable will make any difference. If it doesn't, I'll hazard a guess it could be the Logic Board.
Thanks again for your suggestions!
L.

I get the following error when formatting a external hard drive. Partition failed with the error: POSIX reports: The operation couldn't be completed. Cannot allocate memory

I get the following error when formatting a external hard drive.
Partition failed with the error:
POSIX reports: The operation couldn’t be completed. Cannot allocate memory
I have a Macbook pro 13" A1278. I purchased it around december 2010. I have a HHD 3.5" drive desktop select II 1.5TB. I purchased it around Febuary/March 2011 to use with my Macbook pro. I formatted it and moved all my files to there, I got it so my macbook's hard drive wouldn't brake and I lose everything on my macbook.
Is there any fixes?

First, try a system reset. It cures many ills and it's quick, easy and harmless...
Hold down the on/off switch and the Home button simultaneously until the screen blacks out or you see the Apple logo. Ignore the "Slide to power off" text if it appears. You will not lose any apps, data, music, movies, settings, etc.
If the Reset doesn't work, try a Restore. Note that it's nowhere near as quick as a Reset. From iTunes, select the iPad/iPod and then select the Summary tab. Follow directions for Restore and be sure to say "yes" to the backup. You will be warned that all data (apps, music, movies, etc.) will be erased but, as the Restore finishes, you will be asked if you wish the contents of the backup to be copied to the iPad/iPod. Again, say "yes."

The creation of the shadow copy on the backup destination has failed. Detailed Error: The Volume Shadow Copy operation failed with the error 0x80042316

When using Microsoft Backup on a Windows Server 2008 SP2 (not R2 - [Microsoft version 6.0.6002]) I get the error "The creation of the shadow copy on the backup destination has failed. Detailed Error: The Volume Shadow Copy operation failed with the
error 0x80042316"
The odd thing is that when I start the backup manually, it works fine. When it runs automatically the error appears.
When doing a SFC /scannow I do get errors that can't be corrected.
Is there anything short of rebuilding this machine (It's a DC and the only one this office has) I can do to fix this?

Hi,
0x80042316 means "Another shadow copy creation is already in progress". This error could occur when another VSS instance is running.
Is there any third party backup application installed? Try to uninstall it to see the result. And please also check if there is another backup schedule which causes the conflict.
Meanwhile please provide the result of:
vssadmin list providers
vssadmin list writers
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Support, contact [email protected].
Hi,
I do have Crashplan ProE running. It started at 1900 and the Windows Backup starts at 2000. I have modified Crashplan not to start until 2300 to see if that helps.
Also:
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Provider name: 'Microsoft Software Shadow Copy provider 1.0'
Provider type: System
Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
Version: 1.0.0.7
AND:
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {f0c7ee55-5885-4894-8dd3-14fffbdd4d2e}
State: [1] Stable
Last error: No error
Writer name: 'SqlServerWriter'
Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Instance Id: {017a0133-7577-4322-b513-04f72404b70a}
State: [1] Stable
Last error: No error
Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {6b17d670-9ea8-4ff1-a59e-b474f4b893db}
State: [1] Stable
Last error: No error
Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {56aad1bf-9bf1-4fde-b2f4-a706577c632d}
State: [1] Stable
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {e942d09d-276e-450a-9bf4-b1d5abe6af8a}
State: [1] Stable
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {3737164b-61ac-454c-b1f7-42f2620f10db}
State: [1] Stable
Last error: No error
Writer name: 'DFS Replication service writer'
Writer Id: {2707761b-2324-473d-88eb-eb007a359533}
Writer Instance Id: {39458257-aca4-481e-a302-994f3eb1e9a3}
State: [1] Stable
Last error: No error
Writer name: 'Dhcp Jet Writer'
Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
Writer Instance Id: {6a8ab4aa-760c-4102-a27f-58f570c9c572}
State: [1] Stable
Last error: No error
Writer name: 'NTDS'
Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
Writer Instance Id: {53577013-8397-448e-9a25-c7cac08aa0a8}
State: [1] Stable
Last error: No error
Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
Writer Instance Id: {ee2c9173-92e7-455c-8f73-601647c0ddb2}
State: [1] Stable
Last error: No error
Writer name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
Writer Instance Id: {b1f60392-9dfd-4e3a-bda6-3dc2cb622ba4}
State: [1] Stable
Last error: No error
Writer name: 'IIS Config Writer'
Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
Writer Instance Id: {a328aede-78f0-448e-9c36-e8379e9fe2a8}
State: [1] Stable
Last error: No error
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {c39fa334-5c9d-4906-a3b5-33c3444948e6}
State: [1] Stable
Last error: No error
Writer name: 'NPS VSS Writer'
Writer Id: {35e81631-13e1-48db-97fc-d5bc721bb18a}
Writer Instance Id: {3c9c5584-b5fd-48cf-8541-0c8bfa585ca0}
State: [1] Stable
Last error: No error

Partition failed with the error: No space left on device

I used Boot Camp Assistant (for instaling Windows XP) and there was Partition error:
+*The disc cannot be partioned because some files cannot be moved.*+
+Back up the disk and use Disk Utility to format it as a single Mac OS Extended (journaled) volume. Restore your information to the disk and try using Boot Camp Assistand again.+
so I tried Yasu, verified permission, verified disk, and everything was ok, but in Disk Utility I was trying to split or change size of my disk but there is one error again:
+*Partition failed.*+
+Partition failed with the error: No space left on device+
but I have 64GB free space!
how must I "+Restore your information to the disk+" or what else can I do?
thanks!

arajs wrote:
I used Boot Camp Assistant (for instaling Windows XP) and there was Partition error:
+*The disc cannot be partioned because some files cannot be moved.*+
+Back up the disk and use Disk Utility to format it as a single Mac OS Extended (journaled) volume. Restore your information to the disk and try using Boot Camp Assistand again.+
so I tried Yasu, verified permission, verified disk, and everything was ok, but in Disk Utility I was trying to split or change size of my disk but there is one error again:
+*Partition failed.*+
+Partition failed with the error: No space left on device+
but I have 64GB free space!
how must I "+Restore your information to the disk+" or what else can I do?
thanks!
This is a standard error message.
If you would have checked into the bootcamp forum you would have instantly found the solution.
http://discussions.apple.com/forum.jspa?forumID=1244&start=0
All that error message means is that you do not have enough conguous disk space available. No big deal at all for an older system. You have bits of files strewn over the "free space."
The solution as you would find in the bootcamp forum is to clone your HD, using a file-file clone, then test the clone to be sure it is working and then to erase your HD and clone back.
Works every time.
Message was edited by: Theodore

Partition failed with the error: The target Core Storage volume is locked

partition failed with the error: The target Core Storage volume is locked
Hello everybody!
Please help me.
I'm using MacBook Pro (Retina, 13-inch, Mid 2014), Processer:2.6 GHz Intel Core i5, Memory: 8 GB 1600 MHz DDR3.
my computer i have divided in 3 drives: 1-Machintosh HD (Mac OS) 2-Bootcamp (Window OS) & 3-Data (drive for data storage).
I don't want to use Window OS on my computer anymore so I decided to delete drive Data (the third drive) & Window OS (the second drive).
I want my hard drive become a single drive back but when I was formatting, there were some problem display:
then i clicked ok and it displayed like this:
then i try to format or create new partition, it's nothing happen when press button apply.
my computer has storage space 256GB but now when it is happened like this my storage space is only 127GB only.
so please help me.. what so I do with this problem.
Thank you.!

arajs wrote:
I used Boot Camp Assistant (for instaling Windows XP) and there was Partition error:
+*The disc cannot be partioned because some files cannot be moved.*+
+Back up the disk and use Disk Utility to format it as a single Mac OS Extended (journaled) volume. Restore your information to the disk and try using Boot Camp Assistand again.+
so I tried Yasu, verified permission, verified disk, and everything was ok, but in Disk Utility I was trying to split or change size of my disk but there is one error again:
+*Partition failed.*+
+Partition failed with the error: No space left on device+
but I have 64GB free space!
how must I "+Restore your information to the disk+" or what else can I do?
thanks!
This is a standard error message.
If you would have checked into the bootcamp forum you would have instantly found the solution.
http://discussions.apple.com/forum.jspa?forumID=1244&start=0
All that error message means is that you do not have enough conguous disk space available. No big deal at all for an older system. You have bits of files strewn over the "free space."
The solution as you would find in the bootcamp forum is to clone your HD, using a file-file clone, then test the clone to be sure it is working and then to erase your HD and clone back.
Works every time.
Message was edited by: Theodore

P2V Failed with the Error : "Connection closed at byte 11086778368. Giving"

hi,
P2v gets failed with the error: Connection closed at byte 11086778368. Giving up
i checked the p2v log from /tmp/
10826600K .......... .......... .......... .......... .......... 12% 18.5M 60m9s
10826650K .......... .......... .......... .......... .......... 12% 22.0M 60m9s
10826700K .......... .......... .......... .......... .......... 12% 22.1M 60m9s
10826750K .......... .......... .......... .......... .......... 12% 21.5M 60m9s
10826800K .......... .......... .......... .......... .......... 12% 4.69K 61m26s
10826850K .......... .......... .......... .......... .......... 12% 15.7M 61m26s
10826900K .......... .......... .......... .. 12% 1.50K=8m52s
13:29:53 (19.9 MB/s) - Connection closed at byte 11086778368. Giving up
please suggest if anybody had come across with problem....

Raja Kondar wrote:
P2v gets failed with the error: Connection closed at byte 11086778368. Giving upDo you have enough drive space on the target server? You'll need at least 3x as much drive space as is available on the physical box you're converting. For example, if your physical server has a 72GB disk, you'll need ~200GB of free disk space on the Oracle VM Server.

IDoc failed with the error massaeg "Instance of object type could not be ch

Hi All
I am getting IDoc failed with the error massaeg "Instance of object type could not be changed"
Message type :PORDCR
Basic type : PORDCR05
Message no. BAPI003
Status : 51
All POs are get uploaded in SAP during Cut over activities only.
Please suggest on this.It will be a great help.
Thanks
Ajit

Hi
After uploading POs into SAP we are changing quantity and value in PO in Legacy system, and for this all IDocs are failed, subsequently these changes are not triggering to ECC.
Please help
Thanks
Ajit

ALC-PDG-001-000-ALC-PDG-010-015-The conversion operation timed out before it could be completed. Please report this error to the system administrator.

I am getting the error when trying to convert a word file to pdf.
My Adobe Lifecycle ES is installed on 2GM RAM . Is this the issue for the below error.
ALC-PDG-001-000-ALC-PDG-010-015-The conversion operation timed out before it could be completed. Please report this error to the system administrator.
Please provide me a valuable solution. I am new to Adobe ls es.

This is a forum for Acrobat desktop product. For LiveCycle, try this forum
http://forums.adobe.com/community/livecycle/livecycle_es/pdf_generator_es

Indesign CC packaging process fails with the error message "Unable to copy necessary file(s)"

When I try to package a file with a lot of links, the Indesign CC packaging process fails with the error message "Unable to copy necessary file(s)". I am able to make a PDF of the same file, but when packaking the process fails every time. The app does not crash, just gives an error message. What gives?
(I'm using a MacBook Pro Retina Display with 16 GB RAM, running OS 10.9 and all CC 9.1 updated with the latest patches).

@John – that's really strange… the thing with the file names depending on the file type. That could eleminate Mavericks a bit from the equation and put the weight more on InDesign CC.
Provided:
1. You give it a go with InDesign CS6 v8.0.2 and tests are showing it will work fine in this regard.
2. The same composite characters are present in both file types, the ai files and the PhotoShop ones. On a Mac OSX characters for files and folders can consist of "composite" components:
ü for example is a two component one: the u and the two dots above the u. On a machine with MS Windows, this is not the case…
InDesign CC was programmed from scratch for a 64 bit architecture. So it could be a severe bug in InDesign CC.
Maybe other readers in this forum could test for these cases…
Uwe

SQL Azure - Intermittent The wait operation timed out

I have a website engine which runs a few hundred "white label" sites. It's hosted on Azure with a SQL Azure Business database. Generally everything is fine - it all works and runs at a good speed.
However, throughout the day I get maybe 40 or 50 of the error:
System.ComponentModel.Win32Exception: The wait operation timed out
Please don't refer me to the connectivity blog at http://blogs.msdn.com/b/sqlazure/archive/2010/03/22/9982979.aspx as this seems to refer to problems where you just can't connect. My problem is that it's fine most of the time, but I still get these
intermittently.
This is sometimes on the main database, but we're also using a database for sessions and this gets the errors too. Both databases are on the same server.
I also get errors like:
An existing connection was forcibly closed by the remote host
and:
System.Data.SqlClient.SqlException: The service has encountered an error processing your request. Please try again. Error code 40143. A severe error occurred on the current command. The results, if any, should be discarded.
and, when evil bots are hammering the site:
System.Data.SqlClient.SqlException: Resource ID : 1. The request limit for the database is 180 and has been reached. See 'http://go.microsoft.com/fwlink/?LinkId=267637' for assistance.
Each website can potentially have a Google footprint of around 10,000 pages. The result it that bots are hitting the sites regularly, indexing lots of pages for hundreds of sites. I also have some worker roles doing data work. The database is clearly busy!
I am hoping to add 2 or 3 times the number of sites that I currently have to the "engine".
I am looking at efficiency where possible, but the sites are clearly under a fair load from bots and visitors.
My question is, will one of the upgrades from Business to S2, P1, P2 or P3 resolve these problems? The financial cost of these database instances stagger greatly so I wouldn't want to update and find I'm left with the same problems but am paying many times
more each month.
Thank you in advance.

Hello,
For Web/Business edition database, the maximum limit of concurrent requests is 180. Beyond this limit, you will receive error.
The Max woker threads for Standard(S2) is 100, you should upgrade your database to Permium tier.
The concurrent requests limit of premium database varies depending on the reservation size of a premium database. For example, for P1, the max worker threads is 200.
Reference:Azure SQL Database Resource Governance
Azure SQL Database Service Tiers and Performance Levels
Regards,
Fanny Liu
If you have any feedback on our support, please click here.
Fanny Liu
TechNet Community Support

Disk Erase failed with the error- Operation timed out

Similar Messages

Maybe you are looking for