<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Gpt on Luther Monson</title>
    <link>https://luth.io/tags/gpt/</link>
    <description>Recent content in Gpt on Luther Monson</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sat, 01 Aug 2026 13:15:00 -0700</lastBuildDate>
    <atom:link href="https://luth.io/tags/gpt/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Rescuing a Windows Dynamic Disk Over USB with WSL2 and USB/IP</title>
      <link>https://luth.io/blog/2026/08/windows-dynamic-disk-usb-wsl2-usbip/</link>
      <pubDate>Sat, 01 Aug 2026 13:15:00 -0700</pubDate>
      <guid>https://luth.io/blog/2026/08/windows-dynamic-disk-usb-wsl2-usbip/</guid>
      <description>&lt;p&gt;I pulled a 1 TB NVMe out of an old Windows box, dropped it in a USB enclosure and plugged it in. Windows showed nothing.&#xA;No drive letter, no &amp;ldquo;initialize this disk&amp;rdquo; prompt, nothing in Explorer. Disk Management listed it as &lt;code&gt;Invalid&lt;/code&gt;. The&#xA;enclosure&amp;rsquo;s booklet said to &amp;ldquo;bring the disk online&amp;rdquo;, which silently did nothing. The data was completely intact. Windows&#xA;was refusing on &lt;strong&gt;policy&lt;/strong&gt; grounds, not because anything was broken. Getting it back meant going around the Windows&#xA;storage stack entirely. I handed the raw USB device to a Linux kernel that doesn&amp;rsquo;t share Windows&amp;rsquo; opinions.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
