Mati369

Here’s what happened: To eliminate variables, I detached hardware – removed all PCI cards and disconnected USB devices except for a keyboard. I kept the HDDs and NVMe drives connected. I ran memtest86 overnight. The first pass completed successfully, so I left it running. By morning, I was greeted with a black screen and no response from the server. IPMI was still functional, but all sensors showed no connections, and I couldn’t restart the server through IPMI (no response at all). This was frustrating, so I decided to check for a BIOS update for the X470D4U motherboard. I was previously running version 4.26 (6/21/2022) and found a newer version, 4.29A (4/11/2024). Here’s what I did: Powered off the PSU manually, back on, flashed the new 4.29A BIOS, and rebooted. Ran memtest86 again. After approximately 8 hours, I was greeted with 4 successful passes and no issues. I booted into unRaid, and so far, no new issues have been flagged by Fix Common Problems. My conclusion for those using the X470D4U with a 5950X: if you’re encountering issues, consider updating to the latest BIOS version. You can find it here: ASRock Rack X470D4U Downloads Big thanks to @Squid for your amazing plugins and all your support! What’s still persisting: I still see the following errors in my logs: Cubus kernel: ffmpeg[26609]: segfault at 152b4f960ee8 ip 0000152b57c921eb sp 00007ffcf0d59200 error 4 in libavformat.so.60.16.100[152b57c0f000+1ce000] likely on CPU 6 (core 6, socket 0) @MowMdown This server is used for video encoding, primarily via Jellyfin (using a GPU for transcode and trickplay) and Immich (also GPU-based). If anyone has insights into this error, I’d greatly appreciate your thoughts.

Hi UnRaiders, I’m reaching out for some help with an issue I’ve encountered. Fix Common Problems has reported an error and suggested I post my diagnostics here. Could someone more knowledgeable take a look to help identify what might be going wrong with my server? I also noticed the following error in the logs: Cubus kernel: ffmpeg[26609]: segfault at 152b4f960ee8 ip 0000152b57c921eb sp 00007ffcf0d59200 error 4 in libavformat.so.60.16.100[152b57c0f000+1ce000] likely on CPU 6 (core 6, socket 0) I’m not sure if this is related to the issue flagged by Fix Common Problems or just a separate occurrence. For context, the server has been running quite stable for the past six months since I upgraded the CPU. I’ve attached the diagnostics file for review. Any insights or guidance would be greatly appreciated. Thanks in advance! cubus-diagnostics-20250120-0956.zip

Hi there, After an unexpected shutdown, one of my nvme cache drives (all my docker files on it) is now labeled as "Unmountable - Unsupported or no filesystem." I've attached the diagnostic files and the SMART report for the disk. I was able to recover some data using the method described here. Thanks a lot for that! Is there any chance I can get the disk up and running again, or is it too far gone? I also was not able to format the disk after I have recovered the data. Thanks for your help! Samsung_SSD_970_EVO_Plus_1TB_S6P7NG0R881945V-20240728-0956.txt cubus-diagnostics-20240728-1003.zip

Danke für deinen Input hier. Ich habe zwischenzeitlich rausgefunden, dass meine Einstellungen in den IOMMU Groups das Problem waren. Nun taucht auch der SkyConnect wie bei dir korrekt auf.

Moin, hat jemand von euch schon den SkyConnect in einem HA Docker zum laufen bekommen? Bei mir scheitert es schon daran das ich ihn unter unraid nicht mal finde mit (fehlende Treiber?) ls -l /dev/serial/by-id /bin/ls: cannot access '/dev/serial/by-id': No such file or directory oder unter lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0781:5571 SanDisk Corp. Cruzer Fit Bus 001 Device 005: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 001 Device 004: ID 046b:ffb0 American Megatrends, Inc. Virtual Ethernet Bus 001 Device 007: ID 046b:ff31 American Megatrends, Inc. Virtual HardDisk Device Bus 001 Device 006: ID 046b:ff20 American Megatrends, Inc. Virtual Cdrom Device Bus 001 Device 003: ID 046b:ff01 American Megatrends, Inc. Virtual Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub und mit ls /dev/tty* /dev/tty /dev/tty13 /dev/tty19 /dev/tty24 /dev/tty3 /dev/tty35 /dev/tty40 /dev/tty46 /dev/tty51 /dev/tty57 /dev/tty62 /dev/tty0 /dev/tty14 /dev/tty2 /dev/tty25 /dev/tty30 /dev/tty36 /dev/tty41 /dev/tty47 /dev/tty52 /dev/tty58 /dev/tty63 /dev/tty1 /dev/tty15 /dev/tty20 /dev/tty26 /dev/tty31 /dev/tty37 /dev/tty42 /dev/tty48 /dev/tty53 /dev/tty59 /dev/tty7 /dev/tty10 /dev/tty16 /dev/tty21 /dev/tty27 /dev/tty32 /dev/tty38 /dev/tty43 /dev/tty49 /dev/tty54 /dev/tty6 /dev/tty8 /dev/tty11 /dev/tty17 /dev/tty22 /dev/tty28 /dev/tty33 /dev/tty39 /dev/tty44 /dev/tty5 /dev/tty55 /dev/tty60 /dev/tty9 /dev/tty12 /dev/tty18 /dev/tty23 /dev/tty29 /dev/tty34 /dev/tty4 /dev/tty45 /dev/tty50 /dev/tty56 /dev/tty61 /dev/ttyS0 finde ich auch kein ttyUSB0 Habt ihr noch andere Ideen? Wegen der möglichen fehlenden Treibern habe ich hier auch schon angefragt.