external hard drive locked with custom access

[mikeoscar]

Trevor, delighted to receive your response. I have done as you suggested and one or two other things as well. Below is a full output listing. Some of the [permissions still seem to have one or two odd characters such as + and @. What do they mean and are they okay where they are? Interestingly, both are to do with DroboShare or DroboCapsule and my Drobo is not behaving at all well of late, ie., quitting in the middle of a backup or just being impossibly slow. Could them be part of the problem or perhaps a sympton or indicator of something else.

As ever, incredibly grateful for your advice and input. May I echo another forum member; for every one that corresponds on this forum, there is another 50 or 100 that benefit from it and are equally grateful.

Mike

mike-wilsons-mac-pro:~ mikeoscar$ ls -alO /Volumes
total 13
drwxrwxrwt@ 14 root       admin  hidden  476 27 Dec 23:08 .
drwxrwxr-t  40 root       admin  -      1428 24 Dec 22:15 ..
drwxr-xr-x   7 root       admin  -       442 18 Jun  2009 Backup of mike-wilsons-mac-pro
drwxrwxr-t  23 root       admin  -       850 13 Sep 23:41 DV HD
drwxrwxr-t  28 root       admin  -      1020  5 Sep 23:29 Data HD
drwxrwxrwx@ 10 root       wheel  -       296 27 Dec 23:41 DroboCapsule
drwxrwxrwx+  2 root       admin  -        68 24 Dec 22:15 DroboShare
drwxrwxr-t  35 root       admin  -      1258 18 Dec 20:28 MacPro HD
lrwxr-xr-x   1 root       admin  -         1 24 Dec 22:13 Macintosh HD -> /
lrwxr-xr-x   1 mikeoscar  admin  -        18 24 Dec 22:15 iDisk -> /Volumes/mikeoscar
drwx------  15 mikeoscar  staff  -       850  6 Sep 16:45 mikeoscar
mike-wilsons-mac-pro:~ mikeoscar$ id
uid=501(mikeoscar) gid=20(staff) groups=20(staff),204(_developer),100(_lpoperator),98(_lpadmin),81(_appserveradm),80(admin),79(_appserverusr),61(localaccounts),12(everyone),401(com.apple.access_screensharing),402(com.apple.sharepoint.group.1)
mike-wilsons-mac-pro:~ mikeoscar$ diskutil list
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *750.2 GB   disk0
   1:                        EFI                         209.7 MB   disk0s1
   2:                  Apple_HFS Macintosh HD            749.8 GB   disk0s2
/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *750.2 GB   disk1
   1:                        EFI                         209.7 MB   disk1s1
   2:                 Apple_RAID                         749.8 GB   disk1s2
   3:                 Apple_Boot Boot OSX                134.2 MB   disk1s3
/dev/disk2
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *750.2 GB   disk2
   1:                        EFI                         209.7 MB   disk2s1
   2:                 Apple_RAID                         749.8 GB   disk2s2
   3:                 Apple_Boot Boot OSX                134.2 MB   disk2s3
/dev/disk3
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *750.2 GB   disk3
   1:                        EFI                         209.7 MB   disk3s1
   2:                  Apple_HFS Data HD                 182.1 GB   disk3s2
   3:                  Apple_HFS MacPro HD               567.6 GB   disk3s3
/dev/disk4
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                  Apple_HFS DV HD                  *1.5 TB     disk4
/dev/disk5
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     Apple_partition_scheme                        *21.5 GB    disk5
   1:        Apple_partition_map                         32.3 KB    disk5s1
   2:                 Apple_HFSX mikeoscar               21.5 GB    disk5s2
/dev/disk6
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *4.3 TB     disk6
   1:                        EFI                         209.7 MB   disk6s1
   2:                  Apple_HFS Backup of mike-wilso... 4.3 TB     disk6s2
mike-wilsons-mac-pro:~ mikeoscar$ df
Filesystem                               512-blocks       Used   Available Capacity  Mounted on
/dev/disk0s2                             1464477344 1148308776   315656568    79%    /
devfs                                           268        268           0   100%    /dev
/dev/disk4                               2928954624  881209928  2047744696    31%    /Volumes/DV HD
/dev/disk3s2                              355707192  272316608    83390584    77%    /Volumes/Data HD
/dev/disk3s3                             1108508008 1036568760    71939248    94%    /Volumes/MacPro HD
map -hosts                                        0          0           0   100%    /net
map auto_home                                     0          0           0   100%    /home
/dev/disk5s2                               42000344     777360    41222984     2%    /Volumes/mikeoscar
afp_0IsBu80IsBu80IsBu80IsBu8-1.2d000050 17179869104 4024822360 13155046744    24%    /Volumes/DroboCapsule
/dev/disk6s2                             8387936176 4022210472  4365725704    48%    /Volumes/Backup of mike-wilsons-mac-pro
mike-wilsons-mac-pro:~ mikeoscar$ echo "done"
done
mike-wilsons-mac-pro:~ mikeoscar$ exit
logout

[Process completed]

[trevor]

Quote: Originally Posted by mikeoscar Some of the [permissions still seem to have one or two odd characters such as + and @. What do they mean and are they okay where they are?

Here's what the manual page for ls says about @ and + in the permissions:

Quote: Originally Posted by man ls If the file or directory has extended attributes, the permissions field printed by the -l option is followed by a '@' character. Otherwise, if the file or directory has extended security information (such as an access con- trol list), the permissions field printed by the -l option is followed by a '+' character.

If you would like to see what they are, you can add the @ flag to your directory listing, like:

ls -al@ /Volumes

Show us what you see, and then we'll know what you've got.

Trevor

[mikeoscar]

Quote: If you would like to see what they are, you can add the @ flag to your directory listing, like: ls -al@ /Volumes Show us what you see, and then we'll know what you've got.

Trevor, your wish is my command:

Last login: Mon Dec 28 00:12:33 on ttys000
mike-wilsons-mac-pro:~ mikeoscar$ ls -al@ /Volumes
total 13
drwxrwxrwt@ 13 root admin 442 28 Dec 10:19 .
com.apple.FinderInfo 32
drwxrwxr-t 40 root admin 1428 24 Dec 22:15 ..
drwxrwxr-t 23 root admin 850 13 Sep 23:41 DV HD
drwxrwxr-t 28 root admin 1020 5 Sep 23:29 Data HD
drwxrwxrwx@ 10 root wheel 296 28 Dec 10:19 DroboCapsule
com.apple.FinderInfo 32
drwxrwxrwx+ 2 root admin 68 24 Dec 22:15 DroboShare
drwxrwxr-t 35 root admin 1258 18 Dec 20:28 MacPro HD
lrwxr-xr-x 1 root admin 1 24 Dec 22:13 Macintosh HD -> /
lrwxr-xr-x 1 mikeoscar admin 18 24 Dec 22:15 iDisk -> /Volumes/mikeoscar
drwx------ 15 mikeoscar staff 850 6 Sep 16:45 mikeoscar
mike-wilsons-mac-pro:~ mikeoscar$
Mike

[drdillo]

eMac OS10.4.11. I have read this thread, don't see exact problem. Improper disconnect lead to multiple uchg flags, no access, didn't show up in Finder, still show up in Disk Utilities. Thanks to excellence of Trevor, executed the chflags nouchg /Volumes/"disk name", was able to turn off uchg flags. However, several partitions still don't show up in Finder, can't access them without Terminal: to wit, "A>Leopard Copy", "A>Misty", "B>Annie", "B>Leopard" and "C>Storage." (Yes, I know now that these are incredibly stupid partition names.) Permissions seem wonky to me, but I am a complete non-Unix speaking duffer.

Have included Terminal dump ("WALDO" listed as administrator) and just hope that somebody can tell me how to restore all the data I have lost. TIA

Last login: Mon Dec 28 14:10:24 on ttyp1
Welcome to Darwin!
RMac:~ WALDO$ ls -alo /Volumes
total 8
-rw-r--r--    1 WALDO  admin    -    0 Dec 26 13:29  Misty
-rw-r--r--    1 WALDO  admin    -    0 Dec 26 13:26  Nisty
drwxrwxrwt   16 root     admin    -  544 Dec 28 14:15 .
drwxrwxr-t   52 root     admin    - 1870 Dec 27 16:51 ..
drwxrwxr-t   40 root     admin    - 1462 Dec 25 19:45 A>LeoB2
drwxrwxr-t   42 root     admin    - 1530 Dec 25 19:43 A>Leopard Copy
drw-rw-r-T   23 WALDO  WALDO  -  816 Dec  8 14:03 A>Misty
-rw-r--r--    1 WALDO  admin    -    0 Dec 26 13:34 Annie
drw-rw-r-T   33 WALDO  WALDO  - 1224 Jun 18  2009 B>Annie
drw-rw-r-T   39 root     admin    - 1428 Dec  8 17:22 B>Leopard
drw-rw-r-T   31 WALDO  WALDO  - 1088 Dec  4 15:38 C>Storage
drw-------    3 root     admin    -  102 May 20  2009 Leopard
-rw-r--r--    1 WALDO  admin    -    0 Dec 25 14:17 Misty
drwxr-xr-x    3 WALDO  admin    -  102 May  2  2009 Misty2 FW
drwxrwxr-t   48 root     admin    - 1734 Dec 27 15:03 RMacBackup
lrwxr-xr-x    1 root     admin    -    1 Dec 26 21:14 eMac10.4.11 -> /
RMac:~ WALDO$ id
uid=501(WALDO) gid=501(WALDO) groups=501(WALDO), 81(appserveradm), 79(appserverusr), 80(admin)
RMac:~ WALDO$ diskutil list
/dev/disk0
   #:                   type name               size      identifier
   0: Apple_partition_scheme                    *149.1 GB disk0
   1:    Apple_partition_map                    31.5 KB   disk0s1
   2:         Apple_Driver43                    28.0 KB   disk0s2
   3:         Apple_Driver43                    28.0 KB   disk0s3
   4:       Apple_Driver_ATA                    28.0 KB   disk0s4
   5:       Apple_Driver_ATA                    28.0 KB   disk0s5
   6:         Apple_FWDriver                    256.0 KB  disk0s6
   7:     Apple_Driver_IOKit                    256.0 KB  disk0s7
   8:          Apple_Patches                    256.0 KB  disk0s8
   9:              Apple_HFS eMac10.4.11        149.0 GB  disk0s9
/dev/disk1
   #:                   type name               size      identifier
   0: Apple_partition_scheme                    *931.5 GB disk1
   1:    Apple_partition_map                    31.5 KB   disk1s1
   2:              Apple_HFS A>Misty            465.6 GB  disk1s3
   3:              Apple_HFS A>LeoB2            232.7 GB  disk1s5
   4:              Apple_HFS A>Leopard Copy     232.8 GB  disk1s7
/dev/disk2
   #:                   type name               size      identifier
   0: FDisk_partition_scheme                    *931.5 GB disk2
   1:              Apple_HFS B>Leopard          500.1 GB  disk2s1
   2:              Apple_HFS RMacBackup         200.1 GB  disk2s2
   3:              Apple_HFS B>Annie            231.3 GB  disk2s3
/dev/disk4
   #:                   type name               size      identifier
   0: Apple_partition_scheme                    *931.5 GB disk4
   1:    Apple_partition_map                    31.5 KB   disk4s1
   2:              Apple_HFS C>Storage          931.4 GB  disk4s3
RMac:~ WALDO$ df
Filesystem              512-blocks       Used     Avail Capacity  Mounted on
/dev/disk0s9             312555768  202038240 110005528    65%    /
devfs                          219        219         0   100%    /dev
fdesc                            2          2         0   100%    /dev
<volfs>                       1024       1024         0   100%    /.vol
automount -nsl [170]             0          0         0   100%    /Network
automount -fstab [184]           0          0         0   100%    /automount/Servers
automount -static [184]          0          0         0   100%    /automount/static
/dev/disk1s5             488058856  307616392 180442464    63%    /Volumes/A>LeoB2
/dev/disk1s7             488321016  309989968 178331048    63%    /Volumes/A>Leopard Copy
/dev/disk1s3             976379856  538953104 437426752    55%    /Volumes/A>Misty
/dev/disk2s1            1048838144  307574288 741263856    29%    /Volumes/B>Leopard
/dev/disk2s2             419692544  394287096  25405448    94%    /Volumes/RMacBackup
/dev/disk2s3             485015384   42474648 442540736     9%    /Volumes/B>Annie
/dev/disk4s3            1953284000 1484430192 468853808    76%    /Volumes/C>Storage
RMac:~ WALDO$ df
Filesystem              512-blocks       Used     Avail Capacity  Mounted on
/dev/disk0s9             312555768  202038240 110005528    65%    /
devfs                          219        219         0   100%    /dev
fdesc                            2          2         0   100%    /dev
<volfs>                       1024       1024         0   100%    /.vol
automount -nsl [170]             0          0         0   100%    /Network
automount -fstab [184]           0          0         0   100%    /automount/Servers
automount -static [184]          0          0         0   100%    /automount/static
/dev/disk1s5             488058856  307616392 180442464    63%    /Volumes/A>LeoB2
/dev/disk1s7             488321016  309989968 178331048    63%    /Volumes/A>Leopard Copy
/dev/disk1s3             976379856  538953104 437426752    55%    /Volumes/A>Misty
/dev/disk2s1            1048838144  307574288 741263856    29%    /Volumes/B>Leopard
/dev/disk2s2             419692544  394287096  25405448    94%    /Volumes/RMacBackup
/dev/disk2s3             485015384   42474648 442540736     9%    /Volumes/B>Annie
/dev/disk4s3            1953284000 1484430192 468853808    76%    /Volumes/C>Storage
RMac:~ WALDO$ echo "done"
done
RMac:~ WALDO$

[trevor]

Oops, my mistake. That showed the extended attributes (which are just fine in your case) but not the ACLs. Let's look at those too:

ls -ale@ /Volumes

Trevor

[mikeoscar]

Quote: Originally Posted by trevor Oops, my mistake. That showed the extended attributes (which are just fine in your case) but not the ACLs. Let's look at those too: ls -ale@ /Volumes

Trevor, that's okay, I'm learning all the time. Here is the output:

Last login: Mon Dec 28 10:18:40 on ttys000
mike-wilsons-mac-pro:~ mikeoscar$ ls -ale@ /Volumes
total 13
drwxrwxrwt@ 12 root admin 408 28 Dec 22:11 .
com.apple.FinderInfo 32
0: group:everyone deny add_file,add_subdirectory,directory_inherit,only_inherit
drwxrwxr-t 40 root admin 1428 24 Dec 22:15 ..
drwxrwxr-t 23 root admin 850 13 Sep 23:41 DV HD
drwxrwxr-t 28 root admin 1020 5 Sep 23:29 Data HD
drwxrwxrwx+ 2 root admin 68 24 Dec 22:15 DroboShare
0: group:everyone inherited deny add_file,add_subdirectory,directory_inherit
drwxrwxr-t 35 root admin 1258 18 Dec 20:28 MacPro HD
lrwxr-xr-x 1 root admin 1 24 Dec 22:13 Macintosh HD -> /
lrwxr-xr-x 1 mikeoscar admin 18 24 Dec 22:15 iDisk -> /Volumes/mikeoscar
drwx------ 15 mikeoscar staff 850 6 Sep 16:45 mikeoscar
mike-wilsons-mac-pro:~ mikeoscar$

I'm really looking forward to see what you have to say about this collection.
What can "0: group:everyone inherited deny add_file,add_subdirectory,directory_inherit" mean? And it's that DroboShare again.
Mike

[mikeoscar]

Trevor, sorry, I've just realised that DroboCapsule is missing from the above list. That's because I have temporarily disconnected it. If that is not helpful to the investigation just let me know and I'll reconnect and run the ACLs again.
Mike

[Hal Itosis]

Quote: Originally Posted by mikeoscar What can "0: group:everyone inherited deny add_file,add_subdirectory,directory_inherit" mean?

Trouble... with a capital "T".

I was wondering when we would see one of those <again>.

IMHO, it seems to be a deliberate (and devious) attempt to seriously inconvenience people. [i wonder if we can ever discover its origin.] From all appearances, the volume "DroboShare" has *inherited* that crippling ACL (shown in purple) from the /Volumes folder itself!!! (shown in red).

$ ls -ale@ /Volumes
total 13
drwxrwxrwt@ 12 root      admin  408 28 Dec 22:11 .
	com.apple.FinderInfo	 32 
 0: group:everyone deny add_file,add_subdirectory,directory_inherit,only_inherit
drwxrwxr-t  40 root      admin 1428 24 Dec 22:15 ..
drwxrwxr-t  23 root      admin  850 13 Sep 23:41 DV HD
drwxrwxr-t  28 root      admin 1020  5 Sep 23:29 Data HD
drwxrwxrwx+  2 root      admin   68 24 Dec 22:15 DroboShare
 0: group:everyone inherited deny add_file,add_subdirectory,directory_inherit
drwxrwxr-t  35 root      admin 1258 18 Dec 20:28 MacPro HD
lrwxr-xr-x   1 root      admin    1 24 Dec 22:13 Macintosh HD -> /
lrwxr-xr-x   1 mikeoscar admin   18 24 Dec 22:15 iDisk -> /Volumes/mikeoscar
drwx------  15 mikeoscar staff  850  6 Sep 16:45 mikeoscar 

Something like
sudo chmod -N /Volumes{,/*}
would be the place to start... but i wonder how much deeper that particular ACL has propagated.

More extreme measures may be needed.

[trevor]

Quote: Originally Posted by drdillo eMac OS10.4.11. I have read this thread, don't see exact problem. Improper disconnect lead to multiple uchg flags, no access, didn't show up in Finder, still show up in Disk Utilities. Thanks to excellence of Trevor, executed the chflags nouchg /Volumes/"disk name", was able to turn off uchg flags. However, several partitions still don't show up in Finder, can't access them without Terminal: to wit, "A>Leopard Copy", "A>Misty", "B>Annie", "B>Leopard" and "C>Storage." (Yes, I know now that these are incredibly stupid partition names.) Permissions seem wonky to me, but I am a complete non-Unix speaking duffer.

Let's see, first let's set those restrictive permissions to be a bit more open:

sudo chmod 775 /Volumes/"A>LeoB2"
sudo chmod 775 /Volumes/"A>Leopard Copy"
sudo chmod 775 /Volumes/"A>Misty"
sudo chmod 775 /Volumes/"B>Annie"
sudo chmod 775 /Volumes/"B>Leopard"
sudo chmod 775 /Volumes/"C>Storage"
sudo chmod 775 /Volumes/Leopard
sudo chmod 775 /Volumes/"Misty2 FW"
sudo chmod 775 /Volumes/RMacBackup
echo "done"

Note that I'm removing the sticky bit from most of those volumes with the commands above, as I don't think that it's particularly helpful or necessary. If you want to retain the sticky bit on those volumes, you can substitute 1775 in place of 775 in the commands above.

The sticky bit makes those directories (at the root of the volumes) append-only, meaning that unprivileged users can add to them, but cannot rename or erase files. If you'd like to keep that setting, feel free to substitute 1775 in the commands.

Let us know if the new permissions fix the problems that you are having with these volumes. If not, I'd advise running Disk Utility > First Aid tab > Repair Disk on any of the volumes that you are still having troubles with.

Trevor

[Hal Itosis]

I wonder what the chances are that the "everyone deny" ACL in /Volumes could be behind the iPhone problem reported by mikeoscar.

Mike, what all software have you installed lately?
[and/or run any unusual scripts or something?]

--

EDIT: Mike, more questions... concerning post #141 (top of this page):

drwxrwxrwx+  2 root       admin  -        68 24 Dec 22:15 DroboShare

Why does DroboShare appear to be a totally empty directory (2 items [. and ..] at 68 bytes)? Even a blank volume mounted by Leopard has some files on it (say 240 bytes maybe). But more importantly: why does DroboShare appear in /Volumes... but not in *either* of the command outputs which followed (i.e., diskutil list and df). If it's not a mounted disk or a mounted share, then what is it? An empty folder sitting in /Volumes?

Why?
Explain.

[drdillo]

Trevor:
Hallelujah! All FOUR hard disks up an working like a charm! Just don’t know how to thank you enough. (Although I did have an Avery Out of Bounds in your honor.)

Not to wear out your patience, but I thought I’d ask two small questions:
1) How do I get rid of the chaff that resulted from mistyping, etc? The ones I suspect I have marked †††) Or should I just leave well enough alone? (Don’t have any idea what the *** volumes are.)

2) The volumes with ### beside them used to be bootable. They no longer are. On attempting to “verify permissions,” Disk Utilities says “Error: No valid packages.” Is that something that can be fixed by waving the magic sudo-wand, or do I just need to get over it and re-install?

RMac:~ Russell$ ls -alo /Volumes
total 8
††† -rw-r--r--    1 Russell  admin    -    0 Dec 26 13:29  Misty
††† -rw-r--r--    1 Russell  admin    -    0 Dec 26 13:26  Nisty
*** drwxrwxrwt   17 root     admin    -  578 Dec 28 22:06 .
*** drwxrwxr-t   52 root     admin    - 1870 Dec 28 14:40 ..
### drwxrwxr-t   40 root     admin    - 1462 Dec 25 19:45 A>LeoB2
### drwxrwxr-x   42 root     admin    - 1530 Dec 25 19:43 A>Leopard Copy
drwxrwxr-x   23 Russell  Russell  -  816 Dec  8 14:03 A>Misty
††† -rw-r--r--    1 Russell  admin    -    0 Dec 26 13:34 Annie
drwxrwxr-x   33 Russell  Russell  - 1224 Jun 18  2009 B>Annie
### drwxrwxr-x   39 root     admin    - 1428 Dec  8 17:22 B>Leopard
drwxrwxr-x   31 Russell  Russell  - 1088 Dec  4 15:38 C>Storage
drwxrwxr-x   39 Russell  Russell  - 1428 Jun 28  2009 D>Annie Old
††† drw-------    3 root     admin    -  102 May 20  2009 Leopard
†††-rw-r--r--    1 Russell  admin    -    0 Dec 25 14:17 Misty
drwxr-xr-x    3 Russell  admin    -  102 May  2  2009 Misty2 FW
drwxrwxr-t   48 root     admin    - 1734 Dec 27 15:03 RMacBackup
lrwxr-xr-x    1 root     admin    -    1 Dec 28 14:41 eMac10.4.11 -> /
RMac:~ Russell$

[trevor]

Quote: Originally Posted by drdillo 1) How do I get rid of the chaff that resulted from mistyping, etc? The ones I suspect I have marked †††) Or should I just leave well enough alone? (Don’t have any idea what the *** volumes are.)

The *** are normal parts of a directory listing when you use the -a flag. The
'.' line (the one with a single dot) is the directory that you are currently listing, the '..' line (the one with two dots) is the directory that encloses it, or the parent directory.

I also suspect that the ††† lines are chaff, although it's not clear what kind. If you look at the /Volumes directory in the Finder (use Finder > Go > Go to Folder > in the sheet that appears, enter /Volumes to see it in the Finder) do those chaff lines have the small arrow in a lower corner indicating that they are aliases?

But you're if you just want to delete them without investigation, I can give you directions for that.

rm /Volumes/" Misty"
rm /Volumes/" Nisty"
rm /Volumes/Annie
rm /Volumes/Misty
echo "done"

The "Leopard" line is a directory, so before deleting that, make sure to look inside it. It appears that there is something in there:

ls -al /Volumes/Leopard

If you need to, retrieve whatever is in there. If you don't need it, you can also delete that folder with the command:

sudo rm -R /Volumes/Leopard
ls -al /Volumes
echo "done"

Quote: Originally Posted by drdillo 2) The volumes with ### beside them used to be bootable. They no longer are. On attempting to “verify permissions,” Disk Utilities says “Error: No valid packages.” Is that something that can be fixed by waving the magic sudo-wand, or do I just need to get over it and re-install?

If all the correct files are there for them to be bootable, it's possible that whatever caused all this havoc with your volumes also unblessed them. Bootable volumes need to be blessed.

I *think* the command to bless a volume would be:
sudo bless -folder /Volumes/"TargetBootableVolume"/System/Library/CoreServices -label "TargetBootableVolume"

...where TargetBootableVolume is the actual name of the volume you want to make bootable. Note that I have included quotations around it above, this is necessary if there are spaces or other special characters in the name. '>' is most definitely a special character, so any of your volumes that have a > in them should include those quotations.

Tell us if that worked, I'm not confident that I've formulated the bless command properly.

Trevor

[mikeoscar]

Quote: Originally Posted by Hal Itosis Trouble... with a capital "T". I was wondering when we would see one of those <again>. IMHO, it seems to be a deliberate (and devious) attempt to seriously inconvenience people. [i wonder if we can ever discover its origin.] From all appearances, the volume "DroboShare" has *inherited* that crippling ACL (shown in purple) from the /Volumes folder itself!!! (shown in red). Something like sudo chmod -N /Volumes{,/*} would be the place to start... but i wonder how much deeper that particular ACL has propagated. More extreme measures may be needed.

It's almost like being pleased when the doctor tells you what your serious complaint is. You're just pleased there is a name for it and someone can now, maybe, do something about it.
I believe I am to blame for the chaos. As reported earlier "Having become impatient with not being able to do 'simple' things without having to authenticate (and sometimes not even then), on "it is my own Mac after all" I made the HUGE mistake of changing ownership privileges of my bootable drive in 'Get Info' for my bootable drive AND then selecting 'Apply to enclosed items'." Could that be the cause?

Anyway, from about that time all kinds of things have either not worked and not worked as expected and I've been trying to get sorted. I've looked at your <again> reference and it does indeed look like "Trouble with a capital T". And yes, there could be a connection with my iPhone problem, because that started at about the same time too. Oh what the heck did I do?

A better question is, what do I do now?

[Hal Itosis]

Quote: Originally Posted by mikeoscar I made the HUGE mistake of changing ownership privileges of my bootable drive in 'Get Info' for my bootable drive AND then selecting 'Apply to enclosed items'." Could that be the cause?

I.m.p.o.s.s.i.b.l.e.

There is no way for any user who tinkers with a Finder Get Info window on a volume to generate an ACL of the "deny" persuasion, and there is also no way for them to produce an ACL with any of the "*_inherit" modes... AFAIK.

^ trevor?, hayne?, tw?, acme.mail.order?, agentx?, baf?, biovizier?, cwtnospam?, ganbustein?, Las_Vegas?, Mikey-San?, etc.,... anyone?: Am i not right about that?

EDIT: also note that the "master" ACL was applied directly to the /Volumes folder itself. [i.e., /Volumes did not 'inherit' it from anywhere else.] Even if it were possible for a Get Info window to produce such an ACL (which i contend is impossible), it would hardly have appeared on /Volumes in that form due to some user getting info on visible disk icons.

Quote: Originally Posted by mikeoscar Oh what the heck did I do?

Not sure yet who did what. It might help if you didn't skip over any questions (i.e., post #150 seems to have been conveniently ignored). As mentioned, i'd be interested to know exactly what DroboShare is (does it exist physically, or as a disk image?) and how you're accessing it (directly or via network?), and why (in post #141) does it only appear in /Volumes as an *empty* entity... but apparently totally invisible to both diskutil and df. That is really... mysterious (in a suspicious kind of way). What up with DroboShare?

Quote: Originally Posted by mikeoscar A better question is, what do I do now?

I seem to recall my post (#148) provided a chmod command with which to start out. The logical procedure would be to run that and then *relist* the whole mess so we can see what effect it had [and also tell us if it seems that normality has been restored overall.] Perhaps remembering to attach DroboCapsule this time would be "doable".

--

If it were my Mac, i'd go hunting for more instances of that crippling ACL. Most amazing to me is the overwhelming lack of interest in that critter... either from its (alleged) victims, or from the regular readers in this forum (both here and in that earlier thread).

-HI-

[trevor]

Quote: Originally Posted by Hal Itosis Most amazing to me is the overwhelming lack of interest in that critter... either from its (alleged) victims, or from the regular readers in this forum (both here and in that earlier thread).

Hal Itosis, I'm very interested in that ACL and where it started. If I'm seeming quiet about it, it's just because you're doing a better job than I would of helping with it. I'll chime in if I have anything of value to add.

Trevor

[Hal Itosis]

Google doesn't produce much, but here's an odd one [erroneously] claiming Apple put it there...
cryptomfs (a macfuse implementation of cryptofs): Issue 7: Potental Snow Leopard Incompatibility

It turned up in this Apple discussion (but doesn't seem to have caught anyone's attention):
HFS permissions from Windows 7

[drdillo]

Trevor:

Thanks to your instruction, I cleaned up my Volumes file, removing the junk and renaming the renaming to something that doesn't require quotes. Never would have gotten it all sorted out without your help. Mille thanks!

However, I spent a lot of time investigating/trying your instructions for blessing the System folder on my OS10.5.8 volume called “ALeopardCopy.” No luck blessing, though this is the volume I was using to run my machine when catastrophe struck, I had booted from it many times. There were two other SuperDuper copies, “BLeopard” and “ALeoB” which should have been bootable, too, though I am beginning to have doubts about SuperDuper being able to bless. I made a SuperDuper copy of the volume I had booted from, “eMac10.4.11” to another volume, now named “BeMacBackup.” Although all four of these volumes are listed in System Preferences>Startup Volume, I cannot boot from any of them. I did my first independent stab at UNIX (see immediately below) and the results seem to be that it can’t find a mount point for the volume. Disk Utilities said “Error - No valid packages” upon attempts to verify or repair permissions on “ALeopardCopy.”

I’m so thoroughly discouraged that the Oak aged Yeti in my ‘fridge might be my only escape. Wish you were here to share.
____________________
DUMP #1
Last login: Wed Dec 30 13:04:42 on console
Welcome to Darwin!
RMac:~ WALDO$ sudo bless -info /Volumes/ALeopardCopy/System/Library/CoresServices
Password:
No mount point for /Volumes/ALeopardCopy/System/Library/CoresServices
Can't get mount point for /Volumes/ALeopardCopy/System/Library/CoresServices
RMac:~ WALDO$

DUMP #2
RMac:~ Russell$ ls -alo /Volumes
total 24
drwxrwxrwt 13 root admin - 442 Dec 30 15:01 .
drwxrwxr-t 52 root admin - 1870 Dec 30 13:02 ..
-rw-rw-rw- 1 Russell admin - 6148 Dec 29 16:43 .DS_Store
drwxrwxr-t 40 root admin - 1462 Dec 25 19:45 ALeoB
drwxrwxr-x 42 root admin - 1530 Dec 25 19:43 ALeopardCopy
drwxrwxr-x 23 Russell Russell - 816 Dec 8 14:03 AMisty
drwxrwxr-x 34 Russell Russell - 1258 Dec 29 20:42 BAnnie
drwxrwxr-x 41 root admin - 1496 Dec 28 22:16 BLeopard
drwxrwxr-t 46 root admin - 1666 Dec 30 11:58 BeMacBackup
drwxrwxr-x 29 Russell Russell - 1020 Dec 30 15:28 CStorage
drwxrwxr-x 39 Russell Russell - 1428 Jun 28 2009 DAnnieOld
drwxr-xr-x 4 Russell admin - 136 Dec 29 16:41 Misty2 FW
lrwxr-xr-x 1 root admin - 1 Dec 30 13:03 eMac10.4.11 -> /

DUMP #3
RMac:~ Russell$ id
uid=501(Russell) gid=501(Russell) groups=501(Russell), 81(appserveradm), 79(appserverusr), 80(admin)

DUMP #4
RMac:~ Russell$ diskutil list
/dev/disk0
#: type name size identifier
0: Apple_partition_scheme *149.1 GB disk0
1: Apple_partition_map 31.5 KB disk0s1
2: Apple_Driver43 28.0 KB disk0s2
3: Apple_Driver43 28.0 KB disk0s3
4: Apple_Driver_ATA 28.0 KB disk0s4
5: Apple_Driver_ATA 28.0 KB disk0s5
6: Apple_FWDriver 256.0 KB disk0s6
7: Apple_Driver_IOKit 256.0 KB disk0s7
8: Apple_Patches 256.0 KB disk0s8
9: Apple_HFS eMac10.4.11 149.0 GB disk0s9
/dev/disk1
#: type name size identifier
0: FDisk_partition_scheme *149.1 GB disk1
1: Apple_HFS DAnnieOld 149.0 GB disk1s1
/dev/disk2
#: type name size identifier
0: Apple_partition_scheme *931.5 GB disk2
1: Apple_partition_map 31.5 KB disk2s1
2: Apple_HFS CStorage 931.4 GB disk2s3
/dev/disk3
#: type name size identifier
0: FDisk_partition_scheme *931.5 GB disk3
1: Apple_HFS BLeopard 500.1 GB disk3s1
2: Apple_HFS BeMacBackup 200.1 GB disk3s2
3: Apple_HFS BAnnie 231.3 GB disk3s3
/dev/disk4
#: type name size identifier
0: Apple_partition_scheme *931.5 GB disk4
1: Apple_partition_map 31.5 KB disk4s1
2: Apple_HFS AMisty 465.6 GB disk4s3
3: Apple_HFS ALeoB 232.7 GB disk4s5
4: Apple_HFS ALeopardCopy 232.8 GB disk4s7

[trevor]

Quote: Originally Posted by drdillo I’m so thoroughly discouraged that the Oak aged Yeti in my ‘fridge might be my only escape. Wish you were here to share.

Well, one quick and easy way out of this is to grab that Oak Aged Yeti and open it but don't start drinking yet. Then start an Archive and Install onto ALeopardCopy from your Leopard Install disc. If you leave the box checked to preserve users and network settings (it's checked by default), then Archive and Install will leave your users alone. It also leaves your installed non-Apple apps alone, and just replaces your System and whatever Apple apps get installed from that disc, like Mail.

It will also, of course, bless the System, and you'll have a sparkly clean new Leopard install on that disc, but all of your formerly setup stuff.

Once you've started the install, carefully drink the Oak Aged Yeti.

Trevor

[Hal Itosis]

... ::drool::

[drdillo]

PR, acclamation, acknowledgment, applause, approbation, celebration, cheering, clapping, commendation, eulogizing, exaltation, honor, kudos, pat on the back, pat on the head, plaudits, praise, puff, pumping up, rave, recognition, strokes, stroking
--------------------------------------------

Props, duuude! The A&I, once updated, seems to have done the trick!

Have drunk Yeti (pic enclosed). Very much indebted for your thorough and understandable help.

Russell