432c946e494b0d28ab65d5e66b444e6debd49dd9 — Matthew Jorgensen 5 days ago 6340c5c
Back-publishing draft by one day
3 files changed, 34 insertions(+), 10 deletions(-)

A _drafts/2019-10-12-Status-Update-October-2019.md
R _drafts/{The-Reboot-that-Removed-the-Operating-System.md => 019-10-11-The-Reboot-that-Removed-the-Operating-System.md}
R _posts/{2019-10-11-Pleroma-admin-fe.md => 2019-10-12-Pleroma-admin-fe.md}
A _drafts/2019-10-12-Status-Update-October-2019.md => _drafts/2019-10-12-Status-Update-October-2019.md +5 -0
@@ 0,0 1,5 @@
+ ---
+ layout: post
+ title: "Status Update: October 2019"
+ ---
+ 

R _drafts/The-Reboot-that-Removed-the-Operating-System.md => _posts/2019-10-11-The-Reboot-that-Removed-the-Operating-System.md +29 -10
@@ 8,20 8,31 @@ I've been slowly upgrading our systems to Windows Server 2016 or better.
  Up until this incident, things were going fine.
  
+ ---
+ 
+ ***Note:** This happened about 7 months ago, and I'm just now
+ publishing. The ending is rough because I don't remember all the
+ details, and I'm also not a fan of removing things permanently.*
+ 
+ ---
+ 
  I was configuring virtual memory at the time which requires a reboot for
  settings to take effect. Since it's a server and we hide the
  Shutdown/Restart options via Policy, a quick `shutdown /t 0 /r` and I
  was on my way...
  
  Or so I thought. A few more minutes pass than usual when I notice my
- `ping` shell was scrolling along: `Destination Host Unreachable`. Usually, a
- reboot only produces a handful of `Request timed out`. messages.
- Fortunately, since this is an internal VM, I have console access. I
- hopped into vSphere and opened the console on the machine in question.
- 
-     An operating system wasn't found. Try disconnecting any drives that
-     don't contain an operating system.
-     Press Ctrl+Alt+Del to restart
+ `ping` shell was scrolling along: `Destination Host Unreachable`.
+ Usually, a reboot only produces a handful of `Request timed out`.
+ messages. Fortunately, since this is an internal VM, I have console
+ access. I hopped into vSphere and opened the console on the machine in
+ question.
+ 
+ <pre style="color:lightgray;background-color:black;">
+ 	<code>An operating system wasn't found. Try disconnecting any drives that
+ don't contain an operating system.
+ Press Ctrl+Alt+Del to restart
+ </code></pre>
  
  After staring at the blank, black screen for several minutes as I was
  trying to figure out *what happened to the operating system I was just


@@ 34,5 45,13 @@ I phoned my coworker who hadn't seen this issue before. I ran a few
  search queries online and started sifting through the results.
  
- Diskpart, snapshots, Disk Management in Windows, drive letter
- free-for-all> 
\ No newline at end of file
+ ---
+ 
+ It turns out that using Windows' Disk Management to repartition a VMDK
+ is a *bad idea.* What ensued was two hours of my chasing this problem
+ down, spending at least 45 minutes of those two hours in Windows System
+ Recovery trying to reconfigure the Master Boot Record.
+ 
+ The root issue was that, since VMware didn't recognize the partitions
+ anymore, it was assigning drive letters to it as it pleased, somehow
+ never managing to give the actual C: disk the letter C. 

R _posts/2019-10-11-Pleroma-admin-fe.md => _posts/2019-10-12-Pleroma-admin-fe.md +0 -0