WannabeMKII

Can anyone help, or should I have posted this on the dockers forum?

My system has been up and running for a week or so now and very well, thanks to help from here! But, I've a few more questions about dockers and unassigned devices and the best way to set it up. My current config is 4x 4TB in the array, 1x 500GB cache and 1x 60GB SSD. I was thinking of using the SSD for dockers only using unassigned devices. Does that make sense to do, as I'm only going to run a few small dockers (Hydra initially, then potentially Sonarr, PlexPy, CP & PlexConnect). If I do go down that route, do I set both the 'Default storage location' and 'Default appdata storage location' to the SSD? And would 10GB be the recommended vDisk size taking into account the size of the SSD and the plans to add a couple more dockers?

Just to confirm, the 4TB Wd Red also completed fine after the update along with the SSD. So whatever you did in the update seemed fix it from my perspective, much appreciated!

SSD ran through without any problems, so now running on the 4TB drive. Fingers crossed

No problem. I'm running it on the SSD now, as that one is much quicker being only 60GB. Will let you know how it goes... If it does fail, which logs, both the preclear and diagnostics?

No problem. I have the file, but how can I send them to you directly rather than posting here? Upload it on a sharing service and send me the link via personal message. Enviado de meu SM-G930F usando Tapatalk Whilst we've been going through this with the SSD, a 4TB WD Red failed overnight with zeroing; preclear_disk_sde_15981: Command: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --notify 2 --frequency 1 --cycles 1 --skip-preread --no-prompt /dev/sde preclear_disk_sde_15981: Zeroing: dd if=/dev/zero of=/dev/sde bs=2097152 seek=1 conv=fdatasync,noerror oflag=direct preclear_disk_sde_15981: Zeroing: dd pid [18662] preclear_disk_sdf_19135: Command: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --notify 2 --frequency 3 --cycles 1 --no-prompt /dev/sdf preclear_disk_sdf_19135: Pre-Read: dd if=/dev/sdf of=/dev/null bs=2097152 iflag=direct preclear_disk_sde_21092: Command: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --notify 2 --frequency 3 --cycles 1 --skip-preread --no-prompt /dev/sde preclear_disk_sde_21092: Zeroing: dd if=/dev/zero of=/dev/sde bs=2097152 seek=1 conv=fdatasync,noerror oflag=direct preclear_disk_sde_21092: Zeroing: dd pid [23805] preclear_disk_sdf_19135: Pre-Read: 0 preclear_disk_sdf_19135: Zeroing: dd if=/dev/zero of=/dev/sdf bs=2097152 seek=1 conv=fdatasync,noerror oflag=direct preclear_disk_sdf_19135: Zeroing: dd pid [4255] preclear_disk_sdf_19135: Zeroing: dd command failed, exit code: 1 preclear_disk_sdf_22711: Command: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --notify 2 --frequency 3 --cycles 3 --skip-preread --no-prompt /dev/sdf preclear_disk_sdf_22711: Zeroing: dd if=/dev/zero of=/dev/sdf bs=2097152 seek=1 conv=fdatasync,noerror oflag=direct preclear_disk_sdf_22711: Zeroing: dd pid [24031] preclear_disk_sdf_22711: Zeroing: dd command failed, exit code: 1 preclear_disk_sdf_21104: Command: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --erase --notify 2 --frequency 3 --cycles 1 --no-prompt /dev/sdf preclear_disk_sdf_21104: Erasing: openssl enc -aes-256-ctr -pass pass:"xSMeOPXJNj2fhJ7ov5JcwfK7zhsyFAbxveNC0kWeX4DZSIo33l3V0JPzPKNB2+OlYIBDVZUy13dLA4XJnFbQ7sssv3l9px6bkS0dZMbysScHK+otT2qRv1SZ0pTQtmIB2q2MfxrMRVSjjHCoBtjS3fWaTUZxVbJnB9wZXwXQvvc=" -nosalt < /dev/zero 2>/dev/null | dd of=/dev/sdf bs=2097152 seek=1 iflag=fullblock conv=fdatasync,noerror oflag=direct preclear_disk_sdf_21104: Erasing: dd pid [22392] preclear_disk_sdf_21104: Erasing: dd command failed, exit code: 1 preclear_disk_sdf_1700: Command: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --verify --notify 2 --frequency 3 --cycles 1 --no-prompt /dev/sdf preclear_disk_sdf_4507: Command: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --notify 2 --frequency 3 --cycles 1 --skip-preread --no-prompt /dev/sdf preclear_disk_sdf_4507: Zeroing: dd if=/dev/zero of=/dev/sdf bs=2097152 seek=1 conv=fdatasync,noerror oflag=direct preclear_disk_sdf_4507: Zeroing: dd pid [5802] preclear_disk_sdf_4507: Zeroing: dd command failed, exit code: 1 preclear_disk_sdf_365: Command: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --notify 2 --frequency 3 --cycles 1 --skip-preread --no-prompt /dev/sdf preclear_disk_sdf_365: Zeroing: dd if=/dev/zero of=/dev/sdf bs=2097152 seek=1 conv=fdatasync,noerror oflag=direct preclear_disk_sdf_365: Zeroing: dd pid [1751] preclear_disk_sdf_365: Zeroing: dd command failed, exit code: 1 preclear_disk_sdf_30081: Command: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --erase --notify 2 --frequency 3 --cycles 1 --no-prompt /dev/sdf preclear_disk_sdf_30081: Erasing: openssl enc -aes-256-ctr -pass pass:"/jp3HewFPslai43wWAcOMx6KgdK+CppjHZIqzJtsJKOJMZZx0mfCvyQ/zUexQhDE69rQqCS7LfC3iU5NRm6a/a/0sQtlNkcP+DnjyNfGXcMdNENcNBXMxmrM29nX8B4eiMNjBY3h4/2xTAC/MLHKBSd3BhZRSIY5A74wYHT9BCo=" -nosalt < /dev/zero 2>/dev/null | dd of=/dev/sdf bs=2097152 seek=1 iflag=fullblock conv=fdatasync,noerror oflag=direct preclear_disk_sdf_30081: Erasing: dd pid [31379] preclear_disk_sdf_30081: Erasing: dd command failed, exit code: 1 preclear_disk_sde_21092: Zeroing: dd command failed, exit code: 1 Also as requested, I've PM'd you with a link to the diagnostic's file. Thanks.

