114 lines
13 KiB
HTML
114 lines
13 KiB
HTML
<!DOCTYPE html>
|
||
<html lang="en">
|
||
<head>
|
||
<meta charset="utf-8" />
|
||
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
|
||
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
||
<!-- Begin Jekyll SEO tag v2.8.0 -->
|
||
<title>when the coffee gets cold: recent adventures in my tech homelab | d@n tech</title>
|
||
<meta name="generator" content="Jekyll v4.3.4" />
|
||
<meta property="og:title" content="when the coffee gets cold: recent adventures in my tech homelab" />
|
||
<meta name="author" content="dustin newkirk" />
|
||
<meta property="og:locale" content="en_US" />
|
||
<meta name="description" content="A Not-So-Smooth Brew: Plex VM Crash Just like the perfect cup of coffee, my Plex Media Server has always been a source of comfort. However, recently, it decided to give me a bit of a jolt. The Plex VM crashed, which felt like spilling a fresh brew all over the counter. Thankfully, no media was lost. But, just like trying to clean up a coffee spill, restoring the backup didn’t go as planned. Instead of throwing in the towel, I rolled up my sleeves and rebuilt the VM from scratch. In the end, it was like discovering a new coffee blend – different, but better. I made some significant changes that improved the performance and reliability of the server. Sometimes, the best way to deal with a mess is to embrace the opportunity to improve. Fresh Beans: Upgrading the Server In the quest for better performance, I decided it was time for a hardware upgrade. I purchased 8 Xeon Gold 6138 processors, two per node, and got one node up and running for testing. It was like upgrading from instant coffee to a high-end espresso machine. The server feels more powerful and ready to handle anything I throw at it. However, before I can start moving my VMs, I need to invest in more RAM. For now, the new node is up and running, and I’ve tested moving VMs from Proxmox to XCP-NG. The process was smooth, with no issues – like making a seamless transition from drip coffee to a French press. Everything worked perfectly, setting the stage for future migrations. Scheduled Downtime: Brewing the Perfect Cup As any coffee aficionado knows, good things take time. Similarly, my server setup will require some planned downtime in the last week of July into early August. While this might feel like waiting for your morning coffee to brew, I assure you it’s worth it. There will be no loss of data, although services will be temporarily impacted. This downtime is necessary to ensure everything is running as smoothly as a freshly brewed cup of coffee. Once complete, my homelab will be stronger and more efficient, ready to serve up the tech equivalent of a perfect cup of joe. Stay tuned for more updates from dustin.coffee. Until then, keep your coffee hot and your servers cool!" />
|
||
<meta property="og:description" content="A Not-So-Smooth Brew: Plex VM Crash Just like the perfect cup of coffee, my Plex Media Server has always been a source of comfort. However, recently, it decided to give me a bit of a jolt. The Plex VM crashed, which felt like spilling a fresh brew all over the counter. Thankfully, no media was lost. But, just like trying to clean up a coffee spill, restoring the backup didn’t go as planned. Instead of throwing in the towel, I rolled up my sleeves and rebuilt the VM from scratch. In the end, it was like discovering a new coffee blend – different, but better. I made some significant changes that improved the performance and reliability of the server. Sometimes, the best way to deal with a mess is to embrace the opportunity to improve. Fresh Beans: Upgrading the Server In the quest for better performance, I decided it was time for a hardware upgrade. I purchased 8 Xeon Gold 6138 processors, two per node, and got one node up and running for testing. It was like upgrading from instant coffee to a high-end espresso machine. The server feels more powerful and ready to handle anything I throw at it. However, before I can start moving my VMs, I need to invest in more RAM. For now, the new node is up and running, and I’ve tested moving VMs from Proxmox to XCP-NG. The process was smooth, with no issues – like making a seamless transition from drip coffee to a French press. Everything worked perfectly, setting the stage for future migrations. Scheduled Downtime: Brewing the Perfect Cup As any coffee aficionado knows, good things take time. Similarly, my server setup will require some planned downtime in the last week of July into early August. While this might feel like waiting for your morning coffee to brew, I assure you it’s worth it. There will be no loss of data, although services will be temporarily impacted. This downtime is necessary to ensure everything is running as smoothly as a freshly brewed cup of coffee. Once complete, my homelab will be stronger and more efficient, ready to serve up the tech equivalent of a perfect cup of joe. Stay tuned for more updates from dustin.coffee. Until then, keep your coffee hot and your servers cool!" />
|
||
<link rel="canonical" href="https://dustin.coffee/tech/2024/07/09/when-the-coffee-gets-cold-recent-adventures-in-my-tech-homelab.html" />
|
||
<meta property="og:url" content="https://dustin.coffee/tech/2024/07/09/when-the-coffee-gets-cold-recent-adventures-in-my-tech-homelab.html" />
|
||
<meta property="og:site_name" content="d@n tech" />
|
||
<meta property="og:type" content="article" />
|
||
<meta property="article:published_time" content="2024-07-09T00:00:00-04:00" />
|
||
<meta name="twitter:card" content="summary" />
|
||
<meta property="twitter:title" content="when the coffee gets cold: recent adventures in my tech homelab" />
|
||
<script type="application/ld+json">
|
||
{"@context":"https://schema.org","@type":"BlogPosting","author":{"@type":"Person","name":"dustin newkirk"},"dateModified":"2024-07-09T00:00:00-04:00","datePublished":"2024-07-09T00:00:00-04:00","description":"A Not-So-Smooth Brew: Plex VM Crash Just like the perfect cup of coffee, my Plex Media Server has always been a source of comfort. However, recently, it decided to give me a bit of a jolt. The Plex VM crashed, which felt like spilling a fresh brew all over the counter. Thankfully, no media was lost. But, just like trying to clean up a coffee spill, restoring the backup didn’t go as planned. Instead of throwing in the towel, I rolled up my sleeves and rebuilt the VM from scratch. In the end, it was like discovering a new coffee blend – different, but better. I made some significant changes that improved the performance and reliability of the server. Sometimes, the best way to deal with a mess is to embrace the opportunity to improve. Fresh Beans: Upgrading the Server In the quest for better performance, I decided it was time for a hardware upgrade. I purchased 8 Xeon Gold 6138 processors, two per node, and got one node up and running for testing. It was like upgrading from instant coffee to a high-end espresso machine. The server feels more powerful and ready to handle anything I throw at it. However, before I can start moving my VMs, I need to invest in more RAM. For now, the new node is up and running, and I’ve tested moving VMs from Proxmox to XCP-NG. The process was smooth, with no issues – like making a seamless transition from drip coffee to a French press. Everything worked perfectly, setting the stage for future migrations. Scheduled Downtime: Brewing the Perfect Cup As any coffee aficionado knows, good things take time. Similarly, my server setup will require some planned downtime in the last week of July into early August. While this might feel like waiting for your morning coffee to brew, I assure you it’s worth it. There will be no loss of data, although services will be temporarily impacted. This downtime is necessary to ensure everything is running as smoothly as a freshly brewed cup of coffee. Once complete, my homelab will be stronger and more efficient, ready to serve up the tech equivalent of a perfect cup of joe. Stay tuned for more updates from dustin.coffee. Until then, keep your coffee hot and your servers cool!","headline":"when the coffee gets cold: recent adventures in my tech homelab","mainEntityOfPage":{"@type":"WebPage","@id":"https://dustin.coffee/tech/2024/07/09/when-the-coffee-gets-cold-recent-adventures-in-my-tech-homelab.html"},"url":"https://dustin.coffee/tech/2024/07/09/when-the-coffee-gets-cold-recent-adventures-in-my-tech-homelab.html"}</script>
|
||
<!-- End Jekyll SEO tag -->
|
||
|
||
|
||
<meta name="keywords" content="" />
|
||
|
||
<meta name="google-adsense-account" content="ca-pub-5033279084799102">
|
||
<link rel="shortcut icon" href="/assets/logos/dn-tech-favicon-color.png" />
|
||
<link rel="apple-touch-icon" href="/assets/logos/logo-color.png"/>
|
||
<link rel="stylesheet" type="text/css" href="/assets/css/styles.css" />
|
||
<link rel="stylesheet" type="text/css" href="/assets/css/prism.css" />
|
||
<script src="/assets/js/prism.js"></script>
|
||
|
||
<script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?client=ca-pub-5033279084799102"
|
||
crossorigin="anonymous"></script>
|
||
</head>
|
||
|
||
<body>
|
||
<div class="wrapper">
|
||
<header class="wrapper-header">
|
||
<div class="header">
|
||
<h1>d@n tech</h1>
|
||
<br>
|
||
<h5><i>Caffinated Tech Insights</i></h5>
|
||
<br>
|
||
<nav>
|
||
|
||
<a href="/">About & Contact</a>
|
||
|
||
<a href="/posts">Posts</a>
|
||
|
||
<a href="/categories/">Categories</a>
|
||
|
||
<a href="/resume">Resume</a>
|
||
|
||
</nav>
|
||
<hr>
|
||
</div>
|
||
|
||
</header>
|
||
|
||
<main class="wrapper-main">
|
||
<div class="main-content">
|
||
<div class="post-info">
|
||
<h2>when the coffee gets cold: recent adventures in my tech homelab</h2>
|
||
<p>09 Jul 2024 - </p>
|
||
</div>
|
||
|
||
<div class="post-content">
|
||
<h4 id="a-not-so-smooth-brew-plex-vm-crash">A Not-So-Smooth Brew: Plex VM Crash</h4>
|
||
<p>Just like the perfect cup of coffee, my Plex Media Server has always been a source of comfort. However, recently, it decided to give me a bit of a jolt. The Plex VM crashed, which felt like spilling a fresh brew all over the counter. Thankfully, no media was lost. But, just like trying to clean up a coffee spill, restoring the backup didn’t go as planned.</p>
|
||
|
||
<p>Instead of throwing in the towel, I rolled up my sleeves and rebuilt the VM from scratch. In the end, it was like discovering a new coffee blend – different, but better. I made some significant changes that improved the performance and reliability of the server. Sometimes, the best way to deal with a mess is to embrace the opportunity to improve.</p>
|
||
|
||
<h4 id="fresh-beans-upgrading-the-server">Fresh Beans: Upgrading the Server</h4>
|
||
<p>In the quest for better performance, I decided it was time for a hardware upgrade. I purchased 8 Xeon Gold 6138 processors, two per node, and got one node up and running for testing. It was like upgrading from instant coffee to a high-end espresso machine. The server feels more powerful and ready to handle anything I throw at it.</p>
|
||
|
||
<p>However, before I can start moving my VMs, I need to invest in more RAM. For now, the new node is up and running, and I’ve tested moving VMs from Proxmox to XCP-NG. The process was smooth, with no issues – like making a seamless transition from drip coffee to a French press. Everything worked perfectly, setting the stage for future migrations.</p>
|
||
|
||
<h4 id="scheduled-downtime-brewing-the-perfect-cup">Scheduled Downtime: Brewing the Perfect Cup</h4>
|
||
<p>As any coffee aficionado knows, good things take time. Similarly, my server setup will require some planned downtime in the last week of July into early August. While this might feel like waiting for your morning coffee to brew, I assure you it’s worth it. There will be no loss of data, although services will be temporarily impacted.</p>
|
||
|
||
<p>This downtime is necessary to ensure everything is running as smoothly as a freshly brewed cup of coffee. Once complete, my homelab will be stronger and more efficient, ready to serve up the tech equivalent of a perfect cup of joe.</p>
|
||
|
||
<p>Stay tuned for more updates from dustin.coffee. Until then, keep your coffee hot and your servers cool!</p>
|
||
|
||
</div>
|
||
</div>
|
||
</main>
|
||
</div>
|
||
|
||
<footer class="wrapper-footer">
|
||
<div class="footer">
|
||
<span class="footer-text float-left">This work is licensed under <a rel="license" href="https://www.gnu.org/licenses/gpl-3.0.en.html" target="_blank">GPLv3</a></span>
|
||
<span class="footer-text float-right">
|
||
Site Updated: 2025-07-29 ET (<a href="/feed.xml" target="_blank">RSS</a>)
|
||
</span>
|
||
</div>
|
||
<script src='https://storage.ko-fi.com/cdn/scripts/overlay-widget.js'></script>
|
||
<script>
|
||
kofiWidgetOverlay.draw('dustinnewkirk', {
|
||
'type': 'floating-chat',
|
||
'floating-chat.donateButton.text': 'Support Me',
|
||
'floating-chat.donateButton.background-color': '#ff851b',
|
||
'floating-chat.donateButton.text-color': '#3D2200'
|
||
});
|
||
</script>
|
||
|
||
</footer>
|
||
</body>
|
||
</html>
|