Influencer

I have one a little over 5 years old, its 1 tb. I have others 6-9 years old that are smaller but they are rarely powered on so I wouldn't count those.

If you happened to name it Disk1, capitalizing the D, unraid and any linux OS will treat it as a separate directory from disk1, but windows will see it as one and will show the contents of the first one that it "finds". Not sure if that's what is going on here, can't see the pictures too good on my phone.

If you are using windows it has a habit of using files all the time behind the scenes, indexing, creating thumbs, etc. Sometimes it just doesn't know when to let go. Also, deleting via telnet should always work as your logged in as root, what it most likely means is your permissions are not set right. You can run new permissions from the utility page to fix that (i believe its the utility page).

A good friend of mine is a manager at radio shack, think ill have her pick a few up for me. She'll already be fighting the crowd, no reason for both of us to. My black Friday records are impressive, I talk to employees to find out where the items I'm interested in will be placed, get there a little early, listen to an audiobook while waiting, doors open, I'm in and out in under 10 minutes. I've walked out of Walmart with a tv, camera and 2 32 gigabyte Sd cards from 5 am door opening to 5:07 I was pulling out of the parking lot.

You can change the path, make sure to do it in /boot/config/plugins/vfs_recycle/config/smb-extra.conf and then stop/start the plug-in for the change to take effect. The plug-in won't work on 4.7 but the recycle MIGHT, depends on what version of samba is installed.

Since 5.0 there have been issues between SF and unraid, mainly (and possibly only) if the user upgraded to limetech's webgui. Its an optional step that you would have had to select to upgrade (I think its on the settings page?). If you upgraded you can downgrade by removing the webgui plug-in and package from /boot/plugins/ (which you don't have so its safe to say you didn't do). It means parts of Sf are not working, which are of no fault to the SF dev(s). I can see how you don't have much trust in SF, and to each their own. I've never ran most of the extensions for Sf myself but have used it for quite a while now with no hiccups. Sf did a lot with very little adding a lot of functionality to the webgui, but is done in spare time so sometimes there are bugs that aren't squashed immediately. Teamviewer is a remote login type of application, basically you can download an executable that you do not have to install, run it and it will give you a unique access ID and pin number. You give the other person this information and they can access your desktop. Once you are done (you retain control of the system during this), you can exit out of the application and the next time you open it up the access ID is the same but the pin is different, so even if I've remote accessed your pc before, I can't do it again. Teamviewer is also handy if you have not-so-technologically inclined family members or friends. I have Teamviewer installed on my parents PC as well as my wifes and sons, it starts when the pc does and I can access their pc from mine or even from my phone, making fixing something for them very quick. Of course they can always shut down the application and run it when they need help.

Have you rebooted since you actually removed the file? Either that or you'll have to us lsof or fuser to find what PID has that file open (not sure how that'll work since the file is gone) and either kill the PID or the filehandle.

Actually, simpleFeatures was very stable in the Beta's and I believe only causes issues with unraid if Limetech's upgraded webgui is installed (which is a port of simpleFeatures). Almost 200 pages in a thread is no reason to steer clear, I have a thread that is at 148 pages, a lot of it is questions, some bug reports and feature requests. SimpleFeatures has been around for quite some time, something assuredly wouldn't happen if it was that buggy. There is very little documentation ATM and I haven't ran into any plug-ins that change any system files permanently. Almost all changes are done on the Ramfs and are reversed by a reboot, some changes, such as the VFS_recycle plug-in I just released, modifies a file on the flash drive to include the recycle bin, but disabling it removes the modifications. Again, plug-ins are in their infancy, there is little to no documentation at this time as the system has not been completely designed yet. 5.0 included more framework but plug-ins are a long way from being called mature. Would you be interested in a teamviewer session to see if we can find the cause of the error?

no, the file its looking for is not located on the flash drive, it is located at /usr/local/emhttp/plugins/simpleFeatures/include/SystemTemp.php Although the very reason that it cannot open it tells me the file most likely will not exist. There is something left over looking for that file, did you do a reboot after removing/hiding all of the plug-ins? Is your unraid installation "normal"? For instance, you have unraid installed to the flash drive and not a disk, not a esxi build, etc?

Do you have anything in /boot/extra? or /boot/plugins? There is no real documentation on plug-ins yet as the framework was laid out and users ran with it, but there is no official support. It is being worked on.

The links good so I can only assume its a bad checksum. If not that your server is having trouble accessing the internet to download it. You can click the link in the log you posted to manually download libmcrypt and place that file on your flash drive in /packages/. Then re-run the install and it should pick that package up and install it.

Installplg is working fine, where its deleting directories it was deleting the empty doc directories which are not needed. The problem is it failed to download libmcrypt, probably because of a bad checksum in the plugin or a broken link.

