oscnhome

Hello, I am experiencing a persistent issue with the appfeed download on Unraid. Despite following recommendations for resolving internet access issues, including changing the DNS addresses to 208.67.222.222 and 208.67.220.220, the error continues to occur. The specific error I receive is: "Download of appfeed failed." I have tried resetting the modem and router without success. I also checked for any known disruptions to the appfeed server, but nothing seems to resolve the issue. The JSON error reported is: "Syntax error". Below, I am attaching the server diagnostics for reference and a photo as proof of the problem. I appreciate any help or suggestions you can offer to resolve this issue. Thank you! diagnostics-20240430-1800.zip

Hi everyone, I'm reaching out because I've been experiencing frequent crashes with my Unraid setup, and I'm at a bit of a loss about what could be causing them. I've enabled the syslog server to get more insights, and I've attached the syslog file here for reference. Additionally, I've included the diagnostic file in hopes that it might shed some light on the issue. If anyone could take a look and provide any insights or suggestions on what might be going wrong, I would really appreciate it. I'm not sure if it's a hardware issue, a software conflict, or something else entirely. Additionally, I should mention that whenever Unraid crashes, the only way I can get it back up and running is by performing a hard reset. This involves directly cutting off the power to the server and then turning it back on. It's quite concerning as I worry about the potential damage this might cause to my system in the long run. Any insights into why this is happening and how to avoid these hard resets would be incredibly helpful. Any help or guidance would be greatly appreciated. Thanks in advance for your time and help! oscnhome-diagnostics-20240110-1145.zip syslog-192.168.1.3.log

Hello. I have been an Unraid user for approximately 1 year. I've never had more serious problems, however, today I had a terrible surprise. My server didn't modify configuration files on the frontend, so I decided to reboot and see if that fixed it. To my disappointment, unraid no longer booted. On the bare metal preview screen I identify that the flash drive is in read-only state and there is nothing I can do to correct it. I turned off Unraid and removed the UFB flash drive to try a disk check in Windows. Once again the USB is in full Read Only status. Fortunately (I believed) I had made a backup last week, so I tried to put it on another USB drive, as the original was unusable. I then used Unraid USB Creator to generate the flash drive with my backup. However, Unraid did not start! It reported errors again and gave me a login screen with the name "Tower" without the possibility of typing anything using the keyboard. I'm a little desperate. Could anyone help me get through this? I know that the data must be preserved, but my settings, Shares, Dockers, Virtual Machines... I don't know how to recover them.

hello. Thanks for the answer. In fact, the problem was resolved after I upgraded and changed the MotherBoard. Therefore, the statement about the error being related to the bios makes sense. the other point, about the frequent SSH queries... In reality it was an intentional script that I created between two devices: a raspberry pi querying unraid about the status of some containers. I didn't find a better way to do this, just a cron script running every 30 seconds, treating the output to use information from containers in the ON state. what would be the best way? it would be great to have an api to query that exposes just the information you want. Is there any ready solution? thanks!

Hello everyone, I recently found this error message on my unraid. Since I do not use it very often, I did not find information about Mcelog plugin, I decided to come here to ask if anyone can point me to what went wrong and how to solve. oscnhome-diagnostics-20230924-1602.zip

Ok, i realized that was an hardware error. It's ok now.

