<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Dm-Crypt on Geeky Schmidt</title><link>https://geekyschmidt.com/tags/dm-crypt/</link><description>Recent content in Dm-Crypt on Geeky Schmidt</description><image><title>Geeky Schmidt</title><url>https://geekyschmidt.com/images/papermod-cover.png</url><link>https://geekyschmidt.com/images/papermod-cover.png</link></image><generator>Hugo</generator><language>en</language><copyright>Copyright ©2002-2026, Nicholas Schmidt; all rights reserved.</copyright><lastBuildDate>Sat, 12 Mar 2011 17:09:41 +0000</lastBuildDate><atom:link href="https://geekyschmidt.com/tags/dm-crypt/index.xml" rel="self" type="application/rss+xml"/><item><title>Why is my /dev/sda missing?!?!</title><link>https://geekyschmidt.com/2011/03/12/why-is-my-devsda-missing/</link><pubDate>Sat, 12 Mar 2011 17:09:41 +0000</pubDate><guid>https://geekyschmidt.com/2011/03/12/why-is-my-devsda-missing/</guid><description>&lt;p&gt;I am in the midst of testing some of the latest Linux kernels and realized that my old kernel config was wiped. In my desire to finish the build I forgot to select a VERY important option if you are using dm-crypt and LUKS. If you cannot access your /boot then there is no way to upgrade your kernel. Chicken and egg issue. Another issue maybe that you lost your /dev/sda1 or other nodes due to udev overtaking. Here is the fix in the situation:&lt;/p&gt;</description></item></channel></rss>