No problem. I have the file, but how can I send them to you directly rather than posting here?

Please send me the log: Go to /Tools/Preclear, enable Help in the menu bar, click Download on the help box and send it here. Enviado de meu SM-G930F usando Tapatalk As requested; preclear_disk_sde_15981: Command: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --notify 2 --frequency 1 --cycles 1 --skip-preread --no-prompt /dev/sde preclear_disk_sde_15981: Zeroing: dd if=/dev/zero of=/dev/sde bs=2097152 seek=1 conv=fdatasync,noerror oflag=direct preclear_disk_sde_15981: Zeroing: dd pid [18662] preclear_disk_sdf_19135: Command: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --notify 2 --frequency 3 --cycles 1 --no-prompt /dev/sdf preclear_disk_sdf_19135: Pre-Read: dd if=/dev/sdf of=/dev/null bs=2097152 iflag=direct preclear_disk_sde_21092: Command: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --notify 2 --frequency 3 --cycles 1 --skip-preread --no-prompt /dev/sde preclear_disk_sde_21092: Zeroing: dd if=/dev/zero of=/dev/sde bs=2097152 seek=1 conv=fdatasync,noerror oflag=direct preclear_disk_sde_21092: Zeroing: dd pid [23805] preclear_disk_sdf_19135: Pre-Read: 0 preclear_disk_sdf_19135: Zeroing: dd if=/dev/zero of=/dev/sdf bs=2097152 seek=1 conv=fdatasync,noerror oflag=direct preclear_disk_sdf_19135: Zeroing: dd pid [4255] preclear_disk_sdf_19135: Zeroing: dd command failed, exit code: 1 preclear_disk_sdf_22711: Command: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --notify 2 --frequency 3 --cycles 3 --skip-preread --no-prompt /dev/sdf preclear_disk_sdf_22711: Zeroing: dd if=/dev/zero of=/dev/sdf bs=2097152 seek=1 conv=fdatasync,noerror oflag=direct preclear_disk_sdf_22711: Zeroing: dd pid [24031] preclear_disk_sdf_22711: Zeroing: dd command failed, exit code: 1 preclear_disk_sdf_21104: Command: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --erase --notify 2 --frequency 3 --cycles 1 --no-prompt /dev/sdf preclear_disk_sdf_21104: Erasing: openssl enc -aes-256-ctr -pass pass:"xSMeOPXJNj2fhJ7ov5JcwfK7zhsyFAbxveNC0kWeX4DZSIo33l3V0JPzPKNB2+OlYIBDVZUy13dLA4XJnFbQ7sssv3l9px6bkS0dZMbysScHK+otT2qRv1SZ0pTQtmIB2q2MfxrMRVSjjHCoBtjS3fWaTUZxVbJnB9wZXwXQvvc=" -nosalt < /dev/zero 2>/dev/null | dd of=/dev/sdf bs=2097152 seek=1 iflag=fullblock conv=fdatasync,noerror oflag=direct preclear_disk_sdf_21104: Erasing: dd pid [22392] preclear_disk_sdf_21104: Erasing: dd command failed, exit code: 1 preclear_disk_sdf_1700: Command: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --verify --notify 2 --frequency 3 --cycles 1 --no-prompt /dev/sdf preclear_disk_sdf_4507: Command: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --notify 2 --frequency 3 --cycles 1 --skip-preread --no-prompt /dev/sdf preclear_disk_sdf_4507: Zeroing: dd if=/dev/zero of=/dev/sdf bs=2097152 seek=1 conv=fdatasync,noerror oflag=direct preclear_disk_sdf_4507: Zeroing: dd pid [5802] preclear_disk_sdf_4507: Zeroing: dd command failed, exit code: 1 preclear_disk_sdf_365: Command: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --notify 2 --frequency 3 --cycles 1 --skip-preread --no-prompt /dev/sdf preclear_disk_sdf_365: Zeroing: dd if=/dev/zero of=/dev/sdf bs=2097152 seek=1 conv=fdatasync,noerror oflag=direct preclear_disk_sdf_365: Zeroing: dd pid [1751] preclear_disk_sdf_365: Zeroing: dd command failed, exit code: 1 preclear_disk_sdf_30081: Command: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --erase --notify 2 --frequency 3 --cycles 1 --no-prompt /dev/sdf preclear_disk_sdf_30081: Erasing: openssl enc -aes-256-ctr -pass pass:"/jp3HewFPslai43wWAcOMx6KgdK+CppjHZIqzJtsJKOJMZZx0mfCvyQ/zUexQhDE69rQqCS7LfC3iU5NRm6a/a/0sQtlNkcP+DnjyNfGXcMdNENcNBXMxmrM29nX8B4eiMNjBY3h4/2xTAC/MLHKBSd3BhZRSIY5A74wYHT9BCo=" -nosalt < /dev/zero 2>/dev/null | dd of=/dev/sdf bs=2097152 seek=1 iflag=fullblock conv=fdatasync,noerror oflag=direct preclear_disk_sdf_30081: Erasing: dd pid [31379] preclear_disk_sdf_30081: Erasing: dd command failed, exit code: 1

