goinsnoopin

Jonp, At this point converting to XFS is my only option as I have already replaced the motherboard, memory, cpu, hard drive cables and power supply. The only original equipment is my hard drives and my unraid flash drive. System recently locked up and I grabbed a screenshot from htop...see the 500% CPU usage. I was unable to get diagnostics as when I typed this in telnet it said collecting information....then never returned anything...telnet session locked up. The odd thing is that the VM with windows7 was still running. Hopefully once I am stable, I will get back to the USB passthrough issues. Dan

Jonp, I never ran beta 7 or 8....I didn't convert until 6.01 stable was released...no betas were ever installed. That being said a couple of years ago I had a Sil3132 based add-on sata card. I ran this card for several months and then read postings from other users that this card was causing silent corruption issues. I pulled that card as soon as I learned of this...however could it have caused some background issues that I am still seeing now? Here is a link to that silent corruption issue: http://lime-technology.com/forum/index.php?topic=21052.0

Jonp, My unraid server is in rough shape. I had a disk get "red balled" and a second disk had 32 errors...but was still green. I will provide the USB settings over the next couple of days, as I want to get my server back up and running properly. I don't see any issues in my smart reports, I ran memtest overnight with no issues, and I have run reiserfsck on all disks and it is returning no corruptions found. Attached is my diagnostics captured just once I realized I had a disabled disk. I seem to get these unexplained drive crashes....I have had several over the past two years...but have never discovered the cause. At one point someone on the forums suggested possibly a power supply issue that randomly occurs and since ...I had a corsair TX750....so I swapped to a Corsair TX650 power supply from another PC just to eliminate that possibility. Also I installed all new Sata cables. Attached is my diagnostics in case you are interested in taking a peak. Dan tower-diagnostics-20151107-1556.zip

Jonp, I updated the xml to your latest suggestion and I am able to pass the usb controller through...just the same as my first attempt. However when I shut the VM down Unraid completely crashed...I was unable to refresh the webgui and I was unable to telnet in to the console. If I don't pass the USB controller, it runs flawlessly for days. Dan

Jonp, I tried the xml file and I got the following error: Execution error internal error: early end of file from monitor: possible problem: 2015-11-06T18:55:46.256102Z qemu-system-x86_64: -device vfio-pci,host=02:00.0,bus=root.2,addr=00.0,multifunction=on: Bus 'root.2' not found Any suggestions? Also thank you for the detailed explainations...based on your response, my plan it to solve the USB passthrough without the ACS override. That being said when I add a second GPU, I will need to move the USB PCIe controller card to another slot and it looks like at that time I will need to turn on the ACS Override. Thanks, Dan

