Server becomes unresponsive

Status
Not open for further replies.

Mochaka

Dabbler
Joined
Mar 23, 2013
Messages
10
My server will randomly become unresponsive. Can't ping it or anything and if i plug a screen into it, it doesn't get a signal. So i have to hold the power button down and restart it the hard way. Then it boots and everything is okay. Then it can last a few days or it can last seconds and then become unresponsive again.

Here is the log file i got before it died last time.

Code:
Mar 24 11:20:39 nas newsyslog[2079]: logfile first created
Mar 24 11:20:39 nas syslogd: kernel boot file is /boot/kernel/kernel
Mar 24 11:20:39 nas kernel: Copyright (c) 1992-2012 The FreeBSD Project.
Mar 24 11:20:39 nas kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
Mar 24 11:20:39 nas kernel: The Regents of the University of California. All rights reserved.
Mar 24 11:20:39 nas kernel: FreeBSD is a registered trademark of The FreeBSD Foundation.
Mar 24 11:20:39 nas kernel: FreeBSD 8.3-RELEASE-p4 #0 r241984M: Wed Oct 24 00:57:10 PDT 2012
Mar 24 11:20:39 nas kernel: root@build.ixsystems.com:/usr/home/jpaetzel/8.3.0-RELEASE/os-base/amd64/usr/home/jpaetzel/8.3.0-RELEASE/FreeBSD/src/sys/FREENAS.amd64 amd64
Mar 24 11:20:39 nas kernel: Timecounter "i8254" frequency 1193182 Hz quality 0
Mar 24 11:20:39 nas kernel: CPU: Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz (2400.10-MHz K8-class CPU)
Mar 24 11:20:39 nas kernel: Origin = "GenuineIntel"  Id = 0x6fb  Family = 6  Model = f  Stepping = 11
Mar 24 11:20:39 nas kernel: 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>
Mar 24 11:20:39 nas kernel: Features2=0xe3bd<SSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM>
Mar 24 11:20:39 nas kernel: AMD Features=0x20100800<SYSCALL,NX,LM>
Mar 24 11:20:39 nas kernel: AMD Features2=0x1<LAHF>
Mar 24 11:20:39 nas kernel: TSC: P-state invariant
Mar 24 11:20:39 nas kernel: real memory  = 15032385536 (14336 MB)
Mar 24 11:20:39 nas kernel: avail memory = 14474039296 (13803 MB)
Mar 24 11:20:39 nas kernel: ACPI APIC Table: <GBT    GBTUACPI>
Mar 24 11:20:39 nas kernel: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
Mar 24 11:20:39 nas kernel: FreeBSD/SMP: 1 package(s) x 4 core(s)
Mar 24 11:20:39 nas kernel: cpu0 (BSP): APIC ID:  0
Mar 24 11:20:39 nas kernel: cpu1 (AP): APIC ID:  1
Mar 24 11:20:39 nas kernel: cpu2 (AP): APIC ID:  2
Mar 24 11:20:39 nas kernel: cpu3 (AP): APIC ID:  3
Mar 24 11:20:39 nas kernel: WARNING: VIMAGE (virtualized network stack) is a highly experimental feature.
Mar 24 11:20:39 nas kernel: ioapic0: Changing APIC ID to 2
Mar 24 11:20:39 nas kernel: ioapic0 <Version 2.0> irqs 0-23 on motherboard
Mar 24 11:20:39 nas kernel: kbd1 at kbdmux0
Mar 24 11:20:39 nas kernel: hpt27xx: RocketRAID 27xx controller driver v1.0 (Oct 24 2012 00:56:59)
Mar 24 11:20:39 nas kernel: cryptosoft0: <software crypto> on motherboard
Mar 24 11:20:39 nas kernel: aesni0: No AESNI support.
Mar 24 11:20:39 nas kernel: acpi0: <GBT GBTUACPI> on motherboard
Mar 24 11:20:39 nas kernel: acpi0: [ITHREAD]
Mar 24 11:20:39 nas kernel: acpi0: Power Button (fixed)
Mar 24 11:20:39 nas kernel: acpi0: reservation of 0, a0000 (3) failed
Mar 24 11:20:39 nas kernel: acpi0: reservation of 100000, efde0000 (3) failed
Mar 24 11:20:39 nas kernel: Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
Mar 24 11:20:39 nas kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0
Mar 24 11:20:39 nas kernel: cpu0: <ACPI CPU> on acpi0
Mar 24 11:20:39 nas kernel: ACPI Warning: Incorrect checksum in table [TAMG] - 0x6C, should be 0x6B (20101013/tbutils-354)
Mar 24 11:20:39 nas kernel: cpu1: <ACPI CPU> on acpi0
Mar 24 11:20:39 nas kernel: cpu2: <ACPI CPU> on acpi0
Mar 24 11:20:39 nas kernel: cpu3: <ACPI CPU> on acpi0
Mar 24 11:20:39 nas kernel: acpi_button0: <Power Button> on acpi0
Mar 24 11:20:39 nas kernel: pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
Mar 24 11:20:39 nas kernel: pci0: <ACPI PCI bus> on pcib0
Mar 24 11:20:39 nas kernel: pcib1: <PCI-PCI bridge> irq 16 at device 1.0 on pci0
Mar 24 11:20:39 nas kernel: pci1: <PCI bus> on pcib1
Mar 24 11:20:39 nas kernel: vgapci0: <VGA-compatible display> port 0xee00-0xeeff mem 0xf0000000-0xf7ffffff,0xfdcf0000-0xfdcfffff irq 16 at device 0.0 on pci1
Mar 24 11:20:39 nas kernel: vgapci1: <VGA-compatible display> mem 0xfdce0000-0xfdceffff at device 0.1 on pci1
Mar 24 11:20:39 nas kernel: uhci0: <Intel 82801JI (ICH10) USB controller USB-D> port 0xff00-0xff1f irq 16 at device 26.0 on pci0
Mar 24 11:20:39 nas kernel: uhci0: [ITHREAD]
Mar 24 11:20:39 nas kernel: usbus0: <Intel 82801JI (ICH10) USB controller USB-D> on uhci0
Mar 24 11:20:39 nas kernel: uhci1: <Intel 82801JI (ICH10) USB controller USB-E> port 0xfe00-0xfe1f irq 21 at device 26.1 on pci0
Mar 24 11:20:39 nas kernel: uhci1: [ITHREAD]
Mar 24 11:20:39 nas kernel: usbus1: <Intel 82801JI (ICH10) USB controller USB-E> on uhci1
Mar 24 11:20:39 nas kernel: uhci2: <Intel 82801JI (ICH10) USB controller USB-F> port 0xfd00-0xfd1f irq 18 at device 26.2 on pci0
Mar 24 11:20:39 nas kernel: uhci2: [ITHREAD]
Mar 24 11:20:39 nas kernel: usbus2: <Intel 82801JI (ICH10) USB controller USB-F> on uhci2
Mar 24 11:20:39 nas kernel: ehci0: <Intel 82801JI (ICH10) USB 2.0 controller USB-B> mem 0xfdfff000-0xfdfff3ff irq 18 at device 26.7 on pci0
Mar 24 11:20:39 nas kernel: ehci0: [ITHREAD]
Mar 24 11:20:39 nas kernel: usbus3: EHCI version 1.0
Mar 24 11:20:39 nas kernel: usbus3: <Intel 82801JI (ICH10) USB 2.0 controller USB-B> on ehci0
Mar 24 11:20:39 nas kernel: pci0: <multimedia, HDA> at device 27.0 (no driver attached)
Mar 24 11:20:39 nas kernel: pcib2: <ACPI PCI-PCI bridge> irq 16 at device 28.0 on pci0
Mar 24 11:20:39 nas kernel: pci2: <ACPI PCI bus> on pcib2
Mar 24 11:20:39 nas kernel: pcib3: <ACPI PCI-PCI bridge> irq 16 at device 28.4 on pci0
Mar 24 11:20:39 nas kernel: pci3: <ACPI PCI bus> on pcib3
Mar 24 11:20:39 nas kernel: atapci0: <JMicron JMB368 UDMA133 controller> port 0xdf00-0xdf07,0xde00-0xde03,0xdd00-0xdd07,0xdc00-0xdc03,0xdb00-0xdb0f irq 16 at device 0.0 on pci3
Mar 24 11:20:39 nas kernel: atapci0: [ITHREAD]
Mar 24 11:20:39 nas kernel: ata2: <ATA channel> at channel 0 on atapci0
Mar 24 11:20:39 nas kernel: ata2: [ITHREAD]
Mar 24 11:20:39 nas kernel: pcib4: <ACPI PCI-PCI bridge> irq 17 at device 28.5 on pci0
Mar 24 11:20:39 nas kernel: pci4: <ACPI PCI bus> on pcib4
Mar 24 11:20:39 nas kernel: re0: <RealTek 8168/8111 B/C/CP/D/DP/E/F PCIe Gigabit Ethernet> port 0xce00-0xceff mem 0xfddff000-0xfddfffff,0xfdde0000-0xfddeffff irq 17 at device 0.0 on pci4
Mar 24 11:20:39 nas kernel: re0: Using 1 MSI-X message
Mar 24 11:20:39 nas kernel: re0: Chip rev. 0x3c000000
Mar 24 11:20:39 nas kernel: re0: MAC rev. 0x00400000
Mar 24 11:20:39 nas kernel: miibus0: <MII bus> on re0
Mar 24 11:20:39 nas kernel: rgephy0: <RTL8169S/8110S/8211B media interface> PHY 1 on miibus0
Mar 24 11:20:39 nas kernel: rgephy0:  none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow
Mar 24 11:20:39 nas kernel: re0: Ethernet address: 6c:f0:49:0d:23:9b
Mar 24 11:20:39 nas kernel: re0: [ITHREAD]
Mar 24 11:20:39 nas kernel: uhci3: <Intel 82801JI (ICH10) USB controller USB-A> port 0xfc00-0xfc1f irq 23 at device 29.0 on pci0
Mar 24 11:20:39 nas kernel: uhci3: [ITHREAD]
Mar 24 11:20:39 nas kernel: usbus4: <Intel 82801JI (ICH10) USB controller USB-A> on uhci3
Mar 24 11:20:39 nas kernel: uhci4: <Intel 82801JI (ICH10) USB controller USB-B> port 0xfb00-0xfb1f irq 19 at device 29.1 on pci0
Mar 24 11:20:39 nas kernel: uhci4: [ITHREAD]
Mar 24 11:20:39 nas kernel: usbus5: <Intel 82801JI (ICH10) USB controller USB-B> on uhci4
Mar 24 11:20:39 nas kernel: uhci5: <Intel 82801JI (ICH10) USB controller USB-C> port 0xfa00-0xfa1f irq 18 at device 29.2 on pci0
Mar 24 11:20:39 nas kernel: uhci5: [ITHREAD]
Mar 24 11:20:39 nas kernel: usbus6: <Intel 82801JI (ICH10) USB controller USB-C> on uhci5
Mar 24 11:20:39 nas kernel: ehci1: <Intel 82801JI (ICH10) USB 2.0 controller USB-A> mem 0xfdffe000-0xfdffe3ff irq 23 at device 29.7 on pci0
Mar 24 11:20:39 nas kernel: ehci1: [ITHREAD]
Mar 24 11:20:39 nas kernel: usbus7: EHCI version 1.0
Mar 24 11:20:39 nas kernel: usbus7: <Intel 82801JI (ICH10) USB 2.0 controller USB-A> on ehci1
Mar 24 11:20:39 nas kernel: pcib5: <ACPI PCI-PCI bridge> at device 30.0 on pci0
Mar 24 11:20:39 nas kernel: pci5: <ACPI PCI bus> on pcib5
Mar 24 11:20:39 nas kernel: isab0: <PCI-ISA bridge> at device 31.0 on pci0
Mar 24 11:20:39 nas kernel: isa0: <ISA bus> on isab0
Mar 24 11:20:39 nas kernel: atapci1: <Intel ICH10 SATA300 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf900-0xf90f,0xf800-0xf80f at device 31.2 on pci0
Mar 24 11:20:39 nas kernel: ata0: <ATA channel> at channel 0 on atapci1
Mar 24 11:20:39 nas kernel: ata0: [ITHREAD]
Mar 24 11:20:39 nas kernel: ata1: <ATA channel> at channel 1 on atapci1
Mar 24 11:20:39 nas kernel: ata1: [ITHREAD]
Mar 24 11:20:39 nas kernel: pci0: <serial bus, SMBus> at device 31.3 (no driver attached)
Mar 24 11:20:39 nas kernel: atapci2: <Intel ICH10 SATA300 controller> port 0xf600-0xf607,0xf500-0xf503,0xf400-0xf407,0xf300-0xf303,0xf200-0xf20f,0xf100-0xf10f irq 19 at device 31.5 on pci0
Mar 24 11:20:39 nas kernel: atapci2: [ITHREAD]
Mar 24 11:20:39 nas kernel: ata3: <ATA channel> at channel 0 on atapci2
Mar 24 11:20:39 nas kernel: ata3: [ITHREAD]
Mar 24 11:20:39 nas kernel: ata4: <ATA channel> at channel 1 on atapci2
Mar 24 11:20:39 nas kernel: ata4: [ITHREAD]
Mar 24 11:20:39 nas kernel: acpi_hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff irq 0,8 on acpi0
Mar 24 11:20:39 nas kernel: Timecounter "HPET" frequency 14318180 Hz quality 900
Mar 24 11:20:39 nas kernel: atrtc0: <AT realtime clock> port 0x70-0x73 on acpi0
Mar 24 11:20:39 nas kernel: fdc0: <floppy drive controller> port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0
Mar 24 11:20:39 nas kernel: fdc0: [FILTER]
Mar 24 11:20:39 nas kernel: uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
Mar 24 11:20:39 nas kernel: uart0: [FILTER]
Mar 24 11:20:39 nas kernel: ppc0: <Parallel port> port 0x378-0x37f irq 7 on acpi0
Mar 24 11:20:39 nas kernel: ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
Mar 24 11:20:39 nas kernel: ppc0: [ITHREAD]
Mar 24 11:20:39 nas kernel: ppbus0: <Parallel port bus> on ppc0
Mar 24 11:20:39 nas kernel: lpt0: <Printer> on ppbus0
Mar 24 11:20:39 nas kernel: lpt0: [ITHREAD]
Mar 24 11:20:39 nas kernel: lpt0: Interrupt-driven port
Mar 24 11:20:39 nas kernel: orm0: <ISA Option ROM> at iomem 0xc0000-0xccfff on isa0
Mar 24 11:20:39 nas kernel: sc0: <System console> at flags 0x100 on isa0
Mar 24 11:20:39 nas kernel: sc0: VGA <16 virtual consoles, flags=0x300>
Mar 24 11:20:39 nas kernel: vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
Mar 24 11:20:39 nas kernel: atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
Mar 24 11:20:39 nas kernel: atkbd0: <AT Keyboard> irq 1 on atkbdc0
Mar 24 11:20:39 nas kernel: kbd0 at atkbd0
Mar 24 11:20:39 nas kernel: atkbd0: [GIANT-LOCKED]
Mar 24 11:20:39 nas kernel: atkbd0: [ITHREAD]
Mar 24 11:20:39 nas kernel: acpi_perf0: <ACPI CPU Frequency Control> on cpu0
Mar 24 11:20:39 nas kernel: coretemp0: <CPU On-Die Thermal Sensors> on cpu0
Mar 24 11:20:39 nas kernel: p4tcc0: <CPU Frequency Thermal Control> on cpu0
Mar 24 11:20:39 nas kernel: coretemp1: <CPU On-Die Thermal Sensors> on cpu1
Mar 24 11:20:39 nas kernel: est1: <Enhanced SpeedStep Frequency Control> on cpu1
Mar 24 11:20:39 nas kernel: est: CPU supports Enhanced Speedstep, but is not recognized.
Mar 24 11:20:39 nas kernel: est: cpu_vendor GenuineIntel, msr 926092606000926
Mar 24 11:20:39 nas kernel: device_attach: est1 attach returned 6
Mar 24 11:20:39 nas kernel: p4tcc1: <CPU Frequency Thermal Control> on cpu1
Mar 24 11:20:39 nas kernel: coretemp2: <CPU On-Die Thermal Sensors> on cpu2
Mar 24 11:20:39 nas kernel: est2: <Enhanced SpeedStep Frequency Control> on cpu2
Mar 24 11:20:39 nas kernel: est: CPU supports Enhanced Speedstep, but is not recognized.
Mar 24 11:20:39 nas kernel: est: cpu_vendor GenuineIntel, msr 926092606000926
Mar 24 11:20:39 nas kernel: device_attach: est2 attach returned 6
Mar 24 11:20:39 nas kernel: p4tcc2: <CPU Frequency Thermal Control> on cpu2
Mar 24 11:20:39 nas kernel: coretemp3: <CPU On-Die Thermal Sensors> on cpu3
Mar 24 11:20:39 nas kernel: est3: <Enhanced SpeedStep Frequency Control> on cpu3
Mar 24 11:20:39 nas kernel: est: CPU supports Enhanced Speedstep, but is not recognized.
Mar 24 11:20:39 nas kernel: est: cpu_vendor GenuineIntel, msr 926092606000926
Mar 24 11:20:39 nas kernel: device_attach: est3 attach returned 6
Mar 24 11:20:39 nas kernel: p4tcc3: <CPU Frequency Thermal Control> on cpu3
Mar 24 11:20:39 nas kernel: fuse4bsd: version 0.3.9-pre1, FUSE ABI 7.8
Mar 24 11:20:39 nas kernel: Timecounters tick every 1.000 msec
Mar 24 11:20:39 nas kernel: hpt27xx: no controller detected.
Mar 24 11:20:39 nas kernel: usbus0: 12Mbps Full Speed USB v1.0
Mar 24 11:20:39 nas kernel: usbus1: 12Mbps Full Speed USB v1.0
Mar 24 11:20:39 nas kernel: usbus2: 12Mbps Full Speed USB v1.0
Mar 24 11:20:39 nas kernel: usbus3: 480Mbps High Speed USB v2.0
Mar 24 11:20:39 nas kernel: usbus4: 12Mbps Full Speed USB v1.0
Mar 24 11:20:39 nas kernel: usbus5: 12Mbps Full Speed USB v1.0
Mar 24 11:20:39 nas kernel: usbus6: 12Mbps Full Speed USB v1.0
Mar 24 11:20:39 nas kernel: usbus7: 480Mbps High Speed USB v2.0
Mar 24 11:20:39 nas kernel: ugen0.1: <Intel> at usbus0
Mar 24 11:20:39 nas kernel: uhub0: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0
Mar 24 11:20:39 nas kernel: ugen1.1: <Intel> at usbus1
Mar 24 11:20:39 nas kernel: uhub1: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus1
Mar 24 11:20:39 nas kernel: ugen2.1: <Intel> at usbus2
Mar 24 11:20:39 nas kernel: uhub2: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus2
Mar 24 11:20:39 nas kernel: ugen3.1: <Intel> at usbus3
Mar 24 11:20:39 nas kernel: uhub3: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus3
Mar 24 11:20:39 nas kernel: ugen4.1: <Intel> at usbus4
Mar 24 11:20:39 nas kernel: uhub4: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus4
Mar 24 11:20:39 nas kernel: ugen5.1: <Intel> at usbus5
Mar 24 11:20:39 nas kernel: uhub5: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus5
Mar 24 11:20:39 nas kernel: ugen6.1: <Intel> at usbus6
Mar 24 11:20:39 nas kernel: uhub6: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus6
Mar 24 11:20:39 nas kernel: ugen7.1: <Intel> at usbus7
Mar 24 11:20:39 nas kernel: uhub7: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus7
Mar 24 11:20:39 nas kernel: uhub0: 2 ports with 2 removable, self powered
Mar 24 11:20:39 nas kernel: uhub1: 2 ports with 2 removable, self powered
Mar 24 11:20:39 nas kernel: uhub2: 2 ports with 2 removable, self powered
Mar 24 11:20:39 nas kernel: uhub4: 2 ports with 2 removable, self powered
Mar 24 11:20:39 nas kernel: uhub5: 2 ports with 2 removable, self powered
Mar 24 11:20:39 nas kernel: uhub6: 2 ports with 2 removable, self powered
Mar 24 11:20:39 nas kernel: uhub3: 6 ports with 6 removable, self powered
Mar 24 11:20:39 nas kernel: uhub7: 6 ports with 6 removable, self powered
Mar 24 11:20:39 nas kernel: ugen3.2: <SanDisk> at usbus3
Mar 24 11:20:39 nas kernel: umass0: <SanDisk Cruzer Edge, class 0/0, rev 2.00/1.26, addr 2> on usbus3
Mar 24 11:20:39 nas kernel: ada0 at ata0 bus 0 scbus1 target 1 lun 0
Mar 24 11:20:39 nas kernel: ada0: <WDC WD15EARS-00Z5B1 80.00A80> ATA-8 SATA 2.x device
Mar 24 11:20:39 nas kernel: ada0: 300.000MB/s transfers (SATA 2.x, UDMA5, PIO 8192bytes)
Mar 24 11:20:39 nas kernel: ada0: 1430799MB (2930277168 512 byte sectors: 16H 63S/T 16383C)
Mar 24 11:20:39 nas kernel: ada1 at ata1 bus 0 scbus2 target 0 lun 0
Mar 24 11:20:39 nas kernel: ada1: <WDC WD20EARX-00PASB0 51.0AB51> ATA-8 SATA 3.x device
Mar 24 11:20:39 nas kernel: ada1: 300.000MB/s transfers (SATA 2.x, UDMA5, PIO 8192bytes)
Mar 24 11:20:39 nas kernel: ada1: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
Mar 24 11:20:39 nas kernel: ada2 at ata1 bus 0 scbus2 target 1 lun 0
Mar 24 11:20:39 nas kernel: ada2: <WDC WD20EARS-67S8B1 80.00A80> ATA-8 SATA 2.x device
Mar 24 11:20:39 nas kernel: ada2: 300.000MB/s transfers (SATA 2.x, UDMA5, PIO 8192bytes)
Mar 24 11:20:39 nas kernel: ada2: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
Mar 24 11:20:39 nas kernel: ada3 at ata3 bus 0 scbus3 target 0 lun 0
Mar 24 11:20:39 nas kernel: ada3: <WDC WD15EARS-00MVWB0 51.0AB51> ATA-8 SATA 2.x device
Mar 24 11:20:39 nas kernel: ada3: 300.000MB/s transfers (SATA 2.x, UDMA5, PIO 8192bytes)
Mar 24 11:20:39 nas kernel: ada3: 1430799MB (2930277168 512 byte sectors: 16H 63S/T 16383C)
Mar 24 11:20:39 nas kernel: ada4 at ata4 bus 0 scbus4 target 0 lun 0
Mar 24 11:20:39 nas kernel: ada4: <WDC WD20EARS-00MVWB0 51.0AB51> ATA-8 SATA 2.x device
Mar 24 11:20:39 nas kernel: ada4: 300.000MB/s transfers (SATA 2.x, UDMA5, PIO 8192bytes)
Mar 24 11:20:39 nas kernel: ada4: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
Mar 24 11:20:39 nas kernel: da0 at umass-sim0 bus 0 scbus5 target 0 lun 0
Mar 24 11:20:39 nas kernel: da0: <SanDisk Cruzer Edge 1.26> Removable Direct Access SCSI-5 device 
Mar 24 11:20:39 nas kernel: da0: 40.000MB/s transfers
Mar 24 11:20:39 nas kernel: da0: 3819MB (7821312 512 byte sectors: 255H 63S/T 486C)
Mar 24 11:20:39 nas kernel: SMP: AP CPU #2 Launched!
Mar 24 11:20:39 nas kernel: SMP: AP CPU #1 Launched!
Mar 24 11:20:39 nas kernel: SMP: AP CPU #3 Launched!
Mar 24 11:20:39 nas kernel: GEOM: ada0: the secondary GPT header is not in the last LBA.
Mar 24 11:20:39 nas kernel: GEOM: ada1: the secondary GPT header is not in the last LBA.
Mar 24 11:20:39 nas kernel: GEOM: ada2: the secondary GPT header is not in the last LBA.
Mar 24 11:20:39 nas kernel: GEOM: ada3: the secondary GPT header is not in the last LBA.
Mar 24 11:20:39 nas kernel: GEOM: ada4: the secondary GPT header is not in the last LBA.
Mar 24 11:20:39 nas kernel: GEOM: da0s1: geometry does not match label (16h,63s != 255h,63s).
Mar 24 11:20:39 nas kernel: Trying to mount root from ufs:/dev/ufs/FreeNASs1a
Mar 24 11:20:39 nas kernel: WARNING: /data was not properly dismounted
Mar 24 11:20:39 nas kernel: ZFS filesystem version 5
Mar 24 11:20:39 nas kernel: ZFS storage pool version 28
Mar 24 11:20:39 nas root: /etc/rc: WARNING: Dump device does not exist.  Savecore not run.
Mar 24 11:20:40 nas mountd[2145]: can't get address info for host anon=nfs
Mar 24 11:20:40 nas mountd[2145]: bad host anon=nfs, skipping
Mar 24 11:20:41 nas mountd[2145]: can't get address info for host rw=*
Mar 24 11:20:41 nas mountd[2145]: bad host rw=*, skipping
Mar 24 11:20:41 nas mountd[2145]: bad exports list line /mnt/storage/Backup	anon=nfs rw=*
Mar 24 11:20:41 nas mountd[2145]: can't get address info for host anon=nfs
Mar 24 11:20:41 nas mountd[2145]: bad host anon=nfs, skipping
Mar 24 11:20:41 nas mountd[2145]: bad sec flavor: none
Mar 24 11:20:41 nas mountd[2145]: bad exports list line /mnt/storage/Games	anon=nfs -sec
Mar 24 11:20:42 nas mountd[2145]: can't get address info for host anon=nfs
Mar 24 11:20:42 nas mountd[2145]: bad host anon=nfs, skipping
Mar 24 11:20:43 nas mountd[2145]: can't get address info for host rw=*
Mar 24 11:20:43 nas mountd[2145]: bad host rw=*, skipping
Mar 24 11:20:43 nas mountd[2145]: bad exports list line /mnt/storage/Movies	anon=nfs rw=*
Mar 24 11:20:44 nas mountd[2145]: can't get address info for host anon=nfs
Mar 24 11:20:44 nas mountd[2145]: bad host anon=nfs, skipping
Mar 24 11:20:44 nas mountd[2145]: bad sec flavor: none
Mar 24 11:20:44 nas mountd[2145]: bad exports list line /mnt/storage/TV	anon=nfs -sec
Mar 24 11:20:44 nas root: /etc/rc: WARNING: failed precmd routine for vmware_guestd
Mar 24 11:20:44 nas ntpd[2428]: ntpd 4.2.4p5-a (1)
Mar 24 11:20:48 nas smartd[2671]: Device: /dev/ada0, 1430 Currently unreadable (pending) sectors
Mar 24 11:20:48 nas smartd[2671]: Device: /dev/ada2, 1351 Currently unreadable (pending) sectors
Mar 24 11:20:48 nas smartd[2671]: Device: /dev/ada2, 2 Offline uncorrectable sectors
Mar 24 11:20:56 nas ntpd[2429]: time reset -0.188624 s
Mar 24 11:21:01 nas avahi-daemon[2876]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Mar 24 11:21:06 nas mountd[2146]: can't get address info for host anon=nfs
Mar 24 11:21:06 nas mountd[2146]: bad host anon=nfs, skipping
Mar 24 11:21:07 nas mountd[2146]: can't get address info for host rw=*
Mar 24 11:21:07 nas mountd[2146]: bad host rw=*, skipping
Mar 24 11:21:07 nas mountd[2146]: bad exports list line /mnt/storage/Backup	anon=nfs rw=*
Mar 24 11:21:08 nas mountd[2146]: can't get address info for host anon=nfs
Mar 24 11:21:08 nas mountd[2146]: bad host anon=nfs, skipping
Mar 24 11:21:08 nas mountd[2146]: bad sec flavor: none
Mar 24 11:21:08 nas mountd[2146]: bad exports list line /mnt/storage/Games	anon=nfs -sec
Mar 24 11:21:08 nas mountd[2146]: can't get address info for host anon=nfs
Mar 24 11:21:08 nas mountd[2146]: bad host anon=nfs, skipping
Mar 24 11:21:09 nas mountd[2146]: can't get address info for host rw=*
Mar 24 11:21:09 nas mountd[2146]: bad host rw=*, skipping
Mar 24 11:21:09 nas mountd[2146]: bad exports list line /mnt/storage/Movies	anon=nfs rw=*
Mar 24 11:21:10 nas mountd[2146]: can't get address info for host anon=nfs
Mar 24 11:21:10 nas mountd[2146]: bad host anon=nfs, skipping
Mar 24 11:21:10 nas mountd[2146]: bad sec flavor: none
Mar 24 11:21:10 nas mountd[2146]: bad exports list line /mnt/storage/TV	anon=nfs -sec
 

