archedraft
-
Posts
2,070 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by archedraft
-
-
I've tried both methods of USB hub pass-through and neither will work with my keyboard and mouse but weirdly it will with a portable hard drive.
Do you happen to have a different USB keyboard and mouse you could try? If the portable hard drive works then technically it is working, so the issue is most likely that keyboard and mouse. Does your keyboard/mouse manufacture have any additional software you can install? For example Logitech has their Setpoint software which I have found to be helpful with my devices.
-
Thanks for the info. I subscribe to the philosophy of it ain't broke don't fix it...to a degree. Existing drives for me will remain reiserfs while new will be XFS. Thanks again.
But what's the fun in that?? I've always preferred the, If it ain't broke then how can we make it better, approach. Much more interesting
-
Over the last few weeks my server has been getting random kernel warnings. I have been trying to figure out why they are happening all of the sudden and I think they have something to do with this plugin. After updating to the latest plugin I started running the initial build and export on both of my disks. This kernel warning happened right after I started that process. Does any of this log mean anything too you?
bts buffer is the branch trace store buffer, google indicates there was a patch last year to reduce the frequency of such logs & whether it happens or not is a function of memory fragmentation. I would think that seeing this is just a sign that this plugin is working your CPU hard. Any other problems noted or just that warn?
That is the only relevant info in the log.
-
Over the last few weeks my server has been getting random kernel warnings. I have been trying to figure out why they are happening all of the sudden and I think they have something to do with this plugin. After updating to the latest plugin I started running the initial build and export on both of my disks. This kernel warning happened right after I started that process. Does any of this log mean anything too you?
What format are the disks? Recently a warning was added that problems might be encountered with the plugin if Reiserfs is being used for the disks.
All disks are XFS
-
Over the last few weeks my server has been getting random kernel warnings. I have been trying to figure out why they are happening all of the sudden and I think they have something to do with this plugin. After updating to the latest plugin I started running the initial build and export on both of my disks. This kernel warning happened right after I started that process. Does any of this log mean anything too you?
Jan 6 21:55:02 Pithos kernel: ------------[ cut here ]------------ Jan 6 21:55:02 Pithos kernel: WARNING: CPU: 3 PID: 24488 at arch/x86/kernel/cpu/perf_event_intel_ds.c:315 reserve_ds_buffers+0x10e/0x347() Jan 6 21:55:02 Pithos kernel: alloc_bts_buffer: BTS buffer allocation failure Jan 6 21:55:02 Pithos kernel: Modules linked in: xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables kvm_intel kvm vhost_net vhost macvtap macvlan tun xt_nat veth ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat md_mod ahci r8169 i2c_i801 libahci mii Jan 6 21:55:02 Pithos kernel: CPU: 3 PID: 24488 Comm: qemu-system-x86 Not tainted 4.1.13-unRAID #1 Jan 6 21:55:02 Pithos kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H77 Pro4-M, BIOS P2.00 08/06/2013 Jan 6 21:55:02 Pithos kernel: 0000000000000009 ffff880357b039a8 ffffffff815f12b0 0000000000000000 Jan 6 21:55:02 Pithos kernel: ffff880357b039f8 ffff880357b039e8 ffffffff8104775b ffff88044f395ec0 Jan 6 21:55:02 Pithos kernel: ffffffff8101fd9b 0000000000000000 0000000000000000 0000000000010e10 Jan 6 21:55:02 Pithos kernel: Call Trace: Jan 6 21:55:02 Pithos kernel: [<ffffffff815f12b0>] dump_stack+0x4c/0x6e Jan 6 21:55:02 Pithos kernel: [<ffffffff8104775b>] warn_slowpath_common+0x97/0xb1 Jan 6 21:55:02 Pithos kernel: [<ffffffff8101fd9b>] ? reserve_ds_buffers+0x10e/0x347 Jan 6 21:55:02 Pithos kernel: [<ffffffff810477b6>] warn_slowpath_fmt+0x41/0x43 Jan 6 21:55:02 Pithos kernel: [<ffffffff8101fd9b>] reserve_ds_buffers+0x10e/0x347 Jan 6 21:55:02 Pithos kernel: [<ffffffff8101ab5c>] x86_reserve_hardware+0x141/0x153 Jan 6 21:55:02 Pithos kernel: [<ffffffff8101abb2>] x86_pmu_event_init+0x44/0x240 Jan 6 21:55:02 Pithos kernel: [<ffffffff810a7b77>] perf_try_init_event+0x42/0x74 Jan 6 21:55:02 Pithos kernel: [<ffffffff810ad260>] perf_init_event+0x9d/0xd4 Jan 6 21:55:02 Pithos kernel: [<ffffffff810ad61c>] perf_event_alloc+0x385/0x4f7 Jan 6 21:55:02 Pithos kernel: [<ffffffffa01c1553>] ? stop_counter+0x2f/0x2f [kvm] Jan 6 21:55:02 Pithos kernel: [<ffffffff810ad7bc>] perf_event_create_kernel_counter+0x2e/0x12c Jan 6 21:55:02 Pithos kernel: [<ffffffffa01c166e>] reprogram_counter+0xc0/0x109 [kvm] Jan 6 21:55:02 Pithos kernel: [<ffffffffa01c1739>] reprogram_fixed_counter+0x82/0x8d [kvm] Jan 6 21:55:02 Pithos kernel: [<ffffffffa01c1921>] reprogram_idx+0x4a/0x4f [kvm] Jan 6 21:55:02 Pithos kernel: [<ffffffffa01c2183>] kvm_handle_pmu_event+0x66/0x87 [kvm] Jan 6 21:55:02 Pithos kernel: [<ffffffffa01ee2dc>] ? vmx_invpcid_supported+0x1b/0x1b [kvm_intel] Jan 6 21:55:02 Pithos kernel: [<ffffffffa01ab2dc>] kvm_arch_vcpu_ioctl_run+0x4f9/0xeb0 [kvm] Jan 6 21:55:02 Pithos kernel: [<ffffffffa01f0773>] ? __vmx_load_host_state.part.53+0x125/0x12c [kvm_intel] Jan 6 21:55:02 Pithos kernel: [<ffffffffa01a665b>] ? kvm_arch_vcpu_load+0x139/0x143 [kvm] Jan 6 21:55:02 Pithos kernel: [<ffffffffa019dff1>] kvm_vcpu_ioctl+0x169/0x48f [kvm] Jan 6 21:55:02 Pithos kernel: [<ffffffffa019de88>] ? vcpu_put+0x3b/0x3b [kvm] Jan 6 21:55:02 Pithos kernel: [<ffffffff8110c316>] do_vfs_ioctl+0x367/0x421 Jan 6 21:55:02 Pithos kernel: [<ffffffff81114033>] ? __fget+0x6c/0x78 Jan 6 21:55:02 Pithos kernel: [<ffffffff8110c409>] SyS_ioctl+0x39/0x64 Jan 6 21:55:02 Pithos kernel: [<ffffffff815f69ae>] system_call_fastpath+0x12/0x71 Jan 6 21:55:02 Pithos kernel: ---[ end trace cf2394a39c569833 ]--- Jan 6 21:57:02 Pithos bunker: added 3 files from /mnt/disk2 with mask *. Duration: 00:04:54 Average speed: 46.6 MB/s Jan 6 21:57:27 Pithos bunker: added 8 files from /mnt/disk1 with mask *. Duration: 00:05:20 Average speed: 93.0 MB/s Jan 6 21:57:59 Pithos emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Jan 6 21:58:11 Pithos emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Jan 6 21:59:41 Pithos bunker: exported 42588 files from /mnt/disk1 with mask *. Duration: 00:00:31 Jan 6 22:00:24 Pithos emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Jan 6 22:01:51 Pithos bunker: exported 34208 files from /mnt/disk2 with mask *. Duration: 00:02:41
-
For those interested, version 2016.01.06a is available now, see release notes.
Just updated and saw that my disks have the orange circle. To clarify, will they always be a circle upon a refresh reboot of the server?
-
SMALL feature request for future bumps... a flag indicating if an initial build and a flag indicating an export has been accomplished per disk.
Have created the following, see the attached picture.
For all disks it will show whether an initial build and/or an initial export was done. A green check means yes, while an orange circle means no.
Useful ?
Yes, I think it looks nice and adds value.
-
I created a frontend for the NerdPack repo. Your presented with a table of the packages in the repo. It allows you to download, install, uninstall and remove the packages individually and all together. There's a couple of switches up top for uninstall and delete. So when a package is deselected and the Apply is clicked it will be uninstalled and/or deleted if selected. I haven't fully tested the update functions if a package is updated in the repo.
Also if screen is selected then utempter is selected also same for iotop and python. Let me know if there are any other packages that depend on each other.
https://raw.githubusercontent.com/dmacias72/unRAID-plugins/master/plugins/NerdPack.plg
Fantastic! I wanted to build something like that eventually since our list of packages keeps growing. Nice work!
Are you open to collaboration and merging your work in to the existing Nerdpack repo/plugin?
I open to whatever you wanna do. Let me know what you think is best.
Did you guys ever work out if this is getting incorporated directly into Nerdpack or if they are being separate?
-
Working Great! Thank you
SMALL feature request for future bumps... a flag indicating if an initial build and a flag indicating an export has been accomplished per disk.
Two more feature requests/wish list items
Not sure how much trouble they would be to implement but I figure it can not hurt to ask and see what sticks.1. It would be awesome if there was some sort of icon letting you know that all items (besides excluded folders) on disk1, 2, 3, etc. have a checksum. It would be nice for peace of mind. Maybe if not all file had a checksum then you could see a list of them?
2. Might also be nice if there was a way to check individual folders or files for valid checksums. Especially with people who have slower CPU's they might be concerned about a specific folder but a 8TB filled drive takes awhile to calculate.
-
Seems like a pretty interesting game. I was looking at the files on docker hub but honestly I am not good at all when it comes to creating dockers. If it was me I would end up creating a Linux VM and following this guide: http://ark.gamepedia.com/Dedicated_Server_Setup
But maybe someone with a better understanding of how docker works can point out what's going on...
-
I am a little confused as you can see. I am surprised that the all of the USB are not available to the server if no VM are up.
Regards.
Once a controller gets past through unRAID no longer can see the controller. Once the VM gets shutdown, unRAID doesn't know that the controller is available so you have to restart the server in order for unRAID to see it again. There may be some sort of script you can create that will let unRAID know that the controller is free.
-
So then I suppose even with hostdev you will still have to go through the entire first process of finding out which controller you want?
Yes you still have to do the steps up to and including 9.
Alright, made an 11.a and 11.b step giving users the choice
Just tried passthrough hostdev with a windows machine and that works fine.. But again a gfx card just gives a black screen/no output..
If I remember correctly, JonP mentioned many months ago in a forum post long forgotten, that he had much better luck with the arg format as opposed to the hostdev approach in regards to GPU... [disclaimer, I may have made all that up but I want to say I remember reading that]
-
So then I suppose even with hostdev you will still have to go through the entire first process of finding out which controller you want?
Yes you still have to do the steps up to and including 9.
Alright, made an 11.a and 11.b step giving users the choice
-
So then I suppose even with hostdev you will still have to go through the entire first process of finding out which controller you want?
Yes you still have to do the steps up to and including 9.
Slightly OT, but would hostdev work for gfx cards?
Yes
Might try in with OSX just for science....
Let me know what you find!
-
So then I suppose even with hostdev you will still have to go through the entire first process of finding out which controller you want?
-
For me it's much easier to use the hostdev tag instead of the qemu:arg. It's just too much trouble with it when you don't know what you are doing.
So for passing through a PCI(e) device with the hostdev tag this is the starting code:
I added this to the end of the guide, I know it is else where but I think it should be handy anyways. Thanks.
Good choice
I just read what you added and it says
Forget passing through an entire controller and just use Hostdev
That's not true
You are still passing through an entire controller, but only the way to do it is different.Oops good catch, I was editing the whole first page at a million miles a minute and sort of word vomitted that.
-
For me it's much easier to use the hostdev tag instead of the qemu:arg. It's just too much trouble with it when you don't know what you are doing.
So for passing through a PCI(e) device with the hostdev tag this is the starting code:
I added this to the end of the guide, I know it is else where but I think it should be handy anyways. Thanks.
-
Change the addr line to addr=00.0 and see what happens
-
I think you need to add this first
<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=00:14.0,bus=root.1,addr=00.0'/>
Hi again. No that didn't work. I didn't add this before because I thought it was for a card. Anyways it throws an error for the following:
<qemu:arg value='ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=1,chassis=1,id=root.1'/>[/b]
It it possibly the address as I highlighted above?
Thanks
I am wanting to see the XML with the above code entered so I can see if I can spot the issue. Your post on line 6 doesn't have the added code.
-
I think you need to add this first
<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=00:14.0,bus=root.1,addr=00.0'/>
Hi again. No that didn't work. I didn't add this before because I thought it was for a card. Anyways it throws an error for the following:
<qemu:arg value='ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=1,chassis=1,id=root.1'/>[/b]
It it possibly the address as I highlighted above?
Thanks
Depends on what the error message says? Can you post a screen shot?
See the scree capture:
Please post your entire XML as well.
-
nothing extra appears in device manager needing drivers. I am stumped really, am I missing something with the XML passthrough?
what is the difference between bus=pcie.0 and bus=root.1 ?? why would the usb be root and not a pcie number? or am I just making things up now as I have tried everything else??
I would try making a fresh XML of Windows with unraids VM creator and then only modify the lines necessary for USB passthrough. You will have to view your VM though VNC for the moment but try getting just that working first.
-
Win10 x64, I am just copying over a win 7 iso to try but would rather stick with 10 as I upgraded my install key!
Hmm yeah either should work just fine... So it boots up just fine without error but doesn't find the USB controller, correct? Does the device manager show an unknown device? Maybe check your mobo website for drivers? Other than that I don't have a clue [emoji58]
-
Win10 x64, I am just copying over a win 7 iso to try but would rather stick with 10 as I upgraded my install key!
Hmm yeah either should work just fine... So it boots up give fine without error but doesn't find the USB controller, correct? Does the device manager show an unknown device? Maybe check your mobo website for drivers? Other than that I don't have a clue [emoji58]
-
yup I already tried that, and still nothing. to me it seems like the VM does not see the USB controller even though I have passed it through.
What's OS are you running?
Not sure how much trouble they would be to implement but I figure it can not hurt to ask and see what sticks.
unRAID 6 NerdPack - CLI tools (iftop, iotop, screen, kbd, etc.)
in Plugin Support
Posted
+2, or even if you hit "help" and it listed underneath.