stottle

Not sure if this is progress or not. The above error looked like a passthrough issue, so opened the edit window and changed the soundcard from the nvidia GPU to "None". So VNC instead of GPU for audio/video, and I removed the passthrough of my pcie usb controller. With these changes, the VM will actually start, but it goes immediately into the BSOD (Windows ran into a problem) in the VNC window. I would have thought windows would have all necessary drivers for VNC, so not sure what the problem is here. Help? And to make matters worse, sdh is already showing new errors after the count was zeroed (earlier runs showed all zero): root@Tower2:~# btrfs dev stats /mnt/cache [/dev/sdh1].write_io_errs 441286 [/dev/sdh1].read_io_errs 407435 [/dev/sdh1].flush_io_errs 2040 [/dev/sdh1].corruption_errs 0 [/dev/sdh1].generation_errs 0 [/dev/sdg1].write_io_errs 0 [/dev/sdg1].read_io_errs 0 [/dev/sdg1].flush_io_errs 0 [/dev/sdg1].corruption_errs 0 [/dev/sdg1].generation_errs 0

Ok, powered off and replaced the sata cables. I had tried starting the VM after running scrub with corrections enabled, but received the same error. Now, after powering back on after swapping cables, I'm getting a new message: Execution error internal error: qemu unexpectedly closed the monitor: 2017-02-13T00:07:35.264400Z qemu-system-x86_64: -device vfio-pci,host=01:00.1,id=hostdev0,bus=pci.0,addr=0x6: vfio: error, group 1 is not viable, please ensure all devices within the iommu_group are bound to their vfio bus driver. 2017-02-13T00:07:35.264413Z qemu-system-x86_64: -device vfio-pci,host=01:00.1,id=hostdev0,bus=pci.0,addr=0x6: vfio: failed to get group 1 2017-02-13T00:07:35.264421Z qemu-system-x86_64: -device vfio-pci,host=01:00.1,id=hostdev0,bus=pci.0,addr=0x6: Device initialization failed

Hmm, I turned off all running dockers (array is still running, but this is the cache drive) and tried running a 2nd readonly scrub. I was curious how repeatable it was. It actually has a few LESS errors. root@Tower2:/# btrfs scrub start -rdB /mnt/cache > /boot/logs/scrub_cache2.log root@Tower2:/# cat /boot/logs/scrub_cache2.log scrub device /dev/sdh1 (id 1) done scrub started at Sun Feb 12 18:00:23 2017 and finished after 00:06:36 total bytes scrubbed: 75.84GiB with 175178 errors error details: verify=679 csum=174499 corrected errors: 0, uncorrectable errors: 0, unverified errors: 0 scrub device /dev/sdg1 (id 2) done scrub started at Sun Feb 12 18:00:23 2017 and finished after 00:06:33 total bytes scrubbed: 75.84GiB with 0 errors root@Tower2:/# btrfs dev stats /mnt/cache [/dev/sdh1].write_io_errs 181614787 [/dev/sdh1].read_io_errs 147213104 [/dev/sdh1].flush_io_errs 3842528 [/dev/sdh1].corruption_errs 349010 [/dev/sdh1].generation_errs 1493 [/dev/sdg1].write_io_errs 0 [/dev/sdg1].read_io_errs 0 [/dev/sdg1].flush_io_errs 0 [/dev/sdg1].corruption_errs 0 [/dev/sdg1].generation_errs 0 Diagnostics also attached. tower2-diagnostics-20170212-1810.zip

Thanks for the help. Any suggestions for determining what is causing the errors?

I'm trying to see if there is something else that might be causing the problem. I'm running a btrfs raid1 cache, but get the following root@Tower2:/# btrfs scrub start -rdB /mnt/cache > /boot/logs/scrub_cache.log root@Tower2:/# vi /boot/logs/scrub_cache.log reading /boot/logs/scrub_cache.log Read /boot/logs/scrub_cache.log, 8 lines, 416 chars scrub device /dev/sdh1 (id 1) done scrub started at Sun Feb 12 17:23:16 2017 and finished after 00:06:38 total bytes scrubbed: 75.88GiB with 175313 errors error details: verify=814 csum=174499 corrected errors: 0, uncorrectable errors: 0, unverified errors: 0 scrub device /dev/sdg1 (id 2) done scrub started at Sun Feb 12 17:23:16 2017 and finished after 00:06:38 total bytes scrubbed: 75.88GiB with 0 errors I assume errors in the VM image could cause the issue I am seeing. Since one disk has errors, but the 2nd one doesn't I assume I can run scrub again, but without the readonly flag? Any risk in doing this? Would I be better off reverting from 6.3 back to 6.2.4? Thanks

