JorgeB

Disk10 appears to be failing, you can run an extended SMART test to confirm.

Jul 10 19:41:27 HedonistMedia kernel: BTRFS: device fsid 735f5a28-a992-4be9-b621-47603518b082 devid 1 transid 202666812 /dev/sdc1 scanned by udevd (1059) Jul 10 19:41:27 HedonistMedia kernel: BTRFS: device fsid 735f5a28-a992-4be9-b621-47603518b082 devid 2 transid 202683889 /dev/sdf1 scanned by udevd (1179) Jul 10 19:41:27 HedonistMedia kernel: BTRFS: device fsid 735f5a28-a992-4be9-b621-47603518b082 devid 3 transid 202683889 /dev/sdj1 scanned by udevd (1200) I assume the old deceive is sdc? Did you replace or add new device and the remove the other one? Either way something went wrong since the old device is still part of the filesystem, fiscally disconnect the old device (I'd like to avoid wiping it for now) and if the pool mounts, if it doesn't post new diags

One of the devices has been dropping offline, run a scrub to sync the pool and see here for more info and better pool monitoring.

If it boots with a new config means something in the old one is causing the problem, you copy parts of it until you find the problem or just reconfigure the server.

You can try leaving just the SSDs there, I believe heavy i/o makes this issue worse, so probably the less devices the less chance of seeing this.

Nothing obvious there, please post the diagnostics so we can see the hardware used.

Possibly

Stop that command, stop the array, unassign that disk, start the array and see if Unraid can still emulate it.

Yes. Yes, you'll lose TRIM support on the SSDs though.

You can delete the older one, likely the one from disk2.

No, disk4 is on the onboard SATA ports, don't use those for anything, or like mentioned see if a BIOS update helps.

Problem with the onboard SATA controller, this is quite common with some Ryzen servers, look for a BIOS update but best bet is to use an add-on controller.

As already mentioned that won't affect an Intel NIC, it can't help or hurt your issue.

First create a new flash drive install and restore just the config folder from the backup.

Jul 9 21:21:13 HMS emhttpd: stale configuration This means the GUI is out of sync with the array status, rebuild is still going on and array is functioning normally, not yet clear what sometimes causes this issue, make sure there are no multiple browser windows opened on the GUI, don't forget phones, tables, etc, then close all windows, clear browser cache and open a new window.

Yes, or try first with a new flash and trial key, just see if the issues are gone.

Possibly Unraid will complain of invalid partitions, you'll need to try, if that's the case there's a way to fix it, assuming parity is valid, but it will require rebuilding all the disks. It should detect the new NIC(s) and use that, but if there are issues just delete network.cfg and network-rules.cfg Convert pool to raid1, remove one of the devices, add 500GB device, remove other device.

See if this applies to you, if yes, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right)), or see below for more info.: https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-address-to-docker-containers/ See also here: https://forums.unraid.net/bug-reports/stable-releases/690691-kernel-panic-due-to-netfilter-nf_nat_setup_info-docker-static-ip-macvlan-r1356/

If nomodeset helps just add that to syslinux.cfg, click on the flash drive and scroll down to "syslinux configuration": Save and reboot.

NIC is being passed-through to the VM: -device vfio-pci,host=0000:05:00.0,id=hostdev0,bus=pci.0,addr=0x8 \ 05:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 11)

Looks more like a flash drive problem, also make sure it's using a USB 2.0 port.

Those strange errors are back, you might have a flash drive or install problem, try recreating it.

That will never bring a disabled device online, once a disk is disabled it needs to be rebuilt.

https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself

Possibly related to this? https://forums.unraid.net/topic/3531-looking-for-better-ideas-how-how-to-sleepsuspend-my-unraid-box/?do=findComment&comment=1128998