- #Internal hard drive for macbook pro 13 mid 2010 install#
- #Internal hard drive for macbook pro 13 mid 2010 upgrade#
- #Internal hard drive for macbook pro 13 mid 2010 mac#
#Internal hard drive for macbook pro 13 mid 2010 upgrade#
Interested in building your own site? Fast, reliable, professional web hosting at an affordable price! Видео MacBook Pro 13" 2010 Hard Drive Upgrade Tutorial канала JayPlaysDotCom Please subscribe and watch my upcoming videos on this sleek notebook. I will most likely go for a Western Digital WD7500BPVT 750GB 5400RPM hard drive next time. Any damage you cause to your system is your own responsibility.Ĭlick on the link to purchase the Apple MacBook Pro MC374LL/A 13.3-Inch Laptop on Amazon at lower price than retail: The main point of the video is to show the actual physical steps for the replacement.ĭisclaimer: Please read Apple's warranty. This is a major downgrade to me, personally, even at the slight performance increase, so purchase this hard drive at your own risk. I think I covered everything in the video, but if you have any questions, leave a comment.īTW, the hard drive replacement seemed to have cut my battery life by about 3 hours. But this is an old machine, and I'm willing to get my hands dirty here to find a way out.I had to fast-forward parts of video, to skip the tedious parts (unscrewing, re-screwing). Lastly, this could very well be a hardware fault which I might have caused due to my troubleshooting step – I'd never know i guess. I think my brain's reached the saturation level unless someone can point out something that I haven't tried that might help. So, not really sure where to go from here.
#Internal hard drive for macbook pro 13 mid 2010 mac#
So assuming the next step would be to initialize the disk, ran the following commands.ĭiskutil partitiondisk disk0 JHFS+ Mac 100% Not sure if that has anything to do with it. The other weird thing I found is when I type the command (diskutil list), I get this long list going upto /dev/disk21 and all of them are disk images. So yeah, that's where I am after 5 days of troubleshooting – pretty much nowhere! I am not a mac genius, but I know things. (image below).Īfter which I ran the following command (gpt -v destrory /dev/disk0) with the intention it might clear off the partitioning, I guess I was wrong because now I do not have a Macintosh HD in Disk Utility, and the internal Disk says 'Uninitialized' (image below) However when I went to erase by trying the command (diskutil eraseDisk JHFS+ Mac /dev/disk0), it threw the error – 69825: Wiping volume data to prevent future accidental probing failed. Killed them both.Īnd then was able to force unmount the disk via terminal (diskutil unmountDisk force /dev/disk0). Many more hours of research, and I found out by typing the command (lsof|grep 'Volumes/Macintosh HD') that there were two processes running – 169 and 197 (see image below).
#Internal hard drive for macbook pro 13 mid 2010 install#
I also managed to find another mac and download a genuine High Sierra and make a bootable out of it, but when I went to install it, same error – Permission Denied. So, now tried internet recovery from another Wifi, which took me further only to throw an error before install began saying Permission Denied.
An SMC Reset fixed that issue, and it logged me into my OS which is again the corrupted one.
From this point onwards, Mac started to get stuck at the apple logo with progress bar at 100% and I waited 24 hours, and it still did nothing. As I didn't have another mac at the time, read an article somewhere to download a High Sierra image from a link (not apple store) and using TransMac to create a bootable – which was a mistake, because I was able to install that OS but it started throwing random errors and was unresponsive as well.
Tried internet recovery but it gave an error -2002F. Same error when trying First Aid too.įrom here, it went really dark. I could not erase my internal Macintosh HD – the error said it could not unmount it.
So, restarted and went into Recovery mode, and then disk utility. I thought it might be a good idea to wipe everything clean, and reinstall a fresh copy of High Sierra. Bit of background – the whole problem began with the mac being really slow and unresponsive.
0 kommentar(er)
