Loophole

Oh I see Looks like I was confusing them (Docker & VM in general) Yep definitely backing up the flash, checked that before thanks for the clarification

Hey @Squid Nice work on this plugin! I was going to roll something similar as a script before I found this. Nice Job. Bug: Docker img (libvirt) is not backed up if its not in the right location (which I cant find documented anywhere) or named correctly I use /mnt/cache/docker.img as I setup docker ages before I found this plugin. a field to allow customisation of the libvirt source image would be ideal Comment on functionality: The "Delete backups if they are this many days old" doesn't make a lot of sense when used with anything other than a daily schedule. Eample scenario Initial Setup Set "Delete after" to 5 Set "Schedule" to Daily Outcome: 5 backups kept Changed my mind and I want weekly backups now Set "Schedule" to weekly Forgot to calculate how many days I want (7/14) to keep relative to the schedule type so it remains at 5 Outcome: the weekly backup is erased after 5 days leaving 2 days before the next scheduled backup takes place. Worse again Changed the "Schedule" to monthly and forgot to adjust the days to keep (31/62) so it stays at 5. Outcone: a Backup is created at the specified monthly interval and is then sebsequently erased after 5 days leaving 3/4 of the month with no recovery option. A possibly better and simpler solution to this issue would be to change the "Delete after" to "Backups to keep" in this way it would not matter about the schedule at all as you always know there are X daily/weekly/monthly backups at any given time. I did actually run into this exact scenario (the weekly one) and thought you should know. Keep up the great work

Yes it will fix the issue but if you can hold off for another day Phaze will have his update for V6 complete and the pluin will then work as expected.

Hi All For those of us still wanting to use Phaze's great PMS plugin here is the workaround to install and use PMS 1.0 with it. 1) download the PMS 1.0 UNRAID file from the Plext.tv downloads page 2) rename the file so it adheres to how Phaze has named the downloads like this -> Plexmediaserver-PhAzE-1.0.0.2261-a17e99e-x64.txz 3) copy the renamed file into /boot/config/plugins/Plexmediaserver 4) backup and remove the previous PMS .txz files as if this doesnt work you will have to scour the interwebs like I did ;( 5) reload the plugin in your browser. If that fails to show the new version uninstall and reinstall the plugin (you may have to reenter your config) or restart your server. 6) on the Settings -> plex media server you dhould be presented with an install button. Click it and enjoy PMS 1.0 NOTE this is only a control workaround only and updates and plex pass creds etc will still not work until Phaze has updated the plugin intself. HTH and Thanks to Phaze for his immense contributions to making our lives that much cooler!

@Phaze In the interim until the plex site is updated is there a manual way we can put in the PMS 1.0 release (download from plex.tv) so it installs correctly via the plugin? Or alternatively a command that we can run from the terminal to get this running with the plugin settings? I see in the plugin script there is startcfg.sh which is indicated as the launch point for starting and stopping with. Thanks for all your amazing work.

I didnt actually boot into safe mode. But un assigning the cache then check with xfs_repair -n /dev/sdd1 then xfs_repair /dev/sdd1 then reassigned my cache, start array and all my shares returned on the share management page. PS : You can get the device id on the main page after unassigning then check the /dev folder for the numberd partidion in my case it was sdd1 not sdd. HTH and yes this is very weird

*Slaps Forehead* Yes that was it! it has been such a long time since I added a drive vs swapped out that I had forgotten there was a global on/off for each disk in the share. Thanks for the heads up Loophole

I am not yet in need of a Pro license but a bonus on the plus of adding an eighth drive (ala 6th data disk) was a nice surprise in b13 for us Plus users. So today I added an eighth drive (disk6). It had previously been precleared before it had been swapped out for a larger drive, So I just let the Unraid interface clear and format it as XFS. So now I have 6 data, 1 Parity and 1, cache drive. No probs there everything looks sweet. I go to my shares as I want to update them as I now have a new disk for a dedicated share. I look at each share and in both the included and excluded disk list there is only disks 1-5, no disk 6? I have stopped and started the array and even done a full shutdown, but the issue remains. This may be an issue with the UI or something else i'm not sure On a side note if I stop the array and modify a shares config file manually, adding disk6 to the included disks, then restart the array. it still doesnt appear and if I hit apply on the share it removes the disk6 from the included disks in the config file. Mods : please move this as appropriate as I was not sure if its a defect or just me? Any help or pointers to resolve this greatly appreciated Loophole

This seems to be fixed in the current webgui version. Am also running 5.05 and just manually started the mover with no issue. Regards

+1 in all respects. I, too, am a TM user. I have multiple Macs backing up to unRAID and I'd hate to go back to individual USB drives for them. Apple is clearly working to drop AFP, its just a matter of time. Unlike the NFS v4/3 debate, where you can't effectively have 'either' you must choose one, the issue with AFP seems simpler, you either have it or not. The current implementation of AFP in unRAID has been extremely stable for me since 5.0.3. I'd like to see AFP in unRAID v6 at least until Apple finally kills it off. +1 From Me too as AFP is now only use for timemachine network backups it will only be a matter of time before they move over to SMB2 which hopefully will be more compatible and stable with problems like network stability, connectivity and the like. So in essence Yes prepare to remove AFP but just not yet or possibly make it only available as a time machine option. One thing I have been doing via a modified config is to push all the .AppleDB cache files to the cache drive. This effectively then does not pollute every folder that the afp share has available and seems to be generally faster for large file access. YMMV Regards Loophole

