knew
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
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
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 and on Twitter. The booting issue BIOS cannot boot from drives which present only 4096-byte sectors. This is
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 reboot Upon powering up, I was greeted by this (I have typed out the text for search purposes):
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 with 5TB drives. These new drives are faster, I think perhaps cooler, and, more to the point, bigger.
Swapping 5TB in, 3TB out 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 from 3TB to 5TB drives. 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:
NOTE: this post has been replaced by a newer version. The older post is still available This is x8dtu (named after the Supermicro motherboard). This will be the new FreshPorts server. In short: FreeBSD 11 booting off a mirrored pair of zfsroot SSDs 4.5TB of mirrored ZFS 196612 MB of RAM (yeah, that’s 196GB of RAM) Supermicro X8TDU motherboard Intel Xeon E5620 @ 2.40GHz (two of those, giving 16 CPUs) NOTE: this post
I’ve been given a Dell PowerEdge R610. I’ve installed two 30GB SSDs and installed FreeBSD 11 on it. It will become a tape library server. EDIT: 2017.11.29 – the drives, network card, and SAS card have been moved to the R710. The swap: The zpools: Oh, well, that’s a problem. Let’s fix it: There. Fixed. Just. Like. That.™ The filesystems: And dmesg:
I have a system with three tape drives and two tape changers. If one tape library is powered off when the system boots, the device names for the other tape library may be skewed. That is, /dev/sa0 may not be the LTO-4 drive, it will be the SDLT drive. This is not ideal. FreeBSD uses device.hints for this. I have used it before, and for quite some time, however, I learned something new
Using device.hints to wire physical devices to specific names Read More »
NOTE: this post has been replaced by a newer version. Please meet x8dtu, a server destined to be the future home of FreshPorts. There is nothing installed here. In short: FreeBSD 11 booting off a mirrored pair of zfsroot SSDs 4.5TB of mirrored ZFS 196612 MB of RAM (yeah, that’s 196GB of RAM) Supermicro X8TDU motherboard Intel Xeon E5620 @ 2.40GHz (two of those, giving 16 CPUs)
Three weeks ago, I thought I had flashed my new LSI SAS 9201-16i. I had not. When I powered up the system via mfsBSD, I could see the device, but during the boot process, there was no splash screen. I now believe this should always be a signal that you have not correctly flashed the card. Finally, I went back to basics. I went back to something I did in photos. I used
Flashing an LSI SAS 9201-16i – correctly Read More »