remotevisitor

In Linux the permissions to delete a file depends on the write permission of the folder that contains the file and execute permissions on all parent folders not the file permissions/owner.

Did the test duplicate file that you created exist in the same place on different disks. So if you have a duplicate file at /mnt/disk1/TV/series/file and /mnt/disk2/TV/series/file (just the name has to match, not the contents) then this script will report it as a duplicate. This often happens if you re-organise the data in a share by copying rather than moving the files between disks. As the contents of the 2 disks in the above example would be merged together under /mnt/user/TV to create the TV share only one version of the file will be visible at /mnt/user/TV/series/file, which is why it is useful to identify which files are duplicated and remove the duplicate. i suspect that you were expecting it to report files which have the same name and/or content in random locations .... unfortunately this script does not address this problem.

Did you apply the work around Squid posted about 3 post back in the thread?

Sorry I didn’t follow up on this, was away from home on a flaky Wi-fi connection at the time...... have you managed to get it working in the mean time?

On the windows box what name does this command return: nbtstat -A 192.168.0.15

I suspect your windows box thinks the connection to your new virgin media router is a public network rather then a private network and therefore the windows firewall is blocking the SMB connection to your unraid box.

You are so right .... Looking in the syslog of the referenced issue shows that Fix Common Problems was correctly reporting that disk5 was read only. Wonder if it is possible to update the reported issue to include a suggestion that a possible cause of an array disk being mounted read only can be due to file system corruption and provide the steps to perform a file system check on the disk. But need to be clear that this is not the only possible reason a disk can be read only.

Another suggestion of an issue to detect (inspired by the recent posting http://lime-technology.com/forum/index.php?topic=51046.msg489900 ), is to detect disks in the array mounted read-only and suggest running the appropriate file system check/repair. Not sure if this has to be done by looking in the syslog, or whether the output of the mount command would show it mounted read-only in such circumstances. Testing it may be a bit of a challenge :-)

Another suggestion for a check that I cannot see in the list of checks done ...... The use of legacy IDE disk interface. I have noticed that this is a frequent observation when people's syslogs are examined for problems.

Does the plugin check for user shares which have the same name as disk shares? I couln't see this check in the list of things checked but maybe I am just not looking hard enough. I know a user had this problem a week or so ago when he attempted to copy the contents of one disk to another and accidentally created the directory on the save disk with the name of the original disk. Then when he rebooted the auto created user share 'hid' the actual disk share.

Other checks that occur to me are: Check for duplicate files on shares. Often happens if users copy (not move) files between disk shares. I have seen user scripts in the forum for detecting them, so suggest seeing if the authors are happy for you to incoporate them into your plugin Check for files/directories owned by root on user share Zero length files on user shares. Whilst there could be reasons to have zero length files, I suspect in most cases they are indications of previous problems creating files .... Such as trying to copy files from a disk share to a user share. As these are checks that might take a while you might want to add them under an 'Additional Checks' section.

What about shares names that differ only by case, so that only one share actually appears .... I have seen reports of that before now.

The license keys are not specific to the version of unraid. So your 2 pro keys can be used with version 5 or version 6 .... No additional cost involved.

When this plugin installs it attempts to do: # fix permissions of executable files chmod +x /usr/local/sbin/readvz However this file does not exist and therefore always generates an error message (as can be seen in several earlier posts of installs in this thread)

For the 2nd problem use the command line option '-i Movies' rather than '-i /mnt/user/Movies' ... The /mnt/user is automatically added to what is supplied to the -i parameter's value.