This is the old XigmaNAS forum in read only mode,
it will taken offline by the end of march 2021!
I like to aks Users and Admins to rewrite/take over important post from here into the new fresh main forum!
Its not possible for us to export from here and import it to the main forum!
it will taken offline by the end of march 2021!
I like to aks Users and Admins to rewrite/take over important post from here into the new fresh main forum!
Its not possible for us to export from here and import it to the main forum!
NAS4Free 10.3.0.3.2964 released (FreeBSD 10.3-RELEASE-P7)
- zoon01
- Developer

- Posts: 724
- Joined: 20 Jun 2012 21:06
- Location: Netherlands
- Contact:
- Status: Offline
NAS4Free 10.3.0.3.2964 released (FreeBSD 10.3-RELEASE-P7)
The NAS4Free Team is pleased to announce the release of version 10.3.0.3.2964.
http://sourceforge.net/projects/nas4fre ... .0.3.2964/
Everyone can upgrade from NAS4Free version 9.3.0.2.1310 or Higher.
Please read the README.
BUILD 10.3.0.3.2964
=================
Changes after release 10.3.0.3.2942:
- Update translations.
- Add zfs snapshot rollback feature.
- Add zpool import using gpt labels / gpt id.
- Upgrade inadyn-mt to 02.28.07.
- Upgrade nano to 2.7.0.
- Upgrade e2fsprogs to 1.43.3.
- Upgrade virtualbox-ose to 5.1.6.
- Upgrade netatalk to 3.1.10.
- Upgrade php to 7.0.11.
- Upgrade sudo to 1.8.18.
- Upgrade syncthing to 0.14.7.
Regards,
The NAS4Free Team
http://sourceforge.net/projects/nas4fre ... .0.3.2964/
Everyone can upgrade from NAS4Free version 9.3.0.2.1310 or Higher.
Please read the README.
BUILD 10.3.0.3.2964
=================
Changes after release 10.3.0.3.2942:
- Update translations.
- Add zfs snapshot rollback feature.
- Add zpool import using gpt labels / gpt id.
- Upgrade inadyn-mt to 02.28.07.
- Upgrade nano to 2.7.0.
- Upgrade e2fsprogs to 1.43.3.
- Upgrade virtualbox-ose to 5.1.6.
- Upgrade netatalk to 3.1.10.
- Upgrade php to 7.0.11.
- Upgrade sudo to 1.8.18.
- Upgrade syncthing to 0.14.7.
Regards,
The NAS4Free Team
System specs: XigmaNAS 11.2.0.4 -embedded on Samsung 860 EVO 256GB and Supermicro X10SL7-F w / Bios v3.2, IPMI v.03.86 / CPU E3-1241 v3 @ 3.50GHz - 32GB Crucial DDR3L 1600mhz ECC 1.35v , LSI 2308 on PH20.00.07.00 IT mode, Storage: 5x Western Digital Red (WD30EFRX) raidz
Development system is same system in virtualbox.
Development system is same system in virtualbox.
-
octave
- experienced User

- Posts: 123
- Joined: 30 Sep 2013 12:37
- Status: Offline
Re: NAS4Free 10.3.0.3.2964 released (FreeBSD 10.3-RELEASE-P7)
update since last NAS4Free 10.3.0.3 (2942) on cluster is ok, but juste a litle problem with hast/carp/iscsi, the latence is so longer to switch master node to slave
Project
Cluster Pfsense (end)
Cluster ESXI /Hyperv (standby)
Cluster NAS/SAN (in project)
---
2x Dell Poweredge C6100
2x SuperMicro X8dth-i (NAS/SAN Build) ISCSI
Cluster Pfsense (end)
Cluster ESXI /Hyperv (standby)
Cluster NAS/SAN (in project)
---
2x Dell Poweredge C6100
2x SuperMicro X8dth-i (NAS/SAN Build) ISCSI
- lindsay
- Forum Moderator

