unrais

Yea I'd love this too. The guide is just a bit confusing lol

I'm not quite sure what's causing it, but I've added the diagnostics after the last reboot, as well as the syslog server csv export from the whole of today up until the reboot event. Hopefully this is enough to at least give a direction? I don't want to sway opinions on what it might be, but I do have a feeling it might be to do with drives shutting down due to overheating. I got the LincStation S1 due to my tower system being RMA'd, and I thought this would be a good temp/possible permenant solution. So I've migrated my 4x HDDs (Seagate Exos) and 2x NVME SSDs for cache over to the S1. It works fine mostly, but it does seem to be quite warm all the time and their cooling solution doesn't seem to be living up to expectations. I THINK (can't be certain) that the reboots have happened mostly when all drives are active, such as when a parity check is happening, since that runs all drives at once and drives often get to an uncomfortable ~45 degrees. But hopefully the logs reveal more? All_2025-9-7-13_13_13.csv unrais-diagnostics-20250907-1303.zip

Yep, after testing a new set of ram, it still doesnt work, which leads to a logical conclusion that it's either the CPU or MoBo now, so it's now being RMA'd. Very annoying that there's been so much down-time, but I have just ordered a LincPlus LincStation S1, so hopefully that'll fill in the gap and potentially act as my main unraid system while the system I'm RMA-ing will be more for the 'grunt' work, such as background encoding, gen AI etc. Either that or the S1 will just become a nice 'backup' system to use if the main system fails again. So the silverlining is I get something new to tinker with lol.

@JorgeB I mean RAM vs CPU, I'm hoping it's just the RAM, but what would be the chances that all 4 RAM turn bad? There was zero wrong with the system (and the ram) before I tried to upgrade the bios. So it's got to have been caused by something in that moment too, as I'd successfully rebooted, shutdown etc without seeing any errors until then.

Hey, yes I have, but still no luck. apologies I missed that off the list, I'll update the main post now.

Hi all, After around 1 year of no issues since a failed RAM problem back in Oct 2024, I’ve run into a major issue after updating the BIOS firmware on my main PC that runs Unraid. The BIOS update itself completed fine, but since then Unraid has become unstable and won’t boot properly or operate really at all. Hardware: Gigabyte Z790 Gaming X AX (rev 1.1, BIOS F11d 08/07/2024) Intel i9-14900K 128 GB RAM (4×32 GB DDR5, tested sticks individually) RTX 4070 Ti Super (GPU passthrough not in use for host display) Running Unraid from USB What I’ve tried so far: Restored my original Unraid flash drive from a backup Flashed multiple new USB drives (different brands/ports) with both my backup and fresh Unraid installs Reset BIOS to previous settings that I had before when unraid was running fine (CSM, virtualization, etc.) Restoring the bios version I was on previously. Also tried “Optimized Defaults” Tested each RAM stick individually No matter what, I keep seeing errors like these: SQUASHFS error: Failed to read block 0x1b8736c: -5 SQUASHFS error: xz decompression failed, data probably corrupt SQUASHFS error: Unable to read fragment cache entry [159fa0a4] usb 1-11.3: device descriptor read/64, error -71 usb 1-11-port3: Cannot enable. Maybe the USB cable is bad? /etc/rc.d/rc.runlog: line 11: 1819 Bus error "Se"&> /dev/null rc.rsyslogd: Syslog server daemon…..Failed. kvm_amd: CPU 14 isn't AMD or Hygon mount: /sys/firmuare/efi/efivars: unknown filesystem type 'efivarfs'. dmesg(1) may have more information after failed mount system call. r8169 0000:05:00.0 eth0: Link is Down It looks like the kernel is struggling to read from the bzroot/bzimage (SQUASHFS errors), and there are repeated USB errors too. During startup, I also noticed network failures while the system attempts to download and install plugins. I’ve tried multiple flash drives and ports, so I’m not sure if it’s related to BIOS USB initialization changes, RAM issues, or something else introduced by the BIOS update. I’ve attached a few diagnostics zips from the various failed attempts to get it back up and working Would really appreciate any help narrowing this down. Is it possible the new BIOS changed something critical for Unraid boot (e.g., USB controller handling, ACPI tables, IOMMU, etc.)? I know that it kind of points towards bad RAM, but I just find it hard to believe that all 4 RAM sticks would fail at the same time, so it just seems a bit odd. Needless to say, I have ordered some new ram, but as that's not coming for a day or two, it'd be great if someone had more insight into this. Thanks in advance! unrais-diagnostics-20250826-1411.zip tower-diagnostics-20250826-1316.zip

Yep I'm having the same exact problem here too RTX 4070Ti. It's quite frustrating.

Hey, I just submitted a pull request that implements this feature: https://github.com/VladoPortos/folder.view/pull/7

The only plugins I have installed are: Appdata backup beta Community applications Compose manager Dynamix file manager Folder view Intel GPU TOP Nvidia Driver RTL8125 Drivers Unraid Connect User Scripts Besides that everything else is inside docker containers & the Unraid OS itself is a fresh install (only carried over my license and appdata from the old USB).

I don't think I've installed any out of the ordinary plugin, and as far as I know it's unlikely for docker containers to cause this kind of issue (outside of themselves), is that right? I've attached a diagnostics export I've just made if you could perhaps shed some light on it please? unrais-diagnostics-20240913-0946.zip

Hey, so after testing the ram (trying to run with just one stick at a time) and still having issues, I bit the bullet and bought some new ram. Running like a charm now. Thank you! However, I have noticed this error appearing in the syslog Unrais kernel: traps: light-locker[29184] trap int3 ip:149b64f85ca7 sp:7ffd806a5550 error:0 in libglib-2.0.so.0.6600.8[149b64f49000+89000] Is there any way to fix that?

