2015

CAM status: ATA Status Error READ_DMA48 Error 5, Retries exhausted

This turned up this morning: Aug 5 05:10:04 knew kernel: (ada0:ata0:0:0:0): READ_DMA48. ACB: 25 00 d0 c4 6e 40 57 00 00 00 60 00 Aug 5 05:10:04 knew kernel: (ada0:ata0:0:0:0): CAM status: ATA Status Error Aug 5 05:10:04 knew kernel: (ada0:ata0:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 40 (UNC ) Aug 5 05:10:04 […]

CAM status: ATA Status Error READ_DMA48 Error 5, Retries exhausted Read More »

smartd: ATA error count increased from 0 to 1

I noticed this in /var/log/messages today: Jul 30 13:25:21 knew kernel: (ada0:ata0:0:0:0): READ_DMA48. ACB: 25 00 b0 51 95 40 68 00 00 00 40 00 Jul 30 13:25:21 knew kernel: (ada0:ata0:0:0:0): CAM status: ATA Status Error Jul 30 13:25:21 knew kernel: (ada0:ata0:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 40 (UNC ) Jul 30

smartd: ATA error count increased from 0 to 1 Read More »

smartd: Device: 8 Currently unreadable (pending) sectors

I noticed these messages this morning, on the new server: $ grep smartd /var/log/messages Jul 25 11:35:29 varm smartd[813]: Device: /dev/da15 [SAT], 8 Currently unreadable (pending) sectors Jul 25 11:35:29 varm smartd[813]: Device: /dev/da15 [SAT], 10 Offline uncorrectable sectors Jul 25 12:05:28 varm smartd[813]: Device: /dev/da15 [SAT], 8 Currently unreadable (pending) sectors Jul 25 12:35:29

smartd: Device: 8 Currently unreadable (pending) sectors Read More »

Nagios check_ntp_time failed with ntpd on FreeBSD 10.2

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

Nagios check_ntp_time failed with ntpd on FreeBSD 10.2 Read More »

Configuring unbound on FreeBSD 10.x

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

Configuring unbound on FreeBSD 10.x Read More »

Scroll to Top