davemoreton

Sometimes unraid just blows my mind away! all the apps are back with all the configurations. Thank you for all your help :)

Will they remember all the settings? I had some rather custom bits

Thanks JorgeB Here is the new diags, the rebuild hasn't finished yet. I think the docker image is dead though root@Jeeves:~# mkdir -p /mnt/docker-recovery root@Jeeves:~# btrfs restore -v /mnt/user/system/docker/docker.img /mnt/docker-recovery parent transid verify failed on 44892160 wanted 3065530 found 3065542 parent transid verify failed on 44892160 wanted 3065530 found 3065542 parent transid verify failed on 44892160 wanted 3065530 found 3065542 Ignoring transid failure ERROR: child eb corrupted: parent bytenr=30408704 item=0 parent level=1 child bytenr=44892160 child level=1 ERROR: search for next directory entry failed: -5 root@Jeeves:~# jeeves-diagnostics-20260627-1212.zip

Thanks for that, I have got a little further with this. I think the disk config file got a little messed up, I completely restored the USB boot drive to a few months ago. It's booted with all its drives, wanted to do a rebuild which its currently doing and all network shares are back online etc. The only problem I have at the moment is the docker service won't start :( I will wait for the rebuild to finish first, and then take a look. Thanks

Has anyone got any ideas? I tried a new config last night, which I know is dangerous with a failed drive. But I had a similar thing in the past, and that fixed it. Also the drive that failed is not very old, so I’m a little sceptical. After the new config, it now thinks drive 3 has failed and drive 1 is ok 🤷‍♂️ Still loads of drives in unassigned 😕

Sorry, please find attached the diags. I appreciated (disk1) drive defiantly looks to have failed, I just need some help on disk3 and 4 :) jeeves-diagnostics-20260626-1908.zip

Hi all, I'm hoping someone can point me in the right direction. I was upgrading the second NVMe slot in my server. I had a 256GB NVMe installed for a passthrough VM, which I removed and replaced with a 1TB drive. Since doing that, I've run into a strange issue. Unraid is now reporting one failed drive, and it's asking me to mount three drives. I believe these three drives are all connected to my PCIe SATA controller. My first thought was that the SATA controller had failed, so I replaced it with another one, but I'm seeing exactly the same behaviour. Has anyone come across anything like this before? Could changing the NVMe have altered the PCIe lane allocation or device ordering, causing the SATA controller drives to appear differently? Any ideas would be greatly appreciated. Thanks! jeeves-syslog-20260626-1758.zip

Hi, Hope everyone is doing well. Just changed my motherboard for a Gigabyte B760 DS3H DDR4, very similar to the previous board Gigabyte Z390 D. My PCIE PCE6SAT-A02 sata card is not even detected in the devices in the bios! I have no hard drives. I've kept all the bios settings the same, are my PCIE cards not compatable? Thanks Dave

Hi team, Is anyone else's virtual machine running slow suddenly? I use my VM for gaming and work, and for the last 2 weeks its all of a sudden tanked, not just for gaming but for things like just opening control panel and waiting for the icons to load! Thanks Dave

Hi, Might be a quick easy one? Is there a way to turn CPU performance mode on all the time? I have Tips and Tweaks installed and have it set to performance on normal scaling and power saving on CPU governor, I have no other options! And when I check my CPU, sometimes its power saving: Can it be forced not to? Thanks Dave

Hi, Strangely I just added pcie_aspm=off to the Syslinux and its been stable since. This seems fixed now. Thanks

I do seem to keep getting this now, I reboot and it still show up

