Cessquill

Could be wrong here, but you should be able to get the XML from your flash drive. go to \\<unraid name/IP>>\flash\config\plugins\speedtest There's a speedtest.xml file in there that might be what you need.

Read up a few posts

Fantastic! Well done, and thank you.

Yep

TBS Opensource picks up my card just fine, including correct name. Can't test it right now as the machine's running on the bench. When it's back in the rack I'll give it a go.

That worked. Somebody's Plexing at the moment, so I'll install later.

Will do, but I'm getting "Error Downloading Source Files" on the plugin at the moment. I'm running 6.4.0. Any ideas?

Have you tried the LibreElec builds? My TBS 6982 wasn't detected, but when I switched there, all was good again. Note - it shows up as a different name, but AFAIK works just fine.

Thanks for that @Jcloud - I've been reading some reports that seem to think you can take down your array if you run out of RAM doing this. I haven't gone down this route yet, so something to read up on tomorrow. Thank you.

Thank you

Thank you for posting this - it might be what I'm after. A couple of questions... - Can the drives be of different sizes? - Do you know if there's a way of deciding which drive a file/folder goes on (or does it just show up as one big drive)? I'm looking at adding a second cache, but would like the opportunity to split a download share and appdata share to separate locations (currently, when a download is unpacking it can hog the disk and mess with Plex transcoding). I could do this with Unassigned Devices, but this might be another option.

Thanks for your advice. This command gracefully stopped the sync at its current position. I waited for the first command to complete (the first share to transfer). For anybody else, this is not just when unBALANCE says "Command Finished" (or similar), but when all folders have been removed from the source drive. Wait for the next share to start, then run the command (can be quite a while if - like me - you were moving 2.5TB). Then delete the portion that has already transferred from this new share.

Thanks. I'll let it finish the first share and try killing it.

Hi - is there any way of pausing/cancelling? I've got three entries queued up in a scatter (freeing up a drive to reformat), and it's got 51h remaining. However, I've got a different replacement drive precleared waiting to add to the array that I'd like to get in if possible. Don't mind letting the first of three finish. Thought that clicking on the "-" icon next to each entry would remove.

I'm getting the same stream of errors on the layout page as mentioned previously.. (starts with Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 126 Warning: array_key_exists() expects parameter 2 to be array,...) I'm running 6.4.0_rc16b and have unassigned devices installed. Has a source been found for this issue? The data tab also contains errors (can list if required), and Chrome's console has the following errors... serverlayout:1932 Uncaught SyntaxError: Unexpected token < serverlayout:2416 Uncaught ReferenceError: StartUp is not defined at serverlayout:2416 I'm running the latest version of the plugin in from CA.

Thank you for that. I've got a parity rebuild running at the moment, so I'll look tomorrow. As a couple of other threads on here would tell you, my dockers have crashed and burned by the cache filling up. Would there be any issues, do you think, in using this and the overnight mover? Files could potentially stay out of the array for a while if nothing else is happening.

Ooh! That's handy - I'll go look for it. Ever since using user scripts, dockers have been much easier to manage. Thank you

Thanks. I'll let the parity-sync and preclear die down then turn the cache off and on again.

An option/utility to automatically start the Mover if the cache disk runs low on space would be handy. Edit: Presumably there's a hook in there to run something, since a notification can be raised.

Cool - thanks. Makes sense now I think about it. The mover had freed up some space, so for now I stopped and started the docker service and all appears fine again (dockers started and errors gone). I'm connected remotely at the moment, but if I need to rebuild I'll do it later when I'm back in the house. This is where my knowledge ends - is a docker image kind of mounted as a BTRFS file system then? Any idea why I'm not getting cache disk notifications since switching it to XFS?

Hi - this morning I've noticed that I'm getting lots of entries for... Dec 20 09:10:19 unRAID1 kernel: BTRFS error (device loop2): bad tree block start 0 431685632 ...together with some dockers stopped and giving a server execution error when trying to start. Here's what's currently happening on my server... I'm putting a new parity drive in, and it's slowed right down The old parity is currently pre-clearing to be used as a data drive I have a couple of unmounted drives in there that are only in the rack to aid airflow I do not have a BTRFS drive - my cache WAS up until about a week or so ago, when with the help of you guys I ended up reformatting to XFS The mover is currently running As a side issue (that may be related?), I no longer get notifications if my cache drive fills up. This has been since I reformatted to XFS. Planning on looking into that today, but this has taken precedence. Diags file attached. Any help appreciated - parity sync is currently due to finish in 18.5 days...! unraid1-diagnostics-20171220-0913.zip

Hi - I frequently go through set it and forget phases with unRaid (and I suspect a lot of users might rarely touch the UI in everyday use). Therefore, I've come a cropper several times with my cache drive gradually filling because the mover hasn't been able to move some files and I've not realised. A couple of use cases... Ripped a new series of a TV show that's on a disk which has now filled Ripped the Blu-Ray of a movie where the DVD version is on a full disk It would be handy to receive a notification if a file could not be moved to the array due to space issues. Either that, or automatically move folders without breaking the share settings to free up the necessary space (although I'm overstretching things there). Other Nice to Haves... Also, after spending most of the weekend housekeeping, the following would be handy... Mover progress and/or expected time remaining. Appreciate this might be a can of worms, but the mover was working, and I had no easy way to tell how far through it was Mover stop/pause button. I was moving files onto one of my drives and had to make space on my cache so I ran mover. Unfortunately mover picked the same drive to write to and everything ground to a halt. In retrospect, I could have used mc / Krusader to replicate mover manually, but the ability to cleanly stop a running mover process would be handy

Thanks for your time - I'd done quite a bit of reading and had a few ideas, but ultimately yes - it's much easier to wipe and start again. I'm guessing something to do with metadata and the fact that a lot of small files had been copied on there (but that's about where my knowledge drops off). Stopped array, changed file system, started array, formatted cache, restored appdata and copied other files back onto the drive. All started back straight away - even the docker.img file was fine once there was space. When I get some time over the weekend, I'll clear the img file and reinstall, but it's sorted for now. Thanks!

The copying/deleting was all from within mc - I'm just using Windows to putty onto it. Just rebooted, trying to copy, delete & use the docker settings to clear img file... (thanks for your time with this) unraid1-diagnostics-20171207-2318.zip

I can recreate the docker img file (well, I can when it'll let me). Unfortunately I can't copy to or delete from the cache drive, and I think that's also preventing me from ditching the img file. Also, if I go to the docker tab, I get Warning: stream_socket_client(): unable to connect to unix:///var/run/docker.sock (Connection refused) in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 672 Couldn't create socket: [111] Connection refused Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 852 Warning: stream_socket_client(): unable to connect to unix:///var/run/docker.sock (Connection refused) in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 672 Couldn't create socket: [111] Connection refused Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 852 (which I assume is related)