mortstar

I've been trying to get Syncrify working from the template over at Dockerhub https://hub.docker.com/r/pducharme/syncrify/~/dockerfile/ but the app seems to die straight after the launch. The log looks like this: Starting Sycrify Incremental Backup Solution... Removed stale pid file: /var/run/Syncrify/Syncrify.pid :lib/SyncrifyServer.jar:lib/ant-launcher.jar:lib/ant.jar:lib/gwt-user.jar:lib/mail.jar:lib/tools.jar:lib/wrapper.jar repeated for each start. The template seemed to be missing a config location so I added a /config to my 'appdata' share, this didn't fix it but I assume this needs to be added in to the template somehow? Did anybody ever get this working?

This is absolute not true. Maybe you had the global share include/exclude masks set wrong? In the future it's helpful to post your system log in these situations. I initially had the Global Share Settings of Includes and Excludes set to Includes: All Excludes: None Then I tried: Includes: disk3 & disk4 Excludes: None Neither setups worked and displayed the same symptoms. My diagnostics logs are right there in the first post.

I never wrote any data to the array in the old config (as the User shares were not being created), though it did have a parity drive assigned. When I changed the config, I assigned the same parity drive as was used in the old config and the User Shares are being created. I'm running a Parity Check on the array now.

The USB drive was fine. I've created a 'New Config' and moved the data disks from disk3 and disk4 to disk1 and disk2 (which were previously unoccupied) and that has fixed the problem. So for reference, anybody doing anything weird in the future like having empty drive numbers, this breaks User Shares. The disks have previously been pre-cleared, partity synced (whilst in positions disk3 and disk4) and parity checked. Will I need to do the parity sync and check again with this new disk positioning (disk3 has moved to disk1 and disk4 to disk2)?

I've done a number of restarts (at least 3 this evening) and have tried different share names 'Films', 'Misc', 'films', 'test', 'Balls'. All with the same result.

Yes they are, when trying to add User shares on the web interface they never show up in the list of User Shares. When creating a new share the page either just refreshes to the Share Settings page (with all options reset) after clicking 'Add Share', other times it'll display this message "Share Misc has been deleted."

I've been using Unraid for a number of years and currently have a 'production' device on v5.0.6, this has 4x2TB and 1x1TB in a 7TB protected array with a 240GB SSD cache drive. I've begun creating a entirely new system with new 3x4TB disks on v6.0.1. I've initially set these up in a 1xParity and 2xArray setup in Trail mode, this is so I can transfer over the data from the existing Unraid server, before moving over a couple of the old hard drives and the cache SSD along with my Pro license. I've pre-cleared, parity sync and then finally parity checked all 3 of the 4TB hard drivers over the weekend and am finally in a position to create a User share and begin copying the data over to the new server. I've hit a stumbling block on this, what should be simple step. The server just refuses to create any user shares. Looking at the console of the server the system is creating a /mnt/User folder but on trying to 'cd' to it I get a 'No such file or directory' error. See output here: root@Tower:/mnt# ls -l /bin/ls: user: No such file or directory total 0 drwxrwxrwx 2 nobody users 6 Aug 16 21:11 disk3/ drwxrwxrwx 2 nobody users 6 Aug 16 21:18 disk4/ d--------- 1 root root 0 Jan 1 1970 user/ root@Tower:/mnt# cd user/ -bash: cd: user/: No such file or directory root@Tower:/mnt# The only 'weirdness' I can think is that I have put the initial 2 disks as disk3 and disk4 (not disk1 and disk2) as these disks will be transferred over from the old server once the file copy is complete and match the physical location of the hard drives in the server for location/diagnostics in the future. I've attached the Diagnostics.zip so hopefully somebody might be able to help me out here. tower-diagnostics-20150817-2004.zip

Just want to put a big thanks for the 5.0.3 release. I upgraded from RC12 on a Unraid system hosted on ESXi using RDM drives, which I know isn't best practice. After the upgrade I've got drive-temps in the dashboard for the first time. I've always had drive spindown and that has continued to function in this release. Really impressed with the stability. Cheers!

Sorry I meant physical locations, so from 2 different offices in the UK, using completely different net connections.

The download page doesn't seem to be working, I've tried from a couple of different locations to get 5.0.3 (and the other releases as a test), from 2 places in the UK and 1 in the US, but all downloads start and then stop abruptly. Is this just happening to me?

Got the iTunes server running well, had to change the package address to the latest SQLite in the Slackware repo to get it installed. I have a question for anybody who may be familiar with Android devices. I'm just moving over from iOS and the only thing I'm missing - but something which is pretty big for me - is Airtunes support. Does anybody know an app which will connect to the daapd server running on Unraid and also allow me to send the audio to Airtunes speakers? Reading the forked-daapd project on GitHub looks like this should be possible - but maybe I've got the wrong end of the stick.

I have two WD10EADS drives that I have been using in a D-Link DNS-323 for about two years. I would like to move one to my new Unraid box and leave one in the DNS-323 for backups of system images, unrecoverable personal media (which will be primarily hosted on the Unraid box). From my amateur eye, the HDD WD-WCAU45276695 is healthier as it had 0 re-allocations before or during the pre-clear cycles, whilst WD-WCAU45501747 had 297 re-allocated sectors. Is this a correct reading of these results? Can I trust WD-WCAU45501747 to hold my backup data in the DNS-323? Thanks in advance for any help. preclear_finish__WD-WCAU45276695_2012-04-12.txt preclear_rpt__WD-WCAU45276695_2012-04-12.txt preclear_finish__WD-WCAU45501747_2012-04-12.txt preclear_rpt__WD-WCAU45501747_2012-04-12.txt

Really enjoying using this web interface over the default, not only that, but you've brought some really great features to the party. I've got a couple of suggestions that have already been mentioned in the thread but just wanted to '+1' them. I've disabled the scheduled parity check as it doesn't contain the NOCORRECT keyword and gone back to the monthly_parity_check.sh script. Since disabling the schedule SF is adding: to crontab, which throws up errors. So, could we get the option to not automatically correct parity on a check and if the schedule is disabled to not add the blank cron job? Secondly, could we set the level at which SF emails notifications? If everything is working as it should, I don't want to receive an email. I only want to get an email when there is a problem. Many thanks and keep up the great work!