Daily/Weekly Maintenance

Status
Not open for further replies.

Andrew076

Patron
Joined
Apr 5, 2015
Messages
206
I recently setup a FreeNAS server and I it appears to be running well. I have copied about 500 GB worth of pictures on it as a starting point to verify setup etc.

I have setup and started the CrashPlan plugin and it is currently backing up the pictures (although it says it is going to take 30 days to complete...)

I mirrored the USB boot drives and have the most recent version of FreeNAS running.

So, my question is what, if anything, is recommended to run in the background or check the disks etc. Something is already happening as I get an e-mail at 3:00 in the morning every day.

Thanks
 

SweetAndLow

Sweet'NASty
Joined
Nov 6, 2013
Messages
6,421
you shouldn't get an email every day what exactly does the email say. Some other things that you can configure are short smart tests and long smart tests as well as a scrub but I think this scrub is already configured properly.
 

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,504
Some other things that you can should configure are short smart tests and long smart tests as well as a scrub but I think this scrub is already configured properly.
Fixed that for you. OP, there isn't anything you need to manually do on any sort of periodic schedule, but you should definitely enable the SMART service, set an email address in that service, and set up regular short and long tests (I do short daily and long weekly; others may vary, but at a bare minimum you'd want a long SMART test monthly). When you set up your pool, FreeNAS should have automatically scheduled a scrub every 35 days. I prefer a bit more often than that, so I've set mine to every two weeks.

Older versions of FreeNAS sent a daily status email, but 9.2+ have done away with that. If you're getting an email, it's because your system thinks there's something out of the ordinary going on.
 

Andrew076

Patron
Joined
Apr 5, 2015
Messages
206
That could be. I just assumed because I got a message every day. The first few messages were the same telling me about an update that I didn't install till yesterday (I needed a new keyboard for the boot to go through and didn't want to take it from my desktop): (see below)

A new update is available for the FreeNAS-9.3-STABLE train.
Changelog:
#6323 Bug Normal Group Ownership does not resolve from "account unknown"
#6723 Bug Normal Fix Samba SID generation with group mappings
#8828 Bug Normal Service WebDAV/apache24 unable to start due to syntax error
#8953 Bug Normal SMART errors now generate Alerts
#9149 Bug Normal API request for invalid values should return HTTP 409
#9150 Bug Normal Document iscsi_target_extent_xen field in API docs
#9182 Bug Normal High Point driver update which provides better 4Kn drive support and exposes more disk details

Then I got a new e-mail last night - which concerned me on the data as I didn't understand it all but it appears to be as a result of the update?

freenas.local changes in mounted filesystems:
18c18
< freenas-boot/ROOT/default / zfs rw,noatime,nfsv4acls 0 0
---
> freenas-boot/ROOT/FreeNAS-9.3-STABLE-201504152200 / zfs rw,noatime,nfsv4acls 0 0

