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

File system check exit code 65

V

vett93

macrumors 6502
Original poster
Jul 27, 2014
279
40
California
After I updated the MacOS to 11.5.2, the old external disk random ejection problem has returned. All my USB devices (HDs, webcam, microphone, speakers, etc.) would randomly disconnect from the MacPro. So I tried to debug the system. According to some articles, one should verify if the HDs are good first.

So I use Disk Utility to perform first aid on my two backup HDs. Then I got the following error:

Screen Shot 2021-08-18 at 12.38.30 PM.png

Then I rebooted my MP and checked again on two HDs. No problems with them. But then I ran the Disk Utility after a few hours, the problem returned. Then I reboot the MP and immediately check again, no problem.

These HDs are LaCie drives I bought from Apple Store. So I contacted LaCie and they told me these disks don't have energy management software.

I contacted Apple Support and a Sr. Advisor worked with me to reinstall the latest MacOS. But it does not help the problem.
 
While I have not experienced the USB eject issue, I had 2 external HDDs failing one me after Big Sur upgrade, see link below ... I would contact LaCie and ask for a disk utility so you can run a check independent of DU/First Aid.
I'm seeing the same pattern, sometimes First Aid sees no problem and at other times it does.
How old is the HDD? I would replace it tbh.


2 external HDDs failing AFTER Big Sur upgrade?? or?
 
I bought these two HDs at the same time less than a year ago. It is not likely they both failed at the same time. I contacted LaCie yesterday and they told me that it is a Big Sur issue.
 
vett93 said:
I bought these two HDs at the same time less than a year ago. It is not likely they both failed at the same time. I contacted LaCie yesterday and they told me that it is a Big Sur issue.
Click to expand...
Ok, interesting, so if LaCie claims that, did they tell you how to approach Apple?
Are your drives formatted with APFS?
As you can see from my thread I have suspected Big Sur but the WD utility (mine are WDs) also reports errors, both on APFS and macOS extended. Could of course still be OS that’s causing it…
If you have any more info, esp from LaCie, I’ll go and contact Apple again.
 
jz0309 said:
Ok, interesting, so if LaCie claims that, did they tell you how to approach Apple?
Are your drives formatted with APFS?
As you can see from my thread I have suspected Big Sur but the WD utility (mine are WDs) also reports errors, both on APFS and macOS extended. Could of course still be OS that’s causing it…
If you have any more info, esp from LaCie, I’ll go and contact Apple again.
Click to expand...
Yes, these external HDs are formatted with APFS.

I ran the Disk Utility on the main system SSD and found errors too! It has errors on the snapshots:

warning: Cross check: Mismatch between extentref entry reference count (2) and calculated fsroot entry reference count (1) for extent (112624268 +4)

I am now thinking to erase all these drives....
 
vett93 said:
Yes, these external HDs are formatted with APFS.

I ran the Disk Utility on the main system SSD and found errors too! It has errors on the snapshots:

warning: Cross check: Mismatch between extentref entry reference count (2) and calculated fsroot entry reference count (1) for extent (112624268 +4)

I am now thinking to erase all these drives....
Click to expand...
I have erased and formatted with APFS and HFS my external HDDs with no difference.
But, I did create a Mojave partition during the Big Sur upgrade, maybe I'll boot into that and do the erase from there
 
I have same issue as vett93, has anyone been able to resolve this issue? In my case I have an external WD drive, but exactly same problem.
 
I have the following drive and had this issue no mater what I tried for months. My issue was solved by changing my USB-C cable that came with the drive. Might not be solution for everyone, but thought worth it mentioning it here in case it helps someone else too.

WD 2TB My Passport Ultra for Mac Silver Portable External Hard Drive, USB-C - WDBKYJ0020BSL-WESN

WD 2TB My Passport Ultra for Mac ​

 
vett93 said:
After I updated the MacOS to 11.5.2, the old external disk random ejection problem has returned. All my USB devices (HDs, webcam, microphone, speakers, etc.) would randomly disconnect from the MacPro. So I tried to debug the system. According to some articles, one should verify if the HDs are good first.