Here's the initial release. I've been using it and have sent it to a few other users. What the plugin does: Once enabled the plug-in copies the config to your smb-extra.conf, if the file does not exist it is created. Here is the config: #vfs_recycle_start #Recycle bin share [bIN] path = /mnt/user/BIN read only = No #vfs config [global] vfs objects = recycle recycle:repository = /mnt/user/BIN/%m/%P recycle:keeptree = Yes recycle:touch = Yes recycle:versions = Yes recycle:exclude = *.tmp recycle:exclude_dir = /tmp recycle:noversions = *.doc #vfs_recycle_end Do NOT remove the comments from the config, they are used to add and remove the config if a user wishes to disable the recycle bin. Options will be added in the near future to allow customization of the recycle bins path as well as repository options, as for now it will create a share named BIN, when a file is deleted it will be put in a directory named after the current user, and then in the full path to the file so you will know where the file came from if you were to wish to restore it. Also included is the option to permanently delete the trash once a week. Enabling this feature creates a cronjob that runs every Sunday at 3:30 AM. Default the cron will be set to remove files that were deleted/trashed over 720 minutes (12 hours) ago. This option is user configurable and MUST be in minutes. I chose minutes as I believe this will allow the users the most flexibility on what files to delete. To delete everything simply set to 1 minute. 0 minutes should work fine too but I haven't tested that. If you want every file older than 7 days deleted, set it to 10080. Also when on the plug-ins settings page you'll notice a trash bin on the left side of the screen. This bin will change from an empty bin to a full bin when you have trash, as well as reporting the current size of the bin. You may manually delete everything in the recycle bin by simply clicking the "empty trash" button. This will save less experienced users from possibly having a typo and removing a lot more than they intended. Alright, so that should explain it all. Until options to modify the paths are added you may edit the smb-extra.conf located in /boot/config/plugins/vfs_recycle/config/. This is the base file used to add/remove the config from samba. If you wish to add anything to it just be sure to keep any additions/changes between the #vfs_recycle_start and #vfs_recycle_end comments. Grab it HERE! (right click > save as)

If the plug-in is present in /boot/config/plugins and named with extension .plg it will be installed at boot. To uninstall you either need to 1) know what files were installed and where, then delete them or 2) remove/rename the plug-in and reboot the server. Rebooting the server is easiest and you'll know for sure that it is uninstalled. In /boot/config/plugins I have another directory named "disabled", that's where I put any plug-ins I don't want reinstalled when I reboot.

Ok, was just wanting to make sure I wasn't translating something wrong. I think there are a lot of scripts that the more linux savvy users have written that would be great for the community. One to find possible corruption such as this is one of them.

Does that script your using not return a lot of false positives with ANY file that has an M in its name?

The share that sabnzbd resides on should be cache only and the mover script should NOT move it. You would do this by going into the share settings and the setting named "Cache disk" should be set to "only". Doing this will keep all files in 'appdata' on the cache drive. The share can still be exported like a normal share and you would interact with it through that share. Of course you could setup categories which will work fine if you choose to setup sb and cp, but nzb's grabbed from dropbox will be set with the default complete folder. Basically anything in here you have to manually move to the final destination. If you are having trouble because of permissions, make sure the folder permissions setting is sab is open enough for you to access.

Something is adding illegal characters to your share names. \ / : * ? " < > | Those characters are illegal on Windows using NTFS, and all of those plus ^ if using FAT. In Linux the only illegal characters are the colon : and nul byte, \0. Note that the illegal characters can still be placed on a NTFS file system as long as an application that uses the unicode api is used. But when you view the files with an application that does NOT use the unicode api, the file names will appear screwed up. Have either of you tried using telnet to see the file name? I believe they will appear normal with the addition of an illegal character.

If you set the recycle bin as a share and not one for each share you would bypass that issue. I'm still not sure why someone would want a different bin for each share, set up as it is now it will keep the path so you'd know what share the deleted files came from.

I've sent the plugin to a couple people to test, works fine for me so just making sure it works good for others as well. I'll eventually add in a couple more options but currently you can either manually delete via the settings page or choose the option to delete automatically via cron. If that option is enabled you can set how long to wait before a file is deleted. The cron currently runs Sunday morning at 3 am. I could do daily but I figured once a week should be enough.

Did you get your directories fixed? And are they screwed up on the server or through the samba shares?

Ok, I'll bite, but it'll be later when I reinstall mirc,

So you'd want something that would basically run a weekly cron that checked each files last access date (which is 'touched' by samba when its recycled) and if its been in the bin for more than 30 days to remove it? The number of days could be made configurable, just trying to make sure I got what your saying right. I guess I figured if I deleted something by accident I'd probably know immediately so deleting once a week would be safe. But at the same time if it happened to be 10 seconds before the cron was scheduled, might not have time even if the user immediately tried retrieving it.

I guess it depends on what direction Tom is wanting to take this product. To me I view unraid as a great HOME media server solution. I don't see companies like Netflix or Hulu using unraid to store and serve their data, plus with the money they make features like mixed disks just doesn't mean as much to them as it does to the hobbyist. I stream from my server all the time and with three kids I'm fairly confident in saying something is streaming almost all day long. That being said, High Availability wouldn't be a feature I'd pay extra for and honestly would rather Tom spend time on other features. At the end of the day unraid is a media server solution that we happen to also use for other personal files and documents as well. None of my media is crucial that I be able to access 24/7 so in the event of a failure I could wait to fix things and get up and running again. Would be a minor nuisance and annoyance, but not crucial.

/boot/plugins is for system plug-ins while /boot/config/plugins is for third party plug-ins.