Already tried that, it didn't help. The original xml was from before I tried the steps listed in the release notes. I tried those steps, with no luck, then tried disabling all passthrough devices as well. Same error message. My current xml is: <domain type='kvm'> <name>Win10</name> <uuid>449c8082-8631-ef95-bd97-1bdad139ddc7</uuid> <description>Windows 10</description> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>1</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-2.7'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/449c8082-8631-ef95-bd97-1bdad139ddc7_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='1' threads='1'/> </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/cache/VM/Win10/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> <controller type='usb' index='0' model='nec-xhci'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <controller type='pci' index='0' model='pci-root'/> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:6b:d2:ee'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <target port='0'/> </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='tablet' bus='usb'> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </memballoon> </devices> </domain>

Note: This isn't the Trying to start my VM gives a "Invalid Machine Type" error issue noted in the release notes. I've tried the suggestions listed there and they have no effect. Any other suggestions?

If it helps, my VM xml is shown below I do see <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> This is a file on unRAID dated Feb 2nd, so I am guessing it is part of the 6.3.0 update. I'm not sure what that means, but the error message says initialization of pflash failed... <domain type='kvm'> <name>Win10</name> <uuid>449c8082-8631-ef95-bd97-1bdad139ddc7</uuid> <description>Windows 10</description> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>1</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-2.3'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/449c8082-8631-ef95-bd97-1bdad139ddc7_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='1' threads='1'/> </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/cache/VM/Win10/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <controller type='usb' index='0' model='nec-xhci'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <controller type='pci' index='0' model='pci-root'/> <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:6b:d2:ee'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <target port='0'/> </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='0x01' slot='0x00' function='0x0'/> </source> <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='0x1'/> </source> <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='0x02' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </hostdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </memballoon> </devices> </domain>

I have a Win10 VM that I have GPU passthru on for. I downloaded unRAID 6.3.0 (from 6.2.4), shutdown the VM, restarted unRAID. Now unRAID pops up a big error message when I try to start the VM: Execution error internal error: qemu unexpectedly closed the monitor: 2017-02-04T21:56:40.034390Z qemu-system-x86_64: Initialization of device cfi.pflash01 failed: failed to read the initial flash content Could be 6.3.0 related, but might not be. And I figured the message would make more sense to the people in this forum. I hope you guys have suggestions.

I have OVMF/Win10 setup as well. One thing I found was that after the initial OS install, I had to edit the VM config to remove the OS install iso and the virtio drivers iso. It seemed like OVMF was trying to boot from those instead of the vdisk. Taking then out of the VM config fixed that for me.

arch - thanks for the great write-up. I hit a snag where the controller I wanted to pass was in an IOMMU group that had other devices I didn't want to pass to the VM, though. Since this is a PCIe card, I didn't expect this. I found this blog post about IOMMU groups really helpful, specifically After a few tries, I found a slot that put the usb controller and the GPU I want to pass in the same group. So I don't need to try the PCIe ACS override. Maybe it is worth addressing what to do if you don't have nice groups in your first post? Also, your group shell script would look pretty good in that first post! And again, thanks!

I have a Keyboard/Video/Mouse (KVM) switch I'm trying to use between a desktop windows machine and a Windows VM (of course, using KVM). The VM's edit page in Dynamix only lists "Super Gate Technology Co., Ltd" under USB Devices. However, if I look at Tools->System Devices, it has: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 174c:3074 ASMedia Technology Inc. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 051d:0002 American Power Conversion Uninterruptible Power Supply Bus 001 Device 004: ID 174c:2074 ASMedia Technology Inc. Bus 001 Device 005: ID 05d5:0624 Super Gate Technology Co., Ltd Bus 001 Device 003: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 002: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) Flash Drive Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub which includes: Bus 001 Device 003: ID 0557:7000 ATEN International Co., Ltd Hub the ATEN device from my KVM switch, the extra device for the KVM I need to pass through. So I guess I have two questions 1) Is there an easy way (i.e., not editing the xml directly) of having the ATEN device added? 2) Sounds like there are a number of VM changes in 6.2, will this behave differently? Thanks

If you aren't familiar with stackoverflow, that (among many other benefits) is what it does. You should check it out if you haven't already. Doesn't everyone know about stackoverflow?