So I use Disk Utility to perform first aid on my two backup HDs. Then I got the following error:

View attachment 1820511
Then I rebooted my MP and checked again on two HDs. No problems with them. But then I ran the Disk Utility after a few hours, the problem returned. Then I reboot the MP and immediately check again, no problem.

These HDs are LaCie drives I bought from Apple Store. So I contacted LaCie and they told me these disks don't have energy management software.

I contacted Apple Support and a Sr. Advisor worked with me to reinstall the latest MacOS. But it does not help the problem.
Click to expand...
With the inspiration of another poster who said replacing the cable helped, I tried just unplugging the USB connection and reconnecting it. I unmounted first, and I used a different port. The error went away!
 
I got the Check Exit code 65 on an external HDD (USB) running as a Time Machine backup (APFS and encrypted). I am running 12.3.1 on an M1 MBP 16.

I read somewhere that Disk Utility was failing on encrypted volumes attached by USB, so I tried booting into Recovery, then running Disk Utility from there. I did, and it asked me to enter the password for that external encrypted Time Machine disk. It then performed the disk check fine, without errors (can take a while, though, checking each snapshot).

I doubt this will fix everyone's issues with the error 65, but I hope it helps some.
 
  • Like
Reactions: osplo
When an Error Code 65 appears on your Mac system with a notification like "[program name] cannot be operated" or "[program name] quit unexpectedly", and the specific error code number often indicates a particular type of problem on the computer. Here are few DIY methods that user can try to fix the issue:

1. Keep your system or apps up to date
2. Delete temporary, junk or cache files
3. Disable/Remove problematic application
4. Run disk utility to repair disk permission
5. Reset PRAM or SMC to fix hardware issues
6. Reinstall MacOS

Hope it helps!
 
moisesalejandro said:
I have the following drive and had this issue no mater what I tried for months. My issue was solved by changing my USB-C cable that came with the drive. Might not be solution for everyone, but thought worth it mentioning it here in case it helps someone else too.

WD 2TB My Passport Ultra for Mac Silver Portable External Hard Drive, USB-C - WDBKYJ0020BSL-WESN

WD 2TB My Passport Ultra for Mac​

Click to expand...
Just to add on to what moisesalejandro said: Same issue, same brand (5TB not 2TB, but WD), same solution. My theory is the wire they ship with the drive doesn't work with OSX for some reason. The Disk Utility fails to detect that the drive is encrypted, and failed with check 65. Switch cables and it will work.
 
jb444908 said:
I got the Check Exit code 65 on an external HDD (USB) running as a Time Machine backup (APFS and encrypted). I am running 12.3.1 on an M1 MBP 16.

I read somewhere that Disk Utility was failing on encrypted volumes attached by USB, so I tried booting into Recovery, then running Disk Utility from there. I did, and it asked me to enter the password for that external encrypted Time Machine disk. It then performed the disk check fine, without errors (can take a while, though, checking each snapshot).

I doubt this will fix everyone's issues with the error 65, but I hope it helps some.
Click to expand...
I found this quite helpful; it worked for me running 13.0.1 on an M1 MBP 14". Thought I'd just add that in my case, I'm using an external SSD (Transcend Jetdrive Lite 330) that's not attached via USB but rather the laptop's inbuilt SDXC card reader. Any explanation as to why it works in recovery mode but not in a normal disk bootup? I'm also new to such techy stuffs hehe
 
randomusr said:
I found this quite helpful; it worked for me running 13.0.1 on an M1 MBP 14". Thought I'd just add that in my case, I'm using an external SSD (Transcend Jetdrive Lite 330) that's not attached via USB but rather the laptop's inbuilt SDXC card reader. Any explanation as to why it works in recovery mode but not in a normal disk bootup? I'm also new to such techy stuffs hehe
Click to expand...
Also I recently found that manually unmounting my drive before running first aid on it seemed to solve the error code; it's possible that the error arises from the software trying to unmount the drive?
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back