EricVin

For anyone looking later, this appears to have been fixed by upgrading to Unraid 7.1.4

Here's the log from the Seagate info command as well: ========================================================================================== SeaChest_Info - Seagate drive utilities - NVMe Enabled Copyright (c) 2014-2024 Seagate Technology LLC and/or its Affiliates, All Rights Reserved SeaChest_Info Version: 2.7.0-8_0_1 X86_64 Build Date: Sep 26 2024 Today: 20250426T111806 User: root ========================================================================================== /dev/sg3 - ST8000VN004-2M2101 - WSD9L1SL - SC60 - ATA Model Number: ST8000VN004-2M2101 Serial Number: WSD9L1SL Firmware Revision: SC60 World Wide Name: 5000C500E635BDED Drive Capacity (TB/TiB): 8.00/7.28 Native Drive Capacity (TB/TiB): 8.00/7.28 Temperature Data: Current Temperature (C): 27 Highest Temperature (C): 51 Lowest Temperature (C): 15 Power On Time: 2 years 45 days Power On Hours: 18600.00 MaxLBA: 15628053167 Native MaxLBA: 15628053167 Logical Sector Size (B): 512 Physical Sector Size (B): 4096 Sector Alignment: 0 Rotation Rate (RPM): 7200 Form Factor: 3.5" Last DST information: Time since last DST (hours): 8913.00 DST Status/Result: 0x0 DST Test run: 0x2 Long Drive Self Test Time: 11 hours 53 minutes Interface speed: Max Speed (Gb/s): 6.0 Negotiated Speed (Gb/s): 6.0 Annualized Workload Rate (TB/yr): 191.25 Total Bytes Read (TB): 369.75 Total Bytes Written (TB): 36.32 Encryption Support: Not Supported Cache Size (MiB): 256.00 Read Look-Ahead: Enabled Write Cache: Enabled Low Current Spinup: Disabled SMART Status: Good ATA Security Information: Supported Firmware Download Support: Full, Segmented, Deferred Specifications Supported: ACS-4 ACS-3 ACS-2 ATA8-ACS ATA/ATAPI-7 ATA/ATAPI-6 ATA/ATAPI-5 SATA 3.3 SATA 3.2 SATA 3.1 SATA 3.0 SATA 2.6 SATA 2.5 SATA II: Extensions SATA 1.0a ATA8-AST Features Supported: Read/Write Multiple Sanitize SATA NCQ [QD=32] SATA Rebuild Assist SATA Software Settings Preservation [Enabled] SATA Device Initiated Power Management Power Management Security SMART [Enabled] 48bit Address Set Max Security Extension PUIS GPL Streaming SMART Self-Test SMART Error Logging DSN AMAC EPC Sense Data Reporting Write-Read-Verify SCT Write Same SCT Error Recovery Control SCT Feature Control SCT Data Tables Host Logging Set Sector Configuration Field Accessible Reliability Metrics (FARM) Seagate In Drive Diagnostics (IDD) Adapter Information: Adapter Type: PCI Vendor ID: 1000h Product ID: 0064h Revision: 0002h

Unfortunately even after these changes I'm still getting sporadic read errors (this time on disk8). Attached new diagnostics, and I've confirmed at EPC and Low Current Spinup are disabled on that disk. walle-diagnostics-20250426-1119.zip

Fantastic, thanks for the link! I just made the changes, and hopefully that'll sort everything out. You're a lifesaver!

For the past several months I've had recurring errors showing up on my Unraid drives. I'm using a LSI 9201-16i card for these drives, and have already tried swapping the mini-SAS cable (which has not resolved the issue). More concerning, recently the drives have begun to drop offline fully, requiring me to manually add them back and do a parity sync/rebuild. Does anyone have any recommendations for the what the next steps for troubleshooting might be for this? I've attached diagnostics from the last failure (errors across two disks, one of which dropped offline) to this post. Just from what I've seen in the logs, there were some errors on the disk that dropped off (disk9) at Apr 22 03:02:22. Here's a line from the log: ``` Apr 22 03:02:22 WallE kernel: md: disk9 read error, sector=9185320888 ``` All smart tests are coming back clean as well. Thanks in advance for any help! walle-diagnostics-20250423-1730.zip

