05-25-2017, 07:44 PM
I allowed the recovery partition to reinstall Mavericks on a guinea pig drive. It is booting from that drive, but there is still something thoroughly fscked up because I can't access the other internal drive I put back in or the backup drive that I reconnected. I don't have permission to even open them and see the contents. Trying to fix that using Get Info results in nothing: it stays stuck on the "fetching" part of the ownership options. Everything in the list shows "custom" access and my user name is not listed. If I add my user (it's an admin account) to the list, it gets "custom" access automatically and that can't be changed in any way.
Never had this problem before. I repaired permissions on the drive that is now booting, but that did nothing for the other drives' permissions issues. The internal drive doesn't show as an option in the startup disk prefs. Not even greyed out. Disk Utility says there is nothing wrong with it.
Just tried installing another boot drive (Yosemite) and attempted to boot from it. No dice: it seems to be starting up, and stalls after the progress bar has reached about the 30% mark.
The old drive with the reinstalled Mavs is the only one that fully boots. Running the hardware test disk now.
Update: Hardware test finds no problem. I tried running the extended test, but it timed out, and then couldn't be stopped. Rebooted and ran the short test, which says everything is hunky-dory.
Never had this problem before. I repaired permissions on the drive that is now booting, but that did nothing for the other drives' permissions issues. The internal drive doesn't show as an option in the startup disk prefs. Not even greyed out. Disk Utility says there is nothing wrong with it.
Just tried installing another boot drive (Yosemite) and attempted to boot from it. No dice: it seems to be starting up, and stalls after the progress bar has reached about the 30% mark.
The old drive with the reinstalled Mavs is the only one that fully boots. Running the hardware test disk now.
Update: Hardware test finds no problem. I tried running the extended test, but it timed out, and then couldn't be stopped. Rebooted and ran the short test, which says everything is hunky-dory.