Issue with read/write access to internal SSD - possibly linked to Open Core Patcher upgrade

Messages
1,848
Name
Brian
Edit My Images
No
So.... until recently my 2012 iMac was running Catalina and would not upgrade due to its spec.
I was considering an upgrade to a Mac Studio (still am, to be honest) but thought I'd first try using the Open Core Legacy Patcher to upgrade to Monterey. It appears to have gone successfully but I now have an issue that i suspect is related.

I was doing a lot of hard drive housekeeping and back-up work prior to doing this, but postponed tidying up an internal SSD that I knew I had duplicate files on. Went to tidy it out today and I can't delete anything from it - no right-click/move to bin option and files dragged to the Trash don't go into it. It also appears that I can't write to it either.

Tried going onto the Get Info screen for the drive and unlocking the padlock - I'm logged in as myself and it shows I have read/write access. If I try to change to give all users R/W access I get a pop-up saying "The operation can’t be completed because you don’t have the necessary permission."

Now, I am no expert but I suspect I know the reason for this, just not how to fix it....

By way of necessary background, my iMac is (was) a Fusion model. First time it broke down just outside the warranty Apple replaced the Fusion drive. Next time I took it to an independent Apple repair specialist. They installed a new 2TD internal SSD. They also (if memory serves me right) told me that they'd left the original Apple SSD (part of the Fusion drive) as it appeared to be fully functional, thereby giving me another internal SSD (capacity 120GB). I think they told me that they'd installed the OS on the new 2TB SSD. Whatever has happened since (probably something I have done when trying an earlier OS upgrade), both SSDs were showing as APFS Volumes in Disk Utility and both showed macOS 10.15.7 installed. On boot/restart previously I was never given an option to select the startup disk, clearly one of these was seen as a default.

During the Open Core Legacy Patcher upgrade process, I selected the 2TB SSD (labelled MAC SSD) as the location to install Monterey. Now on a restart I have the option to boot either from the Apple SSD or the MAC SSD, although it defaults to the newer OS (on MAC SSD) if I do nothing.

So I suspect that the fact that the 120 GB Apple SSD is being seen as a system disk is linked to my inability to delete from it - am I right? Doesn't explain how I managed to write the files to it in the first place though...

I haven't tried using Disk Utility to reformat the 120GB Apple SSD (don't currently have the nerve to even try...).

I will repeat (as should be obvious by now) that I am no expert.

Any informed advice would be greatly appreciated.

Thanks in advance.

Screenshots attached might help inform discussion. The final one is from NTFS for Mac, just to show how it 'sees' the Apple SSD.
 

Attachments

  • Screenshot 2022-12-08 at 15.05.20.png
    Screenshot 2022-12-08 at 15.05.20.png
    37.8 KB · Views: 1
  • Screenshot 2022-12-08 at 15.05.12.png
    Screenshot 2022-12-08 at 15.05.12.png
    38.4 KB · Views: 1
  • Screenshot 2022-12-08 at 14.44.57.png
    Screenshot 2022-12-08 at 14.44.57.png
    55.9 KB · Views: 1
  • Screenshot 2022-12-08 at 14.45.17.png
    Screenshot 2022-12-08 at 14.45.17.png
    79.8 KB · Views: 1
  • Screenshot 2022-12-08 at 17.53.36.png
    Screenshot 2022-12-08 at 17.53.36.png
    24 KB · Views: 0
  • Screenshot 2022-12-08 at 17.57.32.png
    Screenshot 2022-12-08 at 17.57.32.png
    25.4 KB · Views: 0
Last edited:
Thanks for the suggestion Kev.

I was loath to try the suggestion, due to warnings on the OCLP site (see attached screenshot) about messing with the SIP settings. Having watched the video, I thought it would do no harm to at least have a peep using the 'csrutil status' command - I was wrong, it bricked the installation!

Got it back again by booting into Catalina using the Apple SSD and re-applying the patch.

Having just had this experience I was actually quite relieved to be able to boot into Catalina this way, and then rebuilding the OCLP and re-accessing the Monterey OS. Yes, I could have restored from TM backups but this was handier.

So I can see the benefit of what is effectively a dual-boot system. particularly if the OCLP/Monterey install proves to be unstable.

My OCD means that I'd still like to clean up the Apple SSD to get rid of those superfluous files, but I suppose it's no biggy.....
 
Thanks for the suggestion Kev.

I was loath to try the suggestion, due to warnings on the OCLP site (see attached screenshot) about messing with the SIP settings. Having watched the video, I thought it would do no harm to at least have a peep using the 'csrutil status' command - I was wrong, it bricked the installation!

Got it back again by booting into Catalina using the Apple SSD and re-applying the patch.

Having just had this experience I was actually quite relieved to be able to boot into Catalina this way, and then rebuilding the OCLP and re-accessing the Monterey OS. Yes, I could have restored from TM backups but this was handier.

So I can see the benefit of what is effectively a dual-boot system. particularly if the OCLP/Monterey install proves to be unstable.

My OCD means that I'd still like to clean up the Apple SSD to get rid of those superfluous files, but I suppose it's no biggy.....
OMG sorry about that, did not think it would brick the install.

I use a hackintosh which uses OC and updates of OS most time are okay as long as you have a backup of the drive and the EFI where OC sits,
 
OMG sorry about that, did not think it would brick the install.

I use a hackintosh which uses OC and updates of OS most time are okay as long as you have a backup of the drive and the EFI where OC sits,

Ah no worries, it was worth checking out.

I forgot to attach that screenshot I mentioned, here it is now.
 

Attachments

  • Screenshot 2022-12-08 at 22.41.19.png
    Screenshot 2022-12-08 at 22.41.19.png
    246.9 KB · Views: 2
Back
Top