sonic6

so, i tried another USB slot from the i/o shild and this one works fine: (1) is the Zigbee (2) is my UPS which is connected to the usb slot were the zigbee stick was before i also tried 6.12.4 which is the same. this is from my syslog, when i disconnected and reconnect it: Dec 17 11:09:07 Unraid-1 kernel: usb 1-9: USB disconnect, device number 8 Dec 17 11:09:07 Unraid-1 kernel: cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0 Dec 17 11:09:07 Unraid-1 kernel: cp210x 1-9:1.0: device disconnected Dec 17 11:09:10 Unraid-1 kernel: usb 1-3: new full-speed USB device number 9 using xhci_hcd Dec 17 11:09:44 Unraid-1 kernel: usb 1-3: new full-speed USB device number 10 using xhci_hcd Dec 17 11:09:44 Unraid-1 kernel: usb 1-3: Device not responding to setup address. Dec 17 11:09:44 Unraid-1 kernel: usb 1-3: Device not responding to setup address. Dec 17 11:09:44 Unraid-1 kernel: usb 1-3: device not accepting address 10, error -71 Dec 17 11:09:48 Unraid-1 kernel: usb 1-9: new full-speed USB device number 12 using xhci_hcd Dec 17 11:09:48 Unraid-1 kernel: cp210x 1-9:1.0: cp210x converter detected Dec 17 11:09:48 Unraid-1 kernel: usb 1-9: cp210x converter now attached to ttyUSB0

Hello, after my last reboot, my sonoff zigbee stick isn't working on the usb slots from i/o shield. front usb slots are working. i hope you can help me. unraid-1-diagnostics-20231216-1748.zip

the main reason why people are telling this to you the following: the more people are reporting the, the higher is the chance that this issue will be solved. you are in the same boat with other users. if you all report it at the right place, then the chance that this will be fixed, it muuuuuch higher then it will only reported by a few unraid devs.

okay, just a stupid question... you buy a volkswagen and one of the tires a broken... do you contact volkswagen? i think so. will volkswagen replace the tire? maybe. do they have so... not really. they sell the tire as a part of the cars, but when the tire itself broken by developement volkswagen will say: GTFO and tell Michelin! and now i am out.

that is another huge part of the problem... more that you (and other user) wouldn't report it to the right, but get pissed... next time switch it up and try the following: report it to the right place and stop getting pissed. could help everyone. and please stop repeating your opinion... my eyes are bleeding and you aren't right.

May that is one of the bigger Part of those Problems.

hello, this night i got a "udma crc error" notification from my server. i know this is often because of a bad cable or sata controller. but something in my syslog looked wired: Dec 12 02:03:52 Unraid-1 kernel: ata12.00: exception Emask 0x11 SAct 0x30 SErr 0x0 action 0x6 frozen Dec 12 02:03:52 Unraid-1 kernel: ata12.00: irq_stat 0x48000008, interface fatal error Dec 12 02:03:52 Unraid-1 kernel: ata12.00: failed command: READ FPDMA QUEUED Dec 12 02:03:52 Unraid-1 kernel: ata12.00: cmd 60/00:20:e8:b9:25/01:00:25:05:00/40 tag 4 ncq dma 131072 in Dec 12 02:03:52 Unraid-1 kernel: res 40/00:20:e8:b9:25/00:00:25:05:00/40 Emask 0x10 (ATA bus error) Dec 12 02:03:52 Unraid-1 kernel: ata12.00: status: { DRDY } Dec 12 02:03:52 Unraid-1 kernel: ata12.00: failed command: READ FPDMA QUEUED Dec 12 02:03:52 Unraid-1 kernel: ata12.00: cmd 60/00:28:e8:ba:25/01:00:25:05:00/40 tag 5 ncq dma 131072 in Dec 12 02:03:52 Unraid-1 kernel: res 40/00:20:e8:b9:25/00:00:25:05:00/40 Emask 0x10 (ATA bus error) Dec 12 02:03:52 Unraid-1 kernel: ata12.00: status: { DRDY } Dec 12 02:03:52 Unraid-1 kernel: ata12: hard resetting link Dec 12 02:03:53 Unraid-1 kernel: ata12: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Dec 12 02:03:54 Unraid-1 kernel: ata12.00: configured for UDMA/133 Dec 12 02:03:54 Unraid-1 kernel: sd 12:0:0:0: [sdh] tag#4 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=2s Dec 12 02:03:54 Unraid-1 kernel: sd 12:0:0:0: [sdh] tag#4 Sense Key : 0x5 [current] Dec 12 02:03:54 Unraid-1 kernel: sd 12:0:0:0: [sdh] tag#4 ASC=0x21 ASCQ=0x4 Dec 12 02:03:54 Unraid-1 kernel: sd 12:0:0:0: [sdh] tag#4 CDB: opcode=0x88 88 00 00 00 00 05 25 25 b9 e8 00 00 01 00 00 00 Dec 12 02:03:54 Unraid-1 kernel: I/O error, dev sdh, sector 22098065896 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 2 Dec 12 02:03:54 Unraid-1 kernel: sd 12:0:0:0: [sdh] tag#5 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=2s Dec 12 02:03:54 Unraid-1 kernel: sd 12:0:0:0: [sdh] tag#5 Sense Key : 0x5 [current] Dec 12 02:03:54 Unraid-1 kernel: sd 12:0:0:0: [sdh] tag#5 ASC=0x21 ASCQ=0x4 Dec 12 02:03:54 Unraid-1 kernel: sd 12:0:0:0: [sdh] tag#5 CDB: opcode=0x88 88 00 00 00 00 05 25 25 ba e8 00 00 01 00 00 00 Dec 12 02:03:54 Unraid-1 kernel: I/O error, dev sdh, sector 22098066152 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 2 Dec 12 02:03:54 Unraid-1 kernel: ata12: EH complete Dec 12 02:05:42 Unraid-1 kernel: ata12.00: exception Emask 0x11 SAct 0x30 SErr 0x0 action 0x6 frozen Dec 12 02:05:42 Unraid-1 kernel: ata12.00: irq_stat 0x48000008, interface fatal error Dec 12 02:05:42 Unraid-1 kernel: ata12.00: failed command: READ FPDMA QUEUED Dec 12 02:05:42 Unraid-1 kernel: ata12.00: cmd 60/00:20:c0:f1:bc/01:00:0a:05:00/40 tag 4 ncq dma 131072 in Dec 12 02:05:42 Unraid-1 kernel: res 40/00:20:c0:f1:bc/00:00:0a:05:00/40 Emask 0x10 (ATA bus error) Dec 12 02:05:42 Unraid-1 kernel: ata12.00: status: { DRDY } Dec 12 02:05:42 Unraid-1 kernel: ata12.00: failed command: READ FPDMA QUEUED Dec 12 02:05:42 Unraid-1 kernel: ata12.00: cmd 60/00:28:c0:f2:bc/01:00:0a:05:00/40 tag 5 ncq dma 131072 in Dec 12 02:05:42 Unraid-1 kernel: res 40/00:20:c0:f1:bc/00:00:0a:05:00/40 Emask 0x10 (ATA bus error) Dec 12 02:05:42 Unraid-1 kernel: ata12.00: status: { DRDY } Dec 12 02:05:42 Unraid-1 kernel: ata12: hard resetting link Dec 12 02:05:43 Unraid-1 kernel: ata12: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Dec 12 02:05:44 Unraid-1 kernel: ata12.00: configured for UDMA/133 Dec 12 02:05:44 Unraid-1 kernel: sd 12:0:0:0: [sdh] tag#4 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=1s Dec 12 02:05:44 Unraid-1 kernel: sd 12:0:0:0: [sdh] tag#4 Sense Key : 0x5 [current] Dec 12 02:05:44 Unraid-1 kernel: sd 12:0:0:0: [sdh] tag#4 ASC=0x21 ASCQ=0x4 Dec 12 02:05:44 Unraid-1 kernel: sd 12:0:0:0: [sdh] tag#4 CDB: opcode=0x88 88 00 00 00 00 05 0a bc f1 c0 00 00 01 00 00 00 Dec 12 02:05:44 Unraid-1 kernel: I/O error, dev sdh, sector 21654991296 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 2 Dec 12 02:05:44 Unraid-1 kernel: sd 12:0:0:0: [sdh] tag#5 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=1s Dec 12 02:05:44 Unraid-1 kernel: sd 12:0:0:0: [sdh] tag#5 Sense Key : 0x5 [current] Dec 12 02:05:44 Unraid-1 kernel: sd 12:0:0:0: [sdh] tag#5 ASC=0x21 ASCQ=0x4 Dec 12 02:05:44 Unraid-1 kernel: sd 12:0:0:0: [sdh] tag#5 CDB: opcode=0x88 88 00 00 00 00 05 0a bc f2 c0 00 00 01 00 00 00 Dec 12 02:05:44 Unraid-1 kernel: I/O error, dev sdh, sector 21654991552 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 2 Dec 12 02:05:44 Unraid-1 kernel: ata12: EH complete Dec 12 02:09:07 Unraid-1 emhttpd: read SMART /dev/sde I also attached the diagnostic. sys spec are in my signature. thanks for your help. maybe it is something different? unraid-1-diagnostics-20231212-0659.zip

@DaHol funktioniert denn eine shutdown? Also fährt dein Server runter? Falls ja, sind wir vom gleichen Problem betroffen. Ein Reboot funktioniert seit geraumer Zeit einfach nicht mehr. Ein Shutdown und Boot jedoch schon. Habe dafür keine Lösung finden können. Daher nutze ich seit geraumer Zeit ein einfaches Shutdown und starte denn Server danach per Hand.

schreib mal folgenden Command ins Terminal: lxc-autobackup -h @ich777 hat hier an auch an einen simplen restore per lxc-autobackup Funktion gedacht Falls du aber ein manuell machen möchtest, hätte ich noch die Holzhammer-Methode (not-recommended):

the new update causes email notifications: Nov 25 11:39:11 Unraid-1 emhttpd: spinning down /dev/sdg Nov 25 11:45:01 Unraid-1 crond[1468]: exit status 127 from user root /usr/local/emhttp/plugins/DriveStandbyMonitor/monitor.sh Nov 25 11:45:01 Unraid-1 sSMTP[30712]: Creating SSL connection to host Nov 25 11:45:01 Unraid-1 sSMTP[30712]: SSL connection using TLS_AES_256_GCM_SHA384 Nov 25 11:45:03 Unraid-1 sSMTP[30712]: Sent mail for root@*****.de (221 2.0.0 Bye) uid=0 username=root outbytes=549 diagnostic is attaced unraid-1-syslog-20231125-1052.zip

Diese Hinweis habe ich aus der Github Readme des Entwicklers übernommen. Genau, so in etwa: Quelle: https://github.com/devedse/DeveLanCacheUI_Backend#develancacheui_backend

ja nein, sondern wie in der Template Info auf die Custom User Bride. Hierzu bitte einmal hier einlesen: https://docs.docker.com/network/drivers/ Die Costum User Bride, bzw eine "user defined brdige" (oder custom user network) verhält sich ähnlich wie die "standart Bridge". Der für DIESEN (und auch einige andere) Container entscheidende unterschied ist die DNS Auflösung der Container Hostname ( mehr dazu hier: https://docs.docker.com/network/drivers/bridge/#differences-between-user-defined-bridges-and-the-default-bridge ). Ich weiß, dass man im Frontend Container die IP des Backend angeben kann. Bei mir hat das aber nicht richtig funktioniert, da das Ziel per Hostname Hardcoded (war). Daher habe ich das Template so angelegt (und auch den Hinweis hinterlegt), dass ein Custom User Network genutzt werden sollte.

