L0rdRaiden

That happend whem I was tryng to move files from one place to another to see If I could copy files to a folder. I enable the share after that, so is not connected. Maybe my issue if one of those weird things that are fixed after reboot the client and or the server, I will try.

I have 5 nodes, all of them "identical" but one of them the first one "Storj1" have a high delta, all the others runs ok. Any idea why? fw/nat rules are the same for all the nodes, using pfsense here.

attached I installed local master to see if the situation improves, thanks. mediacenter-diagnostics-20180429-1756.zip

This is so broken or I don't get how it works. I have a samba shares as public, I access to it but for some reason I have read access but can't write, fantastic. So I disable the share (export=NO) and I can still access to the folder read movies, files whatever I want.... Does it makes any sense? why I can't write in the samba folder? I don't get why nothing works as is suppose to work.

Sonnar have been adding epsiodes to ruTorrent (those are added in stop mode but I can live with this) when the download finished sonnar says "eppisode missing from disk" but the files are there. This was working in the past with other series, so now I don't understand why it doesn't work. 18-4-29 15:24:54.2|Info|SceneMappingService|Updating Scene mappings 18-4-29 15:24:55.3|Info|RefreshSeriesService|Updating Info for XXXXX 18-4-29 15:24:55.3|Info|RefreshEpisodeService|Starting episode info refresh for: [296762][XXXXX] 18-4-29 15:24:55.3|Info|RefreshEpisodeService|Finished episode refresh for series: [296762][XXXXX]. 18-4-29 15:24:55.3|Info|DiskScanService|Scanning disk for XXXXX 18-4-29 15:24:55.3|Info|DiskScanService|Completed scanning disk for XXXXX 18-4-29 15:24:55.5|Info|MetadataService|Series folder does not exist, skipping metadata creation XXXXX= hide on purpose

Updates from Storj, I don't know exactly what they mean and how will affect to the multinode setup. https://blog.storj.io/post/172871463238/updates-to-farmer-payouts-and-network-testing

Do this start with 0.1 volts just in the CPU

Does the container path has to be in "/dev/urandom" or it can be in my usual Docker folder?

anybody got this working? when I install hyperv on server 2016, next boot the system is dead.

Well I have pfsense, so I call it firewall. Regarding the ports I have read the documentation and in principle if you are not using tunels just opening 4000 4004 4008 4012 and 4016 is enough.

I have installed windows server 2016 with the templated offered by unraid, then, I install the virtio drivers and the agent. I install all the windows updates. Then I install hyperv, windows reboots and die, next restart it enters in thourbleshoot mode and can't recognize any windows partition. This has happend 3 times. In the template Hyper-V: is set to YES. Anybody else is experiencing this problem? The log of the VM 2018-04-02 11:21:00.964+0000: starting up libvirt version: 4.0.0, qemu version: 2.11.1, hostname: MediaCenter LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name 'guest=Windows Server 2016,debug-threads=on' -S -object 'secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-13-Windows Server 2016/master-key.aes' -machine pc-i440fx-2.11,accel=kvm,usb=off,dump-guest-core=off,mem-merge=off -cpu host,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff,hv_vendor_id=none -drive file=/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd,if=pflash,format=raw,unit=0,readonly=on -drive file=/etc/libvirt/qemu/nvram/f6a72869-27b2-6432-644f-7accf6b6aa71_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 4096 -realtime mlock=off -smp 4,sockets=1,cores=4,threads=1 -uuid f6a72869-27b2-6432-644f-7accf6b6aa71 -no-user-config -nodefaults -chardev 'socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-13-Windows Server 2016/monitor.sock,server,nowait' -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-hpet -no-shutdown -boot strictgent.0,server,nowait' -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device usb-tablet,id=input0,bus=usb.0,port=1 -vnc 0.0.0.0:1,websocket=5701 -k es -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 -msg timestamp=on 2018-04-02 11:21:00.964+0000: Domain id=13 is tainted: high-privileges 2018-04-02 11:21:00.964+0000: Domain id=13 is tainted: host-cpu 2018-04-02T11:21:01.004947Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/1 (label charserial0) 2018-04-02T11:21:42.409897Z qemu-system-x86_64: terminating on signal 15 from pid 7817 (/usr/sbin/libvirtd) 2018-04-02 11:21:42.634+0000: shutting down, reason=shutdown

I did the setup with the bridges and I could replicate your result, thanks. On the firewall do you open ports 4000, 4004, 4008, or the whole range from 4000 to 4011? Let see how it goes.