Is it also possible that the usb could be causing it? If not then I'll jump straight to the RAM but otherwise I'll try replacing the USB firstly.

Hi, I'm getting a bunch of errors and crashes lately. I've not changed any hardware in the system, and the only change has been upgrading to 6.12.13 (though of course this is less likely to be the problem), and getting a UPS. What's happening? Seems to crash every night. While I can ssh into it and enter the powerdown command, it looks like it begins the process, but then never succeeds. I've suspected that this might be due to docker in some way, but not been able to diagnose. Since yesterday I've started to get 'docker service failed to start' upon rebooting too, with 'SQUASHFS error: xz decompression failed, data probably corrupt'. I deleted and re-built the docker image folder, which fixed it, until I rebooted again and it reported 'docker service failed to start' again. I then tried another way by stopping the array, erasing the mirror of the cache drive and starting the array again, which fixed it (without having to re-build). It crashed again last night, so I had to do a hard reboot, and once again I was greeted with 'docker service failed to start'. So I tried the start/stop of the array again, but this time I couldn't get it to start again, and the system fully froze up. I've also been seeing a lot of segfault 139 errors both inside docker containers and directly in unraid cli (when testing something), which I never used to get before. What I've tried doing to mitigate: Thinking it was a clash of schedules causing the system to crash, I disabled all schedules that weren't totally necessary (docker auto update etc) and ensured the other schedules didn't overlap at all. I ran memtest which didn't report any errors. Thinking it might be some other form of hardware issue, I booted directly into windows and tested a few things there without issue (one of which being one of the things causing a lot of segfault 139 errors in unraid). I considered changing the usb, but after I got it working yesterday, I figured it must have been something else, though now of course I do need to try and actually change it. What I've not been able to try yet (due to it crashing and now at work) Adding '--no-healthcheck' to the plex container (it could already be there, I can't remember), just as a test. entering 'echo "options i915 enable_dc=0" >> /boot/config/modprobe.d/i915.conf' in cli. Again, just as a test. I've attached my Unraid syslog that my Synology NAS captured. It'd be great if someone smarter than me (not difficult!) could take a look at the log to see if there's a better indication as to what the problem is? All_2024-9-10-10_3_11.html

I've followed the video guide for this, and I can get into windows etc, however, it says that windows os isn't 'activated'. I've copied the UUID etc over as per the guide, but no dice. Here's a mini breakdown of my hardware, in case it's helpful: Gigabyte Z790 Gaming X AX motherboard 64GB ram RTX 4070 Ti Super 2TB 990 Pro nvme (this has windows installed on it) And below is the XML for the VM. Does anyone know what might be the issue? <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Win11 BareMetal</name> <uuid>REDACTED</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 11" icon="windows11.png" os="windowstpm"/> </metadata> <memory unit='KiB'>16777216</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> <source type='memfd'/> <access mode='shared'/> </memoryBacking> <vcpu placement='static'>22</vcpu> <cputune> <vcpupin vcpu='0' cpuset='2'/> <vcpupin vcpu='1' cpuset='3'/> <vcpupin vcpu='2' cpuset='4'/> <vcpupin vcpu='3' cpuset='5'/> <vcpupin vcpu='4' cpuset='6'/> <vcpupin vcpu='5' cpuset='7'/> <vcpupin vcpu='6' cpuset='8'/> <vcpupin vcpu='7' cpuset='9'/> <vcpupin vcpu='8' cpuset='10'/> <vcpupin vcpu='9' cpuset='11'/> <vcpupin vcpu='10' cpuset='12'/> <vcpupin vcpu='11' cpuset='13'/> <vcpupin vcpu='12' cpuset='14'/> <vcpupin vcpu='13' cpuset='15'/> <vcpupin vcpu='14' cpuset='16'/> <vcpupin vcpu='15' cpuset='17'/> <vcpupin vcpu='16' cpuset='18'/> <vcpupin vcpu='17' cpuset='19'/> <vcpupin vcpu='18' cpuset='24'/> <vcpupin vcpu='19' cpuset='25'/> <vcpupin vcpu='20' cpuset='26'/> <vcpupin vcpu='21' cpuset='27'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-7.2'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/03560274-043c-05b6-e106-a20700080009_VARS-pure-efi.fd</nvram> <boot dev='hd'/> </os> <features> <acpi/> <apic/> <hyperv mode='custom'> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='11' threads='2'/> <cache mode='passthrough'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/virtio-win-0.1.248-1.iso'/> <target dev='hdb' bus='ide'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'/> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <filesystem type='mount' accessmode='passthrough'> <driver type='virtiofs' queue='1024'/> <binary path='/usr/libexec/virtiofsd' xattr='on'> <cache mode='always'/> <sandbox mode='chroot'/> </binary> <source dir='/mnt/user/data'/> <target dir='data'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </filesystem> <interface type='bridge'> <mac address='52:54:00:0e:2e:5a'/> <source bridge='br0'/> <model type='e1000'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <audio id='1' type='none'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </hostdev> <memballoon model='none'/> </devices> </domain>

Hey, I love FileFlows, I've been using it on windows for a while, but I've just switched over to Unraid, and I'm a bit lost on how the 'dockermods' work, how to make my own etc. Eg, I'd like to use it with Faster-Whisper-XXL which has a linux version, but... I've just no idea how lol. I'm not completely wet behind the ears when it comes to the regular docker container stuff, but having been on windows for so long, I'm a bit stumped here. Other's I'd like to figure out how to add are: HandBrake, which has a 'function' preset available in FileFlows, but there isn't a dockermod for it. SubtitleEdit, which is available in Linux via 'wine' apparently. Any help on this would be appreciated, I've looked for tutorials etc on it, but I've not come across anything clear enough.