L0rdRaiden

@limetech You may want to consider this webgui: VMmachine updates default bus to VirtIO for FreeBSD because it doesn't work, at least in opnsense and pfsense. With Sophos XG doesn't work either although it is based on linux. In case this is the bus for the hardrive image, I had to use SATA.

How do I close some of them without restarting unraid?

I'm having a similar issue here What has the solution at the end? it was fixed in unraid?

But the setting of the HD isn't just wrong? Is making everything to use more space, can't be changed doing a backup and reformating the disk? Is the setting to fix it available in the unraid interface?

It says 512bytes logical, 4096 bytes physical for the HD The SSD cache is 512bytes logical/physical Should I change it?

With br0 you have to port forward to the ip you assign to the comtainer

The sector size I guess, it says 4k aligned, is this the sector size?

I have installed win10 and win server with the virtIO drivers. I have check with HWindo64 and CPUZ and desplite the power plan being on balance the freq of the CPU is always as maximun Is there a way to configure KVM so the CPU freq scales with demand as It happens when you install the SO in baremetal? I have a Ryzen 2400G

I this possible now? to bypass the APU of a Ryzen 2400G? I see the model in the Graphics Card: drop down menu.

with CA Backup you backup the Docker folder but how do you actually backup unraid? just copying the content of the flash?

I have folders in the SSD (Cache) witha size of 500MB but a disk size of 1.4GB. In windows it appears fine. I guess is because of the 4k format? isn't it better a lower one? why is this the default? If I want to convert the disk do I have to re-format it? or can I just convert it?

So the only way to fix it is a restart? or is there a cooldown?

I have the same problem, I can access with SSH but if I open the web terminal I get this error in the log Mar 30 22:27:58 MediaCenter login[30658]: ILLEGAL ROOT LOGIN on '/dev/pts/9' Mar 30 22:28:13 MediaCenter login[30785]: ILLEGAL ROOT LOGIN on '/dev/pts/8' Same issue in chrome and firefox, all I did between working and not working was to create a win 10 VM

For me it works If I have one in host and another in custom br0, the problem with br0 is that I have problems with port forwarding Unraid is reporting the port 4000 despite in the json file I have 4004 192.168.1.214:4000/tcp192.168.1.214:4000 192.168.1.214:4001/tcp192.168.1.214:4001 192.168.1.214:4002/tcp192.168.1.214:4002 192.168.1.214:4003/tcp192.168.1.214:4003 and now it works, don't ask me why root@MediaCenter:~# docker exec Storj2 storjshare status ┌─────────────────────────────────────────────┬─────────┬──────────┬──────────┬─────────┬───────────────┬─────────┬──────────┬───────────┬──────────────┐ │ Node │ Status │ Uptime │ Restarts │ Peers │ Allocs │ Delta │ Port │ Shared │ Bridges │ ├─────────────────────────────────────────────┼─────────┼──────────┼──────────┼─────────┼───────────────┼─────────┼──────────┼───────────┼──────────────┤ │ 4dd54ed8e3b68fe752618e17055e4eec52114b4c │ running │ 3m 54s │ 0 │ 101 │ 0 │ 50ms │ 4004 │ ... │ 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 │ 3h 16m … │ 0 │ 105 │ 3 │ 0ms │ 4000 │ 505.73MB │ connected │ │ → /storj/share │ │ │ │ │ 0 received │ │ (TCP) │ (0%) │ │ └─────────────────────────────────────────────┴─────────┴──────────┴──────────┴─────────┴───────────────┴─────────┴──────────┴───────────┴──────────────┘ THe only problem is that needs around 120MB or RAM and when is actually doing something I have read that it can take up to 1 GB

I did the same.... What command do you use to see the status of the second node?

