Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

smartypantzzzz

macrumors newbie
Original poster
Oct 29, 2021
5
1
Up front, I will confess I broke many of my own rules for doing this kind of thing, and what I tried to do was probably Dumb. Live and learn.

So, I was upgrading an old MacBook Air to Big Sur and I just assumed everything would work, since I have had such good success with these types of projects in the past. Normally I would never do this on a machine (wait for it) without a backup, but this machine didn’t seem to have much on it of real value, so worst case I clean install and all is good.

As it turns out, there is one thing of moderate value that it would be nice not to lose. I have resigned myself to losing it, but thought I would post and see if anyone has any suggestions for things I have not thought of.

Basically, during the final reboot of the upgrade, the machine hangs. I can boot to safe mode and operate out of there (with limited functionality) but I had to create a new non-admin user account to do it.

I can boot to single user no problem. If I proceed to try and get to a normal boot from single user mode it pretty much hangs right away, and this kind of matches the general timing of it hanging when booting normally. So it seems whatever happens right after the single-user mode part of the boot process is where the problem lies.

Is it worth trying to mess around with things in the normal boot process to try and get it to succeed? If so, what should I try, and are there any resources for doing this?

I have reset the NVRAM and checked the disk for errors.

My real problem is I need to copy some files that I do not have permission to copy.

When I try and access the files (from my newly created account in safe mode), it rejects the username and password that worked to login to the computer pre-upgrade. The username in the Users directory is different than what I used to login to the machine normally. I never used the username in the Users directory, always another username. I think that it is possible that looooong ago Apple used to ask to name the machine and and created the Users directory name based on that. Then you would setup a “username” and somehow it managed the complexity of this. And I should add that this user account has been migrated at least once before, and was originally setup on a… Powerbook. :)

So, I just need to access one file. I tried imaging the whole disk, but it only imaged the data that was not owned by the account in question that owns the file I need access to. When I try copy/paste it asks me for Administrator credentials before starting the operation.

I am reasonably comfortable with command line stuff, the reason I migrated to Mac was because they had adopted BSD as their core.

Anyways, appreciate any tips or pointers, and even abuse. Writing this has been at least therapeutic.

Thanks ~
 
There have been some reports that the Mojave to Big Sur updates process has been broken for some time. For example:

----------
Edited to add the text from the link above:

Posted on Tue. Oct. 5, 2021 00:31 EDT
macOS update failures

There’s a severe problem updating from macOS Mojave 10.14 (which Apple no longer supports and thus has security risks) to macOS 11 Big Sur (which Apple pushes for computers it supports).


The macOS Mojave to Big Sur upgrade is causing problems for some users The progress bar is getting stuck, leaving the system in an unbootable state. The user is locked out of their data.

I recommend the following workaround until the issue is found or a fix is deployed by Apple
Mojave –> Catalina –> Big Sur

This sounds like the issue @lapcatsoftware experienced in August. Crazy to imagine it is still a known issue since that is the suggested upgrade path for the now unsupported Mojave.

yes, it hit me last Sunday by upgrading my Mojave to 11.6. The installer progress bar stuck at the last 5%. Nothing helped: not hard reboot, not to reinstall via Recovery-Mode. Finally I deleted the SSD, did a fresh 11.6 install and copied my Data from the Backup.[/I]
 
Last edited:
Screen Shot 2021-11-01 at 6.24.53 AM.png
 
  • Wow
Reactions: KaliYoni
Can confirm that.

Straight Mojave -> Big Sur upgrade can end up with complete wipe and fresh Big Sur install. All possible workarounds to avoid wiping eventually failed. Lot of time and some of locally stored user data was lost, because it was impossible even to "downgrade" to Catalina after that, because problem persisted - user accounts were lost and at best it was possible to boot to safe mode in "there is no admin user" state, which obviously did not solve anything either (beside ability to copy local user data to external device).

This situation is a warning to users, who want to delay major updates to a point when second major update comes out.
 
  • Like
Reactions: Wandering Wastrel
There have been some reports that the Mojave to Big Sur updates process has been broken for some time. For example:

----------
Edited to add the text from the link above:

Posted on Tue. Oct. 5, 2021 00:31 EDT
macOS update failures

There’s a severe problem updating from macOS Mojave 10.14 (which Apple no longer supports and thus has security risks) to macOS 11 Big Sur (which Apple pushes for computers it supports).


The macOS Mojave to Big Sur upgrade is causing problems for some users The progress bar is getting stuck, leaving the system in an unbootable state. The user is locked out of their data.

I recommend the following workaround until the issue is found or a fix is deployed by Apple
Mojave –> Catalina –> Big Sur

This sounds like the issue @lapcatsoftware experienced in August. Crazy to imagine it is still a known issue since that is the suggested upgrade path for the now unsupported Mojave.

yes, it hit me last Sunday by upgrading my Mojave to 11.6. The installer progress bar stuck at the last 5%. Nothing helped: not hard reboot, not to reinstall via Recovery-Mode. Finally I deleted the SSD, did a fresh 11.6 install and copied my Data from the Backup.[/I]
Thanks so much for this info, *very* helpful. You are a Saint!
 
Can confirm that.

Straight Mojave -> Big Sur upgrade can end up with complete wipe and fresh Big Sur install. All possible workarounds to avoid wiping eventually failed. Lot of time and some of locally stored user data was lost, because it was impossible even to "downgrade" to Catalina after that, because problem persisted - user accounts were lost and at best it was possible to boot to safe mode in "there is no admin user" state, which obviously did not solve anything either (beside ability to copy local user data to external device).

This situation is a warning to users, who want to delay major updates to a point when second major update comes out.

Wow, thanks for sharing. Very helpful. I am not giving up on recovering the data yet, but you paint a pretty dire picture.

So yeah, now that I am on Big Sur I am trapped here, pretty funny.

You would think Apple would modify the process to detect <starting OS> and maybe suggest a different approach based on how far away you are from the current version, esp with known issues.

I will accept some blame for being so negligent on not upgrading the machine sooner, but honestly I was on a stable OS that was being maintained by Apple through software updates, and I didn't feel the need to "upgrade".

Thanks again for for info and advice, I really appreciate it!
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.