melorin83

Guys, is it a bad idea to use mixed ECC RAM in this MOBO? 1-1 piece of the following ones: KSM48E40BD8KM-32HM KSM48E40BD8KI-32HA

The newest BIOS (4302) prevents the CPU C-states get above C2, so the power consumption is around 45W idle, instead of ~15W with C8. So I downgraded to 4101 and everything is fine again.

And do not forget to set these settings too. It is all you need for C8 state and sub 20W power consumption. Picture

I do not use the IPMI card. 13600K 32GB ECC RAM 1x500GB WD RED NVMe SSD (cache) 3x18TB HDD (idle) I think most people do not touch this setting in the BIOS, but it it the most important one: Package C State Limit: Auto You MUST set it to C8 or C10, otherwise it won't go lower than C3.

Hi all! I have been using this MOBO for a month now and I love it. I do not know you guys what you are doing to get that high idle power consumption but mine is idleing at 14W. Of course if You use some PCIE cards which prevent lower C-states it is understandable. But I think some potential buyer skipped this MOBO because this false information about high power consumption.

Hello. I have this message in the webdav log: httpd: Could not reliably determine the server's fully qualified domain name, using 172.17.0.13. Set the 'ServerName' directive globally to suppress this message I edited the httpd.conf file and added this line: ServerName localhost But nothing changed, still the same warning in the log. What should I do?

Thank you for your answer!

I am only talking of PCH connected M.2 slots. My MOBO has 1 CPU and 3 PCH attached M.2 slots.

Hey folks, I have a question which I have never got answered on the internet. I have a motherboard with Z790 chipset. It has the following M.2 support: Intel® Z790 Chipset: M.2_2 slot (Key M), type 2242/2260/2280 (supports PCIe 4.0 x4 mode) M.2_3 slot (Key M), type 2242/2260/2280/22110 (supports PCIe 4.0 x4 mode) M.2_4 slot (Key M), type 2242/2260/2280 (supports PCIe 4.0 x4 & SATA modes) Z790 and i5-13600K are connected via DMI 4.0 x8. An NVMe SSD has/needs x4 connection. If I populate all the M.2 slots, 3 SSD need 12 PCIe lanes. But Z790 chipset only have 8. What happens in this case? All SSD switch to X2 mode and I lose half the bandwith? Or 2 SSD have the full bandwith and the 3rd one is disabled? Please help me to understand it.

I have an Asus Z690-P D4 CSM motherboard and had the same issue, the OS (unraid) does not start if the monitor is unplugged. Fast boot was the problem. Without it works like a charm.

Thanks, I"ll give it a try. What NIC is fully supported and no issues at all, even work with C-state >C3?

Hello, this is my first post in this forum My problem is that after some idle time, my server cannot be reached. Not with SMB shares nor SSH or through web interface. At the first time I had this issue I pushed the power button on the server and the system went down properly, so it wasn't frozen. After power ON again, it worked for 2 days without any problem. Of course the log mirror to the flash drive was turned OFF so I did not know what the problem was. Today I lost the connection again but instead of resetting the server again, I tried to unplug and plug the LAN cable. And tadaaam, I can reach Unraid again! I checked the log and found this: Aug 31 09:16:57 NAS kernel: pcieport 0000:00:1c.2: AER: Uncorrected (Non-Fatal) error message received from 0000:02:00.0 Aug 31 09:16:57 NAS kernel: r8125 0000:02:00.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) Aug 31 09:16:57 NAS kernel: r8125 0000:02:00.0: device [10ec:8125] error status/mask=00004000/00500000 Aug 31 09:16:57 NAS kernel: r8125 0000:02:00.0: [14] CmpltTO (First) Aug 31 09:16:57 NAS kernel: r8125 0000:02:00.0: AER: can't recover (no error_detected callback) Aug 31 09:16:57 NAS kernel: pcieport 0000:00:1c.2: AER: device recovery failed ->I unplugged the LAN cable Aug 31 10:31:12 NAS kernel: r8125: eth0: link down Aug 31 10:31:12 NAS kernel: bond0: (slave eth0): link status definitely down, disabling slave Aug 31 10:31:12 NAS kernel: device eth0 left promiscuous mode Aug 31 10:31:12 NAS kernel: bond0: now running without any active interface! Aug 31 10:31:12 NAS kernel: br0: port 1(bond0) entered disabled state Aug 31 10:31:15 NAS ntpd[1319]: Deleting interface #1 br0, 192.168.1.51#123, interface stats: received=158, sent=162, dropped=0, active_time=99230 secs Aug 31 10:31:15 NAS ntpd[1319]: 216.239.35.4 local addr 192.168.1.51 -> <null> ->I plugged the LAN cable Aug 31 10:31:17 NAS kernel: r8125: eth0: link up Aug 31 10:31:17 NAS kernel: bond0: (slave eth0): link status definitely up, 1000 Mbps full duplex Aug 31 10:31:17 NAS kernel: bond0: (slave eth0): making interface the new active one Aug 31 10:31:17 NAS kernel: device eth0 entered promiscuous mode Aug 31 10:31:17 NAS kernel: bond0: active interface up! Aug 31 10:31:17 NAS kernel: br0: port 1(bond0) entered blocking state Aug 31 10:31:17 NAS kernel: br0: port 1(bond0) entered forwarding state Aug 31 10:31:19 NAS ntpd[1319]: Listen normally on 2 br0 192.168.1.51:123 Aug 31 10:31:19 NAS ntpd[1319]: new interface(s) found: waking up resolver Do you have any idea what went wrong with the ethernet at 09:16:57 ?