Einleitung

Ich werdende zur Speicherung meiner privanten Daten und als iSCSI-Ziel der Virtuellen Maschienen auf meinem ESXi-Server einen FreeNAS-Netzwerkspeicher zur Datenspeicherung.

Am Samstag dem 5 Februar hatte mein Netzwerkspeicher einen "Aussetzer" in welchem der FreeNAS für 30 Minuten nicht erreichbar war. Seltsam ist, dass auch die grafischen Aufzeichnungen für diese Zeit ausgesetzt haben.

Ausgangslage

Mein Netzwerkspeicher setzt sich aus folgenden Komponenten zusammen:
- Intel Pinnacle Canyon NUC5PPYH (Intel Pentium N3700, HDMI, USB 3.0 Typ-A)
- Kingston Value RAM (1x, 8GB, DDR3L-1600 (PC3-12800), SODIMM 204)
- WD My Passport (4000GB)
- Samsung 850 EVO Basic (250GB, 2.5")

Fehlerbild

Eventlog

Feb 5 00:00:05 freenas syslog-ng[28590]: Configuration reload request received, reloading configuration;
Feb 5 09:00:04 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs snapshot "data/[email protected]"
Feb 5 09:00:04 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 09:00:05 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 09:00:05 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 09:01:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 09:02:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 09:03:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 09:04:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 09:05:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 09:06:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 09:07:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 09:08:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 09:09:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 09:10:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 09:11:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 09:12:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 09:13:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 09:14:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 09:15:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs snapshot "data/[email protected]"
Feb 5 09:15:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 09:15:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 09:15:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 09:16:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 09:17:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 09:18:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 09:19:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 09:20:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 09:21:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 09:22:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 09:23:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 09:24:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 09:25:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 09:26:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 09:27:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 09:28:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 09:29:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 09:30:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs snapshot "data/[email protected]"
Feb 5 09:30:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 09:30:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 09:30:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 09:31:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 09:32:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 09:33:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 09:34:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 09:35:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 09:36:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 09:37:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 09:38:04 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 09:39:04 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 09:40:05 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 09:41:04 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 09:42:04 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 09:43:05 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 09:44:00 freenas kernel: arp: 192.168.178.32 moved from 02:ff:60:00:05:0a to b8:ae:ed:e9:79:c5 on epair1b
Feb 5 09:44:04 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 09:45:04 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs snapshot "data/[email protected]"
Feb 5 09:45:22 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 09:45:45 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 10:00:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs snapshot "data/[email protected]"
Feb 5 10:00:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 10:00:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 10:15:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs snapshot "data/[email protected]"
Feb 5 10:15:04 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 10:15:04 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 10:30:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs snapshot "data/[email protected]"
Feb 5 10:30:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 10:30:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 10:39:39 freenas notifier: Performing sanity check on Samba configuration: OK
Feb 5 10:39:40 freenas notifier: Stopping mdnsd.
Feb 5 10:39:40 freenas notifier: Waiting for PIDS: 2521.
Feb 5 10:39:40 freenas notifier: Starting mdnsd.
Feb 5 10:39:40 freenas notifier: Cannot 'reload' netatalk. Set netatalk_enable to YES in /etc/rc.conf or use 'onereload' instead of 'reload'.
Feb 5 10:45:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs snapshot "data/[email protected]"
Feb 5 10:45:05 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 10:45:08 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 11:00:04 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs snapshot "data/[email protected]"
Feb 5 11:00:06 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 11:00:08 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 11:15:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs snapshot "data/[email protected]"
Feb 5 11:15:05 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 11:15:07 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 11:16:59 freenas kernel: epair1a: link state changed to DOWN
Feb 5 11:16:59 freenas kernel: epair1a: link state changed to DOWN
Feb 5 11:16:59 freenas kernel: epair1b: link state changed to DOWN
Feb 5 11:16:59 freenas kernel: epair1b: link state changed to DOWN
Feb 5 11:17:25 freenas kernel: epair0a: link state changed to DOWN
Feb 5 11:17:25 freenas kernel: epair0a: link state changed to DOWN
Feb 5 11:17:25 freenas kernel: epair0b: link state changed to DOWN
Feb 5 11:17:25 freenas kernel: epair0b: link state changed to DOWN
Feb 5 11:17:25 freenas kernel: re0: link state changed to DOWN
Feb 5 11:17:25 freenas kernel: re0: link state changed to DOWN
Feb 5 11:17:25 freenas kernel: bridge0: link state changed to DOWN
Feb 5 11:17:25 freenas kernel: bridge0: link state changed to DOWN
Feb 5 11:17:25 freenas syslog-ng[28590]: I/O error occurred while writing; fd='20', error='No route to host (65)'
Feb 5 11:17:25 freenas syslog-ng[28590]: Error opening file for writing; filename='/dev/console', error='Device not configured (6)'
Feb 5 11:17:25 freenas syslog-ng[28590]: Syslog connection broken; fd='0', server='AF_INET(192.168.178.26:514)', time_reopen='60'
Feb 5 11:17:26 freenas kernel: re0: promiscuous mode disabled
Feb 5 11:17:29 freenas dhclient: New IP Address (re0): 192.168.178.32
Feb 5 11:17:29 freenas dhclient: New Subnet Mask (re0): 255.255.255.0
Feb 5 11:17:29 freenas kernel: re0: link state changed to UP
Feb 5 11:17:29 freenas kernel: re0: link state changed to UP
Feb 5 11:17:29 freenas dhclient: New Broadcast Address (re0): 192.168.1.255
Feb 5 11:17:29 freenas dhclient: New Routers (re0): 192.168.178.1
Feb 5 11:17:30 freenas WARNING: 192.168.178.4 (iqn.1998-01.com.vmware:esx-7a41f93e): no ping reply (NOP-Out) after 5 seconds; dropping connection
Feb 5 11:17:49 freenas notifier: Performing sanity check on nginx configuration:
Feb 5 11:17:49 freenas notifier: nginx: the configuration file /usr/local/etc/nginx/nginx.conf syntax is ok
Feb 5 11:17:49 freenas notifier: nginx: configuration file /usr/local/etc/nginx/nginx.conf test is successful
Feb 5 11:17:52 freenas bridge0: Ethernet address: 02:2e:88:13:7f:00
Feb 5 11:17:52 freenas kernel: re0: promiscuous mode enabled
Feb 5 11:17:52 freenas kernel: bridge0: link state changed to UP
Feb 5 11:17:52 freenas kernel: bridge0: link state changed to UP
Feb 5 11:17:52 freenas epair0a: Ethernet address: 02:ff:60:00:04:0a
Feb 5 11:17:52 freenas epair0b: Ethernet address: 02:ff:b0:00:05:0b
Feb 5 11:17:52 freenas kernel: epair0a: link state changed to UP
Feb 5 11:17:52 freenas kernel: epair0a: link state changed to UP
Feb 5 11:17:52 freenas kernel: epair0b: link state changed to UP
Feb 5 11:17:52 freenas kernel: epair0b: link state changed to UP
Feb 5 11:17:52 freenas kernel: epair0a: promiscuous mode enabled
Feb 5 11:17:52 freenas kernel: re0: link state changed to DOWN
Feb 5 11:17:52 freenas kernel: re0: link state changed to DOWN
Feb 5 11:17:52 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair0b
Feb 5 11:17:52 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair0b
Feb 5 11:17:56 freenas kernel: re0: link state changed to UP
Feb 5 11:17:56 freenas kernel: re0: link state changed to UP
Feb 5 11:17:56 freenas WARNING: 192.168.178.4 (iqn.1998-01.com.vmware:esx-7a41f93e): no ping reply (NOP-Out) after 5 seconds; dropping connection
Feb 5 11:17:59 freenas dhclient: New IP Address (re0): 192.168.178.32
Feb 5 11:17:59 freenas dhclient: New Subnet Mask (re0): 255.255.255.0
Feb 5 11:17:59 freenas dhclient: New Broadcast Address (re0): 192.168.1.255
Feb 5 11:17:59 freenas dhclient: New Routers (re0): 192.168.178.1
Feb 5 11:18:13 freenas manage.py: [freeadmin.navtree:577] Konnte http://192.168.178.32/plugins/resilio/1/_s/treemenu nicht empfangen: HTTP Error 503: OK
Feb 5 11:18:20 freenas kernel: ifa_del_loopback_route: deletion failed: 48
Feb 5 11:18:20 freenas Freed UMA keg (udp_inpcb) was not empty (120 items). Lost 12 pages of memory.
Feb 5 11:18:20 freenas Freed UMA keg (udpcb) was not empty (1169 items). Lost 7 pages of memory.
Feb 5 11:18:20 freenas Freed UMA keg (tcptw) was not empty (540 items). Lost 12 pages of memory.
Feb 5 11:18:20 freenas Freed UMA keg (tcp_inpcb) was not empty (120 items). Lost 12 pages of memory.
Feb 5 11:18:20 freenas Freed UMA keg (tcpcb) was not empty (45 items). Lost 15 pages of memory.
Feb 5 11:18:20 freenas Freed UMA keg (ripcb) was not empty (120 items). Lost 12 pages of memory.
Feb 5 11:18:20 freenas hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
Feb 5 11:18:20 freenas hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required
Feb 5 11:18:30 freenas syslog-ng[28590]: Syslog connection established; fd='5', server='AF_INET(192.168.178.26:514)', local='AF_INET(0.0.0.0:514)'
Feb 5 11:18:30 freenas syslog-ng[28590]: Error opening file for writing; filename='/dev/console', error='Device not configured (6)'
Feb 5 11:19:25 freenas syslog-ng[28590]: Error opening file for writing; filename='/dev/console', error='Device not configured (6)'
Feb 5 11:22:17 freenas syslog-ng[1424]: syslog-ng starting up; version='3.6.4'
Feb 5 11:22:17 freenas Copyright (c) 1992-2016 The FreeBSD Project.
Feb 5 11:22:17 freenas Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
Feb 5 11:22:17 freenas The Regents of the University of California. All rights reserved.
Feb 5 11:22:17 freenas FreeBSD is a registered trademark of The FreeBSD Foundation.
Feb 5 11:22:17 freenas FreeBSD 10.3-STABLE #0 r295946+1805185(9.10.2-STABLE): Wed Jan 11 17:12:42 UTC 2017
Feb 5 11:22:17 freenas root@gauntlet:/freenas-9.10-releng/_BE/objs/freenas-9.10-releng/_BE/os/sys/FreeNAS.amd64 amd64
Feb 5 11:22:17 freenas FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512
Feb 5 11:22:17 freenas CPU: Intel(R) Pentium(R) CPU N3700 @ 1.60GHz (1600.05-MHz K8-class CPU)
Feb 5 11:22:17 freenas Origin="GenuineIntel" Id=0x406c3 Family=0x6 Model=0x4c Stepping=3
Feb 5 11:22:17 freenas Features=0xbfebfbff
Feb 5 11:22:17 freenas Features2=0x43d8e3bf
Feb 5 11:22:17 freenas AMD Features=0x28100800
Feb 5 11:22:17 freenas AMD Features2=0x101
Feb 5 11:22:17 freenas Structured Extended Features=0x2282
Feb 5 11:22:17 freenas VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID
Feb 5 11:22:17 freenas TSC: P-state invariant, performance statistics
Feb 5 11:22:17 freenas real memory = 10737418240 (10240 MB)
Feb 5 11:22:17 freenas avail memory = 8146157568 (7768 MB)
Feb 5 11:22:17 freenas Event timer "LAPIC" quality 600
Feb 5 11:22:17 freenas ACPI APIC Table:
Feb 5 11:22:17 freenas FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
Feb 5 11:22:17 freenas FreeBSD/SMP: 1 package(s) x 4 core(s)
Feb 5 11:22:17 freenas cpu0 (BSP): APIC ID: 0
Feb 5 11:22:17 freenas cpu1 (AP): APIC ID: 2
Feb 5 11:22:17 freenas cpu2 (AP): APIC ID: 4
Feb 5 11:22:17 freenas cpu3 (AP): APIC ID: 6
Feb 5 11:22:17 freenas random: initialized
Feb 5 11:22:17 freenas WARNING: VIMAGE (virtualized network stack) is a highly experimental feature.
Feb 5 11:22:17 freenas ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/Gpe0Block: 128/32 (20160527/tbfadt-650)
Feb 5 11:22:17 freenas ioapic0 irqs 0-114 on motherboard
Feb 5 11:22:17 freenas kbd1 at kbdmux0
Feb 5 11:22:17 freenas module_register_init: MOD_LOAD (vesa, 0xffffffff80e48970, 0) error 19
Feb 5 11:22:17 freenas aesni0: on motherboard
Feb 5 11:22:17 freenas padlock0: No ACE support.
Feb 5 11:22:17 freenas cryptosoft0: on motherboard
Feb 5 11:22:17 freenas acpi0: on motherboard
Feb 5 11:22:17 freenas acpi0: Power Button (fixed)
Feb 5 11:22:17 freenas unknown: I/O range not supported
Feb 5 11:22:17 freenas cpu0: on acpi0
Feb 5 11:22:17 freenas cpu1: on acpi0
Feb 5 11:22:17 freenas cpu2: on acpi0
Feb 5 11:22:17 freenas cpu3: on acpi0
Feb 5 11:22:17 freenas attimer0: port 0x40-0x43,0x50-0x53 irq 0 on acpi0
Feb 5 11:22:17 freenas Timecounter "i8254" frequency 1193182 Hz quality 0
Feb 5 11:22:17 freenas Event timer "i8254" frequency 1193182 Hz quality 100
Feb 5 11:22:17 freenas Timecounter "ACPI-safe" frequency 3579545 Hz quality 850
Feb 5 11:22:17 freenas acpi_timer0: port 0x408-0x40b on acpi0
Feb 5 11:22:17 freenas pcib0: port 0xcf8-0xcff on acpi0
Feb 5 11:22:17 freenas pcib0: _OSC returned error 0x4
Feb 5 11:22:17 freenas pci0: on pcib0
Feb 5 11:22:17 freenas vgapci0: port 0xf000-0xf03f mem 0x80000000-0x80ffffff,0x88000000-0x8fffffff irq 16 at device 2.0 on pci0
Feb 5 11:22:17 freenas vgapci0: Boot video device
Feb 5 11:22:17 freenas pci0: at device 18.0 (no driver attached)
Feb 5 11:22:17 freenas ahci0: port 0xf060-0xf07f mem 0x8141b000-0x8141b7ff irq 19 at device 19.0 on pci0
Feb 5 11:22:17 freenas ahci0: AHCI v1.31 with 2 6Gbps ports, Port Multiplier not supported
Feb 5 11:22:17 freenas ahcich0: at channel 0 on ahci0
Feb 5 11:22:17 freenas ahcich1: at channel 1 on ahci0
Feb 5 11:22:17 freenas xhci0: mem 0x81400000-0x8140ffff irq 20 at device 20.0 on pci0
Feb 5 11:22:17 freenas xhci0: 32 bytes context size, 64-bit DMA
Feb 5 11:22:17 freenas usbus0: waiting for BIOS to give up control
Feb 5 11:22:17 freenas usbus0 on xhci0
Feb 5 11:22:17 freenas pci0: at device 24.0 (no driver attached)
Feb 5 11:22:17 freenas pci0: at device 24.6 (no driver attached)
Feb 5 11:22:17 freenas pci0: at device 24.7 (no driver attached)
Feb 5 11:22:17 freenas pci0: at device 26.0 (no driver attached)
Feb 5 11:22:17 freenas pci0: at device 27.0 (no driver attached)
Feb 5 11:22:17 freenas pcib1: at device 28.0 on pci0
Feb 5 11:22:17 freenas pci1: on pcib1
Feb 5 11:22:17 freenas pcib2: at device 28.1 on pci0
Feb 5 11:22:17 freenas pci2: on pcib2
Feb 5 11:22:17 freenas pci2: at device 0.0 (no driver attached)
Feb 5 11:22:17 freenas pcib3: at device 28.2 on pci0
Feb 5 11:22:17 freenas pci3: on pcib3
Feb 5 11:22:17 freenas re0: port 0xe000-0xe0ff mem 0x81204000-0x81204fff,0x81200000-0x81203fff irq 18 at device 0.0 on pci3
Feb 5 11:22:17 freenas re0: Using 1 MSI-X message
Feb 5 11:22:17 freenas re0: Chip rev. 0x54000000
Feb 5 11:22:17 freenas re0: MAC rev. 0x00100000
Feb 5 11:22:17 freenas miibus0: on re0
Feb 5 11:22:17 freenas rgephy0: PHY 1 on miibus0
Feb 5 11:22:17 freenas rgephy0: none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow
Feb 5 11:22:17 freenas re0: Using defaults for TSO: 65518/35/2048
Feb 5 11:22:17 freenas re0: Ethernet address: b8:ae:ed:e9:79:c5
Feb 5 11:22:17 freenas isab0: at device 31.0 on pci0
Feb 5 11:22:17 freenas isa0: on isab0
Feb 5 11:22:17 freenas acpi_lid0: on acpi0
Feb 5 11:22:17 freenas acpi_button0: on acpi0
Feb 5 11:22:17 freenas acpi_tz0: on acpi0
Feb 5 11:22:17 freenas ichwd0: on isa0
Feb 5 11:22:17 freenas orm0: at iomem 0xcf800-0xd07ff on isa0
Feb 5 11:22:17 freenas atkbdc0: at port 0x60,0x64 on isa0
Feb 5 11:22:17 freenas atkbd0: irq 1 on atkbdc0
Feb 5 11:22:17 freenas kbd0 at atkbd0
Feb 5 11:22:17 freenas atkbd0: [GIANT-LOCKED]
Feb 5 11:22:17 freenas atrtc0: at port 0x70 irq 8 on isa0
Feb 5 11:22:17 freenas atrtc0: Warning: Couldn't map I/O.
Feb 5 11:22:17 freenas Event timer "RTC" frequency 32768 Hz quality 0
Feb 5 11:22:17 freenas coretemp0: on cpu0
Feb 5 11:22:17 freenas est0: on cpu0
Feb 5 11:22:17 freenas coretemp1: on cpu1
Feb 5 11:22:17 freenas est1: on cpu1
Feb 5 11:22:17 freenas coretemp2: on cpu2
Feb 5 11:22:17 freenas est2: on cpu2
Feb 5 11:22:17 freenas coretemp3: on cpu3
Feb 5 11:22:17 freenas est3: on cpu3
Feb 5 11:22:17 freenas random: unblocking device.
Feb 5 11:22:17 freenas usbus0: 5.0Gbps Super Speed USB v3.0
Feb 5 11:22:17 freenas ZFS filesystem version: 5
Feb 5 11:22:17 freenas ZFS storage pool version: features support (5000)
Feb 5 11:22:17 freenas Timecounters tick every 1.000 msec
Feb 5 11:22:17 freenas ipfw2 (+ipv6) initialized, divert enabled, nat enabled, default to accept, logging disabled
Feb 5 11:22:17 freenas ugen0.1: at usbus0
Feb 5 11:22:17 freenas uhub0: on usbus0
Feb 5 11:22:17 freenas uhub0: 13 ports with 13 removable, self powered
Feb 5 11:22:17 freenas ugen0.2: at usbus0
Feb 5 11:22:17 freenas uhub1: on usbus0
Feb 5 11:22:17 freenas uhub1: MTT enabled
Feb 5 11:22:17 freenas uhub1: 4 ports with 4 removable, self powered
Feb 5 11:22:17 freenas ugen0.3: at usbus0
Feb 5 11:22:17 freenas ugen0.4: at usbus0
Feb 5 11:22:17 freenas umass0: on usbus0
Feb 5 11:22:17 freenas umass0: SCSI over Bulk-Only; quirks = 0x0100
Feb 5 11:22:17 freenas umass0:3:0:-1: Attached to scbus3
Feb 5 11:22:17 freenas ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
Feb 5 11:22:17 freenas ada0: ACS-2 ATA SATA 3.x device
Feb 5 11:22:17 freenas ada0: Serial Number S21PNXAG724316N
Feb 5 11:22:17 freenas ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 512bytes)
Feb 5 11:22:17 freenas ada0: Command Queueing enabled
Feb 5 11:22:17 freenas ada0: 238475MB (488397168 512 byte sectors)
Feb 5 11:22:17 freenas ada0: quirks=0x1
Feb 5 11:22:17 freenas ada0: Previously was known as ad4
Feb 5 11:22:17 freenas da0 at umass-sim0 bus 0 scbus3 target 0 lun 0
Feb 5 11:22:17 freenas da0: Fixed Direct Access SPC-4 SCSI device
Feb 5 11:22:17 freenas da0: Serial Number NA83RPVJ
Feb 5 11:22:17 freenas da0: 400.000MB/s transfers
Feb 5 11:22:17 freenas da0: 3815447MB (7814037167 512 byte sectors)
Feb 5 11:22:17 freenas da0: quirks=0x2
Feb 5 11:22:17 freenas SMP: AP CPU #2 Launched!
Feb 5 11:22:17 freenas SMP: AP CPU #1 Launched!
Feb 5 11:22:17 freenas SMP: AP CPU #3 Launched!
Feb 5 11:22:17 freenas Timecounter "TSC" frequency 1600051720 Hz quality 1000
Feb 5 11:22:17 freenas Trying to mount root from zfs:freenas-boot/ROOT/9.10.2-U1 []...
Feb 5 11:22:17 freenas GEOM_RAID5: Module loaded, version 1.3.20140711.62 (rev f91e28e40bf7)
Feb 5 11:22:17 freenas GEOM_ELI: Device gptid/b50cd7b1-d5e8-11e6-b564-b8aeede979c5.eli created.
Feb 5 11:22:17 freenas GEOM_ELI: Encryption: AES-XTS 128
Feb 5 11:22:17 freenas GEOM_ELI: Crypto: hardware
Feb 5 11:22:17 freenas pmc: Unknown Intel CPU.
Feb 5 11:22:17 freenas hwpmc: SOFT/16/64/0x67
Feb 5 11:22:17 freenas kernel: re0: link state changed to DOWN
Feb 5 11:22:17 freenas kernel: re0: link state changed to DOWN
Feb 5 11:22:17 freenas kernel: re0: link state changed to UP
Feb 5 11:22:17 freenas kernel: re0: link state changed to UP
Feb 5 11:22:19 freenas GEOM_ELI: Device da0p1.eli created.
Feb 5 11:22:19 freenas GEOM_ELI: Encryption: AES-XTS 128
Feb 5 11:22:19 freenas GEOM_ELI: Crypto: hardware
Feb 5 11:22:29 freenas nfsd: can't register svc name
Feb 5 11:22:29 freenas ntpd[1869]: ntpd 4.2.8p9-a (1): Starting
Feb 5 11:22:38 freenas root: /etc/rc: WARNING: failed precmd routine for vmware_guestd
Feb 5 11:22:58 freenas bridge0: Ethernet address: 02:2e:88:13:7f:00
Feb 5 11:22:58 freenas kernel: re0: promiscuous mode enabled
Feb 5 11:22:58 freenas kernel: bridge0: link state changed to UP
Feb 5 11:22:58 freenas kernel: bridge0: link state changed to UP
Feb 5 11:22:58 freenas epair0a: Ethernet address: 02:ff:60:00:04:0a
Feb 5 11:22:58 freenas epair0b: Ethernet address: 02:ff:b0:00:05:0b
Feb 5 11:22:58 freenas kernel: epair0a: link state changed to UP
Feb 5 11:22:58 freenas kernel: epair0a: link state changed to UP
Feb 5 11:22:58 freenas kernel: epair0b: link state changed to UP
Feb 5 11:22:58 freenas kernel: epair0b: link state changed to UP
Feb 5 11:22:58 freenas kernel: epair0a: promiscuous mode enabled
Feb 5 11:22:58 freenas kernel: re0: link state changed to DOWN
Feb 5 11:22:58 freenas kernel: re0: link state changed to DOWN
Feb 5 11:22:58 freenas syslog-ng[1424]: I/O error occurred while writing; fd='21', error='No route to host (65)'
Feb 5 11:22:58 freenas syslog-ng[1424]: Error opening file for writing; filename='/dev/console', error='Device not configured (6)'
Feb 5 11:22:58 freenas syslog-ng[1424]: Syslog connection broken; fd='21', server='AF_INET(192.168.178.26:514)', time_reopen='60'
Feb 5 11:22:59 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair0b
Feb 5 11:22:59 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair0b
Feb 5 11:23:02 freenas kernel: re0: link state changed to UP
Feb 5 11:23:02 freenas kernel: re0: link state changed to UP
Feb 5 11:23:03 freenas WARNING: 192.168.178.4 (iqn.1998-01.com.vmware:esx-7a41f93e): no ping reply (NOP-Out) after 5 seconds; dropping connection
Feb 5 11:23:07 freenas dhclient: New IP Address (re0): 192.168.178.32
Feb 5 11:23:07 freenas dhclient: New Subnet Mask (re0): 255.255.255.0
Feb 5 11:23:07 freenas dhclient: New Broadcast Address (re0): 192.168.1.255
Feb 5 11:23:07 freenas dhclient: New Routers (re0): 192.168.178.1
Feb 5 11:23:55 freenas epair1a: Ethernet address: 02:ff:60:00:05:0a
Feb 5 11:23:55 freenas epair1b: Ethernet address: 02:ff:b0:00:06:0b
Feb 5 11:23:55 freenas kernel: epair1a: link state changed to UP
Feb 5 11:23:55 freenas kernel: epair1a: link state changed to UP
Feb 5 11:23:55 freenas kernel: epair1b: link state changed to UP
Feb 5 11:23:55 freenas kernel: epair1b: link state changed to UP
Feb 5 11:23:55 freenas kernel: epair1a: promiscuous mode enabled
Feb 5 11:23:55 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair1b
Feb 5 11:23:55 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair1b
Feb 5 11:23:58 freenas syslog-ng[1424]: Error opening file for writing; filename='/dev/console', error='Device not configured (6)'
Feb 5 11:23:58 freenas syslog-ng[1424]: Syslog connection established; fd='24', server='AF_INET(192.168.178.26:514)', local='AF_INET(0.0.0.0:514)'
Feb 5 11:24:40 freenas getty[6925]: open /dev/ttyv0: No such file or directory
Feb 5 11:24:40 freenas getty[6927]: open /dev/ttyv2: No such file or directory
Feb 5 11:24:40 freenas getty[6932]: open /dev/ttyv7: No such file or directory
Feb 5 11:24:40 freenas getty[6928]: open /dev/ttyv3: No such file or directory
Feb 5 11:24:40 freenas getty[6929]: open /dev/ttyv4: No such file or directory
Feb 5 11:24:40 freenas getty[6926]: open /dev/ttyv1: No such file or directory
Feb 5 11:24:40 freenas getty[6930]: open /dev/ttyv5: No such file or directory
Feb 5 11:24:40 freenas getty[6931]: open /dev/ttyv6: No such file or directory
Feb 5 11:24:58 freenas syslog-ng[1424]: Error opening file for writing; filename='/dev/console', error='Device not configured (6)'
Feb 5 11:25:58 freenas syslog-ng[1424]: Error opening file for writing; filename='/dev/console', error='Device not configured (6)'
Feb 5 11:26:58 freenas syslog-ng[1424]: Error opening file for writing; filename='/dev/console', error='Device not configured (6)'
Feb 5 11:27:58 freenas syslog-ng[1424]: Error opening file for writing; filename='/dev/console', error='Device not configured (6)'
Feb 5 11:28:58 freenas syslog-ng[1424]: Error opening file for writing; filename='/dev/console', error='Device not configured (6)'
Feb 5 11:29:58 freenas syslog-ng[1424]: Error opening file for writing; filename='/dev/console', error='Device not configured (6)'
Feb 5 11:30:03 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs snapshot "data/[email protected]"
Feb 5 11:30:05 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 11:30:08 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 11:30:59 freenas syslog-ng[1424]: Error opening file for writing; filename='/dev/console', error='Device not configured (6)'
Feb 5 11:30:59 freenas syslog-ng[1424]: Error opening file for writing; filename='/dev/console', error='Device not configured (6)'
Feb 5 11:31:59 freenas syslog-ng[1424]: Error opening file for writing; filename='/dev/console', error='Device not configured (6)'
Feb 5 11:32:59 freenas syslog-ng[1424]: Error opening file for writing; filename='/dev/console', error='Device not configured (6)'
Feb 5 11:33:59 freenas syslog-ng[1424]: Error opening file for writing; filename='/dev/console', error='Device not configured (6)'
Feb 5 11:34:59 freenas syslog-ng[1424]: Error opening file for writing; filename='/dev/console', error='Device not configured (6)'
Feb 5 11:35:59 freenas syslog-ng[1424]: Error opening file for writing; filename='/dev/console', error='Device not configured (6)'
Feb 5 11:36:59 freenas syslog-ng[1424]: Error opening file for writing; filename='/dev/console', error='Device not configured (6)'
Feb 5 11:37:59 freenas syslog-ng[1424]: Error opening file for writing; filename='/dev/console', error='Device not configured (6)'
Feb 5 11:38:59 freenas syslog-ng[1424]: Error opening file for writing; filename='/dev/console', error='Device not configured (6)'
Feb 5 11:39:59 freenas syslog-ng[1424]: Error opening file for writing; filename='/dev/console', error='Device not configured (6)'
Feb 5 11:40:33 freenas kernel: arp: 192.168.178.32 moved from 02:ff:60:00:05:0a to b8:ae:ed:e9:79:c5 on epair1b
Feb 5 11:40:59 freenas syslog-ng[1424]: Error opening file for writing; filename='/dev/console', error='Device not configured (6)'
Feb 5 11:41:59 freenas syslog-ng[1424]: Error opening file for writing; filename='/dev/console', error='Device not configured (6)'
Feb 5 11:42:59 freenas syslog-ng[1424]: Error opening file for writing; filename='/dev/console', error='Device not configured (6)'
Feb 5 11:43:59 freenas syslog-ng[1424]: Error opening file for writing; filename='/dev/console', error='Device not configured (6)'
Feb 5 11:44:59 freenas syslog-ng[1424]: Error opening file for writing; filename='/dev/console', error='Device not configured (6)'
Feb 5 11:45:04 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs snapshot "data/[email protected]"
Feb 5 11:45:05 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 11:45:08 freenas autosnap.py: [tools.autosnap:66] Popen()ing: /sbin/zfs destroy -r -d "data/[email protected]"
Feb 5 11:45:59 freenas syslog-ng[1424]: Error opening file for writing; filename='/dev/console', error='Device not configured (6)'

Weiteres Vorgehen

Ich werde mein Problem mal in der FreeNAS Mailing-Liste posten und sehen, ob jemand im Log etwas sieht was auf ein Problem hinweisen könnte. Meine Vermuting ist, dass die Snapshot-Löschungen etwas damit zutun haben da diese im Vergleich zu vorher sehr lange gedauert haben.