goinsnoopin

JonP, Any suggestions on how to move forward. In terms of buggy hardware...Do you mean the USB3 controller...or maybe the older GPU? I assume the motherboard and cpu are fine and the memory has tested out perfect. Its also interesting that the system is perfectly stable as long as I am not passing the USB3 controller through...so far no issues with the GPU. Is there anyway to troubleshoot this, logs, etc. as it is concerning that it takes down unraid. Dan

So I went through the process of replacing disk6 with a clean drive. The rebuild completed and I got the following warning notification at the end of the process: unRAID Data rebuild:: 13-12-2015 11:42 Notice [TOWER] - Data rebuild: finished (26 errors) Duration: unavailable (no parity-check entries logged) So what are these errors...is this telling me that the original 26 parity check errors may have been actual parity errors? At this point I have original disk6 plus the rebuilt disk6. I am assuming that I should proceed with a parity check and allow it to write the corrections. Would you agree? I have also attached a copy of my diagnostics for reference. Thanks again, Dan tower-diagnostics-20151213-1905.zip

Gary, I don't have any checksums (I did some reading and I can see where it make sense to have these...I am going to experiment with the unraid plugin). I have backups of only specific irreplaceable data...such as my photo shares. I don't have backups of my tv show recordings or movies. To be able to rebuild disk 6...I have some work to do....I need to mount a drive from another PC with the unassigned drives plugin...move the data to unraid...and then preclear this drive...then rebuild the data...so it may take a couple of days as I have a very busy weekend. I am hoping the sync error are from the hard reset...at the time I know some files were being synced with BTSync. Thanks for the advice!

Gary, I did check the parity is already valid box and I guess I was tired while writing my last message...I did uncheck the box that said write parity corrections to disk and then clicked the parity check button...so I believe I did it correct. It says parity check in progress. That being said, I am 62% complete and there are 25 sync errors. So I am not sure what to think. EDIT: I am now 100% complete and there were 26 sync errors. Any suggestions on a next step or interpreting the 26 sync errors? Also smart report came back clean on disk6 and I also went into maintenance mode and ran an xfs file system check and the status windows showed: Phase 1 - find and verify superblock... Phase 2 - using internal log - scan filesystem freespace and inode maps... - 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 - agno = 1 - agno = 2 - agno = 3 - 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 = 1 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting. Dan

Gary, I did as you suggested and when the array came up it was the exact same thing...disk6 red/disabled with a couple of errors and then disk 3 was showing errors but stayed green. I decided to pull my flash drive and make a backup of its contents and while making the zip of the contents...it hung up on two files....fsck0000 the file type was listed as rec in windows and there was no date or time. There was also a second file named fsck0001??? In any event I decided to reformat the flash drive and put a fresh install of unraid 6.16 on it. I am now able to follow your suggested procedure. So far disk6 is still green and I spot checked some of its contents and it seems fine. A non writing parity sync is underway...12 hours to go. Thanks again for your assistance. Dan

Gary, Thanks for taking the time to respond. I am on unraid 6.16...so I should good in that regard. I will give it a try when I get home.

Yes all drives show up in bios. They are also all available for assignment in the unraid webgui. But I haven't assigned yet as I am waiting for feedback. I am tempted to assign disks and trust parity...but not sure if that is wise

I have been working on getting usb pass through to work without crashing my entire unraid Tower and have seen some posts about Q35. My current VM template is set to use i440fx. In googling Q35, I see that this emulates the ICH9 chipset and provides better support for PCIe pass through. Being new to VMs...is there any down side to trying Q35? Dan

