OddMagnet

Same thing again today, Docker logs got an unexpected EOF again as well. Guess I'll have to go with the slow and painful "disabling some containers and checking if it still happens"

Again, the interface spam happened at 8am on Sunday. I've tried getting logs from docker via this script: #!/bin/bash cd /mnt/user/appdata timeout 2h docker compose logs -f -t --since=1s > /mnt/user/data/docker-compose.log However, this didn't record properly for the full duration: Script Starting Apr 28, 2024 07:00.01 Full logs for this script are available at /tmp/user.scripts/tmpScripts/Get Docker Compose Logs/log.txt error from daemon in stream: Error grabbing logs: unexpected EOF Script Finished Apr 28, 2024 07:01.21 Full logs for this script are available at /tmp/user.scripts/tmpScripts/Get Docker Compose Logs/log.txt I don't think it's a problem with the script, since it recorded over a minute. The last line from the logs doesn't seem to be the problem either: autobrr | 2024-04-28T05:01:21.043895040Z {"level":"debug","module":"filter","method":"CheckFilter","time":"2024-04-28T07:01:21+02:00","message":"(Cross-Seed) external filter check not matching what filter wanted"}

So I've setup a user script to start logging docker events on Sundays, one hour before the interface spam happens. Looking at the log, I can see a few things: container exec_create → exec_start → exec_die happens a lot. After a quick google search I learned that those events also happen for Healthchecks, which is the case in my logs a lot of container kill / die / stop happening after the interface spam started also a lot of network disconnect for my docker bridge network I've edited the logs to remove all the healthchecks and attached it here. I don't think there are any pointers in there, but if anyone is bored enough to take a look at it I'd appreciate it. Additionally I've checked docker compose logs (with --since and --until), but there's not much to see before the time of the problem. (It doesn't help that not all log lines contain times and the containers don't all use the same formatting for times...) For now I'll set up another script to catch the docker compose logs and hopefully that'll be more helpful next week.. docker-events-edited.log

Changed the cable and router port, hopefully it's not gonna happen again. Everything (Router, Cable, Server) is brand-new, but I'd much rather have the cable be the culprit, lol. What's weird though, is that eth0 always goes up again when I connect a KB+Monitor, login and start the diagnostics command. (and obviously loosing the physical link when nothing is moving is extremely weird in the first place)

that'd suck a lot. I guess that'd explain the drops for eth0 as well? Though it's weird there are only drops for receive Errors info Receive counters Transmit counters eth0 Errors: 0 Errors: 0 Drops: 19739 Drops: 0 Overruns: 0 Overruns: 0 Any suggestions on how I'd be able to verify what parts of the chain are good and where the problem actually is?

Had a look at the syslog, this time it's different it seems. Not interface spam before eth0 goes down. (I don't think it previously even had an entry about eth0 going down) @JorgeB can you take another look at the new diagnostics? oddnas-diagnostics-20240403-0729.zip

So it happened again, guess it's not a Sunday only thing then. Again no container restarts, nothing in the container or docker logs that would indicate any problems

