Suddenly can't boot
0
votes
1
answer
149
views
I was using my 13 inch Macbook Pro (mid 2012) as normal when it suddenly became really slow and it became so unresponsive I just forced it to shutdown by holding down the power button. After that I couldn't boot it off of any partition as there was a question mark folder on boot.
I launched the latest version of internet recovery mode by using option-command-r while restarting the computer. After that I used the Terminal and typed
diskutil list /dev/disk0
and got:
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *525.1 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_APFS Container disk1 524.9 GB disk0s2
followed by diskutil info /dev/disk0
with output:
Device Identifier: disk0
Device Node: /dev/disk0
Whole: Yes
Part of Whole: disk0
Device / Media Name: Crucial_CT525MX300SSD1
Volume Name: Not applicable (no file system)
Mounted: Not applicable (no file system)
File System: None
Content (IOContent): GUID_partition_scheme
OS Can Be Installed: No
Media Type: Generic
Protocol: SATA
SMART Status: Verified
Disk Size: 525.1 GB (525112713216 Bytes) (exactly 1025610768 512-Byte-Units)
Device Block Size: 512 Bytes
Read-Only Media: No
Read-Only Volume: Not applicable (no file system)
Device Location: Internal
Removable Media: Fixed
Solid State: Yes
Virtual: No
Hardware AES Support: No
followed by fsck_apfs -y /dev/disk0
and got:
** Checking the container superblock.
warning: checkpointsuperblock disagree for xp 203
warning: container has been mounted by APFS version 1412.141.3.7.2, which is newer than 1412.141.1
warning: disabling overallocation repairs by default; use -o to override
** Checking the EFI jumpstart record.
** Checking the space manager
error: (oid 0x30d62) cib: invalid o_cksum (0x0)
error: failed to read spaceman cib 0x30d62
Space manager is invalid.
** The volume /dev/disk0 could not be verified completely.
after which I used fsck_apfs -y /dev/disk0s2
and got the exact same output.
I notice the space manager is invalid, but is that the cause of my unbootable partition/drive? If yes, how do I solve it? If no, what could it be?
Asked by onni82
(111 rep)
Jan 4, 2024, 11:21 PM
Last activity: Jan 8, 2024, 09:49 PM
Last activity: Jan 8, 2024, 09:49 PM