I have a gaming VM on my machine that reliably crashes when I launch certain games. What's especially annoying is that when the VM crashes, it takes Unraid down with it. I've attatched the logs from a reboot and crash, which I obtained by mirroring the syslog to USB though it doesn't appear to show anything from the crash, and the VM XML. My machine has the following motherboard: `ASUSTeK COMPUTER INC. ProArt X670E-CREATOR WIFI`, with an AMD Ryzen 9 7950X and 128GB of RAM. The VM is running off a pass-through NVME SSD with a 3080 passed through as well.. I've run memtest with no issues, and ensured SVM is enabled on my motherboard. Does anyone have any advice on potential issues and/or how to debug this further? <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='2'> <name>Windows 10</name> <uuid>28b6fd51-b5b3-c712-e4bc-7f7adcbfd3f2</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>33554432</memory> <currentMemory unit='KiB'>33554432</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>16</vcpu> <cputune> <vcpupin vcpu='0' cpuset='8'/> <vcpupin vcpu='1' cpuset='24'/> <vcpupin vcpu='2' cpuset='9'/> <vcpupin vcpu='3' cpuset='25'/> <vcpupin vcpu='4' cpuset='10'/> <vcpupin vcpu='5' cpuset='26'/> <vcpupin vcpu='6' cpuset='11'/> <vcpupin vcpu='7' cpuset='27'/> <vcpupin vcpu='8' cpuset='12'/> <vcpupin vcpu='9' cpuset='28'/> <vcpupin vcpu='10' cpuset='13'/> <vcpupin vcpu='11' cpuset='29'/> <vcpupin vcpu='12' cpuset='14'/> <vcpupin vcpu='13' cpuset='30'/> <vcpupin vcpu='14' cpuset='15'/> <vcpupin vcpu='15' cpuset='31'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-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/28b6fd51-b5b3-c712-e4bc-7f7adcbfd3f2_VARS-pure-efi.fd</nvram> <smbios mode='host'/> </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='8' threads='2'/> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> </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/en-us_windows_10_consumer_editions_version_22h2_x64_dvd_8da72ab3.iso' index='2'/> <backingStore/> <target dev='hda' bus='sata'/> <readonly/> <alias name='sata0-0-0'/> <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.248-1.iso' index='1'/> <backingStore/> <target dev='hdb' bus='sata'/> <readonly/> <alias name='sata0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x8'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x9'/> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0xa'/> <alias name='pci.3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0xb'/> <alias name='pci.4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0xc'/> <alias name='pci.5'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x4'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0xd'/> <alias name='pci.6'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x5'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='sata' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb'/> <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'> <alias name='usb'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:be:0b:6f'/> <source bridge='br0'/> <target dev='vnet1'/> <model type='virtio-net'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/1'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/1'> <source path='/dev/pts/1'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-2-Windows 10/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='connected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <alias name='input0'/> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'> <alias name='input1'/> </input> <input type='keyboard' bus='ps2'> <alias name='input2'/> </input> <sound model='ich9'> <alias name='sound0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </sound> <audio id='1' type='none'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </source> <boot order='1'/> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source startupPolicy='optional'> <vendor id='0x046d'/> <product id='0xc534'/> <address bus='7' device='3'/> </source> <alias name='hostdev2'/> <address type='usb' bus='0' port='2'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source startupPolicy='optional'> <vendor id='0x2357'/> <product id='0x0604'/> <address bus='7' device='2'/> </source> <alias name='hostdev3'/> <address type='usb' bus='0' port='3'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain> syslog-previous

Issue happened again this morning. Output of df -h / is: Filesystem Size Used Avail Use% Mounted on rootfs 16G 2.1G 14G 14% / And I've attached another log. unraid_logs_5.txt

Same issue this morning. Output of dh -h / again is: Filesystem Size Used Avail Use% Mounted on rootfs 16G 2.1G 14G 14% / And I attatched another log. @trurl any idea what could be the problem? unraid_logs_4.txt

Happened again this morning: the output of `df -h /` is: Filesystem Size Used Avail Use% Mounted on rootfs 16G 2.1G 14G 14% / And I've attached another log from the crash. unraid_logs_3.txt

Ah, understood! Here's diagnostics after reboot. Thanks! walle-diagnostics-20230213-0725.zip

Unfortunately when the system crashes the diagnostics tool lags forever (also on an nvidia-smi command, like the pagefault), so the only way I could get the syslogs was through the terminal. Please let me know if you have an idea for how to get around this. I'll try that command next time the issue occurs!

Same error this morning, attaching new syslogs. It seems to be consistently happening after the CA Backup/Restore schedule, and that plugin is up to do date. unraid_logs_2.txt

Can do but it reproduces pretty randomly (e.g. sometimes twice in a day, sometimes a month passes), so I'm not really sure if there's a way to to tell if it's linked to plugins long term or just not appearing. Any advice?

Wanted to bump this to see if anyone could take a look at it.

I've been somewhat consistently getting a 500 error on my server, similar to the one in I can restart the webgui using the `/etc/rc.d/rc.php-fpm restart` command, but dockers and vms aren't visible and I can't gracefully restart. I'm also unable to export logs from the WebGUI (stalling forever), but I was able to manually grab the syslog which is attached. It looks like an unhandled pagefault occurred, but I'm not sure why. Any help would be appreciated! unraid_logs.txt