So it happened again, or at least the "soft version" where all my containers restart after the interface spam. This seems to mostly happen on Sunday mornings, I've looked over all my container logs, but not one of them had anything in it that would indicate being a problem. Additionally I've checked all my container settings, but none of them are configured to do anything at around that time. It doesn't look like it's a docker problem to me. I'll try disabling some of my containers over the coming weeks and months, but it's gonna be a very tedious process of narrowing it down (if they're the problem) In the meantime, is there anything else I could check? I'm still confused why there is any mention of IPv6 in my logs, when I don't even have it enabled.

Still looking for help with this problem. I'd really like to solve the interface spam in my logs, which I believe is the root cause of my problem

Still looks like a problem to me though. To me it seems that WebGUI and SSH broke because of the interfaces being down (aside from the br-... and veth... interfaces) It's hard to believe that the spam I mentioned in my second post is completely unrelated to the interfaces going down. I don't understand why there are so many veth... interfaces in the first place, why the br-... interfaces ports are spamming my log so much or why there are entries about IPv6 when that's not even enabled in my settings

Containers all had 100% uptime (other than intentional restarts - e.g. when I changed things in the compose file)

Looking back, there also has been a lot of this, though I'm not sure if it's related: Mar 18 09:58:46 OddNas kernel: veth5e5dac8: renamed from eth0 Mar 18 09:58:46 OddNas kernel: br-db82cd71027f: port 20(veth3e692a8) entered disabled state Mar 18 09:58:46 OddNas kernel: br-db82cd71027f: port 20(veth3e692a8) entered disabled state Mar 18 09:58:46 OddNas kernel: device veth3e692a8 left promiscuous mode Mar 18 09:58:46 OddNas kernel: br-db82cd71027f: port 20(veth3e692a8) entered disabled state Mar 18 09:58:46 OddNas kernel: br-db82cd71027f: port 20(veth7260a7f) entered blocking state Mar 18 09:58:46 OddNas kernel: br-db82cd71027f: port 20(veth7260a7f) entered disabled state Mar 18 09:58:46 OddNas kernel: device veth7260a7f entered promiscuous mode Mar 18 09:58:46 OddNas kernel: br-db82cd71027f: port 20(veth7260a7f) entered blocking state Mar 18 09:58:46 OddNas kernel: br-db82cd71027f: port 20(veth7260a7f) entered forwarding state Mar 18 09:58:47 OddNas kernel: br-db82cd71027f: port 20(veth7260a7f) entered disabled state Mar 18 09:58:48 OddNas kernel: eth0: renamed from veth190d797 Mar 18 09:58:48 OddNas kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth7260a7f: link becomes ready Mar 18 09:58:48 OddNas kernel: br-db82cd71027f: port 20(veth7260a7f) entered blocking state Mar 18 09:58:48 OddNas kernel: br-db82cd71027f: port 20(veth7260a7f) entered forwarding state Some more stuff that might be noteworthy: Looking at the ifconfig.txt, there's a lot of vethsomething interfaces, no idea why In the same file, my aside from the above mentioned interfaces, only some br-... interface was up

I've had the WebGUI and SSH break one or two times before already and simply rebooted. This time I figured might as well connect my keyboard and monitor and create a diagnostics file. Weirdly enough, right when I pressed enter to start the diagnostics tool, the WebGUI and SSH started working again. I checked the logs and this seems to be the timeframe it happened (unless I'm misinterpreting something): 20:11 → WebGUI and SSH stopped working 20:20 → connected Keyboard 20:23 → connected Monitor 20:31 → started diagnostics Mar 20 17:05:06 OddNas sshd[8859]: Starting session: shell on pts/0 for root from 192.168.178.80 port 50226 id 0 Mar 20 20:11:15 OddNas kernel: e1000e 0000:00:1f.6 eth0: NIC Link is Down Mar 20 20:11:15 OddNas kernel: br0: port 1(eth0) entered disabled state Mar 20 20:11:18 OddNas ntpd[1127]: Deleting interface #1 br0, 192.168.178.200#123, interface stats: received=7185, sent=7186, dropped=0, active_time=1387370 secs Mar 20 20:11:18 OddNas ntpd[1127]: 216.239.35.12 local addr 192.168.178.200 -> Mar 20 20:11:18 OddNas ntpd[1127]: 216.239.35.8 local addr 192.168.178.200 -> Mar 20 20:11:18 OddNas ntpd[1127]: 216.239.35.4 local addr 192.168.178.200 -> Mar 20 20:11:18 OddNas ntpd[1127]: 216.239.35.0 local addr 192.168.178.200 -> Mar 20 20:20:51 OddNas kernel: usb 1-1: new full-speed USB device number 4 using xhci_hcd Mar 20 20:20:51 OddNas kernel: input: Corsair Corsair Gaming K55 RGB Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/0003:1B1C:1B3D.0002/input/input5 Mar 20 20:20:51 OddNas kernel: hid-generic 0003:1B1C:1B3D.0002: input,hidraw0: USB HID v1.11 Keyboard [Corsair Corsair Gaming K55 RGB Keyboard] on usb-0000:00:14.0-1/input0 Mar 20 20:20:51 OddNas kernel: input: Corsair Corsair Gaming K55 RGB Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/0003:1B1C:1B3D.0003/input/input6 Mar 20 20:20:51 OddNas kernel: input: Corsair Corsair Gaming K55 RGB Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/0003:1B1C:1B3D.0003/input/input7 Mar 20 20:20:51 OddNas kernel: input: Corsair Corsair Gaming K55 RGB Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/0003:1B1C:1B3D.0003/input/input8 Mar 20 20:20:51 OddNas kernel: hid-generic 0003:1B1C:1B3D.0003: input,hiddev96,hidraw1: USB HID v1.11 Keyboard [Corsair Corsair Gaming K55 RGB Keyboard] on usb-0000:00:14.0-1/input1 Mar 20 20:20:51 OddNas kernel: hid-generic 0003:1B1C:1B3D.0004: hiddev97,hidraw2: USB HID v1.11 Device [Corsair Corsair Gaming K55 RGB Keyboard] on usb-0000:00:14.0-1/input2 Mar 20 20:23:11 OddNas kernel: fbcon: i915drmfb (fb0) is primary device Mar 20 20:23:11 OddNas kernel: Console: switching to colour frame buffer device 320x90 Mar 20 20:23:11 OddNas kernel: i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device Mar 20 20:23:33 OddNas login: pam_unix(login:auth): authentication failure; logname=LOGIN uid=0 euid=0 tty=/dev/tty1 ruser= rhost= user=root Mar 20 20:23:36 OddNas login: FAILED LOGIN 1 FROM tty1 FOR root, Authentication failure Mar 20 20:24:04 OddNas login: pam_unix(login:session): session opened for user root(uid=0) by LOGIN(uid=0) Mar 20 20:24:04 OddNas login: ROOT LOGIN ON tty1 Mar 20 20:26:46 OddNas sshd[8859]: Read error from remote host 192.168.178.80 port 50226: No route to host Mar 20 20:26:46 OddNas sshd[8859]: pam_unix(sshd:session): session closed for user root Mar 20 20:27:17 OddNas root: ACPI action up is not defined Mar 20 20:27:18 OddNas root: ACPI action left is not defined Mar 20 20:27:18 OddNas root: ACPI action left is not defined Mar 20 20:27:18 OddNas root: ACPI action left is not defined Mar 20 20:27:18 OddNas root: ACPI action left is not defined Mar 20 20:27:18 OddNas root: ACPI action left is not defined Mar 20 20:27:19 OddNas root: ACPI action left is not defined Mar 20 20:27:22 OddNas root: ACPI action up is not defined Mar 20 20:27:22 OddNas root: ACPI action down is not defined Mar 20 20:31:39 OddNas kernel: e1000e 0000:00:1f.6 eth0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx Mar 20 20:31:39 OddNas kernel: br0: port 1(eth0) entered blocking state Mar 20 20:31:39 OddNas kernel: br0: port 1(eth0) entered forwarding state Mar 20 20:31:41 OddNas ntpd[1127]: Listen normally on 2 br0 192.168.178.200:123 Mar 20 20:31:41 OddNas ntpd[1127]: new interface(s) found: waking up resolver Mar 20 20:31:45 OddNas emhttpd: read SMART /dev/sdb Mar 20 20:32:19 OddNas sshd[13939]: Connection from 192.168.178.80 port 54474 on 192.168.178.200 port 22 rdomain "" Mar 20 20:32:19 OddNas sshd[13939]: Failed publickey for root from 192.168.178.80 port 54474 ssh2: ED25519 SHA256:GInj1AiL72FiRCs+JM71XjgEElxEiNHUoR508RkQS3g Mar 20 20:32:19 OddNas sshd[13939]: Postponed keyboard-interactive for root from 192.168.178.80 port 54474 ssh2 [preauth] Mar 20 20:32:22 OddNas sshd[13939]: Postponed keyboard-interactive/pam for root from 192.168.178.80 port 54474 ssh2 [preauth] Mar 20 20:32:22 OddNas sshd[13939]: Accepted keyboard-interactive/pam for root from 192.168.178.80 port 54474 ssh2 Mar 20 20:32:22 OddNas sshd[13939]: pam_unix(sshd:session): session opened for user root(uid=0) by (uid=0) Mar 20 20:32:22 OddNas sshd[13939]: Starting session: shell on pts/0 for root from 192.168.178.80 port 54474 id 0 Full diagnostics are attached oddnas-diagnostics-20240320-2031.zip

