NickI
Members
-
Joined
-
Last visited
-
Thank you so much i knew its something in front of my eyes that i couldn't see. Just for my personal reference, or anyone ever reaching into this topic, this is the topic that explains the Turbo Write perfectly https://forums.unraid.net/topic/50397-turbo-write/
-
Hi Everyone, i would kindly like to ask for your help on this issue i am struggling with. I have been operating my unraid for years, and i had no issues with drives spinning down. Without knowing when exactly this started i have really tried to find the reason why. I know i have the syslog process writing to disk 3 which i expect to wake up parity as well, however, all the rest of the disks should be spun down. When i spin down the disks, i see for example Disks 1 and 3 which i now they are used, but almost instantly the rest are spun up again, at the same time the syslog writes read SMART /dev/sdX Your insights would be really appreciated. nas-unraid-diagnostics-20250524-2356.zip
-
Hi i am getting the same strange behaviour from the plugin. I am a long time user of Unbalanced so i know this is this not normal. To explain in a bit more detail I am trying for example to gather some files distributed to multiple disk to cache. So i select the GATHER action, select the share and click Next. Usually the plan phase took around 30sec max. After looking at the log and waiting for the plan to complete, the planning phase took around 6 minutes to complete. Have a look at the log 2024/06/04 08:37:16 scanning:disk(/mnt/disk1):folder(nextcloud) 2024/06/04 08:40:13 issues:owner(0):group(0):folder(39465):file(91400) 2024/06/04 08:40:14 items:count(6):size(13.40 GB) 2024/06/04 08:40:14 scanning:disk(/mnt/disk2):folder(nextcloud) 2024/06/04 08:42:23 issues:owner(0):group(0):folder(69196):file(19822) 2024/06/04 08:42:24 items:count(5):size(34.94 GB) 2024/06/04 08:42:24 scanning:disk(/mnt/disk3):folder(nextcloud) 2024/06/04 08:42:24 issues:owner(0):group(0):folder(76):file(26) 2024/06/04 08:42:24 items:count(3):size(5.14 MB) 2024/06/04 08:42:24 scanning:disk(/mnt/disk4):folder(nextcloud) 2024/06/04 08:42:24 issues:not-available:(stat /mnt/disk4/nextcloud: no such file or directory) 2024/06/04 08:42:24 items:not-available:(stat /mnt/disk4/nextcloud: no such file or directory) 2024/06/04 08:42:24 scanning:disk(/mnt/disk5):folder(nextcloud) 2024/06/04 08:43:09 issues:owner(0):group(0):folder(25461):file(8091) 2024/06/04 08:43:09 items:count(8):size(5.34 GB) 2024/06/04 08:43:09 scanning:disk(/mnt/disk6):folder(nextcloud) 2024/06/04 08:43:11 issues:owner(0):group(0):folder(539):file(608) 2024/06/04 08:43:11 items:count(5):size(3.36 GB) 2024/06/04 08:43:11 scanning:disk(/mnt/cache):folder(nextcloud) 2024/06/04 08:43:11 issues:owner(0):group(0):folder(4):file(1) 2024/06/04 08:43:11 items:count(1):size(205.48 KB) After that, the move phase worked as expected.
-
Hi everyone! we could though install virt tools into a small linux vm or live cd/img and do these operations right? I guess providing direct access to the domains share.
-
-
NickI changed their profile photo
-
Hi everyone, i recently started monitoring my server with netdata, and i started getting a lot of messages from the service about packet loss on various virtual interfaces all comming down to eth0 # uptime 15:16:58 up 3 days, 1:53, 1 user, load average: 1.81, 2.01, 2.15 # ifconfig eth0 eth0: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 1500 ether 3c:7c:3f:7d:42:a0 txqueuelen 1000 (Ethernet) RX packets 67059799 bytes 74451288124 (69.3 GiB) RX errors 0 dropped 32374 overruns 0 frame 0 TX packets 49994008 bytes 41492480626 (38.6 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 for my setup eth0 is used for dockers and vms and unraid access, except my pfsense VM running completely on a different separate intel network card. This means that i have a 0,04% of packet loss on my eth0 interface since last reboot for 12 release, which i guess is acceptable, however i would like to get rid of it. Do you have any hints of what could be going wrong here? Thank you in advance.
-
i only reboot my unraid for updates, so depends on Lime-tech release cycle....the biggest one i think 6 months since i installed the 6.12.0 rc6 from 6.11.5 on Nov 2022.
-
Paypal would also be an option i would consider, i use it a lot.
-
Definitely multiple array pools would be my No.1 go to feature request and an added bonus: trim support for SSDs 🔥
-
I don't use them and probably never will. But i liked the idea of relating this feature with the share.
-
32GB. I am running a lot of dockers and a few demanding VMs including my Internet gateway and Home Assistant installation
-
Amazing work, thank you! I came across this plugin while i was searching for a way to transmit the ups power consumption readings via mqtt to my home assistant setup. Do anyone know if something like this even exists?
-
After updating to 6.11.1 i issued an update all through the UI button to update all dockers in my installation. After the process completed all the updates it was supposed to do, it started updating all my dockers one by one. This is not supposed to happen, the process was stopping the dockers, tried to pull an updated image which was up to date and then started the docker again. When the list of dockers ended it started again from the top. To stop it i had to go to the cli and kill the update process manually. root 27866 1 0 08:18 ? 00:00:01 /usr/bin/php -q /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/update_container swag*adguardhome*Agent-DVR*redis*unifi-controller*Metabase*code-server*nextcloud*binhex-delugevpn*sonarr*nzbhydra2*jackett*overseerr*netdata*uptime-kuma*swag*adguardhome*Agent-DVR*redis*unifi-controller*Metabase*code-server*nextcloud*binhex-delugevpn*sonarr*nzbhydra2*jackett*overseerr*netdata*uptime-kuma*swag*adguardhome*Agent-DVR*redis*unifi-controller*Metabase*code-server*nextcloud*binhex-delugevpn*sonarr*nzbhydra2*jackett*overseerr*netdata*uptime-kuma*swag*adguardhome*Agent-DVR*redis*unifi-controller*Metabase*code-server*nextcloud*binhex-delugevpn*sonarr*nzbhydra2*jackett*overseerr*netdata*uptime-kuma*swag*adguardhome*Agent-DVR*redis*unifi-controller*Metabase*code-server*nextcloud*binhex-delugevpn*sonarr*nzbhydra2*jackett*overseerr*netdata*uptime-kuma*swag*adguardhome*Agent-DVR*redis*unifi-controller*Metabase*code-server*nextcloud*binhex-delugevpn*sonarr*nzbhydra2*jackett*overseerr*netdata*uptime-kuma*swag*adguardhome*Agent-DVR*redis*unifi-controller*Metabase*code-server*nextcloud*binhex-delugevpn*sonarr*nzbhydra2*jackett*overseerr*netdata*uptime-kuma*swag*adguardhome*Agent-DVR*redis*unifi-controller*Metabase*code-server*nextcloud*binhex-delugevpn*sonarr*nzbhydra2*jackett*overseerr*netdata*uptime-kuma*swag*adguardhome*Agent-DVR*redis*unifi-controller*Metabase*code-server*nextcloud*binhex-delugevpn*sonarr*nzbhydra2*jackett*overseerr*netdata*uptime-kuma*swag*adguardhome*Agent-DVR*redis*unifi-controller*Metabase*code-server*nextcloud*binhex-delugevpn*sonarr*nzbhydra2*jackett*overseerr*netdata*uptime-kuma*swag*adguardhome*Agent-DVR*redis*unifi-controller*Metabase*code-server*nextcloud*binhex-delugevpn*sonarr*nzbhydra2*jackett*overseerr*netdata*uptime-kuma
-
I also wanted to say i am having the same issue with GraphQL offline. Until some time, just restarting the unraid-api twice on each system reboot was enough. Now, i am getting the sign-in prompt, and regardless of how many times i login, the prompt is the same
-
Hello Everyone, i also got trouble with the TemplateURL behaviour, where some of my dockers could not start due my port assignments. Especially heimdall that by default wanted to listen to port 80, 443/tcp, but i already had swag listening to these ports. its no issue for me editing the necessary xml files. However i observed that the apps that behaved the way i expected them to (honour my local configuration) had the TemplateURL defined in the xml file, just like the ones that "misbehaved" and decided to write this here for reference. For example: Organizr app, never created any issues for me re-adding ports i did not want, and uses this xml template https://raw.githubusercontent.com/Organizr/docker-organizr/master/organizr.xml Inside this template i saw: <Config Name="WebUI" Target="80" Default="" Mode="tcp" Description="Container Port: 80" Type="Port" Display="always" Required="false" Mask="false"/> I noticed that on the WebUI config the default port is empty and set as not required. On the other hand, heimdall the misbehaving app, had the default ports set to 80,443 and set as required <Config Name="WebUI" Target="80" Default="80" Mode="tcp" Description="http gui" Type="Port" Display="always" Required="true" Mask="false"/> <Config Name="Port: 443" Target="443" Default="443" Mode="tcp" Description="https gui" Type="Port" Display="always" Required="true" Mask="false"/> Clearly, this is the template's author decision to honour the local configuration of the app, and there is nothing wrong with Unraid's behaviour. Having said that, if i for example removed the required and default assignments in template authoring mode, what would this count as an alternative workaround on removing the template url from xml file?
