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

    • Only option I want is to disable the system tray overflow menu and always show icons, W11 added option to hide the menu but then icons will still go there instead of the tray.
    • Windows 11 blocks Google Chrome due to a Microsoft safety feature, fix out by Sayan Sen Microsoft has a parental control and safety feature called "Microsoft Family Safety" which allows users to create safe spaces for their family members for browsing the web by setting up filters so as to block and filter inappropriate content and limit browsing to kid-friendly and family friendly content. However, as it turns out, following Chrome version updates 137.0.7151.68, 137.0.7151.69, Google's web browser is getting automatically blocked by Microsoft Family Safety as affected users have reported that the browser will automatically close or crash and then fail to reopen. Thus if you are using Edge, you get the green signal from the Family Safety app, but not if you are using Google Chrome. The issue seems to be affecting mainly Windows 11 devices but Windows 10 or macOS may be affected too. A thread on Microsoft's official Windows forum by Peter Priestley1, which is presumably from an educational institute, says: The thread has been upvoted by 122 people at the time of writing. There are plenty of other such threads online and users also say that they have tried all sorts of things like refreshing cookies and appdata but "nothing" seems to fix it. This shows that Microsoft's safety feature is certainly robust and that it is not easy to bypass but it also means affected users are not too happy about it considering it is seemingly blocking all versions of Chrome. There is one fix that worked though, renaming chrome.exe to something else like chrome1.exe for example. A Chrome community manager, Ellen T, has confirmed that the Microsoft feature is indeed what is causing it and the only way to fix the issue is to "unblock Chrome" inside the Family Safety app. Ellen says: Microsoft has also shared a similar guidance on the issue according to Fred SR., a senior member of the Chrome community.
  • Recent Achievements

    • Week One Done
      Helen Shafer earned a badge
      Week One Done
    • First Post
      emptyother earned a badge
      First Post
    • Week One Done
      Crunchy6 earned a badge
      Week One Done
    • One Month Later
      KynanSEIT earned a badge
      One Month Later
    • One Month Later
      gowtham07 earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      660
    2. 2
      ATLien_0
      270
    3. 3
      Michael Scrip
      218
    4. 4
      Steven P.
      162
    5. 5
      +FloatingFatMan
      159
  • Tell a friend

    Love Neowin? Tell a friend!