dhcpcd comes, afaik installed by default. I wasn't able to find anything saying otherwise. For now I've just disabled IPv6, would love to find a real solution to this

The Docker usage on my Dashboard is at 904 GiB Which happens to be pretty much exactly the amount of actually used space on my Cache disk: (904 GiB => 970 GB) A couple days ago, when my cache was almost full from transferring files: My Settings for Docker: Why is the usage showing like this? And is there any way to "fix" this? It's not affecting performance, but it'd be nice to see how much my Docker images are really using. (I checked and the actual size of all images is 81GB)

still got the problem, though it looks like it's not only spamming deletions now: Feb 16 12:39:43 OddNas avahi-daemon[17573]: Registering new address record for ADDRESS on br0.*. Feb 16 12:39:47 OddNas dhcpcd[1016]: br0: deleting address ADDRESS/64 Feb 16 12:39:47 OddNas avahi-daemon[17573]: Withdrawing address record for ADDRESS on br0. Feb 16 12:41:36 OddNas dhcpcd[1016]: br0: deleting address ADDRESS/64 Feb 16 12:42:44 OddNas avahi-daemon[17573]: Registering new address record for ADDRESS on br0.*.

By variables I meant that I replaced the same numbers in my logs with the same words, to anonymise my IPs Not sure where "dhcpcd" would be coming from then. I have these Plugins installed: Appdata Backup CA Mover Tuning Community Apps Compose.Manager Dynamix Active Streams File Manager S3 Sleep System Buttons System Information System Statistics System Temperature Enhanced Log Viewer File Activity Fix Common Problems Folder View Intel GPU TOP NerdTools Open Files Theme Engine Tips and Tweaks Unassigned Devices + Preclear Unraid Connect User Scripts I checked NerdTools and it isn't installed there (not even listed there).

