-
Posts
264 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Report Comments posted by Iker
-
-
Sorry, I have some workloads on the two servers that are important, so I can not provide diagnostics right now, however it seems to be replicated by other user:
-
hdparm -C /dev/sdx
smartctl -i -n standby /dev/sdx
-
Hi, ZFS Master developer here; I have already answered some of the doubts on the plugin thread; however, I thought it would be beneficial also to respond and even dive a little bit deeper here.
Just one question regarding this issue. Are you experiencing the same behavior even with the main tab closed? I agree that loading the main tab will wake up your disks, but there are no other background processes in the plugin besides the ones running when the main tab is open. So if your spin-up issue persists even with the unRaid GUI closed, something else is happening.
Please confirm if that is the case.
-
Upgrade from RC1 without any problems, everything seems to work just fine, however in the developer console this message keeps popping up; it doesn't interfere with anything beyond "My Servers" as long as I can tell, but maybe is of help for you as developers:
-
Same here, a couple of days ago I update and getting flood with these messages:
021-10-12 17:34:57.980+0000: 20738: error : virConnectNumOfDefinedStoragePools:244 : this function is not supported by the connection driver: virConnectNumOfDefinedStoragePools 2021-10-12 17:34:57.981+0000: 8018: error : virConnectNumOfStoragePools:164 : this function is not supported by the connection driver: virConnectNumOfStoragePools 2021-10-12 17:34:57.982+0000: 20735: error : virConnectNumOfStoragePools:164 : this function is not supported by the connection driver: virConnectNumOfStoragePools 2021-10-12 17:34:57.982+0000: 20731: error : virConnectNumOfDefinedStoragePools:244 : this function is not supported by the connection driver: virConnectNumOfDefinedStoragePools 2021-10-12 17:34:57.983+0000: 7992: error : virConnectNumOfSecrets:79 : this function is not supported by the connection driver: virConnectNumOfSecrets
A Temporary Workaround to prevent Log from filling up to 100% with messages this command flush the logs:
rm /var/log/libvirt/libvirtd.log virt-admin daemon-log-outputs ""
- 1
-
Upgrade from beta 35 to RC2 without any problems MOBO:
OS: UNRAID OS Basic Version: 6.9.0-rc2 (Next) (on Kingston Data Traveler 16GB)
Hardware: X470 GAMING PRO CARBON (MS-7B78) | AMD Ryzen 5 2600 OC 3.8 GHz | Corsair Vengeance LPX (2x32GB) DDR4 DRAM 3600MHz C18 | Geforce GTX 1060 3 GB, Intel 82576 Dual NIC
Storage: Intel 660P NVME 1TB x 2 RAID-0 Cache | Seagate Barracuda 4 TB, 8 TB | Seagate IronWolf 4 TB
Dockers: letsencrypt, Plex, Tautulli, RedNode, MQTT, Wekan, Pydio, SageMath, Psono, ELK Stack, Sonarr, Radarr, Bazzar, TIG Stack
VMs: Windows 10, Windows Server 2019, MacOS Catalina, Ubuntu 20.0.4, pfSense
-
I can confirm that in my mobo, upgrading from 6.8.3 everything is working flawlessly, the cpu governor and performance in general is better than ever and bluestacks is finally working in my VMs.
Hardware: X470 GAMING PRO CARBON (MS-7B78) | AMD Ryzen 9 3900x NO OC | Corsair Vengeance RGB Pro (4x16GB) DDR4 DRAM 2400MHz C16 | Geforce GTX 1060 3 GB, Intel 82576 Dual NIC
Storage: Intel 660P NVME 1TB x 2 RAID-0 Cache | Seagate Barracuda 4 TB, 8 TB | Seagate IronWolf 4 TB
Dockers: swag, Plex, Tautulli, NodeRed, MQTT, Wekan, Pydio, SageMath, Psono, ELK Stack, Sonarr, Radarr, Bazzar, TIG Stack
VMs: Windows 10, Windows Server 2019, MacOS Catalina, Ubuntu 20.0.4, pfSense- 1
[6.12] Networking not working correctly after upgrading to 6.12 and changing docker to ipvlan
in Stable Releases
Posted · Edited by Iker
Jummm, that's weird; as I said in the other post, I experienced the same error with the same resolution. My router is an Asus with Asuswrt-Merlin fully updated, and my 2, 6.12 Unraid servers are using static IP addresses; the other one with 6.11.5 it's working just fine. In my case I don't use the ipvlan feature; none of my dockers receive exclusive IP addresses. Over the weekeend, I will try to replicate the issue and provide diagnostics.