FreeNAS 8.3.0-RELEASE is now available

Status
Not open for further replies.
J

jpaetzel

Guest
The FreeNAS development team is pleased to announce the immediate
availability of FreeNAS 8.3.0-RELEASE.

Images and plugins can be downloaded from the following site:

http://sourceforge.net/projects/freenas/files/FreeNAS-8.3.0/RELEASE/

FreeNAS 8.3.0 is based on FreeBSD 8.3 with version 28 of the ZFS
filesystem. This is a major milestone in FreeNAS development, bringing
in the plugin system with ZFS version 28. Development of the FreeNAS 8.2
branch has come to a halt, as both ZFS version 15 as well as FreeBSD 8.2
are no longer supported.

There have been no major changes between 8.3.0-RC1 and RELEASE, mostly
bugfixes and minor usability improvements to the GUI. See the
release notes for a complete list:

http://sourceforge.net/projects/freenas/files/FreeNAS-8.3.0/RC1/README/download

The bug tracker for FreeNAS is available at http://support.freenas.org

Discussion about FreeNAS occurs in the FreeNAS forums, located at:
http://forums.freenas.org as well as in the official FreeNAS IRC channel
on FreeNode in #freenas.
 

Sir.Robin

Guru
Joined
Apr 14, 2012
Messages
554
Great work! Been looking forward to it!! :) Thank you all!
 

Daisuke

Contributor
Joined
Jun 23, 2011
Messages
1,041
Upgraded without issues from 8.2.0-p1.x86_64.
While rebooting, I get a new warning I never saw before:
/etc/rc.d/dhclient: WARNING: failed to start dhclient

This is displaying repeatedly from usbus1 to usbus7?
I'm doing a scrub right now... after the zpool upgrade, so I can test the disks performance. I will post the exact warning message once the scrub is completed.

Update: Based on my initial transfer tests with files over 5GB through CIFS, the transfer speeds lost about 10MB/sec.

Here it is the warning:

IMG_20121027_005952.jpg
 

Yatti420

Wizard
Joined
Aug 12, 2012
Messages
1,437
Upgraded without issues from 8.2.0-p1.x86_64.
While rebooting, I get a new warning I never saw before:
/etc/rc.d/dhclient: WARNING: failed to start dhclient

This is displaying repeatedly from usbus1 to usbus7?
I'm doing a scrub right now... after the zpool upgrade, so I can test the disks performance. I will post the exact warning message once the scrub is completed.

I look forward to upgrading.. Everything is stable for now on 8.2.0...
 

Daisuke

