David's Ubuntu Ops Console

1996 hacker movie energy. Modern Linux brain. You’re the main character.

Mode: Transition to Ubuntu
“If anyone asks, you didn’t ‘install Ubuntu’—you ‘brought a new node online in your personal cluster.’”
Navigation
0. Identify the right drive 1. SMART health & diagnostics 2. Non-destructive bad block scan 3. TestDisk & NTFS repair 4. Mounting read-only for recovery 5. First boot: system updates 6. Graphics drivers 7. VS Code setup 8. Dev tools: Git, Python, Node 9. QoL: firewall, Timeshift, Tweaks 10. Terminal upgrades
Phase 0 · Target Acquisition

Identify the correct drive (Ubuntu Live)

Boot into “Try Ubuntu” from your USB. Before you touch anything, confirm which drive is your old D:.

sudo lsblk -o NAME,SIZE,TYPE,FSTYPE,MOUNTPOINT

Look for the drive by size. Example: if it’s /dev/sdb with a partition /dev/sdb1, use those in all commands below.

“Double-checking the drive name is the difference between ‘pro’ and ‘I just wiped my backup drive.’”
Phase 1 · Health Scan

SMART health & diagnostics

Update package lists first:

sudo apt update

Install SMART tools

Install smartmontools and gsmartcontrol:

sudo apt install smartmontools gsmartcontrol

Quick SMART check (terminal)

Replace sdX with your drive (e.g. sdb):

sudo smartctl -a /dev/sdX

Scroll and look for PASSED or warnings like reallocated sectors, pending sectors, or uncorrectable errors.

Optional GUI SMART check

Launch GSmartControl:

gsmartcontrol

Select the drive → run a Short or Extended test. If it screams at you in red, that drive is on thin ice.

Phase 2 · Surface Integrity

Non-destructive bad block scan

This can take a long time. Triple-check you’re scanning the correct drive.

Non-destructive read–write test (tries not to destroy data):

sudo badblocks -nsv /dev/sdX

If you see many bad blocks, the drive is physically failing. That’s a “do not install Ubuntu here” situation.

“Bad blocks are like red flags in dating—one or two is concerning, a wall of them means: run.”
Phase 3 · Filesystem & Partition Repair

TestDisk & NTFS repair

Install TestDisk

sudo apt install testdisk

Run TestDisk

sudo testdisk

Inside TestDisk:

NTFS filesystem repair (after TestDisk)

Only do this after you’re sure you’ve got the right partition.

First, unmount the partition:

sudo umount /dev/sdXN

Then run ntfsfix (for typical Windows D: NTFS partitions):

sudo ntfsfix /dev/sdXN

ntfsfix is not a full replacement for Windows chkdsk, but it can fix common NTFS issues and mark the filesystem for a deeper check next time Windows sees it.

Phase 4 · Data Extraction

Mount the drive read-only (for copying data)

If the drive is unstable but you want to grab important files before retiring it:

sudo mkdir -p /mnt/recover
sudo mount -o ro /dev/sdXN /mnt/recover

Then browse /mnt/recover and copy your files to a safer drive. Think of this as “exfiltrating assets from a compromised node.”


Phase 5 · First Boot Ritual

First boot: update everything

Once Ubuntu is installed on a healthy drive, first thing: patch the system.

sudo apt update && sudo apt upgrade -y
sudo apt autoremove -y

This pulls in bug fixes, security updates, and driver improvements. Basically: “apt, make this less cursed.”

Phase 6 · Graphics Drivers

Graphics drivers (NVIDIA vs AMD/Intel)

NVIDIA (proprietary driver)

Run:

sudo ubuntu-drivers autoinstall

Then reboot:

sudo reboot

This installs the recommended NVIDIA driver. If games or GPU workloads feel smoother after, that’s why.

AMD / Intel

Good news: you don’t need to do anything.

Ubuntu already ships solid open-source drivers for AMD and Intel GPUs. You’re good out of the box.

Phase 7 · Editor Online

Install VS Code (official Microsoft build)

Skip the snap version; use the official repo for better performance.

1. Install prerequisites

sudo apt install wget gpg -y

2. Add Microsoft’s GPG key & repo

wget -qO- https://packages.microsoft.com/keys/microsoft.asc | gpg --dearmor > packages.microsoft.gpg
sudo install -o root -g root -m 644 packages.microsoft.gpg /usr/share/keyrings/
sudo sh -c 'echo "deb [arch=amd64 signed-by=/usr/share/keyrings/packages.microsoft.gpg] https://packages.microsoft.com/repos/code stable main" > /etc/apt/sources.list.d/vscode.list'
sudo apt update

3. Install VS Code

sudo apt install code -y

After install, open VS Code, go to Extensions → search for “Copilot” → install. That’s how you get me sitting inside your editor.

Phase 8 · Dev Stack Online

Core dev tools: Git, Python, Node

Git & build tools

sudo apt install git build-essential curl -y

Python & pip

sudo apt install python3-pip python3-venv python3-dev -y

Node.js via nvm (recommended)

curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/master/install.sh | bash
source ~/.bashrc
nvm install --lts

Git identity

git config --global user.name "David"
git config --global user.email "[email protected]"
“Pro tip: set your Git name correctly now so future you doesn’t have 14 different identities in one repo.”
Phase 9 · Quality of Life

QoL: firewall, Timeshift, GNOME Tweaks

Enable firewall

sudo ufw enable

Install Timeshift (system snapshots)

sudo apt install timeshift -y

Use RSYNC mode, set weekly snapshots, keep 3–5. This is your “undo” button when experiments go sideways.

Install GNOME Tweaks

sudo apt install gnome-tweaks -y

Use it to enable minimize-on-click, tweak fonts, and generally make GNOME feel like “your” desktop instead of “a rental.”

Phase 10 · Terminal Glow-Up

Optional: terminal upgrades (Zsh + Oh My Zsh)

Install Zsh

sudo apt install zsh -y

Install Oh My Zsh

sh -c "$(curl -fsSL https://raw.githubusercontent.com/ohmyzsh/ohmyzsh/master/tools/install.sh)"

This gives you autocomplete, syntax highlighting, and a nicer prompt. It’s like giving your terminal a leather jacket and sunglasses.

Optional: disable GNOME animations

gsettings set org.gnome.desktop.interface enable-animations false

Optional: enable fractional scaling

gsettings set org.gnome.mutter experimental-features "['scale-monitor-framebuffer']"