Thaddeus’s Personal Site

So for some reason that Home Assistant OS virtual machine doesn’t really like being on certain versions of Vmware ESXI (typically older versions as I assume they do their testing as close to the newer releases as possible). I believe the issue stems from needing to change your virtual disk to IDE instead of SCSI which causes some underlying hard drive integrity issues that they didn’t plan for. Nonetheless, the fix is pretty easy and just takes a couple of minutes on your time and a Linux terminal (or any terminal that can SSH I guess).

Theres no real way to delete a cluster in the gui with out doing a fresh install (that i know of) but the following set of commands should stop the cluster service, force it to local, delete the configs and restart it like new. systemctl stop pve-cluster systemctl stop corosync pmxcfs -l rm /etc/pve/corosync.conf rm -r /etc/corosync/* killall pmxcfs systemctl start pve-cluster

Introduction# For those who aren’t familiar with the concept. Different hypervisors use different file formats to represent VM images and due to the fact that Proxmox uses Qemu (Quick Emulator)/KVM (Kernel-based Virtual Machine) to provide virtualization, it in turn uses Qcow2 (Qemu Copy-On-Write) as the storage file format for virtual machines data. The process to move Qcow2 files into Proxmox may not be as straight forward as it is on VMware, but its still a relatively painless process.

If you ever want a simple way to pull your public keys from Github so that you can use your safely stored ssh private keys where you need them. curl https://github.com/[USERNAME].keys This command will put it in your authorized_keys file which will actually allow you to use them in ssh. curl https://github.com/[USERNAME].keys | tee -a ~/.ssh/authorized_keys

Sometimes when trying to replace text using the sed command line tool you will tun into the issue in which your text has the forward slash characters which can be a bit of a headache because thats what sed uses to delimit strings. Thankfully the delimiter is pretty flexible. I like to use the pipe “|” symbol, but pretty much any other symbol will work such as the tilde “`” or the colon “:” ex:

In order to get proper email notifications from the TP-link Omada SDN Controller you need to set up SMTP and have it authenticate to your email provider of choice (here we’re gong to use gmail). This tutorial is assuming that you have a google domain because you use the google SMTP servers to send your mail. Gmail allows application access to SMTP functions pretty seamlessly so this whole evolution takes like 5 mins.

So i was trying to make a script that would automate SSL key exports from a BSD machine to another so I don’t have to go through the pain of doing it manually every time and i ran into the issue of me not being able to ssh-copy-id my files over but i keep running into the issue of it not being able to connect to my auth agent due to a lack of keys even though i generated them with ssh-keygen, nonetheless no matter what I did i kept getting met with:

Just a quick example of how to use dd to test drive read/write speed. NOTE: Dont do this a lot or you could shorten the live of your drive since youre making arbitrary writes. Reading# sudo dd if=/dev/zero of=/tmp/test.img bs=1G count=1 oflag=dsync This command will write 1G of zeros to an arbitrary file of your choosing. Feel free to delete it when you’re done. Your output will look a little like this.

The Problem# When installing Ubuntu Server with the LVM option in the default partitioning options, it will often only use a fraction of the actual disk space you have available. Thankfully LVM is flexible enough to extend this partition without causing any huge issues to your operating system. In this writeup, I’m gonna extend a 15G volume to a 200G volume on my Ubuntu 22.04.3 LTS VM. user@ubuntu:~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS loop0 7:0 0 55M 1 loop /snap/core18/1880 loop1 7:1 0 55.

After upgrading my Ubuntu Version and subsequently my kernel I tried running VMware Workstation Pro so I could access my VMs and kept running into the following error code when trying to open the application. Unfortunately, there was no way around it as rebooting, uninstalling/reinstalling, and anything else in my usual low-hanging fruit bag of tricks didn’t work so I had to really figure out what was really going on. Lets start with the actual error.