Problem with a disc image

Discussion in 'macOS' started by miles01110, Jul 2, 2009.

  1. miles01110 macrumors Core

    miles01110

    Joined:
    Jul 24, 2006
    Location:
    The Ivory Tower (I'm not coming down)
    #1
    I have a password protected disk image that mounts, but when I mount it there's a lock that shows up in the icon and I can't access the contents- "The folder "Disk Image" could not be opened because you do not have sufficient access privileges." When I Get Info it has my account, (unknown) and "everyone" all set with custom access. Ignoring ownership does nothing, and I can't change the permissions. I can't get at it via Terminal, and sudo chmod doesn't work either (which I don't quite understand...).

    How can I get at the contents of this disk image?
     
  2. angelwatt Moderator emeritus

    angelwatt

    Joined:
    Aug 16, 2005
    Location:
    USA
    #2
  3. miles01110 thread starter macrumors Core

    miles01110

    Joined:
    Jul 24, 2006
    Location:
    The Ivory Tower (I'm not coming down)
    #3
    Hm, tried everything in that thread but still no dice. From ls -go:

    Code:
    drwxrwxr-x  10   408 Jul  1 14:47 Disk Image
    From chflags (list.txt is the one I want to get at):

    Code:
    chflags: Disk Image//.com.apple.timemachine.supported: Permission denied
    chflags: Disk Image//.DS_Store: Permission denied
    chflags: Disk Image//.fseventsd: Permission denied
    chflags: Disk Image//.Spotlight-V100: Permission denied
    chflags: Disk Image//.Trashes: Permission denied
    chflags: Disk Image//list.txt: Permission denied
    chflags: Disk Image/: Permission denied
    
    The sequence of sudo chflags 0 / sudo chown 0:80 ... didn't do anything, and also didn't ask for my password (?)...

    edit: ok, I don't really know why this worked but I ran Onyx's "Repair Disk Permissions" a few times and now it works. Strange.
     
  4. angelwatt Moderator emeritus

    angelwatt

    Joined:
    Aug 16, 2005
    Location:
    USA
    #4
    Ha ha, nice. Thanks for posting what eventually did the trick. There's too many different permission settings on Macs now. Makes troubleshooting extra fun.
     

Share This Page