deebeo

Leider zu spät gesehen - das neue Lizenzmodell ist ja... 🤐 Unraid ist zweifellos cool, aber 250€ cool? 35 Euro fee pro Jahr bei nicht-Lifetime finde ich definitiv zu hart. Schade, dass auch der Black Friday Sale gefühlt ein totaler Reinfall ist.

Wieviel nimmt er denn so, wenn Frigate und HA laufen?

Ja okay, das gleiche wie für die Coral TPU als USB Dongle gilt ja im Prinzip dann auch wieder für etwaige ZIgbee USB dongles, die ja auch nicht abgeschaltet werden können. Dh selbst ohne Frigate könnte ich mich eh von der Ultra-Niedrigverbrauchsidee verabschieden. Danke, die Diskussion hat mir weitergeholfen. Da hätte ich sonst bittere Tränen geweint, nachdem ich hunderte von Euros ausgegeben hätte 🤣

Leistung im Prinzip. Frigate allein bringt beim n5105 trotz google coral schonmal alle Kerne auf ca 30-40 % (5 4k Cams). Aktuell läuft noch kein HA, Zigbee und Homematic drauf und etwas skalieren will ich gerne auch noch können. Media-technisch passt das eigentlich im Moment schon soweit. Dazu kommt aber natürlich der "will basteln" Faktor. Ich möchte halt gerne ein langfristig gutes Fundament legen. Von daher schaue ich vielleicht mal nach einem Board, für das hier das Vorgehen für möglichst niedrige Verbräuche dokumentiert ist. Ich kann zwar einen lauffähigen PC zusammenschrauben, aber bei C States, Aufteilung von PCIE Lanes etc hört es dann bei mir auf Schönen Tag!

Danke! Werde ich wohl tun. Das A und O für niedrigen Stromverbrauch scheinen ja zuerst die Bios Settings zu sein. Gibt es da irgendwo einen Allgemeinen Thread mit Empfehlungen(den ich bisher nicht gefunden habe), oder Empfehlungen speziell für ein Asus Z690-P D4? Ich kenne den Fred von mgutt, wo er spezifisch auf bestimmte Gigabyte Boards eingeht.

Hi Zusammen, ich habe eine Frage zu den CPU Typen von Intel: T CPUs sind nach dem, was ich so gelesen habe, die CPUSs, die mit weniger Kühlung(Laptops, kleine Geräte etc) klarkommen sollen. Um mit weniger Kühlung klar zu kommen, werden diese in der Leistung begrenzt, was dazu führt, dass sie weniger Strom verbrauchen. Ist das so richtig? Und kann man mit einer K CPU den gleichen, niedrigen Stromverbrauch erzielen, wenn man die CPU in der Leistung begrenzt, oder bringt das andere Nachteile? Sollte man für einen Stromsparserver unbedingt eine von Intel aus begrenzte T CPU nehmen, oder kann man auch eine K CPU selbst herunter regeln? Ich frage, weil ich einen i5 12600k auf einem Asus Z690-P D4 hier habe, der mit 125W jetzt erstmal keine Alternative für einen Server ist, der so wenig wie möglich verbrauchen soll. Anwendung wäre bei mir hauptsächlich Nas ein paar Media-Docker Container, Home Assistant, Frigate und vielleicht ab und zu mal eine Linux VM. Keine VMs zum Spiele streamen etc. Ich habe aktuell 2x m2 NVME(Pool), 1x SSD(cache) und 5 HDDs(array), die ich in diesem potentiellen Server betreiben wollen würde.(Die HDDs laufen derzeit auf einem N5105 Board). Kann man damit realistisch ein gutes Ergebnis hinsichtlich Verbrauch erzielen? Danke und viele Grüße,

Thanks mate. I already had NTP enabled and unraid time was correct. Just a simple reboot did indee fix it.

