johnsanc

What are the key factors into how fast a parity sync will go with one of these drives? My parity sync is currently very steady at 42 MB/s at about 1TB position now. Interestingly this is almost identical to danioj's transfer speed test. My setup is in my signature. And my drives are: 1x ST4000DM000-1F2168 1x WDC_WD40EFRX-68WT0N0 1x WDC_WD20EZRX-00DC0B0 6x WDC_WD20EARS-00MVWB0

Wow that was fast! Thanks! I will be moving this into the parity slot today and converting my old 4TB drive into a data drive.

Would someone mind taking a look at my preclear reports for this drive and give their thoughts? preclear_start_Z8402Y2D_2015-05-02.txt preclear_finish_Z8402Y2D_2015-05-02.txt preclear_rpt_Z8402Y2D_2015-05-02.txt

I'm currently preclearing one of these now with the official preclear and its 82% into the postread and I'm at 69hrs 51mins.

Good ole supply and demand. http://camelcamelcamel.com/Archive-3-5-Internal-Hard-Drive/product/B00QX0ZGO6

I'm not sure if it matters much, but I think the test should have varying filesizes instead of everything being 215k. If anything its just a truer representation of a real world scenario.

The exact size or number of files for the test doesn't really matter to me. I was just providing my own worst case scenario on my own array. Interestingly these files probably are scattered on one of my disks because I initially downloaded them via a torrent, so their initial creation was not sequential. However if you need a bunch of semi random small files just download a few of these packs and copy it a few times: http://www.progettosnaps.net/snapshots/

Fantastic results so far. I am considering buying a few of these, but it would be nice to see someone run another test with "small" files. I would consider the previous 2 tests as "large" and "medium". For example I have some arcade artwork that spans 170,000 files in about 35GB. If these drives can handle something like that then I think we have ourselves a winner.

For some reason all of my shares only show 12 files in the web gui. I know the other files are there since I can keep scrolling and click in the whitespace and I can download whatever file is there. I can even see the URL at the bottom of the browser change as I mouse over each file. I tried a few different browsers and shares but I still always can only see 12 files. Anyone else have this issue or know how to fix it?

I noticed earlier you mentioned that a way to do backups was on your to-do list. Have you given this any extra thought? I was thinking of maybe creating incremental rolling backups of my images with rdiff-backup, but it doesn't look like there is a readily available unraid plugin for it. WeeboTech's rsync_linked_backup script may also work, but it doesn't look like it includes backup expiration so I would have to manually remove old backups. Just curious how you would tackle automatic backups of entire qcow2 images.

Yes I did have it set to whatever the default balanced power profile is in windows 8.1. I think this includes hibernate after 20 mins. For now I configured so it doesn't hibernate/sleep and that seems to have worked until the plugin is updated (if this is on the roadmap)

Good points. Frankly I am by no means an rsync expert so I hope someone else can chime in. I just modified a script from someone else on the 5.x support forum so it works with docker. I didn't tinker with the arguments.

Nevermind, I think I figured it out. For anyone who is interested I used this script and set it to run daily in my Go file. You will need to modify your directories accordingly. I have my appdata on a disk mounted with SNAP outside of the array at /mnt/disk/appdisk/appdata/. My docker img file is under /mnt/disk/appdisk/docker/ Also, rsync does not like Plex and will give you a ton of "failed to set times" errors if you backup to a user share. However, it works fine if you backup directly to a disk share, which is why the script below references disk1 instead of my Backup user share. Script: #!/bin/bash #Stop Docker Apps docker stop CouchPotato docker stop CrashPlan docker stop Deluge docker stop MariaDB docker stop NzbDrone docker stop NZBGet docker stop PlexMediaServer docker stop Syncthing #Backup Docker App data via rsync date >/var/log/docker_app_backup.log date >/var/log/docker_img_backup.log /usr/bin/rsync -avrtH --delete /mnt/disk/appdisk/appdata/ /mnt/disk1/Backup/appdata >>/var/log/docker_app_backup.log /usr/bin/rsync -avrtH --delete /mnt/disk/appdisk/docker/ /mnt/disk1/Backup/docker >>/var/log/docker_img_backup.log #Start Docker Apps docker start CouchPotato docker start CrashPlan docker start Deluge docker start MariaDB docker start NzbDrone docker start NZBGet docker start PlexMediaServer docker start Syncthing Go file: # Set up daily Docker App backup cp /boot/custom/backup.sh /etc/cron.daily This was pretty simple, but I hope someone else finds this useful.

Any chance of building in support to wakeup the domain with "dompmwakeup" ? My Windows 8.1 VM likes to go into "pmsuspended" state after awhile and the only way to wake it up is by command line. Also, this isn't handled very well on the frontend yet. the GUI shows only 2 options - Start and View XML. Start doesn't work and throws a debug error.