freenas.local kernel log messages:
> epair1a: link state changed to DOWN
> epair1b: link state changed to DOWN
> epair0a: link state changed to DOWN
> epair0b: link state changed to DOWN
> igb0: link state changed to DOWN
> bridge0: link state changed to DOWN
> igb0: promiscuous mode disabled
> ifa_del_loopback_route: deletion failed
> Freed UMA keg (udp_inpcb) was not empty (80 items). Lost 8 pages of memory.
> Freed UMA keg (udpcb) was not empty (1008 items). Lost 6 pages of memory.
> Freed UMA keg (tcpreass) was not empty (252 items). Lost 3 pages of memory.
> Freed UMA keg (tcptw) was not empty (400 items). Lost 8 pages of memory.
> Freed UMA keg (tcp_inpcb) was not empty (90 items). Lost 9 pages of memory.
> Freed UMA keg (tcpcb) was not empty (44 items). Lost 11 pages of memory.
> Freed UMA keg (ripcb) was not empty (60 items). Lost 6 pages of memory.
> hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
> hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required
> pid 1873 (syslog-ng), uid 0: exited on signal 6 (core dumped)
> Waiting (max 60 seconds) for system process `vnlru' to stop...done
> Waiting (max 60 seconds) for system process `syncer' to stop...
> Syncing disks, vnodes remaining...0 0 0 0 0 done
> Waiting (max 60 seconds) for system process `bufdaemon' to stop...done
> All buffers synced.
> Copyright (c) 1992-2014 The FreeBSD Project.
> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
> The Regents of the University of California. All rights reserved.
> FreeBSD is a registered trademark of The FreeBSD Foundation.
> FreeBSD 9.3-RELEASE-p13 #4 r281084+c7bb047: Wed Apr 15 15:03:01 PDT 2015
> root@build3.ixsystems.com:/tank/home/jkh/build/FN/objs/os-base/amd64/tank/home/jkh/build/FN/FreeBSD/src/sys/FREENAS.amd64 amd64
> gcc version 4.2.1 20070831 patched [FreeBSD]
> CPU: Intel(R) Xeon(R) CPU E3-1230 v3 @ 3.30GHz (3300.07-MHz K8-class CPU)
> Origin = "GenuineIntel" Id = 0x306c3 Family = 0x6 Model = 0x3c Stepping = 3
> Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
> Features2=0x7ffafbff<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,<b11>,FMA,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND>
> AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM>
> AMD Features2=0x21<LAHF,ABM>
> Standard Extended Features=0x2fbb<GSFSBASE,TSCADJ,SMEP,ENHMOVSB,INVPCID>
> TSC: P-state invariant, performance statistics
> real memory = 17716740096 (16896 MB)
> avail memory = 16484061184 (15720 MB)
> Event timer "LAPIC" quality 600
> ACPI APIC Table: <SUPERM SMCI--MB>
> FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs
> FreeBSD/SMP: 1 package(s) x 4 core(s) x 2 SMT threads
> cpu0 (BSP): APIC ID: 0
> cpu1 (AP): APIC ID: 1
> cpu2 (AP): APIC ID: 2
> cpu3 (AP): APIC ID: 3
> cpu4 (AP): APIC ID: 4
> cpu5 (AP): APIC ID: 5
> cpu6 (AP): APIC ID: 6
> cpu7 (AP): APIC ID: 7
> WARNING: VIMAGE (virtualized network stack) is a highly experimental feature.
> ACPI Warning: FADT (revision 5) is longer than ACPI 5.0 version, truncating length 268 to 256 (20111123/tbfadt-325)
> ioapic0 <Version 2.0> irqs 0-23 on motherboard
> ispfw: registered firmware <isp_1040>
> ispfw: registered firmware <isp_1040_it>
> ispfw: registered firmware <isp_1080>
> ispfw: registered firmware <isp_1080_it>
> ispfw: registered firmware <isp_12160>
> ispfw: registered firmware <isp_12160_it>
> ispfw: registered firmware <isp_2100>
> ispfw: registered firmware <isp_2200>
> ispfw: registered firmware <isp_2300>
> ispfw: registered firmware <isp_2322>
> ispfw: registered firmware <isp_2400>
> ispfw: registered firmware <isp_2400_multi>
> ispfw: registered firmware <isp_2500>
> ispfw: registered firmware <isp_2500_multi>
> kbd1 at kbdmux0
> cryptosoft0: <software crypto> on motherboard
> aesni0: <AES-CBC,AES-XTS> on motherboard
> padlock0: No ACE support.
> acpi0: <SUPERM SMCI--MB> on motherboard
> acpi0: Power Button (fixed)
> cpu0: <ACPI CPU> on acpi0
> cpu1: <ACPI CPU> on acpi0
> cpu2: <ACPI CPU> on acpi0
> cpu3: <ACPI CPU> on acpi0
> cpu4: <ACPI CPU> on acpi0
> cpu5: <ACPI CPU> on acpi0
> cpu6: <ACPI CPU> on acpi0
> cpu7: <ACPI CPU> on acpi0
> hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
> Timecounter "HPET" frequency 14318180 Hz quality 950
> Event timer "HPET" frequency 14318180 Hz quality 550
> atrtc0: <AT realtime clock> port 0x70-0x77 irq 8 on acpi0
> Event timer "RTC" frequency 32768 Hz quality 0
> attimer0: <AT timer> port 0x40-0x43,0x50-0x53 irq 0 on acpi0
> Timecounter "i8254" frequency 1193182 Hz quality 0
> Event timer "i8254" frequency 1193182 Hz quality 100
> Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
> acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1808-0x180b on acpi0
> pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
> pci0: <ACPI PCI bus> on pcib0
> pci0: <serial bus, USB> at device 20.0 (no driver attached)
> em0: <Intel(R) PRO/1000 Network Connection 7.4.2> port 0xf020-0xf03f mem 0xf7200000-0xf721ffff,0xf7235000-0xf7235fff irq 20 at device 25.0 on pci0
> em0: Using an MSI interrupt
> em0: Ethernet address: 00:25:90:47:79:df
> ehci0: <EHCI (generic) USB 2.0 controller> mem 0xf7234000-0xf72343ff irq 16 at device 26.0 on pci0
> usbus0: EHCI version 1.0
> usbus0 on ehci0
> pcib1: <ACPI PCI-PCI bridge> irq 16 at device 28.0 on pci0
> pci1: <ACPI PCI bus> on pcib1
> pcib2: <ACPI PCI-PCI bridge> at device 0.0 on pci1
> pci2: <ACPI PCI bus> on pcib2
> vgapci0: <VGA-compatible display> port 0xe000-0xe07f mem 0xf6000000-0xf6ffffff,0xf7000000-0xf701ffff irq 16 at device 0.0 on pci2
> vgapci0: Boot video device
> pcib3: <ACPI PCI-PCI bridge> irq 17 at device 28.1 on pci0
> pci3: <ACPI PCI bus> on pcib3
> igb0: <Intel(R) PRO/1000 Network Connection version - 2.4.0> port 0xd000-0xd01f mem 0xf7100000-0xf717ffff,0xf7180000-0xf7183fff irq 17 at device 0.0 on pci3
> igb0: Using MSIX interrupts with 5 vectors
> igb0: Ethernet address: 00:25:90:47:79:de
> igb0: Bound queue 0 to cpu 0
> igb0: Bound queue 1 to cpu 1
> igb0: Bound queue 2 to cpu 2
> igb0: Bound queue 3 to cpu 3
> ehci1: <EHCI (generic) USB 2.0 controller> mem 0xf7233000-0xf72333ff irq 23 at device 29.0 on pci0
> usbus1: EHCI version 1.0
> usbus1 on ehci1
> isab0: <PCI-ISA bridge> at device 31.0 on pci0
> isa0: <ISA bus> on isab0
> ahci0: <Intel Lynx Point AHCI SATA controller> port 0xf070-0xf077,0xf060-0xf063,0xf050-0xf057,0xf040-0xf043,0xf000-0xf01f mem 0xf7232000-0xf72327ff irq 19 at device 31.2 on pci0
> ahci0: AHCI v1.30 with 6 6Gbps ports, Port Multiplier not supported
> ahcich0: <AHCI channel> at channel 0 on ahci0
> ahcich1: <AHCI channel> at channel 1 on ahci0
> ahcich2: <AHCI channel> at channel 2 on ahci0
> ahcich3: <AHCI channel> at channel 3 on ahci0
> ahcich4: <AHCI channel> at channel 4 on ahci0
> ahcich5: <AHCI channel> at channel 5 on ahci0
> acpi_button0: <Sleep Button> on acpi0
> acpi_button1: <Power Button> on acpi0
> acpi_tz0: <Thermal Zone> on acpi0
> acpi_tz1: <Thermal Zone> on acpi0
> uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
> uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0
> orm0: <ISA Option ROMs> at iomem 0xc0000-0xc7fff,0xc8000-0xc8fff on isa0
> sc0: <System console> at flags 0x100 on isa0
> sc0: CGA <16 virtual consoles, flags=0x300>
> vga0: <Generic ISA VGA> at port 0x3d0-0x3db iomem 0xb8000-0xbffff on isa0
> wbwd0: HEFRAS and EFER do not align: EFER 0x2e DevID 0xff DevRev 0xff CR26 0xff
> coretemp0: <CPU On-Die Thermal Sensors> on cpu0
> est0: <Enhanced SpeedStep Frequency Control> on cpu0
> coretemp1: <CPU On-Die Thermal Sensors> on cpu1
> est1: <Enhanced SpeedStep Frequency Control> on cpu1
> coretemp2: <CPU On-Die Thermal Sensors> on cpu2
> est2: <Enhanced SpeedStep Frequency Control> on cpu2
> coretemp3: <CPU On-Die Thermal Sensors> on cpu3
> est3: <Enhanced SpeedStep Frequency Control> on cpu3
> coretemp4: <CPU On-Die Thermal Sensors> on cpu4
> est4: <Enhanced SpeedStep Frequency Control> on cpu4
> coretemp5: <CPU On-Die Thermal Sensors> on cpu5
> est5: <Enhanced SpeedStep Frequency Control> on cpu5
> coretemp6: <CPU On-Die Thermal Sensors> on cpu6
> est6: <Enhanced SpeedStep Frequency Control> on cpu6
> coretemp7: <CPU On-Die Thermal Sensors> on cpu7
> est7: <Enhanced SpeedStep Frequency Control> on cpu7
> ZFS filesystem version: 5
> ZFS storage pool version: features support (5000)
> Timecounters tick every 1.000 msec
> ipfw2 (+ipv6) initialized, divert enabled, nat enabled, default to accept, logging disabled
> usbus0: 480Mbps High Speed USB v2.0
> usbus1: 480Mbps High Speed USB v2.0
> ugen0.1: <Intel> at usbus0
> uhub0: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus0
> ugen1.1: <Intel> at usbus1
> uhub1: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus1
> uhub0: 2 ports with 2 removable, self powered
> uhub1: 2 ports with 2 removable, self powered
> ugen0.2: <vendor 0x8087> at usbus0
> uhub2: <vendor 0x8087 product 0x8008, class 9/0, rev 2.00/0.05, addr 2> on usbus0
> ugen1.2: <vendor 0x8087> at usbus1
> uhub3: <vendor 0x8087 product 0x8000, class 9/0, rev 2.00/0.05, addr 2> on usbus1
> uhub2: 4 ports with 4 removable, self powered
> uhub3: 6 ports with 6 removable, self powered
> ugen1.3: <vendor 0x0000> at usbus1
> uhub4: <vendor 0x0000 product 0x0001, class 9/0, rev 2.00/0.00, addr 3> on usbus1
> uhub4: 4 ports with 3 removable, self powered
> ugen1.4: <vendor 0x0557> at usbus1
> ukbd0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 4> on usbus1
> ums0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 4> on usbus1
> ums0: 3 buttons and [Z] coordinates ID=0
> ugen0.3: <SanDisk> at usbus0
> umass0: <SanDisk Cruzer Fit, class 0/0, rev 2.00/1.27, addr 3> on usbus0
> umass0: SCSI over Bulk-Only; quirks = 0x8100
> umass0:7:0:-1: Attached to scbus7
> ugen1.5: <SIGMACHIP> at usbus1
> ukbd1: <SIGMACHIP USB Keyboard, class 0/0, rev 1.10/1.10, addr 5> on usbus1
> kbd2 at ukbd1
> uhid0: <SIGMACHIP USB Keyboard, class 0/0, rev 1.10/1.10, addr 5> on usbus1
> ugen0.4: <SanDisk> at usbus0
> umass1: <SanDisk Cruzer Fit, class 0/0, rev 2.00/1.27, addr 4> on usbus0
> umass1: SCSI over Bulk-Only; quirks = 0x8100
> umass1:8:1:-1: Attached to scbus8
> ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
> ada0: <WDC WD30EFRX-68EUZN0 82.00A82> ATA-9da0 at umass-sim0 bus 0 scbus7 target 0 lun 0
> da0: <SanDisk Cruzer Fit 1.27> Removable Direct Access SCSI-6 device
> da0: Serial Number 4C530301260110111034
> da0: 40.000MB/s transfers
> da0: 15267MB (31266816 512 byte sectors: 255H 63S/T 1946C)
> da0: quirks=0x2<NO_6_BYTE>
> da1 at umass-sim1 bus 1 scbus8 target 0 lun 0
> da1: <SanDisk Cruzer Fit 1.27> Removable Direct Access SCSI-6 device
> da1: Serial Number 4C530008060110121231
> da1: 40.000MB/s transfers
> da1: 15267MB (31266816 512 byte sectors: 255H 63S/T 1946C)
> da1: quirks=0x2<NO_6_BYTE>
> SATA 3.x device
> ada0: Serial Number WD-WCC4NJANZTZ8
> ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
> ada0: Command Queueing enabled
> ada0: 2861588MB (5860533168 512 byte sectors: 16H 63S/T 16383C)
> ada0: quirks=0x1<4K>
> ada0: Previously was known as ad4
> ada1 at ahcich1 bus 0 scbus1 target 0 lun 0
> ada1: <WDC WD30EFRX-68EUZN0 82.00A82> ATA-9 SATA 3.x device
> ada1: Serial Number WD-WCC4NDZPHV7N
> ada1: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
> ada1: Command Queueing enabled
> ada1: 2861588MB (5860533168 512 byte sectors: 16H 63S/T 16383C)
> ada1: quirks=0x1<4K>
> ada1: Previously was known as ad6
> ada2 at ahcich2 bus 0 scbus2 target 0 lun 0
> ada2: <WDC WD30EFRX-68EUZN0 82.00A82> ATA-9 SATA 3.x device
> ada2: Serial Number WD-WMC4N0F3P1YZ
> ada2: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
> ada2: Command Queueing enabled
> ada2: 2861588MB (5860533168 512 byte sectors: 16H 63S/T 16383C)
> ada2: quirks=0x1<4K>
> ada2: Previously was known as ad8
> ada3 at ahcich3 bus 0 scbus3 target 0 lun 0
> ada3: <WDC WD30EFRX-68EUZN0 82.00A82> ATA-9 SATA 3.x device
> ada3: Serial Number WD-WCC4NEAUV8ND
> ada3: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
> ada3: Command Queueing enabled
> ada3: 2861588MB (5860533168 512 byte sectors: 16H 63S/T 16383C)
> ada3: quirks=0x1<4K>
> ada3: Previously was known as ad10
> ada4 at ahcich4 bus 0 scbus4 target 0 lun 0
> ada4: <WDC WD30EFRX-68EUZN0 82.00A82> ATA-9 SATA 3.x device
> ada4: Serial Number WD-WMC4N0F3APUY
> ada4: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
> ada4: Command Queueing enabled
> ada4: 2861588MB (5860533168 512 byte sectors: 16H 63S/T 16383C)
> ada4: quirks=0x1<4K>
> ada4: Previously was known as ad12
> ada5 at ahcich5 bus 0 scbus5 target 0 lun 0
> ada5: <WDC WD30EFRX-68EUZN0 82.00A82> ATA-9 SATA 3.x device
> ada5: Serial Number WD-WMC4N0F95M77
> ada5: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
> ada5: Command Queueing enabled
> ada5: 2861588MB (5860533168 512 byte sectors: 16H 63S/T 16383C)
> ada5: quirks=0x1<4K>
> ada5: Previously was known as ad14
> SMP: AP CPU #1 Launched!
> SMP: AP CPU #5 Launched!
> SMP: AP CPU #3 Launched!
> SMP: AP CPU #7 Launched!
> SMP: AP CPU #4 Launched!
> SMP: AP CPU #2 Launched!
> SMP: AP CPU #6 Launched!
> Timecounter "TSC-low" frequency 1650035138 Hz quality 1000
> Trying to mount root from zfs:freenas-boot/ROOT/FreeNAS-9.3-STABLE-201504152200 []...
> GEOM_RAID5: Module loaded, version 1.3.20140711.62 (rev f91e28e40bf7)
> ipmi0: <IPMI System Interface> port 0xca2,0xca3 on acpi0
> ipmi0: KCS mode found at io 0xca2 on acpi
> ipmi0: IPMI device rev. 1, firmware rev. 1.35, version 2.0
> ipmi0: Number of channels 2
> ipmi0: Attached watchdog
> ipmi1: <IPMI System Interface> on isa0
> device_attach: ipmi1 attach returned 16
> wbwd0: HEFRAS and EFER do not align: EFER 0x2e DevID 0xff DevRev 0xff CR26 0xff
> GEOM_ELI: Device ada0p1.eli created.
> GEOM_ELI: Encryption: AES-XTS 256
> GEOM_ELI: Crypto: hardware
> GEOM_ELI: Device ada1p1.eli created.
> GEOM_ELI: Encryption: AES-XTS 256
> GEOM_ELI: Crypto: hardware
> GEOM_ELI: Device ada2p1.eli created.
> GEOM_ELI: Encryption: AES-XTS 256
> GEOM_ELI: Crypto: hardware
> GEOM_ELI: Device ada3p1.eli created.
> GEOM_ELI: Encryption: AES-XTS 256
> GEOM_ELI: Crypto: hardware
> GEOM_ELI: Device ada4p1.eli created.
> GEOM_ELI: Encryption: AES-XTS 256
> GEOM_ELI: Crypto: hardware
> GEOM_ELI: Device ada5p1.eli created.
> GEOM_ELI: Encryption: AES-XTS 256
> GEOM_ELI: Crypto: hardware
> vboxdrv: fAsync=0 offMin=0x2c1 offMax=0xf90
> bridge0: Ethernet address: 02:86:66:b2:04:00
> bridge0: link state changed to UP
> igb0: promiscuous mode enabled
> epair0a: Ethernet address: 02:04:eb:00:08:0a
> epair0b: Ethernet address: 02:04:eb:00:09:0b
> epair0a: link state changed to UP
> epair0b: link state changed to UP
> igb0: link state changed to DOWN
> epair0a: promiscuous mode enabled
> ng_ether_ifnet_arrival_event: can't re-name node epair0b
> epair1a: Ethernet address: 02:63:68:00:09:0a
> epair1b: Ethernet address: 02:63:68:00:0a:0b
> epair1a: link state changed to UP
> epair1b: link state changed to UP
> epair1a: promiscuous mode enabled
> ng_ether_ifnet_arrival_event: can't re-name node epair1b
> linux: pid 4757 (java): syscall inotify_init not implemented
> linux: pid 5672 (java): syscall inotify_init not implemented
> igb0: link state changed to UP
> pid 1873 (syslog-ng), uid 0: exited on signal 6 (core dumped)
> arp: 192.168.1.11 moved from 02:63:68:00:09:0a to 00:25:90:47:79:de on epair1b
> arp: 192.168.1.11 moved from 02:04:eb:00:08:0a to 00:25:90:47:79:de on epair0b

-- End of security output --

I will do a search on how to do a Smart Test...
 

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,504
OK, the first is a normal update notification--the system will notify you daily about available updates. The second is normal when you reboot the system (which is, or at least has been, necessary when you update).

Setting up SMART tests is discussed in the manual at http://doc.freenas.org/9.3/freenas_tasks.html#s-m-a-r-t-tests.
 
Status
Not open for further replies.
Top