I did this but I get this error, Storj is my original container Storj2 is the new one. Am I using the command right? root@MediaCenter:~# docker exec Storj storjshare status ┌─────────────────────────────────────────────┬─────────┬──────────┬──────────┬─────────┬───────────────┬─────────┬──────────┬───────────┬──────────────┐ │ Node │ Status │ Uptime │ Restarts │ Peers │ Allocs │ Delta │ Port │ Shared │ Bridges │ ├─────────────────────────────────────────────┼─────────┼──────────┼──────────┼─────────┼───────────────┼─────────┼──────────┼───────────┼──────────────┤ │ 6ec5490584a014188a8e3ae366d5e17ed7749bf1 │ running │ 15m 32s │ 0 │ 107 │ 0 │ 32ms │ 4000 │ 505.73MB │ connected │ │ → /storj/share │ │ │ │ │ 0 received │ │ (TCP) │ (0%) │ │ └─────────────────────────────────────────────┴─────────┴──────────┴──────────┴─────────┴───────────────┴─────────┴──────────┴───────────┴──────────────┘ root@MediaCenter:~# docker exec Storj2 storjshare status Error response from daemon: Container 8c732a9d378bab85f3b062afb47c63713e0248a2bcd6cbc8752ea5b634e1fdcf is restarting, wait until the container is running root@MediaCenter:~# docker exec Storj2 storjshare status Error response from daemon: Container 8c732a9d378bab85f3b062afb47c63713e0248a2bcd6cbc8752ea5b634e1fdcf is restarting, wait until the container is running root@MediaCenter:~# docker exec Storj2 storjshare status Error response from daemon: Container 8c732a9d378bab85f3b062afb47c63713e0248a2bcd6cbc8752ea5b634e1fdcf is restarting, wait until the container is running I edited the Json file but it looks like is not even reading it, share and log folder and empty despite having Storj2 container running. What network type do you use?

I hope you can get this work for dummies, like everything configurable from the docker template. I have tried to troubleshoot the folder error but nothing works. Just running 1 node.

I would be as well interested in this

It work, somehow I was able to enter to a kind of BIOS related to PXE not Seabios and I could change the boot order, so now 1 of the nics doesn't try to boot but the other still try to do it. I have tried to press different buttons at different times to see If I can get into a different BIOS but no luck. Does SEABIOS has a bios interface?

If I run the comand below in the screenshot I get the output above the command Every time I run the command it writes a new Json file but I don't know where it is stored Every time I run the command to create a new node I get this error The path are fine, is case sensitive, I don't now what could be failing, I have found this https://github.com/Storj/storjshare-daemon/issues/122 but I don't know how to use it to fix this issue Any idea?

Regarding the system stats app is there any way to keep log of the statistics even when you are not viewing them? I mean every time I enter in the Stats tabs everything is reset, and all the graphs start to write at the time and open the tab, previous data doesn't exist, doesn't matter if I change the periods available when you select Real time -> 2h, 1h, 30 min etc.

In the docker containers, this 2 graphs produces a perfect match (talking about the netdata screeshot), which makes sense, but in the VM I get what you can see in the picture bellow and it doesn't match with what unraid is reporting (unraid reported and average of 15-20% as much load during the period 10:50 and 10:55, and the CPU report included in the application (SophosXG) running in the VM was reporting almost a iddle load... Why is this? I don't know what to trust. I have all the cores assigned to SophosXG and looking at the netdata graphs everything else was mostly idle. In te doc

Like this? it doesn't work

The disk image is a bootable disk with SophosXG on it, it's like a firewall based on linux, I have the same issue with pfsense, which is a firewall based on FreeBSD The pcie card is based on i350 lan chipset. The image is bootable but the OS on both pfsense and sophos XG only start after the VM tries to boot or do whatever is trying to do with the 2 nics, which if you don't skip the process manually it takes around 3 mins or more. It tries to do it with one nic and then with the other.

Any help here? it can't be that hard, and I can't be the only one with this issue. Both nics belong to the same pcie card and they are passthrough to the VM