goinsnoopin

I just wanted to post an update that I discovered a corruption on disk5, after running xfs repair my missing files returned under the lost+found folder. Here is a link to that other thread: http://lime-technology.com/forum/index.php?topic=47092.0 Still trying to understand the root cause, but wanted to provide feedback. lboregard has been great with followup via PM! Dan

I ran with the -v option. Here is the output of the actual repair: Phase 1 - find and verify superblock... - block cache size set to 1466696 entries Phase 2 - using internal log - zero log... zero_log: head block 320199 tail block 320199 - scan filesystem freespace and inode maps... sb_icount 132992, counted 132480 sb_ifree 808, counted 293 sb_fdblocks 385972351, counted 385965893 - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 entry " " in shortform directory 96 references invalid inode 0 entry contains illegal character in shortform dir 96 entry contains offset out of order in shortform dir 96 junking entry "" in directory inode 96 entry "I?-?" in shortform directory 96 references invalid inode 4294967295 junking entry "I?-?" in directory inode 96 entry " lost+fo" in shortform directory 96 references invalid inode 0 entry contains illegal character in shortform dir 96 junking entry "lost+fo" in directory inode 96 entry contains illegal character in shortform dir 96 junking entry "Reco" in directory inode 96 entry " Sage" in shortform directory 96 references invalid inode 0 entry contains illegal character in shortform dir 96 junking entry "Sage" in directory inode 96 entry contains illegal character in shortform dir 96 junking entry "UnbalanceT" in directory inode 96 entry " Unbalanc" in shortform directory 96 references invalid inode 0 entry #9 extends past end of dir in shortform dir 96, junking 1 entries corrected entry count in directory 96, was 10, now 9 corrected directory 96 size, was 164, now 153 corrected entry offsets in directory 96 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 2 - agno = 3 - agno = 6 - agno = 5 entry "S???H" in shortform directory 96 references non-existent inode 1712259720 junking entry "S???H" in directory inode 96 entry "??" in shortform directory 96 references non-existent inode 76087295 junking entry "??" in directory inode 96 entry "Unbalanc" in shortform directory 96 references non-existent inode 443107844 junking entry "Unbalanc" in directory inode 96 - agno = 4 - agno = 1 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 Phase 5 - rebuild AG headers and trees... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - traversal finished ... - moving disconnected inodes to lost+found ... disconnected inode 99, moving to lost+found disconnected dir inode 145256087, moving to lost+found disconnected dir inode 145256088, moving to lost+found disconnected dir inode 706744427, moving to lost+found disconnected dir inode 1074723220, moving to lost+found disconnected dir inode 1682641380, moving to lost+found disconnected dir inode 2228257969, moving to lost+found disconnected dir inode 2684472622, moving to lost+found disconnected dir inode 2684472624, moving to lost+found disconnected dir inode 3758146963, moving to lost+found Phase 7 - verify and correct link counts... resetting inode 96 nlinks from 18 to 9 resetting inode 145256089 nlinks from 2 to 11 XFS_REPAIR Summary Wed Mar 2 18:01:26 2016 Phase Start End Duration Phase 1: 03/02 18:00:46 03/02 18:00:53 7 seconds Phase 2: 03/02 18:00:53 03/02 18:01:13 20 seconds Phase 3: 03/02 18:01:13 03/02 18:01:23 10 seconds Phase 4: 03/02 18:01:23 03/02 18:01:23 Phase 5: 03/02 18:01:23 03/02 18:01:23 Phase 6: 03/02 18:01:23 03/02 18:01:23 Phase 7: 03/02 18:01:23 03/02 18:01:23 Total run time: 37 seconds done Once the repair completed I stopped the array and restarted it normally (i.e. not in maint mode). User Shares returned and it looks like I am allset. Coincidentally, in the lost+found directory all the missing files from running unbalance to move files from disk7 (now removed from my system) to disk5 are all here. So there must have been some corruption issue on disk 5 that caused issues with unbalance. Thanks to all that helped! Dan

