trurl

Almost there. Uncomment the soap line in dynamix.php.cfg

Where exactly are you stuck? Have you downloaded phpvirtualbox and put it in the Dynamix webserver? Is phpvirtualbox still not part of the virtualbox package? I thought it was. I thought that was one of the items that it installed from the virtualbox gui. I see it mentioned a lot but dont see how to get it or install it. EDIT: okay I got phpvirtualbox from sourceforge, and have it extracted. what do I need from here? do I dump all of it into a location, or just a select few items? vboxwebsrv is installed, but you need something to talk to it. Download phpvirtualbox and put it in the web root you set up in Dynamix webserver.

Where exactly are you stuck? Have you downloaded phpvirtualbox and put it in the Dynamix webserver?

I really like my Q25B, but this case is sexy! I have had as many as 7 drives in my Q25B but right now I am just using the 5 hotswaps plus an SSD for cache. 8 hotswaps would really be ideal for a plus license, since it would allow one extra for preclearing or mounting outside the array. I will probably resist this temptation for a while at least since I don't really need the space but I won't be surprised if I go ahead and buy it without justification when it becomes more readily available.

Similar to mine. I had to update BIOS too. All of my bays are full and I have an SSD cache drive so I am also using all SATA ports. I went with a different processor in case I wanted to do some of the more advanced virtualization. You should unbundle your SATA cables. They can interfere with each other (crosstalk) if they are running parallel for long stretches.

Looks like I need this for System Temp to work on my new mobo. Can anyone build it from source?

Dynamix has replaced SimpleFeatures and it has a webserver for unRAID v5.

Sounds like you have SimpleFeatures installed or maybe Dynamix. These are not compatible with the Limetech "new" webGUI, which is the subject of this thread. Go read the Dynamix thread to get stats and health set up.

I had same problem. See here

You do know that folder is in RAM? Anything written there will not survive reboot.

In v5, if you make the folder part of a cache-only share it won't be moved even if it doesn't start with a dot (.)

unRAID has a RAM filesystem where all of its operating system files are kept. When unRAID boots it unpacks all of its operating system files from bzroot and keeps them in RAM. Since bzroot is not altered to reflect any changes to these operating system files, they will all be restored to the original from bzroot when you reboot. This is why anything stored in any of the usual linux operating system folders does not survive a reboot. In general, anything not in /boot (your flash drive) or /mnt (actual disks or shares on those disks) is in RAM. Anything stored in these locations will persist after reboot. This is why some people add code to the go script to alter operating system files every time they reboot. I have code in my go script which alters /etc for example. You can put those packages in /boot/extra and they will be automatically installed on boot. Add the other script to the script in /boot/config/go (like I have just done. Thanks for this)

Not sure I understand your problem. If you want guests to be able to read/write a share make it Public. If you want guests to only be able to read a share make it Secure. If you don't want guests to have any access to a share make it Private. You can also make shares hidden so it can't be seen when you browse. The only way to get to these is to specify the path. Are you anticipating guests accessing your server from: One of your computers using your Windows user? Using one of your computers using a separate Windows user? Using their own computer using their own Windows user? Some other scenario I haven't imagined? Where is a workaround required?

I have used every scenario Tom describes here, including referring to the server by IP to get a different login to my server. I can confirm that it all works just as described for me.

I've been using this for pre-clears since my case is full and I have one sata port left over: eSATA enclosure This particular one even came with an eSATA bracket

Go back to page 73 of this thread for more discussion of these parameters. I was trying to do 3TB. Increased -b parameter is what you need. Did that but did not find anything concerning a -b parameter... Since there does appear to be a relation with these parameters (I conclude this from your reply) I will take my chances and do the preclear without the extra parameters, if only to see if that makes the difference.. Sorry, wrong thread. Try this instead. When I tried it on 3TB with the defaults (no parameters) I ran out of memory. The originally suggested -b 200 parameter was too conservative and caused it to be very slow. -b 256000 was suggested and I stopped mine during post-read and restarted it like this.

Go back to page 73 of this thread for more discussion of these parameters. I was trying to do 3TB. Increased -b parameter is what you need.