Contributor
Joined
Jun 23, 2011
Messages
1,041
The poll timeouts are still there. :(
Code:
# tail -n 300 /var/log/messages
Oct 26 19:21:04 pluto newsyslog[2258]: logfile first created
Oct 26 19:21:04 pluto syslogd: kernel boot file is /boot/kernel/kernel
Oct 26 19:21:04 pluto kernel: Copyright (c) 1992-2012 The FreeBSD Project.
Oct 26 19:21:04 pluto kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
Oct 26 19:21:04 pluto kernel: The Regents of the University of California. All rights reserved.
Oct 26 19:21:04 pluto kernel: FreeBSD is a registered trademark of The FreeBSD Foundation.
Oct 26 19:21:04 pluto kernel: FreeBSD 8.3-RELEASE-p4 #0 r241984M: Wed Oct 24 00:57:10 PDT 2012
Oct 26 19:21:04 pluto 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
Oct 26 19:21:04 pluto kernel: Timecounter "i8254" frequency 1193182 Hz quality 0
Oct 26 19:21:04 pluto kernel: CPU: Intel(R) Atom(TM) CPU D525   @ 1.80GHz (1807.21-MHz K8-class CPU)
Oct 26 19:21:04 pluto kernel: Origin = "GenuineIntel"  Id = 0x106ca  Family = 6  Model = 1c  Stepping = 10
Oct 26 19:21:04 pluto 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>
Oct 26 19:21:04 pluto kernel: Features2=0x40e31d<SSE3,DTES64,MON,DS_CPL,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE>
Oct 26 19:21:04 pluto kernel: AMD Features=0x20100800<SYSCALL,NX,LM>
Oct 26 19:21:04 pluto kernel: AMD Features2=0x1<LAHF>
Oct 26 19:21:04 pluto kernel: TSC: P-state invariant
Oct 26 19:21:04 pluto kernel: real memory  = 8589934592 (8192 MB)
Oct 26 19:21:04 pluto kernel: avail memory = 8235593728 (7854 MB)
Oct 26 19:21:04 pluto kernel: ACPI APIC Table: <022112 APIC1550>
Oct 26 19:21:04 pluto kernel: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
Oct 26 19:21:04 pluto kernel: FreeBSD/SMP: 1 package(s) x 2 core(s) x 2 HTT threads
Oct 26 19:21:04 pluto kernel: cpu0 (BSP): APIC ID:  0
Oct 26 19:21:04 pluto kernel: cpu1 (AP/HT): APIC ID:  1
Oct 26 19:21:04 pluto kernel: cpu2 (AP): APIC ID:  2
Oct 26 19:21:04 pluto kernel: cpu3 (AP/HT): APIC ID:  3
Oct 26 19:21:04 pluto kernel: WARNING: VIMAGE (virtualized network stack) is a highly experimental feature.
Oct 26 19:21:04 pluto kernel: ioapic0: Changing APIC ID to 4
Oct 26 19:21:04 pluto kernel: ioapic0 <Version 2.0> irqs 0-23 on motherboard
Oct 26 19:21:04 pluto kernel: kbd1 at kbdmux0
Oct 26 19:21:04 pluto kernel: hpt27xx: RocketRAID 27xx controller driver v1.0 (Oct 24 2012 00:56:59)
Oct 26 19:21:04 pluto kernel: cryptosoft0: <software crypto> on motherboard
Oct 26 19:21:04 pluto kernel: aesni0: No AESNI support.
Oct 26 19:21:04 pluto kernel: acpi0: <SMCI > on motherboard
Oct 26 19:21:04 pluto kernel: acpi0: [ITHREAD]
Oct 26 19:21:04 pluto kernel: acpi0: Power Button (fixed)
Oct 26 19:21:04 pluto kernel: acpi0: reservation of fee00000, 1000 (3) failed
Oct 26 19:21:04 pluto kernel: acpi0: reservation of 0, a0000 (3) failed
Oct 26 19:21:04 pluto kernel: acpi0: reservation of 100000, bff00000 (3) failed
Oct 26 19:21:04 pluto kernel: Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
Oct 26 19:21:04 pluto kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
Oct 26 19:21:04 pluto kernel: cpu0: <ACPI CPU> on acpi0
Oct 26 19:21:04 pluto kernel: cpu1: <ACPI CPU> on acpi0
Oct 26 19:21:04 pluto kernel: cpu2: <ACPI CPU> on acpi0
Oct 26 19:21:04 pluto kernel: cpu3: <ACPI CPU> on acpi0
Oct 26 19:21:04 pluto kernel: pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
Oct 26 19:21:04 pluto kernel: pci0: <ACPI PCI bus> on pcib0
Oct 26 19:21:04 pluto kernel: uhci0: <Intel 82801I (ICH9) USB controller> port 0xac00-0xac1f irq 16 at device 26.0 on pci0
Oct 26 19:21:04 pluto kernel: uhci0: [ITHREAD]
Oct 26 19:21:04 pluto kernel: usbus0: <Intel 82801I (ICH9) USB controller> on uhci0
Oct 26 19:21:04 pluto kernel: uhci1: <Intel 82801I (ICH9) USB controller> port 0xa880-0xa89f irq 21 at device 26.1 on pci0
Oct 26 19:21:04 pluto kernel: uhci1: [ITHREAD]
Oct 26 19:21:04 pluto kernel: usbus1: <Intel 82801I (ICH9) USB controller> on uhci1
Oct 26 19:21:04 pluto kernel: uhci2: <Intel 82801I (ICH9) USB controller> port 0xa800-0xa81f irq 19 at device 26.2 on pci0
Oct 26 19:21:04 pluto kernel: uhci2: [ITHREAD]
Oct 26 19:21:04 pluto kernel: usbus2: <Intel 82801I (ICH9) USB controller> on uhci2
Oct 26 19:21:04 pluto kernel: ehci0: <Intel 82801I (ICH9) USB 2.0 controller> mem 0xfebfbc00-0xfebfbfff irq 18 at device 26.7 on pci0
Oct 26 19:21:04 pluto kernel: ehci0: [ITHREAD]
Oct 26 19:21:04 pluto kernel: usbus3: EHCI version 1.0
Oct 26 19:21:04 pluto kernel: usbus3: <Intel 82801I (ICH9) USB 2.0 controller> on ehci0
Oct 26 19:21:04 pluto kernel: pcib1: <ACPI PCI-PCI bridge> irq 17 at device 28.0 on pci0
Oct 26 19:21:04 pluto kernel: pci1: <ACPI PCI bus> on pcib1
Oct 26 19:21:04 pluto kernel: ahci0: <Marvell 88SE912x AHCI SATA controller> port 0xc480-0xc487,0xc400-0xc403,0xcc00-0xcc07,0xc880-0xc883,0xc800-0xc80f mem 0xfe8ef800-0xfe8effff irq 16 at device 0.0 on pci1
Oct 26 19:21:04 pluto kernel: ahci0: [ITHREAD]
Oct 26 19:21:04 pluto kernel: ahci0: AHCI v1.20 with 8 6Gbps ports, Port Multiplier not supported
Oct 26 19:21:04 pluto kernel: ahcich0: <AHCI channel> at channel 0 on ahci0
Oct 26 19:21:04 pluto kernel: ahcich0: [ITHREAD]
Oct 26 19:21:04 pluto kernel: ahcich1: <AHCI channel> at channel 1 on ahci0
Oct 26 19:21:04 pluto kernel: ahcich1: [ITHREAD]
Oct 26 19:21:04 pluto kernel: ahcich2: <AHCI channel> at channel 2 on ahci0
Oct 26 19:21:04 pluto kernel: ahcich2: [ITHREAD]
Oct 26 19:21:04 pluto kernel: ahcich3: <AHCI channel> at channel 3 on ahci0
Oct 26 19:21:04 pluto kernel: ahcich3: [ITHREAD]
Oct 26 19:21:04 pluto kernel: ahcich4: <AHCI channel> at channel 4 on ahci0
Oct 26 19:21:04 pluto kernel: ahcich4: [ITHREAD]
Oct 26 19:21:04 pluto kernel: ahcich5: <AHCI channel> at channel 5 on ahci0
Oct 26 19:21:04 pluto kernel: ahcich5: [ITHREAD]
Oct 26 19:21:04 pluto kernel: ahcich6: <AHCI channel> at channel 6 on ahci0
Oct 26 19:21:04 pluto kernel: ahcich6: [ITHREAD]
Oct 26 19:21:04 pluto kernel: ahcich7: <AHCI channel> at channel 7 on ahci0
Oct 26 19:21:04 pluto kernel: ahcich7: [ITHREAD]
Oct 26 19:21:04 pluto kernel: atapci0: <Marvell 88SE912x UDMA133 controller> port 0xb880-0xb887,0xb800-0xb803,0xc080-0xc087,0xc000-0xc003,0xbc00-0xbc0f mem 0xfe8cfc00-0xfe8cfc0f irq 17 at device 0.1 on pci1
Oct 26 19:21:04 pluto kernel: pcib2: <ACPI PCI-PCI bridge> irq 17 at device 28.4 on pci0
Oct 26 19:21:04 pluto kernel: pci2: <ACPI PCI bus> on pcib2
Oct 26 19:21:04 pluto kernel: em0: <Intel(R) PRO/1000 Network Connection 7.3.2> port 0xdc00-0xdc1f mem 0xfe9e0000-0xfe9fffff,0xfe9dc000-0xfe9dffff irq 16 at device 0.0 on pci2
Oct 26 19:21:04 pluto kernel: em0: Using MSIX interrupts with 3 vectors
Oct 26 19:21:04 pluto kernel: em0: [ITHREAD]
Oct 26 19:21:04 pluto last message repeated 2 times
Oct 26 19:21:04 pluto kernel: em0: Ethernet address: 00:25:90:38:2e:1e
Oct 26 19:21:04 pluto kernel: pcib3: <ACPI PCI-PCI bridge> irq 16 at device 28.5 on pci0
Oct 26 19:21:04 pluto kernel: pci3: <ACPI PCI bus> on pcib3
Oct 26 19:21:04 pluto kernel: em1: <Intel(R) PRO/1000 Network Connection 7.3.2> port 0xec00-0xec1f mem 0xfeae0000-0xfeafffff,0xfeadc000-0xfeadffff irq 17 at device 0.0 on pci3
Oct 26 19:21:04 pluto kernel: em1: Using MSIX interrupts with 3 vectors
Oct 26 19:21:04 pluto kernel: em1: [ITHREAD]
Oct 26 19:21:04 pluto last message repeated 2 times
Oct 26 19:21:04 pluto kernel: em1: Ethernet address: 00:25:90:38:2e:1f
Oct 26 19:21:04 pluto kernel: uhci3: <Intel 82801I (ICH9) USB controller> port 0xa480-0xa49f irq 23 at device 29.0 on pci0
Oct 26 19:21:04 pluto kernel: uhci3: [ITHREAD]
Oct 26 19:21:04 pluto kernel: usbus4: <Intel 82801I (ICH9) USB controller> on uhci3
Oct 26 19:21:04 pluto kernel: uhci4: <Intel 82801I (ICH9) USB controller> port 0xa400-0xa41f irq 19 at device 29.1 on pci0
Oct 26 19:21:04 pluto kernel: uhci4: [ITHREAD]
Oct 26 19:21:04 pluto kernel: usbus5: <Intel 82801I (ICH9) USB controller> on uhci4
Oct 26 19:21:04 pluto kernel: uhci5: <Intel 82801I (ICH9) USB controller> port 0xa080-0xa09f irq 18 at device 29.2 on pci0
Oct 26 19:21:04 pluto kernel: uhci5: [ITHREAD]
Oct 26 19:21:04 pluto kernel: usbus6: <Intel 82801I (ICH9) USB controller> on uhci5
Oct 26 19:21:04 pluto kernel: ehci1: <Intel 82801I (ICH9) USB 2.0 controller> mem 0xfebfb800-0xfebfbbff irq 23 at device 29.7 on pci0
Oct 26 19:21:04 pluto kernel: ehci1: [ITHREAD]
Oct 26 19:21:04 pluto kernel: usbus7: EHCI version 1.0
Oct 26 19:21:04 pluto kernel: usbus7: <Intel 82801I (ICH9) USB 2.0 controller> on ehci1
Oct 26 19:21:04 pluto kernel: pcib4: <ACPI PCI-PCI bridge> at device 30.0 on pci0
Oct 26 19:21:04 pluto kernel: pci4: <ACPI PCI bus> on pcib4
Oct 26 19:21:04 pluto kernel: vgapci0: <VGA-compatible display> mem 0xfc000000-0xfcffffff,0xfdffc000-0xfdffffff,0xfe000000-0xfe7fffff irq 17 at device 4.0 on pci4
Oct 26 19:21:04 pluto kernel: isab0: <PCI-ISA bridge> at device 31.0 on pci0
Oct 26 19:21:04 pluto kernel: isa0: <ISA bus> on isab0
Oct 26 19:21:04 pluto kernel: ahci1: <Intel ICH9 AHCI SATA controller> port 0x9480-0x9487,0xa000-0xa003,0x9c00-0x9c07,0x9880-0x9883,0x9800-0x981f mem 0xfebfb000-0xfebfb7ff irq 19 at device 31.2 on pci0
Oct 26 19:21:04 pluto kernel: ahci1: [ITHREAD]
Oct 26 19:21:04 pluto kernel: ahci1: AHCI v1.20 with 6 3Gbps ports, Port Multiplier not supported
Oct 26 19:21:04 pluto kernel: ahcich8: <AHCI channel> at channel 0 on ahci1
Oct 26 19:21:04 pluto kernel: ahcich8: [ITHREAD]
Oct 26 19:21:04 pluto kernel: ahcich9: <AHCI channel> at channel 1 on ahci1
Oct 26 19:21:04 pluto kernel: ahcich9: [ITHREAD]
Oct 26 19:21:04 pluto kernel: ahcich10: <AHCI channel> at channel 2 on ahci1
Oct 26 19:21:04 pluto kernel: ahcich10: [ITHREAD]
Oct 26 19:21:04 pluto kernel: ahcich11: <AHCI channel> at channel 3 on ahci1
Oct 26 19:21:04 pluto kernel: ahcich11: [ITHREAD]
Oct 26 19:21:04 pluto kernel: ahcich12: <AHCI channel> at channel 4 on ahci1
Oct 26 19:21:04 pluto kernel: ahcich12: [ITHREAD]
Oct 26 19:21:04 pluto kernel: ahcich13: <AHCI channel> at channel 5 on ahci1
Oct 26 19:21:04 pluto kernel: ahcich13: [ITHREAD]
Oct 26 19:21:04 pluto kernel: pci0: <serial bus, SMBus> at device 31.3 (no driver attached)
Oct 26 19:21:04 pluto kernel: acpi_button0: <Power Button> on acpi0
Oct 26 19:21:04 pluto kernel: atrtc0: <AT realtime clock> port 0x70-0x71 irq 8 on acpi0
Oct 26 19:21:04 pluto kernel: uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
Oct 26 19:21:04 pluto kernel: uart0: [FILTER]
Oct 26 19:21:04 pluto kernel: uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0
Oct 26 19:21:04 pluto kernel: uart1: [FILTER]
Oct 26 19:21:04 pluto kernel: uart2: <16550 or compatible> port 0x3e8-0x3ef irq 5 on acpi0
Oct 26 19:21:04 pluto kernel: uart2: [FILTER]
Oct 26 19:21:04 pluto kernel: acpi_hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
Oct 26 19:21:04 pluto kernel: Timecounter "HPET" frequency 14318180 Hz quality 900
Oct 26 19:21:04 pluto kernel: orm0: <ISA Option ROMs> at iomem 0xc0000-0xc7fff,0xc8000-0xcafff on isa0
Oct 26 19:21:04 pluto kernel: sc0: <System console> at flags 0x100 on isa0
Oct 26 19:21:04 pluto kernel: sc0: VGA <16 virtual consoles, flags=0x300>
Oct 26 19:21:04 pluto kernel: vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
Oct 26 19:21:04 pluto kernel: atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
Oct 26 19:21:04 pluto kernel: atkbd0: <AT Keyboard> irq 1 on atkbdc0
Oct 26 19:21:04 pluto kernel: kbd0 at atkbd0
Oct 26 19:21:04 pluto kernel: atkbd0: [GIANT-LOCKED]
Oct 26 19:21:04 pluto kernel: atkbd0: [ITHREAD]
Oct 26 19:21:04 pluto kernel: ppc0: cannot reserve I/O port range
Oct 26 19:21:04 pluto kernel: coretemp0: <CPU On-Die Thermal Sensors> on cpu0
Oct 26 19:21:04 pluto kernel: p4tcc0: <CPU Frequency Thermal Control> on cpu0
Oct 26 19:21:04 pluto kernel: coretemp1: <CPU On-Die Thermal Sensors> on cpu1
Oct 26 19:21:04 pluto kernel: p4tcc1: <CPU Frequency Thermal Control> on cpu1
Oct 26 19:21:04 pluto kernel: coretemp2: <CPU On-Die Thermal Sensors> on cpu2
Oct 26 19:21:04 pluto kernel: p4tcc2: <CPU Frequency Thermal Control> on cpu2
Oct 26 19:21:04 pluto kernel: coretemp3: <CPU On-Die Thermal Sensors> on cpu3
Oct 26 19:21:04 pluto kernel: p4tcc3: <CPU Frequency Thermal Control> on cpu3
Oct 26 19:21:04 pluto kernel: fuse4bsd: version 0.3.9-pre1, FUSE ABI 7.8
Oct 26 19:21:04 pluto kernel: Timecounters tick every 1.000 msec
Oct 26 19:21:04 pluto kernel: hpt27xx: no controller detected.
Oct 26 19:21:04 pluto kernel: usbus0: 12Mbps Full Speed USB v1.0
Oct 26 19:21:04 pluto kernel: usbus1: 12Mbps Full Speed USB v1.0
Oct 26 19:21:04 pluto kernel: usbus2: 12Mbps Full Speed USB v1.0
Oct 26 19:21:04 pluto kernel: usbus3: 480Mbps High Speed USB v2.0
Oct 26 19:21:04 pluto kernel: usbus4: 12Mbps Full Speed USB v1.0
Oct 26 19:21:04 pluto kernel: usbus5: 12Mbps Full Speed USB v1.0
Oct 26 19:21:04 pluto kernel: usbus6: 12Mbps Full Speed USB v1.0
Oct 26 19:21:04 pluto kernel: usbus7: 480Mbps High Speed USB v2.0
Oct 26 19:21:04 pluto kernel: ugen0.1: <Intel> at usbus0
Oct 26 19:21:04 pluto kernel: uhub0: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0
Oct 26 19:21:04 pluto kernel: ugen1.1: <Intel> at usbus1
Oct 26 19:21:04 pluto kernel: uhub1: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus1
Oct 26 19:21:04 pluto kernel: ugen2.1: <Intel> at usbus2
Oct 26 19:21:04 pluto kernel: uhub2: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus2
Oct 26 19:21:04 pluto kernel: ugen3.1: <Intel> at usbus3
Oct 26 19:21:04 pluto kernel: uhub3: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus3
Oct 26 19:21:04 pluto kernel: ugen4.1: <Intel> at usbus4
Oct 26 19:21:04 pluto kernel: uhub4: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus4
Oct 26 19:21:04 pluto kernel: ugen5.1: <Intel> at usbus5
Oct 26 19:21:04 pluto kernel: uhub5: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus5
Oct 26 19:21:04 pluto kernel: ugen6.1: <Intel> at usbus6
Oct 26 19:21:04 pluto kernel: uhub6: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus6
Oct 26 19:21:04 pluto kernel: ugen7.1: <Intel> at usbus7
Oct 26 19:21:04 pluto kernel: uhub7: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus7
Oct 26 19:21:04 pluto kernel: uhub0: 2 ports with 2 removable, self powered
Oct 26 19:21:04 pluto kernel: uhub1: 2 ports with 2 removable, self powered
Oct 26 19:21:04 pluto kernel: uhub2: 2 ports with 2 removable, self powered
Oct 26 19:21:04 pluto kernel: uhub4: 2 ports with 2 removable, self powered
Oct 26 19:21:04 pluto kernel: uhub5: 2 ports with 2 removable, self powered
Oct 26 19:21:04 pluto kernel: uhub6: 2 ports with 2 removable, self powered
Oct 26 19:21:04 pluto kernel: uhub3: 6 ports with 6 removable, self powered
Oct 26 19:21:04 pluto kernel: uhub7: 6 ports with 6 removable, self powered
Oct 26 19:21:04 pluto kernel: ugen3.2: <vendor 0x13fe> at usbus3
Oct 26 19:21:04 pluto kernel: umass0: <vendor 0x13fe Patriot Memory, class 0/0, rev 2.00/1.00, addr 2> on usbus3
Oct 26 19:21:04 pluto kernel: ugen4.2: <Dell> at usbus4
Oct 26 19:21:04 pluto kernel: ukbd0: <EP1 Interrupt> on usbus4
Oct 26 19:21:04 pluto kernel: kbd2 at ukbd0
Oct 26 19:21:04 pluto kernel: ugen2.2: <Winbond Electronics Corp> at usbus2
Oct 26 19:21:04 pluto kernel: ums0: <Winbond Electronics Corp Hermon USB hidmouse Device, class 0/0, rev 1.10/0.01, addr 2> on usbus2
Oct 26 19:21:04 pluto kernel: ums0: 3 buttons and [Z] coordinates ID=0
Oct 26 19:21:04 pluto kernel: ukbd1: <Winbond Electronics Corp Hermon USB hidmouse Device, class 0/0, rev 1.10/0.01, addr 2> on usbus2
Oct 26 19:21:04 pluto kernel: kbd3 at ukbd1
Oct 26 19:21:04 pluto kernel: ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
Oct 26 19:21:04 pluto kernel: ada0: <M4-CT064M4SSD2 0009> ATA-9 SATA 3.x device
Oct 26 19:21:04 pluto kernel: ada0: 600.000MB/s transfers (SATA 3.x, UDMA5, PIO 8192bytes)
Oct 26 19:21:04 pluto kernel: ada0: Command Queueing enabled
Oct 26 19:21:04 pluto kernel: ada0: 61057MB (125045424 512 byte sectors: 16H 63S/T 16383C)
Oct 26 19:21:04 pluto kernel: ada1 at ahcich8 bus 0 scbus8 target 0 lun 0
Oct 26 19:21:04 pluto kernel: ada1: <WDC WD20EARS-00MVWB0 51.0AB51> ATA-8 SATA 2.x device
Oct 26 19:21:04 pluto kernel: ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
Oct 26 19:21:04 pluto kernel: ada1: Command Queueing enabled
Oct 26 19:21:04 pluto kernel: ada1: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
Oct 26 19:21:04 pluto kernel: ada2 at ahcich9 bus 0 scbus9 target 0 lun 0
Oct 26 19:21:04 pluto kernel: ada2: <WDC WD20EARS-00MVWB0 51.0AB51> ATA-8 SATA 2.x device
Oct 26 19:21:04 pluto kernel: ada2: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
Oct 26 19:21:04 pluto kernel: ada2: Command Queueing enabled
Oct 26 19:21:04 pluto kernel: ada2: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
Oct 26 19:21:04 pluto kernel: ada3 at ahcich10 bus 0 scbus10 target 0 lun 0
Oct 26 19:21:04 pluto kernel: ada3: <WDC WD20EARS-00MVWB0 51.0AB51> ATA-8 SATA 2.x device
Oct 26 19:21:04 pluto kernel: ada3: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
Oct 26 19:21:04 pluto kernel: ada3: Command Queueing enabled
Oct 26 19:21:04 pluto kernel: ada3: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
Oct 26 19:21:04 pluto kernel: ada4 at ahcich11 bus 0 scbus11 target 0 lun 0
Oct 26 19:21:04 pluto kernel: ada4: <WDC WD20EARS-00MVWB0 51.0AB51> ATA-8 SATA 2.x device
Oct 26 19:21:04 pluto kernel: ada4: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
Oct 26 19:21:04 pluto kernel: ada4: Command Queueing enabled
Oct 26 19:21:04 pluto kernel: ada4: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
Oct 26 19:21:04 pluto kernel: ada5 at ahcich12 bus 0 scbus12 target 0 lun 0
Oct 26 19:21:04 pluto kernel: ada5: <WDC WD20EARS-00MVWB0 51.0AB51> ATA-8 SATA 2.x device
Oct 26 19:21:04 pluto kernel: ada5: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
Oct 26 19:21:04 pluto kernel: ada5: Command Queueing enabled
Oct 26 19:21:04 pluto kernel: ada5: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
Oct 26 19:21:04 pluto kernel: ada6 at ahcich13 bus 0 scbus13 target 0 lun 0
Oct 26 19:21:04 pluto kernel: ada6: <WDC WD20EARS-00MVWB0 51.0AB51> ATA-8 SATA 2.x device
Oct 26 19:21:04 pluto kernel: ada6: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
Oct 26 19:21:04 pluto kernel: ada6: Command Queueing enabled
Oct 26 19:21:04 pluto kernel: ada6: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
Oct 26 19:21:04 pluto kernel: da0 at umass-sim0 bus 0 scbus14 target 0 lun 0
Oct 26 19:21:04 pluto kernel: da0: < Patriot Memory PMAP> Removable Direct Access SCSI-0 device 
Oct 26 19:21:04 pluto kernel: da0: 40.000MB/s transfers
Oct 26 19:21:04 pluto kernel: da0: 3824MB (7831552 512 byte sectors: 255H 63S/T 487C)
Oct 26 19:21:04 pluto kernel: pass1 at ahcich7 bus 0 scbus7 target 0 lun 0
Oct 26 19:21:04 pluto kernel: pass1: <Marvell 91xx Config 1.01> Removable Processor SCSI-0 device 
Oct 26 19:21:04 pluto kernel: pass1: 150.000MB/s transfers (SATA 1.x, UDMA4, ATAPI 12bytes, PIO 8192bytes)
Oct 26 19:21:04 pluto kernel: SMP: AP CPU #1 Launched!
Oct 26 19:21:04 pluto kernel: SMP: AP CPU #3 Launched!
Oct 26 19:21:04 pluto kernel: SMP: AP CPU #2 Launched!
Oct 26 19:21:04 pluto kernel: GEOM: da0s1: geometry does not match label (16h,63s != 255h,63s).
Oct 26 19:21:04 pluto kernel: GEOM: da0s2: geometry does not match label (16h,63s != 255h,63s).
Oct 26 19:21:04 pluto kernel: Trying to mount root from ufs:/dev/ufs/FreeNASs1a
Oct 26 19:21:04 pluto kernel: ZFS filesystem version 5
Oct 26 19:21:04 pluto kernel: ZFS storage pool version 28
Oct 26 19:21:05 pluto root: /etc/rc: WARNING: failed precmd routine for vmware_guestd
Oct 26 19:21:05 pluto ntpd[2569]: ntpd 4.2.4p5-a (1)
Oct 26 19:21:16 pluto ntpd[2570]: time reset +0.976942 s
Oct 26 19:29:02 pluto su: floren to root on /dev/pts/0
Oct 26 19:36:39 pluto ntpd[2570]: kernel time sync status change 2001
Oct 26 20:09:32 pluto kernel: ahcich0: Timeout on slot 1 port 0
Oct 26 20:09:32 pluto kernel: ahcich0: is 00000000 cs 0000000e ss 0000000e rs 0000000e tfd 40 serr 00000000 cmd 10008317
Oct 26 20:10:23 pluto kernel: ahcich0: Timeout on slot 3 port 0
Oct 26 20:10:23 pluto kernel: ahcich0: is 00000000 cs 00000008 ss 00000000 rs 00000008 tfd 50 serr 00000000 cmd 10008317
Oct 26 20:11:06 pluto su: floren to root on /dev/pts/0
Oct 26 20:11:13 pluto kernel: ahcich0: Timeout on slot 3 port 0
Oct 26 20:11:13 pluto kernel: ahcich0: is 00000000 cs 00000008 ss 00000000 rs 00000008 tfd 50 serr 00000000 cmd 10008317
Oct 26 20:11:13 pluto kernel: (ada0:ahcich0:0:0:0): lost device
Oct 26 20:12:03 pluto kernel: ahcich0: Timeout on slot 3 port 0
Oct 26 20:12:03 pluto kernel: ahcich0: is 00000000 cs 00000038 ss 00000038 rs 00000038 tfd 50 serr 00000000 cmd 10008317
Oct 26 20:12:42 pluto kernel: ahcich0: Poll timeout on slot 5 port 0
Oct 26 20:12:42 pluto kernel: ahcich0: is 00000001 cs 00000020 ss 00000000 rs 00000020 tfd 450 serr 00000000 cmd 10008517


Not sure if related but they started popping after an hour of scrubbing.
 

Daisuke

Contributor
Joined
Jun 23, 2011
Messages
1,041
More issues. The load hovers at around 1.25 with a 30% CPU usage, when I do nothing. Looking quckly at ps aux and top, I see these processes running:
Code:
# ps aux
USER     PID %CPU %MEM   VSZ   RSS  TT  STAT STARTED      TIME COMMAND
root      11 249.4  0.0     0    64  ??  RL   12:58AM 2035:00.68 [idle]
root       2 100.0  0.0     0    16  ??  RL   12:58AM 663:24.14 [g_event]
root    2824 12.7  1.1 199424 95312  ??  S     1:00AM  35:35.17 /usr/local/bin/python /usr/local/www/freenasUI/manage.py runfcgi method
root       0  0.4  0.0     0  2576  ??  DLs  12:58AM  37:36.11 [kernel]
...

# top
last pid: 11603;  load averages:  1.33,  1.34,  1.33  up 0+12:10:37  13:08:20
38 processes:  1 running, 37 sleeping
CPU:  3.4% user,  0.0% nice, 26.5% system,  0.1% interrupt, 70.0% idle
Mem: 141M Active, 5337M Inact, 2068M Wired, 17M Cache, 208M Buf, 342M Free
Swap: 12G Total, 12G Free

  PID USERNAME    THR PRI NICE   SIZE    RES STATE   C   TIME   WCPU COMMAND
 2824 root          6  48    0   195M 95780K uwait   1  36:00 12.06% python
 4063 root          1  44    0 50356K  8148K select  0   2:48  0.00% smbd


Is it normal to have the g_event and manage.py script consume resources like that? If I reboot the server, the load stays at 0.10 for a while (as it was before) then the load jumps back to 1.25-1.30.

Code:
# ps aux
USER     PID %CPU %MEM   VSZ   RSS  TT  STAT STARTED      TIME COMMAND
root      11 399.7  0.0     0    64  ??  RL    1:14PM  15:38.49 [idle]
root       0  0.0  0.0     0  2576  ??  DLs   1:14PM   0:00.99 [kernel]
root       1  0.0  0.0  3204   584  ??  ILs   1:14PM   0:00.01 /sbin/init --
root       2  0.0  0.0     0    16  ??  DL    1:14PM   0:00.18 [g_event]
...
root    2824  0.0  0.9 175792 75596  ??  I     1:16PM   0:04.75 /usr/local/bin/python /usr/local/www/freenasUI/manage.py runfcgi method
...

# top
last pid:  3708;  load averages:  0.06,  0.27,  0.25  up 0+00:09:30  13:23:47
37 processes:  1 running, 36 sleeping
CPU:  0.0% user,  0.0% nice,  0.1% system,  0.1% interrupt, 99.8% idle
Mem: 96M Active, 60M Inact, 237M Wired, 2176K Cache, 182M Buf, 7510M Free
Swap: 12G Total, 12G Free

  PID USERNAME    THR PRI NICE   SIZE    RES STATE   C   TIME   WCPU COMMAND
 2824 root          6  45    0   174M 78652K uwait   2   0:08  0.00% python


Edit: Re-installing from scratch and configuring manually the settings solved the load issue. Looks like the best way way to upgrade to a major version is to install from scratch, without importing your old settings.
 

joeschmuck

Old Man
Moderator
Joined
May 28, 2011
Messages
10,994
Loaded and runs as well as RC1. It is too bad there is a slowness after converting to V28 but I guess that's progress :(
 

bleomycin

Cadet
Joined
Nov 1, 2012
Messages
5
Loaded and runs as well as RC1. It is too bad there is a slowness after converting to V28 but I guess that's progress :(

Do you mind clarifying this? Are you getting slow network performance? What do your CIFS transfer rates tap out compared to raw disk read/write speeds directly on the machine? Anything less than gigabit line speed is completely unacceptable to me, i've never gotten anywhere close to that on extremely modern hardware with any of the BSD based distros. Switching to zfsonlinux.org solved the speed problems but i lost the easy management gui.
 

Daisuke

Contributor
Joined
Jun 23, 2011
Messages
1,041
Do you mind clarifying this? Are you getting slow network performance? What do your CIFS transfer rates tap out compared to raw disk read/write speeds directly on the machine?

My own experience with FreeNAS and CIFS, on same hardware:
8.0.1-8.0.2 = 115MB/sec
8.0.4-8.2.0 = 80MB/sec
8.3.0 = 50MB/sec

Something went down the drain, related to CIFS. 8.3.0 slowdown is related to ZFS v28 but I'm pretty sure CIFS is slowing things also. Either ways, I miss my 115MB transfers and I know I will never see them again. Hopefully, NFSv4 will make surface in FreeNAS and I will be able to switch to it.
 

Ico747

Dabbler
Joined
Jan 5, 2012
Messages
39
After upgrading from 8.2.0-p1.x86_64 to 8.3.0-RELEASE I get from Alert system WARNING: The volume volume_A (ZFS) status is UNKNOWN. In Active volumes I have: volume_A /mnt/volume_A None (Error) Error getting available space Error getting total space UNKNOWN. View Disks is empty. Please help.

-Solved - BIOS SATA emulatition changed from IDE to AHCI.
 

Stephens

Patron
Joined
Jun 19, 2012
Messages
496
You can always go to a shell and type "zpool status -v" if you want to know what's going on with your pool. I suspect there's no real error and it's just "warning" you that your ZPOOL is still at version v15, not v28 (which is supported as of FreeNAS 8.3).
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,526
FYI. I did a zpool upgrade tonight on a production server. You WILL get the yellow alert light that your zpool is not the latest version for about 30 minute after you do a zpool upgrade. Just wait it out and it will clear on its own.
 

Simon00

Dabbler
Joined
Jan 22, 2012
Messages
17
From reading the comments, I am deathly afraid to upgrade from FreeNAS-8.2.0-RELEASE-p1-x64, as it is my main/only server at the moment with ALL my useful (no A/V stuff) software, drivers, docs, manuals, etc... on it.

Should we be waiting for 8.3.1-RELEASE??? in order for all the kinks to be fixed? No hurry though...:) as 8.2.0 p1 fixed ALL the issues of failure to boot I was having. I only have 2GB of RAM, though... w/ only 1-2 user using it...

