We have a HP Color LaserJet in the office, one of these 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.
The printer refuses scans to a network folder with the error message: "Scan Error" "Unable to connect to the network. Check the network, and then try again."
Continue reading "HP Color LaserJet: Unable to connect to the network"
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?
Continue reading "SMART error (ErrorCount) detected on host - but the NVRAM disk is perfectly fine"
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.
The Luna computer has an IrDA port, and using a USB Infrared Adapter (I'm using an IRwave 3902B500) I was able to read all the dive logs from the computer into Subsurface. However at some point, Linux decided that IrDA is no longer worth supporting, and they removed the support and modules in Linux 4.17.
It's possible to read the most basic data about each dve on the computer display itself, but you won't get all the details, and the profiles.
Continue reading "Reading data from my Scuba Diving computer after Linux removed IrDA support"
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.
Newer systems all use the GUID partition table (GPT), and therefore allow almost unlimited disk sized. Instructions for re-adding a disk using GPT are a bit different from the days when MBR (up to 2 TB disk space) was used, therefore I'm writing them down here for future use.
Continue reading "Replace and re-add a failed drive to a Linux software RAID"
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.
Continue reading "Avoid "wear out" of SSD-cards in an openHAB system"
Ein Bekannter hat sich ein Acer Notebook geholt und wunderte sich dann, warum in der Systemsteuerung beim Mikrofon nur "nicht angeschlossen" steht. Acer hat mit dem Aspire 5732ZG ein Notebook mit integrierter Webcam herausgebracht - dem tada ein Mikrofon fehlt. Es gibt lediglich einen Eingang, an dem man ein externes Mikrofon anstecken kann.
Da hat Acer wohl am falschen Ende gespart! Multimedia - zum Lachen.