artstack

Okay, I've format the disk and now copying from backup. Looks OK so far. Thank you so much for all the helpful recommendation in this forum.

Happy New Year !!! I just back to my server after a long vacation. I did try to follow the recommendation from JorgeB by follow the Step#2. Here is the result I got. Please advise. root@chbvault:/# btrfs restore -v /dev/sdg1 /mnt/disk8/restore parent transid verify failed on 22183936 wanted 519 found 510 parent transid verify failed on 22183936 wanted 519 found 510 parent transid verify failed on 22183936 wanted 519 found 510 Ignoring transid failure ERROR: child eb corrupted: parent bytenr=22052864 item=4 parent level=1 child level=1 Couldn't read chunk tree Could not open root, trying backup super parent transid verify failed on 22183936 wanted 519 found 510 parent transid verify failed on 22183936 wanted 519 found 510 parent transid verify failed on 22183936 wanted 519 found 510 Ignoring transid failure ERROR: child eb corrupted: parent bytenr=22052864 item=4 parent level=1 child level=1 Couldn't read chunk tree Could not open root, trying backup super parent transid verify failed on 22183936 wanted 519 found 510 parent transid verify failed on 22183936 wanted 519 found 510 parent transid verify failed on 22183936 wanted 519 found 510 Ignoring transid failure ERROR: child eb corrupted: parent bytenr=22052864 item=4 parent level=1 child level=1 Couldn't read chunk tree Could not open root, trying backup super ==================================== By the way, if the file on the unmountable is acceptable to be lost, what happen if I format the unmountable disk , will I just lost the file on the unmountable disk only without impacting the Parity validity or I will need to rebuild the parity all over again ?

Happy New Year !!! I just back to my server after a long vacation. I did try to follow the recommendation from JorgeB by follow the Step#2. Here is the result I got. Please advise. root@chbvault:/# btrfs restore -v /dev/sdg1 /mnt/disk8/restore parent transid verify failed on 22183936 wanted 519 found 510 parent transid verify failed on 22183936 wanted 519 found 510 parent transid verify failed on 22183936 wanted 519 found 510 Ignoring transid failure ERROR: child eb corrupted: parent bytenr=22052864 item=4 parent level=1 child level=1 Couldn't read chunk tree Could not open root, trying backup super parent transid verify failed on 22183936 wanted 519 found 510 parent transid verify failed on 22183936 wanted 519 found 510 parent transid verify failed on 22183936 wanted 519 found 510 Ignoring transid failure ERROR: child eb corrupted: parent bytenr=22052864 item=4 parent level=1 child level=1 Couldn't read chunk tree Could not open root, trying backup super parent transid verify failed on 22183936 wanted 519 found 510 parent transid verify failed on 22183936 wanted 519 found 510 parent transid verify failed on 22183936 wanted 519 found 510 Ignoring transid failure ERROR: child eb corrupted: parent bytenr=22052864 item=4 parent level=1 child level=1 Couldn't read chunk tree Could not open root, trying backup super

Thanks Itimpi and JorgeB for the recommendation and guide me to the article that help to recover the filesystem. I still have a question since I forgot to share that I have a perfect full backup on another Unraid server in a different location. In this case, is it easier for me to just pull off the physical drive and make the disk failed and Unraid mark status as "Disabled". Then I can copy file over again ? Also do you think that the Parity I have on this server with failed filesystem can save me by rebuilding after I force the Drive into "Disabled" status ? To be specific, will any of the below method works ? Method 1 (Force the drive to fail, re-format as BTRFS and then rebuild onto the drive using Parity) 1. Make the physical drive "Disabled". (By shutdown server and pull SATA power cable off) 2. Try to format in Unassigned device with BTRFS filesystem 3. Add the Disk back to original DISK9 location 4. Parity rebuild. Method 2 (Force the drive to fail --> New configuration --> Build parity --> Copy missing file from backup server) 1. Make the physical drive "Disabled". (By shutdown server and pull SATA power cable off) 2. Go to New Configuration and assign the drive location. 3. Build Partity, knowing that there will be some missing file. 4. Do file Compare and Sync with backup server and see which file is missing and copy file from another server.

I'm still using Unraid 6.9.0 Beta 25. I just successfully added a new disk with following steps but after file copy to new disk, it become un-mountable. 1, Preclear disk 2.Set disk to btrfs filesystem 3.Stop Array and add new disk (DISK9) 4.Start array and Format the disk 5.After completed the array are good. 6.Use Krusader to copy file from /mnt/disk8/* to /mnt/disk9/ 7.Successfully copy many files but suddenly Krusader start to report that it cannot write file 8.Test to creat small text file directly into /mnt/disk9/test.txt and got error the disk is Read-Only 9.Reboot Unraid and now disk become "Unmountable:No FIle System" Attached the Diagnostic file below Did I just lost the file on disk ? It strange that the circle status indicator in front of the disk still show green. SMART did not show any sign of issue. Now Unraid asked me if I want to format this disk. chbvault-diagnostics-20201227-2157.zip

I did both vbios and update Nvidia driver as you mentioned folowing Spaceinvaer One tutorial. Now it works for both GPU and Audio !!! Thanks for your great help to guide me in the right direction to fix this. One other thing that I wonder if we can passthrough onboard audio at the same time ? When I try to passthrough the onboard audio while keeping the one the come with GPU the same. I got a whole Unraid server freeze and need to reboot. Any recommendation on this ?