Good Morning All, I am running Frigate on unraid(docker) and my Timestamps in Frigate are 9 hours off. Time Config in Unraid is correct and /etc/localtime is passed to the docker container as /etc/localtime which as i found out on the forums should theoretically pass on the correct time. Is there anything else i need to to like setting a timezone in Frigate as well? I couldnt find any other information yet. Thanks! Any helping comment is appreciated.

Using iperf3 across multiple different devices and jackpoints throughout my network I worked out that writing to unraid from devices within the same VLAN worked completely fine. When tried writing or reading from PCs in another VLAN is when things slowed down siginificantly. I am using a Unifi Dream Machine which seems to be overpowered by VLAN routing larger amounts of data passing through. I opened another Lan Port on unraid and connected it to my second VLAN which holds my devices of daily use. This completely fixed the issue.

Hi, have any of you had any problems with the Intel 226-V Network adapters? Mine won't make more data transfer than ~240megabits per second although unraid dashboard shows them to be in 1000 Mbps, full duplex, mtu 1500. Please let me know, if you had the same problem and found a solution. Regards, deebeo

This is writing from pc to unraid: (looks the same from another pc) copy from unraid to pc:(looks the same on other pc as well) copy array share to nvme share internally None of the shares involved use secondary storage.. To me it is obious that the target drive is generally fast enough and CAN write much quicker. Data intake or export over LAN seems to be the problem. I have not tested the reconstruct write setting since the target is a nvme drive, the setting seems to be for turnable drives and drive performance doesnt seemt to be the issue.

Write speed internally array to cache nvme is fine (190 MB/s)

HI Guys, I can't seem to find out why write speeds to my unraid are so low. Scenario is as follows. I was trying to send a large file (>1GB) to a share on my newly set up unraid -> Speed only goes up to ~ 26MB/s Tried again with a SSD Pool share instead of array as target : Same result. Connected my laptop with disabled wifi via cable to the same switch as unraid is connected to: Only slightly better rate but still <30MB/s I changed the LAN cable for the unraid pc and the one between the switch to which unraid is hooked up and the main router/switch in my network. Unraid Home screen shows: eth3: 1000 Mbps, full duplex, mtu 1500 --> should be capable of >100MB/s Inbound: 226 Mbps I tried to simplify as much as possible by writing straight to an NVME share und eliminating faulty LAN connections. I am thinking this has to be some kind of driver issue. These are my lan Ports in system devices. As far as I can tell, the controller name is correct. IOMMU group 18: [8086:125c] 03:00.0 Ethernet controller: Intel Corporation Ethernet Controller I226-V (rev 04) IOMMU group 19: [8086:125c] 04:00.0 Ethernet controller: Intel Corporation Ethernet Controller I226-V (rev 04) IOMMU group 20: [8086:125c] 05:00.0 Ethernet controller: Intel Corporation Ethernet Controller I226-V (rev 04) IOMMU group 21: [8086:125c] 06:00.0 Ethernet controller: Intel Corporation Ethernet Controller I226-V (rev 04) Diagnostics are attached. What else can I try to find the problem? Any kind of help is greatly appreciated! nas-diagnostics-20240203-1722.zip

Hi Guys, I am currently trying to get my unraid-independent Win11 installation working also as a VM in such a way that i can boot either directly into windows OR run Windows via Unraid VM when I'm booting into unraid. So far the VM starts and I can see Windows on my Screen which is attached to the passed-through graphics card. However Windows doesnt recognize the Graphics Card as an Nvidia 3070. The device manager only shows "Other Devices -- Videocontroller (vga compatible). Resolution is vga(ish). I'm thinking this has to do with missing or wrong virtio drivers. So I have mounted virtio-win-0.1.225.img inside the vm and tried searching for a new driver on the mounted driver cd... without results. What am I missing ? Which driver and how can I install it? I already ran the installer which is on the virtio cd. This gave me a working network card but still no graphics. Since this is an already running PC i couldnt install the drivers during windows setup. What am I missing? Please help