When checking the logs, they're flooded with "deleting address". Here's a bit of those logs: Feb 11 04:44:52 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 04:45:07 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 04:45:58 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 04:49:18 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 04:49:23 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 04:49:27 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 04:54:59 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 04:55:04 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 04:57:44 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 04:57:45 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 04:57:47 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 04:58:19 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 05:07:30 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 05:08:16 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 05:16:08 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 05:16:12 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 05:19:04 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 05:19:05 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 05:19:23 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 05:19:28 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 05:22:06 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 05:22:10 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 05:22:12 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 05:22:15 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 05:22:16 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 05:22:32 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 05:26:29 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 05:26:33 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 05:26:37 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 05:27:44 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 05:59:12 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 06:07:32 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 06:09:39 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 06:09:46 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 06:12:53 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 06:13:06 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 06:13:10 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 06:13:15 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 06:14:10 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 06:14:14 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 06:14:18 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 06:20:05 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 06:27:44 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 06:33:40 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 06:35:04 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 06:35:42 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 06:38:00 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 06:38:05 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 06:47:41 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 06:51:17 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 06:57:44 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:01:46 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:03:42 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:03:46 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:03:51 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:10:01 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:10:05 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:10:10 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:13:42 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:21:23 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:21:28 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:27:44 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:27:45 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:33:49 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:42:11 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:47:17 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:53:00 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:54:09 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:54:13 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:54:18 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:54:28 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:55:06 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:57:08 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:57:13 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:57:16 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:57:44 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:57:45 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:58:26 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:58:30 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:58:35 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 08:00:04 Unraid-NAS kernel: vethbf49f2a: renamed from eth0 Feb 11 08:00:04 Unraid-NAS kernel: br-9a649b6f5d31: port 1(veth99ebabf) entered disabled state Feb 11 08:00:04 Unraid-NAS kernel: br-9a649b6f5d31: port 1(veth99ebabf) entered disabled state Feb 11 08:00:04 Unraid-NAS kernel: device veth99ebabf left promiscuous mode Feb 11 08:00:04 Unraid-NAS kernel: br-9a649b6f5d31: port 1(veth99ebabf) entered disabled state Feb 11 08:00:05 Unraid-NAS kernel: br-9a649b6f5d31: port 1(vethf6bba0f) entered blocking state Feb 11 08:00:05 Unraid-NAS kernel: br-9a649b6f5d31: port 1(vethf6bba0f) entered disabled state Feb 11 08:00:05 Unraid-NAS kernel: device vethf6bba0f entered promiscuous mode Feb 11 08:00:05 Unraid-NAS kernel: br-9a649b6f5d31: port 1(vethf6bba0f) entered blocking state Feb 11 08:00:05 Unraid-NAS kernel: br-9a649b6f5d31: port 1(vethf6bba0f) entered forwarding state Feb 11 08:00:05 Unraid-NAS kernel: eth0: renamed from veth732f06a Feb 11 08:00:05 Unraid-NAS kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethf6bba0f: link becomes ready I've redacted my IPV6 addresses. Couldn't find a tool for that, so I simply replaced parts of it by variables, where I saw them repeating ¯\_(ツ)_/¯ Here's what my settings look: Interface eth0 IPv6 address assignment: Automatic IPv6 address: [PART1]:[PART2] / 64 IPv6 default gateway: fe80::[GATEWAY-ADDRESS] IPv6 privacy extensions: Disabled IPv6 DNS server assignment: Automatic IPv6 DNS server: fd00::[GATEWAY-ADDRESS] IPv6 DNS server 2: [PART1][GATEWAY-ADDRESS] Desired MTU: 1500 Enable VLANs: No Interface Extra Current listening interfaces: br0 Include listening interfaces: -empty- Exclude listening interfaces: -empty- Routing Table ROUTE - GATEWAY - METRIC IPv4 default - 192.168.178.1 via br0 - 0 172.22.0.0/16 - br-9a649b6f5d31 - 0 192.168.178.0/24 - br0 - 1 IPv6 [PART1]::/64 - br0 - 1005 [OTHER-ADDRESS]::/64 - br0 - 1005 default - fe80::[GATEWAY-ADDRESS] via br0 - 1005