- Posts: 282
- Joined: 23 Jun 2012 09:59
- Location: Steinkjer,Norway
- Status: Offline
Re: NAS4Free 10.3.0.3.2964 released (FreeBSD 10.3-RELEASE-P7)
The upgrade went smooth, did make a backup of the configs this time.
Did not need them this time.
Did not need them this time.
Protected by smoothiebox Red,Green,
Purple,Orange Zones/VLAN`s
Powered by AMD A10-6700T
XigmaNAS Box-1 11.2.0.4 - Omnius (revision 6625)
Platform : x64-embedded on 2X Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
Motherboard: ASUS Z10PA-D8, 2xSocket-2011-3
SATA Controllers : 1X Avago Technologies (LSI) SAS2008 and 1x Avago Technologies (LSI) SAS2308
Pool 1 (Media-Pool) 8X4TB in raidz2
Pool 2 (Media-Pool-2) 4X2TB in raidz2 and 2X2TB in mirror mirror and 2X3TB in mirror
Pool 3 (Media-Pool-3) 2X2TB in mirror and 2X4TB in mirror and 2X1TB in mirror
Purple,Orange Zones/VLAN`s
Powered by AMD A10-6700T
XigmaNAS Box-1 11.2.0.4 - Omnius (revision 6625)
Platform : x64-embedded on 2X Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
Motherboard: ASUS Z10PA-D8, 2xSocket-2011-3
SATA Controllers : 1X Avago Technologies (LSI) SAS2008 and 1x Avago Technologies (LSI) SAS2308
Pool 1 (Media-Pool) 8X4TB in raidz2
Pool 2 (Media-Pool-2) 4X2TB in raidz2 and 2X2TB in mirror mirror and 2X3TB in mirror
Pool 3 (Media-Pool-3) 2X2TB in mirror and 2X4TB in mirror and 2X1TB in mirror
- F8BOE
- experienced User

- Posts: 106
- Joined: 03 Jun 2013 23:09
- Location: France
- Status: Offline
Re: NAS4Free 10.3.0.3.2964 released (FreeBSD 10.3-RELEASE-P7)
Hello,
All went smooth here on my old PII, it still runs rock solid!
Ciao @+
All went smooth here on my old PII, it still runs rock solid!
Ciao @+
-
pkatruss
- NewUser

- Posts: 3
- Joined: 20 Sep 2015 16:22
- Status: Offline
Re: NAS4Free 10.3.0.3.2964 released (FreeBSD 10.3-RELEASE-P7)
I tried to create a Dataset and noticed that the GUI now limits the name to 20 characters. I had originally created all my Datasets back when I was running 9.2.0.1 (972).
The longest name I had created then was "DataBase/PlexMediaServer". The Dataset works OK with this name even after upgrading to 10.3.0.3 (2870). However, when I try to create a Dataset with this name under 10.3.0.3 (2964), as well as under (2870) the GUI limits me to "DataBase/PlexMediaSe".
According to the FreeBSD Man Pages a Dataset name can be 256 characters. I cannot find any explanation why the 20 character limit. If anyone can enlighten me I would be grateful.
Peter.
The longest name I had created then was "DataBase/PlexMediaServer". The Dataset works OK with this name even after upgrading to 10.3.0.3 (2870). However, when I try to create a Dataset with this name under 10.3.0.3 (2964), as well as under (2870) the GUI limits me to "DataBase/PlexMediaSe".
According to the FreeBSD Man Pages a Dataset name can be 256 characters. I cannot find any explanation why the 20 character limit. If anyone can enlighten me I would be grateful.
Peter.
-
jack47
- Starter

- Posts: 35
- Joined: 20 Jul 2013 09:27
- Status: Offline
Re: NAS4Free 10.3.0.3.2964 released (FreeBSD 10.3-RELEASE-P7)
How about this?
https://sourceforge.net/p/nas4free/bugs/300/
I haven't time to try.
Best Regards
Jack
https://sourceforge.net/p/nas4free/bugs/300/
I haven't time to try.
Best Regards
Jack
- ms49434
- Developer