So, I am making some progress but also have a major issue. I added the pci-stub for the PCIe USB controller. The card is in a PCI 3 slot and my motherboard CPU put it in the same IOMMU group as my GPU and the PCI bridge for the PCI x16 and PCI x8 controller. I added the PCI USB to the xml file and the the VM starts and passes the USB controller through to windows 7. Here is where it gets strange...after an hour of use, I installed a piece of software that needed a restart of the computer. From the taskbar I told windows to restart and after shutting down the screen went blank and never rebooted. But with whatever happened it took unraid down with it. I was unable to connect to the unraid web interface...I was also unable to telnet in to the console. I left it alone for an hour and decided to manually reboot. When the computer rebooted it did not load/boot unraid...it actually booted to a usb flash drive that I had inserted into the PCI USB controller that I just passed through. I pulled this flash drive and my PC booted to my bios as it did not see my unraid flash. once I pulled the only usb cable from the USB controller card that I passed through, only then did unraid come back. I then restarted my windows 7 VM...and then plugged the USB hub back into the passed through USB controller and it worked fine for a half hour...I then shut it down to see if all was well and it shutdown fine, I then attempted to restart the vm with no changes made and it crashed unraid completely again. Any suggestions? Do I need to pass the PCI bridge for the x16 and x8 ? So far I have done nothing with these. I was trying to avoid turning the ACS override on, but if having the USB controller in a PCI 3.0 slot is an issue, maybe I should move it to another slot and turn the ACS override on. Any suggestions would be greatly appreciated. Thanks, Dan Here is my xml: <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>HTPC</name> <uuid>cce39c7c-b747-11c4-8710-f9f195c532fe</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='0'/> <vcpupin vcpu='1' cpuset='1'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='3'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-2.3'>hvm</type> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> </hyperv> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='4' threads='1'/> </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/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'/> <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/ISOs/Win7_Pro_SP1_English_COEM_x64.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/ISOs/virtio-win-0.1.110.iso'/> <target dev='hdb' bus='ide'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' 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:2b:5a:f7'/> <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'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/HTPC.org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0'/> <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'/> </source> </hostdev> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x046d'/> <product id='0xc01d'/> </source> </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='0x06' function='0x0'/> </hostdev> <memballoon model='virtio'> <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=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on'/> </qemu:commandline> </domain> Here is my syslinux.cfg default /syslinux/menu.c32 menu title Lime Technology prompt 0 timeout 50 label unRAID OS menu default kernel /bzimage append pci-stub.ids=1b73:1100 initrd=/bzroot label unRAID OS Safe Mode (no plugins) kernel /bzimage append initrd=/bzroot unraidsafemode label Memtest86+ kernel /memtest Here is the output from my Tools...System Devices: System Devices PCI Devices 00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06) 00:01.1 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x8 Controller (rev 06) 00:14.0 USB controller: Intel Corporation 9 Series Chipset Family USB xHCI Controller 00:16.0 Communication controller: Intel Corporation 9 Series Chipset Family ME Interface #1 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection (2) I218-V 00:1a.0 USB controller: Intel Corporation 9 Series Chipset Family USB EHCI Controller #2 00:1b.0 Audio device: Intel Corporation 9 Series Chipset Family HD Audio Controller 00:1c.0 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 1 (rev d0) 00:1c.2 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 3 (rev d0) 00:1c.3 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 4 (rev d0) 00:1c.6 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 7 (rev d0) 00:1d.0 USB controller: Intel Corporation 9 Series Chipset Family USB EHCI Controller #1 00:1f.0 ISA bridge: Intel Corporation 9 Series Chipset Family Z97 LPC Controller 00:1f.2 SATA controller: Intel Corporation 9 Series Chipset Family SATA Controller [AHCI Mode] 00:1f.3 SMBus: Intel Corporation 9 Series Chipset Family SMBus Controller 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] 01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cedar HDMI Audio [Radeon HD 5400/6300 Series] 02:00.0 USB controller: Fresco Logic Device 1100 (rev 10) 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 11) 05:00.0 PCI bridge: ASMedia Technology Inc. Device 1184 06:01.0 PCI bridge: ASMedia Technology Inc. Device 1184 06:03.0 PCI bridge: ASMedia Technology Inc. Device 1184 06:05.0 PCI bridge: ASMedia Technology Inc. Device 1184 06:07.0 PCI bridge: ASMedia Technology Inc. Device 1184 08:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02) 0a:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02) 0b:00.0 USB controller: ASMedia Technology Inc. ASM1042A USB 3.0 Host Controller IOMMU Groups /sys/kernel/iommu_groups/0/devices/0000:00:00.0 /sys/kernel/iommu_groups/1/devices/0000:00:01.0 /sys/kernel/iommu_groups/1/devices/0000:00:01.1 /sys/kernel/iommu_groups/1/devices/0000:01:00.0 /sys/kernel/iommu_groups/1/devices/0000:01:00.1 /sys/kernel/iommu_groups/1/devices/0000:02:00.0 /sys/kernel/iommu_groups/2/devices/0000:00:14.0 /sys/kernel/iommu_groups/3/devices/0000:00:16.0 /sys/kernel/iommu_groups/4/devices/0000:00:19.0 /sys/kernel/iommu_groups/5/devices/0000:00:1a.0 /sys/kernel/iommu_groups/6/devices/0000:00:1b.0 /sys/kernel/iommu_groups/7/devices/0000:00:1c.0 /sys/kernel/iommu_groups/7/devices/0000:00:1c.2 /sys/kernel/iommu_groups/7/devices/0000:00:1c.3 /sys/kernel/iommu_groups/7/devices/0000:00:1c.6 /sys/kernel/iommu_groups/7/devices/0000:04:00.0 /sys/kernel/iommu_groups/7/devices/0000:05:00.0 /sys/kernel/iommu_groups/7/devices/0000:06:01.0 /sys/kernel/iommu_groups/7/devices/0000:06:03.0 /sys/kernel/iommu_groups/7/devices/0000:06:05.0 /sys/kernel/iommu_groups/7/devices/0000:06:07.0 /sys/kernel/iommu_groups/7/devices/0000:08:00.0 /sys/kernel/iommu_groups/7/devices/0000:0a:00.0 /sys/kernel/iommu_groups/7/devices/0000:0b:00.0 /sys/kernel/iommu_groups/8/devices/0000:00:1d.0 /sys/kernel/iommu_groups/9/devices/0000:00:1f.0 /sys/kernel/iommu_groups/9/devices/0000:00:1f.2 /sys/kernel/iommu_groups/9/devices/0000:00:1f.3 USB Devices Bus 006 Device 002: ID 8087:8001 Intel Corp. Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 012: ID 046d:c31c Logitech, Inc. Keyboard K120 Bus 003 Device 011: ID 046d:c01d Logitech, Inc. MX510 Optical Mouse Bus 003 Device 010: ID 5453:5038 Bus 003 Device 009: ID 05e3:0607 Genesys Logic, Inc. Logitech G110 Hub Bus 003 Device 004: ID 05e3:0607 Genesys Logic, Inc. Logitech G110 Hub Bus 003 Device 003: ID 1a40:0101 Terminus Technology Inc. Hub Bus 003 Device 002: ID 0566:3002 Monterey International Corp. Keyboard Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 002: ID 8087:8009 Intel Corp. Bus 005 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 003: ID 174c:2074 ASMedia Technology Inc. Bus 001 Device 002: ID 05dc:a701 Lexar Media, Inc. JumpDrive FireFly Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub SCSI Devices [0:0:0:0] disk LEXAR JD FIREFLY 1100 /dev/sda [1:0:0:0] disk ATA WDC WD30EFRX-68E 0A82 /dev/sdb [2:0:0:0] disk ATA ST3500630AS E /dev/sdc [3:0:0:0] disk ATA WDC WD10EADS-00L 1A01 /dev/sdd [4:0:0:0] disk ATA WDC WD20EFRX-68E 0A80 /dev/sde [5:0:0:0] disk ATA ST3320620AS C /dev/sdf [6:0:0:0] disk ATA Samsung SSD 840 6B0Q /dev/sdg [7:0:0:0] disk ATA WDC WD1001FALS-0 0K05 /dev/sdh [8:0:0:0] disk ATA WDC WD20EARX-008 AB51 /dev/sdi [10:0:0:0] disk ATA WDC WD10EARX-00N AB51 /dev/sdj [11:0:0:0] disk RDP8 SD/microSD 1.00 /dev/sdk [11:0:0:1] disk RDP8 MS/M2 1.00 /dev/sdl [11:0:0:2] disk RDP8 CF 1.00 /dev/sdm