paleoN

Wizard
Joined
Apr 22, 2012
Messages
1,403
Code:
Mar 24 11:20:48 nas smartd[2671]: Device: /dev/ada0, 1430 Currently unreadable (pending) sectors
Mar 24 11:20:48 nas smartd[2671]: Device: /dev/ada2, 1351 Currently unreadable (pending) sectors
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,526
The errors paleoN quoted tells me your system was most likely unresponsive because you have 2 hard drives failing. Those should be replaced asap. If you don't have backups, you'd better start doing them!
 

Mochaka

Dabbler
Joined
Mar 23, 2013
Messages
10
Wow can't believe i totally missed those two lines, feel stupid now. RMAing the drives now :)
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,526
You didn't post your zpool layout, but if you are using a RAIDZ2 it is possible you may have some corrupted files. When you install the 2 new disks and they complete their resilver it will tell you exactly what is corrupted due to bad sectors, bit rot, etc.
 

Mochaka

Dabbler
Joined
Mar 23, 2013
Messages
10
Running a scrub on it now to see how it goes. It still becomes unresponsive after accessing a file on it. It comes up with an error on the terminal if i have a screen plugged into it, but i didn't write it down last time. It had some zfs error, and when the server went unresponsive it came to a db> prompt.

Code:
  pool: storage
 state: DEGRADED