Hello everyone, I have a problem configuring my Passthrough AMD Radeon RX 5700 XT GPU. I had this configuration working until I needed to change disks for the cache. After that, always the error code 127. Below is my diagnosis and photos with the settings. The Error: System Devices: Some interesting log: Syslinux Configuration: VM XML: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Windows-VM</name> <uuid>5d327ec0-cf51-e93c-6c6e-6b8c6e518162</uuid> <description>- Máquina Virtual Windows com acesso à GPU</description> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>16777216</memory> <currentMemory unit='KiB'>16777216</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='6'/> <vcpupin vcpu='1' cpuset='16'/> <vcpupin vcpu='2' cpuset='7'/> <vcpupin vcpu='3' cpuset='17'/> <vcpupin vcpu='4' cpuset='8'/> <vcpupin vcpu='5' cpuset='18'/> <vcpupin vcpu='6' cpuset='9'/> <vcpupin vcpu='7' cpuset='19'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-7.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/5d327ec0-cf51-e93c-6c6e-6b8c6e518162_VARS-pure-efi.fd</nvram> </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='4' 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='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/Windows-VM/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/Windows_10_x64_Pro.iso'/> <target dev='hda' bus='sata'/> <readonly/> <boot order='2'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/virtio-win-0.1.229-1.iso'/> <target dev='hdb' bus='sata'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0' model='qemu-xhci' ports='15'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <controller type='pci' index='0' model='pci-root'/> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:9a:f0:cf'/> <source bridge='br0'/> <model type='virtio-net'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' 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='tablet' bus='usb'> <address type='usb' bus='0' port='1'/> </input> <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='0x05' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/isos/Navi_10_gpu_amd_5700xt.rom'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x05' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x1'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x00' slot='0x1b' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </hostdev> <memballoon model='none'/> </devices> </domain> The Diagnostic file: oscnhome-diagnostics-20230831-1952.zip Any help would be very welcome. 😰

I just had to drop you a huge THANK YOU for coming to my rescue and helping me out with my Unraid server drama. Your insights were spot on, and I gotta say, I'm super grateful! You made it crystal clear that the disk wasn't dead and buried, just "disabled" because of those pesky write failures. Darn those imperfect cables! And yep, the SMART report was showing some CRC errors, just as you said. So, following your advice, I ran that Extended SMART test, and bam, confirmed the errors. But no worries, I got my hands dirty and checked and reconnected those cables like a champ, making sure they were snug and solid. You're a real lifesaver! Your guidance made all the difference, and I couldn't be happier with the outcome. Thanks again! Cheers.

Dear Unraid Forum Community, Greetings to all members! I hope this message finds you well. I am reaching out to seek assistance with an issue I'm facing with my Unraid server. First and foremost, I want to apologize if anything in this post is not in line with the forum's guidelines or rules as this is my very first time posting here. Here are the specifications of my home server: Motherboard: HUANANZHI X99-8M-F CPU: Xeon E5-2660 v3 Disks: Parity: Seagate IronWolf 4.00 TB 5980 rpm Disk 1: Seagate Skyhawk 4.00 TB 5980 rpm Disk 2: Seagate BarraCuda 3.5 (SMR) 4.00 TB 5400 rpm Cache: Reletech P400 EVO 1TB Unassigned Devices: P3-1TB Flash: Sandisk Ultra Fit Initially, everything was running smoothly, and after going through the trial period of Unraid, I decided to purchase the basic license to continue using the operating system. However, on a certain day, Disk 2 started to exhibit problems. It first disappeared from the RAID array and ended up in the Unassigned Devices section with a "Mount" button to perform the mounting. I found this behavior strange, but I attempted to remount the HDD. Unfortunately, the remounting process failed, and even after restarting the Unraid server, my disk was still not recognized. Suspecting that the issue might be related to the power supply, I replaced the ATX power supply with a better 750W 80 Gold Plus-rated one. However, the problem persisted. Next, I thought it could be a faulty SATA cable. I changed the cable, but the disk still wouldn't function correctly. Finally, in an attempt to resolve the hardware issue, I purchased another HDD (the one listed above for Disk 2). It was recognized normally and worked well for about a month. But now, I find myself facing exactly the same problem with Disk 2 of the RAID array. The puzzling part is that when I access the BIOS, I can see the HDD properly plugged into the corresponding SATA port for Disk 2, and it is recognized there without any issues. At this point, I'm at a loss as to what could be causing this problem. Could it be a motherboard issue? Before investing more money in additional hardware, I decided to turn to this forum and make my first post here in the hopes of finding a solution to my predicament. If any of you have encountered a similar problem or have any suggestions to troubleshoot and resolve this issue, I would be immensely grateful for your help. oscnhome-diagnostics-20230727-0926.zip Thank you all in advance for your time and assistance. Best regards, Oswaldo Neto