1

My Mac stops booting at spaceman_scan_free_blocks and then just hangs there indefinitely. I tried all the usual, repairing disk in recovery, etc but nothing works. Singleuser / safe mode not working too.

Anything I could do over command line? Mac is iMac 2017 running Ventura.

Any help appreciated.

Improve this question
13
  • I checked all of those. However, most of those are four hackintoshes. Apparently it occurs as a drive issue on some systems but not on apple’s ones. I didn’t do anything special, I was just using the system. However, I did recently install bitdefender antivirus on the computer. Bout two weeks ago. Also, the number of hits for this particular search is very low. Less than 20 in total.
    – mrmut
    Commented Apr 10, 2023 at 9:36
  • I’m voting to close this question because the use of macOS on non-Apple hardware is a legal grey area and as a result "Hackintosh" questions have been deemed off-topic.
    – Tetsujin
    Commented Apr 10, 2023 at 9:48
  • What? Did you read my comment?!? I have an actual Mac.
    – mrmut
    Commented Apr 10, 2023 at 9:52
  • I read your comment, hence the vote. Clarify in your actual question.
    – Tetsujin
    Commented Apr 10, 2023 at 9:53
  • You've tried resetting the SMC and NVRAM/PRAM, right? Do you have the original Apple drive, or have you replaced it with an aftermarket part? Can you Safe Boot it? Searching for ventura slow boot also brings results referring to a recent system upgrade.
    – Peregrino69
    Commented Apr 10, 2023 at 10:06

1 Answer 1

Reset to default
0

Unfortunately, there was no saving the installation.

In the call with Apple, they told me that there are some corrupted files on the system that can not be repaired, and they advised fully formatting and reinstalling the system.

Apple diagnostics, NVRAM/PRAM and SMC reset and other usual stuff did not help. I did not find command line tools that could scan and fix the disk in the spirit of SFC and DISM commands on Windows.

I used external USB SSD with mac installation to access files, copied them to another drive (2x) and then bombed the system and reinstalled it.

It is a hassle, but unfortunately nothing else would have helped.

I have reinstalled the mac using USB stick with latest Ventura on it and all now seems dandy. In retrospect, Windows machines seem much more repairable than Mac when c*ap hits the fan, but it is what it is.

I presume that the issue I faced was due to relatively old system (about 5y) that had been upgraded several times. If I have stayed on Catalina I originally used for years, this probably wouldn't have happened, for a while at least.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .