March 29, 201610 yr Hi everyone, built a tower, i7-4930k (2011 socket) Gigabyte GA-X79-UD3 Corsair 16Gb DDR3 Nvidia GTX745 (UNRAID display) HD 5830 (WIN10 VM Display) Corsair RMi Series 750W Fully Modular Power Supply UNRAID (plus) 6.1.9 3 SSD drive as Cache 4x 4TB drives as storage setup UNRAID6 plus, all went well. The server started the parity sync. this is where things got odd. around 10 to 20% the system would hang, for 2 mintues. then just shut down. so i read the Marvell Sata chipset was a bad idea. so i disabled these. got the sync to do its thing. woke up this morning and the unit was off again? :'( the CPU/GPU is not overclocked and is currently cooled by a Corsair H100i V2 AIO Hydro/Water cooler and 2 front intake fans and a rear exhaust fan. So i dont think it is a cooling issue. What i would love, is for some help to point me to a way to try and find out what is causing UNRAID to be unhappy. But i am very impressed with UNRAID thus far, coming from a background in VMware and Citrix servers. just really need to get this unit stable. Thx guys tower-diagnostics-20160329-2058.zip
March 29, 201610 yr Author So got home, updated the ticket as per the guide lines, booted up the unit and started the array. ERROR: error removing the device @missing@ - unable to go below two devices on raid1 however all drives were showing in dashboard and the parity scan started to run again. But then again, lost all connections both my SSH and telnet connections dropped. GUI hung and webpage not available. Then again, the system just shuts down. No VMs started nor any dockers The VM I currently have setup is a WIN10 Vm with GPU pass through. (sea bios) The only diff i can think of since my testing phase on the UNRAID trial, is there are more disks now with the licensed UNRAID 6 plus, and instead of a WIN7 VM i have a win10 VM.
March 29, 201610 yr Community Expert Never heard of a system just shutting down unless there is a hardware issue. It is typically due to the CPU overheating and the system auto-shutting down to protect it. However you seemed to be reasonably certain that was not it. Is there any other critical fan that might have stopped working?
March 29, 201610 yr Author Currently running a tail -f on the GUI and in telnet and SSH putty sessions. Lets see if i can grab anything useful. As for the cooling, The only fan i have not checked would be the GTX745 GPU. If the server hangs up again, i will pull that card and boot and server with only the HD5830 GPU and re-test.
March 30, 201610 yr Author So here is the tail log, the server ran all night without problems. got home today... server off! Mar 29 21:24:12 Tower kernel: ip_tables: (C) 2000-2006 Netfilter Core Team Mar 29 21:24:12 Tower avahi-daemon[3900]: Joining mDNS multicast group on interface docker0.IPv4 with addre ss 172.17.42.1. Mar 29 21:24:12 Tower avahi-daemon[3900]: New relevant interface docker0.IPv4 for mDNS. Mar 29 21:24:12 Tower avahi-daemon[3900]: Registering new address record for 172.17.42.1 on docker0.IPv4. Mar 29 21:24:13 Tower avahi-daemon[3900]: Service "Tower" (/services/smb.service) successfully established. Mar 29 21:24:13 Tower ntpd[1909]: Listen normally on 3 docker0 172.17.42.1:123 Mar 29 21:24:13 Tower ntpd[1909]: new interface(s) found: waking up resolver Mar 29 21:24:19 Tower logger: Updating templates... Updating info... Done. Mar 29 21:24:19 Tower kernel: EXT4-fs (loop1): recovery complete Mar 29 21:24:19 Tower kernel: EXT4-fs (loop1): mounted filesystem with ordered data mode. Opts: (null) Mar 29 21:24:19 Tower emhttp: Starting libvirt... Mar 29 21:24:19 Tower logger: Starting libvirtd... Mar 29 21:24:19 Tower kernel: tun: Universal TUN/TAP device driver, 1.6 Mar 29 21:24:19 Tower kernel: tun: (C) 1999-2004 Max Krasnyansky <[email protected]> Mar 29 21:24:19 Tower kernel: Ebtables v2.0 registered Mar 29 21:24:19 Tower kernel: device virbr0-nic entered promiscuous mode Mar 29 21:24:19 Tower avahi-daemon[3900]: Joining mDNS multicast group on interface virbr0.IPv4 with addres s 192.168.122.1. Mar 29 21:24:19 Tower avahi-daemon[3900]: New relevant interface virbr0.IPv4 for mDNS. Mar 29 21:24:19 Tower avahi-daemon[3900]: Registering new address record for 192.168.122.1 on virbr0.IPv4. Mar 29 21:24:19 Tower kernel: virbr0: port 1(virbr0-nic) entered listening state Mar 29 21:24:19 Tower kernel: virbr0: port 1(virbr0-nic) entered listening state Mar 29 21:24:19 Tower dnsmasq[4840]: started, version 2.72 cachesize 150 Mar 29 21:24:19 Tower dnsmasq[4840]: compile time options: IPv6 GNU-getopt no-DBus i18n IDN DHCP DHCPv6 no- Lua TFTP no-conntrack ipset auth no-DNSSEC loop-detect Mar 29 21:24:19 Tower dnsmasq-dhcp[4840]: DHCP, IP range 192.168.122.2 -- 192.168.122.254, lease time 1h Mar 29 21:24:19 Tower dnsmasq-dhcp[4840]: DHCP, sockets bound exclusively to interface virbr0 Mar 29 21:24:19 Tower dnsmasq[4840]: reading /etc/resolv.conf Mar 29 21:24:19 Tower dnsmasq[4840]: using nameserver 192.168.0.1#53 Mar 29 21:24:19 Tower dnsmasq[4840]: read /etc/hosts - 1 addresses Mar 29 21:24:19 Tower dnsmasq[4840]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses Mar 29 21:24:19 Tower dnsmasq-dhcp[4840]: read /var/lib/libvirt/dnsmasq/default.hostsfile Mar 29 21:24:19 Tower kernel: virbr0: port 1(virbr0-nic) entered disabled state Mar 29 21:25:34 Tower login[3808]: ROOT LOGIN on '/dev/tty1' Mar 29 21:28:52 Tower kernel: kvm: already loaded the other module Mar 29 21:31:37 Tower kernel: kvm: already loaded the other module Mar 29 21:42:43 Tower kernel: kvm: already loaded the other module Mar 29 22:01:32 Tower kernel: kvm: already loaded the other module Mar 29 22:09:42 Tower kernel: usb 2-1.6: reset high-speed USB device number 3 using ehci-pci Mar 29 22:27:13 Tower php: /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker 'start' 'PlexMed iaServer' Mar 29 22:27:18 Tower kernel: device vnet0 entered promiscuous mode Mar 29 22:27:18 Tower kernel: br0: port 2(vnet0) entered listening state Mar 29 22:27:18 Tower kernel: br0: port 2(vnet0) entered listening state Mar 29 22:27:18 Tower kernel: vgaarb: device changed decodes: PCI:0000:02:00.0,olddecodes=io+mem,decodes=io +mem:owns=none Mar 29 22:27:18 Tower kernel: kvm: SMP vm created on host with unstable TSC; guest TSC will not be reliable Mar 29 22:27:19 Tower kernel: vfio-pci 0000:02:00.0: enabling device (0000 -> 0003) Mar 29 22:27:19 Tower kernel: vfio-pci 0000:00:1b.0: enabling device (0000 -> 0002) Mar 29 22:27:19 Tower kernel: vfio_ecap_init: 0000:00:1b.0 hiding ecap 0x5@0x130 Mar 29 22:27:21 Tower kernel: vgaarb: device changed decodes: PCI:0000:02:00.0,olddecodes=io+mem,decodes=io +mem:owns=none Mar 29 22:27:22 Tower kernel: usb 1-1.6: reset low-speed USB device number 5 using ehci-pci Mar 29 22:27:22 Tower kernel: usb 1-1.6: reset low-speed USB device number 5 using ehci-pci Mar 29 22:27:23 Tower kernel: usb 1-1.5: reset full-speed USB device number 4 using ehci-pci Mar 29 22:27:23 Tower kernel: kvm: zapping shadow pages for mmio generation wraparound Mar 29 22:27:25 Tower kernel: usb 1-1.6: reset low-speed USB device number 5 using ehci-pci Mar 29 22:27:25 Tower kernel: usb 1-1.6: reset low-speed USB device number 5 using ehci-pci Mar 29 22:27:29 Tower kernel: usb 1-1.6: reset low-speed USB device number 5 using ehci-pci Mar 29 22:27:30 Tower kernel: usb 1-1.6: reset low-speed USB device number 5 using ehci-pci Mar 29 22:27:31 Tower kernel: usb 1-1.6: reset low-speed USB device number 5 using ehci-pci Mar 29 22:27:31 Tower kernel: usb 1-1.6: reset low-speed USB device number 5 using ehci-pci Mar 29 22:27:32 Tower kernel: usb 1-1.5: reset full-speed USB device number 4 using ehci-pci Mar 29 22:27:32 Tower kernel: usb 1-1.5: reset full-speed USB device number 4 using ehci-pci Mar 29 22:27:33 Tower kernel: br0: port 2(vnet0) entered learning state Mar 29 22:27:48 Tower kernel: br0: topology change detected, propagating Mar 29 22:27:48 Tower kernel: br0: port 2(vnet0) entered forwarding state Mar 29 22:32:49 Tower kernel: kvm: already loaded the other module Mar 29 22:35:08 Tower kernel: usb 1-1.6: reset low-speed USB device number 5 using ehci-pci Mar 29 22:35:09 Tower kernel: usb 1-1.6: reset low-speed USB device number 5 using ehci-pci Mar 29 22:35:11 Tower kernel: usb 1-1.6: reset low-speed USB device number 5 using ehci-pci Mar 29 22:35:12 Tower kernel: usb 1-1.6: reset low-speed USB device number 5 using ehci-pci Mar 29 22:35:13 Tower kernel: usb 1-1.6: reset low-speed USB device number 5 using ehci-pci Mar 29 22:35:13 Tower kernel: usb 1-1.5: reset full-speed USB device number 4 using ehci-pci Mar 29 22:35:15 Tower kernel: usb 1-1.6: reset low-speed USB device number 5 using ehci-pci Mar 29 22:35:16 Tower kernel: usb 1-1.6: reset low-speed USB device number 5 using ehci-pci Mar 29 22:35:19 Tower kernel: usb 1-1.6: reset low-speed USB device number 5 using ehci-pci Mar 29 22:35:19 Tower kernel: usb 1-1.6: reset low-speed USB device number 5 using ehci-pci Mar 29 22:35:21 Tower kernel: usb 1-1.6: reset low-speed USB device number 5 using ehci-pci Mar 29 22:35:21 Tower kernel: usb 1-1.6: reset low-speed USB device number 5 using ehci-pci Mar 29 22:35:22 Tower kernel: usb 1-1.5: reset full-speed USB device number 4 using ehci-pci Mar 29 22:35:22 Tower kernel: usb 1-1.5: reset full-speed USB device number 4 using ehci-pci Mar 29 22:38:01 Tower emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log libvirt/qemu/Windows 10.log Mar 29 22:39:33 Tower kernel: kvm: already loaded the other module Mar 29 23:13:41 Tower php: /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerupdate.php Mar 29 23:39:39 Tower emhttp: shcmd (57): /usr/local/sbin/mover |& logger & Mar 29 23:39:39 Tower logger: mover started Mar 29 23:39:39 Tower logger: skipping "VM Disks" Mar 29 23:39:39 Tower logger: mover finished Mar 30 01:12:23 Tower kernel: usb 2-1.6: reset high-speed USB device number 3 using ehci-pci Mar 30 02:55:04 Tower kernel: usb 2-1.6: reset high-speed USB device number 3 using ehci-pci Mar 30 03:40:01 Tower logger: mover started Mar 30 03:40:01 Tower logger: skipping "VM Disks" Mar 30 03:40:01 Tower logger: mover finished Mar 30 06:46:25 Tower kernel: md: sync done. time=33735sec Mar 30 06:46:25 Tower kernel: md: recovery thread sync completion status: 0 Mar 30 09:22:31 Tower dhcpcd[1862]: br0: renewing lease of 192.168.0.24 Mar 30 09:22:31 Tower dhcpcd[1862]: br0: rebind in 32400 seconds, expire in 43200 seconds Mar 30 09:22:31 Tower dhcpcd[1862]: br0: sending REQUEST (xid 0xa973b240), next in 4.4 seconds Mar 30 09:22:31 Tower dhcpcd[1862]: br0: acknowledged 192.168.0.24 from 192.168.0.1 Mar 30 09:22:31 Tower dhcpcd[1862]: br0: leased 192.168.0.24 for 86400 seconds Mar 30 09:22:31 Tower dhcpcd[1862]: br0: renew in 43200 seconds, rebind in 75600 seconds Mar 30 09:22:31 Tower dhcpcd[1862]: br0: writing lease `/var/lib/dhcpcd/dhcpcd-br0.lease' Mar 30 09:22:31 Tower dhcpcd[1862]: br0: IP address 192.168.0.24/24 already exists Mar 30 09:22:31 Tower dhcpcd[1862]: br0: executing `/lib/dhcpcd/dhcpcd-run-hooks' RENEW Mar 30 09:22:31 Tower dhcpcd[1862]: br0: ARP announcing 192.168.0.24 (1 of 2), next in 2.0 seconds Mar 30 09:22:33 Tower dhcpcd[1862]: br0: ARP announcing 192.168.0.24 (2 of 2) Mar 30 12:17:32 Tower dhcpcd[1862]: br0: xid 0x16fe1718 is for hwaddr 70:ec:e4:a1:cc:50:00:00:00:00:00:00:00:00:00:00 Mar 30 12:17:34 Tower dhcpcd[1862]: br0: xid 0x16fe1718 is for hwaddr 70:ec:e4:a1:cc:50:00:00:00:00:00:00:00:00:00:00 Mar 30 14:04:00 Tower dhcpcd[1862]: br0: xid 0x1f9d96d8 is for hwaddr 70:ec:e4:a1:cc:50:00:00:00:00:00:00:00:00:00:00 Mar 30 14:04:16 Tower dhcpcd[1862]: br0: xid 0x1f9d96d9 is for hwaddr 70:ec:e4:a1:cc:50:00:00:00:00:00:00:00:00:00:00 Mar 30 14:04:18 Tower dhcpcd[1862]: br0: xid 0x1f9d96d9 is for hwaddr 70:ec:e4:a1:cc:50:00:00:00:00:00:00:00:00:00:00 Mar 30 14:04:20 Tower dhcpcd[1862]: br0: xid 0x1f9d96d9 is for hwaddr 70:ec:e4:a1:cc:50:00:00:00:00:00:00:00:00:00:00 Mar 30 14:04:24 Tower dhcpcd[1862]: br0: xid 0x1f9d96d9 is for hwaddr 70:ec:e4:a1:cc:50:00:00:00:00:00:00:00:00:00:00 Mar 30 14:04:28 Tower dhcpcd[1862]: br0: xid 0x1f9d96d9 is for hwaddr 70:ec:e4:a1:cc:50:00:00:00:00:00:00:00:00:00:00 Mar 30 14:04:38 Tower dhcpcd[1862]: br0: xid 0x1f9d96da is for hwaddr 70:ec:e4:a1:cc:50:00:00:00:00:00:00:00:00:00:00 Mar 30 14:04:40 Tower dhcpcd[1862]: br0: xid 0x1f9d96da is for hwaddr 70:ec:e4:a1:cc:50:00:00:00:00:00:00:00:00:00:00 Mar 30 14:04:41 Tower dhcpcd[1862]: br0: xid 0x1f9d96da is for hwaddr 70:ec:e4:a1:cc:50:00:00:00:00:00:00:00:00:00:00 Mar 30 14:04:42 Tower dhcpcd[1862]: br0: xid 0x1f9d96da is for hwaddr 70:ec:e4:a1:cc:50:00:00:00:00:00:00:00:00:00:00 Mar 30 14:04:44 Tower dhcpcd[1862]: br0: xid 0x1f9d96da is for hwaddr 70:ec:e4:a1:cc:50:00:00:00:00:00:00:00:00:00:00 Mar 30 14:04:48 Tower dhcpcd[1862]: br0: xid 0x1f9d96da is for hwaddr 70:ec:e4:a1:cc:50:00:00:00:00:00:00:00:00:00:00 I cant see any errors, but this one stands out br0: xid 0x1f9d96da is for hwaddr 70:ec:e4:a1:cc:50:00:00:00:00:00:00:00:00:00:00 Any ideas? full log attached as a txt file. Full_tail_log.txt
March 31, 201610 yr Author Removed the GTX745 GPU, turned off the XMP profile within the bios. started the server and worked on it all night. WIN10 vm running(6 cores and 10Gb of ram running on VNC currently) and copying data from a USB3 drive with the plugin unregistered or unassigned ( i forget the name) Testing sickbread and couchpotatoe. and later in the evening streamed some content from Plex to the smart TV in the bedroom. wake up in the morning. server off! Mar 30 21:39:46 Tower avahi-daemon[3827]: Withdrawing workstation service for as0t2. Mar 30 21:39:46 Tower avahi-daemon[3827]: Withdrawing workstation service for as0t22. Mar 30 21:39:46 Tower avahi-daemon[3827]: Withdrawing workstation service for as0t13. Mar 30 21:39:46 Tower avahi-daemon[3827]: Withdrawing workstation service for as0t21. Mar 30 21:39:46 Tower avahi-daemon[3827]: Withdrawing workstation service for as0t14. Mar 30 21:39:48 Tower ntpd[1841]: Deleting interface #28 as0t0, 172.27.224.1#123, interface stats: received=0, sent=0, dropped=0, active_time=94 secs Mar 30 21:39:48 Tower ntpd[1841]: Deleting interface #29 as0t1, 172.27.224.129#123, interface stats: received=0, sent=0, dropped=0, active_time=94 secs Mar 30 21:39:48 Tower ntpd[1841]: Deleting interface #30 as0t2, 172.27.225.1#123, interface stats: received=0, sent=0, dropped=0, active_time=94 secs Mar 30 21:39:48 Tower ntpd[1841]: Deleting interface #31 as0t3, 172.27.225.129#123, interface stats: received=0, sent=0, dropped=0, active_time=94 secs Mar 30 21:39:48 Tower ntpd[1841]: Deleting interface #32 as0t4, 172.27.226.1#123, interface stats: received=0, sent=0, dropped=0, active_time=94 secs Mar 30 21:39:48 Tower ntpd[1841]: Deleting interface #33 as0t5, 172.27.226.129#123, interface stats: received=0, sent=0, dropped=0, active_time=94 secs Mar 30 21:39:48 Tower ntpd[1841]: Deleting interface #34 as0t6, 172.27.227.1#123, interface stats: received=0, sent=0, dropped=0, active_time=94 secs Mar 30 21:39:48 Tower ntpd[1841]: Deleting interface #35 as0t7, 172.27.227.129#123, interface stats: received=0, sent=0, dropped=0, active_time=94 secs Mar 30 21:39:48 Tower ntpd[1841]: Deleting interface #36 as0t8, 172.27.228.1#123, interface stats: received=0, sent=0, dropped=0, active_time=94 secs Mar 30 21:39:48 Tower ntpd[1841]: Deleting interface #37 as0t9, 172.27.228.129#123, interface stats: received=0, sent=0, dropped=0, active_time=94 secs Mar 30 21:39:48 Tower ntpd[1841]: Deleting interface #38 as0t10, 172.27.229.1#123, interface stats: received=0, sent=0, dropped=0, active_time=94 secs Mar 30 21:39:48 Tower ntpd[1841]: Deleting interface #39 as0t11, 172.27.229.129#123, interface stats: received=0, sent=0, dropped=0, active_time=94 secs Mar 30 21:39:48 Tower ntpd[1841]: Deleting interface #40 as0t12, 172.27.230.1#123, interface stats: received=0, sent=0, dropped=0, active_time=94 secs Mar 30 21:39:48 Tower ntpd[1841]: Deleting interface #41 as0t13, 172.27.230.129#123, interface stats: received=0, sent=0, dropped=0, active_time=94 secs Mar 30 21:39:48 Tower ntpd[1841]: Deleting interface #42 as0t14, 172.27.231.1#123, interface stats: received=0, sent=0, dropped=0, active_time=94 secs Mar 30 21:39:48 Tower ntpd[1841]: Deleting interface #43 as0t15, 172.27.231.129#123, interface stats: received=0, sent=0, dropped=0, active_time=94 secs Mar 30 21:39:48 Tower ntpd[1841]: Deleting interface #44 as0t16, 172.27.232.1#123, interface stats: received=0, sent=0, dropped=0, active_time=94 secs Mar 30 21:39:48 Tower ntpd[1841]: Deleting interface #45 as0t17, 172.27.232.129#123, interface stats: received=0, sent=0, dropped=0, active_time=94 secs Mar 30 21:39:48 Tower ntpd[1841]: Deleting interface #46 as0t18, 172.27.233.1#123, interface stats: received=0, sent=0, dropped=0, active_time=94 secs Mar 30 21:39:48 Tower ntpd[1841]: Deleting interface #47 as0t19, 172.27.233.129#123, interface stats: received=0, sent=0, dropped=0, active_time=94 secs Mar 30 21:39:48 Tower ntpd[1841]: Deleting interface #48 as0t20, 172.27.234.1#123, interface stats: received=0, sent=0, dropped=0, active_time=94 secs Mar 30 21:39:48 Tower ntpd[1841]: Deleting interface #49 as0t21, 172.27.234.129#123, interface stats: received=0, sent=0, dropped=0, active_time=94 secs Mar 30 21:39:48 Tower ntpd[1841]: Deleting interface #50 as0t22, 172.27.235.1#123, interface stats: received=0, sent=0, dropped=0, active_time=94 secs Mar 30 21:39:48 Tower ntpd[1841]: Deleting interface #51 as0t23, 172.27.235.129#123, interface stats: received=0, sent=0, dropped=0, active_time=94 secs Mar 30 21:42:05 Tower sshd[16200]: Accepted password for root from 192.168.0.2 port 53630 ssh2 Mar 30 21:42:50 Tower shfs/user: shfs_rmdir: rmdir: /mnt/disk1/appdata/couchpotato (39) Directory not empty Mar 30 21:44:06 Tower shfs/user: shfs_rmdir: rmdir: /mnt/disk1/appdata/couchpotato (39) Directory not empty Mar 30 21:47:08 Tower shfs/user: shfs_rmdir: rmdir: /mnt/disk1/appdata/openVPN (39) Directory not empty Mar 30 22:27:45 Tower ntpd[1841]: Listen normally on 52 as0t0 172.27.224.1:123 Mar 30 22:27:45 Tower ntpd[1841]: Listen normally on 53 as0t1 172.27.232.1:123 Mar 30 22:27:45 Tower ntpd[1841]: new interface(s) found: waking up resolver Mar 30 22:55:54 Tower kernel: xhci_hcd 0000:09:00.0: Command completion event does not match command Mar 30 22:55:54 Tower kernel: xhci_hcd 0000:09:00.0: Timeout while waiting for setup device command Mar 30 22:55:59 Tower kernel: xhci_hcd 0000:09:00.0: Error while assigning device slot ID Mar 30 22:55:59 Tower kernel: xhci_hcd 0000:09:00.0: Max number of devices this xHCI host supports is 31. Mar 30 22:55:59 Tower kernel: usb usb5-port2: couldn't allocate usb_device Mar 30 22:56:04 Tower kernel: xhci_hcd 0000:09:00.0: Command completion event does not match command Mar 30 22:56:04 Tower kernel: xhci_hcd 0000:09:00.0: Timeout while waiting for setup device command Mar 30 22:56:04 Tower kernel: usb 6-2: device not accepting address 2, error -62 Mar 30 22:56:07 Tower kernel: usb 8-1: new SuperSpeed USB device number 2 using xhci_hcd Mar 30 22:56:07 Tower kernel: usb-storage 8-1:1.0: USB Mass Storage device detected Mar 30 22:56:07 Tower kernel: scsi host8: usb-storage 8-1:1.0 Mar 30 22:56:08 Tower kernel: scsi 8:0:0:0: Direct-Access Seagate Expansion 0636 PQ: 0 ANSI: 6 Mar 30 22:56:08 Tower kernel: sd 8:0:0:0: Attached scsi generic sg11 type 0 Mar 30 22:56:08 Tower kernel: sd 8:0:0:0: [sdl] Spinning up disk... Mar 30 22:56:11 Tower kernel: .ready Mar 30 22:56:11 Tower kernel: sd 8:0:0:0: [sdl] 1953525167 512-byte logical blocks: (1.00 TB/932 GiB) Mar 30 22:56:11 Tower kernel: sd 8:0:0:0: [sdl] Write Protect is off Mar 30 22:56:11 Tower kernel: sd 8:0:0:0: [sdl] Mode Sense: 2b 00 10 08 Mar 30 22:56:11 Tower kernel: sd 8:0:0:0: [sdl] Write cache: enabled, read cache: enabled, supports DPO and FUA Mar 30 22:56:11 Tower kernel: sdl: sdl1 Mar 30 22:56:11 Tower kernel: sd 8:0:0:0: [sdl] Attached SCSI disk Mar 30 22:56:13 Tower kernel: usb usb6-port2: Cannot enable. Maybe the USB cable is bad? Mar 30 22:56:17 Tower kernel: usb usb6-port2: Cannot enable. Maybe the USB cable is bad? Mar 30 22:56:21 Tower kernel: usb usb6-port2: Cannot enable. Maybe the USB cable is bad? Mar 30 22:56:21 Tower kernel: usb usb6-port2: unable to enumerate USB device Mar 30 22:57:19 Tower ntfs-3g[11771]: Version 2016.2.22 integrated FUSE 27 Mar 30 22:57:19 Tower ntfs-3g[11771]: Mounted /dev/sdl1 (Read-Write, label "Seagate Expansion Drive", NTFS 3.1) Mar 30 22:57:19 Tower ntfs-3g[11771]: Cmdline options: rw,nosuid,nodev,umask=000 Mar 30 22:57:19 Tower ntfs-3g[11771]: Mount options: rw,nosuid,nodev,allow_other,nonempty,relatime,default_permissions,fsname=/dev/sdl1,blkdev,blksize=4096 Mar 30 22:57:19 Tower ntfs-3g[11771]: Global ownership and permissions enforced, configuration type 1 Mar 30 23:35:51 Tower emhttp: shcmd (95): mkdir '/mnt/user/Music' |& logger Mar 30 23:35:51 Tower emhttp: shcmd (96): chmod 0777 '/mnt/user/Music' Mar 30 23:35:51 Tower emhttp: shcmd (97): chown 'nobody':'users' '/mnt/user/Music' Mar 30 23:35:51 Tower emhttp: shcmd (98): :>/etc/samba/smb-shares.conf Mar 30 23:35:51 Tower avahi-daemon[3827]: Files changed, reloading. Mar 30 23:35:51 Tower emhttp: Restart SMB... Mar 30 23:35:51 Tower emhttp: shcmd (99): killall -HUP smbd Mar 30 23:35:51 Tower emhttp: shcmd (100): cp /etc/avahi/services/smb.service- /etc/avahi/services/smb.service Mar 30 23:35:51 Tower avahi-daemon[3827]: Files changed, reloading. Mar 30 23:35:51 Tower avahi-daemon[3827]: Service group file /services/smb.service changed, reloading. Mar 30 23:35:51 Tower emhttp: shcmd (101): pidof rpc.mountd &> /dev/null Mar 30 23:35:51 Tower emhttp: shcmd (102): /etc/rc.d/rc.atalk status Mar 30 23:35:52 Tower avahi-daemon[3827]: Service "Tower" (/services/smb.service) successfully established. Mar 30 23:46:20 Tower shfs/user: shfs_rmdir: rmdir: /mnt/disk1/appdata/PlexMediaServer/Library/Application Support/Plex Media Server/Media/localhost/d/1e732d70d5ef49b8296516071cd9513d6d3fc97.bundle/Contents/Indexes/tmp (39) Directory not empty Mar 31 00:12:42 Tower emhttp: shcmd (103): mkdir '/mnt/user/General Drive' |& logger Mar 31 00:12:42 Tower emhttp: shcmd (104): chmod 0777 '/mnt/user/General Drive' Mar 31 00:12:42 Tower emhttp: shcmd (105): chown 'nobody':'users' '/mnt/user/General Drive' Mar 31 00:12:42 Tower emhttp: shcmd (106): :>/etc/samba/smb-shares.conf Mar 31 00:12:42 Tower avahi-daemon[3827]: Files changed, reloading. Mar 31 00:12:42 Tower emhttp: Restart SMB... Mar 31 00:12:42 Tower emhttp: shcmd (107): killall -HUP smbd Mar 31 00:12:42 Tower emhttp: shcmd (108): cp /etc/avahi/services/smb.service- /etc/avahi/services/smb.service Mar 31 00:12:42 Tower avahi-daemon[3827]: Files changed, reloading. Mar 31 00:12:42 Tower avahi-daemon[3827]: Service group file /services/smb.service changed, reloading. Mar 31 00:12:42 Tower emhttp: shcmd (109): pidof rpc.mountd &> /dev/null Mar 31 00:12:42 Tower emhttp: shcmd (110): /etc/rc.d/rc.atalk status Mar 31 00:12:43 Tower avahi-daemon[3827]: Service "Tower" (/services/smb.service) successfully established. Mar 31 00:21:08 Tower shfs/user: shfs_rmdir: rmdir: /mnt/disk1/appdata/PlexMediaServer/Library/Application Support/Plex Media Server/Media/localhost/0/3a691228705b1694a2b50021e3c5d59806a6116.bundle/Contents/Indexes/tmp (39) Directory not empty Mar 31 02:48:42 Tower kernel: usb 2-1.6: reset high-speed USB device number 3 using ehci-pci Mar 31 03:26:38 Tower kernel: usb 2-1.6: reset high-speed USB device number 3 using ehci-pci Mar 31 03:40:01 Tower logger: mover started Mar 31 03:40:01 Tower logger: skipping "VM Disks" Mar 31 03:40:01 Tower logger: mover finished
April 1, 201610 yr Author as Itimpi put the idea in here that this maybe a hardware issue. I have done more testing. Made a window10 usb boot drive. Booted the UNRAID box into win10. 1. Stress tested the computer at full load over the 6 cores (12 threads) for more than an hour and half. max temp seen on any core was 43'c - PASSED 2. loaded MSI afterburner and Unigine Heaven. let Heaven to run on max setting in a windowed 720p res until the temp of the GPU temp settled, then run the benchmark - PASS 3. created a USB boot flash from Memtest86, boot the computer into memtest last night and let it run. This morning it was 75% done with the final memtest pass. (10 and half hours later) showing 1 error in 10h30min - in my books - PASS for non ECC ram so what now?
April 3, 201610 yr Author Ok, so i have finally had some success. Turns out the Corsair PSU RM750i (these full mod and digital PSU) have a safety feature that is meant to safe hardware if it detects any issues. However i think this setting is a little to safe! these unit are also meant to be silent, and the fan only comes on around 40'c. so i have set the fan to 50% all the time and turned off the OCP setting (the odd save the hardware if anything odd is detected setting) So after all this the server run for 3 days and 2 nights, under real load. copying 1.5TB into the array and plex doing its thing. I have re-add the 2nd GPU and the Sata controller card. Now i will check the unit , leaving it on and see if the server stays stable and running.
April 5, 201610 yr Author Corsair PSU was the problem. If you have issues with your UNRAID server and have a digital corsair PSU. Plug the corsair link cable to the PSU and a laptop and install corsair link. If your unit is one of the newer version , if not you might need to do a windows 8/8.1/10 USB drive install [http://www.easyuefi.com/wintousb/index.html] to use the non standard USB cable to the USB header on your motherboard. Turn off the OCP setting and set your fan to run all the time. 50% is almost silent and keeps the PSU under 30'c is my rig.
Archived
This topic is now archived and is closed to further replies.