You mean like JIRA? If so, I disagree. It's to easy to add issues (like asking questions here), and very difficult and time consuming to resolve them. That doesn't address the fundamental issue that unRAID has a lot of collaborators (who probably couldn't close bugs), and not nearly as many developers. Stackoverflow makes the collaborators work more valuable, an issue tracking system doesn't. To me, making it easier to find the (current) best answer would resolve many of the issues, but the answers are hard to find on the forums. Once that problem is handled, I may start to agree with you.

There are so many questions repeated or asked with slightly different permutations on this forum. Has Tom, Jon, or anyone else at Limetech looked at using Stackoverflow's engine? Two huge benefits would be 1) Voting/comments and additional answers (even years later) help ensure the highest rated answers are both current and relevant 2) Works very well with search engines (including google) There's such an active community on the forums, seems like this one step would make their contributions so much more accessible. Thoughts? More info can be found at this page.

So the timestamp on bzroot was unchanged from the unRAID 6.1.8 installer zip file, windows copy said the two files were the same size and timestamp, but replacing it gets unRAID to boot. Thanks a ton for the prompt reply!

You posted while I was adding more info. I will try replacing bzroot and see if that helps.

More info, I have two licenses. Using a different usb stick will actually load unRAID (not the correct config, though), so it appears to be something wrong with my flash data. I plugged the "bad" flash into a PC, it did NOT ask to fix anything. Nothing at the root level has a recent timestamp except readvz, although I think that is because I installed the powerdown plugin yesteray. In config, super.dat and secrets.tdb were touched most recently (same timestamp), while domain.cfg and disk.cfg have timestamps of within 1/2 hour of super.dat and secrets.tdb. Could issues in any of these files create what I'm seeing?

unRAID (clean install of 6.1. was working fine. Been restarting to try to get GPU passthrough working on a VM. As in stop array, check "yes I want to do this" and hit reboot button. On one of the reboots (nothing changed other than the VM on the cache drive), the unraid screen starts, gets to the blue screen, says loading /bzimage....ok, loading /bzroot...ok, flashes to a black screen for just a moment, then shows the loading /bzroot stuff in blue again and just stays there. No idea what to do here. Turned off the computer and unplugged it for about an hour (thinking it may be thermal), but after an hour, same result. Appreciate any help! Unrelated I think - working on Win10 VM, and my GPU, an EVGA GT730, seems to not handle VM restart once I pass a GPU through. If the VM restarts w/ passthrough, I need to reboot the VM before anything goes to the monitor. I had this in the past, it worked fine once I got the nvidia drivers installed, but I'm having trouble repeating the process to get the drivers installed.

I asked in an old thread, but didn't get any response, so I trying here. Can someone point me to instructions for putting a clean install of unRAID on a new flash drive (I have a 2nd/backup license available) and specifically getting it set up to work with what is already on my drives? Will it automatically find my current unRAID setup (data/shares) because the drives are already formatted properly? Almost positive this is the case, just like a "New Config" would do. Can I enable dockers and add the same containers and recover what I have already? If so, how? Are there specific files I need/should to copy over from the old flash drive? Pointers to other threads/wiki are fine for answers (just looking for confirmation of the right process). Just want to ask before I do anything and risk corrupting my array!

I know this is old. I didn't realize jonp had asked for more info. I still have this problem, but assume it is something out-of-date on my flash drive. F12 on the webpage (from chrome) said there was an error on the page's source. Can someone point me to instructions for putting a clean install of unRAID on a new flash drive (I have a 2nd/backup license available) and specifically getting it set up to work with what is already on my drives? Will it automatically find my current unRAID setup (data/shares) because the drives are already formatted properly? Can I enable dockers and add the same containers and recover what I have already? If so, how? Are there specific files I need/should to copy over from the old flash drive? Pointers to other threads/wiki are fine for answers (just looking for confirmation of the right process). Just want to ask before I do anything and risk corrupting my array!

Ok, I manually deleted the files from the cache (from windows), then a scrub ran quickly and found no errors. I then ran balance, as it had been saying I had a several hundred GB in "single" and only 2 GB in "raid1". Now it has the following in the web UI: Label: none uuid: a84b9278-e4b6-463b-b0bd-aa655dabce37 Total devices 2 FS bytes used 640.00KiB devid 1 size 465.76GiB used 2.03GiB path /dev/sdg1 devid 2 size 465.76GiB used 2.03GiB path /dev/sdd1 btrfs-progs v4.1.2 Data, RAID1: total=1.00GiB, used=512.00KiB System, RAID1: total=32.00MiB, used=16.00KiB Metadata, RAID1: total=1.00GiB, used=112.00KiB GlobalReserve, single: total=16.00MiB, used=0.00B Can someone confirm if this looks reasonable or not?

I have an old btrfs formatted drive I was mounting myself (neither cache nor array). It was formatted in the early days of btrfs being available in unRAID. Running scrub says there are uncorrectable errors. I bought 2nd identical drive, and I tried to install both as a cache pool. That part worked, but the manual says that once you install the gui will give you the option to format. I guess since one of my drives was already btrfs, it isn't giving me that option. The "old stuff" (including errors) is still on the drive - which is showing up as the cache drive. How do I correct this? In particular, have there been btrfs updates (to the fs itself) that I should reformat for? Or is just deleting the files sufficient? Thanks in advance

This is, in my opinion, one of the biggest benefits AND problems with unRAID. There is so much information in the forum threads that those that keep up have insight that is almost impossible to find elsewhere. At the same time people that don't have time to monitor the threads get pointed to random links, and have no idea if the "community opinion" has changed based on some later set of threads that are more recent. And I'm sure you get tired of getting asked the same questions. Add to this the fact that this is an opinion-based question, and it gets even tougher. Maybe the stackoverflow model would make sense here? /rant Thanks for the info. I'm not sure what I will do yet, but I appreciate people talking the time to reply.

Mind explaining why?