ads' corner

badblocks: Value too large for defined data type invalid end block (4394573824): must be 32-bit value

Bought a new large external disk as data sink for my server at home. The disk is 18TB and after the previous purchase had a hardware problem I wanted to make sure that this one is working. Created a partition, formatted it with ext4 and let's run a badblocks check on it. That failed, badblocks can't handle Big Data.

How to determine the mount point for a device on Linux

While reinstalling a server and moving it to Debian, I ran into the problem that I need to sync the EFI partitions. The system is using a RAID on two disks, but the EFI partitions can't be a RAID and need to exist on both disks. Or rather it is useful to have the EFI partition on every disk: if one disk fails, the system can boot from the other disk. grub only installs the necessary files on one partition. However one can use a script as grub hook, and sync all partitions. This script needs to determine if a device is already mounted somewhere, or needs to be mounted. Turns out there is a little and not well-known tool for this.

Install Debian Bookworm on a Software RAID and EFI

Moving my systems away from Ubuntu, I also have to reinstall a server at home. This system has two equal disks for a RAID system, and my plan is to install Debian on it. Turns out, setting up a Software RAID on Debian and booting from EFI is not a straightforward approach. This blog posting describes the steps.

How many Raspberry Pi can be operated in a Shipping Container

Back in December, during PGConf.EU 2023 in Prague, we had a discussion about datacenter hosting. Someone brought up Microsoft’s underwater datacenter experiment from a few years ago. And then someone else asked the obvious question: is it possible to run a datacenter in a shipping container using only Raspberry Pi computers. At first glance, this might seem impractical. But is it really? Let’s crunch the numbers and find out!

fwupdmgr: /usr/libexec/fwupd/efi/fwupdx64.efi and /usr/libexec/fwupd/efi/fwupdx64.efi.signed cannot be found

From time to time our laptops receive firmware updates, by using the Linux Vendor Firmware Service (short: fwupd). This worked fine for a long time, until it didn't. One day I was facing an error message.

HP Color LaserJet: Unable to connect to the network

We have a HP Color LaserJet in the office, one of these devices which can do both printing and scanning. The newer versions include a very nice feature “Scan to network folder” - so I did setup options to scan different PDF sizes to all of our laptops. Very convenient!

Until it stopped working a while ago.


SMART error (ErrorCount) detected on host - but the NVRAM disk is perfectly fine

Recently I got a new system with a NVRAM disk (nice and fast). Upon installing smartmontools, it started reporting that the error counter for the disk is increasing. For a brand new disk?


Reading data from my Scuba Diving computer after Linux removed IrDA support

When I go Scuba Diving, I use two diving computers. It’s always good to have a fallback, right? My main computer is a ScubaPro Uwatec Galileo Luna. That’s a wrist mounted computer with hoseless air-integration. That means that a sender is connected to the first stage of the regulator, and it transmits data to the wrist computer. In addition the computer records data like depths, consumption, temperature, alarms ect. My fallback is an air-integrated console mounted Suuntu Cobra. I check this computer too when I’m under water, but mostly for the most conservative reading for the safety stop.


Replace and re-add a failed drive to a Linux software RAID

Most of my systems run on a software RAID 1 configuration (that is, two disks, where each disk is mirrored to the other). This way, one of the disks can fail and still all the data is available.

If a disk failure happens, the disk is replaced with a similar disk, and then needs to be configured and re-added to the RAID.


Avoid "wear out" of SSD-cards in an openHAB system

You might know that problem: the brand new SSD in your system is super fast, but after a good time using it, the card is dead. Unlike spinning disks, which usually fail over time, and show I/O errors by blocks, SSD cards are prone to a problem called Wear leveling. Blocks which are written more often will “wear out”, and become unresponsible. More writes increase this risk. And a typical openHAB system does a number of writes all the time: every time an external status changes, it’s written to the event log. By default the syslog is written to disk as well, and then there is a myriad of systemd services, writing status information into files.