I've just updated to 2016.12.23a and run it again and still getting an error zeroing the disk?

I've installed an 60GB Kingston SSD from an old machine today, but preclear is failing. It's failed on 'zeroing' and 'erasing the disk' and I've tried more than once. The SMART report is reporting everything as passed. Any ideas why this may be happening?

I don't appear to have that setting available? Not to worry, all in progressing nicely now anyway, I just need to be patient

I've seen that setting, but I'm thinking if I do install the 500GB drive for cache and I want to use the 50GB SSD for Dockers, I assume the SSD isn't set as cache, but as something else?

Not really, did you enable write cache on the bios? I easily got 100MB/s+ parity checks and 40/60MB/s writes when I used them with similar disks. Ah ha, write cache now enabled and currently transferring at a much more reasonable +-51 MB/sec, so pretty much twice as fast! Damn, I wish I posted yesterday, would've saved me quite a few hours! But much appreciated, thanks for the pointer! Now I'm wondering if I need a cache and to just us the SSD for dockers? If that's the case, how's it best to set up the SSD to only be used for dockers? Can it just be installed, not set as cache or part of the array and point the docker image file to the SSD? Is that correct?

So, I'm up and running! However, I wanted to check these speeds seem OK, as building the parity took 1 day, 16 hours, 24 minutes, 46 seconds. Average speed: 27.5 MB/sec. That's 2 4TB WD Red with the Parity drive also being a 4TB WD Red. Does that sound right for an N54L with 4GB RAM? I'm now transferring large mkv files directly to the array and Windows is reporting a transfer rate of 26.1 MB/sec. Again, is this reasonable? Finally, I've also checked some of the drives I've knocking around and I've one drive of 500GB that is 7,200 rpm, with all others being 5,400 rpm. I'm now thinking of using that drive for cache and keeping the 50GB SSD separate for dockers (whilst space permits)? Does that sound like a good plan? Thanks again for the help everyone, I'm learning and enjoying unraid with the plan for it to be 'set and forget' once I've got it right

The only thing I'm thinking about with regards to the BIOS is enabling all SATA ports and running it at full speed, as it's not enabled by default? There's an extra 'hidden' one if I remember rightly?

You would copy the files on the small one to the array, replace the drive, then copy them back. (Or use something like CA Backup / Restore plugin to do it for you) Perfect. I'm planning to start the build over the weekend, so will initially go for the 50GB SSD.

If I found the SSD too small in the long run, is there an easy method to upgrade / swap it out for a bigger one?