He is my situation. I have a red/disabled disk. Here is what I did to my system today: 1. I installed a new PCIe USB3 card for passthrough to my VM. I completed this task...passed the card through and tested it by plugging in a USB DVD drive and ripped a movie. I then converted the movie to mp4 and everything was fine for several hours. 2. Changed network settings...removed bonding...rebooted unraid entered bios and disabled the second NIC on my motherboard. After completing this item...unraid booted up and I immediately got a notification on the unraid webgui indicating that a disk6 was disabled...it also showed errors on disk3 but that disk was still green and it indicated that parity was invalid. I grabbed a diagnostic it is attached. I then attempted to shutdown unraid and it would not powerdown for over an hour. I manually powercycled the Tower and when unraid came backup there were no disks assigned...which I have never had this happen previously. Before I do anything, I thought I would solicit suggestions from the forum. tower-diagnostics-20151209-1250.zip

I recently converted from reiserfs to XFS. I currently have two WD Green drives in my array with that are not 4K aligned and they have the jumper on pins 5-6 to force the 1.5 GB PHY setting. Should I convert these drives to 4k aligned? While doing my filesystem conversion, I planned it so one of these drives is completely empty and globally excluded from my shares…so it is completely empty. Below is what I was thinking of doing and I would love feedback on this approach! I assume my first step is to take a photo of my drive assignments and to then do a new config then reassign parity correctly (I will triple check this)…and then reassign my data disks with the exception of the empty drives that I want to remove from the array (in my instance I want to remove one of the WD Green Drives that is not 4K aligned and a second disk that I no longer want in the array..an old 320 GB drive). Once the assignment is complete, I believe a parity sync will start. Once this is complete I could then shut down the server, pull the jumper on the WD Green Drive and then run preclear on this drive to get it 4K aligned. Once 4K aligned and preclear is O.K. I could add this disk back to the array. Next I would need to move files around to free up the second WD Green Drive and repeat the process above. Thanks in advance for any feedback. Dan

JonP, What hardware are you referring to being buggy? Any suggestions on how to proceed? My intent was to pass through the Inateck PCIe USB controller...this controller will have a single USB3 hub connected to it at my VM location for connecting flash drives, usb DVD etc. My hardware is as follows: Motherboard: AsRock Z97 Extreme6 (running most current bios 10/19/2015) CPU: i7 4790K Ram: (2) 8gb G. Skill Trident DDR3 GPU: HD5450 PCIe USB: Inateck PCIe USB 3.0 controller. Here is the link: http://www.amazon.com/Inateck-Express-Connector-Controller-Internal/dp/B00FPIMJEW

JonP, This thread took a turn...I have unraid stable...by converting disks from reiserfs to xfs. So I am getting back to this post below from earlier in the thread where you requested information from me as I am having an issue where passing a PCIe USB controller through is causing my entire unraid server to crash. A couple posts above I pasted dropbox links to photos of my USB settings in the bios per your request. Thanks for looking! Dan I'm curious about your BIOS settings for USB. Look for things like EHCI/XHCI handoff and other settings. Report back what settings are available, what they are currently set at, and what options are available for each.

JonP, As a follow up to my last post...I was looking through my XML file and realized that I was passing my keyboard and mouse though to the VM....once the VM was running with the PCIe USB controller passed through, I moved the usb cable that feeds the hub for the keyboard and mouse to the USB controller that I passed through. Would this cause the VM and unraid to crash? Dan

JonP, I went through the process of converting all my reiserfs drives to xfs. Unraid has been stable...so I am back to my USB Controller Passthough. In your last post you requested by bios USB settings. Here are some pictures (first is what everthing is set at...others are the choices as you click on each in bios): https://www.dropbox.com/s/5vo3z5yw6koett0/unraid%20usb.jpg?dl=0 https://www.dropbox.com/s/bgq2e5o51kaljhc/unraid%20usb-2.jpg?dl=0 https://www.dropbox.com/s/zag33m6rbgln2zp/unraid%20usb-3.jpg?dl=0 https://www.dropbox.com/s/mdmjwusph1pwplx/unraid%20usb-4.jpg?dl=0 https://www.dropbox.com/s/uxytej89ft3hdjc/unraid%20usb-5.jpg?dl=0 https://www.dropbox.com/s/spht1npomflso4t/unraid%20usb-6.jpg?dl=0 https://www.dropbox.com/s/u8zrh1c3u0cpcrh/unraid%20usb-7.jpg?dl=0 Let me know you thoughts on these settings...now that unraid is stable I would like to get the USB passthrough worked out. If you recall, I can get it to passthrough...but the VM locks up and it takes unraid down completely...can not telnet in, have to powercycle server. Thanks, Dan 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: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] 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 11) 04:00.0 PCI bridge: ASMedia Technology Inc. Device 1184 05:01.0 PCI bridge: ASMedia Technology Inc. Device 1184 05:03.0 PCI bridge: ASMedia Technology Inc. Device 1184 05:05.0 PCI bridge: ASMedia Technology Inc. Device 1184 05:07.0 PCI bridge: ASMedia Technology Inc. Device 1184 06:00.0 USB controller: Fresco Logic Device 1100 (rev 10) 07:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02) 09:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02) 0a:00.0 USB controller: ASMedia Technology Inc. ASM1042A USB 3.0 Host Controller IOMMU Groups Warning: Your system has booted with the PCIe ACS Override setting enabled. The below list doesn't not reflect the way IOMMU would naturally group devices. To see natural IOMMU groups for your hardware, go to the VM Settings page and set the PCIe ACS Override setting to No. /sys/kernel/iommu_groups/0/devices/0000:00:00.0 /sys/kernel/iommu_groups/1/devices/0000:00:01.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/8/devices/0000:00:1c.2 /sys/kernel/iommu_groups/9/devices/0000:00:1c.3 /sys/kernel/iommu_groups/10/devices/0000:00:1c.6 /sys/kernel/iommu_groups/11/devices/0000:00:1d.0 /sys/kernel/iommu_groups/12/devices/0000:00:1f.0 /sys/kernel/iommu_groups/12/devices/0000:00:1f.2 /sys/kernel/iommu_groups/12/devices/0000:00:1f.3 /sys/kernel/iommu_groups/13/devices/0000:01:00.0 /sys/kernel/iommu_groups/13/devices/0000:01:00.1 /sys/kernel/iommu_groups/14/devices/0000:03:00.0 /sys/kernel/iommu_groups/15/devices/0000:04:00.0 /sys/kernel/iommu_groups/16/devices/0000:05:01.0 /sys/kernel/iommu_groups/17/devices/0000:05:03.0 /sys/kernel/iommu_groups/18/devices/0000:05:05.0 /sys/kernel/iommu_groups/19/devices/0000:05:07.0 /sys/kernel/iommu_groups/20/devices/0000:06:00.0 /sys/kernel/iommu_groups/21/devices/0000:07:00.0 /sys/kernel/iommu_groups/22/devices/0000:09:00.0 /sys/kernel/iommu_groups/23/devices/0000:0a:00.0 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 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 005: ID 0566:3002 Monterey International Corp. Keyboard Bus 001 Device 014: ID 046d:c31c Logitech, Inc. Keyboard K120 Bus 001 Device 013: ID 046d:c01d Logitech, Inc. MX510 Optical Mouse Bus 001 Device 011: ID 05e3:0607 Genesys Logic, Inc. Logitech G110 Hub Bus 001 Device 006: ID 05e3:0607 Genesys Logic, Inc. Logitech G110 Hub Bus 001 Device 004: ID 1a40:0101 Terminus Technology Inc. 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 015: ID 5453:5038 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub XML File: <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> <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:arg value='-device'/> <qemu:arg value='vfio-pci,host=06:00.0,bus=root.1,addr=00.1,multifunction=on'/> </qemu:commandline> </domain>

Two weeks ago, I converted all of my reiserfs drives to XFS and my system has been running perfect! I just wanted to take a minute and thank those of you who took the time to respond to my numerous posts on Unraid 6 being unresponsive. Dan