Thanks for the heads-up will try this later.

this seems to do the trick: <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source dev='/dev/nvme1n1' index='2'/> <backingStore/> <target dev='hdc' bus='sata'/> <boot order='1'/> <alias name='sata0-0-2'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> unfortunately windows is all going crazy with security problems and is also missing internet. Probably due to missing virtio drivers. will try do install them during normal boot,

Hi Everyone, I would like to use the Win11 Installation on my PC in two ways 1. Boot directly to Windows 2. Boot to unraid and start same Windows in a VM In order to realise 2. I need some kind of way to use the Windows HD as a primary Vdisk in the VM configuration. I already read that the disk needs to be mounted, which it is. Do I need to put the device or only the partition into the vdisk definition? What kind of Vdisk Bus do I have to use? Right now im getting the error message Cannot access storage file '/mnt/disks/50026B7684AE8FDD-part3': No such file or directory Im guessing "disk type='file'" my be wrong? Any Help would be greatly appreciated. Here is the VM config I tried last: <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/disks/50026B7684AE8FDD-part3/'/> <target dev='hdc' bus='sata'/> <boot order='1'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> Here ist the definition of my drive:

solved. seems to have been some kind of cache issue. after clearing multiple times, it finally worked again

I also can't create user or do other stuff... error looks similar Oct 26 15:03:20 unraid nginx: 2022/10/26 15:03:20 [error] 3224#3224: *20744 connect() to unix:/var/run/emhttpd.socket failed (11: Resource temporarily unavailable) while connecting to upstream, client: 192.168.16.34, server: , request: "GET /update.htm?cmd=/webGui/scripts/share_size&arg1=system&arg2=ssz1&arg3=nvme&csrf_token=CD4F477987583A39 HTTP/1.1", upstream: "http://unix:/var/run/emhttpd.socket:/update.htm?cmd=/webGui/scripts/share_size&arg1=system&arg2=ssz1&arg3=nvme&csrf_token=CD4F477987583A39", host: "192.168.16.173", referrer: "http://192.168.16.173/Shares" Oct 26 15:04:34 unraid nginx: 2022/10/26 15:04:34 [error] 3224#3224: *21390 connect() to unix:/var/run/emhttpd.socket failed (11: Resource temporarily unavailable) while connecting to upstream, client: 192.168.16.34, server: , request: "POST /update.htm HTTP/1.1", upstream: "http://unix:/var/run/emhttpd.socket:/update.htm", host: "192.168.16.173", referrer: "http://192.168.16.173/Users/UserAdd"

Hi guys, after moving to new hardware and basically changing all the disks in my system I am trying to rebuild... and stumble across not being able to create shares. While moving I lost all my shares except system so I am currently trying to set them up correctly again. I am filling out the new share form but cant save when I'm done. The "Add Share" screen stays open and the new share doesn't appear. log says: Oct 26 14:52:13 unraid nginx: 2022/10/26 14:52:13 [error] 3224#3224: *13806 connect() to unix:/var/run/emhttpd.socket failed (11: Resource temporarily unavailable) while connecting to upstream, client: 192.168.16.34, server: , request: "POST /update.htm HTTP/1.1", upstream: "http://unix:/var/run/emhttpd.socket:/update.htm", host: "192.168.16.173", referrer: "http://192.168.16.173/Shares/Share?name=" Google told me to turn off my ad blocker which I did. Unfortunately this changed nothing. Diagnostics are attached. I am aware there are many different problems to be solved which I am planning to tackle one by one now... Any Idea on why this happens? Thanks for any help or comment! unraid-diagnostics-20221026-1252.zip