Genau, weil sich die Beschreibung auf den Einsatz in einem Custom User Network bezieht. Dort wäre dann der Host Port zu nehmen. Da du das ganze aber als Custom User Bride br0 nutzt, gibt es den "Host Port" nicht. Daher wäre dann Port 80 korrekt. Du vermischt halt die Beschreibung und dass du dich nicht an die "empfohlene Vorgabe" gehalten hast Hierzu kann ich nichts sagen, da der Container nicht von mir ist. Ich habe nur das Template für die Nutzung in Unraid zum Bezug über die CA bereitgestellt.

Moin @GhostLeader, ich wüsste persönlich nicht, was ich groß in eine Anleitung schreiben sollte. Es gibt, abgesehen vom Port, noch zwei Dinge die man am Backend anpassen muss: -Netzwerk auf eine Custom User Bride. (Ob br0/eth0 funktioniert, hängt ganz von deinem DNS im LAN ab.) -Pfad zum LANCache Log Ohne einen Log oder was bei dir schiefläuft, kann ich dir nicht sehr gut weiterhelfen. Mein Tipp wäre in erster Linie auf eine Custom User Bride (custom user network) umzustellen.

das ist normal. eines davon ist der Unraid Host selbst (erkennbar an der MAC des NICs), der andere ist der vhost0. geh mal ins unraid terminal und nutze "ip address", dann kannste dort nach den in deiner Unifi aufgeführten MAC Adressen suchen und wirst dahinter steigen.

doch, man sieht ja wo die Ordner gemounted sind im Template. habe deswegen extra den screenshot eingefügt in meiner letzten antwort. freut mich aber, dass es nun klappt.

das Verzeichnis "config" besteht schon: Sprich dein Verzeichniss /homeassistant/ in /mnt/user/appdata entspricht im Container dem Verzeichnis /config/ . Du musst nur folgendes Verzeichnis erstellen: /mnt/user/appdata/homeassistant/custom_zha_quirks/ und schon gehts.

This one works also fine: plexinc/pms-docker:1.32.5.7349-8f4248874

Which Container are you using?

it wasn't intel-gpu-top, it was the latest Plex update. if you are using the LSIO container, try v1.32.5.7349-8f4248874 which worked fine. this problem isn't the web client, it is the latest update. if you are using any other clients or platforms and using the HDR tonemapping, it won't use hardware transcoding: Source:

also the fix common problem plugin reported nearly every trace as a "mac macvlan trace". don't know if that is fixed.

you are right, the first try is the change to ipvlan, but of your hardware need a seperated MAC-Address per device, or had other conflicts with ipvlan, then use "eth0". (i am using a fritzbox, which needs seperated MAC-Addresses per device). with your hardware i would strait go to the "eth0" solution. yes, i would do that. read carefully the changelog. in short: stop docker, disable array autostart, update unraid, reboot unraid, disable bridging in network settings, activate "host access" in docker settings, start docker, check if all br0 container are started. if not all container started, check if they changed from br0 to eth0. if some container disapeared go to "add container" on docker page, choose your template. change from br0 to bridge, start the container, edit the container again and change it to eth0. after all runs activate the array autostart again. now you should check you router etc, because the MAC-Addresses of your container could be change, also there is a second MAC-Address with the same IP address like your unraid host. this is normal.

@JorgeB @bonienl maybe NOW is the time, to mark this as "deprected" as a fix for MACVLAN? Maybe unipin it, and edition the first Post with a hint to update to 6.12.4 instead of using two NICs? There a still users, who are confused by this """"solution"""

try the simplest solution now: read the 6.12.4 changelog, to the manually steps, update to 6.4.12 and use eth0 instead of br0.

@scolcipitato is there a way to see the correct startup order for the docker container? if i remember right it is the position, but without the folders? How can i set up my wished startup order?