I’m using FreeBSD 10.2-RC2. One of my new hard 3TB drives was acting up. I removed it and sent it off to be replaced. In the meantime, I received some 5TB drives and I added one of them into the existing vdev of the zpool. First, I partitioned the drive much like the other drives in the system. In my case, this was: $ sudo gpart create -s gpt da0 da0 created $ […]
Replacing a failed drive in ZFS on FreeBSD Read More »
I took delivery of another 10 x Toshiba PH3500U-1I72 5TB drives yesterday. They are installed into the latest server (varm). This sever also contains 10x Toshiba DT01ACA300 3TB drives. Last night I wrote a wee script to start long tests on each of them. I was able to extract a list of the hard drives through this command: I suspect I could have done similar with ls /dev/da*. With the above list, I
smartctl -t long /dev/allthedrives Read More »
As I was setting up the new varm server, one of the Nagios checks I included was check_ntp_time. It comes standard with nagios-plugins. The check was reporting NTP CRITICAL: Offset unknown. Running the check from the command line showed: [dan@webserver:/usr/local/libexec/nagios] $ ./check_ntp_time -4 -H varm NTP CRITICAL: Offset unknown| Running the check with a timeout showed: [dan@webserver:/usr/local/libexec/nagios] $ ./check_ntp_time -4 -H varm -t 1 CRITICAL – Socket timeout after 1 seconds I checked
Nagios check_ntp_time failed with ntpd on FreeBSD 10.2 Read More »
NOTE: I found out these settings do not persist after a reboot. Annoying. I’ll get back to that soon for a fix. EDIT 2021-05-05: On more recent FreeBSD, say 12.2, to disable resolvconf.conf, do this, as provided by [dvl@r720-02:~] $ cat /etc/resolvconf.conf resolvconf=NO [dvl@r720-02:~] $ The above is documented in man 8 resolvconf.conf (search for disable). I now return you to the original article. Today I was setting up my new server, varm,
Configuring unbound on FreeBSD 10.x Read More »
World, please meet varm, the newest addition to my home lab. Some of the hardware has been described in an earlier blog post and not all of the hardware has been installed. But for the record:
While in Ottawa for BSDCan 2015 and PGCon 2015, I obtained a 4TB external USB HDD. It now contains copies of the videos back to 2012 for BSDCan and PGCon. This is for backup. All these videos exist elsewhere (e.g. Youtube) and I have these just for backup. NOTE: the videos for BSDCan 2015 and PGCon 2015 will be online as soon as they are available. There is no ETA. Here’s what it
Following on from my post about excluding the base OS with a Bacula FileSet, I decided to exclude some more. The starting point Here are the baselines: What else will I exclude? I decided to exclude the following as well: Adding iocage support Along the way, I extended the Exclude to work on server using the iocage jail management tool. I also split the Exclude out into its own file. Here is the
More Bacula Excludes with Jails and FreeBSD Read More »
I recently implemented Fail2ban on a FreeBSD jail host. It monitors log files within the jails, from the host. Offensive IP addresses which act up in one jail will be blocked at the host, thus blocking the rascal IP from all jails. This has been running for about two weeks. Today I added another tool, the WP fail2ban plugin. The plugin comes with a wordpress.local file, but to make it work with FreeBSD,
WordPress and Fail2ban Read More »
I felt I was backing up way too much on my jail server. I was backing up files which would be installed as part of the OS. Let’s look at the esimate: *estimate level=full job=”slocum jail snapshots” Using Catalog “MyCatalog” Connecting to Client slocum-fd at slocum.int.unixathome.org:9102 2000 OK estimate files=2,824,716 bytes=239,568,332,325 * I decided to add these to the FileSet: Options { Exclude = yes WildDir = “/usr/jails/*/.zfs/snapshot/basejail” WildDir = “/usr/jails/*/.zfs/snapshot/bin” WildDir =
Excluding the base-OS when backing up FreeBSD jails with Bacula Read More »
I have no idea when I wrote this. It got saved but never published, until today. I recently had the boot drive at one of my servers change. It’s really a VM on a box, but at least it’s running FreeBSD. To fix it, I got a VNC session going to their server, and was greeted by the prompt: mountroot> ? List of GEMO managed disk devices: ufsid/48ee594bdcbf83e3 ufsid/48dd594bad4c1d6f ufsif/48ee594b514a21e1 ufsid/48ee594b75a0ff85 acd0 ad1s1f
drive letters changed? Read More »