- Posts: 828
- Joined: 03 Sep 2015 18:49
- Location: Neuenkirchen-Vörden, Germany - GMT+1
- Contact:
- Status: Offline
Re: NAS4Free 10.3.0.3.2964 released (FreeBSD 10.3-RELEASE-P7)
The length of a zfs dataset name or a zfs volume name was always limited to 20 characters in the WebGUI.pkatruss wrote:I tried to create a Dataset and noticed that the GUI now limits the name to 20 characters. I had originally created all my Datasets back when I was running 9.2.0.1 (972).
The longest name I had created then was "DataBase/PlexMediaServer". The Dataset works OK with this name even after upgrading to 10.3.0.3 (2870). However, when I try to create a Dataset with this name under 10.3.0.3 (2964), as well as under (2870) the GUI limits me to "DataBase/PlexMediaSe".
According to the FreeBSD Man Pages a Dataset name can be 256 characters. I cannot find any explanation why the 20 character limit. If anyone can enlighten me I would be grateful.
Peter.
The next release will allow up to 40 characters.
1) XigmaNAS 12.1.0.4 amd64-embedded on a Dell T20 running in a VM on ESXi 6.7U3, 22GB out of 32GB ECC RAM, LSI 9300-8i IT mode in passthrough mode. Pool 1: 2x HGST 10TB, mirrored, L2ARC: Samsung 850 Pro; Pool 2: 1x Samsung 860 EVO 1TB, SLOG: Samsung SM883, services: Samba AD, CIFS/SMB, ftp, ctld, rsync, syncthing, zfs snapshots.
2) XigmaNAS 12.1.0.4 amd64-embedded on a Dell T20 running in a VM on ESXi 6.7U3, 8GB out of 32GB ECC RAM, IBM M1215 crossflashed, IT mode, passthrough mode, 2x HGST 10TB , services: rsync.
2) XigmaNAS 12.1.0.4 amd64-embedded on a Dell T20 running in a VM on ESXi 6.7U3, 8GB out of 32GB ECC RAM, IBM M1215 crossflashed, IT mode, passthrough mode, 2x HGST 10TB , services: rsync.
-
pkatruss
- NewUser

- Posts: 3
- Joined: 20 Sep 2015 16:22
- Status: Offline
Re: NAS4Free 10.3.0.3.2964 released (FreeBSD 10.3-RELEASE-P7)
I still have a system running Nas4Free 9.2.0.1 (972). I was able to create a Dataset name with 63 characters using the web interface. The characters scrolled left when entering more characters than the window size (24 characters). I also was able to scroll left and right using the left and right arrow keys.ms49434 wrote:The length of a zfs dataset name or a zfs volume name was always limited to 20 characters in the WebGUI.pkatruss wrote:I tried to create a Dataset and noticed that the GUI now limits the name to 20 characters. I had originally created all my Datasets back when I was running 9.2.0.1 (972).
The longest name I had created then was "DataBase/PlexMediaServer". The Dataset works OK with this name even after upgrading to 10.3.0.3 (2870). However, when I try to create a Dataset with this name under 10.3.0.3 (2964), as well as under (2870) the GUI limits me to "DataBase/PlexMediaSe".
According to the FreeBSD Man Pages a Dataset name can be 256 characters. I cannot find any explanation why the 20 character limit. If anyone can enlighten me I would be grateful.
Peter.
The next release will allow up to 40 characters.
For example when I enter "ThisIsAtestDataSetName0123456789" the windows show "ThisIsAtestDataSetName01" before scrolling starts. When I finished typing in all the characters I only see the last 24 characters in the windows "stDataSetName0123456789". As I said I can use the left and right arrow keys to review the full name.
Would it be possible to have this scrolling functionality back?
-
provels
- experienced User

- Posts: 108
- Joined: 05 Jan 2014 15:31
- Location: Chicago, IL, USA
- Status: Offline
Re: NAS4Free 10.3.0.3.2964 released (FreeBSD 10.3-RELEASE-P7)
Upgrade went fine on my simple setup. MiniDLNA and CIFS/SMB only.
Peder
XigmaNAS 11.4.0.4.7718 Embedded / MiniDLNA and CIFS/SMB only
HP ProLiant DL320 G3 / P4 660 3.6GHz HT / 4GB ECC / 2 x 3TB WD Red, ZFS Mirror / APC Back-UPS BR 800
XigmaNAS 11.4.0.4.7718 Embedded / MiniDLNA and CIFS/SMB only
HP ProLiant DL320 G3 / P4 660 3.6GHz HT / 4GB ECC / 2 x 3TB WD Red, ZFS Mirror / APC Back-UPS BR 800
- alexey123
- Moderator

