toby9999

Ahh that did the trick (I didn't know about the Help button ... pretty cool feature!) ... anyway, here's the log... 2015-12-07 10:51:13.075+0000: 8142: info : libvirt version: 1.2.18 2015-12-07 10:51:13.075+0000: 8142: error : virUSBDeviceFindByVendor:242 : internal error: Did not find USB device 45e:cb 2015-12-07 10:51:13.098+0000: 8142: warning : virHostdevReAttachUSBDevices:1455 : Unable to find device 001.008 in list of active USB devices 2015-12-07 10:51:13.098+0000: 8142: warning : virHostdevReAttachUSBDevices:1455 : Unable to find device 000.000 in list of active USB devices 2015-12-07 10:51:13.098+0000: 8142: warning : virHostdevReAttachUSBDevices:1455 : Unable to find device 000.000 in list of active USB devices 2015-12-07 10:51:13.098+0000: 8142: warning : virHostdevReAttachUSBDevices:1455 : Unable to find device 000.000 in list of active USB devices 2015-12-07 10:51:13.098+0000: 8142: warning : virHostdevReAttachUSBDevices:1455 : Unable to find device 000.000 in list of active USB devices 2015-12-07 10:51:13.108+0000: 8142: error : qemuAutostartDomain:302 : Failed to autostart VM 'Win10VM': internal error: Did not find USB device 45e:cb 2015-12-07 10:52:06.469+0000: 8125: warning : qemuDomainObjTaint:2065 : Domain id=2 name='Win10VM' uuid=0ea65933-a1b4-fb12-0206-1e29ea25f5cf is tainted: high-privileges 2015-12-07 10:52:06.469+0000: 8125: warning : qemuDomainObjTaint:2065 : Domain id=2 name='Win10VM' uuid=0ea65933-a1b4-fb12-0206-1e29ea25f5cf is tainted: host-cpu Sure enough, looks like a USB issue ... it's just a bit surprising that when I do a manual start of the VM, it starts ok (and all the USB devices work fine). I'm not too concerned, I have my mouse/kbd/phone charger all passing through the usb hub that's built in to my monitor, and it's often a bit flaky. I'll eventually get around to bypassing the monitor's usb hub and going direct to the server's motherboard (or using an external USB hub). Thanks!

Ok, I checked the reliability history in Windows, but everything looks ok. Any other ideas? What's the config file/setting that controls the autostart?

Really strange ... I can't pinpoint exactly when this problem started happening, but I have a Win10 VM set to autostart, but it won't auto start (ie after a reboot of unraid). It manually starts with no problems at all. I've tried disabling autostart, then re-enabling it. I've also tried upgrading from 6.1.3 to 6.1.6, but both OS versions have the same issue. Is there a config file I can check to see if the autostart setting is in fact set? The VM's xml file doesn't have an autostart option in there that I can see, so I'm guessing it's in a different config file. Anyway, any help is greatly appreciated, thanks!

No, not at the moment. I put the idea of creating a plugin to run this on my list of 'nice-to-try-creating' items a few weeks ago. However demands on my time have have meant I have not got any further, but it is still something I would like to try my hand at if time becomes available. It actually seems fairly easy to use via CLI, but a GUI would probably open it up to a lot more non-techie users. I'm looking around for an easy solution to protect my unraid data from data degradation. I have a full copy of every unraid hard drive on another hard drive, but there's no integrity checking, hence my interest in this solution or something else (snapraid?).

This utility looks really useful. Is there any GUI front-end (dynamix, docker??) for this?

"Gaz" is an aussie thing

Thanks for all the great feedback guys ... I'm off to research some more!

I think this setup is going to be my next purchase Small, cool, lots of storage, low energy, quiet ... what's not to like? A couple of questions... 1) How's the performance if I wanted to run say (a) the usual containers for Plex, Sab, CP, Sonarr, etc + (b) 1 or 2 Windows VMs under Xen? Would the 8-core Atom be capable of handling all that (in addition to unraid of course)? Does it support the required vt-d for xen? 2) If I were to populate all 8 drive bays with data drives, would there be enough room to add my 2xcache ssds (2.5" drives) + 1 x parity drive (8TB seagate 3.5") into one of the internal bays (I understand they are 2.5" bays, but a slight case mod should allow me to squeeze in the 3.5")? Thanks!

I just wanted to say a big thanks for this ... I'm running 14b and I've installed all the unraid 6 plugins. Very nice interface/dashboard and very useful info that's displayed.

Is this only for unraid running as a vmware vm? Do I need this plugin for unraid 6.x running on real hardware and using say xen to run other vms?

You can not install the v5 versions of the plugins, these are not compatible with v6. See the OP for the v6 versions. Ahh ok, I had no idea they were v5.

I'm on the latest beta (b14), which includes the dynamix gui. However when I try to install one of the plugins from https://github.com/bergware/dynamix, I get an error saying the dynamix webgui plugin isn't installed... /usr/local/sbin/plugin install /boot/config/plugins-error/dynamix.active.streams-2.1.1-noarch-bergware.plg 2>&1 plugin: installing: /boot/config/plugins-error/dynamix.active.streams-2.1.1-noarch-bergware.plg plugin: creating: /tmp/plugin-startup - from INLINE content plugin: running: /tmp/plugin-startup missing Dynamix webGui plugin !!! plugin: run failed: /bin/bash retval: 1

Because post-read is verifying what was written is all zeros. Pre-read is not verifying, it is just sending the contents read to /dev/null as existing contents could be anything Is that a 3TB drive? Thanks - make sense. Yes that one is a Hitachi 3TB green drive running off the SATA port on the motherboard (Supermicro X8SIL-F).

Just got these final results from a preclear (as shown in MyMain)... Preclear Successful ... Total time 38:34:45 ... Pre-Read time 9:46:21 (85 MB/s) ... Zeroing time 9:53:09 (84 MB/s) ... Post-Read time 18:54:05 (44 MB/s) Why is the post-read slower than the pre-read? Just curious... thanks.

@Joe L. I was running 1.11 :-( Have downloaded 1.12beta now and will see how I go. I ran pre... -t /dev/sdc (another drive already precleared by 1.11) and it didn't find a valid signature (see attached image) - I'll obviously have to redo every drive, no problem. As the 6 drives all reported absolutely no problems (1 pass), I might use the -n switch to skip the pre/post reads on those drives. I'll contact BJP999 re: the drivedb issue, thanks. Many things are in flux at the moment with the new versions of unraid, support for 3TB drives etc. --- On another note ... I know the suggested method for running multiple preclears simultaneously is via screen, but I was just wondering if it wouldn't be easier to have that capability included in UnMenu? Or would it be too dangerous if the interface was too easy? Hmmm.

Hi I precleared 6 drives (sda, sdc-sdg). Then I installed latest unmenu/screen to do the rest (another 16 drives). In MyMenu, sda didn't show as a precleared drive (it's icon = "+") and it's number of writes showed quite a different value to the other 5 precleared drives. I then used screen to kick off preclearing sda again as well as the remaining 16 drives (sdh-sdw). I refreshed the MyMenu page and it showed every drive EXCEPT SDA as a precleared drive, and the usage column showed the progress of the preclear. I then noticed the last line of the syslog saying ... Tower unmenu[18653]: Precleared disk sda not found in drivedb[] (Drive related) 1) how do I fix this problem? is there a way to manually add sda to the drivedb? 2) since sda has started the preclear again (pre-read, step 1), is it safe to cancel the preclear and will it retain the precleared signature ready for when I add it to the unraid array? Thx! Cheers Toby