danthekilla Posted April 15, 2018 Share Posted April 15, 2018 I am using unraid 6.5 and the system becomes unresponsive frequently now after updating from 6.3.5 When I start the device I now just get Array Starting•Starting services...for ever. My parity drive has failed (no idea why) and I cannot access the logs via the log button on the webUI (is there another way?) System Information also takes forever to load if I click on it, after about ten minutes I get this Model: Custom M/B: Gigabyte Technology Co., Ltd. - B85M-HD3-A CPU: Intel® Core™ i5-4670K CPU @ 3.40GHz HVM: Enabled IOMMU: Disabled Cache: 256 kB, 1024 kB, 6144 kB Memory: 12 GB (max. installable capacity 32 GB) Network: eth0: 100 Mb/s, full duplex, mtu 1500 Kernel: Linux 4.14.26-unRAID x86_64 OpenSSL: 1.0.2n Uptime: Unraid 6.5 is a nightmare for me. The last log I managed to get out was this, 3-4 hours ago. It took about 40 minutes before the log loaded after a reboot. Quote Apr 15 01:30:03 Tower kernel: BTRFS: device fsid f443e7d7-fd54-4f30-befa-8b201b565a1e devid 1 transid 146 /dev/loop3Apr 15 01:30:03 Tower kernel: BTRFS info (device loop3): disk space caching is enabledApr 15 01:30:03 Tower kernel: BTRFS info (device loop3): has skinny extentsApr 15 01:30:03 Tower root: Resize '/etc/libvirt' of 'max'Apr 15 01:30:03 Tower kernel: BTRFS info (device loop3): new size for /dev/loop3 is 1073741824Apr 15 01:30:03 Tower emhttpd: shcmd (88): /etc/rc.d/rc.libvirt startApr 15 01:30:03 Tower root: Starting virtlockd...Apr 15 01:30:03 Tower root: Starting virtlogd...Apr 15 01:30:03 Tower root: Starting libvirtd...Apr 15 01:30:03 Tower kernel: tun: Universal TUN/TAP device driver, 1.6Apr 15 01:30:03 Tower kernel: mdcmd (41): check correctApr 15 01:30:03 Tower kernel: md: recovery thread: recon Q ...Apr 15 01:30:03 Tower kernel: md: using 1536k window, over a total of 3907018532 blocks.Apr 15 01:30:03 Tower kernel: ip6_tables: (C) 2000-2006 Netfilter Core TeamApr 15 01:30:03 Tower kernel: Ebtables v2.0 registeredApr 15 01:30:03 Tower kernel: virbr0: port 1(virbr0-nic) entered blocking stateApr 15 01:30:03 Tower kernel: virbr0: port 1(virbr0-nic) entered disabled stateApr 15 01:30:03 Tower kernel: device virbr0-nic entered promiscuous modeApr 15 01:30:03 Tower dhcpcd[1529]: virbr0: new hardware address: 9a:07:a6:cd:f1:c6Apr 15 01:30:03 Tower dhcpcd[1529]: virbr0: new hardware address: 52:54:00:2c:37:deApr 15 01:30:04 Tower avahi-daemon[3743]: Joining mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1.Apr 15 01:30:04 Tower avahi-daemon[3743]: New relevant interface virbr0.IPv4 for mDNS.Apr 15 01:30:04 Tower avahi-daemon[3743]: Registering new address record for 192.168.122.1 on virbr0.IPv4.Apr 15 01:30:04 Tower kernel: virbr0: port 1(virbr0-nic) entered blocking stateApr 15 01:30:04 Tower kernel: virbr0: port 1(virbr0-nic) entered listening stateApr 15 01:30:04 Tower dnsmasq[11630]: started, version 2.78 cachesize 150Apr 15 01:30:04 Tower dnsmasq[11630]: compile time options: IPv6 GNU-getopt no-DBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP no-conntrack ipset auth no-DNSSEC loop-detect inotifyApr 15 01:30:04 Tower dnsmasq-dhcp[11630]: DHCP, IP range 192.168.122.2 -- 192.168.122.254, lease time 1hApr 15 01:30:04 Tower dnsmasq-dhcp[11630]: DHCP, sockets bound exclusively to interface virbr0Apr 15 01:30:04 Tower dnsmasq[11630]: reading /etc/resolv.confApr 15 01:30:04 Tower dnsmasq[11630]: using nameserver 1.1.1.1#53Apr 15 01:30:04 Tower dnsmasq[11630]: using nameserver 8.8.8.8#53Apr 15 01:30:04 Tower dnsmasq[11630]: using nameserver 192.168.1.1#53Apr 15 01:30:04 Tower dnsmasq[11630]: read /etc/hosts - 2 addressesApr 15 01:30:04 Tower dnsmasq[11630]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addressesApr 15 01:30:04 Tower dnsmasq-dhcp[11630]: read /var/lib/libvirt/dnsmasq/default.hostsfileApr 15 01:30:04 Tower kernel: virbr0: port 1(virbr0-nic) entered disabled stateApr 15 01:30:05 Tower emhttpd: error: send_file, 139: Broken pipe (32): sendfile: /usr/local/emhttp/logging.htmApr 15 01:31:39 Tower kernel: ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x4090000 action 0xe frozenApr 15 01:31:39 Tower kernel: ata1.00: irq_stat 0x00400040, connection status changedApr 15 01:31:39 Tower kernel: ata1: SError: { PHYRdyChg 10B8B DevExch }Apr 15 01:31:39 Tower kernel: ata1.00: failed command: FLUSH CACHE EXTApr 15 01:31:39 Tower kernel: ata1.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 5Apr 15 01:31:39 Tower kernel: res 50/00:00:e7:66:12/00:00:e9:00:00/e0 Emask 0x10 (ATA bus error)Apr 15 01:31:39 Tower kernel: ata1.00: status: { DRDY }Apr 15 01:31:39 Tower kernel: ata1: hard resetting linkApr 15 01:31:42 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)Apr 15 01:31:42 Tower kernel: ata1.00: configured for UDMA/33Apr 15 01:31:42 Tower kernel: ata1.00: retrying FLUSH 0xea Emask 0x10Apr 15 01:31:42 Tower kernel: ata1: EH complete 5 Link to comment
JorgeB Posted April 15, 2018 Share Posted April 15, 2018 (is there another way?) Type diagnostics on the console. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.