The time has come for me to move from shelving to racks. My first thought was to list the various racks over the years. Look below for old photos and links to the posts I lifted them from. Why a rack? In the past, I have always built my own servers, computers, from parts. I always chose tower cases for space and quiet. A large fan and heatsink can be easily mounted in […]
Moving from shelves to racks Read More »
Let’s try the speed test which comes with Bacula’s btape utility. This is Bacula 7.4.0 on FreeBSD 10.2, with a Dell TL4000 LTO-4 tape library.
Using Bacula’s btape speed test on FreeBSD 10.2 and an LTO-4 tape drive Read More »
For future reference, this is the knew server. It runs a few jails, including Bacula regression testing services. File systems Paritions zpools /var/run/dmesg.boot
I do have a FreeBSD-11 box, cuppy: $ uname -a FreeBSD cuppy.int.unixathome.org 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r279394: Sat Feb 28 21:01:21 UTC 2015 dan@cuppy.unixathome.org:/usr/obj/usr/src/sys/GENERIC amd64 $ That box is used mostly for testing and/or erasing DLT tapes. The current status of that box is not healthy. It’s running fine, but it is not optimal: Let’s fix this. Background Why is one drive upset? Because I installed FreeBSD onto it. Why? I don’t know,
Adding a failed HDD back into a ZFS mirror Read More »
In this post, I am working with FreeBSD 10.2 on this server. Over the past few days, a 3 year old drive has been giving errors. The number of errors has been constant, but I have a spare drive here, so I decided to replace it. I have verified that it is out of warranty. Rather than pull the error drive and replace it, I opted to add in a new drive and
Added new drive when existing one gave errors, then zpool replace Read More »
These appeared overnight: Feb 18 08:08:23 knew kernel: (ada0:ata0:0:0:0): READ_DMA48. ACB: 25 00 90 a8 f0 40 4b 00 00 00 f0 00 Feb 18 08:08:23 knew kernel: (ada0:ata0:0:0:0): CAM status: ATA Status Error Feb 18 08:08:23 knew kernel: (ada0:ata0:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 40 (UNC ) Feb 18 08:08:23 knew kernel: (ada0:ata0:0:0:0): RES: 51 40 58 a9 f0 4b 4b 00 00 28 00 Feb 18 08:08:23 knew kernel:
CAM status: ATA Status Error Read More »
That smartd: Device: /dev/ada0, 8 Currently unreadable (pending) sectors problem which arose on Sunday is still around. I’ve run a short test, a long test, and a ZFS scrub is now underway. I may just replace the drive. $ sudo smartctl -P show /dev/ada0 smartctl 6.4 2015-06-04 r4109 [FreeBSD 10.2-RELEASE-p9 amd64] (local build) Copyright (C) 2002-15, Bruce Allen, Christian Franke, www.smartmontools.org Drive found in smartmontools Database. Drive identity strings: MODEL: TOSHIBA DT01ACA300 FIRMWARE:
smartd: Device: /dev/ada0, 8 Currently unreadable (pending) sectors persists Read More »
This morning I discovered this in my logs: Feb 14 04:56:39 knew kernel: (ada0:ata0:0:0:0): READ_DMA48. ACB: 25 00 b8 a8 f0 40 4b 00 00 00 e8 00 Feb 14 04:56:54 knew kernel: (ada0:ata0:0:0:0): CAM status: ATA Status Error Feb 14 04:56:54 knew kernel: (ada0:ata0:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 40 (UNC ) Feb 14 04:56:54 knew kernel: (ada0:ata0:0:0:0): RES: 51 40 58 a9 f0 4b 4b 00 00 48 00
smartd: Device: /dev/ada0, 8 Currently unreadable (pending) sectors Read More »
Last night, I managed to install new (but used) SAS cables for my Dell TL4000 on the tape01 server. I managed to get bacula-sd running, but I was unable to communicate with it from bacula-dir, via bconsole on my laptop. Eventually, I ran bacula-sd from the command line in the foreground and with debugging and saw things which needed to be corrected. In this post, I will adjust permissions on devices get bacula-dir
Using a Dell TL4000 with Bacula’s bacula-sd on FreeBSD with ZFS Read More »
This post has been superseded by a newer post. The new SFF-8088 to SFF-8088 SAS cables have arrived and have been connected to the LSI 9200-8E SAS card and to the Dell TL4000 tape library. The updated the dmesg output etc and appear on this page, for future reference. The significant portion is: I will have to investigate those no free space available messages later, but given all the devices are present, I