Is v28 buggy at the moment under 8.3.0?
 

Milhouse

Guru
Joined
Jun 1, 2011
Messages
564
From reading the comments, I am deathly afraid to upgrade from FreeNAS-8.2.0-RELEASE-p1-x64, as it is my main/only server at the moment with ALL my useful (no A/V stuff) software, drivers, docs, manuals, etc... on it.

Should we be waiting for 8.3.1-RELEASE??? in order for all the kinks to be fixed? No hurry though...:) as 8.2.0 p1 fixed ALL the issues of failure to boot I was having. I only have 2GB of RAM, though... w/ only 1-2 user using it...

You wouldn't be so afraid if you had a current backup on which to fall back on. I'd be worried too if I didn't have a backup when upgrading ANY software on the NAS, but then I'd have nobody to blame other than myself if I lost all my data.

Is v28 buggy at the moment under 8.3.0?

v28 in 8.3.0 seems OK so far (still testing).
 

Stephens

Patron
Joined
Jun 19, 2012
Messages
496
I don't think we should be discussing this stuff in a release thread. Some people subscribe to release threads and don't want all the general chit-chat, just information about new releases. But since I'm making one useless post to say that, I'll cover a few other things in this post.

1. Back up your NAS. Seriously. I don't care if you have RAID-Z9, back it up. There has to be some way you can do a reasonable backup so if your RAID blows up in smoke taking out EVERYTHING at one time, you still have some of youre more important stuff. Burn a DVD-R with documents, get an external 2TB or 3TB USB drive. Something.