Jonp, I did not set a pci-stub for the USB card. I have searched through the forums and I understand what I need to do....I am away from my server so I will have to try this later today. Quick question...should I do this and then go back and retest the card in each slot to see if that makes a difference for the IOMMU grouping....or is this more for allowing the device to be passed through so unraid does not take control of it? Dan

JonP, Thanks for the very detailed explanation! So I moved my PCIe USB card around and it stayed in the same IOMMU group with all of the PCI 2.0 slots. When I put it in the PCI 3.0 slot it ended up in the IOMMU group 1. However when I put it in this group the VM would not start...that being said I did not add the PCIe USB controller card to the xml...so maybe that is why it did not start. In looking at my group 1, should I attempt to pass it through or just proceed with the ACS overide? Dan

Here it is...it is in group 7 with a bunch of stuff. This info plus additional lspci info is in my original post...in the systemdevices.txt file. Also Bus 1 with the Lexar flash drive is UNRAID. Thanks for offering help! reason for modification...I updated bios and rebooted PC...the IOMMU groups changed. Also updated systemdevices.txt in the original post. Dan /sys/kernel/iommu_groups/0/devices/0000:00:00.0 /sys/kernel/iommu_groups/1/devices/0000:00:01.0 /sys/kernel/iommu_groups/1/devices/0000:01:00.0 /sys/kernel/iommu_groups/1/devices/0000:01:00.1 /sys/kernel/iommu_groups/2/devices/0000:00:14.0 /sys/kernel/iommu_groups/3/devices/0000:00:16.0 /sys/kernel/iommu_groups/4/devices/0000:00:19.0 /sys/kernel/iommu_groups/5/devices/0000:00:1a.0 /sys/kernel/iommu_groups/6/devices/0000:00:1b.0 /sys/kernel/iommu_groups/7/devices/0000:00:1c.0 /sys/kernel/iommu_groups/7/devices/0000:00:1c.2 /sys/kernel/iommu_groups/7/devices/0000:00:1c.3 /sys/kernel/iommu_groups/7/devices/0000:00:1c.6 /sys/kernel/iommu_groups/7/devices/0000:03:00.0 /sys/kernel/iommu_groups/7/devices/0000:04:00.0 /sys/kernel/iommu_groups/7/devices/0000:05:01.0 /sys/kernel/iommu_groups/7/devices/0000:05:03.0 /sys/kernel/iommu_groups/7/devices/0000:05:05.0 /sys/kernel/iommu_groups/7/devices/0000:05:07.0 /sys/kernel/iommu_groups/7/devices/0000:07:00.0 /sys/kernel/iommu_groups/7/devices/0000:08:00.0 /sys/kernel/iommu_groups/7/devices/0000:09:00.0 /sys/kernel/iommu_groups/7/devices/0000:0a:00.0 /sys/kernel/iommu_groups/8/devices/0000:00:1d.0 /sys/kernel/iommu_groups/9/devices/0000:00:1f.0 /sys/kernel/iommu_groups/9/devices/0000:00:1f.2 /sys/kernel/iommu_groups/9/devices/0000:00:1f.3

