jetsetjimbo

Ok so that worked and as you said the disk remained disabled but the other drives reappeared. I started the array ok, then stopped it again. Upon trying to start the array back up the web UI hung when mounting disks. The system still pings and I can telnet but I'm not sure how to go about shutting it down now. If I have to pull the plug I'm sure it will want to try a parity check on restart which can only be bad if a disk is disabled?

Thanks, I will try this and report back later. Would you expect to see the adjustment for the PCI speed in the bios of the motherboard or the controller card?

Apologies. Full diagnostics attached. Any help is gratefully received. tower-diagnostics-20161108-0904.zip

Hi all, I've recently had a drive redball which I replaced, then ran a successful parity check, as the attached log should show. I then attempted a pre-clear on the failed drive. This morning I've woken to find multiple drives showing errors and another (virtually new WD Red drive) marked as failed. Really not sure what to do from here. As things stand the system is still up and I have resisted doing a reboot. If anyone who really understands these logs could take a look and let me know what they think I'd be most grateful! James tower-syslog-20161108-0601.zip

Thanks Johnnie. What was throwing me is that currently the shares aren't showing anything, if said share spans over disc 7. I guess that must be down to the fact that something went wrong with the rebuild... I'll just remove the drive from the share, reformat and re-add and see if that sorts it.

If I format them and leave them added to the share set it should just recreate the shares across them correctly? I assume I then just copy the data back into the folders?

I have already managed to recover the data from the red balled disc onto and external drive on a machine with Ubuntu. The drive which is now showing as unmountable is the brand new one which has just successfully been through 2 cycles of preclear and then an attempted rebuild...

Yes, I still have the two failed drives. It's odd as disc 7 (the one which was being rebuilt as 4 seemed to have failed), despite not having the data on it and being displayed as having more space used than is the case, was actually returned to the array. It's shown as being online and has a folder structure on it which reflects the names of the shares that should be on it. Browsing to the root of a share which is spanned across that disc however shows nothing. The new disc 4, despite going through the motion of a rebuild process and showing a huge number of writes and no errors, is still still showing as unmountable.

Hi, I've used the same setup since 2012 without issues expanding and adding discs as I've gone. I have 9 (mix of 3tb and 2tb) disc plus a cache and am running v6.1.9. A week or so ago Unraid red balled one of my 3tb drives (disc 7). I order a new one, replaced it and began the process of rebuilding. As the process was ongoing I then started getting an ever increasing number of errors reporting on another of my 2tb data discs (disc 4). I allowed the build to complete at which point the system then red balled the 2tb (disc 4). When browsing the Tower and looking in at any share which was spread across either of the failed discs it showed as being completely empty although when browsing directly to the discs which weren't faulty there was obviously still data on them. I have since purchased a drive to replace disc 4, pre-cleared and and attempted to rebuild again. This took ~24 hours and then on completion the system states that the parity is valid but that disc 4 is unmountable. I am now able to see the content on the shares which spanned disc 4, minus anything that was actually stored on that disc obviously. Any shares that spanned disc 7 however still show as being empty. The unraid disc stats show that disc 7 is 15% of 3tb full but there is only 4Mb of data on there which comprised a couple of files in one directory which were on the disc before it failed. I have managed to recover data from the red balled drives on machine running a bootable copy of Ubuntu. I'm not sure what to do now to get disc 4 back up and running, should I just choose the option to format it? Also what action should I take to get the data usage on disc 7 to appear correctly, the shares displaying the actual content on the drives and how should I approach getting the data I've recovered back into the shares? I've attached what's in the syslog and would greatly appreciate any input. If I need to provide anymore information please let me know. Thanks James syslog.txt

Thanks - Do you then use categories in SAB to place completed downloads in specific folders on user? If so what path do you use?

I tried mnt/TV shows and ended up with files in: /config/Downloads/complete/mnt/TV Shows/ I'm not using Sickbeard at the moment, just trying to get it to work directly from SABnzb...

Thanks. I like what you've done here and it seems like a good option. I guess by pointing to /mnt/user it gives you the ability to go to any share on the server...correct? So rather than taking the time to create individual paths for the container you can just do this and point to really just about anywhere...right? Hi, Sorry to seem slow but could you explain exactly how you have things setup? My unraid server is called 'Tower', I then have a number of user shares; Video, TV Shows, Music, etc... In the docker I have the container volume /mnt set to /mnt/user. That should then expose all the user shares to the docker? Assuming this is the case what do I then need to put in the Category 'folder/path' field to get SAB to place the decompressed file in the correct folder? I've tried '/tv shows' but that just ends up in the config folder.

Indeed the OS is different but I wouldn't have thought it would make that much difference. The hardware is all the same I will check the driver versions later. The VM manages <30fps in project cars where as the be bare metal install of w7 is 50 - 60 (all the same quality settings).

Yes, I thought the number of cores / memory should have been enough not thave resulted in a significant reduction in performance. On the bare metal install of w7 the overall score is 5254 on the Unraid VM it's 4069 a difference of 1185. Which is way more than I would have expected?

I've setup a working VM with GPU pass through. All seems well other than I'm seeing a significant reduction in 3D performance in the VM compared to a bare metal install of the OS on the same machine. 3D mark is down ~1100 points. I'm using a Gigabyte 990FXA-UD5, FX6300 and Radeon R270. As far as I can tell I have everything set as it should be. I've tried setting up another VM with the Bios set to OVMF to no avail. The contents of my XML are below, any input would be most appreciated as I anticipating near bare metal performance. <domain type='kvm' id='6' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>SSDVM</name> <uuid>c0440d25-0b1d-3360-bfbb-2e73d2ac5eca</uuid> <metadata> <vmtemplate name="Custom" icon="windows.png" os="windows"/> </metadata> <memory unit='KiB'>6815744</memory> <currentMemory unit='KiB'>6815744</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>5</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='3'/> <vcpupin vcpu='4' cpuset='4'/> </cputune> <resource> <partition>/machine</partition> </resource> <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='5' 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/cache/SSDVM/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/IsoShare2/windows8_1(2).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/IsoShare2/virtio-win-0.1.96.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='usb0'/> <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='ide0'/> <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:00:9d:23'/> <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/SSDVM.org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <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='0xc01d'/> <address bus='4' device='4'/> </source> <alias name='hostdev0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x046a'/> <product id='0x0021'/> <address bus='4' device='3'/> </source> <alias name='hostdev1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x045e'/> <product id='0x028e'/> <address bus='4' device='2'/> </source> <alias name='hostdev2'/> </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=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=00:14.2,bus=root.1,addr=01.0'/> </qemu:commandline> </domain>