Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Started a VM and disk 5 went into error, followed by tons of IO errors on parity!

Featured Replies

Hi,

 

Earlier today I went to start a VM on my server and a disk (Disk 5) immediately went into error. I stopped the array, de-assigned the disk, started the array again, stoped it and re-assigned the disk. After the data rebuild on that disk I tried again to start the VM and the same thing happened.

 

Except this time my SMB shares wouldn't work, I had 7M + errors on my parity drive (Disk 0) and the log immediately filled to 100%.

 

I managed to grab a log before shutting everything down. First of all I'd like to make sure I didn't lose data and second of all I'd like to know what caused this issue and is it safe to reboot and bring the system back online.

 

 

Thanks everyone

 

 

IMG_0876.jpeg

unraid-diagnostics-20220601-1912.zip

Solved by itimpi

  • Community Expert

I have not looked at the diagnostics, but your symptoms suggest you are doing a hardware pass-through to the VM and the device now being selected is the disk controller.    If you have recently upgraded Unraid you need to be aware that hardware ID’s can change after the upgrade and need to be checked before starting any VM using hardware pass-through.

  • Author
21 hours ago, itimpi said:

I have not looked at the diagnostics, but your symptoms suggest you are doing a hardware pass-through to the VM and the device now being selected is the disk controller.    If you have recently upgraded Unraid you need to be aware that hardware ID’s can change after the upgrade and need to be checked before starting any VM using hardware pass-through.

Wow you certainly do know your stuff! that was exactly it! I unchecked the disk controller in the VM config. is it safe to start the VM back up now that no hardware is being passed-through?

Edited by sloob

  • Community Expert
  • Solution
3 hours ago, sloob said:

Wow you certainly do know your stuff! that was exactly it! I unchecked the disk controller in the VM config. is it safe to start the VM back up now that no hardware is being passed-through?

one begins to see a pattern after a while to certain types of error :) 
 

If no hardware is being passed through then there is no reason not to start the VM.

  • Author
15 hours ago, itimpi said:

one begins to see a pattern after a while to certain types of error :) 
 

If no hardware is being passed through then there is no reason not to start the VM.

One last question, Do you think I lost data with  what happened?

  • Community Expert
28 minutes ago, sloob said:

One last question, Do you think I lost data with  what happened?

No obvious reason why you should have as long as the drives mounted OK after rectifying the error.   If any drives are showing as unmountable I would suggest posting new diagnostics taken after starting the array.

  • 2 months later...
  • Author
On 6/2/2022 at 12:53 AM, itimpi said:

I have not looked at the diagnostics, but your symptoms suggest you are doing a hardware pass-through to the VM and the device now being selected is the disk controller.    If you have recently upgraded Unraid you need to be aware that hardware ID’s can change after the upgrade and need to be checked before starting any VM using hardware pass-through.

Sorry to revive such an old thread, but I was never able to start the VM back up. Even if I uncheck every devices on the "edit" screen for that VM, it crashes my whole server every time. Is there any other way to force remove the controller from the VM while still passing my capture card? Ideally without deleting and re-installing the VM? Here is the XML for that VM

<?xml version='1.0' encoding='UTF-8'?>
<domain type='kvm'>
  <name>Capture Card</name>
  <uuid>17e53729-4f3b-ecb0-642e-50cb56087e3c</uuid>
  <metadata>
    <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/>
  </metadata>
  <memory unit='KiB'>4194304</memory>
  <currentMemory unit='KiB'>4194304</currentMemory>
  <memoryBacking>
    <nosharepages/>
  </memoryBacking>
  <vcpu placement='static'>7</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='0'/>
    <vcpupin vcpu='1' cpuset='1'/>
    <vcpupin vcpu='2' cpuset='7'/>
    <vcpupin vcpu='3' cpuset='3'/>
    <vcpupin vcpu='4' cpuset='9'/>
    <vcpupin vcpu='5' cpuset='5'/>
    <vcpupin vcpu='6' cpuset='11'/>
  </cputune>
  <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/17e53729-4f3b-ecb0-642e-50cb56087e3c_VARS-pure-efi.fd</nvram>
  </os>
  <features>
    <acpi/>
    <apic/>
    <hyperv mode='custom'>
      <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='7' threads='1'/>
    <cache mode='passthrough'/>
  </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/CaptureCard/vdisk1.img'/>
      <target dev='hdc' bus='virtio'/>
      <boot order='1'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/user/Softwares/ISO/Microsoft Windows 10 Home and Pro x64 Clean ISO/en_windows_10_multiple_editions_x64_dvd_6846432.iso'/>
      <target dev='hda' bus='ide'/>
      <readonly/>
      <boot order='2'/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/user/Softwares/ISO/virtio-win-0.1.141-1.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='0x04' 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:a6:d2:e6'/>
      <source bridge='br0'/>
      <model type='virtio-net'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' 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='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>
    <audio id='1' type='none'/>
    <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>
    <memballoon model='virtio'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
    </memballoon>
  </devices>
</domain>

And here is the device I'm trying to parse (See attachment)

 

 

Thanks

 

Screen Shot 2022-08-14 at 11.56.11 AM.png

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.