Can't delete random boot.efi file


Recommended Posts

Some weird file remained in my trash after deleting my Aperture library back up file from an external hard drive.

 

I can't get rid of it.

 

I've tried:

1.) Restarting finder, multiple times.

2.) Rebooting, multiple times.

3.) A basic Sharing & Permissions adjustment (which you can see does not work in the video)

4.) Changing permissions using CHMOD 777 in Terminal.

 

Uhh... any other ideas?

 

Link to comment
https://www.neowin.net/forum/topic/1160360-cant-delete-random-bootefi-file/
Share on other sites

What about the Terminal command

sudo rm -rf ~/Desktop/boot.efi

But what puzzles me is how a file only found inside the OS X System folder comes into play with Aperture.

 

Also try looking at this ling on how to unlock files in OS X using Terminal http://superuser.com/questions/40749/command-to-unlock-locked-files-on-os-x

 

Your computer is a Hackintosh? I get some videos on Hackintoshes after viewing your video. If it is then it's mysterious because is it not needed for Chameleon?

Just asking - you can safely ignore this comment about Hackintoshes - I have one stashed away myself so I'm not holy about it :)

Unlocking the file is a good suggestion. It would also be helpful if you try removing it from Terminal like allan.nyholm suggested; then if it fails you can at least get a specific error message.

 

Troubleshooting this issue should be easier for you with a complete understanding of the OS X permissions system. Unfortunately Apple developed more than one. The first answer to this superuser.com question provides a good overview of permissions in OS X.

 

  Quote

 

Mac files can be protected in four three different ways that I'm aware of:

  1. Standard Unix ownerships and permissions like r/w/x for user/group/others that you see with ls -l and fix with chown(1) and chmod(1).
  2. File flags like uchg and schg that you see with ls -lO and fix with chflags(1).
  3. The old Finder metadata "Lock bit" that you see with GetFileInfo filename. You can also see the presence of the Finder metadata, but not its meaning, with ls -l@. You can fix it with SetFile(1). Never mind, this is mapped to the uchg flag now.
  4. Access Control Lists (ACLs) that you see with ls -le and fix with the ACL-related arguments to chmod(1).

So let's see what's up with your file by combining all those flags to ls:

ls -lO@e main.m
  • 3 weeks later...
  On 26/06/2013 at 03:35, Mikee4fun said:

Have you tried logging is as root and then attempted deleting it. 

 

Also this guy looks like he solved a similar issue

 

http://forums.macrumors.com/showpost.php?p=14198556&postcount=4

 

No go.

 

  On 26/06/2013 at 06:11, Timan said:

Curious if you've tried secure delete. Finder > Secure Empty Trash. 

 

I couldn't even get it into the trash.

 

  On 26/06/2013 at 11:56, allan.nyholm said:

What about the Terminal command

sudo rm -rf ~/Desktop/boot.efi

But what puzzles me is how a file only found inside the OS X System folder comes into play with Aperture.

 

Also try looking at this ling on how to unlock files in OS X using Terminal http://superuser.com/questions/40749/command-to-unlock-locked-files-on-os-x

 

Your computer is a Hackintosh? I get some videos on Hackintoshes after viewing your video. If it is then it's mysterious because is it not needed for Chameleon?

Just asking - you can safely ignore this comment about Hackintoshes - I have one stashed away myself so I'm not holy about it :)

 

My sig says "27" iMac".  No hackintosh ;)

 

But the sudo command actually worked!!!  I don't reboot too often, but if it's there next time I boot up, I'll let you know.

 

Since that didn't work, I didn't get to xorangekiller's suggestion.

  • 1 month later...
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Now I may not quite understand this, so someone tell me if I'm off the mark here, but does this mean they'll be potentially removing drivers for now unsupported systems, such as old processors and chipsets? In the past 15 years, Windows has been amazing at just installing on any device, and often having zero, or just a few unessential drivers missing on first install. It would be a shame for that experience to go, though I understand the reasoning, or at least their financial reasoning for it!
    • Microsoft is removing legacy drivers from Windows Update by Usama Jawad Last month, we learned that Microsoft is making major changes to the development of hardware drivers in Windows. This included the retirement of Windows Metadata and Internet Services (WMIS), along with the process for pre-production driver signing. Now, the Redmond tech firm has informed partners that it will be getting rid of old drivers in Windows Update. In what is being described as a "strategic" move to improve the security posture and compatibility of Windows, Microsoft has announced that it will be performing a cleanup of legacy drivers that are still being delivered through Windows Update. Right now, the first phase only targets drivers that already have modern replacements present in Windows Update. As a part of its cleanup process, Microsoft will expire legacy drivers so that it is not offered to any system. This expiration involves removing audience segments in the Hardware Development Center. Partners can still republish a driver that was deemed as legacy by Microsoft, but the firm may require a justification. Once the Redmond tech giant completes its first phase of this cleanup, it will give partners a six-month grace period to share any concerns. However, if no concerns are brought forward, the drivers will be permanently eradicated from Windows Update. Microsoft has emphasized that this will be a regular activity moving forward and while the current phase only targets legacy drivers with newer replacements, the next phases may expand the scope of this cleanup and remove other drivers too. That said, each time the company takes a step in this direction, it will inform partners so that there is transparency between both parties. Microsoft believes that this move will help improve the security posture of Windows and ensure that an optimized set of drivers is offered to end-users. The firm has asked partners to review their drivers in Hardware Program so that there are no unexpected surprises during this cleanup process.
    • No idea, but I had a client the other week that lost the entire drive to it. I suggested relying on the Samsung T7's instead. The Sandisk Extreme's had reliability issues too.
    • I use it every day so personally yes I need it, or rather I want it. I use OpenShell though, not the garbage modern Start Menu. I just counted and at the moment I have a total of 92 program shortcuts organized into six folders almost exactly the way I did back in Windows 95. I can get to any program I want to run very quickly. I never use Search to find or run programs.
    • I do miss the Apps view from Windows 8.1 Update.
  • Recent Achievements

    • One Month Later
      KynanSEIT earned a badge
      One Month Later
    • One Month Later
      gowtham07 earned a badge
      One Month Later
    • Collaborator
      lethalman went up a rank
      Collaborator
    • Week One Done
      Wayne Robinson earned a badge
      Week One Done
    • One Month Later
      Karan Khanna earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      683
    2. 2
      ATLien_0
      274
    3. 3
      Michael Scrip
      220
    4. 4
      +FloatingFatMan
      171
    5. 5
      Steven P.
      160
  • Tell a friend

    Love Neowin? Tell a friend!