egtrev

Sorry, my mistake, I had my DHCP locked down, so my server wouldn't get an address when the network cfg was reset. All working now, it automatically made the 2.5 card eth0 and the motherboard ports eth1/eth2, which is what I wanted. Thanks for the help.

I have rebooted but I'm now unable to see my server on my network. Can I restore the deleted cfg files to get it back online, or will that mess things up?

I don't see eth122 in the interface rules. Currently using it as the backup with eth0/eth1 unplugged, works but would prefer to have it as the main interface.

Hi all, Currently I have a dual Gigabit LAN motherboard (Eth0 & Eth01), setup in Bonding mode 'active-backup', so if one goes down the other takes over. Static IP set and all works fine, solid 110MB/s network file transferring. I have purchased a 2.5Gbps PCI-E card, the goal is to have this as the main interface in Bonding mode 'active-backup' with one of the motherboard ports becoming the backup. I've installed the card and it shows up in devices fine, under network settings it shows as another interface 'eth122'. I'm a bit stuck now on how I can make this the main interface. So far I've added 'eth122' as a Bonding member and removed 'eth01', if I unplug 'eth0' it then falls to the 2.5G (eth122) and it works fine - 260-280MB/s network file transferring. The problem is I don't won't it to be the backup I want it to be the main interface. Would anyone be able to point me in the right direction on the correct steps for this please?

Has anyone had issues mounting an image backup from the WebUI? The WebUI tries to mount but it just endlessly keeps loading/spinning and doesn't come back with any errors. The log shows the below multiple times, which I'm guessing is related to the issue: ERROR: Cannot open "/media/DELL/231001-2019_Image_C/contents0": Permission denied (13) I have to restart the Docker to stop the Mount attempt.

Hi, I've noticing some errors when rebooting Unraid and they seem to point to the flash drive. See below for the Flash drive log, everything is working fine, is this something I should be worried about? Sep 1 11:06:37 UNRAID emhttpd: SanDisk_Ultra_Fit_4C531154480830111172-0:0 (sda) 512 60062500 Sep 1 11:06:37 UNRAID emhttpd: import flash device: sda Sep 1 11:06:37 UNRAID emhttpd: read SMART /dev/sda Sep 1 11:07:01 UNRAID kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Sep 1 11:07:01 UNRAID kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] Sep 1 11:07:01 UNRAID kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 Sep 1 11:07:01 UNRAID kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 00 02 c8 00 00 01 00 Sep 1 11:07:01 UNRAID kernel: critical medium error, dev sda, sector 712 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Sep 1 11:07:01 UNRAID kernel: Buffer I/O error on dev sda1, logical block 680, async page read Sep 1 11:07:01 UNRAID kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Sep 1 11:07:01 UNRAID kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] Sep 1 11:07:01 UNRAID kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 Sep 1 11:07:01 UNRAID kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 00 02 c9 00 00 07 00 Sep 1 11:07:01 UNRAID kernel: critical medium error, dev sda, sector 713 op 0x0:(READ) flags 0x0 phys_seg 7 prio class 2 Sep 1 11:07:01 UNRAID kernel: Buffer I/O error on dev sda1, logical block 681, async page read Sep 1 11:07:01 UNRAID kernel: Buffer I/O error on dev sda1, logical block 682, async page read Sep 1 11:07:01 UNRAID kernel: Buffer I/O error on dev sda1, logical block 683, async page read Sep 1 11:07:01 UNRAID kernel: Buffer I/O error on dev sda1, logical block 684, async page read Sep 1 11:07:01 UNRAID kernel: Buffer I/O error on dev sda1, logical block 685, async page read Sep 1 11:07:01 UNRAID kernel: Buffer I/O error on dev sda1, logical block 686, async page read Sep 1 11:07:01 UNRAID kernel: Buffer I/O error on dev sda1, logical block 687, async page read Sep 1 11:07:01 UNRAID kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Sep 1 11:07:01 UNRAID kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] Sep 1 11:07:01 UNRAID kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 Sep 1 11:07:01 UNRAID kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 00 02 c8 00 00 01 00 Sep 1 11:07:01 UNRAID kernel: critical medium error, dev sda, sector 712 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Sep 1 11:07:01 UNRAID kernel: Buffer I/O error on dev sda1, logical block 680, async page read Sep 1 11:08:02 UNRAID kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Sep 1 11:08:02 UNRAID kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] Sep 1 11:08:02 UNRAID kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 Sep 1 11:08:02 UNRAID kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 00 02 c8 00 00 01 00 Sep 1 11:08:02 UNRAID kernel: critical medium error, dev sda, sector 712 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Sep 1 11:08:02 UNRAID kernel: Buffer I/O error on dev sda1, logical block 680, async page read

