There was one instance of the HDD not being bootable when in an external USB case.
#MBP VOLUME RESET UPDATE#
10.14's Disk Utility in Recovery Mode always seems to do some update to the boot sector, but otherwise everything checks out ok. Disk Utility's First Aid has found nothing and seems able to verify everything as ok. I was originally planning to order the iFixIt SATA cable kit, but given that only covers the primary drive bay but not the optical bay SATA, and the fact the issue crops up booting off either internally, doesn't it make there's something bigger than the mere SATA cable(s) going bad on the MBP? Is it just the SATA controller (if it's individually replaceable part on MBP 9,2), or am I looking at replacing at the entire logic board?īesides, are the HDD and SSD corrupted or not? So far the SMART status has always been verified (I know Disk Utility's SMART reporting is just that) when installed internally. Removed all the disks from inside the MBP, stuck them in external USB enclosures and booted up from there. How the heck could it affect file operation on an USB-connected external disk as well? Looking in Console, disk I/O and error -50 and journaling failure, etc., all over again. Then I tried deleting some file on an external USB drive. Well, all was peachy, until I tried to move a file on CLI in Terminal, something about "invalid argument".
#MBP VOLUME RESET WINDOWS#
So I re-commissioned the SSD in the optical bay as my boot drive, via TimeMachine restore, after resorting to using Windows to reformat the APFS volume because Disk Utility in Recovery Mode can't. Reading up on this SATA cable problem on the mid-2012 MBP on iFixIt and beyond, I got the impression it only affects the cable leading to the primary drive bay, since iFixIt only sells replacement kit for that bay. One reply on the Apple discussion board hinted to the OP that "error -50" might be due to SATA cable failure (leading to storage drive corruption) particular to MBP mid-2012 13", which was the exact model owned by that OP and the same as mine. There were 6-7 Disk I/O errors in Console since 2-3 hours ago, sprinkled with a few unable to write journaling info errors, and plenty of other seemingly related log messages. Looking around, I found I couldn't even make a new folder in Finder. I didn't bother investigating, since that's not my primary boot drive and working environment.įast-forward to two days ago, BBEdit suddenly started reporting failure to save a changed file, due to "error -50". I also installed fresh 10.14 Mojave on the SSD.Ħ-10 months later, the SSD in the optical bay booted into Mojave fine, but Finder would remain stuck at a black background with only the Dock loaded, forever. But fearing the SSD was failing, I re-commissioned the original stock Hitachi 500GB HDD in the optical drive bay as the primary startup drive.Īt some point later, I flipflopped the locations of the Samsung SSD and the Hitachi HD The SSD went into the slower SATA II(?) optical bay, and the HDD went into the SATA III(?) primary drive bay. Pretty certain SMART status in Disk Utility was verified. I don't remember the exact error messages in the Console app now, but vaguely recall that DriveDx might be reporting I/O error count being in the 300s and slightly incrementing sporadically. One day, two years ago, it suddenly crashed while in use, and it became unbootable from the internal Samsung EVO850.
My mid-2012 MBP is pretty tricked out with plenty of hardware upgrades.
0 kommentar(er)