Thanks, I removed one of 2 types of RAM i had in the computer. However I can't run the memtest - the computer restarts right away after selecting memtest from the menu. After having crashed again just today, there are fatal errors in my syslog which do not speak to me. Apr 17 08:22:46 unraid kernel: BERT: Error records from previous boot: Apr 17 08:22:46 unraid kernel: [Hardware Error]: event severity: fatal Apr 17 08:22:46 unraid kernel: [Hardware Error]: Error 0, type: fatal Apr 17 08:22:46 unraid kernel: [Hardware Error]: section_type: Firmware Error Record Reference Apr 17 08:22:46 unraid kernel: [Hardware Error]: Firmware Error Record Type: SOC Firmware Error Record Type2 Apr 17 08:22:46 unraid kernel: [Hardware Error]: Revision: 2 Apr 17 08:22:46 unraid kernel: [Hardware Error]: Record Identifier: 8f87f311-c998-4d9e-a0c4-6065518c4f6d Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000000: 41037305 00000273 29348faa 00000000 .s.As.....4).... Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000010: 00210000 00000005 80003fff 0001f65c ..!......?..\... Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000020: 0001f658 00027d44 00000002 02000000 X...D}.......... Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000030: 04c70000 f1804f02 0a6053ff e0a000b1 .....O...S`..... Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000040: 1100009f 00200020 01004000 00000000 .... . ..@...... Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000050: 00000004 00500881 000ecf02 0304035d ......P.....]... Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000060: 00000000 31000000 00015bf8 7f110600 .......1.[...... Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000070: 088001fc fe39ffe0 0f07817f ff7f07c6 ......9......... Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000080: 1889ffff f839ffe0 0002007d 03c97007 ......9.}....p.. Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000090: 5bf83100 00000001 00000106 e0000000 .1.[............ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000000a0: 0114b8c7 00000002 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000000b0: 00000000 5a582100 00000081 00000117 .....!XZ........ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000000c0: 0006ffe0 40003c00 00000808 e0000000 .....<.@........ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000000d0: a0180000 00000040 00000000 00400000 ....@.........@. Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000000e0: 00001000 00000340 00000000 00000000 ....@........... Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000000f0: 00000000 00000000 02002080 7f05fe03 ......... ...... Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000100: 00000001 00000000 00000000 a31b0000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000110: 000000a0 00203301 00000080 09110000 .....3 ......... Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000120: 80000000 a0000000 80074fec b1746f80 .........O...ot. Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000130: 06ffff81 00000000 00000000 001f0000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000140: 0000001f 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000150: 00000000 00000000 00200172 00000000 ........r. ..... Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000160: 00000000 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000170: 00000000 00000000 00000000 000fff01 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000180: 00000000 00000000 001f0000 0000001f ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000190: 00000000 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000001a0: 00000000 04000172 00000000 00000000 ....r........... Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000001b0: 00000000 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000001c0: 00000000 00000000 000fff01 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000001d0: 00000001 001f0000 0000001f 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000001e0: 00000000 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000001f0: 00000172 00000006 00000000 00000000 r............... Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000200: 00000000 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000210: 38048500 83048433 00000004 00000000 ...83........... Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000220: 001f0000 0000001f 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000230: 00000000 00000000 00000000 04000172 ............r... Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000240: 00000000 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000250: 00000000 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000260: 000fff01 00000000 00000000 001f0000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000270: 0000001f 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000280: 00000000 00000000 04200172 00000000 ........r. ..... Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000290: 00000000 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000002a0: 00000000 00000000 00000000 000fff01 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000002b0: 00000000 00000000 001f0000 0000001f ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000002c0: 00000000 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000002d0: 00000000 04000172 00000000 00000000 ....r........... Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000002e0: 00000000 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000002f0: 00000000 00000000 000fff01 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000300: 00000000 001f0000 0000001f 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000310: 00000000 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000320: 04000172 00000000 00000000 00000000 r............... Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000330: 00000000 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000340: 00000000 000fff01 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000350: 001f0000 0000001f 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000360: 00000000 00000000 00000000 04000172 ............r... Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000370: 00000000 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000380: 00000000 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000390: 000fff01 00000000 00000001 001f0000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000003a0: 0000001f 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000003b0: 00000000 00000000 00200172 00000006 ........r. ..... Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000003c0: 00000000 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000003d0: 00000000 00000000 3806f400 f206f333 ...........83... Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000003e0: 00000006 00000000 001f0000 0000001f ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000003f0: 00000000 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000400: 00000000 04000172 00000000 00000000 ....r........... Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000410: 00000000 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000420: 00000000 00000000 000fff01 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000430: 00000000 001f0000 0000001f 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000440: 00000000 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000450: 04000172 00000000 00000000 00000000 r............... Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000460: 00000000 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000470: 00000000 000fff01 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000480: 001f0000 0000001f 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000490: 00000000 00000000 00000000 04000172 ............r... Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000004a0: 00000000 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000004b0: 00000000 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000004c0: 000fff01 00000000 00000000 001f0000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000004d0: 0000001f 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000004e0: 00000000 00000000 04200172 00000000 ........r. ..... Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000004f0: 00000000 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000500: 00000000 00000000 00000000 000fff01 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000510: 00000000 00000000 001f0000 0000001f ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000520: 00000000 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000530: 00000000 04000172 00000000 00000000 ....r........... Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000540: 00000000 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000550: 00000000 00000000 000fff01 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000560: 00000000 001f0000 0000001f 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000570: 00000000 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000580: 04000172 00000000 00000000 00000000 r............... Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000590: 00000000 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000005a0: 00000000 000fff01 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000005b0: 001f0000 0000001f 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000005c0: 00000000 00000000 00000000 04000172 ............r... Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000005d0: 00000000 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000005e0: 00000000 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000005f0: 000fff01 00000000 00000000 001f0000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000600: 0000001f 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000610: 00000000 00000000 00200172 00000000 ........r. ..... Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000620: 00000000 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000630: 00000000 00000000 00000000 000fff01 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000640: 00000000 00000000 001f0000 0000001f ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000650: 00000000 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000660: 00000000 04000172 00000000 00000000 ....r........... Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000670: 00000000 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000680: 00000000 00000000 000fff01 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000690: 00000000 001f0000 0000001f 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000006a0: 00000000 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000006b0: 04000172 00000000 00000000 00000000 r............... Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000006c0: 00000000 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000006d0: 00000000 000fff01 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000006e0: 001f0000 0000001f 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000006f0: 00000000 00000000 00000000 04000172 ............r... Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000700: 00000000 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000710: 00000000 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000720: 000fff01 00000000 00000002 001f0000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000730: 0000001f 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000740: 00000000 00000000 00200172 00000e96 ........r. ..... Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000750: 00000000 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000760: 00000000 00000000 3804a300 e204a233 ...........83... Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000770: 00000009 00000000 001f0000 0000001f ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000780: 00000000 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000790: 00000000 04000172 00000000 00000000 ....r........... Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000007a0: 00000000 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000007b0: 00000000 00000000 000fff01 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000007c0: 00000000 001f0000 0000001f 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000007d0: 00000000 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000007e0: 04000172 00000000 00000000 00000000 r............... Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000007f0: 00000000 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000800: 00000000 000fff01 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000810: 001f0000 0000001f 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000820: 00000000 00000000 00000000 04000172 ............r... Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000830: 00000000 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000840: 00000000 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000850: 000fff01 00000000 00000001 001f0000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000860: 0000001f 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000870: 00000000 00000000 00200172 00000006 ........r. ..... Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000880: 00000000 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000890: 00000000 00000000 38001600 ed001533 ...........83... Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000008a0: 00000000 00000000 001f0000 0000001f ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000008b0: 00000000 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000008c0: 00000000 04000172 00000000 00000000 ....r........... Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000008d0: 00000000 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000008e0: 00000000 00000000 000fff01 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000008f0: 00000000 001f0000 0000001f 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000900: 00000000 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000910: 04000172 00000000 00000000 00000000 r............... Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000920: 00000000 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000930: 00000000 000fff01 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000940: 001f0000 0000001f 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000950: 00000000 00000000 00000000 04000172 ............r... Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000960: 00000000 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000970: 00000000 00000000 00000000 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000980: 000fff01 00000000 9c000000 00333808 .............83. Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000990: 00400000 00000100 00000000 00000000 ..@............. Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000009a0: 00000000 02450000 01069000 00203985 ......E......9 . Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000009b0: 40000000 00000000 00020000 00004020 ...@........ @.. Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000009c0: 00000000 00000000 039af780 00000000 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000009d0: deadbeef deadbeef deadbeef deadbeef ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000009e0: deadbeef deadbeef deadbeef deadbeef ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000009f0: deadbeef deadbeef deadbeef deadbeef ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: Error 1, type: fatal Apr 17 08:22:46 unraid kernel: [Hardware Error]: section_type: Firmware Error Record Reference Apr 17 08:22:46 unraid kernel: [Hardware Error]: Firmware Error Record Type: SOC Firmware Error Record Type2 Apr 17 08:22:46 unraid kernel: [Hardware Error]: Revision: 2 Apr 17 08:22:46 unraid kernel: [Hardware Error]: Record Identifier: 8f87f311-c998-4d9e-a0c4-6065518c4f6d Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000000: 11037101 00000080 00000000 fe0139f0 .q...........9.. Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000010: 00000000 00000011 0500020e ececa1a5 ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000020: 00000800 01002203 ed13d718 0000200e ....."....... .. Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000030: edae2847 0000200f edae2969 c7e00000 G(... ..i)...... Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000040: 00000001 07c40800 017bf839 00000111 ........9.{..... Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000050: 0500020e edb13302 00000000 00000000 .....3.......... Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000060: 07000000 0079f839 00000211 0500020e ....9.y......... Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000070: edb13618 c7e00000 00000001 06000000 .6.............. Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000080: 015bf831 00000311 0500020e edb1393d 1.[.........=9.. Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000090: 000000e0 01002009 edb140c9 0000200c ..... ...@... .. Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000000a0: edb28676 0000200d edb69e3b 00002012 v.... ..;.... .. Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000000b0: edb6d493 00002806 edc8e7cf 0000280e .....(.......(.. Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000000c0: edc8e8ed 0000280f edc8e9e9 0000280e .....(.......(.. Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000000d0: edc8eafc 0000280f edc8ebf8 00002810 .....(.......(.. Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000000e0: edc8ed1b 0000280e edc8ef4a 0000280f .....(..J....(.. Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000000f0: edc8f046 0000280e edc8f159 0000280f F....(..Y....(.. Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000100: edc8f255 00002810 edc8f378 0000280e U....(..x....(.. Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000110: edc8f569 0000280f edc8f665 0000280e i....(..e....(.. Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000120: edc8f778 0000280f edc8f874 00002810 x....(..t....(.. Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000130: edc8f997 0000280e edc8fb88 0000280f .....(.......(.. Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000140: edc8fc84 0000280e edc8fd97 0000280f .....(.......(.. Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000150: edc8fe93 00002810 edc8ffb6 0000280e .....(.......(.. Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000160: edc901a7 0000280f edc902a3 0000280e .....(.......(.. Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000170: edc903b6 0000280f edc904b2 00002810 .....(.......(.. Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000180: edc905d5 0000280e edc9071f 0000280f .....(.......(.. Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000190: edc9081b 0000280e edc9098b 0000280f .....(.......(.. Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000001a0: edc90a87 0000280e edc90b9a 0000280f .....(.......(.. Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000001b0: edc90c96 00002810 edc90db9 0000280e .....(.......(.. Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000001c0: edc90f03 0000280f edc90fff 00002807 .....(.......(.. Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000001d0: edc91154 00002013 edc913bd 00000002 T.... .......... Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000001e0: 01002000 56fd8104 00002014 56fd8273 . .....V. ..s..V Apr 17 08:22:46 unraid kernel: [Hardware Error]: 000001f0: c7e00000 00000001 07000000 005bf839 ............9.[. Apr 17 08:22:46 unraid kernel: [Hardware Error]: Error 2, type: fatal Apr 17 08:22:46 unraid kernel: [Hardware Error]: section_type: Firmware Error Record Reference Apr 17 08:22:46 unraid kernel: [Hardware Error]: Firmware Error Record Type: SOC Firmware Error Record Type2 Apr 17 08:22:46 unraid kernel: [Hardware Error]: Revision: 2 Apr 17 08:22:46 unraid kernel: [Hardware Error]: Record Identifier: 8f87f311-c998-4d9e-a0c4-6065518c4f6d Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000000: 17037101 0000000a 00001802 00000002 .q.............. Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000010: 00000000 00000002 00000000 deadbeef ................ Apr 17 08:22:46 unraid kernel: [Hardware Error]: 00000020: deadbeef deadbeef ........ which firmware is responsible for the errors? how can i go about analyzing this further? and why can't i start memtest?` unraid-diagnostics-20220417-0910.zip syslog (2)

Hey Guys, my unraid system just crashed again. syslog is attached. last entries before hard restart at 17:33: Apr 10 16:50:25 unraid kernel: vfio-pci 0000:05:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=none Apr 10 16:50:25 unraid kernel: br0: port 5(vnet13) entered blocking state Apr 10 16:50:25 unraid kernel: br0: port 5(vnet13) entered disabled state Apr 10 16:50:25 unraid kernel: device vnet13 entered promiscuous mode Apr 10 16:50:25 unraid kernel: br0: port 5(vnet13) entered blocking state Apr 10 16:50:25 unraid kernel: br0: port 5(vnet13) entered forwarding state Apr 10 16:50:27 unraid avahi-daemon[4986]: Joining mDNS multicast group on interface vnet13.IPv6 with address fe80::fc54:ff:fefb:bbf1. Apr 10 16:50:27 unraid avahi-daemon[4986]: New relevant interface vnet13.IPv6 for mDNS. Apr 10 16:50:27 unraid avahi-daemon[4986]: Registering new address record for fe80::fc54:ff:fefb:bbf1 on vnet13.*. Apr 10 16:50:36 unraid kernel: vfio-pci 0000:05:00.0: vfio_ecap_init: hiding ecap 0x19@0x900 Apr 10 16:50:37 unraid kernel: x86/split lock detection: #AC: CPU 0/KVM/30747 took a split_lock trap at address: 0x7fe014dd Apr 10 17:02:16 unraid kernel: x86/split lock detection: #AC: CPU 0/KVM/31922 took a split_lock trap at address: 0xfffff801128d7b23 Apr 10 17:26:00 unraid kernel: x86/split lock detection: #AC: CPU 0/KVM/31922 took a split_lock trap at address: 0xfffff801128d7b23 Apr 10 17:33:20 unraid kernel: Linux version 5.15.27-Unraid (root@Develop) (gcc (GCC) 11.2.0, GNU ld version 2.37-slack15) #1 SMP Wed Mar 9 11:15:51 PST 2022 Some help would be highly appreciated. Thanks! syslog (1) unraid-diagnostics-20220410-1739.zip

Hi Guys, In case of a power loss or crash,my VM Service stays offline. Since I am running home assistant in an unraid vm it is very important for this VM to come back to life asap. Currently I have to restart the service manually after the system has rebooted. Could you please check my diag and tell me what to change? Thanks very much! unraid-diagnostics-20220405-1330.zip

Hi Guys, my unraid server keeps crashing about once every week and I don't know why and how to solve it. The last syslog entry before the crash is: Apr 5 10:02:58 unraid kernel: vfio-pci 0000:05:00.0: vgaarb: changed VGA decodes: olddecodes=none,decodes=io+mem:owns=none Apr 5 10:02:58 unraid kernel: br0: port 3(vnet27) entered blocking state Apr 5 10:02:58 unraid kernel: br0: port 3(vnet27) entered disabled state Apr 5 10:02:58 unraid kernel: device vnet27 entered promiscuous mode Apr 5 10:02:58 unraid kernel: br0: port 3(vnet27) entered blocking state Apr 5 10:02:58 unraid kernel: br0: port 3(vnet27) entered forwarding state Apr 5 10:02:58 unraid kernel: vfio-pci 0000:01:00.0: vgaarb: changed VGA decodes: olddecodes=none,decodes=io+mem:owns=none Apr 5 10:02:58 unraid kernel: br0: port 4(vnet28) entered blocking state Apr 5 10:02:58 unraid kernel: br0: port 4(vnet28) entered disabled state Apr 5 10:02:58 unraid kernel: device vnet28 entered promiscuous mode Apr 5 10:02:58 unraid kernel: br0: port 4(vnet28) entered blocking state Apr 5 10:02:58 unraid kernel: br0: port 4(vnet28) entered forwarding state Apr 5 10:02:59 unraid kernel: vfio-pci 0000:05:00.0: vfio_ecap_init: hiding ecap 0x19@0x900 Apr 5 10:02:59 unraid kernel: vfio-pci 0000:05:00.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0x0000 Apr 5 10:02:59 unraid kernel: vfio-pci 0000:01:00.0: vfio_ecap_init: hiding ecap 0x1e@0x258 Apr 5 10:02:59 unraid kernel: vfio-pci 0000:01:00.0: vfio_ecap_init: hiding ecap 0x19@0x900 Apr 5 10:02:59 unraid kernel: vfio-pci 0000:01:00.0: vfio_ecap_init: hiding ecap 0x26@0xc1c Apr 5 10:02:59 unraid kernel: vfio-pci 0000:01:00.0: vfio_ecap_init: hiding ecap 0x27@0xd00 Apr 5 10:02:59 unraid kernel: vfio-pci 0000:01:00.0: vfio_ecap_init: hiding ecap 0x25@0xe00 Apr 5 10:02:59 unraid kernel: vfio-pci 0000:01:00.1: vfio_ecap_init: hiding ecap 0x25@0x160 Apr 5 10:03:00 unraid avahi-daemon[5153]: Joining mDNS multicast group on interface vnet27.IPv6 with address fe80::fc54:ff:fefb:bbf1. Apr 5 10:03:00 unraid avahi-daemon[5153]: New relevant interface vnet27.IPv6 for mDNS. Apr 5 10:03:00 unraid avahi-daemon[5153]: Registering new address record for fe80::fc54:ff:fefb:bbf1 on vnet27.*. Apr 5 10:03:00 unraid avahi-daemon[5153]: Joining mDNS multicast group on interface vnet28.IPv6 with address fe80::fc54:ff:fefc:8541. Apr 5 10:03:00 unraid avahi-daemon[5153]: New relevant interface vnet28.IPv6 for mDNS. Apr 5 10:03:00 unraid avahi-daemon[5153]: Registering new address record for fe80::fc54:ff:fefc:8541 on vnet28.*. Apr 5 10:03:01 unraid kernel: x86/split lock detection: #AC: CPU 0/KVM/18504 took a split_lock trap at address: 0x7fe014dd The OS seems to have stopped working since even in my router, the server was not listed as an active network device anymore. I can only hard-power off and restart. Could you please advise what to do? Syslog and diagnostics are attached. Thanks! unraid-diagnostics-20220405-1330.zip syslog

Hi Guys, I cannot access my VMs Tab anymore. It says "Libvirt Service failed to start." The VMs are running though... could someone please look at my diagnostics and syslog an tell me what might be wrong?. I am also suffering frequent crashes(none in log yet) and the problem, that the VM Service won't start up after a power failure. Maybe same root cause? Thanks for your help! unraid-diagnostics-20220401-1435.zip syslog