This is great. I have a backup 4G WAN connection on my router when my main broadband goes down. The issue was the 4G provider uses a shared external IP with NAT so any port forwarding I was using does not work when running through the backup 4G connection so all my VPN's didn't work. This app allowed access to my network even when using the 4G WAN, very useful, thanks.

3rd check completed, no errors found. Thanks for the help.

Thanks I'll start a non correcting check now and see what that comes back with.

There are multiple users so unsure if anyone was writing to it or not. How do I get the Parity back in sync or find out what files are corrupted? Should the correcting Parity check not have fixed the errors?

Hello, I had an issue with a faulty UPS that caused my Unraid system to shutdown twice. Once was during normal system operation and the second was about 10% into the automatic parity check after the unclean shutdown. The automatic Parity check that completed after the 2nd shutdown notified of 336 errors. I manually started a 2nd Parity check with the 'Write corrections to parity' checked. That also completed with 336 errors. Is there anyway to find out what the errors are? I assume some files may be corrupted - I have backups so happy to restore anything that could have been corrupted. Everything seems to be working fine no issues just the notification that it found the errors. Do I need to run a 3rd check now? It takes about 24 hours to finish (14TB drives) Thanks.

I seem to have lost the ability on the Dashboard to see current transcodes/playback. Does anyone know if this is a setting somewhere?

I haven't used Wireguard for a while but I had the same issue and I believe I fixed it my manually adding DNS on the config. See screenshot of my config. Worth a try if you haven't already.

Windows 7 Seabios (No signal) XML <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Windows Seven</name> <uuid>4885e26a-5b51-9440-2568-7b98f117ba9b</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 7" icon="windows7.png" os="windows7"/> </metadata> <memory unit='KiB'>2097152</memory> <currentMemory unit='KiB'>2097152</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>1</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-4.2'>hvm</type> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='1' threads='1'/> <cache mode='passthrough'/> </cpu> <clock offset='localtime'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <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/VM/Windows Seven/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/ISO/virtio-win-0.1.126-2.iso'/> <target dev='hdb' bus='ide'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='pci' index='0' model='pci-root'/> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <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'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:56:c3:8a'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <hostdev mode='subsystem' type='pci' managed='yes' xvga='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </source> <rom file='/mnt/cache/appdata/MSI960.dump'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0' multifunction='yes'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x02' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x1'/> </hostdev> <memballoon model='none'/> </devices> </domain> The Windows 7 OVMF is pretty much the same as above, except GPU passthrough works (but gets stuck on Windows 7 boot logo) <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Windows Seven</name> <uuid>b5648100-a87a-8272-a46f-f27253caa09a</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 7" icon="windows7.png" os="windows7"/> </metadata> <memory unit='KiB'>2097152</memory> <currentMemory unit='KiB'>2097152</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>1</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-4.2'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/b5648100-a87a-8272-a46f-f27253caa09a_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='1' threads='1'/> <cache mode='passthrough'/> </cpu> <clock offset='localtime'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <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/VM/Windows Seven/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/ISO/virtio-win-0.1.126-2.iso'/> <target dev='hdb' bus='ide'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <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'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'/> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:1e:40:61'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </source> <rom file='/mnt/cache/appdata/MSI960.dump'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0' multifunction='yes'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x02' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x1'/> </hostdev> <memballoon model='none'/> </devices> </domain>

Thanks for oyur help, unfortunately those steps are what I followed from Spaceinvaders videos, I don't have any issues except with Windows 7. My Windows 10 VM works great. Just Windows 7 with Seabios I get no signal and Windows 7 with OVMF I get video but can't get the installer to proceed. It's an MSI GTX960 Gaming 2GB. I don't know if something changed in UNRAID in the last year or so that broke my Windows 7 VM passthrough, driving me crazy that it was working previously! haha.