Okay, so since I‘m reaching C10 that should be the case for me as well. It sounds like after that there’s no difference compared to headless in terms of power savings?

I‘m confused, I assumed not plugging in any monitor would be running headless. Is there a difference?

Had to go a bit more complicated, since Unraid is kept in Memory. So I created the file /boot/rules/01-asrock-led.rules, then added commands to /boot/config/go so it'd copy and reload the rules. # Copy the rules file cp /boot/rules/01-asrock-led.rules /etc/udev/rules.d/ chmod 644 -R /etc/udev/rules.d/01-asrock-led.rules 2> /dev/null # reload udev rules udevadm control --reload-rules udevadm trigger Sadly this doesn't work though. Not sure what I'm missing I was missing the udevadm trigger 🤦‍♂️ I don't have USB devices plugged in, other than the USB for Unraid. The only other thing plugged in is my network cable. From what I was able to google "consoleblank" shouldn't make any difference is no screen is plugged in, right? After disabling the LED controller, I'm down to !!! 6W IDLE !!!, pretty fucking good I'd say I'm pretty much ~90% C10 Idle, is that something that can still be pushed? (I'm literally clueless, first time trying to build a DIY NAS ^^') Based on the device stats I think there isn't anything left to disable? The Device 1ed0:2283 seems to be a Non-Volatile memory controller, I assume that's for my SSD, so a no-no in terms of disabling

