Cool, yeah these drives take about 12 hours for a long test.
Yikes!
No guarantees. Personally, I am staying with my Warden Jail I am using (Plex) until the IOcage Jails are ready for "prime time". Then I will make the move.
My initial choices were based on a lot of reading (the guide on this forum for example). I bought the things that were needed to run FreeNAS as a file server only. When I decided that I wanted to switch to ESXi I expanded my memory to the max and upgraded my CPU from an i3 to a Xeon.
I expect the CPU I have to be sufficent for what I want to do with it. I will run FreeNAS on it and at its most three other VM's. I have no plans for things like a media server.
How did this come out? Are you going to share some progress photos?
Just a matter of opinion, but I wouldn't want to use it very extensively as a hypervisor because I don't want to risk impacting the performance of my storage by burdening the same system with too many other tasks.
I wouldn't trust myself to give you advice good advice ;) For me the 8tb disks were largely impulse purchases that had ostensibly good value. I bought about 8x 2tb WD Red drives in 2014, and the first one just failed a few days ago, so I'd say I'm happy enough with the perceived quality of WD Red drives.
Yeah :( That's a very good point, and I've already seen how the Rsync backups max out all 24gigs of ram on this FreeNAS box. But the temptation of consolidation is pretty big for me. I'm really torn about it.
Well, the Precision T7500 can be maxed out to around 192GB of RAM and dual 6 core 3.4 GHz processors, so you have some room to grow.
The price of the shucked WD 8TB drives is about as good as you can get and the cost to operate (cost of electricity per GB of storage) is about as good as you can get too.
All the drives in a single vdev of a pool should be the same size because you can only use the amount of space on each drive that is equal to the smallest drive.
The set of drives I replaced around the middle of last year had been in continuous operation for a little over 5 years. I have 2 vdevs in my main pool I replaced all 12 drives (6 in each vdev) last year. In 2016, I had replaced all the drives in vdev-0 because they had reached the 5 year limit where I had originally planned to replace them. Unfortunately I replaced them with Toshiba 2TB drives simply because the Toshiba drives were inexpensive. I had 3 of those drives fail within the first six months of operation and for that reason I became concerned that they would not hold up in the long term. In 2017, I replaced the six drives in vdev-1 (they had been 2TB drives) with 4TB drives to expand the capacity of the pool. I selected Seagate Barracuda drives for this pool expansion and after six months I have had no issues with them. None at all. I got a little lost there. It is late.
I am seriously considering moving my pool to 8TB drives for the lower energy use. The comparisons I have done make me think that that is the way to go. The biggest reason I have my pool in the configuration it is in, is the speed of access. More vdevs give more IOPS and more IOPS generally equates to faster access, especially when looking at a bunch of small files.
ARC (Adaptive Replacement Cache) will use all available memory if you don't limit it with a tunable. If you want to run VMs, go for it, but you do need to adjust the default settings to make set aside some memory and you might want to add more memory depending on how much you want to do with VMs. I use a T7500 at work to run VMs and I can run 8 Windows VMs in that thing with no trouble using Windows server as the host (with Hyper-v) and having some of the VMs being additional Windows Server instances or Windows 10 instances.
I'm still working out the details. Initially I wanted to have the ReadyNAS become a backup for the most important files on the FreeNAS box, but I feel like that'd be a mess to maintain with how much I dislike the ReadyNAS. Now I'm considering giving the ReadyNAS to a family member to use.
Feels like I'm not proficient enough with FreeBSD yet to tackle the required troubleshooting to get things up and running.
pkg alright, but then wouldn't run. Eventually I found that I needed to put allow.sysvipc=true in the Sysctls box of the jail configuration dialog. And then I couldn't import my old databases, apparently the postgresql package was compiled for 11.1 and wanted a function that wasn't available. ALLOW_UNSUPPORTED_SYSTEM=yes to /etc/make.conf for the time being. That seems to work, but I've run out of time and will have to come back and set up the database and webserver.
Error 22:rrdtool failed: ERROR: opening '/var/db/collectd/rrd/localhost//aggregation-cpu-sum/cpu-user.rrd': No such file or directory
Traceback (most recent call last):
File "/usr/local/lib/python3.6/site-packages/middlewared/main.py", line 150, in call_method
result = await self.middleware.call_method(self, message)
File "/usr/local/lib/python3.6/asyncio/coroutines.py", line 109, in __next__
return self.gen.send(None)
File "/usr/local/lib/python3.6/site-packages/middlewared/main.py", line 908, in call_method
return await self._call(message['method'], serviceobj, methodobj, params, app=app)
File "/usr/local/lib/python3.6/asyncio/coroutines.py", line 109, in __next__
return self.gen.send(None)
File "/usr/local/lib/python3.6/site-packages/middlewared/main.py", line 876, in _call
return await methodobj(*args)
File "/usr/local/lib/python3.6/asyncio/coroutines.py", line 109, in __next__
return self.gen.send(None)
File "/usr/local/lib/python3.6/site-packages/middlewared/schema.py", line 491, in nf
return await f(*args, **kwargs)
File "/usr/local/lib/python3.6/asyncio/coroutines.py", line 109, in __next__
return self.gen.send(None)
File "/usr/local/lib/python3.6/site-packages/middlewared/plugins/stats.py", line 111, in get_data
raise ValueError('rrdtool failed: {}'.format(err.decode()))
ValueError: rrdtool failed: ERROR: opening '/var/db/collectd/rrd/localhost//aggregation-cpu-sum/cpu-user.rrd': No such file or directory
Error 201:[ENOMETHOD] Method "summary" not found in "network.general"
Traceback (most recent call last):
File "/usr/local/lib/python3.6/site-packages/middlewared/main.py", line 893, in _method_lookup
serviceobj = self.get_service(service)
File "/usr/local/lib/python3.6/site-packages/middlewared/main.py", line 822, in get_service
return self.__services[name]
KeyError: 'network.general'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.6/site-packages/middlewared/main.py", line 150, in call_method
result = await self.middleware.call_method(self, message)
File "/usr/local/lib/python3.6/asyncio/coroutines.py", line 109, in __next__
return self.gen.send(None)
File "/usr/local/lib/python3.6/site-packages/middlewared/main.py", line 902, in call_method
serviceobj, methodobj = self._method_lookup(message['method'])
File "/usr/local/lib/python3.6/site-packages/middlewared/main.py", line 896, in _method_lookup
raise CallError(f'Method "{method_name}" not found in "{service}"', CallError.ENOMETHOD)
middlewared.service_exception.CallError: [ENOMETHOD] Method "summary" not found in "network.general"
