Forem: Eddy Bobbin

Easily replace your hard drive

Eddy Bobbin — Tue, 04 Jun 2024 06:06:18 +0000

Recently, I encountered the issue that my 512GB SSD was gradually filling up. Naturally, the first step is to manually clean up. Under Linux, there’s a useful tool called du that allows you to determine how much disk space each directory occupies. This helps identify space-consuming culprits quickly:

# The `max-depth` parameter specifies the depth of the output breakdown.
du -h --max-depth=1 /

In my case, there was no obvious space hog that I could easily eliminate, so I decided to upgrade to a new SSD.

Now, how can you switch to a new disk without the hassle of a complete laptop reinstallation? Well, I took the lazy route and used the dd tool to create a byte-wise copy of my old hard drive onto the new one. This saved me the time-consuming process of setting up my laptop from scratch, and I was done in about an hour (including installing the new drive).

Here’s a step-by-step guide:

Create a Bootable Ubuntu USB Stick

Make sure you have a bootable USB stick with Ubuntu on it. You’ll need it to create a copy of your hard drive. Ensure that the old hard drive is not mounted; otherwise, the process won’t work.

Install the New Hard Drive in an External Enclosure

I ordered the Samsung EVO 990 2TB hard drive. For compatibility, I paired it with this external enclosure. I opted for a more expensive enclosure because the cheaper ones had poor reviews regarding speed and support for the Samsung drive.

Connect the New Hard Drive via USB

The new disk doesn’t need to be formatted, simply install it and connect it via USB.

Create a Byte-Wise Copy

Use the following command to create the copy:

# List all installed HDDs
lshw -class disk

# Replace `<old disk>` with something like `/dev/nvme0n1`, and `<new disk>` with `/dev/sdb` or similar (you'll recognize it by the disk size). Use `status=progress` to track the progress.
dd if=<old disk> of=<new disk> bs=64m status=progress

The copying process took less than 20 minutes for me, with the enclosure achieving around 700MB/s write speed to the new drive.

Installing the New Hard Drive

Open the laptop case, remove the old drive, insert the new drive, and close the case.

With my Lenovo T14s, the screw securing the SSD was quite tight. I had to apply significant force to loosen it and ended up using pliers to make it easier. I suspect that too much screw-locking adhesive was used. Ideally, the screw shouldn’t be tighter than the case screws.

Boot the Laptop and Resize Partitions if Necessary

The laptop should boot normally with the new hard drive.

If the new drive is larger than the old one, you’ll need to adjust your partitions to utilize the entire space. The steps depend on your existing partition setup. In my Ubuntu installation, I chose the default partitioning. Here’s what I did to resize the partition:

Open GParted and right-click on the largest partition to resize it to the maximum size.

Since my partition is a LVM partition (Logical Volume Manager), I needed the following command to expand it:

# First, check which parameter to append to `lvextend`:
df -h

# Then, execute this command to ultimately resize the partition:
lvextend -l +100%FREE -r /dev/mapper/vgubuntu-root

And that’s it—the hard drive replacement is complete!

Github Action to check helm charts for deprecated k8s APIs

Eddy Bobbin — Fri, 05 May 2023 16:02:45 +0000

What I built

I Built a github action which checks your helm chart for deprecated k8s API usages by leveraging pluto functionality.

At the moment, you have to build this on your own using multiple steps in your github action workflow. This github action simplifies it in one step and makes your workflow definition more readable.

Category Submission:

Maintainer Must Haves
DIY Deployments

App Link

Helm pluto github action

Description

Without the plugin, you have to put multiple steps in your github action pipeline to match necessary preconditions:

Download helm
Download pluto
render your helm chart
hand over helm chart to pluto

This github action takes care of all the preconditions and allows you to verify your helm chart in a single step.

It's just a minor improvement, but by using this action you do not have to take care of the boilerplate.

Link to Source Code

Source Code

Permissive License

Apache 2.0

Background (What made you decide to build this particular app? What inspired you?)

I built this as a shared library for Jenkins and did not find a pendant for github actions.

How I built it (How did you utilize GitHub Actions or GitHub Codespaces? Did you learn something new along the way? Pick up a new skill?)

This is a github action itself.

Additional Resources/Info

An example usage can be found here

Atom editor with linter, prettier and all the stuff you need

Eddy Bobbin — Thu, 19 Mar 2020 10:23:54 +0000

Finally, my working atom editor setup for javascript

Recently, I setup my atom editor because of a React javascript project. What I knew from work (my fellow teammembers use VSCode there) is there are some nice tools like linter and prettier to keep your code clean, error free and readable. Some of those things remind me of the typical IntelliJ IDEA tools (e.g. Firebug, Checkstyle and so on).
However I didn't find a good instruction or tutorial to make all the stuff work. So I tried a bit around and here is what I got for all those who have the same trouble I had:

Prerequisites

This tutorial is optimized for unix- based clients which have a bash or similar. However, you can use this setup on other machines as well but I did not test it for them.

Download atom from https://atom.io/

Required atom packages

Install required atom packages with

apm install linter \ 
linter-eslint \
linter-ui-default \
busy-signal \
intentions \
prettier-atom \

Atom settings

Open the editor and the settings by pressing CTRL + Comma
Go to packages and filter for prettier-atom and click settings
Enable the options ESlint integration and Format files on save

Test your setup

To test the setup, I created a new react-app by executing npx create-react-app test-app and imported it into atom editor.
When saving an edited file with obvious errors (unused import, newlines, single vs double quotes), I can see the editor shows me linter warnings and autoformats things on save:

The create-react-app setup inherits a default eslint config from the react packages. If you wish to override these with your own settings, you can create a .eslintrc file in your project root.