So I have read through the simple USB passthrough and the passthrough entire usb controller threads and am having a problem getting my USB PCIe USB controller to pass. Attached is a systemdevices.txt file with the iommu groups, pci devices, usb devices, etc. I also attached my vm xml file (saved as a text file so I can attach it) and system diagnostics. The error message I get is that it cannot assign the pci device. I am assuming this is because the PCI device I am trying to pass is grouped with a bunch of other devices. I understand there is the ACS override option, but I am not clear on the risks I would be taking and the help indicates to only do this if instructed. The addon PCI usb controller that I am trying to pass is the 08:00.0 USB controller: Fresco Logic Device 1100 (rev 10) motherboard is ASRock Z97 Extreme 6. Any suggestions would be greatly appreciated. htpc.txt tower-diagnostics-20151031-0854.zip systemdevices.txt

Smart report passed....reiserfsck ran and returned the result of no corruptions. I borrowed some sata cables from a friend and connected the balance of my drives to the motherboard and removed the supermicro AOCMV8SASLP card. Data rebuild is in progress. Dan

Over the past couple of months I have made several posts on issues I have had since upgrading to unraid 6.X....to the point where I am sick of seeing my own posts Over the weekend I decided to combine with windows 7 PC with my unraid tower and fully leverage unraid 6 and run windows 7 as a VM. Everything went well until today. After 2.5 days of uptime, I got a red "balled" X drive. It showed 7 errors in main status window. Diagnostics attached. Disk 3 was disabled and there is no smart report in the zipped diagnostics file. I assume I should start in maintenance mode and see if I can get a smart report...possibly also run reiserfsck on this disk? I assume it could be a cabling issue since I just rebuilt this machine. One item I forgot to prepare for in advance of combining the PC's was purchasing additional SATA cables. My plan was to run all of the drives off of the motherboard...but since I did not have enough sata cables, I was forced to use my supermicro AOCMV8SASLP card with the sata breakout cables. It just so happens disk 3 was connected to this add on card. I plan on ordering some new cable and pull this card. I guess at this point I will work through this troubleshooting guide. http://lime-technology.com/wiki/index.php/Troubleshooting#Hard_drive_failures Hopefully someone is willing to look at my syslog and see if anything jumps out at them. Thanks, Dan tower-diagnostics-20151028-1335.zip

