JKunraid

I have an unraid server with 12 drives on main array. 7 of them are 18TB (1 of the 7 is a parity drive). The remaining 5 drives are smaller. I'd like to replace the 5 smaller drives with 18TB drives. I can change drives one by one and rebuild but is there a faster and less drive torturous way to do it without losing my data? For instance, can I pull all five drives at once, add the 5 replacements, then manually add back the data from the smaller drives I pulled? (e.g. using USB dock or temporary using spare SATA).

When I click the "Add remote SMB/NFS Share" button on Main tab button a pop up appears that allows me to select Linux. I then click "next" and it lets be search for servers. It can find server but I can't view or add the share because there is no obvious way to add userid and password. so I can connect to remote share.

Problem is still occurring. Unraid's log of the crashed VM when I try to restart it without rebooting Unraid.... -uuid c2e6aa27-27d4-3b09-bf73-6cfe5722ef4c \ -no-user-config \ -nodefaults \ -chardev socket,id=charmonitor,fd=31,server,nowait \ -mon chardev=charmonitor,id=monitor,mode=control \ -rtc base=utc,driftfix=slew \ -global kvm-pit.lost_tick_policy=delay \ -no-hpet \ -no-shutdown \ -boot strict=on \ -device pcie-root-port,port=0x10,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x2 \ -device pcie-root-port,port=0x11,chassis=2,id=pci.2,bus=pcie.0,addr=0x2.0x1 \ -device pcie-root-port,port=0x12,chassis=3,id=pci.3,bus=pcie.0,addr=0x2.0x2 \ -device pcie-root-port,port=0x13,chassis=4,id=pci.4,bus=pcie.0,addr=0x2.0x3 \ -device pcie-root-port,port=0x14,chassis=5,id=pci.5,bus=pcie.0,addr=0x2.0x4 \ -device pcie-root-port,port=0x15,chassis=6,id=pci.6,bus=pcie.0,addr=0x2.0x5 \ -device qemu-xhci,p2=15,p3=15,id=usb,bus=pcie.0,addr=0x7 \ -device virtio-serial-pci,id=virtio-serial0,bus=pci.2,addr=0x0 \ -blockdev '{"driver":"file","filename":"/mnt/user/domains/Ubuntu20.04LTS-Desktop/vdisk1.img","node-name":"libvirt-1-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-1-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"qcow2","file":"libvirt-1-storage","backing":null}' \ -device virtio-blk-pci,bus=pci.4,addr=0x0,drive=libvirt-1-format,id=virtio-disk2,bootindex=1,write-cache=on \ -fsdev local,security_model=passthrough,id=fsdev-fs0,path=/mnt/user/ChiaPlots/ \ -device virtio-9p-pci,id=fs0,fsdev=fsdev-fs0,mount_tag=/mnt/ChiaPlots,bus=pci.1,addr=0x0 \ -netdev tap,fd=33,id=hostnet0 \ -device virtio-net,netdev=hostnet0,id=net0,mac=52:54:00:64:27:e5,bus=pci.3,addr=0x0 \ -chardev pty,id=charserial0 \ -device isa-serial,chardev=charserial0,id=serial0 \ -chardev socket,id=charchannel0,fd=34,server,nowait \ -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ -device usb-tablet,id=input0,bus=usb.0,port=1 \ -vnc 0.0.0.0:0,websocket=5700 \ -k en-us \ -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pcie.0,addr=0x1 \ -device vfio-pci,host=0000:23:00.0,id=hostdev0,bus=pci.5,addr=0x0 \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on 2021-09-27 12:04:31.013+0000: Domain id=3 is tainted: high-privileges 2021-09-27 12:04:31.013+0000: Domain id=3 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) 2021-09-27 12:04:57.956+0000: shutting down, reason=failed

Created an Ubuntu Desktop 20.04 (x64) VM. Use it mostly for Chia farming and occasional odd task. it's supposed to be on 24/7. Worked fine for weeks but in the last week its been crashing several times a day. The weird part is after the VM crashes I can't even start it up again unless I reboot the Unraid server entirely. (which suggests an Unraid problem rather than a VM OS problem). Any suggestions how to tackle this problem? Unless I reboot unraid server entirely, when I try to restart the crashed VM I get following message "Execution error internal error: qemu unexpectedly closed the monitor"

I have a share setup in Unraid. If I start my Ubuntu VM (in Unraid) and go to "other locations" in the file manager I can see my Unraid server. When I click it prompts for userid/password (which I input) and then displays all my Unraid shares. I click on my share in the file manager and it appears to the left as a mounted drive in file manager. I can even add folders and files to it through the file manager The problems arise when I then switch to terminal window in same VM. I can see the mounted share in the folder /run/user/1000/gvfs but when I try to write a folder or file to it using command line it fails. (folder shows permissions of drwx------)

Found the solution. Speaking as an experienced dev, this was way way too complicated to setup. I can only imagine how many non-techies give up trying to figure this out Hopefully future versions of Unraid make this far more intuative. For anyone else experiencing similar problem here is a brief walkthrough of major steps I took to get an EVGA GTX 1070 SC running on an AMD Threadripper board on Unraid 6,9.2. 1. Enable IOMMU, CSM and Legacy mode in bios (note for some GPUs UEFI rather than legacy might work better) 2.1 In Unraid go to tools > system devices. 2.2 Scroll down until you find the IOMMU group with your GPU. 2.3. Click the checkbox for all the devices in the GPU's IOMMU group and save. 3. Go to techpower up website and download vbios version for your GPU https://www.techpowerup.com/vgabios/ 4.1 (NOTE: This step might only apply to systems with single NVIDIA GPU) Download/Install a Hex editor. 4.2 Use Hex editor to modify the above VBIOS file deleting leading section (google to find exact section that needs to be deleted on your card) 4.3 Save then upload modified VBIOS file to some location on your Unraid server. 5.1 Go to VM manger screen and create new win10 VM 5.2 For initial installation for "GRAPHICS CARD" field select VNC. 5.3 Install Win10 and enable remote desktop. 5.4 Confirm you can connect with RDP 6.1 Go back to the VM template you created to edit it. 6.2. For "Graphics Card" field select you GPU from dropdown (in my case a EVGA GTX 1070 SC) 6.3 For "Graphics ROM BIOS" select your modified VBIOS 6.4. For "Sound Card" you must select sound card that is same IOMMU group as GPU (you can add second card if needed) 6.6 select "UPDATE" to save the file 7.1 reopen your VM template from above (the reason why this step is needed is because of a bug that resets below if you try to use "form view" for following steps) 7.2 click on "XML View" 7.3 scroll down to the fields that list the slots for you GPU and Sound Drive .(In my case it looks like below. Yours may differ and need additional edits if more devices on same IOMMU) <rom file='/mnt/transfer_pool/Transfer/Unraid/VBIOS/EVGA.GTX1070.8192.161103_1.rom'/> <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='0x50' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> 7.4 My GPU also have a sound device built in. When you plug into a physical mobo both devices are in the same PCIe slot. Unfortunately when Unraid maps it to virtual mobo it places the devices in different slots which confuse the NVIDIA driver. To fix this issue you have to put all the devices on the same IOMMU in same slots. For my particular GPU these were the two lines that I modified from above. <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0' '/> (changed to below) <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0' multifunction='on'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0/> (changed to below) <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x1'/> 7.5 Click update to save XML file. Note: it's essential not to go back to the "form version" to save the VM template as it will discard these manual edits. If you do ever change the template again in form view you will need to save it then manually edit it again in "XML view" again. 8.1. Start the VM. And try to connect with RDP after a minute (does some sort of update so takes a bit longer than normal to connect) 8.2 If you can't connect with RDP do a force shutdown of VM then restart it again (for some reason I had to do it twice for it to work)

UPDATE 2: Now I'm getting a message from fix common problems plugin that log is 100% full. I checked my syslog in /var/logs/ and its over 125Mb. When I tail the last 200 records show up with this message Aug 9 09:11:16 Threadripper kernel: vfio-pci 0000:50:00.0: BAR 1: can't reserve [mem 0xc0000000-0xcfffffff 64bit pref]

UPDATE: I just tried checking the boxes for following items (in tools > system files) then rebooting IOMMU group 74: [10de:1b81] 50:00.0 VGA compatible controller: NVIDIA Corporation GP104 [GeForce GTX 1070] (rev a1) [10de:10f0] 50:00.1 Audio device: NVIDIA Corporation GP104 High Definition Audio Controller (rev a1) It still can't connect via RDP but I think it has bound the devices to VFIO as mentioned. Below is copy of View VFIO-PCI log (found in from tools > system files) Loading config from /boot/config/vfio-pci.cfg BIND=0000:50:00.0|10de:1b81 0000:50:00.1|10de:10f0 --- Processing 0000:50:00.0 10de:1b81 Vendor:Device 10de:1b81 found at 0000:50:00.0 IOMMU group members (sans bridges): /sys/bus/pci/devices/0000:50:00.0/iommu_group/devices/0000:50:00.0 /sys/bus/pci/devices/0000:50:00.0/iommu_group/devices/0000:50:00.1 Binding... Successfully bound the device 10de:1b81 at 0000:50:00.0 to vfio-pci --- Processing 0000:50:00.1 10de:10f0 Vendor:Device 10de:10f0 found at 0000:50:00.1 IOMMU group members (sans bridges): /sys/bus/pci/devices/0000:50:00.1/iommu_group/devices/0000:50:00.0 /sys/bus/pci/devices/0000:50:00.1/iommu_group/devices/0000:50:00.1 Binding... 0000:50:00.0 already bound to vfio-pci 0000:50:00.1 already bound to vfio-pci Successfully bound the device 10de:10f0 at 0000:50:00.1 to vfio-pci --- vfio-pci binding complete Devices listed in /sys/bus/pci/drivers/vfio-pci: lrwxrwxrwx 1 root root 0 Aug 9 07:54 0000:50:00.0 -> ../../../../devices/pci0000:40/0000:40:03.1/0000:50:00.0 lrwxrwxrwx 1 root root 0 Aug 9 07:54 0000:50:00.1 -> ../../../../devices/pci0000:40/0000:40:03.1/0000:50:00.1 ls -l /dev/vfio/ total 0 crw------- 1 root root 249, 0 Aug 9 07:54 74 crw-rw-rw- 1 root root 10, 196 Aug 9 07:54 vfio

I'm not certain but believe IOMMU is enabled in bios. I can see my GPU listed under an IOMMU group in Unraid (tools > system devices) with check boxes for it unchecked. IOMMU group 74: [10de:1b81] 50:00.0 VGA compatible controller: NVIDIA Corporation GP104 [GeForce GTX 1070] (rev a1) [10de:10f0] 50:00.1 Audio device: NVIDIA Corporation GP104 High Definition Audio Controller (rev a1) I don't know if GPU IoMMU group is bound to VFIO at boot (and don't know how to check). For the record I looked at the VM's log and found this VFIIO message. Perhaps my problem? "2021-08-08T22:55:18.709941Z qemu-system-x86_64: vfio_region_write(0000:50:00.0:region1+0x42478, 0x0,8) failed: Device or resource busy:" When you say "passthrough parts", I'm assuming you mean in VM template right?. If so I've selected mygpu, nvidia audio driver, and tried all three available usb controller options in dropdown in VM template. Below is the xml view of the VM's template. <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='31'> <name>Windows 10 Pro</name> <uuid>b178c5a5-184a-f35a-04d3-5ab9b25d87f2</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>16777216</memory> <currentMemory unit='KiB'>16777216</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>34</vcpu> <cputune> <vcpupin vcpu='0' cpuset='1'/> <vcpupin vcpu='1' cpuset='33'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='34'/> <vcpupin vcpu='4' cpuset='3'/> <vcpupin vcpu='5' cpuset='35'/> <vcpupin vcpu='6' cpuset='4'/> <vcpupin vcpu='7' cpuset='36'/> <vcpupin vcpu='8' cpuset='5'/> <vcpupin vcpu='9' cpuset='37'/> <vcpupin vcpu='10' cpuset='6'/> <vcpupin vcpu='11' cpuset='38'/> <vcpupin vcpu='12' cpuset='7'/> <vcpupin vcpu='13' cpuset='39'/> <vcpupin vcpu='14' cpuset='8'/> <vcpupin vcpu='15' cpuset='40'/> <vcpupin vcpu='16' cpuset='9'/> <vcpupin vcpu='17' cpuset='41'/> <vcpupin vcpu='18' cpuset='10'/> <vcpupin vcpu='19' cpuset='42'/> <vcpupin vcpu='20' cpuset='11'/> <vcpupin vcpu='21' cpuset='43'/> <vcpupin vcpu='22' cpuset='12'/> <vcpupin vcpu='23' cpuset='44'/> <vcpupin vcpu='24' cpuset='13'/> <vcpupin vcpu='25' cpuset='45'/> <vcpupin vcpu='26' cpuset='14'/> <vcpupin vcpu='27' cpuset='46'/> <vcpupin vcpu='28' cpuset='15'/> <vcpupin vcpu='29' cpuset='47'/> <vcpupin vcpu='30' cpuset='16'/> <vcpupin vcpu='31' cpuset='48'/> <vcpupin vcpu='32' cpuset='17'/> <vcpupin vcpu='33' cpuset='49'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-5.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/b178c5a5-184a-f35a-04d3-5ab9b25d87f2_VARS-pure-efi.fd</nvram> </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' migratable='on'> <topology sockets='1' dies='1' cores='17' 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='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/Windows 10 Pro Template/vdisk1.img' index='1'/> <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> <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='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='usb' index='0' model='qemu-xhci' ports='15'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:ac:e6:5f'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio-net'/> <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-31-Windows 10 Pro/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'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x50' 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='0x50' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <hub type='usb'> <alias name='hub0'/> <address type='usb' bus='0' port='2'/> </hub> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain>

I've been working though setting up my first Unraid server. I've configured some plugins, precleared and smart tested my HDDs, started the array, setup several cache pools, and added some shares. I'm currently in the process of setting up a win10pro VM. I managed to install windows and It works fine when I use either Unraids VNC or I RDP into it. if "VNC" is selected as my graphics option in Unraid's VM template. Unfortunately when I select my actual card (EVGA GTX 1070) I can't connect via RDP. Any suggestions as to what the problem might be?

Sending RMA is a bit of pain. Can you elaborate on errors in smart log? Is it something that I need to fix right away or it something that a utility could mark a bad sector and play it by ear to see if more errors show up later (i.e. RMA it later if needed)

In the process of building my first Unraid server. Ran preclear once and one of the hard drives failed (Seagate Exos 18TB). So I ran Unraid short Smart test and it failed too. The drive that failed is new. Other than the preclear and Smart test error drive seems to work (e.g. I was able to format it). Is it possible to fix the error or should I be looking to RMA the drive? (I've attached smart report) smart-20210729-1519.zip

You mention "raid level". Do Unraid pools offer an exact software parallel to classical raid? (i..e Raid0 for read/write performance but no drive redundancy, raid 1 for mirroring but no performance benefit, raid 5 for increased read speeds but slower writes, Raid 10 better read/write with both stripping and mirroring because no parity,)

I have a ASUS Hypecard (PCIe 4.0) and some PCIe 4.0 NVMe SSDs . One of the (hypothetical) use cases for my Unraid server is as a Windows 10 VM that acts as a compile machine (Visual Studio) that I can connect locally to from my laptop using RDP. I'd like to allocate as much resources as possible to that VM to speed up compile times Ideally I'd like to combine 4 m.2 ssds on the Hypercard + 1 M.2 ssd on the board into a single combined persistent cache that would allow an SSD to fail while also providing better read/write performance than a single or mirrored SSD drive. Is this possible with Unraid? Alternatively, could I somehow achieve the same effect by allocating multiple unassigned drives to somehow software raid them together in Windows to get better performance than standalone? Some other option?