Macbook Pro Disk

[Darci Carlton]

Onmy Macbook Pro 2015, I had installed Ventura through a hack called Opencore Patcher, but after an update to 13.*.6, the graphics drivers were broken, so after reinstalling Opencore Patcher itself, it completely broke the system. So I booted using usb, copied my files and reinstalled Mojave (which flies twice faster as Ventura on the same machine so I will not upgrade again), but I had forgotten to repartition the hard disk.

I could get rid of Opencore's reliquate bootloaders by deleting its EFI's after mounting them manually from Terminal, but now I would like to get rid of this Incompatible message without reinstalling the whole system. I already spent some time reinstalling all my apps, accounts (Google's and Apple's are ... not to be taken lightly) and all my Macports so I would like to avoid the hassle and find a way to this from Terminal in Mojave.

Anyways, if your disk happens to be ExFAT, and you remember improperly removing the disk the last time you used it, chances are, fsck is holding it hostage (metaphorically, of course). fsck is trying to repair the disk, but it will stall forever, so you want to launch Disk Utility, and the Terminal. Try to mount the disk, and switch to Terminal and write sudo pkill -f fsck. The disk will mount in read-only mode, and from there, you can repair it with First Aid in Disk Utility. This won't work for non-ExFat drives, as macOS manages them differently.

This happened for me on a Big Sur MacOS, clicking the 'First Aid' option in Disk Utility kept giving me this same error. What ended up working for me was restarting my laptop, then continuously trying 'First Aid' until one time it suddenly didn't give me the error, and after waiting about 20minutes the drive mounted properly. I don't think I did anything differently other than trying over and over again.

This still isn't working for me. I don't understand what this "and the Terminal" means. When I try to mount my drive, the error that is the title of the forum comes up and it appears I am at a dead end. I tried to repair the drive, and it seemed to do something (with a bunch of green check marks) saying it was fixed, but it still won't open or be recognized by my finder or desktop. If anyone is able to walk me through this, I would be very appreciative.

This time, though, even after running First Aid in Disk Utility, the drive is still registering as Read-Only, which I'm not sure how to fix! Anyone have any suggestions or have experience with this? The drive does have about 1.5 TB of data on it, and it hasn't completely backed up to my cloud storage yet, so ideally not anything that requires reformatting (fingers crossed)

The quickest way to sort out problematic exfat drives I've found is to mount them in a windows environment (either in a virtual machine or on actual windows computer) and repair them from there. Disk first aid takes a loooong time on larger drives.

Thankyou @jkrosado and @calif94577. It worked out but without hitting the enter button, magic! Also the exfat formatted LA CIE 5GB drive worked on BigSur before then after upgrading to Monterrey it didn't show up.

I tried that command on the Terminal, the 'First Aid' option on Disk Utility said everything was OK and then same Could not mount drive error, I restarted , tried it few times, same error. Dont ask me why but what worked was Logging Out my Mac user and logging again with the same user, super weird. There's defo some bug on Monterey and the external drives / Time Capsule Mac application...

Hi everyone! I have followed the steps and Disk Utility is running first AID. I have got a SEAGATE 2TB ExFat formatted...but first AID is running "Checking file system hierarchy." and it has done so for 24 hours...is that normal for a 2TB? I am tempted to quit it....

Hi there, My external HDD (LaCie Rugged 4 TB, MacOS Extended (Journaled) formatted) doesn't show up on the desktop. It is visible in Disk Utility but I can't repair it. The system returns com.apple.DiskManagement.disenter error 49244..

Checking file system and repairing if necessary and if possible.Volume is already unmounted.Performing fsck_hfs -fy -x /dev/rdisk6s2Executing fsck_hfs (version hfs-583.100.10).Checking Journaled HFS Plus volume.Invalid B-tree node sizeThe volume could not be verified completely.File system check exit code is 8.Restoring the original state found as unmounted.File system verify or repair failed. : (-69845)

And finally the size. However I get a message that states "The volume OS X Base System" is not journaled. As a result it can not be resized. To enable journaling...." but the "Enable Journaling" selection is not selectable

BTW, you keep referring to something called the Base System disk. Usually, that is not an actual disk, but an installer or installer disc that you may find below the display of "real" disks in Disk Utility. Here is an image of the device list in Disk Utility:

In this photo were you able at that point to click on the Erase button in the Disk Utility toolbar? i cannot tell what is ghosted or not. This is image 4. And, please don't post any images except what I specifically ask for because it's a lot of unnecessary scrolling.

I wanted you to see what the display might look like. Yours will not look like mine because I have several drives mounted both internally and externally. You have a single drive system, I assume. If you do not see the Recovery HD, but you have booted from it, then you have a CoreStorage managed drive.

Press RETURN. If this succeeds (no errors returned) then Quit Terminal. Select Disk Utility from the Utility Menu. Now, see if you can do the steps to reinstall OS X. This time First Aid should work when the disk is already unmounted.

Hi, I have similar issues with 2 of my hard drives, WD passport and elements on my M1 MBA.. These 2 drives work fine with my older MacBook Pro late 2013 on Mojave and my Windows setup but cannot seem to work well on Big Sur..

Once I updated to Catalina it started showing up every few days when the computer was asleep. I might see 1 or 2 messages when I logged on in the AM.I updated to Big Sur hoping this bug was resolved and now I see 10-20 of these messages upon awakening the computer. If I eject the drive before putting the computer to sleep it will still result in 10-20 messages.

I have spent hours researching this issue and tried every tip/fix I have seen. There are simply no energy settings, cable, reformatting, resetting PRAM etc etc. that resolves the issue. What I have learned is:

Every time I try to copy a directory from my external USB drive to the SSD on my Mac, the disk ejects and the copy fails. It is 100% reproducible. The USB disk is connected via a USB hub with separate power supply to ensure enough power. I can access the disk, read from it and copy files to it. I use it with Logic to keep my sound library on, and that works fine.

Tried different cables (even thunderbolt certified), different hard drive caddies, tried different ports, tried disconnecting everything except those drives, tried different hard drive brands, restarted several times, ran first aid, reinstalled the OS, etc

Looked all over google about the error 100006 and some random errors trying to erase, partition or reformatting the drive.They get ejected at random, quite often as soon as I plug them they keep getting ejected so I can't even do anything on them at all.

ADATA SX8200 PRO and Toshiba NVMe M2 drives. Tried several brands for hard drive caddies. Seems like this is a long time error on such a renowned brand, how come this hasn't been fixed?Lots of threads and no solutions! Some manage to get them working, others never do!

Same here. Seagate 2TB and 4TB on MacBook Pro 2018 running Big Sur 11.6. The 4TB ejects every now and then, but of course always at the wrong moment, like when finishing a complicated video edit. The 2TB disk (my Time Machine disk) is the real PITA, ejecting umpty times a week and in the process screwing up Finder and other apps that are running, only to be fixed by forced reboot. Started with Catalina. Disks are ok when checked in Disk Utility and work fine on older MBP running High Sierra. Apple, please fix ASAP!

It is helpful to know I'm not the only one whose drives are spontaneously ejecting. I've been trying different connections and it is occurring on multiple drives. Mostly USB 3.0. These are all LaCie drives and on at least one if I hookup via Firewire through Thunderbolt, it seems stable. At least one drive has become corrupt due to these issues. I hope Apple can understand that the only thing that changed was their software/hardware. This started for me after 'upgrading' to an iMac M1 and Big Sur. I remember the days when Window machines were this unpredictable, change is the only constant.

After dealing with the dreaded "disk not ejected properly" error for months while running Big Sur 11.6 I think i have finally seen the light at the end of the tunnel. I upgraded macOS to Monterey 12.0 this week and my Mac Pro (Late 2013) seems to have stabilized. While the "eject" continued to show up initially after I completed the install, the "eject" errors seem to have disappeared 100%. My setup was related to the use of a Promise Pegasus R6. I tried everything from cable swaps, to firmware updates, to Mac Power Management settings. Now I can only hope that future updates (and I know there will be many) to Monterey will not bring back the dreaded "eject" error.

When trying to quit Todoist app, Command + Q also caused error notification. Also could not close Todoist. Force Quit Todoist. Restarted. Eject error notification appears to be occurring less but not solved.

It seems the problem is that Big Sur and Monterey are using more power than Catalina, and not delivering enough power to the hub to keep the hard drive alive. In my case Monterey crashed every time Time Machine finished which was driving me mad. The solution is to use a powered hub, no disk ejection since I installed one (or you could throw away the perfectly good hub and hard drive and buy a powered hard drive, sending Apple the bill).

3a8082e126