Thanks for your advice testdasi. Here is my System Devices IOMMU group 0: [1022:1482] 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 1: [1022:1483] 00:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge IOMMU group 2: [1022:1482] 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 3: [1022:1482] 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 4: [1022:1483] 00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge IOMMU group 5: [1022:1482] 00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 6: [1022:1482] 00:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 7: [1022:1482] 00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 8: [1022:1484] 00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] IOMMU group 9: [1022:1482] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 10: [1022:1484] 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] IOMMU group 11: [1022:1484] 00:08.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] IOMMU group 12: [1022:1484] 00:08.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] IOMMU group 13: [1022:790b] 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 61) [1022:790e] 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51) IOMMU group 14: [1022:1440] 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 0 [1022:1441] 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 1 [1022:1442] 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 2 [1022:1443] 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 3 [1022:1444] 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 4 [1022:1445] 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 5 [1022:1446] 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 6 [1022:1447] 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 7 IOMMU group 15: [1022:43d0] 01:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] Device 43d0 (rev 01) IOMMU group 16: [1022:43c8] 01:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset SATA Controller (rev 01) IOMMU group 17: [1022:43c6] 01:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Bridge (rev 01) IOMMU group 18: [1022:43c7] 02:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01) IOMMU group 19: [1022:43c7] 02:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01) [1b21:1242] 04:00.0 USB controller: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller IOMMU group 20: [1022:43c7] 02:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01) IOMMU group 21: [1022:43c7] 02:07.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01) [8086:1539] 06:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03) IOMMU group 22: [1022:43c7] 02:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01) IOMMU group 23: [10de:128b] 08:00.0 VGA compatible controller: NVIDIA Corporation GK208B [GeForce GT 710] (rev a1) IOMMU group 24: [10de:0e0f] 08:00.1 Audio device: NVIDIA Corporation GK208 HDMI/DP Audio Controller (rev a1) IOMMU group 25: [1022:148a] 09:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function IOMMU group 26: [1022:1485] 0a:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP IOMMU group 27: [1022:1486] 0a:00.1 Encryption controller: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Cryptographic Coprocessor PSPCPP IOMMU group 28: [1022:149c] 0a:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller IOMMU group 29: [1022:1487] 0a:00.4 Audio device: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller IOMMU group 30: [1022:7901] 0b:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) IOMMU group 31: [1022:7901] 0c:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) The VM XML <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='2'> <name>Windows 10 SSD</name> <uuid>16679549-a582-877d-bb23-4ac4631f4964</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>8912896</memory> <currentMemory unit='KiB'>8912896</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='2'/> <vcpupin vcpu='1' cpuset='8'/> <vcpupin vcpu='2' cpuset='4'/> <vcpupin vcpu='3' cpuset='10'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-4.2'>hvm</type> </os> <features> <acpi/> <apic/> <hyperv> <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'> <topology sockets='1' cores='2' 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='block' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source dev='/dev/disk/by-id/ata-WDC_WDS500G2B0A-00SM50_20063B805428' index='2'/> <backingStore/> <target dev='hdc' bus='sata'/> <boot order='1'/> <alias name='sata0-0-2'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/virtio-win-0.1.173-2.iso' index='1'/> <backingStore/> <target dev='hdb' bus='ide'/> <readonly/> <alias name='ide0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='ide' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='sata' index='0'> <alias name='sata0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </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:b3:33:63'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <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 SSD/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <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> <hostdev mode='subsystem' type='pci' managed='yes' xvga='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x08' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </source> <alias name='hostdev2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain> Diagnostic File is as atteched. And here is my driver capture from Windows 10 Device Manager backup-diagnostics-20200407-0344.zip

Hi, This is my first unraid setup and I follow the guide on youtube. I've got everything setup on... CPU: AMD Ryzen 5 3600 GPU: NVIDIA Zotac GT710 Motherboard: ASUS X470 Prim Pro First I install baremetal Windows 10 on SATA SSD and once the Unraid was setup, I passthrough the SATA SSD to run as VM in Unraid. Everything work great as long as I only passthrough GPU only. Once I start to passthorugh the Audio device with the NVIDIA name in it to make sure that it the sound counterpart of GPU, then everything go black screen. I tried to search for solution and found one of the video from invader on advance GPU passthorugh (https://www.youtube.com/watch?v=QlTVANDndpM&t=638s), where he mentioned that sometime need to modify the XML for VM to ensure that GPU and Audio do not split into different slot. So I follow and modify my GPU as multifunction and change Audio to the same virtual slot as GPU (see XML below). Once I save and try to start the VM. It go black screen. Hope if someone can point out what I did wrong or something I should study more to correct the configuration. Thanks. ===1. CONFIGURATION THAT WORKS WELL FOR VIDEO BUT HAVE NO AUDIO=== <hostdev mode='subsystem' type='pci' managed='yes' xvga='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x08' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </hostdev> ===2. CONFIGURATION THAT NOT WORKS AFTER PASSTHROUGH AUDIO FROM MENU === <hostdev mode='subsystem' type='pci' managed='yes' xvga='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x08' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </hostdev> ===3. CONFIGURATION THAT NOT WORKS AFTER ADD ADAPTER + MODIFY SLOT OF AUDIO TO BE SAME AS GPU=== <hostdev mode='subsystem' type='pci' managed='yes' xvga='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x08' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x08' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x1'/> </hostdev> ===================