I have all the cores between 3.3 and 3.6 GHz and the CPU use is almost idle between 0 and 2 % Is this normal? With Intel the freq under windows go much lower. cpufreq-info tell me something different. 000 3306000 00 sec 011 ms 00 sec 988 ms 01 001 3648000 00 sec 013 ms 00 sec 986 ms 01 002 3382000 00 sec 009 ms 00 sec 990 ms 00 003 3230000 00 sec 003 ms 00 sec 996 ms 00 004 3420000 00 sec 007 ms 00 sec 992 ms 00 005 3686000 00 sec 007 ms 00 sec 992 ms 00 006 3268000 00 sec 012 ms 00 sec 987 ms 01 007 3382000 00 sec 005 ms 00 sec 994 ms 00 ^C root@MediaCenter:~# cpufreq-infpo -bash: cpufreq-infpo: command not found root@MediaCenter:~# cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to [email protected], please. analyzing CPU 0: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 4294.55 ms. hardware limits: 1.60 GHz - 3.80 GHz available frequency steps: 3.80 GHz, 1.60 GHz available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil current policy: frequency should be within 1.60 GHz and 3.80 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.60 GHz (asserted by call to hardware). cpufreq stats: 3.80 GHz:1.30%, 1.60 GHz:98.70% (172407) analyzing CPU 1: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 1 CPUs which need to have their frequency coordinated by software: 1 maximum transition latency: 4294.55 ms. hardware limits: 1.60 GHz - 3.80 GHz available frequency steps: 3.80 GHz, 1.60 GHz available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil current policy: frequency should be within 1.60 GHz and 3.80 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.60 GHz (asserted by call to hardware). cpufreq stats: 3.80 GHz:1.16%, 1.60 GHz:98.84% (67851) analyzing CPU 2: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 2 CPUs which need to have their frequency coordinated by software: 2 maximum transition latency: 4294.55 ms. hardware limits: 1.60 GHz - 3.80 GHz available frequency steps: 3.80 GHz, 1.60 GHz available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil current policy: frequency should be within 1.60 GHz and 3.80 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.60 GHz (asserted by call to hardware). cpufreq stats: 3.80 GHz:0.95%, 1.60 GHz:99.05% (109275) analyzing CPU 3: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 3 CPUs which need to have their frequency coordinated by software: 3 maximum transition latency: 4294.55 ms. hardware limits: 1.60 GHz - 3.80 GHz available frequency steps: 3.80 GHz, 1.60 GHz available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil current policy: frequency should be within 1.60 GHz and 3.80 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.60 GHz (asserted by call to hardware). cpufreq stats: 3.80 GHz:1.22%, 1.60 GHz:98.78% (67545) analyzing CPU 4: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 4 CPUs which need to have their frequency coordinated by software: 4 maximum transition latency: 4294.55 ms. hardware limits: 1.60 GHz - 3.80 GHz available frequency steps: 3.80 GHz, 1.60 GHz available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil current policy: frequency should be within 1.60 GHz and 3.80 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.60 GHz (asserted by call to hardware). cpufreq stats: 3.80 GHz:0.84%, 1.60 GHz:99.16% (100685) analyzing CPU 5: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 5 CPUs which need to have their frequency coordinated by software: 5 maximum transition latency: 4294.55 ms. hardware limits: 1.60 GHz - 3.80 GHz available frequency steps: 3.80 GHz, 1.60 GHz available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil current policy: frequency should be within 1.60 GHz and 3.80 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.60 GHz (asserted by call to hardware). cpufreq stats: 3.80 GHz:1.19%, 1.60 GHz:98.81% (68539) analyzing CPU 6: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 6 CPUs which need to have their frequency coordinated by software: 6 maximum transition latency: 4294.55 ms. hardware limits: 1.60 GHz - 3.80 GHz available frequency steps: 3.80 GHz, 1.60 GHz available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil current policy: frequency should be within 1.60 GHz and 3.80 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.60 GHz (asserted by call to hardware). cpufreq stats: 3.80 GHz:0.84%, 1.60 GHz:99.16% (100911) analyzing CPU 7: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 7 CPUs which need to have their frequency coordinated by software: 7 maximum transition latency: 4294.55 ms. hardware limits: 1.60 GHz - 3.80 GHz available frequency steps: 3.80 GHz, 1.60 GHz available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil current policy: frequency should be within 1.60 GHz and 3.80 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.60 GHz (asserted by call to hardware). cpufreq stats: 3.80 GHz:0.74%, 1.60 GHz:99.26% (69445)

I am talking about this picture where all use 4000

The first time I had 8/8 cores, second time 4, maybe the second time there was something corrupt in the virtual disk. But still in hyperv I can assign 8 cores benchmark or run a cpu stress test and hyper v doesn't die and the other VM will go slow but won't die.

I have notice that unraid becomes unresponsive affecting docker and Unraid itself when a VM is stressing the CPU, up to the point to kill unraid and require a hard shutdown. Has happens while doing a benchmark, and after another VM that was freeze and Unraid wasn't able to kill it. This doesn't happens in promox or hyperv so I guess they have some kind of mechanism to ensure hypervisor stability. I think the implementation of KVM in unraid could be done better and there should be a way to manage the resource sharing between docker and VM. In promox you can share cores among VM but assign preference for a VM. Am I the only one experiencing this? I have had to restore unraid from backup 2 times in 24 hours because of this. I was using 3 VM win 10 and win 2016 and Pfsense. Could promox be integrated in unraid somehow? Or parts of it? @limetech https://pve.proxmox.com/wiki/Open_Source

For those trying the OC instead of disabling the C6 state, now Ryzen 2400g is stable with just +0,1v in the processor, not in the core. A question I have is if there is a way in Ryzen to see the real freq to which the processor is working, the processor governor is set on demand so it should scale up and down. Is there a way to see this on real time?