I am also looking to do this. Any help from the scripting gurus is greatly appreciated!

Thanks for the clarification. That was indeed the problem. I didn't even realize it until I compared what the XML looked like by "view xml" feature compared to "edit xml" when the domain was not running. I added the cdrom back in as the first boot device and just reinstalled windows 8.1 since it didn't detect any partitions or anything. So far so good... I swear I had Windows installed and running properly though prior to attempting my GPU passthrough... so that doesn't really explain why I was getting the boot device error. I will be careful to make sure I gracefully shut everything down from now on. Maybe I will test forcing the domain to stop after I back everything up to see if I can recreate the issue. The good news is that I now have my GTX970 properly passed through with audio. Windows Media Center and Kodi are smooth as silk.

I still haven't fixed this, but here is what I tried: - Reverted my syslinux.cfg and go scripts - Rebooted - Created a new vanilla test VM with VM Manager and chose to create a new disk - Started VNC - Success. This worked, however I tried forcing the domain to shutdown with the eject button in VM Manager. This shut down the domain, but now it will not start back up and I get the same boot device error. Why does forcing the domain to shutdown cause this to happen? This persists through a reboot. It looks like forcing the domain to shutdown possibly corrupted the disk image. Can anyone else confirm? Is there a better way to shutdown when the standard graceful shutdown in VM Manager does not work?

I am trying to load windows 8.1 through KVM. I originally set it up with the VM Manager plugin and everything loaded up fine through VNC. I installed a few windows updates and decided to attempt GPU passthrough. I feel like I am close because I can get my screen to display when I start the VM, but I get an error: Booting from Hard Disk... Boot failed: not a bootable disk No bootable device. So far I have done the following: Ensured VT-d is enabled in the BIOS Changed my primary display to the integrated GPU (Xeon E3 1276 v3) Updated my go script to include: /usr/local/sbin/vfio-bind 0000:01:00.0 0000:01:00.1 Updated syslinux.cfg to include: append intel_iommu=on vfio_iommu_type1.allow_unsafe_interrupts=1 pcie_acs_override=downstream initrd=/bzroot Updated my XML file for gpu passthrough instead of vnc Here is my xml: <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>windows81pro</name> <uuid>d2f62486-79d7-1d78-145a-70e63187f893</uuid> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <vcpu placement='static'>4</vcpu> <os> <type arch='x86_64' machine='pc-q35-2.1'>hvm</type> <boot dev='hd'/> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'> </cpu> <clock offset='localtime'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='qcow2'/> <source file='/mnt/disk/appdisk/vm/windows81pro/windows81pro.qcow2'/> <target dev='hda' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/disk/appdisk/vm/windows81pro/os_image/Win81.iso'/> <target dev='hdc' bus='sata'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='dmi-to-pci-bridge'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/> </controller> <controller type='pci' index='2' model='pci-bridge'> <address type='pci' domain='0x0000' bus='0x01' slot='0x01' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:76:56:bd'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/> </interface> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <input type='tablet' bus='usb'/> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x0'/> </memballoon> </devices> <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=1,chassis=1,id=root.1'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=01:00.1,bus=pcie.0'/> </qemu:commandline> </domain> What am I missing? Its late and I'm sure its something easy I'm just not seeing.

Yeah I was looking at those. NewEgg had a Crucial 16GB kit (8x2) 1600 CL11 1.35V for like $30 less than that, but its out of stock now and it looks like the prices at other stores also jumped overnight. Interestingly it looks like the SuperMicro board supports 1.35V but it will run at 1.5V anyways, so I suppose it doesn't really matter. http://www.supermicro.com/products/motherboard/xeon/c220/x10sat.cfm -> Tested Memory List "Please note: The qualified 1.35V DDR3 will operate at 1.5V" Thanks again for all your help!

As far as ECC RAM goes, are there particular modules you would recommend for the SuperMicro X10-SAT-O board? I see that it supports 1.5V and 1.35V. I don't have much experience with ECC RAM so I'm not sure if some manufacturers/brands have a better track record than others.

Thanks for the advice! As much as I would love to go for option #2, I am leaning toward option #1. The Xeon E-1271 or E-1276 v3 look like a great fit for my purposes. 3.6Ghz with 4.0Ghz TurboBoost should be enough horsepower for applications that can't take advantage of multiple cores. I was looking into the E-128x series but I cant seem to find any for sale from the normal places I would go to, and they don't seem to be worth double the price of the E-127x. I was also considering a Core i7 4790K since it supports VT-d and would be great for my single core applications... but since my primary use case is more server oriented, I think you sold me on ECC support.