2. I'm a firm believer in if it ain't broke, don't fix it. Some people enjoy experimenting, etc. More power to them. But why would you upgrade if 8.2 is really doing everything you want/need. The only reason I upgrade is because an upgraded version addresses issues I currently have, or may have in the future, or has new features I want. I still have an 8.0.4 server that I'm going to upgrade, but only because the UPS support is better. I've tested it, and my 8.2 system shuts down when it goes on UPS power, but my 8.0.4 system doesn't. That's a reason to upgrade. But I may as well go to 8.3 instead of 8.2. I have other reasons too. But the point is, I have _reasons_ to upgrade, I'm not just upgrading to upgrade.

3. I wouldn't call ZFS v28 buggy under 8.3.0. ZFS v28 support is inherent in the version of FreeBSD (nanoBSD) FreeNAS is built on top of. V28 has been out for some time, and so has the version of FreeBSD which first used it. FreeNAS tends to lag, but that lag gives things time to be settle before FreeNAS uses it.

4. I'm not sure what errors you think you've seen in 8.3. I saw one with a "Welcome to NGIX!" error, but that's all that jumps out at me (that one looks like it may be a browser cache issue).

I would have no fear of FreeNAS 8.3 or ZFS v28 at this point. Folks with slow machines like mine should just be aware it's may run a little slower than previous versions. You may be especially sensitive to that with only 2GB of RAM.
 