What response time are you getting? I have between 6 and 10 secs

In my json files for the storj containers I have 4004 for Storj2 and 4008 for Storj3. If you look at the storjshare status they are using those ports not 4000

Ok thanks, So in the firewall are you doing port forwarding of 4000 only for the first container or for the range 4000-4003? On the other hand I still don't get why unraid\docker reports the same ports for all the containers despite these are different as you can see when I post the storjshare status

I use br0 usually in all my Dockers because it allows to assign different IP. What is the conceptual difference between br0 and bridge? Which one should I use for docker? I thought that br0 was already a bridge

@MrChunky I have already running several Storj containers the problem is that despite having them in diferent ports and working unraid tell me that they are using the same ports. THe json files have differnet ports 4000 4004 and 4008 and the firewall has open this ports and reporting the traffic correctly Still in advance mode I don't see the container port field root@MediaCenter:~# docker exec Storj3 storjshare status ┌─────────────────────────────────────────────┬─────────┬──────────┬──────────┬─────────┬───────────────┬─────────┬──────────┬───────────┬──────────────┐ │ Node │ Status │ Uptime │ Restarts │ Peers │ Allocs │ Delta │ Port │ Shared │ Bridges │ ├─────────────────────────────────────────────┼─────────┼──────────┼──────────┼─────────┼───────────────┼─────────┼──────────┼───────────┼──────────────┤ │ dcea81e7741aeb8db49174ac5821d9035b00e532 │ running │ 2m 25s │ 0 │ 129 │ 0 │ 18ms │ 4008 │ ... │ connected │ │ → /storj/share │ │ │ │ │ 0 received │ │ (TCP) │ (...%) │ │ └─────────────────────────────────────────────┴─────────┴──────────┴──────────┴─────────┴───────────────┴─────────┴──────────┴───────────┴──────────────┘ root@MediaCenter:~# docker exec Storj storjshare status ┌─────────────────────────────────────────────┬─────────┬──────────┬──────────┬─────────┬───────────────┬─────────┬──────────┬───────────┬──────────────┐ │ Node │ Status │ Uptime │ Restarts │ Peers │ Allocs │ Delta │ Port │ Shared │ Bridges │ ├─────────────────────────────────────────────┼─────────┼──────────┼──────────┼─────────┼───────────────┼─────────┼──────────┼───────────┼──────────────┤ │ 6ec5490584a014188a8e3ae366d5e17ed7749bf1 │ running │ 2h 6m 4… │ 1 │ 120 │ 3 │ ... │ 4000 │ 505.73MB │ connected │ │ → /storj/share │ │ │ │ │ 0 received │ │ (TCP) │ (0%) │ │ └─────────────────────────────────────────────┴─────────┴──────────┴──────────┴─────────┴───────────────┴─────────┴──────────┴───────────┴──────────────┘ root@MediaCenter:~# docker exec Storj storjshare status ^[[A^[[A^[[A ┌─────────────────────────────────────────────┬─────────┬──────────┬──────────┬─────────┬───────────────┬─────────┬──────────┬───────────┬──────────────┐ │ Node │ Status │ Uptime │ Restarts │ Peers │ Allocs │ Delta │ Port │ Shared │ Bridges │ ├─────────────────────────────────────────────┼─────────┼──────────┼──────────┼─────────┼───────────────┼─────────┼──────────┼───────────┼──────────────┤ │ 6ec5490584a014188a8e3ae366d5e17ed7749bf1 │ running │ 2h 6m 4… │ 1 │ 121 │ 3 │ ... │ 4000 │ 505.73MB │ connected │ │ → /storj/share │ │ │ │ │ 0 received │ │ (TCP) │ (0%) │ │ └─────────────────────────────────────────────┴─────────┴──────────┴──────────┴─────────┴───────────────┴─────────┴──────────┴───────────┴──────────────┘ root@MediaCenter:~# docker exec Storj2 storjshare status ┌─────────────────────────────────────────────┬─────────┬──────────┬──────────┬─────────┬───────────────┬─────────┬──────────┬───────────┬──────────────┐ │ Node │ Status │ Uptime │ Restarts │ Peers │ Allocs │ Delta │ Port │ Shared │ Bridges │ ├─────────────────────────────────────────────┼─────────┼──────────┼──────────┼─────────┼───────────────┼─────────┼──────────┼───────────┼──────────────┤ │ 4dd54ed8e3b68fe752618e17055e4eec52114b4c │ running │ 15m 21s │ 0 │ 156 │ 1 │ 4ms │ 4004 │ ... │ connected │ │ → /storj/share │ │ │ │ │ 0 received │ │ (TCP) │ (...%) │ │ └─────────────────────────────────────────────┴─────────┴──────────┴──────────┴─────────┴───────────────┴─────────┴──────────┴───────────┴──────────────┘

@MrChunky Clould you post an screenshot of your port mapping column in the docker tab? In the port configuration in unraid I only have Host port not Container port...

And can I do that even with the array started?

OFFTOPIC. that interface is qemu? can you manage/configure unraid VM with that? how?