- Posts: 1469
- Joined: 19 Aug 2012 08:22
- Location: Israel, Karmiel
- Contact:
- Status: Offline
Re: NAS4Free 10.3.0.3.2964 released (FreeBSD 10.3-RELEASE-P7)
I begin to build new hardware and see first simple fault with temperature sensor

Themporary solve problem - add to loader config (Check bios temperature monitor)

Themporary solve problem - add to loader config (Check bios temperature monitor)
Code: Select all
dev.amdtemp.0.sensor_offset=42Home12.1.0.4 - Ingva (revision 7091)/ x64-embedded on AMD A8-7600 Radeon R7 A88XM-PLUS/ 16G RAM / UPS Ippon Back Power Pro 600
Lab 12.1.0.4 - Ingva (revision 7091) /x64-embedded on Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz / H61M-DS2 / 4G RAM / UPS Ippon Back Power Pro 600
Lab 12.1.0.4 - Ingva (revision 7091) /x64-embedded on Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz / H61M-DS2 / 4G RAM / UPS Ippon Back Power Pro 600
-
provels
- experienced User

- Posts: 108
- Joined: 05 Jan 2014 15:31
- Location: Chicago, IL, USA
- Status: Offline
Re: NAS4Free 10.3.0.3.2964 released (FreeBSD 10.3-RELEASE-P7)
Mine has same problem, shows 8.3 C, but always has been that way. I thought probably a chipset incompatibility.
The server is a P4, about 13 years old.
The server is a P4, about 13 years old.
You do not have the required permissions to view the files attached to this post.
Peder
XigmaNAS 11.4.0.4.7718 Embedded / MiniDLNA and CIFS/SMB only
HP ProLiant DL320 G3 / P4 660 3.6GHz HT / 4GB ECC / 2 x 3TB WD Red, ZFS Mirror / APC Back-UPS BR 800
XigmaNAS 11.4.0.4.7718 Embedded / MiniDLNA and CIFS/SMB only
HP ProLiant DL320 G3 / P4 660 3.6GHz HT / 4GB ECC / 2 x 3TB WD Red, ZFS Mirror / APC Back-UPS BR 800
-
NAS4Free4Me
- NewUser

- Posts: 14
- Joined: 27 Nov 2012 11:19
- Status: Offline
Re: NAS4Free 10.3.0.3.2964 released (FreeBSD 10.3-RELEASE-P7)
Hi:
Not seeing that on my current system configuration:
M/B: ASUSTeK COMPUTER INC. H87M-E
CPU: x64-embedded on Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz
F/W: American Megatrends Inc. version: 2103 04/14/2015
What I'd really like to see is the F Temp in parenthesis (IE: CPU Temp: 41 C (105.8 F). I mean how hard could it be to program that in to the System Info screen on the same line for each CPU core? Not trying to be super critical, just my .02 worth.
Not seeing that on my current system configuration:
M/B: ASUSTeK COMPUTER INC. H87M-E
CPU: x64-embedded on Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz
F/W: American Megatrends Inc. version: 2103 04/14/2015
What I'd really like to see is the F Temp in parenthesis (IE: CPU Temp: 41 C (105.8 F). I mean how hard could it be to program that in to the System Info screen on the same line for each CPU core? Not trying to be super critical, just my .02 worth.
NAS-A = MB: Asus H87M-E, CPU: Intel i5-4590 CPU @ 3.30GHz, RAM: 16GB, HDD: ZFS-R1 / 3.0 TB (x5) Seagate Barracuda 7200.14 (AF)
- darioml
- Starter

