Lately I've noticed that there was a certain volume that cannot be mounted on disk utility. Everytime I try to mount it I always get the same error message.
I've ran First Aid on that particular volume at least 5 times so far but to no avail, as Disk Utility doesn't seem to find any error when running First Aid on it. Is there a way to fix this?
[Edited by Moderator]
iMac 21.5″, macOS 10.15
Yes, that is correct. It is the one you have highlighted in the image.
Yes, that is correct. It is the one you have highlighted in the image.
jagcraed40 wrote:
Just to be clear, will this require me to erase and/or delete "disk1s4" right? Despite being labeled as a corrupted System volume? I seem to have another System volume under "disk1s9" that looks to be in working condition according to Terminal.
To have at least nine volumes/partitions on this drive indicates there is more going on here than the Disk Utility GUI app is showing (it is known to hide partitions from view if they are unknown). More than likely you still have some remnants hiding behind the scenes from your experiments with OCLP. In fact, I check my Catalina system and the "Update" volume should not be showing up within Disk Utility as it should be hidden from view. My guess is this "Update" volume belongs to another version of macOS or the hacked version of a later version of macOS did something to this "Update" volume.
FYI, to get a better view of the drive's current layout, you can use the following command:
diskutil list internal
Personally I want to wipe the entire system just to be safe & to get rid of any remaining traces from the OCLP experiment. I would first perform a PRAM Reset to get rid of any OCLP settings that may still exist there (hold the PRAM Reset for at least three chimes if possible). Then boot to Internet Recovery Mode (Command + Option + R) or to a bootable macOS Catalina USB installer to erase the whole physical drive followed by selecting the "Install Catalina" option. I would highly recommend creating a bootable macOS Catalina USB installer now while you still can just so you have more options in case Internet Recovery Mode gives you problems since most people don't have access to another compatible to make the USB installer once the computer has been erased.
My SATA Internal Physical Disk, i'm guessing for clarification, correct?
Correct.
Also, another possibility for the unknown volume is file system corruption possibly caused by a failing Hard Drive.
Hmm, I had a feeling that is what has happened.
At this point, you have already "broken" your computer, and your only option will be to completely erase it, and re-install macOS.
Since you have an Intel-based Mac, you will need to boot it up in 'Internet Recovery Mode' to get the restoration process started. Ref: Use macOS Recovery on an Intel-based Mac - Apple Support. Specifically, use the following key combination: Option-Command-R
While in Recovery Mode, use Disk Utility to completely erase the Mac's system drive.
Then install a fresh copy of macOS:
When you use Disk Utility in Recovery Mode, you want to be sure to select the physical drive, not any volume, to completely erase the drive.
Your decision to use OpenCore again, basically "broke" your Mac. There is no value to save any volume on that drive. Besides the system volume does not contain any user data. macOS Catalina is the latest version of macOS that Apple approves to be run on your 2013 iMac, and what I suggest that you install.
Based on what you’ve described, it sounds like `disk1s4` is either a corrupted or orphaned APFS volume in the container that’s no longer serving a functional purpose but hasn’t been removed cleanly. The fact that it shows 0 KB used and can’t be mounted despite no errors in First Aid is a strong indicator that macOS doesn’t know what to do with it anymore, but also doesn’t consider it a disk error.
I suggest that you try the following to get this resolved:
If you determine that this volume is NOT needed, we can remove it with this command:
Important: Only do this after verifying it’s not used by macOS. Don’t delete any volume labeled as `Preboot`, `VM`, `Recovery`, or associated with `Macintosh HD`. Doing so, will require a new install of macOS.
Since you haven't provided any details on what led up to this issue, and you’re on Catalina, this is likely related to the split system/data volumes and how updates handled that structure. These "ghost volumes" can show up if a system update gets interrupted or if a Time Machine snapshot cleanup leaves something behind.
Update:
While it runs through with no problem with Disk Utility, I noticed there were warnings and errors in the first aid report listed here:
Running First Aid on “” (disk1s4)
Verifying the startup volume will cause this computer to stop responding.
Verifying file system.
Volume is already unmounted.
Live mode required because other APFS Volumes in its Container are mounted.
Using live mode.
Performing fsck_apfs -n -l -x /dev/rdisk1s4
Checking the container superblock.
warning: container has been mounted by APFS version 2332.101.1, which is newer than 1412.141.3.7.2
warning: disabling overallocation repairs by default; use -o to override
Checking the EFI jumpstart record.
Checking the space manager.
Checking the space manager free queue trees.
Checking the object map.
Checking volume.
Checking the APFS volume superblock.
The volume Macintosh HD was formatted by storagekitd (2332.101.1) and last modified by apfs_kext (2332.101.1).
error: apfs_sb at apfs_fs_index (3): apfs_incompatible_features has unsupported flags: (0x20)
Volume superblock is invalid.
The volume /dev/rdisk1s4 could not be verified completely.
File system check exit code is 0.
Restoring the original state found as unmounted.
Operation successful.
I don't know why this is the case, as strange as it may sound.
On the other hand, running through terminal, it seems to be listed as an error and listed as System in the parenthesis
I seem to have a second System listed as disk1s9 however.
Okay, I actually managed to erase the corrupt system with no issue to my iMac, thankfully. I'm sure that concludes my problem, doesn't it?
And as for the internals, I've ran through with Terminal and it only shows 6 volumes under that particular disk.
So far the numbers are sorta the only oddity I can find, though i'm sure that's entirely to do with the reinstall of Catalina on my system than anything else.
Disk Utility doesn't seem to find any issues with my Hard Drive however.
For reference, I kept copies of the results of using 'diskutil list internal' for various versions of macOS over the years, and this is what I have for macOS Catalina. It looks like a match to your results ...except for the 'Update' volume.
Again, without knowing what led up to this issue, I have no idea how these additional APFS volumes were created or why. As such, all I can recommend it that you completely erase this Mac's system drive, and then, install a fresh copy of macOS.
Per chance, are you using some third-party software to allow it to run a version of macOS that is not designed to run on it?
This may have been a bad idea, but last month I attempted to use OpenCore Legacy Patcher to install Sequoia onto my iMac. However, I didn't like how slow it was on my computer, so I ended up erasing my hard drive to do a fresh install of Catalina in Recovery Mode.
Even when I still had Sequoia on it, I noticed the disk was greyed out. Is there a certain guide perchance you can provide me with on how to erase my system drive entirely? I'm sort of nervous about potentially breaking my computer.
Just to be clear, will this require me to erase and/or delete "disk1s4" right? Despite being labeled as a corrupted System volume? I seem to have another System volume under "disk1s9" that looks to be in working condition according to Terminal.
My SATA Internal Physical Disk, i'm guessing for clarification, correct?
Could not mount “disk1s4”. Late 2013 21.5 inch iMac running on Catalina