This is about FreeBSD 11.1 on my knew server. I recently replaced the 3TB drives with 5TB drives. Along the way, it didn’t boot, the swap was adjusted, I got concerned about power, and there was a brief CAM status: SCSI Status Error scare. Then today, the planned reboot, I started asking questions on Reddit […]
Booting off the new 5TB drives Read More »
I started replacing 3TB drives with 5TB drives in a 10 drive raidz3 array on a FreeBSD 10.3 box. I was not sure which drive tray to pull, so I powered off the server, and, one by one, pulled the drive tray, photographed it, and reinserted the drive tray. No changes were made. The first
After replacing 3TB drive with 5TB drive, FreeBSD 10.3 system did not reboot Read More »
In this power, the server is running FreeBSD 10.3. I am completely and unreasonably biased: ZFS is the best filesystem out there. Do not take my word for it. Ask around. Today, I started a process I’ve been waiting to do for a while. I am replacing the 3TB drives in a 10-drive raidz2 array
Swapping 5TB in, 3TB out Read More »
WARNING: This did not work. It succeeded, without error, but the card did not work. There will be a new blog post soon. Yesterday, a new LSI SAS 9201-16i arrived. I bought it on eBay from a supplier in China and paid for expedited shipping. I offered US$250 for their $338 listing and it was
Flashing an LSI SAS 9201-16i 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
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.
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:
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)
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 )
smartd: Device: /dev/ada0, 8 Currently unreadable (pending) sectors Read More »