My server is long overdue for an overhaul. I recently had a gfx card die on my HTPC, and with all the new virtualization features in unraid 6, I think its time to build a multipurpose server. I need some advice around the core components, specifically the Motherboard, CPU, and RAM. What should I buy? I will be using the server primarily for: Media streaming to up to 3 HTPCs Running docker apps like NZBGet, NZBDrone, CrashPlan, CouchPotato, Deluge, MariaDB (for Kodi), SyncThing Fairly heavy par checking, unpacking, and compressing files Providing Crashplan backups for my family, 4-5 computers Acting as an HTPC for at least 1 room, preferably 2 if I can pass through the appropriate hardware to 2 VMs Emulating older console gaming systems, which tends to not be optimized to use multiple cores Gaming, but I am not a hardcore gamer or anything Budget is flexible, but I don't want to spend thousands if I can help it. After reading through the forums I can't help but think: "WWGCD: What would garycase do?" Any help is greatly appreciated!

SOLVED. Turns out I had the webgui open in a browser (Chrome) on another computer on the network. Once I closed that browser, all was well. Anyone know why this happened? This seems like it might be some kind of bug...

After some searching it looks like the excessive logging (loading and unloading) happens when the array is not started and whenever the webGUI has actions. Here is the output from ps -ef > /boot/ps_output.txt UID PID PPID C STIME TTY TIME CMD root 1 0 0 23:21 ? 00:00:06 init root 2 0 0 23:21 ? 00:00:00 [kthreadd] root 3 2 0 23:21 ? 00:00:00 [ksoftirqd/0] root 4 2 0 23:21 ? 00:00:00 [kworker/0:0] root 6 2 0 23:21 ? 00:00:00 [migration/0] root 7 2 0 23:21 ? 00:00:00 [migration/1] root 9 2 0 23:21 ? 00:00:00 [ksoftirqd/1] root 10 2 0 23:21 ? 00:00:00 [kworker/0:1] root 11 2 0 23:21 ? 00:00:00 [khelper] root 12 2 0 23:21 ? 00:00:00 [kworker/u:1] root 158 2 0 23:21 ? 00:00:00 [sync_supers] root 160 2 0 23:21 ? 00:00:00 [bdi-default] root 162 2 0 23:21 ? 00:00:00 [kblockd] root 275 2 0 23:21 ? 00:00:00 [ata_sff] root 285 2 0 23:21 ? 00:00:00 [khubd] root 308 2 0 23:27 ? 00:00:00 [kworker/0:13] root 394 2 0 23:21 ? 00:00:00 [rpciod] root 414 2 0 23:21 ? 00:00:00 [kswapd0] root 475 2 0 23:21 ? 00:00:00 [fsnotify_mark] root 495 2 0 23:21 ? 00:00:00 [nfsiod] root 498 2 0 23:21 ? 00:00:00 [cifsiod] root 504 2 0 23:21 ? 00:00:00 [crypto] root 570 2 0 23:21 ? 00:00:00 [kworker/1:1] root 658 2 0 23:21 ? 00:00:00 [deferwq] root 659 2 0 23:21 ? 00:00:00 [kworker/1:2] root 686 1 0 23:21 ? 00:00:00 /sbin/udevd --daemon root 846 2 0 23:21 ? 00:00:00 [scsi_eh_0] root 857 2 0 23:21 ? 00:00:00 [scsi_eh_1] root 858 2 0 23:21 ? 00:00:00 [usb-storage] root 880 2 0 23:21 ? 00:00:00 [scsi_eh_2] root 881 2 0 23:21 ? 00:00:00 [scsi_eh_3] root 882 2 0 23:21 ? 00:00:00 [scsi_eh_4] root 883 2 0 23:21 ? 00:00:00 [scsi_eh_5] root 884 2 0 23:21 ? 00:00:00 [scsi_eh_6] root 885 2 0 23:21 ? 00:00:00 [scsi_eh_7] root 890 2 0 23:21 ? 00:00:00 [kworker/u:7] root 943 2 0 23:33 ? 00:00:00 [kworker/0:2] root 945 2 0 23:21 ? 00:00:00 [scsi_wq_0] root 961 686 0 23:21 ? 00:00:00 /sbin/udevd --daemon root 962 686 0 23:21 ? 00:00:00 /sbin/udevd --daemon root 1060 1 0 23:21 ? 00:00:01 /usr/sbin/syslogd -m0 root 1064 1 0 23:21 ? 00:00:00 /usr/sbin/klogd -c 3 -x bin 1106 1 0 23:21 ? 00:00:00 /sbin/rpc.portmap root 1110 1 0 23:21 ? 00:00:00 /sbin/rpc.statd root 1120 1 0 23:21 ? 00:00:00 /usr/sbin/inetd root 1127 1 0 23:21 ? 00:00:00 /usr/sbin/ntpd -g -p /var/run/ntpd.pid root 1134 1 0 23:21 ? 00:00:00 /usr/sbin/acpid 81 1144 1 0 23:21 ? 00:00:00 /usr/bin/dbus-daemon --system root 1149 1 0 23:21 ? 00:00:00 /usr/sbin/crond -l notice daemon 1151 1 0 23:21 ? 00:00:00 /usr/sbin/atd -b 15 -l 1 root 7256 1 3 23:23 ? 00:00:24 /usr/local/sbin/emhttp root 7270 2 0 23:23 ? 00:00:00 [kworker/0:3] root 7281 1 0 23:23 ? 00:00:00 /usr/sbin/sshd root 7284 1 0 23:23 tty1 00:00:00 /sbin/agetty 38400 tty1 linux root 7285 1 0 23:23 tty2 00:00:00 /sbin/agetty 38400 tty2 linux root 7286 1 0 23:23 tty3 00:00:00 /sbin/agetty 38400 tty3 linux root 7287 1 0 23:23 tty4 00:00:00 /sbin/agetty 38400 tty4 linux root 7288 1 0 23:23 tty5 00:00:00 /sbin/agetty 38400 tty5 linux root 7289 1 0 23:23 tty6 00:00:00 /sbin/agetty 38400 tty6 linux root 7290 686 0 23:23 ? 00:00:00 /sbin/udevd --daemon root 7311 1 0 23:23 ? 00:00:00 /usr/sbin/nmbd -D root 7313 1 0 23:23 ? 00:00:00 /usr/sbin/smbd -D root 7318 7313 0 23:23 ? 00:00:00 /usr/sbin/smbd -D root 7328 2 0 23:23 ? 00:00:00 [kworker/0:4] root 7403 2 0 23:23 ? 00:00:00 [kworker/0:6] root 7441 2 0 23:23 ? 00:00:00 [kworker/0:7] root 7479 2 0 23:23 ? 00:00:00 [kworker/0:8] root 7517 2 0 23:23 ? 00:00:00 [kworker/0:9] root 7555 2 0 23:23 ? 00:00:00 [kworker/0:10] root 7675 7826 0 23:34 ? 00:00:00 sleep 60 root 7826 1 0 23:22 ? 00:00:00 /bin/bash /usr/bin/unraid_notify run_service root 8082 2 0 23:23 ? 00:00:00 [kworker/1:4] root 8126 2 0 23:23 ? 00:00:00 [kworker/1:5] root 8181 2 0 23:23 ? 00:00:00 [kworker/1:6] root 8284 2 0 23:23 ? 00:00:00 [kworker/1:7] root 8436 2 0 23:23 ? 00:00:00 [kworker/0:11] root 9234 2 0 23:23 ? 00:00:00 [kworker/0:12] root 9642 2 0 23:23 ? 00:00:00 [kworker/1:9] root 9902 2 0 23:23 ? 00:00:00 [kworker/1:10] root 11029 2 0 23:35 ? 00:00:00 [md] root 11030 2 0 23:35 ? 00:00:00 [mdrecoveryd] root 11032 2 0 23:35 ? 00:00:00 [spinupd] root 11033 2 0 23:35 ? 00:00:00 [spinupd] root 11034 2 0 23:35 ? 00:00:00 [spinupd] root 11035 2 0 23:35 ? 00:00:00 [spinupd] root 11036 2 0 23:35 ? 00:00:00 [spinupd] root 11037 2 0 23:35 ? 00:00:00 [spinupd] root 11038 2 0 23:35 ? 00:00:00 [spinupd] root 11039 2 0 23:35 ? 00:00:00 [spinupd] root 11040 2 0 23:35 ? 00:00:00 [spinupd] root 11041 2 0 23:35 ? 00:00:00 [spinupd] root 11055 7256 0 23:35 ? 00:00:00 sh -c cd /usr/local/emhttp; /usr/bin/php -d magic_quotes_gpc=Off plugins/simpleFeatures/include/SystemTemp.php 'item=CPU&unit=C' root 11056 11055 0 23:35 ? 00:00:00 /usr/bin/php -d magic_quotes_gpc=Off plugins/simpleFeatures/include/SystemTemp.php item=CPU&unit=C root 11060 17616 0 23:35 pts/0 00:00:00 ps -ef root 12014 2 0 23:24 ? 00:00:00 [kworker/1:11] root 14240 2 0 23:30 ? 00:00:00 [kworker/1:3] root 15097 2 0 23:24 ? 00:00:00 [kworker/1:12] root 17020 7281 0 23:30 ? 00:00:00 sshd: root@pts/0 root 17616 17020 0 23:30 pts/0 00:00:00 -bash nobody 28171 7313 0 23:32 ? 00:00:00 /usr/sbin/smbd -D

I got tower:8080 and 192.168.2.100:8080 to resolve correctly, but I am still having issues with the main webGUI. I find it really odd that it will sometimes load but with no images. It just sits there an churns.