<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Lessons Learned on System Overlord</title><link>https://systemoverlord.com/tags/lessons-learned.html</link><description>Recent content in Lessons Learned on System Overlord</description><generator>Hugo</generator><language>en-us</language><managingEditor>david@systemoverlord.com (David Tomaschik)</managingEditor><webMaster>david@systemoverlord.com (David Tomaschik)</webMaster><lastBuildDate>Mon, 20 Oct 2014 14:19:40 +0000</lastBuildDate><atom:link href="https://systemoverlord.com/tags/lessons-learned/index.xml" rel="self" type="application/rss+xml"/><item><title>PSA: Typos in mkfs commands are painful</title><link>https://systemoverlord.com/2014/10/20/psa-typos-in-mkfs-commands-are-painful/</link><pubDate>Mon, 20 Oct 2014 14:19:40 +0000</pubDate><author>david@systemoverlord.com (David Tomaschik)</author><guid>https://systemoverlord.com/2014/10/20/psa-typos-in-mkfs-commands-are-painful/</guid><description>&lt;p&gt;TL;DR: I apparently typed &lt;code&gt;mkfs.vfat /dev/sda1&lt;/code&gt; at some point. Oops.&lt;/p&gt;
&lt;p&gt;So I rarely reboot my machines, and last night, when I rebooted my laptop (for graphics card weirdness) Grub just came up with:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;Error: unknown filesystem.
grub rescue&amp;gt;
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;WTF, I wonder how I borked my grub config? Let&amp;rsquo;s see what happens when we ls my /boot partition.&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;grub rescue&amp;gt;ls (hd0,msdos1)
unknown filesystem
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Hrrm, that&amp;rsquo;s no good. An &lt;code&gt;ls&lt;/code&gt; on my other partition isn&amp;rsquo;t going to be very useful, it&amp;rsquo;s a LUKS-encrypted LVM PV. Alright, time for a live system. I grab a Kali live USB (not because Kali is necessarily the best option here, it&amp;rsquo;s just what I happen to have handy) and put it in the system and boot from that. &lt;code&gt;file&lt;/code&gt; tells me its an &lt;code&gt;x86 boot sector&lt;/code&gt;, which is not at all what I&amp;rsquo;m expecting from an ext4 boot partition. It slowly dawns on me that at some point, intending to format a flash drive or SD card, I must&amp;rsquo;ve run &lt;code&gt;mkfs.vfat /dev/sd&lt;/code&gt;&lt;strong&gt;&lt;code&gt;a&lt;/code&gt;&lt;/strong&gt;&lt;code&gt;1&lt;/code&gt; instead of &lt;code&gt;mkfs.vfat /dev/sd&lt;/code&gt;&lt;strong&gt;&lt;code&gt;b&lt;/code&gt;&lt;/strong&gt;&lt;code&gt;1&lt;/code&gt;. That one letter makes all the difference. Of course, it turns out it&amp;rsquo;s not even a valid FAT filesystem&amp;hellip; since the device was mounted, the OS had kept writing to it like an ext4 filesystem, so it was basically a mangled mess. &lt;code&gt;fsck&lt;/code&gt; wasn&amp;rsquo;t able to restore it, even pointing to backup superblocks: it seems as though, among other things, the root inode was destroyed.&lt;/p&gt;</description></item><item><title>My Time at KSU</title><link>https://systemoverlord.com/2012/02/03/my-time-at-ksu/</link><pubDate>Fri, 03 Feb 2012 04:24:58 +0000</pubDate><author>david@systemoverlord.com (David Tomaschik)</author><guid>https://systemoverlord.com/2012/02/03/my-time-at-ksu/</guid><description>&lt;p&gt;
	As you might have seen, I'm leaving my position at Kennesaw State University to take a position as a Site Reliability Engineer at Google.  This is something I'm very excited about, but I thought I'd take a look back at my time at KSU as I approach the end.  It's worth mentioning that I'm not leaving KSU because of KSU, but because this is an opportunity I just could not turn down.  For the most part, I like my position at KSU, and I really like most of the people that I work with.  There's a particular group that's become three of my closest friends and one treasured acquaintance.&lt;/p&gt;</description></item></channel></rss>