Ok booted into safe mode and tested several moves. No change in schedule. Booted with webgui plugin installed and problem returns although I am unable to ascertain if the gui is just not parsing the params properly or if its actually adjusting the schedule. Looks more like its the former. So the next question is how does the community help fix/upgrade the webui plugin? or are we even allowed? As Unraid is really good many of us just want to contribute Regards Loophole

Ok my bad for not testing as thoroughly as I thought I had. It seems that I found this glitch in an earlier version and had not tested in 5.0.4 Sorry This topic can now be removed or locked . Again Apologies Loophole

Additional Syslogs attached. I noted in them there is a parse error for the mover cron daemon which may be the cause of the reset to monthly. I also removed all the mover file log lines as they were 99% of the files anyway Keep up the good work Loophole syslog.1.txt syslog.2.txt

This is Just a UI Bug in 5.x (tested in 5.0.2, .3, and .4) After setting the time machine user share and volume size limit the size limit is not shown. ie the size limit box is empty. I have looking in the sheres config and the value is there it is just not being shown on the UI. Time machine shows the volume size correctly. I have not added a syslog as this is just a UI glitch . I can add one if required but I know it will not shed light on the non display of variables from the settings. Currently running Unraid 5.0.4 Regards Loophole

UnRaid V 5.0.4 Apologies for not adding the syslog Mover was set to Daily at 1am the syslog the mover shows moving a slew of files at abou that time. I triggered the mover manually at approx (9:10 Am ) as there were no files to move not much shows. The interface has now reset back to 1st of the month. What other logs can I supply? Regards Loophole syslog.txt

This bug is not major but might cause some issues for those with small cache drives. Tested Under 5.04 go to shares settings and check if the mover is set to the 1st day of the month. change it to say daily and hit apply. It will change. now hit the move now button. Assuming you have some content to move the "move now" button will become greyed out and the schedule will reset to the 1st of the month. Workaround : Hit move now and wait for it to finish then reset the schedule to your preferred time / date. HTH Loophole

Backed up Unraid and moved it to newly formatted via Win7 full format 32K clusters sd card . I am Using the Kingston G2 SD reader so this is much simpler. No change lots of Error still showing on check. Moving remaining data from disk 4 to external storage then will completely empty the share attached to that particular disk and check again. Also replacing Disk3 as it noted as having power up issues with the 1TB Samsung . As there was nothing on Disk 3 anyway luckinly. this is a no brainer and will happen after the data from disk 4 has been removed. Anything else I should be doing?

Thanks for the help My System is as is follows Unraid 5.0 RC16c Plus Antec nine hundred two V3 Coolermaster 550W Single rail 2x Notco SS-500 MB : Asus P5QL Pro CPU : C2D @2.66 Ghz 8192 Mb DDR2 Ram @800 Mhz (4x 2Gb dimms) Drives 2x WD 3.0 Tb Red NAS (1x Parity, 1x Data) 2x WD 2.0 Tb Green with wdidle fix 2x WD 500 Gb Green with wdidle fix 1x WD 320 GB Green with wdidle fix (cache) 1x Samsung 1.0 Tb (not in array) All drives passed smart tests but Drive 4 showed powerup issues could this be the source of the problems? I am copying all data from Disk 4 to external storage then I will remove it from the array and see if that fixes it but in the mean time could I please have any feedback/notes on the syslog and smart tests please. Your help is appreciated Checked the bios for voltage levels - all within spec Attached Logs for all smart reports and log.zip

Ok so here is my syslog It should be noted that the first Check was the monthly sceduled one while the second was manually triggered by me then cancalled when I realised it was correcting not checking (oops) and the third was a checking but cancelled when it showed that lots of sync errors were appearing straight away. I really just wanted to know if this is expected behavior or not? I thought that as the parity is updated as data is added to the array sync error should be minimal? Thanks for any insight offered syslog.txt.zip

Hi All I am a bit baffled by this but for a long time now (should have paid more attention!) EVERY time I do a parity check I get a huge amount of sync errors in excess if 1.5million errors. If I correct the errors then check without correction errors are listed straight away! All drives are showing as having 0 errors and I have checked the smart status of all drives with no issues found. This is a concern and I want to know what is going on and how to fix it please. Running 5.0RC16. Any pointers, info, explanations would be appreciated. TIA

Thanks overbyrn Will check it out tonight on the way hm from work Much appreciated

Not strictly correct. An earlier post from Tom ... http://lime-technology.com/forum/index.php?topic=14665.msg138228#msg138228 /boot/plugins/ = "system" plugins /boot/config/plugins/ = "user" plugins Thanks for the Clarifications on placement of plugins As to the examples... Looks like I will just have to get various ones and check their source.

Hi all I have looked far and wide though the wiki, manual and these forums but I cant seem to find a definite set of docs that specify how to create a plugin for unraid 5.0. I have also seen that some reside in /boot/extra (eg plex) and some in /boot/plugins (eg simple features) so which is the correct/recommended location? Thanks for any info Loophole

aah i see thanks I did a new config and set all drives appropriately. Now proceeding with parity sync.... Still makes me wonder about the swap-disable issue though? Anyway its working and thats the main thing.

Well after doing a new config everything went fine except i noticed one of my other drives was now producing smart errors ;(. So I backed up all the data and swapped the newly fault 2tb for an extra 3tb which I was going to replace one of my 500gb with. In any case after starting the server I could not even start the array ( See attached pic) I know I had to do a parity sync but that should not stop me from starting the array with the upgraded (and unformatted) drive in place. This seems like a major fault, Can someone please verify this is the case? words of wisdom are always appreciated Should I start a new topis for this as it seems related to my initial issue which included upgrading a data drive?