Can't erase or paritition primary internal HD: "wiping volume data to prevent future accidental probing failed"

Question

georgezma Author

Level 1

1 points

Can't erase or paritition primary internal HD: "wiping volume data to prevent future accidental probing failed"

Yesterday my computer (mid-2010 macbook pro) froze and after doing a hard reset my computer would hang during the bootup process.
I then started the machine in recovery mode and tried to do a Repair Disk using the Disk Utility.
The Repair Disk failed an indicated that the partition needed to be erased and recreated.
Why I tried to erase and recreate the paritition, I got the error message: "wiping volume data to prevent future accidental probing failed"
I am unable to create a new partition on my internal hd using Disk Utility. I keep on getting the error same message. I've already tried the fixes mentioned in https://discussions.apple.com/thread/4490281?start=0&tstart=0
I've tried creating the partition using Parted Magic but that fails as well
When I start the machine now in recovery mode, it goes to internet recovery.
I would suspect that this is a hd failure, but there are a couple of things that seem to indicate otherwise:
1. The Lion recovery parition is still visible in Disk Utility, and when I run a Verify Disk on it, everything is ok
2. Using Parted Magic, I've run a complete HD self test, and there are no errors reported

Any help would be greatly appreciated.

MacBook Pro, Mac OS X (10.7.5), Mid-2010 Macbook Pro

Posted on May 28, 2013 1:24 PM

Reply

Answer 1

Best reply

ds store

Level 7

30,695 points

May 28, 2013 1:39 PM in response to georgezma

Use command option r at boot, use Disk Utility to change the Partition > Option to MBR and MSDOS as the format and Apply.

Then click Erase and move the slider one spot to the right, click Erase and let it finish, if it fails the drive is bad. (bad sector check)

When done head to Partitions > Option GUID and OS X Extended J and click Apply.

Quit and install OS X from Apple's servers, reboot and log in, update and AppStore to upgrade to last OS X version if applicable.

Reply

Answer 2

georgezma Author

Level 1

1 points

Jun 4, 2013 4:48 PM in response to ds store

None of the above worked for me. Disk Utility kept on reporting errors.

I even got a new HD but the same error occurred.

It turns out that the HD cable had failed. I replaced the cable, reformatted my HD (since my earlier attempts had corrupted the partition map), and restored from a time machine backup.

Everything is back to normal :-)

Reply

Answer 3

pdr13571

Level 1

0 points

Jun 5, 2013 6:07 PM in response to georgezma

Sounds like I have the same problem as you georgezma.

Can you tell me where you got your replacement cable and the part number?

cheers!

Reply

Answer 4

georgezma Author

Level 1

1 points

Jun 6, 2013 9:43 AM in response to pdr13571

The part number is 821-0814-A. I ordered it from an amazon seller.

I followed these instructions: http://www.ifixit.com/Guide/Installing+MacBook+Pro+13-Inch+Unibody+Mid+2010+Hard +Drive+Cable/4304/1

Reply

Answer 5

Paul_Vic

Level 1

0 points

Feb 6, 2014 8:19 AM in response to georgezma

Hi there!

Sounds like i have similar problem but with my MacBook Pro 13' (9.2, mid 2012)

I have made some updates 500GB SSD Intel 520, and original kit of 500GB Toshiba 5400 (with Opticbay)

It is time to change kit Toshiba to larges one. My choise is Hitachi 7K1000 Travelstar 7200 rpm for 1TB (SATA III).

I try to set up new HDD to Opticbay, when using Disk Utility there is Error

"wiping volume data to prevent future accidental probing failed"

When i change it to original place for HDD - everything fine, but if SSD on Opticbay - MacBook does not see it.

I have read a lot of forums about this problem, and there some issues how to fix it - need to install updates for EFI Frimeware manualy, but suddenly it is impossible - when i try to install update there is Alert -

Actualy i realy need to help with that! Maybe some one?

Reply

Answer 6

tony0502

Level 1

0 points

Feb 18, 2014 11:17 AM in response to georgezma

Hi there!

I had the same issues as georgezma. Assumed the SSD was broken and got myself a brand new drive. To my disappointment the disk utility gave me the same error message when trying to format it. After reading this thread I understood it has to be the SATA cable that is the bugger, so I removed the cable from motherboard connector and plugged it back in. You can call it a wild shot but it worked. No error and mountain lion installation worked just the way it should from the internet recovery.

Thanks a lot guys and hopefully this will help some other unlucky SSD fans out there.

Reply

Answer 7

R1ck111

Level 1

0 points

Jul 2, 2015 3:46 PM in response to tony0502

Bizarrely this seemed to work! Although I am still going to order a new cable. There are parts of the cable which are prone to wear and can short out on the aluminium body, like the the part that hoes over the corner of the optical drive and underneath the HDD.

Reply

Answer 8

Aug 27, 2015 6:43 AM in response to georgezma

Did you use a reliable test to zero in on the HD cable?

I'm seeing the same error message when trying to format the older drive as well as a new one. I'd like to have some indication that the cable maybe at fault. I guess it's not the motherboard as the Laptop passes other diagnostics.

please recommend a test or software if you know of one.

Reply

Answer 9

Mar 12, 2016 10:49 AM in response to Paul_Vic

Hello! I have exactly the same problem! How did you decide this?

I have a same macbook and a same hdd, and my SMC and Boot ROM is wrong, and I don't refresh it, because Ysomite 10.105 not supported installing SMC and Boot Rom - this files can working only on 10.8.5.

Reply

Answer 10

Mar 12, 2016 10:53 AM in response to thinkSantosh

The Mac will happily and reliably Install or boot on any appropriate drive, including an external drive. A quick "litmus test " is to move the drive to an external enclosure and check its function from there. It may be a little slow, but it should work without issue.

Works as an external, fails as an Internal >> replace the cable.

Reply