I checked disk5. Phase 1 - find and verify superblock... Phase 2 - using internal log - scan filesystem freespace and inode maps... sb_icount 132992, counted 132480 sb_ifree 808, counted 293 sb_fdblocks 385972351, counted 385965893 - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 entry " " in shortform directory 96 references invalid inode 0 entry contains illegal character in shortform dir 96 entry contains offset out of order in shortform dir 96 would have junked entry "" in directory inode 96 entry "I?-?" in shortform directory 96 references invalid inode 4294967295 would have junked entry "I?-?" in directory inode 96 entry " lost+fo" in shortform directory 96 references invalid inode 0 entry contains illegal character in shortform dir 96 would have junked entry "lost+fo" in directory inode 96 entry contains illegal character in shortform dir 96 would have junked entry "Reco" in directory inode 96 entry " Sage" in shortform directory 96 references invalid inode 0 entry contains illegal character in shortform dir 96 would have junked entry "Sage" in directory inode 96 entry contains illegal character in shortform dir 96 would have junked entry "UnbalanceT" in directory inode 96 entry " Unbalanc" in shortform directory 96 references invalid inode 0 entry #15 extends past end of dir in shortform dir 96, would junk 1 entries would have corrected entry count in directory 96 from 16 to 15 would have corrected directory 96 size from 256 to 245 would have corrected entry offsets in directory 96 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 4 entry " " in shortform directory 96 references invalid inode 0 entry contains illegal character in shortform dir 96 entry contains offset out of order in shortform dir 96 - agno = 3 - agno = 7 would have junked entry "" in directory inode 96 entry "I?-?" in shortform directory 96 references invalid inode 4294967295 would have junked entry "I?-?" in directory inode 96 entry "S???H" in shortform directory 96 references non-existent inode 1712259720 would have junked entry "S???H" in directory inode 96 - agno = 6 - agno = 2 entry " lost+fo" in shortform directory 96 references invalid inode 0 entry contains illegal character in shortform dir 96 would have junked entry "lost+fo" in directory inode 96 entry " Reco" in shortform directory 96 references non-existent inode 2412055105 entry contains illegal character in shortform dir 96 would have junked entry "Reco" in directory inode 96 entry " Sage" in shortform directory 96 references invalid inode 0 entry contains illegal character in shortform dir 96 would have junked entry "Sage" in directory inode 96 entry " UnbalanceT" in shortform directory 96 references non-existent inode 3502158298 entry contains illegal character in shortform dir 96 would have junked entry "UnbalanceT" in directory inode 96 entry "??" in shortform directory 96 references non-existent inode 76087295 would have junked entry "??" in directory inode 96 entry "Unbalanc" in shortform directory 96 references non-existent inode 443107844 would have junked entry "Unbalanc" in directory inode 96 entry " Unbalanc" in shortform directory 96 references invalid inode 0 entry #15 extends past end of dir in shortform dir 96, would junk 1 entries would have corrected entry count in directory 96 from 16 to 15 would have corrected directory 96 size from 256 to 245 would have corrected entry offsets in directory 96 - agno = 5 - agno = 8 - agno = 9 - agno = 10 - agno = 11 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... entry "S???H" in shortform directory 96 references non-existent inode 1712259720 would junk entry entry "Reco" in shortform directory 96 references non-existent inode 2412055105 would junk entry entry "UnbalanceT" in shortform directory 96 references non-existent inode 3502158298 would junk entry entry "??" in shortform directory 96 references non-existent inode 76087295 would junk entry entry "Unbalanc" in shortform directory 96 references non-existent inode 443107844 would junk entry entry "Unbalanc?h" in shortform directory 96 references non-existent inode 12545 would junk entry - traversal finished ... - moving disconnected inodes to lost+found ... disconnected inode 99, would move to lost+found disconnected dir inode 145256087, would move to lost+found disconnected dir inode 145256088, would move to lost+found disconnected dir inode 706744427, would move to lost+found disconnected dir inode 1074723220, would move to lost+found disconnected dir inode 1682641380, would move to lost+found disconnected dir inode 2228257969, would move to lost+found disconnected dir inode 2684472622, would move to lost+found disconnected dir inode 2684472624, would move to lost+found disconnected dir inode 3758146963, would move to lost+found Phase 7 - verify link counts... would have reset inode 96 nlinks from 17 to 8 No modify flag set, skipping filesystem flush and exiting.