Two weeks ago, I converted all of my reiserfs drives to XFS and my system has been running perfect! At this point I do not believe that any of my issues were related to Plex...rather some issue with the reiser file system. I just wanted to take a minute and thank those of you who took the time to respond to my numerous posts on Unraid 6 being unresponsive. Dan

Two weeks ago, I converted all of my reiserfs drives to XFS and my system has been running perfect! I just wanted to take a minute and thank those of you who took the time to respond to my numerous posts on Unraid 6 being unresponsive. Dan

Two weeks ago, I converted all of my reiserfs drives to XFS and my system has been running perfect! I just wanted to take a minute and thank those of you who took the time to respond to my numerous posts on Unraid 6 being unresponsive. Dan

I have two WD Green disks in my array that have the jumper on pins 5-6 to force the 1.5 GB PHY setting...these drives go back to the time when unraid did not support 4K aligned disks. Can I convert these drives to 4k aligned? It seems like this would be the time to do so. Any recommendations on how to accomplish this as part of my conversion from reiserfs to xfs? Dan

In looking at this a little closer...this folder refers to an appdata subfolder for an old instance of plex...I switched to another users docker...so I think I feel comfortable moving forward to the next disk. Dan

So I just started my conversion to xfs. Below is the output of my rsync verify.txt file...it lists a bunch of files that were skipped as they were non regular files. These files appear to be data from my plex docker. Before I proceed with erasing the source disk, I thought I would post to get some feedback. Here is the link to the file on my dropbox account as it exceeds the size permitted by the forum. https://www.dropbox.com/s/gawnbm26ydwyewl/verifydisk3.zip?dl=0 Thanks for looking. Dan

So what was the fix referenced in your post below?

While I am waiting for my 3 TB drive (arrives tomorrow), I am switching from a Windows 7 VM to a Windows 10 VM just to see if there is any difference. I had over a year of uptime with unraid 5...currently my uptime is less than 24 hours. It leaves me very concerned...I don't know if I can get the drive precleared in that time frame...also worried about the data transfer. Dan

Plupien79, Your description for the hard reset matches mine. There have not been any messages on the physical console. Sometimes I am able to to telnet to the console and grab a diagnostics file...sometimes I can not. Dan

Since upgrading to Unraid 6, I have had several instances of the webgui becoming unresponsive and smbd processes spawning. I have several posts about this on the forum. I am still having this issue and I wanted to post what I have done and what I plan to do moving forward. I have updated my hardware to the following: AsRock Z97 Extreme6, i7 4790K, 16 GB ram, Corsair TX650 Powersupply, HD5450 GPU for passthrough to my Win7 VM, all new Sata Cables and I removed my add on AOCSASMV8 Sata card. All my disks are reiserfs and I never installed any of the Unraid 6 betas. I have booted Unraid in safemode, and started the array in maintenance mode and have run reiserfsck on all disk and get no corruptions found. I am having the exact same crashes with this hardware as I did with my old Supermicro C2SEE motherboard and 2 GB of ram. The only difference this time around is that with my updated hardware I am running windows 7 64 bit pro as a VM. The interesting thing is that when the webgui crashes....the VM still runs and I can browse the web, etc as long as I dont try and read or write to the files with samba. Attached is the diagnostics for my most recent crash, as well as a screenshot from htop showing the CPU at 500%? The only two things that have not been replaced are the unraid flash drive (however I did run checkdisk on it and found no errors) and the drives themselves. I have ordered a new 3 TB drive and it will arrive on Friday. At this point I plan on attempting a conversion to the XFS file format. One item I mentioned to Jonp is that two years ago, I had an add on sata card that was based on the SIL3132 chipset that was found to be the cause of some silent corruptions. Not sure if that could have done something to my data, but figure I should give conversion to XFS a shot. Any sugestions, just let me know. Dan tower-diagnostics-20151111-0722.zip