Maticks

Members
  • Posts

    323
  • Joined

  • Last visited

Everything posted by Maticks

  1. in Shares in the webui it will show on the right how much space is free, this is based on the drives included in the share. click on your TV share. Have you included more than one drive in the include or is it set to all. optionally you might have excluded some drives.
  2. great job guys. works flawlessly and dockers seem to be a bit faster doing processing. Plex from clicking play to Transcoding and showing a video stream is about 2 seconds faster. loving the webui being in its own thread.
  3. Most linux OS's seem to have intel-ucode package loaded, i have noticed that Unraid hasn't installed this package by default. Since this patches meltdown it could be useful for people. You can usb any other distro to get the microcode patch but as a community thing shouldn't we have this package installed for security reasons.
  4. I had some issues with getting Nvidia GPU passthrough working i got an error starting the VM. I discovered turning on pcie ACS override and it looks like that split out the 1070 from the IOMMU group 1. Which means i can now start my VM with the graphics card.. However i started seeing these errors after i rebooted. Jan 9 16:11:50 Vault kernel: DMAR: DRHD: handling fault status reg 3 Jan 9 16:11:50 Vault kernel: DMAR: [DMA Write] Request device [04:00.1] fault addr 39d9c0000 [fault reason 02] Present bit in context entry is clear Jan 9 16:11:50 Vault kernel: DMAR: DRHD: handling fault status reg 3 Jan 9 16:11:50 Vault kernel: DMAR: [DMA Write] Request device [04:00.1] fault addr 39d9c0000 [fault reason 02] Present bit in context entry is clear Jan 9 16:11:50 Vault kernel: DMAR: DRHD: handling fault status reg 3 Jan 9 16:11:50 Vault kernel: DMAR: [DMA Write] Request device [04:00.1] fault addr 39d9c0000 [fault reason 02] Present bit in context entry is clear Jan 9 16:11:50 Vault kernel: DMAR: DRHD: handling fault status reg 3 Jan 9 16:11:50 Vault kernel: DMAR: [DMA Write] Request device [04:00.1] fault addr 39d9c0000 [fault reason 02] Present bit in context entry is clear Jan 9 16:11:50 Vault kernel: DMAR: DRHD: handling fault status reg 3 Jan 9 16:11:50 Vault kernel: DMAR: [DMA Write] Request device [04:00.1] fault addr 39d9c0000 [fault reason 02] Present bit in context entry is clear Jan 9 16:11:50 Vault kernel: DMAR: DRHD: handling fault status reg 3 Jan 9 16:11:50 Vault kernel: DMAR: [DMA Write] Request device [04:00.1] fault addr 39d9c0000 [fault reason 02] Present bit in context entry is clear Jan 9 16:11:50 Vault kernel: DMAR: DRHD: handling fault status reg 3 Jan 9 16:11:50 Vault kernel: DMAR: [DMA Write] Request device [04:00.1] fault addr 39d9c0000 [fault reason 02] Present bit in context entry is clear Jan 9 16:11:50 Vault kernel: DMAR: DRHD: handling fault status reg 3 Jan 9 16:11:50 Vault kernel: DMAR: [DMA Write] Request device [04:00.1] fault addr 39d9c0000 [fault reason 02] Present bit in context entry is clear Jan 9 16:11:50 Vault kernel: DMAR: DRHD: handling fault status reg 3 Jan 9 16:11:50 Vault kernel: DMAR: [DMA Write] Request device [04:00.1] fault addr 39d9c0000 [fault reason 02] Present bit in context entry is clear Jan 9 16:11:50 Vault kernel: DMAR: DRHD: handling fault status reg 3 Jan 9 16:11:50 Vault kernel: DMAR: [DMA Write] Request device [04:00.1] fault addr 39d9c0000 [fault reason 02] Present bit in context entry is clear I left it like this for 24 hours and then tonight, i lost a Parity Drive and Disk 1. I tried moving the data sata cables around and still had the same drives failed in the system. I have turned off ACS and ended up doing a new config to get the disk 1 back and then forced a party rebuild on the failed parity drive. There is no physical error it looks like ACS broke something here. Now i can't start my VM with GPU passthrough is there another option here ?
  5. i enabled this and had some disk DMA messages in the logs for 24 hours. all of a sudden one my parity drives just dropped out of the array and a data disk just died as well. Yet both disks are fine, i wouldn't turn this option on even though it also fixed my passthrough issues its now broken things.
  6. i dumped my vbios and put the rom in the VM. but i can only do that with PCIE ACS on, otherwise i cannot access the device. passthrough is working fine at the moment but i am seeing a heap of errors in my log files. Jan 9 19:08:26 Vault kernel: dmar_fault: 15 callbacks suppressed Jan 9 19:08:26 Vault kernel: DMAR: DRHD: handling fault status reg 3 Jan 9 19:08:26 Vault kernel: DMAR: [DMA Write] Request device [04:00.1] fault addr 39d9c0000 [fault reason 02] Present bit in context entry is clear Jan 9 19:08:33 Vault kernel: DMAR: DRHD: handling fault status reg 3 Jan 9 19:08:33 Vault kernel: DMAR: [DMA Write] Request device [04:00.1] fault addr 39d9c0000 [fault reason 02] Present bit in context entry is clear Jan 9 19:08:33 Vault kernel: DMAR: DRHD: handling fault status reg 3 Jan 9 19:08:33 Vault kernel: DMAR: [DMA Write] Request device [04:00.1] fault addr 39d9c0000 [fault reason 02] Present bit in context entry is clear Jan 9 19:08:33 Vault kernel: DMAR: DRHD: handling fault status reg 3 Jan 9 19:08:33 Vault kernel: DMAR: [DMA Write] Request device [04:00.1] fault addr 39d9c0000 [fault reason 02] Present bit in context entry is clear So trying to find a way to keep the passthrough working but get rid of the errors, there must be another way other than turning on PCIE ACS.
  7. it was suggested to use append vfio_iommu_type1.allow_unsafe_interrupts=1 initrd=/bzroot in the syslinix config file over pcie_acs_override=downstream will that work or break things more..
  8. actually one of my drives i can't see the temperature for it seems to be the SATA controller its plugged into that is throwing the above errors. Anyway i can keep the IOMMU groups divided so i can use my 1070 and exclude 04:00.1 from this division.
  9. ok so i turned on pcie ASC override and it looks like that split out the 1070 from the IOMMU group 1. Which means i can now start my VM with the graphics card.. some progress finally... But in my kernel logs i now see the below but all my drives are there and no errors. Jan 9 16:11:50 Vault kernel: DMAR: DRHD: handling fault status reg 3 Jan 9 16:11:50 Vault kernel: DMAR: [DMA Write] Request device [04:00.1] fault addr 39d9c0000 [fault reason 02] Present bit in context entry is clear Jan 9 16:11:50 Vault kernel: DMAR: DRHD: handling fault status reg 3 Jan 9 16:11:50 Vault kernel: DMAR: [DMA Write] Request device [04:00.1] fault addr 39d9c0000 [fault reason 02] Present bit in context entry is clear Jan 9 16:11:50 Vault kernel: DMAR: DRHD: handling fault status reg 3 Jan 9 16:11:50 Vault kernel: DMAR: [DMA Write] Request device [04:00.1] fault addr 39d9c0000 [fault reason 02] Present bit in context entry is clear Jan 9 16:11:50 Vault kernel: DMAR: DRHD: handling fault status reg 3 Jan 9 16:11:50 Vault kernel: DMAR: [DMA Write] Request device [04:00.1] fault addr 39d9c0000 [fault reason 02] Present bit in context entry is clear Jan 9 16:11:50 Vault kernel: DMAR: DRHD: handling fault status reg 3 Jan 9 16:11:50 Vault kernel: DMAR: [DMA Write] Request device [04:00.1] fault addr 39d9c0000 [fault reason 02] Present bit in context entry is clear Jan 9 16:11:50 Vault kernel: DMAR: DRHD: handling fault status reg 3 Jan 9 16:11:50 Vault kernel: DMAR: [DMA Write] Request device [04:00.1] fault addr 39d9c0000 [fault reason 02] Present bit in context entry is clear Jan 9 16:11:50 Vault kernel: DMAR: DRHD: handling fault status reg 3 Jan 9 16:11:50 Vault kernel: DMAR: [DMA Write] Request device [04:00.1] fault addr 39d9c0000 [fault reason 02] Present bit in context entry is clear Jan 9 16:11:50 Vault kernel: DMAR: DRHD: handling fault status reg 3 Jan 9 16:11:50 Vault kernel: DMAR: [DMA Write] Request device [04:00.1] fault addr 39d9c0000 [fault reason 02] Present bit in context entry is clear Jan 9 16:11:50 Vault kernel: DMAR: DRHD: handling fault status reg 3 Jan 9 16:11:50 Vault kernel: DMAR: [DMA Write] Request device [04:00.1] fault addr 39d9c0000 [fault reason 02] Present bit in context entry is clear Jan 9 16:11:50 Vault kernel: DMAR: DRHD: handling fault status reg 3 Jan 9 16:11:50 Vault kernel: DMAR: [DMA Write] Request device [04:00.1] fault addr 39d9c0000 [fault reason 02] Present bit in context entry is clear
  10. Hi Guys, First i had an issue with my i5 not support IOMMU so i bought an i7. Getting closer i can select my graphics card from the list but it throws an error when i start. I have tried to follow the guide and i get this error. can anyone please help? root@Vault:/sys/bus/pci/devices/0000:02:00.0# cat rom > /mnt/user/Downloads/msi1070.dump cat: rom: Input/output error 02:00.0 VGA compatible controller: NVIDIA Corporation GP104 [GeForce GTX 1070] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device 330c Flags: fast devsel Memory at f4000000 (32-bit, non-prefetchable) [disabled] Memory at e0000000 (64-bit, prefetchable) [disabled] Memory at f0000000 (64-bit, prefetchable) [disabled] I/O ports at d000 [disabled] Expansion ROM at f5000000 [disabled by cmd] Capabilities: [60] Power Management version 3 Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [78] Express Legacy Endpoint, MSI 00 Capabilities: [100] Virtual Channel Capabilities: [250] Latency Tolerance Reporting Capabilities: [128] Power Budgeting <?> Capabilities: [420] Advanced Error Reporting Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?> Capabilities: [900] #19 When i start the VM i get this error. Execution error internal error: qemu unexpectedly closed the monitor: 2018-01-09T04:29:08.439513Z qemu-system-x86_64: -device vfio-pci,host=02:00.0,id=hostdev0,bus=pci.0,addr=0x5: vfio: error, group 1 is not viable, please ensure all devices within the iommu_group are bound to their vfio bus driver. 2018-01-09T04:29:08.439531Z qemu-system-x86_64: -device vfio-pci,host=02:00.0,id=hostdev0,bus=pci.0,addr=0x5: vfio: failed to get group 1 2018-01-09T04:29:08.439540Z qemu-system-x86_64: -device vfio-pci,host=02:00.0,id=hostdev0,bus=pci.0,addr=0x5: Device initialization failed Here is my VM XML file is there an error here, have i missed something? i have tried to run it in Slot 1 and just moved it to Slot 2 but that has made no difference. <domain type='kvm'> <name>Miner</name> <uuid>96ea6ac6-0537-c284-a455-d1b5d6d15a27</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>3</vcpu> <cputune> <vcpupin vcpu='0' cpuset='4'/> <vcpupin vcpu='1' cpuset='5'/> <vcpupin vcpu='2' cpuset='6'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-2.7'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/96ea6ac6-0537-c284-a455-d1b5d6d15a27_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='3' 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/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/Vm/Miner/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/Windows10.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.126-2.iso'/> <target dev='hdb' bus='ide'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'/> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:2c:17:3a'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <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> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x02' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </hostdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </memballoon> </devices> </domain>
  11. i have an i5-4670K it supports vt-x but not vt-d.. I can't pass through graphics cards etc but if i purchased a 2 port Intel PCI-x Network card can i pass through the two ports on the card to the VM? I want to setup PFSense on the Unraid Server but i want to allocate it these two ports for WAN and LAN i can plug it back into my switch and have it completely dedicated interfaces. I am just not sure if i can or can't pass through Network Interfaces ?
  12. Any news on when 6.4 is released ?
  13. After some testing with my system i noticed that with my i5 4670k i am not getting my configured speed. the processor is default 3.4Ghz with 3.8Ghz Boost, i have been stable at 4.6Ghz for years on windows. however my CPUInfo shows 3.4 Only. cat /proc/cpuinfo | grep -i mhz cpu MHz : 3400.000 cpu MHz : 3396.679 cpu MHz : 3398.754 cpu MHz : 3400.000 Following some instructions on here i turned on Performance in the Tips and Tricks plugin. That seem to do the trick with the clock speeds going up to 4.6Ghz. But then the system won't boot i get the error "Kernel panic - not syncing: Timeout: Not all cpus entered broadcast exception handler" Which is apparently to do with having Intel Speed Step on, so when i turn that off i am back to the start i have 3.4Ghz again even with Performance on in Tips and Tricks. Anyone know how i can have my cake and eat it too? Processor Title Information Processor Information Socket Designation: SOCKET 0 Type: Central Family: Core i5 Manufacturer: Intel ID: C3 06 03 00 FF FB EB BF Signature: Type 0, Family 6, Model 60, Stepping 3 Flags: FPU (Floating-point unit on-chip) VME (Virtual mode extension) DE (Debugging extension) PSE (Page size extension) TSC (Time stamp counter) MSR (Model specific registers) PAE (Physical address extension) MCE (Machine check exception) CX8 (CMPXCHG8 instruction supported) APIC (On-chip APIC hardware supported) SEP (Fast system call) MTRR (Memory type range registers) PGE (Page global enable) MCA (Machine check architecture) CMOV (Conditional move instruction supported) PAT (Page attribute table) PSE-36 (36-bit page size extension) CLFSH (CLFLUSH instruction supported) DS (Debug store) ACPI (ACPI supported) MMX (MMX technology supported) FXSR (FXSAVE and FXSTOR instructions supported) SSE (Streaming SIMD extensions) SSE2 (Streaming SIMD extensions 2) SS (Self-snoop) HTT (Multi-threading) TM (Thermal monitor supported) PBE (Pending break enabled) Version: Intel® Core™ i5-4670K CPU @ 3.40GHz Voltage: 1.2 V External Clock: 100 MHz Max Speed: 3800 MHz Current Speed: 3400 MHz Status: Populated, Enabled Upgrade: Socket BGA1155 Serial Number: Not Specified Asset Tag: Fill By OEM Part Number: Fill By OEM Core Count: 4 Core Enabled: 4 Thread Count: 4 Characteristics: 64-bit capable
  14. A tickbox for running Balance on the Cache after Mover runs would be nice. I am running into BTRFS bugs with cache space being filled. more evident after installing a second cache drive then when i ran a single drive. A Balance stops it from throwing disk full errors. I only need a Balance after my cache is cleared.
  15. maybe we just need balance to run after mover runs..
  16. got to the bottom of the issue... its BUGFS. btrfs filesystem show: Label: none uuid: 8e82d82d-f6f6-45d7-9e5a-d389fb0e0bb3 Total devices 2 FS bytes used 31.45GiB devid 1 size 238.47GiB used 201.06GiB path /dev/sdl1 devid 3 size 238.47GiB used 201.06GiB path /dev/sdo1 The filesystem show is filling up it was at 201GB when it hits 235GB it starts throwing those errors. Given my average data patterns on the cache it makes sense why it happens on write times. My filesystem shows 31GB is usage though. Manually forcing a balance btrfs balance start -dusage=80 /mnt/cache Done, had to relocate 107 out of 143 chunks btrfs filesystem show: Label: none uuid: 8e82d82d-f6f6-45d7-9e5a-d389fb0e0bb3 Total devices 2 FS bytes used 31.41GiB devid 1 size 238.47GiB used 35.06GiB path /dev/sdl1 devid 3 size 238.47GiB used 35.06GiB path /dev/sdo1 No more cache errors I think ill have to convert this to XFS or something..
  17. Ok changed out the SATA Power cable and changed out the SATA Data cable. ran for 10 hours no issues reading and writing then this happened in the syslog. Nov 21 10:42:36 Vault kernel: ata3.00: exception Emask 0x0 SAct 0x7fffffff SErr 0x0 action 0x6 frozen Nov 21 10:42:36 Vault kernel: ata3.00: failed command: WRITE FPDMA QUEUED Nov 21 10:42:36 Vault kernel: ata3.00: cmd 61/00:00:c0:42:7c/05:00:00:00:00/40 tag 0 ncq dma 655360 out Nov 21 10:42:36 Vault kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Nov 21 10:42:36 Vault kernel: ata3.00: status: { DRDY } Nov 21 10:42:36 Vault kernel: ata3.00: failed command: WRITE FPDMA QUEUED Nov 21 10:42:36 Vault kernel: ata3.00: cmd 61/00:08:c0:47:7c/05:00:00:00:00/40 tag 1 ncq dma 655360 out Nov 21 10:42:36 Vault kernel: res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Nov 21 10:42:36 Vault kernel: ata3.00: status: { DRDY } Nov 21 10:42:36 Vault kernel: ata3.00: failed command: WRITE FPDMA QUEUED Nov 21 10:42:36 Vault kernel: ata3.00: cmd 61/00:10:c0:4c:7c/05:00:00:00:00/40 tag 2 ncq dma 655360 out Nov 21 10:42:36 Vault kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Nov 21 10:42:36 Vault kernel: ata3.00: status: { DRDY } Nov 21 10:42:36 Vault kernel: ata3.00: failed command: WRITE FPDMA QUEUED Nov 21 10:42:36 Vault kernel: ata3.00: cmd 61/00:18:c0:51:7c/06:00:00:00:00/40 tag 3 ncq dma 786432 out Nov 21 10:42:36 Vault kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Nov 21 10:42:36 Vault kernel: ata3.00: status: { DRDY } Nov 21 10:42:36 Vault kernel: ata3.00: failed command: WRITE FPDMA QUEUED Nov 21 10:42:36 Vault kernel: ata3.00: cmd 61/00:20:c0:57:7c/07:00:00:00:00/40 tag 4 ncq dma 917504 out Nov 21 10:42:36 Vault kernel: res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Nov 21 10:42:36 Vault kernel: ata3.00: status: { DRDY } Nov 21 10:42:36 Vault kernel: ata3.00: failed command: WRITE FPDMA QUEUED Nov 21 10:42:36 Vault kernel: ata3.00: cmd 61/00:28:c0:5e:7c/05:00:00:00:00/40 tag 5 ncq dma 655360 out Nov 21 10:42:36 Vault kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Nov 21 10:42:36 Vault kernel: ata3.00: status: { DRDY } Nov 21 10:42:36 Vault kernel: ata3.00: failed command: WRITE FPDMA QUEUED Nov 21 10:42:36 Vault kernel: ata3.00: cmd 61/08:30:50:10:62/04:00:00:00:00/40 tag 6 ncq dma 528384 out Nov 21 10:42:36 Vault kernel: res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Nov 21 10:42:36 Vault kernel: ata3.00: status: { DRDY } Nov 21 10:42:36 Vault kernel: ata3: hard resetting link Nov 21 10:42:42 Vault kernel: ata3: link is slow to respond, please be patient (ready=0) Nov 21 10:42:46 Vault kernel: ata3: COMRESET failed (errno=-16) Nov 21 10:42:46 Vault kernel: ata3: hard resetting link Nov 21 10:42:52 Vault kernel: ata3: link is slow to respond, please be patient (ready=0) Nov 21 10:42:56 Vault kernel: ata3: COMRESET failed (errno=-16) Nov 21 10:42:56 Vault kernel: ata3: hard resetting link Nov 21 10:43:02 Vault kernel: ata3: link is slow to respond, please be patient (ready=0) Nov 21 10:43:31 Vault kernel: ata3: COMRESET failed (errno=-16) Nov 21 10:43:31 Vault kernel: ata3: limiting SATA link speed to 3.0 Gbps Nov 21 10:43:31 Vault kernel: ata3: hard resetting link Nov 21 10:43:36 Vault kernel: ata3: COMRESET failed (errno=-16) Nov 21 10:43:36 Vault kernel: ata3: reset failed, giving up Nov 21 10:43:36 Vault kernel: ata3.00: disabled Nov 21 10:43:36 Vault kernel: ata3: EH complete Nov 21 10:43:36 Vault kernel: sd 4:0:0:0: [sdg] tag#7 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Nov 21 10:43:36 Vault kernel: sd 4:0:0:0: [sdg] tag#7 CDB: opcode=0x2a 2a 00 00 7c 3d c0 00 05 00 00 Nov 21 10:43:36 Vault kernel: blk_update_request: I/O error, dev sdg, sector 8142272 Nov 21 10:43:36 Vault kernel: btrfs_dev_stat_print_on_error: 47087 callbacks suppressed Nov 21 10:43:36 Vault kernel: BTRFS error (device sdh1): bdev /dev/sdg1 errs: wr 14752897, rd 13109798, flush 62525, corrupt 2409818, gen 6908 Nov 21 10:43:36 Vault kernel: BTRFS error (device sdh1): bdev /dev/sdg1 errs: wr 14752898, rd 13109798, flush 62525, corrupt 2409818, gen 6908 Nov 21 10:43:36 Vault kernel: BTRFS error (device sdh1): bdev /dev/sdg1 errs: wr 14752899, rd 13109798, flush 62525, corrupt 2409818, gen 6908 Nov 21 10:43:36 Vault kernel: BTRFS error (device sdh1): bdev /dev/sdg1 errs: wr 14752900, rd 13109798, flush 62525, corrupt 2409818, gen 6908 Nov 21 10:43:36 Vault kernel: BTRFS error (device sdh1): bdev /dev/sdg1 errs: wr 14752901, rd 13109798, flush 62525, corrupt 2409818, gen 6908 Nov 21 10:43:36 Vault kernel: BTRFS error (device sdh1): bdev /dev/sdg1 errs: wr 14752902, rd 13109798, flush 62525, corrupt 2409818, gen 6908 Nov 21 10:43:36 Vault kernel: BTRFS error (device sdh1): bdev /dev/sdg1 errs: wr 14752903, rd 13109798, flush 62525, corrupt 2409818, gen 6908 Nov 21 10:43:36 Vault kernel: BTRFS error (device sdh1): bdev /dev/sdg1 errs: wr 14752904, rd 13109798, flush 62525, corrupt 2409818, gen 6908 Nov 21 10:43:36 Vault kernel: BTRFS error (device sdh1): bdev /dev/sdg1 errs: wr 14752905, rd 13109798, flush 62525, corrupt 2409818, gen 6908 Nov 21 10:43:36 Vault kernel: BTRFS error (device sdh1): bdev /dev/sdg1 errs: wr 14752906, rd 13109798, flush 62525, corrupt 2409818, gen 6908 Nov 21 10:43:36 Vault kernel: sd 4:0:0:0: [sdg] tag#8 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Nov 21 10:43:36 Vault kernel: sd 4:0:0:0: [sdg] tag#8 CDB: opcode=0x2a 2a 00 00 7c 38 c0 00 05 00 00 Nov 21 10:43:36 Vault kernel: blk_update_request: I/O error, dev sdg, sector 8140992 Nov 21 10:43:36 Vault kernel: sd 4:0:0:0: [sdg] tag#9 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Nov 21 10:43:36 Vault kernel: sd 4:0:0:0: [sdg] tag#9 CDB: opcode=0x2a 2a 00 00 7c 31 c0 00 07 00 00 Nov 21 10:43:36 Vault kernel: blk_update_request: I/O error, dev sdg, sector 8139200 Nov 21 10:43:36 Vault kernel: sd 4:0:0:0: [sdg] tag#10 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Nov 21 10:43:36 Vault kernel: sd 4:0:0:0: [sdg] tag#10 CDB: opcode=0x2a 2a 00 00 7c 28 40 00 09 80 00 Nov 21 10:43:36 Vault kernel: blk_update_request: I/O error, dev sdg, sector 8136768 Nov 21 10:43:36 Vault kernel: sd 4:0:0:0: [sdg] tag#11 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Nov 21 10:43:36 Vault kernel: sd 4:0:0:0: [sdg] tag#11 CDB: opcode=0x28 28 00 05 eb 8c c0 00 02 60 00 Nov 21 10:43:36 Vault kernel: blk_update_request: I/O error, dev sdg, sector 99323072 Nov 21 10:43:36 Vault kernel: blk_update_request: I/O error, dev sdg, sector 159799760 Nov 21 10:43:36 Vault kernel: BTRFS warning (device sdh1): lost page write due to IO error on /dev/sdg1 Nov 21 10:43:36 Vault kernel: BTRFS warning (device sdh1): lost page write due to IO error on /dev/sdg1 Nov 21 10:43:36 Vault kernel: BTRFS warning (device sdh1): lost page write due to IO error on /dev/sdg1 Nov 21 10:43:36 Vault kernel: BTRFS warning (device sdh1): lost page write due to IO error on /dev/sdg1 Nov 21 10:43:37 Vault kernel: BTRFS warning (device sdh1): lost page write due to IO error on /dev/sdg1 Nov 21 10:43:37 Vault kernel: BTRFS warning (device sdh1): lost page write due to IO error on /dev/sdg1 Nov 21 10:43:37 Vault kernel: BTRFS warning (device sdh1): lost page write due to IO error on /dev/sdg1 Nov 21 10:43:37 Vault kernel: BTRFS warning (device sdh1): lost page write due to IO error on /dev/sdg1 Nov 21 10:43:37 Vault kernel: BTRFS warning (device sdh1): lost page write due to IO error on /dev/sdg1 Nov 21 10:43:37 Vault kernel: BTRFS warning (device sdh1): lost page write due to IO error on /dev/sdg1 Nov 21 10:43:41 Vault kernel: scsi_io_completion: 123230 callbacks suppressed Nov 21 10:43:41 Vault kernel: sd 4:0:0:0: [sdg] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Nov 21 10:43:41 Vault kernel: sd 4:0:0:0: [sdg] tag#0 CDB: opcode=0x28 28 00 03 34 a1 b0 00 02 10 00 Nov 21 10:43:41 Vault kernel: blk_update_request: 123285 callbacks suppressed Nov 21 10:43:41 Vault kernel: blk_update_request: I/O error, dev sdg, sector 53780912 Nov 21 10:43:41 Vault kernel: btrfs_dev_stat_print_on_error: 241929 callbacks suppressed Nov 21 10:43:41 Vault kernel: BTRFS error (device sdh1): bdev /dev/sdg1 errs: wr 14878386, rd 13226455, flush 62535, corrupt 2409818, gen 6908 Nov 21 10:43:41 Vault kernel: BTRFS error (device sdh1): bdev /dev/sdg1 errs: wr 14878386, rd 13226456, flush 62535, corrupt 2409818, gen 6908 Nov 21 10:43:41 Vault kernel: BTRFS error (device sdh1): bdev /dev/sdg1 errs: wr 14878386, rd 13226457, flush 62535, corrupt 2409818, gen 6908 Nov 21 10:43:41 Vault kernel: BTRFS error (device sdh1): bdev /dev/sdg1 errs: wr 14878386, rd 13226458, flush 62535, corrupt 2409818, gen 6908 Nov 21 10:43:41 Vault kernel: BTRFS error (device sdh1): bdev /dev/sdg1 errs: wr 14878386, rd 13226459, flush 62535, corrupt 2409818, gen 6908 Nov 21 10:43:41 Vault kernel: sd 4:0:0:0: [sdg] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Nov 21 10:43:41 Vault kernel: sd 4:0:0:0: [sdg] tag#1 CDB: opcode=0x28 28 00 03 34 a3 c8 00 00 68 00 Nov 21 10:43:41 Vault kernel: blk_update_request: I/O error, dev sdg, sector 53781448 Nov 21 10:43:41 Vault kernel: BTRFS error (device sdh1): bdev /dev/sdg1 errs: wr 14878386, rd 13226460, flush 62535, corrupt 2409818, gen 6908 Nov 21 10:43:41 Vault kernel: sd 4:0:0:0: [sdg] tag#2 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Nov 21 10:43:41 Vault kernel: sd 4:0:0:0: [sdg] tag#2 CDB: opcode=0x28 28 00 03 34 a1 b0 00 00 08 00 Nov 21 10:43:41 Vault kernel: blk_update_request: I/O error, dev sdg, sector 53780912 Nov 21 10:43:41 Vault kernel: BTRFS error (device sdh1): bdev /dev/sdg1 errs: wr 14878386, rd 13226461, flush 62535, corrupt 2409818, gen 6908 Nov 21 10:43:41 Vault kernel: BTRFS error (device sdh1): bdev /dev/sdg1 errs: wr 14878386, rd 13226463, flush 62535, corrupt 2409818, gen 6908 Nov 21 10:43:41 Vault kernel: sd 4:0:0:0: [sdg] tag#5 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Nov 21 10:43:41 Vault kernel: sd 4:0:0:0: [sdg] tag#5 CDB: opcode=0x28 28 00 03 34 a1 c8 00 00 08 00 Nov 21 10:43:41 Vault kernel: blk_update_request: I/O error, dev sdg, sector 53780936 Nov 21 10:43:41 Vault kernel: BTRFS error (device sdh1): bdev /dev/sdg1 errs: wr 14878386, rd 13226464, flush 62535, corrupt 2409818, gen 6908 Nov 21 10:43:41 Vault kernel: sd 4:0:0:0: [sdg] tag#6 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Nov 21 10:43:41 Vault kernel: sd 4:0:0:0: [sdg] tag#6 CDB: opcode=0x28 28 00 03 34 a1 d0 00 00 08 00 Nov 21 10:43:41 Vault kernel: blk_update_request: I/O error, dev sdg, sector 53780944 Nov 21 10:43:41 Vault kernel: sd 4:0:0:0: [sdg] tag#7 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Nov 21 10:43:41 Vault kernel: sd 4:0:0:0: [sdg] tag#7 CDB: opcode=0x28 28 00 03 34 a1 d8 00 00 08 00 Nov 21 10:43:41 Vault kernel: blk_update_request: I/O error, dev sdg, sector 53780952 Nov 21 10:43:41 Vault kernel: sd 4:0:0:0: [sdg] tag#8 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Nov 21 10:43:41 Vault kernel: sd 4:0:0:0: [sdg] tag#8 CDB: opcode=0x28 28 00 03 34 a1 e0 00 00 08 00 Nov 21 10:43:41 Vault kernel: blk_update_request: I/O error, dev sdg, sector 53780960 Nov 21 10:43:41 Vault kernel: sd 4:0:0:0: [sdg] tag#9 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Nov 21 10:43:41 Vault kernel: sd 4:0:0:0: [sdg] tag#9 CDB: opcode=0x28 28 00 03 34 a1 e8 00 00 08 00 Nov 21 10:43:41 Vault kernel: blk_update_request: I/O error, dev sdg, sector 53780968 Nov 21 10:43:42 Vault kernel: btrfs_end_buffer_write_sync: 1 callbacks suppressed Nov 21 10:43:42 Vault kernel: BTRFS warning (device sdh1): lost page write due to IO error on /dev/sdg1 Nov 21 10:43:42 Vault kernel: BTRFS warning (device sdh1): lost page write due to IO error on /dev/sdg1 Nov 21 10:43:43 Vault kernel: BTRFS warning (device sdh1): lost page write due to IO error on /dev/sdg1 Nov 21 10:43:46 Vault kernel: scsi_io_completion: 42067 callbacks suppressed Nov 21 10:43:46 Vault kernel: sd 4:0:0:0: [sdg] tag#3 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Nov 21 10:43:46 Vault kernel: sd 4:0:0:0: [sdg] tag#3 CDB: opcode=0x28 28 00 04 32 cd f8 00 03 f8 00 Nov 21 10:43:46 Vault kernel: blk_update_request: 42086 callbacks suppressed Nov 21 10:43:46 Vault kernel: blk_update_request: I/O error, dev sdg, sector 70438392 Nov 21 10:43:46 Vault kernel: btrfs_dev_stat_print_on_error: 79975 callbacks suppressed Nov 21 10:43:46 Vault kernel: BTRFS error (device sdh1): bdev /dev/sdg1 errs: wr 14927015, rd 13257903, flush 62538, corrupt 2409818, gen 6908 Nov 21 10:43:46 Vault kernel: BTRFS error (device sdh1): bdev /dev/sdg1 errs: wr 14927015, rd 13257904, flush 62538, corrupt 2409818, gen 6908 Nov 21 10:43:46 Vault kernel: BTRFS error (device sdh1): bdev /dev/sdg1 errs: wr 14927015, rd 13257905, flush 62538, corrupt 2409818, gen 6908 Nov 21 10:43:46 Vault kernel: BTRFS error (device sdh1): bdev /dev/sdg1 errs: wr 14927015, rd 13257906, flush 62538, corrupt 2409818, gen 6908 Nov 21 10:43:46 Vault kernel: BTRFS error (device sdh1): bdev /dev/sdg1 errs: wr 14927015, rd 13257907, flush 62538, corrupt 2409818, gen 6908 Nov 21 10:43:46 Vault kernel: BTRFS error (device sdh1): bdev /dev/sdg1 errs: wr 14927015, rd 13257908, flush 62538, corrupt 2409818, gen 6908 Nov 21 10:43:46 Vault kernel: BTRFS error (device sdh1): bdev /dev/sdg1 errs: wr 14927015, rd 13257909, flush 62538, corrupt 2409818, gen 6908 Nov 21 10:43:46 Vault kernel: BTRFS error (device sdh1): bdev /dev/sdg1 errs: wr 14927015, rd 13257910, flush 62538, corrupt 2409818, gen 6908 Nov 21 10:43:46 Vault kernel: BTRFS error (device sdh1): bdev /dev/sdg1 errs: wr 14927015, rd 13257911, flush 62538, corrupt 2409818, gen 6908 Nov 21 10:43:46 Vault kernel: sd 4:0:0:0: [sdg] tag#4 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Smart says everything is ok...
  18. Could it be the OCZ Firmware on the drive that is causing this? usually with SATA cables a stress test shows the problem, 11 hours of heavy data read and writes and its still fine..
  19. I have them both plugged into my onboard Sata controller on my Z87 motherboard. I do have an LSI 9210-8i is that going to be better to run them off of? the first cache drive seems to be fine though and its running off the same Sata controller as the second one.
  20. Something weird is happening to my cache system. I have ran one drive for a long time just added in my second SSD about 2 weeks ago. I am getting these errors. ov 19 20:35:21 Vault kernel: sd 4:0:0:0: [sdk] tag#17 CDB: opcode=0x28 28 00 1d 54 f4 28 00 00 08 00 Nov 19 20:35:21 Vault kernel: blk_update_request: I/O error, dev sdk, sector 492106792 Nov 19 20:35:21 Vault kernel: sd 4:0:0:0: [sdk] tag#18 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Nov 19 20:35:21 Vault kernel: sd 4:0:0:0: [sdk] tag#18 CDB: opcode=0x28 28 00 1d 54 f4 30 00 00 08 00 Nov 19 20:35:21 Vault kernel: blk_update_request: I/O error, dev sdk, sector 492106800 Nov 19 20:35:22 Vault kernel: BTRFS warning (device sdl1): lost page write due to IO error on /dev/sdk1 Nov 19 20:35:22 Vault kernel: BTRFS warning (device sdl1): lost page write due to IO error on /dev/sdk1 Nov 19 20:35:22 Vault kernel: BTRFS warning (device sdl1): lost page write due to IO error on /dev/sdk1 Nov 19 20:35:22 Vault kernel: BTRFS warning (device sdl1): lost page write due to IO error on /dev/sdk1 Nov 19 20:35:22 Vault kernel: BTRFS warning (device sdl1): lost page write due to IO error on /dev/sdk1 Nov 19 20:35:22 Vault kernel: BTRFS warning (device sdl1): lost page write due to IO error on /dev/sdk1 When i Smart the drive its all fine and when i do preclears it is error free. Can anyone help with this, when i reboot it seems to be repairing it. Model family: Indilinx Barefoot_2/Everest/Martini based SSDs Device model: OCZ-VERTEX4 Serial number: OCZ-O71N80GX4YB2BAX3 LU WWN device id: 5 e83a97 79a2515c2 Firmware version: 1.5.1 User capacity: 256,060,514,304 bytes [256 GB] Sector size: 512 bytes logical/physical Rotation rate: Solid State Device Device: In smartctl database [for details use: -P show] ATA version: ACS-2 (minor revision not indicated) SATA version: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Local time: Sun Nov 19 20:55:43 2017 AEDT SMART support: Available - device has SMART capability. SMART support: Enabled SMART overall-health: Passed scrub status for 8e82d82d-f6f6-45d7-9e5a-d389fb0e0bb3 scrub started at Sun Nov 19 21:16:33 2017 and finished after 00:02:37 total bytes scrubbed: 27.56GiB with 1208172 errors error details: verify=3447 csum=1204725 corrected errors: 1208172, uncorrectable errors: 0, unverified errors: 0
  21. I love Unraid, but... after installing 6.3.2 i was seeing updates frequently with fixes and security patches. 26th of May was the last update with 6.3.5 it's been quite some time since we have had any security patches is one coming soon?
  22. Mine usually lasts about 65 mins. I have other machines on that shutdown when power is lost.
  23. I have a few pieces missing in the UPS Plug the data is in the key below though. How do i edit the fields for Norminal Power to show OUTPUTV and UPS Load to not showing load current. Is there a better UPS plugin ?
  24. I might do this once a month i have had those disk full messages before when i had 80G free before on the cache.