R.G.

Explorer
Joined
Sep 11, 2011
Messages
96
Note of thanks - it's working fine for me

A special note of thanks to everyone who worked on and tested this release. My install worked fine, first time (excluding my dumb mistakes) and looks to be exactly what I needed.

Some history is appropriate. I decided I needed a home file server about three years ago. I googled my file server education, decided that what I needed was ZFS. I found Opensolaris, jumped in, got the system running, then Oracle pulled their little 'in your face' on the world. Stewed for a while, found FreeNAS. Looked great, as what I really wanted was a NAS, not a world-server-savior. Found that version 7 was just shy of my needs, but that 8.x would be it. So I waited and watched as bits I needed were ticked off the releases. 8.0 was close, but

8.3 is it. The install and management were a breeze - barring that I still need to self-educate on what in the devil rsync is really doing - and are easily within the reach of the modestly computer literate person.

Again, thank you. I worked on and managed OS development for a while, and I know how much work not only the coding but the testing is. I am very grateful.
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,526
So does anyone want to clarify on what's changed with 8.3.0-p1? I noticed that 3 days ago that a new version of 8.3.0 was posted but I cannot find any release notes or anything even acknowledging that a new version has been released.
 

Stephens

Patron
Joined
Jun 19, 2012
Messages
496
They've said before new releases can show up before they're officially released and that we should hold off until the announcement. We'll get the announcement soon, at which point the release notes will be available.
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,526
Oops. I'll be quiet now.

/goes to the corner
 
Status
Not open for further replies.

Similar threads

Top