status: One or more devices could not be opened.  Sufficient replicas exist for
        the pool to continue functioning in a degraded state.
action: Attach the missing device and online it using 'zpool online'.
   see: http://www.sun.com/msg/ZFS-8000-2Q
  scan: scrub in progress since Mon Mar 25 20:39:16 2013
        503M scanned out of 5.35T at 29.6M/s, 52h43m to go
        0 repaired, 0.01% done
config:

        NAME                                            STATE     READ WRITE CKSUM
        storage                                         DEGRADED     0     0     0
          raidz1-0                                      DEGRADED     0     0     0
            gptid/922e1fd2-7fcf-706c-a494-c6fc0b1645fe  ONLINE       0     0     0
            11871215638548847284                        UNAVAIL      0     0     0  was /dev/gptid/e208a0ca-664f-016a-ef3d-be6c50d76354
            gptid/7aa5894a-0c23-5ec7-f44a-a06f7a83b5b7  ONLINE       0     0     0
          mirror-1                                      DEGRADED     0     0     0
            8155143147738015238                         OFFLINE      0     0     0  was /dev/dsk/gptid/041c7d00-da2f-8a60-e653-b2e8e5e029e2
            gptid/ccd2073b-7c54-d742-9655-9771593bba4b  ONLINE       0     0     0

errors: No known data errors
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,526
Yeah, if you have any bad sectors on either vdev you'll have some corruption since you have no additional replicas to rely on to reconstruct any corruption.
 
Status
Not open for further replies.
Top