The emails are sent to the same address the system notification emails are sent. This can be setup in the simplefeatures email notify plugin. There is also an unMenu package but I don't use that method anymore since I upgraded from 4.7

Working for me. At first I tried to increase the size but I closed the page before it finished and that didn't work so I tried again and waited for it and it works. Thanks

What Joe said. Linux "screen" lets you reconnect if the session dies. Preclearing With Screen There is also a plugin.

Longer answer: Because the OS is running completely in RAM (this includes any "files" in the usual places, such as /etc/sudoers) any changes you make in the running OS is lost when you reboot. To make a change that will survive a reboot, you need to make the system make those changes for you each time it boots. This is usually done in /boot/config/go script file which is run automatically after the system boots.

How would it anticipate a file being opened?

I ran the new version twice this afternoon and can report that log packaging and cleanup is working as intended. Both times rsync completed without errors so I haven't really tested what happens when it fails but at least it looks like I managed to get all of my filenames cleaned up. After the first run I didn't get an email so I looked at the script again and noticed that there was no email for success (I just love getting notifications from my unRAID) so I put in an email on success before the second run and that worked too. One thing that didn't work was Dropbox. After each run I waited for the log to show up in my Dropbox but it was stuck on the unRAID side. I think Dropbox had probably crashed due to OOM or something. A lot of OOM going around these days as people try to squeeze more apps into their server. I tried to restart Dropbox from the webGUI but that resulted in SAMBA crashing as well and I had to reboot. I didn't bother to capture the syslog. I don't know if the size of the rsync log (about 16MB on each run) had anything to do with this or not since I am not really clear on all this Linux memory management, low memory, swap, etc. I do have a swap file and 4GB RAM. I will investigate further if it continues to be a problem.

OK. I have been playing with this some more today. Ran it a few times while trying to fix the filenames. The first thing I tried was fixing the filenames in my source files. Then I noticed that it seemed to have created some of the bad filenames on my destination so I deleted all of those. The last run it seemed to complete without error. I think at least some of the errors may have been due to trying to do the compare on the NTFS volume rather than the copy from the array. I tweaked the script a little with some copy/paste so I could get an email and a log package on both success and fail. I am running it again to test. I also set my logdir to my Dropbox (thanks for the plugin) so I could access it after I got the email. It is appending the log rather than creating a new one and that was a little confusing at first as I was trying to fix some things I had already fixed because they were coming up in a search of the log. Also, the log is still hanging around in /tmp after completion and it can get large. I deleted it from /tmp and the old logs in my logdir. Might need some more work to get it to quit appending and clean up the old log in /tmp. rsync_backup_to_external.sh.txt

What version of unRAID are you using? 5.0rc8a What is your unRAID locale set to? (issue "locale" from command line) That command gives a bunch of lines but they are all set to "en_US.UTF-8" What is the method/command you're using to mount your Offsite disk to /mnt/user/Backups/Offsite? It has been mounted for several days so I don't have that command line handy anymore but I took it from this wiki page: Mounting an external USB drive having an existing NTFS file system in READ/WRITE mode to transport files from/to unRaid server so it must have been something like: mkdir /mnt/user/Backup/offsite mount -t ntfs-3g -o umask=111,dmask=000 /dev/sdc1 /mnt/user/Backup/offsite Thanks for the new version. The previous one did indeed only do dry-run. I don't entirely understand the code but it looks like the log only gets packaged if rsync is successful. In any case I had to go find it in /tmp instead of $logdir/$logname. Anyway... After staying up way too late beating my head against the wall I have determined that there are only a few files affected by this problem (thanks to the log). There are plenty of other files (my wife has some "world" music in her iTunes) with "foreign" characters that are not affected by this problem. It seems the main thing the problem files all have in common is that they were all downloads and so were originally created on some other system. I have been trying to rename them from Windows but that doesn't seem to work very well. I even tried to retag one of the files in MediaMonkey and that didn't work either. Even though these filenames are displayed "correctly" (whatever that means in this context) in Windows, Windows does not seem to be able to tell unRAID what file it is talking about when it asks unRAID (or SAMBA) to manipulate the file. I am going to try renaming these few files from the unRAID (linux) command line in PuTTY, then I will try the new version of the script. Thanks