I ran a reiser check on the cache drive and saw no errors. Thanks for the opinion on XFS, I think my plan will be to reformat my cache drive as XFS and leave my user shares set as they are now so they do not utilize the cache drive. For reference I have attached two diagnostics zip files. The one with the 20151020-1434 date contains a syslog that is littered with memory issues, call traces, killall smbd. The second syslog that contains the 20151023-0553 shows my system since then and as you can see the only syslog entries since the initial startup is the mover script initiating and then skipping the new vdisk share. Again my only change was stopping my movie and sagetv shares from utilizing the cache drive. I also deleted an appdata and Appdata share (one was my original unraid 5 Appdata share for plugins like logitech media server, and the other was an unraid 6 share for some dockers that I turned off while diagnosing issues). As you can see these syslogs are night and day. tower-diagnostics-20151020-1434.zip tower-diagnostics-20151023-0553.zip

So over the past couple of months this forum is littered with many emails about my unraid server and the webgui becoming unresponsive and multiple smbd processes running. Some syslogs have shown some memory issues, however memcheck when run shows no issues. My attempts to add memory to my older Supermicro C2SEE have been unsuccessful, so I have decided to smash my windows 7 PC and my unraid server together and fully embrace running win 7 as a VM. In preparation for this I created the ISO and Vdisk user shares....I also went through my existing shares and decided to remove the use cache drive setting for all of the shares with the exception of the new Vdisk user share. After doing this, I noticed something interesting...my syslog no longer has strange entries being made about memory or killing processes, etc. Htop and smbstatus and ps -ef don't show any smbd processes being spawned. Is there anything specific about how the cache drive is utilized in unraid 6 that could explain the issues I was having? The cache drive and all disks were formatted as reiserfs...I see that btrfs is needed for cache pools...is that a requirement for the cache drive in unraid 6 even if you are not utilizing a cache pool. Just curious...and thought it was worth mentioning as there are a lot of unresponsive webgui posts on the forum. Dan

I was wondering if an "experienced" forum member would be willing to review my syslog. I have attached the diagnostics.zip file. In particular the last 10 minutes of the syslog, I am seeing some entries that I don't recall seeing previously. Thanks, Dan tower-diagnostics-20151020-1850.zip

Still Crashing. I think I am going to move forward with combining my windows 7 pc with my unraid server and using VMs. I backed up my windows 7 PC and invoked the mover to push the 105 gb image file from my cache to my backup share and it locked my unraid server and samba. Here is a link to a screenshot of htop showing the 100% cpu usage on two cores. https://www.dropbox.com/s/0vi9npgmvplb896/unraid%20htop%2010162015.jpg?dl=0

I ran memtest overnight...17 passes no errors found. I reformatted and prepped a clean unraid install. Lets see what happens.

I just checked the diagnostics zip file....all the files have 0 bytes...so no information. I clean booted this morning so this run had the swapfile active. After the parity check, I typed powerdown from the console and that grabbed a syslog. I have attached it for reference. Dan syslog-20151008-191817.txt

