MarkAC

Hi everyone, I’m running into a serious issue with my Unraid system failing to boot from the USB key, and I could really use some help. My system has been running fine until recently, but now it won’t boot properly, and I’m seeing a lot of errors related to the USB key /dev/sda). I’ve attached the relevant logs below and would appreciate any advice on how to troubleshoot or recover from this. What Happened I was using my Unraid server as usual when I noticed it wasn’t responding properly. I attempted a reboot via the webGUI, but the system failed to come back up. Now, when I try to boot, it gets stuck with a message prompting me to press ENTER to reboot, and I see a bunch of errors related to the USB key. USB Type: Samsung BAR Plus Logs Here are the key error messages I’m seeing during the boot process: ``` sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA xhci_hcd 0000:0c:00.3: Timeout while waiting for setup device command usb 8-1: device not accepting address 2, error -71 usb 8-1: Device not responding to setup address usb 8-1: device not accepting address 2, error -71 I/O error, dev sda, sector 22563104 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 Buffer I/O error on dev sda, logical block 22963105, async page read Buffer I/O error on dev sda, logical block 22963106, async page read [... several more Buffer I/O errors ...] can't mount: /dev/sda1 is not a valid block device mount: /dev/sda1: press ENTER key to reboot... sd 0:0:0:0: [sda] Synchronizing SCSI cache ``` Additionally, I noticed this message, which might be related: ``` mount: /sys/filesystem/efi/efivars: unknown filesystem type 'efivars' ``` What I’ve Tried 1. I’ve tried rebooting multiple times, but the issue persists. 2. I moved the USB key to a different USB port (another USB 2.0 port), but I’m still seeing the same errors. 3. I haven’t yet tested the USB key on another system to see if it’s readable, but I plan to do that next. Questions - Does this look like a failing USB key, or could it be an issue with the USB port/controller on my motherboard? - Is there a way to recover the USB key, or should I focus on creating a new boot drive? - Could the efivars error be contributing to the issue, or is that a separate problem? Any guidance would be greatly appreciated—I’m a bit stuck and don’t want to lose my array configuration if possible. Thanks in advance for your help!