Thanks for the feedback. To be honest, from what I've read, I'm not sure I'm actually going to use a cache drive for data as it's not really going to benefit me and my usage. However, it sounds like it makes sense for Dockers and the plan is to potential / eventually run; [*]nzbget & nzbtomedia (and a few other extensions) [*]Couchpotato [*]Sonarr [*]Plexconnect [*]NZBHydra [*]PlexPY So I'm hoping they're run on the SSD? Also, what's the latest / recommended BIOS update for the N54L? I 'think' I got mine from AVForums about 2 years ago before running XPEnology, so not sure if that's still the correct one?

I'm changing from XPEnology to UNRAID and wanted to check on the 'best' setup for my scenario. I'm going to be using an N54L with 4GB RAM and 4x WD Red 4TB HDD's for storage with a one of them being a parity drive giving me 12TB. But, this is where I need assistance. I'm not sure on the correct config with the rest of the setup, as I have the following drives spare and I'm planning to run a couple of dockers to start with, with more in the future; 1x 500GB Seagate 2.5" 2x 500GB WD 2x 500GB WD 2.5" 1x Kingston 50GB SSD 2.5" The UNRAID machine will primarily be used as a backup device and to store and serve up media that'll feed my Plex Server, which is a Dell T110 Tower Server Intel Xeon E3-1220v2 3.1GHz with 8GB ECC RAM and a 120GB SSD. I was thinking 1x 500GB for cache and the 1x SSD for running the dockers and therefore using all my SATA connections? But open to suggestions / guidance, as I'm new to UNRAID and want to try and get it right first time. Thanks in advance!

That sounds perfect. I can then move across bit by bit rather than all in one go. Gives me more time to work things out, test bits etc. Looking at what I use, the only potential issues I still see are; 1. Crashplan PROe - Currently running on Windows (No unraid replacement - So I'll have to change my backup solution (looking at ACD, but doesn't appear to be anything to run a backup to ACD on unraid), unless there's something else... Regular Crashplan is just too slow) 2. Google Drive Sync / Backup - Running on XPEnology (I use Google App's, so this is my local backup - I've been advised of rsync, but this looks way to complicated for me. Hoping to find something more straightforward (the whole aim behind this potential move), so open to suggestions) 3. TimeMachine - Running on XPEnology (From what I've read, there's not a reliable unraid replacement) I do like XPEnology, but the fact that any reboot or update can cause it to stop working is my reason for moving away, just a shame I lose Google Drive Sync and TimeMachine as a result. My initial thoughts now are to just replace XPEnology with unraid if I can, as unraid shouldn't be as high risk, then eventually run everything from the Dell and retire the N54L if all goes well / to plan. From user experience, am I still potentially pursuing the correct solution, or am I expecting too much?

I also use Crashplan PROe rather than regular Crashplan, so wondered if there's a docker for it?

The opening line in the last message, about a strategy, struck a cord and made me think more about my approach. Which got me thinking... If I move my data away from the NAS, 'could' I replace XPEnology on the N54L with unraid? Copy the data back over to unraid, then in the long term, move unraid from the N54L to the Dell Server and keep all my settings, arrays etc intact? The reason I'm thinking this possible route, is rather than take everything offline and do everything in one go, slowly transition. For example, keep Plex on the server (for system power reasons) and move data to unraid, followed by program by program from the Dell and Windows to unraid, such as nzbget, CP, Sonarr etc. Then if happy, ready and comfortable, move unraid from the N54L to the Dell and install Plex. Is that a potential option? Can unraid move hardware with no issues? Thanks again for reading and helping!

Been a busy week, so now it's the weekend, doing a bit more research and how best to configure... In terms of drives, I have (god knows where they all came from ); 3x WD Red 4TB (Currently in NAS) 2x WD Red 2TB 1x 500GB Seagate 2.5" 2x 500GB WD 2x 500GB WD 2.5" 1x Samsung 120GB SSD 1x Kingston 50GB SSD I know I don't need to use all the drives, and to be honest I don't need that much storage so wasn't going to bother with the 500GB drives. The other issue I have, is the Dell server only has 4 SATA ports. But I'm guessing ideally, I'd need 7 SATA? 5 for the WD Red's and 2 for the SSD's? Is there a way to increase the number of SATA ports the Dell has? If so, or not, what would be the best config? Thanks again all! Edited as I can't count...

I've not heard of any of this before, so appreciate your comments. I don't / won't need the VM to do anything fancy, just run any any programs within a VM if I'm unable to run it in a docker directly within unraid. So I guess, do I need VT-d and will VT-x (if that's what I have) be sufficient? Another question, but not related to virtualisation, how do people choose the correct / best docker when there's multiple choice? For example, there's quite a few variations of Plex, Sonarr etc, so how do you guys choose which one to install and run? Assume it's a case of research and trying them?

You can use the Rclone docker I've heard lots about Rclone and on looking, doesn't look straight forward to use. Also, the only one I've seen is by 'tynor88' through 'Community Applications'. Is that the correct one?