I am not sure, there is a parity check in progress from the manual reboot performed this morning. That won't finish until tonight. My plan was to wait for that to finish and then pull the flash drive to check the diagnostics.zip and to back it up and prepare it from scratch. Dan

Did a manual reboot this AM. Unraid came up and I started the array which kicked off a parity check due to the unclean shutdown. Came home at lunch tried to browse unraid shares via samba on win 7 PC and I get the Tower is not accessible. The webgui is still functioning. I opened a telnet session and typed diagnostics and got the following: root@Tower:~# diagnostics Starting diagnostics collection... Warning: file_put_contents(): Only 0 of 15 bytes written, possibly out of free d isk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 36 Warning: file_put_contents(): Only 0 of 12 bytes written, possibly out of free d isk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 36 Warning: file_put_contents(): Only 0 of 10024 bytes written, possibly out of fre e disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 36 Warning: file_put_contents(): Only 0 of 89 bytes written, possibly out of free d isk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 36 Warning: file_put_contents(): Only 0 of 7698 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 36 Warning: file_put_contents(): Only 0 of 5784 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 36 Warning: file_put_contents(): Only 0 of 4638 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 36 Warning: file_put_contents(): Only 0 of 4581 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 36 Warning: file_put_contents(): Only 0 of 3738 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 36 Warning: file_put_contents(): Only 0 of 2 bytes written, possibly out of free di sk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 50 Warning: file_put_contents(): Only 0 of 34 bytes written, possibly out of free d isk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 52 Warning: file_put_contents(): Only 0 of 36 bytes written, possibly out of free d isk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 66 Warning: file_put_contents(): Only 0 of 36 bytes written, possibly out of free d isk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 66 Warning: file_put_contents(): Only 0 of 36 bytes written, possibly out of free d isk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 66 done. ZIP file '/boot/logs/tower-diagnostics-20151008-1249.zip' created. There is plenty of space on the flash drive. Just didn't know if this strange behavior meant anything. Wondering if I should backup the unraid USB and prepare it from scratch?

Poprin, I agree with you...in my troubleshooting, I stumbled upon Plex being set to update hourly. Ultimately my discs were not spinning down as my time was set to two hours. My reason for the automatic updates, is that I get TV recordings from SageTV, so shows are added automatically versus me manually adding files to my Plex library. At this point I am running the Plex updates manually, which is somewhat of an inconvenience if I am in bed looking to watch a TV show via a Roku and then realize the show hasn't been added requiring me to run downstairs to my PC to kick off a manual library update. I wish I could get my server to 4GB of ram...but for some strange reason it won't post. Supermicro confirmed that the ram should work based on its specs...even tried a single stick and it wont post...just a black screen with no beeps, no other indicators. Dan

