Current FreeBSD versions will allow you to create a zroot zpool from which you can boot. However, when I created the main zpool for slocum (on Fri May 3 2:16 2013), that option did not exist. You might ask: how do I know that date? [dan@slocum:~] $ zfs get creation system NAME PROPERTY VALUE SOURCE system creation Fri May 3 2:16 2013 – At present, the system boots from a raidz2 zpool. This […]
Adding a zroot pool to an existing system Read More »
This post has been replaced by a newer one. For reference, the previous post on this server is still available. The most recent change was extracting the beadm boot environment to a new zpool, zroot. For future reference, this is the slocum server, which I use for various jails and services. It is mounted in the 4U chassis mentioned in this post The filesystems, well, some of them: And dmesg:
I have added comments to the output of this command. This is a brief description of what runs in each jail. This post has been replaced by a newer one. slocum slocum – named for the first person to sail solo around the world This host also runs a DNS and DHCP. [dan@slocum:~] $ jls -v | grep ACTIVE | cut -f 2 -w | sort bacula – runs bacula-dir, main component for
What runs on the servers at home? Read More »
This is x8dtu (named after the SuperMicro motherboard). This is the new FreshPorts server. The older post is still available In short: FreeBSD 11.2 booting off a mirrored pair of zfsroot SSDs 4.5TB of mirrored ZFS 196612 MB of RAM (yeah, that’s 196GB of RAM) SuperMicro X8DTU motherboard Intel Xeon E5620 @ 2.40GHz (two of those, giving 16 CPUs) NOTE: this post replaces
This post has been replaced by a newer post. This is the previous post for this system configuration. For future reference, this is the knew server … oh wait, I think it’s this server which is was mounted in the 3U chassis mentioned in this post (perviously erroneously referred to as a 4U). It runs a few jails, including Bacula regression testing services. It is now mounted in a SuperChassis 846E16-R1200B This recent
This server, knew has had an intermittent problem related to CAM status: SCSI Status Error messages. There is a FreeBSD Forums post about it. On Sunday, the problem returned, and this time it degraded the zpool. I collected the information in this gist and I will list the relevant portions below. I had enabled smartd testing and I received this email late on Sunday: Despite the promise of more information in the logs,
zpool: FAULTED – too many errors Read More »
NOTE: I am not convinced of the value of doing these tests on a regular basis. smartd and smartctl are two utility programs included with the smartmontools package. On FreeBSD, smartmontools is installed via the sysutils/smartmontools port. Those programs can “control and monitor storage systems using the Self-Monitoring, Analysis and Reporting Technology System (SMART) built into most modern ATA/SATA, SCSI/SAS and NVMe disks. In many cases, these utilities will provide advanced warning of
using smartd to automatically run tests on your drives Read More »
On Monday night at about 5:30 PM, I noticed the email: ** PROBLEM alert – knew/zpool is CRITICAL ** What sickened me was that the email was sent at 3:58 PM. That makes me think I should add a Pushover.net alert …. I could do that at my mail server. Logging into the server, I saw: [dan@knew:~] $ zpool list NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT system 90.5T
bhyve is a hypervisor/virtual machine manager developed on FreeBSD. xhyve is port of bhyve to OS X. It is built on top of Hypervisor.framework in OS X 10.10 Yosemite and higher, runs entirely in userspace, and has no other dependencies. I usually use MacPorts, but ran into trouble with xhyve, so this morning I tried Homebrew instead. Installing Homebew (often referred to as brew) is outside scope, so please refer to their documentation.
Running FreeBSD on OSX using xhyve, a port of bhyve Read More »
This problem was difficult to figure out. The cause was simple, but not obvious. Messages such as this were appearing in emails From July: In August: I had no idea why. My initial suspicion was the /etc/newsyslog.conf configuration for that file: [dan@knew:~] $ grep auth /etc/newsyslog.conf /var/log/auth.log root:logcheck 640 7 * @T00 JC [dan@knew:~] $ That count is 7, so why is it complaining about 6? The files look ok: [dan@knew:~] $ ls
newsyslog: chmod(/var/log/auth.log.6.bz2) in change_attrs: No such file or directory Read More »