Hi bmartino1, Here is the vfio-pci log: Loading config from /boot/config/vfio-pci.cfg BIND=0000:03:00.0|1002:7480 0000:03:00.1|1002:ab30 0000:05:00.0|1b21:2142 0000:0a:00.0|144d:a808--- Processing 0000:03:00.0 1002:7480 Vendor:Device 1002:7480 found at 0000:03:00.0 IOMMU group members (sans bridges): /sys/bus/pci/devices/0000:03:00.0/iommu_group/devices/0000:03:00.0 /sys/bus/pci/devices/0000:03:00.0/iommu_group/devices/0000:03:00.1 Binding... success... Device 1002:7480 at 0000:03:00.0 bound to vfio-pci --- Processing 0000:03:00.1 1002:ab30 Vendor:Device 1002:ab30 found at 0000:03:00.1 IOMMU group members (sans bridges): /sys/bus/pci/devices/0000:03:00.1/iommu_group/devices/0000:03:00.0 /sys/bus/pci/devices/0000:03:00.1/iommu_group/devices/0000:03:00.1 Binding... 0000:03:00.0 already bound to vfio-pci 0000:03:00.1 already bound to vfio-pci success... Device 1002:ab30 at 0000:03:00.1 bound to vfio-pci --- Processing 0000:05:00.0 1b21:2142 Vendor:Device 1b21:2142 found at 0000:05:00.0 IOMMU group members (sans bridges): /sys/bus/pci/devices/0000:05:00.0/iommu_group/devices/0000:05:00.0 Binding... Unbound 0000:05:00.0 from xhci_hcd success... Device 1b21:2142 at 0000:05:00.0 bound to vfio-pci --- Processing 0000:0a:00.0 144d:a808 Vendor:Device 144d:a808 found at 0000:0a:00.0 IOMMU group members (sans bridges): /sys/bus/pci/devices/0000:0a:00.0/iommu_group/devices/0000:0a:00.0 Binding... success... Device 144d:a808 at 0000:0a:00.0 bound to vfio-pci --- Devices listed in /sys/bus/pci/drivers/vfio-pci: lrwxrwxrwx 1 root root 0 Oct 23 05:12 0000:03:00.0 -> ../../../../devices/pci0000:00/0000:00:01.0/0000:01:00.0/0000:02:00.0/0000:03:00.0 lrwxrwxrwx 1 root root 0 Oct 23 05:12 0000:03:00.1 -> ../../../../devices/pci0000:00/0000:00:01.0/0000:01:00.0/0000:02:00.0/0000:03:00.1 lrwxrwxrwx 1 root root 0 Oct 23 05:12 0000:05:00.0 -> ../../../../devices/pci0000:00/0000:00:1b.3/0000:05:00.0 lrwxrwxrwx 1 root root 0 Oct 23 05:12 0000:0a:00.0 -> ../../../../devices/pci0000:00/0000:00:1d.0/0000:0a:00.0 vfio-pci binding complete Loading config from /boot/config/vfio-pci.cfg BIND=0000:03:00.0|1002:7480 0000:03:00.1|1002:ab30 0000:05:00.0|1b21:2142 0000:0a:00.0|144d:a808--- Processing 0000:03:00.0 1002:7480 Vendor:Device 1002:7480 found at 0000:03:00.0 IOMMU group members (sans bridges): /sys/bus/pci/devices/0000:03:00.0/iommu_group/devices/0000:03:00.0 /sys/bus/pci/devices/0000:03:00.0/iommu_group/devices/0000:03:00.1 Binding... success... Device 1002:7480 at 0000:03:00.0 bound to vfio-pci --- Processing 0000:03:00.1 1002:ab30 Vendor:Device 1002:ab30 found at 0000:03:00.1 IOMMU group members (sans bridges): /sys/bus/pci/devices/0000:03:00.1/iommu_group/devices/0000:03:00.0 /sys/bus/pci/devices/0000:03:00.1/iommu_group/devices/0000:03:00.1 Binding... 0000:03:00.0 already bound to vfio-pci 0000:03:00.1 already bound to vfio-pci success... Device 1002:ab30 at 0000:03:00.1 bound to vfio-pci --- Processing 0000:05:00.0 1b21:2142 Vendor:Device 1b21:2142 found at 0000:05:00.0 IOMMU group members (sans bridges): /sys/bus/pci/devices/0000:05:00.0/iommu_group/devices/0000:05:00.0 Binding... Unbound 0000:05:00.0 from xhci_hcd success... Device 1b21:2142 at 0000:05:00.0 bound to vfio-pci --- Processing 0000:0a:00.0 144d:a808 Vendor:Device 144d:a808 found at 0000:0a:00.0 IOMMU group members (sans bridges): /sys/bus/pci/devices/0000:0a:00.0/iommu_group/devices/0000:0a:00.0 Binding... success... Device 144d:a808 at 0000:0a:00.0 bound to vfio-pci --- Devices listed in /sys/bus/pci/drivers/vfio-pci: lrwxrwxrwx 1 root root 0 Oct 23 05:12 0000:03:00.0 -> ../../../../devices/pci0000:00/0000:00:01.0/0000:01:00.0/0000:02:00.0/0000:03:00.0 lrwxrwxrwx 1 root root 0 Oct 23 05:12 0000:03:00.1 -> ../../../../devices/pci0000:00/0000:00:01.0/0000:01:00.0/0000:02:00.0/0000:03:00.1 lrwxrwxrwx 1 root root 0 Oct 23 05:12 0000:05:00.0 -> ../../../../devices/pci0000:00/0000:00:1b.3/0000:05:00.0 lrwxrwxrwx 1 root root 0 Oct 23 05:12 0000:0a:00.0 -> ../../../../devices/pci0000:00/0000:00:1d.0/0000:0a:00.0 vfio-pci binding complete It's currently green and looks like this: Thanks Dave