- Posts: 33
- Joined: 08 Feb 2016 20:09
- Status: Offline
Re: NAS4Free 10.3.0.3.2964 released (FreeBSD 10.3-RELEASE-P7)
Hi.
Last night, I updated my N3150-itx server from embedded (usb) 2942, but it didn't go well at first.
On the screen, I could see that the firmware had (supposedly) been updated, but it said that the system had halted and asked me to turn the system off and on. Well, I thought that it was going to reboot itself automatically... Strange. So, I got scared...
After turning it on, a FreeBSD prompt appeared and said that no boot loader was found... no kernel... Nothing...
I had to download the Live-CD iso of N4F, install it on the pendrive by using VM (after some problems to make it GPT since the N4F installer could not make it automatically), connect the pendrive, boot the server up and restore the settings through the GUI.
After more than 2 hours (yes, next time it happens, I intend to make it much shorter), I had finally my server up and running with this new 2964 release.
Still, I don't know what went wrong during the process of updating the pendrive during the normal process from the GUI...
Cheers!
Last night, I updated my N3150-itx server from embedded (usb) 2942, but it didn't go well at first.
On the screen, I could see that the firmware had (supposedly) been updated, but it said that the system had halted and asked me to turn the system off and on. Well, I thought that it was going to reboot itself automatically... Strange. So, I got scared...
After turning it on, a FreeBSD prompt appeared and said that no boot loader was found... no kernel... Nothing...
I had to download the Live-CD iso of N4F, install it on the pendrive by using VM (after some problems to make it GPT since the N4F installer could not make it automatically), connect the pendrive, boot the server up and restore the settings through the GUI.
After more than 2 hours (yes, next time it happens, I intend to make it much shorter), I had finally my server up and running with this new 2964 release.
Still, I don't know what went wrong during the process of updating the pendrive during the normal process from the GUI...
Cheers!
- HenriM
- Starter

- Posts: 56
- Joined: 15 Jun 2013 12:17
- Location: Rijsbergen, The Netherlands
- Contact:
- Status: Offline
Re: NAS4Free 10.3.0.3.2964 released (FreeBSD 10.3-RELEASE-P7)
Did you had 'Extended GUI' enabled when upgrading? My experience is to disable it always before upgrading your firmware, otherwise you can run into these kind of issues.
- darioml
- Starter

- Posts: 33
- Joined: 08 Feb 2016 20:09
- Status: Offline
Re: NAS4Free 10.3.0.3.2964 released (FreeBSD 10.3-RELEASE-P7)
It was enabled... Last time, I lost the configuration, but I can live with it. But... losing completely the capacity of booting... it's too much trouble.
- ChriZathens
- Forum Moderator

- Posts: 758
- Joined: 23 Jun 2012 09:14
- Location: Athens, Greece
- Contact:
- Status: Offline
Re: NAS4Free 10.3.0.3.2964 released (FreeBSD 10.3-RELEASE-P7)
I doubt egui would cause such an issue.
Most probably your pen drive got crapped somehow.
Most probably your pen drive got crapped somehow.
My Nas
Backup Nas: U-NAS NSC-400, Gigabyte MB10-DS4 (4x4TB Seagate Exos disks in RaidZ configuration - 32GB RAM)
- Case: Fractal Design Define R2
- M/B: Supermicro x9scl-f
- CPU: Intel Celeron G1620
- RAM: 16GB DDR3 ECC (2 x Kingston KVR1333D3E9S/8G)
- PSU: Chieftec 850w 80+ modular
- Storage: 8x2TB HDDs in a RaidZ2 array ~ 10.1 TB usable disk space
- O/S: XigmaNAS 11.2.0.4.6625 -amd64 embedded
- Extra H/W: Dell Perc H310 SAS controller, crosflashed to LSI 9211-8i IT mode, 8GB Innodisk D150SV SATADOM for O/S
Backup Nas: U-NAS NSC-400, Gigabyte MB10-DS4 (4x4TB Seagate Exos disks in RaidZ configuration - 32GB RAM)
- darioml
- Starter

- Posts: 33
- Joined: 08 Feb 2016 20:09
- Status: Offline
Re: RE: Re: NAS4Free 10.3.0.3.2964 released (FreeBSD 10.3-RELEASE-P7)
Well, I hope that it isn't... I got a SanDisk SDCZ80-016G-FFP for it. It's said it is the best in speed (specially in small files) and durability. I hope it doesn't break down in only 9 monthsChriZathens wrote:I doubt egui would cause such an issue.
Most probably your pen drive got crapped somehow.

- HenriM
- Starter

- Posts: 56
- Joined: 15 Jun 2013 12:17
- Location: Rijsbergen, The Netherlands
- Contact:
- Status: Offline
Re: NAS4Free 10.3.0.3.2964 released (FreeBSD 10.3-RELEASE-P7)
I had this issue 3 times with previous updates when Extended GUI was turned on. Firmware update with GUI went OK, but after reboot there was not bootable disk and I had to use the LIVE CD to recover from it. After that time I always disable Extended GUI first before I updating my firmware with the GUI. Since that time no issues anymore. Coincidence? Perhaps, but for me it now always went fine when disabling Extended GUI first.
- ChriZathens
- Forum Moderator

