Skip to main content
Bumped by Community user
Bumped by Community user
Bumped by Community user
added output of diskutil
Source Link

The original hard drive stopped working, so I got a new SSD (Crucial MX300, 275GB, part number CT275MX300SSD1) to put into the MacBook Pro and make a clean install of macOS.

Installation of High Sierra using an USB drive looked like it went through well, but when the MacBook Pro rebooted, it got to a screen where it just shows a flashing folder icon with a question mark inside.

After that failed, I tried a second time using Network Recovery and installed Mountain Lion. Same flashing folder icon after reboot. NVRAM reset did not fix the issue.

After wiping the drive once again, I immediately ran a volume check using Disk Utility and it told me that the volume was damaged.

Output of diskutil verifyVolume disk1s2:

Started file system verification on disk1s2 Macintosh SSD
Check file system
Checking Journaled HFS Plus volume
Checking extents overflow file
The volume Macintosh SSD could not be verified completely
Error: -69845: File system verify or repair failed
Underlying error: 8: POSIX reports: Exec format error

So maybe the issue lies on the SSD itself?

The original hard drive stopped working, so I got a new SSD (Crucial MX300, 275GB, part number CT275MX300SSD1) to put into the MacBook Pro and make a clean install of macOS.

Installation of High Sierra using an USB drive looked like it went through well, but when the MacBook Pro rebooted, it got to a screen where it just shows a flashing folder icon with a question mark inside.

After that failed, I tried a second time using Network Recovery and installed Mountain Lion. Same flashing folder icon after reboot. NVRAM reset did not fix the issue.

After wiping the drive once again, I immediately ran a volume check using Disk Utility and it told me that the volume was damaged.

So maybe the issue lies on the SSD itself?

The original hard drive stopped working, so I got a new SSD (Crucial MX300, 275GB, part number CT275MX300SSD1) to put into the MacBook Pro and make a clean install of macOS.

Installation of High Sierra using an USB drive looked like it went through well, but when the MacBook Pro rebooted, it got to a screen where it just shows a flashing folder icon with a question mark inside.

After that failed, I tried a second time using Network Recovery and installed Mountain Lion. Same flashing folder icon after reboot. NVRAM reset did not fix the issue.

After wiping the drive once again, I immediately ran a volume check using Disk Utility and it told me that the volume was damaged.

Output of diskutil verifyVolume disk1s2:

Started file system verification on disk1s2 Macintosh SSD
Check file system
Checking Journaled HFS Plus volume
Checking extents overflow file
The volume Macintosh SSD could not be verified completely
Error: -69845: File system verify or repair failed
Underlying error: 8: POSIX reports: Exec format error

So maybe the issue lies on the SSD itself?

Improved formatting, fixed grammar
Source Link
jaume
  • 15.6k
  • 4
  • 59
  • 74

MacBookPro9,2 does not recognize Drivedrive as bootable after clean Install

The original hard drive did stopstopped working, so I got a new SSD (Crucial MX300, 275GB model, CT275MX300SSD1part number CT275MX300SSD1) to put into the MBPMacBook Pro and make a clean install of macOS. 

Installation of High Sierra using an USB drive looked like it went through well, but when the MBPMacBook Pro rebooted, it got to a screen where it just shows a flashing folder icon with a question mark inside.

After that failed, iI tried a second time using Network Recovery and installed Mountain Lion. Same flashing folder icon after reboot. NVRAM reset did not fix the issue.

After wiping the drive once again, iI immediately ran a volume check using disk utilityDisk Utility and it told me that the volume was damaged. 

So maybe the issue lies inon the SSD itself?

MacBookPro9,2 does not recognize Drive as bootable after clean Install

The original hard drive did stop working, so I got a new SSD (Crucial 275GB model, CT275MX300SSD1) to put into the MBP and make a clean install of macOS. Installation of High Sierra using an USB drive looked like it went through well, but when the MBP rebooted it got to a screen where it just shows a flashing folder icon with a question mark inside.

After that failed, i tried a second time using Network Recovery and installed Mountain Lion. Same flashing folder icon after reboot. NVRAM reset did not fix the issue.

After wiping the drive once again, i immediately ran a volume check using disk utility and it told me that the volume was damaged. So maybe the issue lies in the SSD itself?

MacBookPro9,2 does not recognize drive as bootable after clean Install

The original hard drive stopped working, so I got a new SSD (Crucial MX300, 275GB, part number CT275MX300SSD1) to put into the MacBook Pro and make a clean install of macOS. 

Installation of High Sierra using an USB drive looked like it went through well, but when the MacBook Pro rebooted, it got to a screen where it just shows a flashing folder icon with a question mark inside.

After that failed, I tried a second time using Network Recovery and installed Mountain Lion. Same flashing folder icon after reboot. NVRAM reset did not fix the issue.

After wiping the drive once again, I immediately ran a volume check using Disk Utility and it told me that the volume was damaged. 

So maybe the issue lies on the SSD itself?

Source Link

MacBookPro9,2 does not recognize Drive as bootable after clean Install

The original hard drive did stop working, so I got a new SSD (Crucial 275GB model, CT275MX300SSD1) to put into the MBP and make a clean install of macOS. Installation of High Sierra using an USB drive looked like it went through well, but when the MBP rebooted it got to a screen where it just shows a flashing folder icon with a question mark inside.

After that failed, i tried a second time using Network Recovery and installed Mountain Lion. Same flashing folder icon after reboot. NVRAM reset did not fix the issue.

After wiping the drive once again, i immediately ran a volume check using disk utility and it told me that the volume was damaged. So maybe the issue lies in the SSD itself?