Unable to upgrade to Big Sur - Not formatted as APFS

Question

Level 1

9 points

Unable to upgrade to Big Sur - Not formatted as APFS

Hi all,

I recently tried to upgrade to Big Sur from Mojave but ran into issues when it came to the install. I was met with the message 'This volume is not formatted as APFS' when trying to select which hard drive to install it on, and i'm unsure how to get around this.

I'm currently on a 2017 MacBook Pro and the hard drive is a Mac OS Extended (journaled). I've tried to go into disk utility and convert it to APFS, but the option is greyed out. I've also tried to do this via recovery mode but the option is still greyed out.

Is anyone able to help me? Any information much appreciated!

Thanks

MacBook Pro 13″, macOS 10.14

Posted on Jun 27, 2021 3:32 AM

Reply

Answer 1

Jun 27, 2021 4:29 AM in response to CharlesNicos

First, make sure you have a backup.

Second, which version of Mojave, exactly? I don’t remember exactly but I think there was an update of Mojave that would convert to APFS in the process (maybe 10.14.3? Or .6?)

Ultimately, this may be an opportunity to do the upgrade the right way. Create a Big Sur bootable installer on a thumb drive. Make a full Time Machine backup and preferably also a full bootable clone using CCC or SuperDuper. Start from the installer drive, completely erase the internal, formatting as APFS with GUID partition table. Install Big Sur and then migrate from your backup when asked. Elect to migrate only the accounts and not applications, settings or other files.

Reply

Answer 2

Owl-53

Level 10

105,771 points

Jun 27, 2021 4:07 AM in response to CharlesNicos

I will step aside for More Learned Contributor for ideas to work though this issue.

If that method will not work >> may have to Reformat the Entire drive as APFS then Install Big Sur from USB Installer. Then, restore only User Account from the most recent Time Machine Backup

Reply

Answer 3

Owl-53

Level 10

105,771 points

Jun 28, 2021 2:35 AM in response to CharlesNicos

Agree with both @ Matti H and @ Luis S. It would appear the only option is to backup what already exists then download the Full Installer of Big Sur >> Make a USB Installer >> Wipe the entire drive ( not the volumes indented and listed below ) and install Big Sur. Then Migrate Only Use account. Suggest not migrating Application etc as Mojave supported 32 bit applications, drivers and extensions which are Not Supported at all in Big Sir nor Catalina.

Reply

Answer 4

Owl-53

Level 10

105,771 points

Jun 27, 2021 3:57 AM in response to CharlesNicos

Have found an older Apple Forum on this very topic https://discussions.apple.com/thread/8381507 and check the posting from @leroydouglas on theNon-Destructive way to convert HFS to APFS

Reply

Answer 5

Jun 28, 2021 1:04 AM in response to CharlesNicos

Mojave installer should convert to APFS but for some reason it is still Mac OS Extended where Mojave updates don't work (it is possible to clone Mojave to Mac OS Extended and use it -- maybe this explains your setup or maybe the installer just failed to do the conversion?).

Anyway, follow Luis's advice to make a clean Big Sur install and restore from a backup.

Reply

Answer 6

Owl-53

Level 10

105,771 points

Jun 27, 2021 6:49 AM in response to CharlesNicos

As long as there is a very recent TM Backup. Otherwise - run the risk of disaster and starting from Scratch via USB Installer.

Reply

Answer 7

CharlesNicos Author

Level 1

9 points

Jun 27, 2021 6:46 AM in response to Luis Sequeira1

I have found another discussion on this here - https://discussions.apple.com/thread/8613766

Do you know if I follow those steps, will it work?

Thanks

Reply

Answer 8

Owl-53

Level 10

105,771 points

Jun 27, 2021 4:53 AM in response to CharlesNicos

There are a whole lot of updated between where you are 10.14.1 and 10.14.6 plus the additional Security Updates for Mojave.

https://support.apple.com/en_CA/downloads

As for the best procedure and steps to follow - perhaps @Luis S is better experienced to guide you. Have never every stuck to a .1 release - so can not reliably comment.

Reply