Hi bmartino1, Thanks for the info, much appreciated. So I checked everything and found all the settings was like your images and the NVME was right at the bottom of the list. Added the command to the syslinx and rebooted but nothing showed up in the VM settings. It looks loke this: default menu.c32 menu title Lime Technology, Inc. prompt 0 timeout 50 label Unraid OS menu default kernel /bzimage append pcie_acs_override=downstream,multifunction isolcpus=2-7,10-15 initrd=/bzroot label Unraid OS GUI Mode kernel /bzimage append pcie_acs_override=downstream,multifunction isolcpus=2-7,10-15 initrd=/bzroot,/bzroot-gui label Unraid OS Safe Mode (no plugins, no GUI) kernel /bzimage append initrd=/bzroot unraidsafemode label Unraid OS GUI Safe Mode (no plugins) kernel /bzimage append initrd=/bzroot,/bzroot-gui unraidsafemode label Memtest86+ kernel /memtest label Unraid OS (GPUs left alone) menu default kernel /bzimage append initrd=/bzroot earlymodules=vfio-pci video=efifb:off,vesafb:off isolcpus=2-7,10-15 gfxpayload=text nvme_core.default_ps_max_latency_us=5500 default_hugepagesz=1G hugepagesz=1G transparent_hugepage=always pci=noaer pcie_aspm=off pcie_acs_override=downstream,multifunction Thank You Dave

Hi, Really hoping someone can help. I have been running a stable server for a long time, and I was running a VM gaming machine on a NVME but not properly passed though. I decided tonight to pass it through and reinstall windows. It went ok, install went fine and installed all the drivers etc. Was just starting to download some games and then the wholes server crashed! Restarted it and done the same thing! so I've left the VM off for now. 20:15:22 Jeeves kernel: pcieport 0000:00:1b.3: AER: Corrected error received: 0000:05:00.0 Oct 22 20:15:22 Jeeves kernel: vfio-pci 0000:05:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Oct 22 20:15:22 Jeeves kernel: vfio-pci 0000:05:00.0: device [1b21:2142] error status/mask=00000001/00002000 Oct 22 20:15:22 Jeeves kernel: vfio-pci 0000:05:00.0: [ 0] RxErr Oct 22 20:15:22 Jeeves kernel: pcieport 0000:00:1b.3: AER: Corrected error received: 0000:05:00.0 I found this in the logs and I've attahced the diags, has anyone seen this? Many thanks Dave jeeves-diagnostics-20241022-2020.zip