Hey @genesisdoeswhatnintendont, thanks so much for your guide, I followed it and am able to reach C10 now (mostly) and dropped down to 10W Idle. I have a couple of questions, since you have the exact same Mainboard that I do. Not sure if you're still around since your post was a year ago, but here's to hoping (not sure why I thought that, lol) Could you explain what those do exactly? I looked at the `setup_script_file`, but it's not quite clear to me. It looks like "LED MCU" disabled USB devices, so that's a no-no for me since I'm using Unraid I guess? "Native ASPM" disabled means that the BIOS handles ASPM, correct? If so that should be good for me as well? (already enabled it) "Discrete Bluetooth Interface" not sure if this applies to the AsRock H610m-itx. Does it use Bluetooth over the Wifi Antennas? Would that also disable Wifi? "Password protection of Runtime Variables" just means I could use that tool without having to set an admin password? @genesisdoeswhatnintendont, could I compare my BIOS settings with yours? Currently I'm still getting about 28% C2, which I'd like to eliminate as well if possible

Gonna try a couple more things in BIOS before giving this a try, will report back after that. Checked without it, sadly not the cause of my problems. (Or luckily I guess, since I don't need to send it back, lol)

Hey guys, I've followed the guide, but I can't reach better than C3 PKG states. Hoping to get some help here My System is: CPU: i3-13100 MB: AsRock H610m-itx RAM: Mushkin 2x32GB SSD: Teamgroup MP33 Pro 2TB I haven't installed HDDs yet, since I'm still waiting for my case, lol. (So I decided to dive into this topic while waiting xD) Not sure if this matters, but I've not created the Cache Pool with my SSD either. The iGPU driver however is installed. Current Idle Draw: 15W (I assume/hope this can still go lower) I've attached screenshots of my powertop idle stats, device stats and tunables, as well as the ASPM stats. Device Stats looks suspicious to me, since some devices are permanently at 100%? When checking the CPU frequency there are always some cores jumping to ~4GHz before going down to 800MHz again. Unraid WebGUI was not open, I only used the terminal to access Unraid. Additionally, here are my BIOS settings: CPU Config: Hyper Threading: Enabled Active P-Cores: All CPU C States Support: Enabled Enhanced Halt State: Enabled CPU C6 & C7 Support: Enabled CPU Package C State Support: Enabled CFG Lock: Disabled (couldn't find any real info on what this does ¯\_(ツ)_/¯ ) C6DRAM: Enabled AVX/AVX2: Enabled Intel Virtualization Technology: Enabled Hardware Prefetcher: Enabled Adjacent Cache Line Prefetch: Enabled Chipset Config: Primary Graphics Adapter: Onboard Above 4G Decoding: Enabled Clever Access Memory: Enabled VI-d: Enabled SR-IOV Support: Enabled DMI Link Speed: Gen4 PCIE1 Link Speed: Auto PCI Express Native Control: Enabled PCIE ASPM Support: L1 PCH PCIE ASPM Support: L1 DMI ASPM Support: Enabled PCH DMI ASPM Support: Enabled iGPU Multi Monitor: Disabled Intel® Ethernet Connection I219-V: Enabled Onboard HD Audio: Disabled Onboard WAN Device: Disabled Deep Sleep: Enabled in S4-5 Restore on AC/Power Loss: Power Off Restore Onboard LED Default: Disabled RGB LED: Off GNA Device: Disabled Storage Config: SATA Controller(s): Enabled SATA Mode Selection: AHCI Hybrid Storage Detection and Configuration Mode: Disabled SATA Aggressive Link Power Management: Enabled Hard Disk S.M.A.R.T: Enabled ACPI Config: Suspend to RAM: Auto (other choice was disabled) PS/2 Keyboard Wake Support: Disabled PCIE Devices Power On: Disabled I219 LAN Power On: Disabled RTC Alarm Power On: By OS USB Keyboard/Mouse Power On: Disabled USB Config Legacy USB Support: Enabled XHCI Hand-off: Disabled Lastly: I found this post on askubuntu.com, which was about the my exact MB, is that something I should look into? Don't want to go around installing Windows on my SSD and doing some potential dangerous stuff before asking here first

Based on the docs that should work as well (didn't test it yet) I guess that's probably more reasonably, to expect people like me to just set that variable