I have been suffering from a server that falls off the network. After setting up remote sysloging, I can now see the following events. ICMP is the only service that is responding, all other services are hard down. To recover, I have had to hard reset the box each time, which is giving me a checksum error. I'll open another thread on that one. Any ideas what is going on here? 2024-06-26T04:41:02+01:00 Tower flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update 2024-06-26T04:42:02+01:00 Tower flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update 2024-06-26T06:00:04+01:00 Tower flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update 2024-06-26T06:01:04+01:00 Tower flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update 2024-06-26T06:28:29+01:00 Tower kernel: vethc722702: renamed from eth0 2024-06-26T06:28:29+01:00 Tower kernel: docker0: port 9(veth9c1d90d) entered disabled state 2024-06-26T06:28:30+01:00 Tower kernel: docker0: port 9(veth9c1d90d) entered disabled state 2024-06-26T06:28:30+01:00 Tower kernel: device veth9c1d90d left promiscuous mode 2024-06-26T06:28:30+01:00 Tower kernel: docker0: port 9(veth9c1d90d) entered disabled state 2024-06-26T06:30:05+01:00 Tower flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update 2024-06-26T07:14:21+01:00 Tower root: netdata-glibc: Could not download icon https://raw.githubusercontent.com/netdata/netdata/master/web/gui/dashboard/images/ms-icon-310x310.png 2024-06-26T07:14:25+01:00 Tower root: netdata-glibc: Could not download icon https://raw.githubusercontent.com/netdata/netdata/master/web/gui/dashboard/images/ms-icon-310x310.png 2024-06-26T07:16:04+01:00 Tower kernel: docker0: port 9(veth41e0150) entered blocking state 2024-06-26T07:16:04+01:00 Tower kernel: docker0: port 9(veth41e0150) entered disabled state 2024-06-26T07:16:04+01:00 Tower kernel: device veth41e0150 entered promiscuous mode 2024-06-26T07:16:09+01:00 Tower kernel: eth0: renamed from veth8169cc4 2024-06-26T07:16:09+01:00 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth41e0150: link becomes ready 2024-06-26T07:16:09+01:00 Tower kernel: docker0: port 9(veth41e0150) entered blocking state 2024-06-26T07:16:09+01:00 Tower kernel: docker0: port 9(veth41e0150) entered forwarding state 2024-06-26T07:16:10+01:00 Tower root: netdata-glibc: Could not download icon https://raw.githubusercontent.com/netdata/netdata/master/web/gui/dashboard/images/ms-icon-310x310.png 2024-06-26T07:17:48+01:00 Tower root: netdata-glibc: Could not download icon https://raw.githubusercontent.com/netdata/netdata/master/web/gui/dashboard/images/ms-icon-310x310.png 2024-06-26T07:18:16+01:00 Tower kernel: br-6fc325bd4074: port 6(vethaa376b7) entered disabled state 2024-06-26T07:18:16+01:00 Tower kernel: vetheba5e69: renamed from eth0 2024-06-26T07:18:16+01:00 Tower kernel: br-6fc325bd4074: port 6(vethaa376b7) entered disabled state 2024-06-26T07:18:16+01:00 Tower kernel: device vethaa376b7 left promiscuous mode 2024-06-26T07:18:16+01:00 Tower kernel: br-6fc325bd4074: port 6(vethaa376b7) entered disabled state 2024-06-26T07:18:17+01:00 Tower kernel: br-6fc325bd4074: port 6(veth9fb2b96) entered blocking state 2024-06-26T07:18:17+01:00 Tower kernel: br-6fc325bd4074: port 6(veth9fb2b96) entered disabled state 2024-06-26T07:18:17+01:00 Tower kernel: device veth9fb2b96 entered promiscuous mode 2024-06-26T07:18:17+01:00 Tower kernel: br-6fc325bd4074: port 6(veth9fb2b96) entered blocking state 2024-06-26T07:18:17+01:00 Tower kernel: br-6fc325bd4074: port 6(veth9fb2b96) entered forwarding state 2024-06-26T07:18:17+01:00 Tower kernel: br-6fc325bd4074: port 6(veth9fb2b96) entered disabled state 2024-06-26T07:18:17+01:00 Tower kernel: eth0: renamed from veth8236e87 2024-06-26T07:18:17+01:00 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth9fb2b96: link becomes ready 2024-06-26T07:18:17+01:00 Tower kernel: br-6fc325bd4074: port 6(veth9fb2b96) entered blocking state 2024-06-26T07:18:17+01:00 Tower kernel: br-6fc325bd4074: port 6(veth9fb2b96) entered forwarding state 2024-06-26T07:18:22+01:00 Tower root: netdata-glibc: Could not download icon https://raw.githubusercontent.com/netdata/netdata/master/web/gui/dashboard/images/ms-icon-310x310.png 2024-06-26T08:00:19+01:00 Tower kernel: docker0: port 3(vethc24ca4b) entered disabled state 2024-06-26T08:00:19+01:00 Tower kernel: veth6f34836: renamed from eth0 2024-06-26T08:00:19+01:00 Tower kernel: docker0: port 3(vethc24ca4b) entered disabled state 2024-06-26T08:00:19+01:00 Tower kernel: device vethc24ca4b left promiscuous mode 2024-06-26T08:00:19+01:00 Tower kernel: docker0: port 3(vethc24ca4b) entered disabled state 2024-06-26T08:02:30+01:00 Tower kernel: docker0: port 3(vethfea8e76) entered blocking state 2024-06-26T08:02:30+01:00 Tower kernel: docker0: port 3(vethfea8e76) entered disabled state 2024-06-26T08:02:30+01:00 Tower kernel: device vethfea8e76 entered promiscuous mode 2024-06-26T08:02:34+01:00 Tower kernel: eth0: renamed from veth3ad9112 UnRaid.log

Greetings all. Unraid noob here but not so much with the world of tech. Just spun up my first Unriad node and attempting to verify VM setting before taking the leap and buying a license. I am access the GPU via VFIO group. The GPU is a Radeon RX 5600 on the following group. IOMMU group 35:[1002:731f] 0c:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] (rev c1) The game (Dayz) fires up without issue, but then will crash out a few minutes later. I have attached additional unraid logs which clear show resets are occurring on the unraid side. I assume causing the in VM issues. Any thoughts or insights would be great. gamrcrashlogs.txt