- Posts: 758
- Joined: 23 Jun 2012 09:14
- Location: Athens, Greece
- Contact:
- Status: Offline
Re: NAS4Free 10.3.0.3.2964 released (FreeBSD 10.3-RELEASE-P7)
In this case, then, it is no coinsidence...
I think you should bring this to crest's attention, if you haven't done it already.
I think you should bring this to crest's attention, if you haven't done it already.
My Nas
Backup Nas: U-NAS NSC-400, Gigabyte MB10-DS4 (4x4TB Seagate Exos disks in RaidZ configuration - 32GB RAM)
- Case: Fractal Design Define R2
- M/B: Supermicro x9scl-f
- CPU: Intel Celeron G1620
- RAM: 16GB DDR3 ECC (2 x Kingston KVR1333D3E9S/8G)
- PSU: Chieftec 850w 80+ modular
- Storage: 8x2TB HDDs in a RaidZ2 array ~ 10.1 TB usable disk space
- O/S: XigmaNAS 11.2.0.4.6625 -amd64 embedded
- Extra H/W: Dell Perc H310 SAS controller, crosflashed to LSI 9211-8i IT mode, 8GB Innodisk D150SV SATADOM for O/S
Backup Nas: U-NAS NSC-400, Gigabyte MB10-DS4 (4x4TB Seagate Exos disks in RaidZ configuration - 32GB RAM)
-
octave
- experienced User

- Posts: 123
- Joined: 30 Sep 2013 12:37
- Status: Offline
Re: NAS4Free 10.3.0.3.2964 released (FreeBSD 10.3-RELEASE-P7)
Hi all
i replaced all realteck nic 8111/8169/8168/8411 by intel pro nic 1gb because they was instable with carp and or lagg solution.
all realteck nic are new, and i see this problem on linux distribution too.
so i don't think that realy the fact of nas4free or any bsd solution.
thx for build job
i replaced all realteck nic 8111/8169/8168/8411 by intel pro nic 1gb because they was instable with carp and or lagg solution.
all realteck nic are new, and i see this problem on linux distribution too.
so i don't think that realy the fact of nas4free or any bsd solution.
thx for build job
Project
Cluster Pfsense (end)
Cluster ESXI /Hyperv (standby)
Cluster NAS/SAN (in project)
---
2x Dell Poweredge C6100
2x SuperMicro X8dth-i (NAS/SAN Build) ISCSI
Cluster Pfsense (end)
Cluster ESXI /Hyperv (standby)
Cluster NAS/SAN (in project)
---
2x Dell Poweredge C6100
2x SuperMicro X8dth-i (NAS/SAN Build) ISCSI
-
danzi
- Starter

- Posts: 66
- Joined: 11 Nov 2012 23:24
- Location: Budapest
- Status: Offline
Re: NAS4Free 10.3.0.3.2964 released (FreeBSD 10.3-RELEASE-P7)
Guys, have this badboy up since about a week, but phpVirtualBox errors out with
The virtual machine 'win7' has terminated unexpectedly during startup with exit code 1 (0x1)
No matter what OS I try to run. Also remote display VNC tab is greyed out. Is there any tricks to get vm up and running?
The virtual machine 'win7' has terminated unexpectedly during startup with exit code 1 (0x1)
No matter what OS I try to run. Also remote display VNC tab is greyed out. Is there any tricks to get vm up and running?
----------------------------------------------
Dell T130 - 32Gb ECC - ESXi 6.7
VM Full Instal - 11.2.0.4 - Omnius (revision 6005)
HP/LSI 9121-4i SAS2008 Pass Through mode
2 x 2Tb ZFS mirror
1 x 3Tb UFS
----------------------------------------------
Dell T130 - 32Gb ECC - ESXi 6.7
VM Full Instal - 11.2.0.4 - Omnius (revision 6005)
HP/LSI 9121-4i SAS2008 Pass Through mode
2 x 2Tb ZFS mirror
1 x 3Tb UFS
----------------------------------------------