Thanks everyone for your suggestions. I have run memtest and I get no errors. If you read through any of my old threads, I mentioned that this hardware has been working fine and stable for over 5 years. I have tried the swapfile plugin and configured it for 2GB, however I still get the crash. I am not using Jumbo frames. I have tried upgrading the ram from 2GB to 4GB...I have tried two different brands of Ram and neither of them will post....I just get a blank black screen with no beeps or anything. Called supermicro and they confirmed that the ram should work and they would talk to their bios engineer...and to date I have not heard back from them. NFS is an interesting option, but some people indicate that the NFS client is slow. Since my last post, I have had two additional crashes, one with the swap file active and one while booted to unraid safe mode. The safe mode crash was interesting as I was simply opening a folder on unraid from my Windows 7 x64 pro computer….so I know that Plex was not a culprit. I confirmed this by opening a telnet session and typing smbstatus. When I ran this I had several locked files (15 or so) which where all the root directory of the unraid share I was trying to open….previously when I thought it was just Plex, it was the individual files that were being scanned that were locked. So something is just not right with the samba connection. When this happened I ran htop and it showed the cpu at 400% (I assume this means that all 4 cores were at 100%). memory usage was not at 100%...however if I let the computer sit….6-12 hours later with the browser window open showing the tail of the syslog, entries get written about memory…once this occurs, I am no longer able to telnet into the console. Unraid 5 was flawless. I just don’t know what I should do moving forward. The constant crashing is an annoyance to say the least. As I see it my options are: 1. Revert to unraid 5 (I am having a hard time with this as I love the look, and concept of dockers, etc.) 2. Invest money to purchase new hardware to upgrade my unraid motherboard, memory and CPU. 3. Combine the hardware of my Windows 7 machine with my unraid box and fully leverage Unraid 6 and have windows 7 running as a VM. My windows 7 PC has an Asrock Z97 Extreme6 motherboard, 16 GB of Ram, i7 4790K CPU and a 250 GB SSD harddrive. Since I have more than 10 drives I believe I will still need my AOC SASLP MV8 card. I understand the concept of VM, but I have never implemented one, so I would have a lot of reading to do to get up to speed. For example I am unclear if I need a GPU beyond the integrated on built into the motherboard to run a windows 7 vm. We don’t play any games on the windows 7 PC, it is mainly used for Lightroom and basic internet surfing. I believe I have an old HD5450 video card floating around…maybe that would work?? Also the VM image files…am I making an image of my existing PC or am I starting with a stock Microsoft image and doing a fresh install? I am leaning towards option 3, but clearly I have a lot of learning to do. Any suggestions are greatly appreciated! Dan

Trurl, You are correct, the reason I didn't was that I only had a Celeron E1200 CPU, which could not handle the transcoding. I threw the Q9300 in my unraid box to see if that would address the 100% CPU issue/webgui crashing issue. The CPU in my windows 7 PC has an i7 4790K CPU, so it has more than enough power to handle the PLEX transcoding. I guess I could try Plex on unraid now that I have a Q9300...but I am now running a CPU that uses much more power than my E1200. It just seams strange to me that this setup worked just fine with Unraid 5. Dan

So I have been plagued with Webgui crashes since upgrading to the 6.x version of unraid. I have multiple threads on this issue, and I have marked my most recent thread as "Solved", however after 13 days of uptime I just had another crash. As mentioned in my old thread I made two changes at the same time: 1. upgraded CPU and 2. changed Plex Server Library to update daily (was previously set to hourly). Once I had uptime of 8 days I marked the thread as solved. Since I made two changes at the same time - I decided to go back and change the Plex Server Library update back to hourly. Needless to say my server did not make it to 14 days of uptime. Failure was the same...CPU usage in htop went to 100%. With a Q9300 cpu now installed...and stock unraid with no dockers/plugins etc...it doesnt make any sense that a Q9300 should go to 100% I started this thread to see if it would spark any discussions on why this Plex scanning would cause the spawning of the hundreds of smbd processes. Please note that Plex Server is running on a windows 7 x64 professional PC and connecting via samba. To me it seems like the crash occurs just after the mover script runs. I am going to attach my diagnostics, which has historically showed nothing, and a zip file containing the output of smbstatus with all the locked files...which must be getting locked as part of the Plex scan. Also here is a link to my old thread: http://lime-technology.com/forum/index.php?topic=42900.msg409193#msg409193 In the meantime, I have changed the Plex scanning back to daily. Also I have upgraded to unraid 6.13 as part of this manual reboot. Any suggestions would be greatly appreciated! Dan tower-diagnostics-20150930-0808.zip Unraid_putty_session_output.zip

Pickthenimp, My system is still Reiserfs. Still no crashes for me. My uptime is now at 8 days 2 hours and 37 minutes. Keeping my fingers crossed. Since I crossed the 7 day threshold, I am going to mark this thread as solved. It still baffles me, as I never had these issues with unraid 5 with the Celeron E1200. But at this point I am just happy for the stability I have had for the past week. Good luck to you! Dan