Good afternoon, I rebooted my server this afternoon, and after it came up, I decided to create a user share called "UnbalanceTest". I went through the usual steps of creating the share, noticed that it was visible in the webgui and then went on to start my VM. Unraid gave the warning that my image file was missing...so I went to main and noticed that my cache drive was unassigned. I have had the issue in the past where assigning drives in chrome resulted in the changes not being saved, so I opened firefox, stopped the array and assigned the cache drive, I then noticed that my user shares were missing. I started and stopped several times to see if they would be read from the disks and return and they did not...so I telneted into the console and browsed to the /mnt/user share and typed ls and I got an error saying that the file structure needs cleaning. So, I shut unraid down, pulled the flash drive and did a chkdsk and no errors were found. I then restarted and looked at the syslog and see the errors regarding corruption on disk5. I am attaching the first syslog (don't have full diagnostics..I am thankful for the syslog generated by powerdown). I also browsed to disk5 and typed ls -al and I can see a folder named "Unbalanc" in red letters (please note that this does not match my first sentence in this post)...there was also a second folder named "Unbalanc\033\004\210\377\377 Any suggestions on how to proceed? Thanks, Dan Added screenshot of ls -al of disk5 syslog-20160302-131748.zip

lboregard, Attached is a screenshot of the ls -al /mnt/disk5 The shares are not there? I did not see any errors in the logs either which is why I am confused. If disk5 did not have the folders for the user shares ISOs, SageTV, Recovered and lost+found, would it have created them? Dan

lboregard, I just ran the unbalance plugin and had an issue. I was copying all of my user shares that existing on disk7 to other disks as I needed to remove disk7 from my array. In my instance unbalance moved all the files to disk5 as it had the most free space. However I am noticing that some files did not move correctly. I noticed this when trying to start a VM, the iso file was missing from my ISOs share. It seems like the files for the ISOs, lost+found, SageTV and Recovered user shares did not get moved. I attached a screenshot of disk5's user share folders and as you can see these folders are missing, but if you look in the unbalance log they existed on the source disk. Do you have any suggestions? Does it mean that these files are gone? Dan unbalance.zip

What file system is on your disks in the array? If it is reiserfs, search the forums, many users (including myself) have had issues with reiserfs and converting the disks to xfs has solved the issue. Dan

So I just got a warning from unraid this morning regarding Disk 5 that it has current pending sectors: 1 So I know this is an issue and I need to resolve it ASAP. In general the recommendation is to replace the drive with a precleared spare...unfortunately, I do not have a spare, so I would have to order one (probably a 3TB WD Red that is on sale at newegg)...so it won't get here until next week and then I have a day of preclearing. So I was wondering, since I have free space on my array (2.2 TB), should I move the contents of Disk 5 (660 GB) to another drive, and then remove the drive from the array. The problem with this is that the array will not be protected while the parity is recalculating after removing the drive. I would love to not spend the money on a new drive right now...but don't want to be pound wise and penny foolish. Any suggestions would be greatly appreciated! Dan

I have witnessed this behavior and am so grateful that Johnnie.Black responded in my thread suggesting the use of another browser. My issues were not remembering the cache drive, changing the number of slots and also what Helmonder mentioned with the VNC password issues with a VM. Dan

Gridrunner, Just a thought, check to make sure the MSI interrupt is still set for both the video card and the hdmi sound. I noticed that when the Nvidia drivers were updated on my VM that the MSI interrupt settings were reset back to positive and I had to go back and reapply the registry fix. Dan

Thanks for looking, here are the XML files. Win7 XML <domain type='kvm' id='6' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>HTPC_AMD_USB</name> <uuid>af24cc45-3d50-476f-bc34-eaf87907be62</uuid> <metadata> <vmtemplate name="Custom" icon="windows7.png" os="windows7"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='1'/> <vcpupin vcpu='1' cpuset='2'/> <vcpupin vcpu='2' cpuset='3'/> <vcpupin vcpu='3' cpuset='4'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-2.3'>hvm</type> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='4' 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/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/Vdisks/HTPC/vdisk1.img'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <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/ISOs/Win7_Pro_SP1_English_COEM_x64.iso'/> <backingStore/> <target dev='hda' bus='ide'/> <readonly/> <boot order='2'/> <alias name='ide0-0-0'/> <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/ISOs/virtio-win-0.1.112.iso'/> <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='usb' index='0'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <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='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:02:56:5f'/> <source bridge='br0'/> <target dev='vnet1'/> <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/1'/> <target port='0'/> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/1'> <source path='/dev/pts/1'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/HTPC_AMD_No USB.org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='connected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x046d'/> <product id='0xc31c'/> <address bus='1' device='12'/> </source> <alias name='hostdev0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x046d'/> <product id='0xc01d'/> <address bus='1' device='11'/> </source> <alias name='hostdev1'/> </hostdev> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </memballoon> </devices> <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='ioh3420,bus=pci.0,addr=1c.0,multifunction=on,port=2,chassis=1,id=root.1'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=09:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=09:00.1,bus=root.1,addr=00.1'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=00:1b.0,bus=root.1,addr=01.0'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=05:00.0,bus=root.1,addr=00.2,multifunction=on'/> </qemu:commandline> </domain> Win 10 XML <domain type='kvm' id='5' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>Win10</name> <uuid>27eb1460-b644-a7cf-af68-0235db930e7f</uuid> <metadata> <vmtemplate name="Custom" icon="windows.png" os="windows"/> </metadata> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='4'/> <vcpupin vcpu='1' cpuset='5'/> <vcpupin vcpu='2' cpuset='6'/> <vcpupin vcpu='3' cpuset='7'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-2.3'>hvm</type> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='4' 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/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/Vdisks/Win10/vdisk1.img'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/Vdisks/Win10/Win10/vdisk2.img'/> <backingStore/> <target dev='hdd' bus='virtio'/> <alias name='virtio-disk3'/> <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/ISOs/Windows10_10_29_15.iso'/> <backingStore/> <target dev='hda' bus='ide'/> <readonly/> <boot order='2'/> <alias name='ide0-0-0'/> <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/ISOs/virtio-win-0.1.110.iso'/> <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='usb' index='0'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <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='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:1d:87:4f'/> <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 port='0'/> <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/Win10.org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='connected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </memballoon> </devices> <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='ioh3420,bus=pci.0,addr=1c.0,multifunction=on,port=2,chassis=1,id=root.1'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=01:00.1,bus=root.1,addr=00.1'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=07:00.0,bus=root.1,addr=00.2,multifunction=on'/> <qemu:arg value='-device'/> <qemu:arg value='usb-kbd'/> <qemu:arg value='-device'/> <qemu:arg value='usb-mouse'/> </qemu:commandline> </domain>

I am running unraid 6.1.8 and I started getting some strange errors in my log and noticed that Unraid killed my two running windows VMs due to Out of memory. Diagnostics attached. Any suggestions on how to troubleshoot the cause. Motherboard Asrock z97 Extreme6, i7 4790K, 16 GB ram, Two VMs running: Windows 7 Pro had 8GB ram assigned, Windows 10 Pro had 4 GB ram assigned. Dan Feb 12 19:46:44 Tower kernel: Out of memory: Kill process 22531 (qemu-system-x86) score 535 or sacrifice child Feb 12 19:46:44 Tower kernel: Killed process 22531 (qemu-system-x86) total-vm:13332856kB, anon-rss:8894432kB, file-rss:17840kB Feb 12 19:46:44 Tower kernel: qemu-system-x86 invoked oom-killer: gfp_mask=0xd0, order=0, oom_score_adj=0 Feb 12 19:46:44 Tower kernel: qemu-system-x86 cpuset=emulator mems_allowed=0 Feb 12 19:46:44 Tower kernel: CPU: 3 PID: 22699 Comm: qemu-system-x86 Tainted: G W 4.1.17-unRAID #1 Feb 12 19:46:44 Tower kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z97 Extreme6, BIOS P2.50 10/06/2015 Feb 12 19:46:44 Tower kernel: 0000000000000000 ffff88025c9ef6f8 ffffffff815f1df0 000000000000a840 Feb 12 19:46:44 Tower kernel: ffff88044cc3e480 ffff88025c9ef7a8 ffffffff815ee36c ffff8802513cad70 Feb 12 19:46:44 Tower kernel: ffff88044cc3e480 ffff88025c9ef8a0 ffff88025c9ef740 ffffffff815f489b Feb 12 19:46:44 Tower kernel: Call Trace: tower-diagnostics-20160212-2043.zip

I just want to report that plugin update notifications are not running for me as of 6.1.7. I also talked to a friend at work who indicated they stopped for him as well. As can be seen in my screenshots below, I receive notifications for drive temps, docker updates, array status....its just plugin updates that are not being sent to the browser or to email. Please note I just added a new video card for a VM and obviously I need to improve my cooling. Just wanted to let you know I understand the reason for all the drive temp warnings (kids just discovered PC gaming). Attached is my diagnostics. Here are links to relevant screenshots as in total they exceed the forum posting limit: https://www.dropbox.com/s/l69tuxehxk7vl0g/unraid%20plugins.PNG?dl=0 https://www.dropbox.com/s/g97yx51adwccr9f/unraid%20notifications.PNG?dl=0 https://www.dropbox.com/s/704r47kzzql4nl4/unraid%20notifications%20archive.PNG?dl=0 tower-diagnostics-20160208-2249.zip

Squid, Thanks for the link...since there are only two of them in my syslog and nothing seems to be wrong, I assume that I am O.K I don't think mcelog is installed, so maybe I will add that to see if I get any additional details. Dan

I have a new error in my syslog that I do not recognize: Feb 2 13:22:20 Tower kernel: mce: [Hardware Error]: Machine check events logged Any ideas about this...should I be worried. Full diagnostics is attached. Please note the system appears to be running fine. I also saw this: Feb 1 20:43:35 Tower kernel: CPU: 6 PID: 23849 Comm: qemu-system-x86 Not tainted 4.1.15-unRAID #1 Feb 1 20:43:35 Tower kernel: Call Trace: Thanks, Dan tower-diagnostics-20160202-2111.zip

So I have been trying different things...for the gparted .iso case I replaced the ubuntu install .iso with the gparted live cd.iso and changed the boot order accordingly and I am able to boot gparted...however after answering the setup questions, about keyboard, language etc, It gets to video settings and then stops. Attached is a screenshot of where it ends. I am using VNC for the graphics...maybe I should try passthrough? Maybe I am going in the wrong direction. I created an ubuntu LTS VM and the initial size was 5Gb and its too small. I want to increase it to 10Gb. I have made the change in the unraid VM to 10 Gb. How do I resize my file system to get the additional 5GB I added? I know how to do this with my windows VMs...I assumed I needed to run gparted to make the change...but could be wrong. Any suggestions would be greatly appreciated. Dan

So I have an existing working VM and I also have a .dd image of a bootable USB drive. How would I go about modifying my existing XML file to boot this .dd image file before my hard drive. My two use cases are to boot a clover image before going into OS X and my second use case is the need to boot the live gparted .iso file. Example OS X XML (In this example I believe I need to delete the kernal line as that is envoking the chameleon bootloader). <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>OSX-El-Capitan-10.11-VNC</name> <uuid>0ba39646-7ba1-4d41-9602-e2968b2fe36d</uuid> <metadata> <type>None</type> </metadata> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <vcpu placement='static'>2</vcpu> <cputune> <vcpupin vcpu='0' cpuset='1'/> <vcpupin vcpu='1' cpuset='2'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-2.3'>hvm</type> <kernel>/mnt/user/Vdisks/OSX_10_11/enoch_rev2795_boot</kernel> <boot dev='hd'/> <bootmenu enable='yes'/> </os> <features> <acpi/> </features> <cpu mode='custom' match='exact'> <model fallback='allow'>core2duo</model> </cpu> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw'/> <source file='/mnt/user/Vdisks/OSX_10_11/ElCapitan.img'/> <target dev='hda' bus='sata'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <controller type='usb' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='dmi-to-pci-bridge'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/> </controller> <controller type='pci' index='2' model='pci-bridge'> <address type='pci' domain='0x0000' bus='0x01' slot='0x01' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:00:20:30'/> <source bridge='br0'/> <model type='e1000-82545em'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/> </interface> <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='vmvga' vram='16384' heads='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> <memballoon model='none'/> </devices> <seclabel type='none' model='none'/> <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='usb-kbd'/> <qemu:arg value='-device'/> <qemu:arg value='usb-mouse'/> <qemu:arg value='-device'/> <qemu:arg value='isa-applesmc,osk='/> <qemu:arg value='-smbios'/> <qemu:arg value='type=2'/> </qemu:commandline> </domain>

Gridrunner, Thank you so much for your post. I plan on giving this a try...it will be much easier than the copy/paste method I have been using! Dan

I am looking for some suggestions on managing my VMs in particular the resulting XML files. Let me start by saying I am a newbie with VMs and have been experimenting with VMs in unraid over the past couple of months. It has been a lot of fun and I have a lot to learn. I find that I start with testing the VM utilizing VNC as the graphics card which is one xml then I experiment with GPU passthrough which is a different xml file and I end up wanting to save all these versions until I have a sucessful/stable VM. What I have been doing is emailing myself the xml for each of these and when I stop the VM and want to test something...I then paste the xml and then attempt to start the VM....then I end up going back to the original...so I have all of this back and forth (which can be difficult if I am using my smart phone to switch VMs). This method seems to be cumbersome, so I thought I would reach out and see what others were doing. It would be nice if we could save multiple versions of an xml file and select the one we want when starting a VM. As I am typing this...I started thinking... is it possible to create a new VM and just have it point to the same image file. I assume the xml file would need its own unique uuid in the xml. Any suggestions would be greatly appreciated! Dan

By any chance are your drives formatted with the ReiserFS? I can tell you that I had issues similar to yours back in October and November of last year. I provided HTOP screenshots showing shfs, logs and diagnostics, etc and no one was able to recreate my situation. I did see several other users posts indicating that conversion to XFS solved their issue, so I went through the process of converting my disks to XFS in November of 2015 and haven't had an issue since. For converting to XFS I followed this posting: http://lime-technology.com/forum/index.php?topic=37490.msg346739#msg346739 Dan

Aptalca, Thanks...Duh moment. The whole reason I was switching from Coppit's to your docker was that you had the ability to pass these variable through the template. Sorry. Dan

Marking this thread as solved...not sure I understand why...but Johnie.black's suggestion of using another browser has definitely worked. Thanks Johnie! Dan

I am going to mark this thread as solved. Johnie.black offered a suggestion in another thread I had started about my cache drive becoming unassigned that resolved this issue. Here is a link to that other thread. http://lime-technology.com/forum/index.php?topic=45946.msg438935#msg438935 Dan

Aptalca, I am attempting to install your DuckDNS docker, when I click the create button nothing happens. I have the config folder defined. I am not having any issues installing other dockers. Any help would be greatly appreciated. Thanks, Dan

Johnie.Black, I followed your suggestion and used firefox and everything works as it should. The cache drive stays assigned. I have tested a reboot cycle as well as a powerdown then restart. Do you know why this happens with Chrome? I dont remember seeing any warnings about this on the forums. Thanks for your help! Dan