had to update index again
This commit is contained in:
67
posts/personal/1693890000-blog-issue.html
Normal file
67
posts/personal/1693890000-blog-issue.html
Normal file
@@ -0,0 +1,67 @@
|
||||
<!DOCTYPE html>
|
||||
<html>
|
||||
<head>
|
||||
<link rel="Stylesheet" type="text/css" href="../../style.css">
|
||||
<link rel="alternate" type="application/rss+xml" title="RSS" href="../../rss.xml">
|
||||
<title>Blog Issue</title>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1">
|
||||
</head>
|
||||
<body>
|
||||
|
||||
|
||||
|
||||
<hr />
|
||||
<p>
|
||||
<a href="index.html">Index</a>
|
||||
<hr />
|
||||
</p>
|
||||
|
||||
<p>
|
||||
last 5 posts
|
||||
<hr />
|
||||
</p>
|
||||
<ul>
|
||||
<li>
|
||||
<a href="1693630800-hello-world.html">Hello World</a>
|
||||
|
||||
</ul>
|
||||
<hr />
|
||||
<p>
|
||||
<span id="-Date:"></span><strong id="Date:">Date:</strong> 2023/09/05
|
||||
</p>
|
||||
|
||||
<p>
|
||||
<span id="-Author:"></span><strong id="Author:">Author:</strong> Tristan Ancelet
|
||||
</p>
|
||||
|
||||
<div id="Blog Issue"><h1 id="Blog Issue" class="header"><a href="#Blog Issue">Blog Issue</a></h1></div>
|
||||
<div id="Blog Issue-DNS"><h2 id="DNS" class="header"><a href="#Blog Issue-DNS">DNS</a></h2></div>
|
||||
<hr />
|
||||
<p>
|
||||
Looks like my master DNS server was down for the last 3 days (didn't know until the teacher mentioned it). Had to end up taking a look at my provider and it looks like my master DNS server had crashed at some point. After restarting it I got everything started up and it seems to have come back up.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
I had a backup DNS server as well, but after looking into the VM (that was still running), it turns out that I never whitelisted the DNS port (53/udp) on it. So it's entire life has been failure (as it's been the backup for several months). My thought is that I <span id="Blog Issue-DNS-DID"></span><strong id="DID">DID</strong> whitelist it but not perminately. So after a reboot it cleared the config and DNS traffic wasn't whitelisted it anymore.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
Here is the commands it did to whitelist DNS (running firewalld as a device side firewall)
|
||||
</p>
|
||||
|
||||
<pre bash>
|
||||
firewall-cmd --perm --zone=public --add-service=dns
|
||||
firewall-cmd --reload
|
||||
</pre>
|
||||
|
||||
<p>
|
||||
After checking that DNS was resolving with dig, I was able to visit my site with no more issues.
|
||||
</p>
|
||||
|
||||
<pre bash>
|
||||
dig blog.tristanancelet.com
|
||||
</pre>
|
||||
|
||||
</body>
|
||||
</html>
|
74
posts/personal/1699564352-webhooks.html
Normal file
74
posts/personal/1699564352-webhooks.html
Normal file
@@ -0,0 +1,74 @@
|
||||
<!DOCTYPE html>
|
||||
<html>
|
||||
<head>
|
||||
<link rel="Stylesheet" type="text/css" href="../../style.css">
|
||||
<link rel="alternate" type="application/rss+xml" title="RSS" href="../../rss.xml">
|
||||
<title>Webhooks</title>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1">
|
||||
</head>
|
||||
<body>
|
||||
|
||||
|
||||
|
||||
<hr />
|
||||
<p>
|
||||
<a href="index.html">Index</a>
|
||||
<hr />
|
||||
</p>
|
||||
|
||||
<p>
|
||||
last 5 posts
|
||||
<hr />
|
||||
</p>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
<a href="1699558725-ref-290-submitted.html">REF-290 Submitted</a>
|
||||
|
||||
<li>
|
||||
<a href="1699375988-ref-209-start.html">REF-290: Start</a>
|
||||
|
||||
<li>
|
||||
<a href="1698642000-first-ticket.html">First Ticket</a>
|
||||
|
||||
<li>
|
||||
<a href="1693890000-blog-issue.html">Blog Issue</a>
|
||||
|
||||
<li>
|
||||
<a href="1693630800-hello-world.html">Hello World</a>
|
||||
|
||||
</ul>
|
||||
<hr />
|
||||
<p>
|
||||
<span id="-Date:"></span><strong id="Date:">Date:</strong> 2023/11/09
|
||||
</p>
|
||||
|
||||
<p>
|
||||
<span id="-Author:"></span><strong id="Author:">Author:</strong> Tristan Ancelet
|
||||
</p>
|
||||
|
||||
<div id="Webhooks"><h1 id="Webhooks" class="header"><a href="#Webhooks">Webhooks</a></h1></div>
|
||||
<div id="Webhooks-gitea"><h2 id="gitea" class="header"><a href="#Webhooks-gitea">gitea</a></h2></div>
|
||||
<hr />
|
||||
<p>
|
||||
I just recently started hosting my own gitserver (gitea). Had a few issues setting it up due to some default values in the gitea.service file (that prevented the program from using port 80).
|
||||
</p>
|
||||
|
||||
<p>
|
||||
After getting that dealt with I decided to see what I could do with gitea's support for webhooks. So I decided to setup a webhook that will handle updating my blog when I push to my <a href="https://git.arcanium.tech/tristan/blog-site">Blog Repo</a>.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
Once I push a new addition to the repo it now automatically makes a post request to my webhook server that will automatically update my website without manual intervention.
|
||||
</p>
|
||||
|
||||
|
||||
<div id="Webhooks-This Post"><h2 id="This Post" class="header"><a href="#Webhooks-This Post">This Post</a></h2></div>
|
||||
<hr />
|
||||
<p>
|
||||
This post was simply being used to test that functionality in gitea.
|
||||
</p>
|
||||
|
||||
</body>
|
||||
</html>
|
74
posts/personal/1700104768-new-job-offer.html
Normal file
74
posts/personal/1700104768-new-job-offer.html
Normal file
@@ -0,0 +1,74 @@
|
||||
<!DOCTYPE html>
|
||||
<html>
|
||||
<head>
|
||||
<link rel="Stylesheet" type="text/css" href="../../style.css">
|
||||
<link rel="alternate" type="application/rss+xml" title="RSS" href="../../rss.xml">
|
||||
<title>New Job Offer</title>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1">
|
||||
</head>
|
||||
<body>
|
||||
|
||||
|
||||
|
||||
<hr />
|
||||
<p>
|
||||
<a href="index.html">Index</a>
|
||||
<hr />
|
||||
</p>
|
||||
|
||||
<p>
|
||||
last 5 posts
|
||||
<hr />
|
||||
</p>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
<a href="1699564352-webhooks.html">Webhooks</a>
|
||||
|
||||
<li>
|
||||
<a href="1699558725-ref-290-submitted.html">REF-290 Submitted</a>
|
||||
|
||||
<li>
|
||||
<a href="1699375988-ref-209-start.html">REF-290: Start</a>
|
||||
|
||||
<li>
|
||||
<a href="1698642000-first-ticket.html">First Ticket</a>
|
||||
|
||||
<li>
|
||||
<a href="1693890000-blog-issue.html">Blog Issue</a>
|
||||
|
||||
</ul>
|
||||
<hr />
|
||||
<p>
|
||||
<span id="-Date:"></span><strong id="Date:">Date:</strong> 2023/11/15
|
||||
</p>
|
||||
|
||||
<p>
|
||||
<span id="-Author:"></span><strong id="Author:">Author:</strong> Tristan Ancelet
|
||||
</p>
|
||||
|
||||
|
||||
<div id="New Job Offer"><h1 id="New Job Offer" class="header"><a href="#New Job Offer">New Job Offer</a></h1></div>
|
||||
<div id="New Job Offer-The offer"><h2 id="The offer" class="header"><a href="#New Job Offer-The offer">The offer</a></h2></div>
|
||||
<p>
|
||||
Yea, as the post suggests I got a job offer from another company that want's to hire me as a Linux Systems Engineer.
|
||||
</p>
|
||||
|
||||
<div id="New Job Offer-The Company"><h2 id="The Company" class="header"><a href="#New Job Offer-The Company">The Company</a></h2></div>
|
||||
<p>
|
||||
The company being <a href="https://www.acumera.com/">Acumera</a>. I had one round of interviews with the hiring manager and one of their engineers. We had a really good time and I rather enjoyed the convo, as I got to talk about all of the work I do for my current company and the tools I've both made and used for work.
|
||||
</p>
|
||||
|
||||
<div id="New Job Offer-Struggles"><h2 id="Struggles" class="header"><a href="#New Job Offer-Struggles">Struggles</a></h2></div>
|
||||
<p>
|
||||
I've noticed working and getting job offers is dealing with actually accepting them. I've been working for my current company for about 2 years, and without going too far into it, I've had a really bad time due to lack of support. Mostly due to me being the sole person responsible for my companies infrastructure. I've told them several times that I've needed assistance handling our systems (as we have over 40 and each server is handling their own undocumented legacy applications and services. I do not have the time in the day to handle both admin and engineering duties. It has been over a year of this and honestly I can't take it anymore.
|
||||
</p>
|
||||
|
||||
<div id="New Job Offer-Will I take it"><h2 id="Will I take it" class="header"><a href="#New Job Offer-Will I take it">Will I take it</a></h2></div>
|
||||
<p>
|
||||
Yes I will proabably take it. The new position actually has me doing engieneering work with a team. Meaning I will not be the sole person to handle my workload. It will be shared. While the job will probably not be a cakewalk, I believe I will be able to handle it much better than my current workplace. As I will be doing my work, and not the work of an entire dept.
|
||||
</p>
|
||||
|
||||
</body>
|
||||
</html>
|
151
posts/personal/1700863814-auvik-trial.html
Normal file
151
posts/personal/1700863814-auvik-trial.html
Normal file
@@ -0,0 +1,151 @@
|
||||
<!DOCTYPE html>
|
||||
<html>
|
||||
<head>
|
||||
<link rel="Stylesheet" type="text/css" href="../../style.css">
|
||||
<link rel="alternate" type="application/rss+xml" title="RSS" href="../../rss.xml">
|
||||
<title>Auvik Trial</title>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1">
|
||||
</head>
|
||||
<body>
|
||||
|
||||
|
||||
|
||||
<hr />
|
||||
<p>
|
||||
<a href="index.html">Index</a>
|
||||
<hr />
|
||||
</p>
|
||||
|
||||
<p>
|
||||
last 5 posts
|
||||
<hr />
|
||||
</p>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
<a href="1700345096-busy-week.html">Busy Week</a>
|
||||
|
||||
<li>
|
||||
<a href="1700104768-new-job-offer.html">New Job Offer</a>
|
||||
|
||||
<li>
|
||||
<a href="1699564352-webhooks.html">Webhooks</a>
|
||||
|
||||
<li>
|
||||
<a href="1699558725-ref-290-submitted.html">REF-290 Submitted</a>
|
||||
|
||||
<li>
|
||||
<a href="1699375988-ref-209-start.html">REF-290: Start</a>
|
||||
|
||||
</ul>
|
||||
<hr />
|
||||
<p>
|
||||
<span id="-Date:"></span><strong id="Date:">Date:</strong> 2023/11/24
|
||||
</p>
|
||||
|
||||
<p>
|
||||
<span id="-Author:"></span><strong id="Author:">Author:</strong> Tristan Ancelet
|
||||
</p>
|
||||
|
||||
<div id="Auvik Trial"><h1 id="Auvik Trial" class="header"><a href="#Auvik Trial">Auvik Trial</a></h1></div>
|
||||
<div id="Auvik Trial-The Trial"><h2 id="The Trial" class="header"><a href="#Auvik Trial-The Trial">The Trial</a></h2></div>
|
||||
<hr />
|
||||
|
||||
<p>
|
||||
<a href="https://www.auvik.com/">Auvik</a> was providing a 14 day trial to test out their platform.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
I wasn't even aware of what Auvik even was until I came accross a "try Auvik and win a free Ubiquity Switch" ad. The primary factor for me messing with their paltform was admittedly the free switch.
|
||||
</p>
|
||||
|
||||
<div id="Auvik Trial-Their Platform"><h2 id="Their Platform" class="header"><a href="#Auvik Trial-Their Platform">Their Platform</a></h2></div>
|
||||
<hr />
|
||||
<p>
|
||||
Unbeknownst to me, their platform was akin to something I've just recently been working with at work. A network monitoring service, but instead of an on-prem solution it's based in the cloud with a collector/agent you have to install on a server in your network.
|
||||
</p>
|
||||
|
||||
|
||||
<div id="Auvik Trial-LibreNMS: At Work"><h2 id="LibreNMS: At Work" class="header"><a href="#Auvik Trial-LibreNMS: At Work">LibreNMS: At Work</a></h2></div>
|
||||
<hr />
|
||||
<p>
|
||||
At work we use Solarwinds almost exclusively, but recently in the engineering dept we decided to setup our own NMS with <a href="https://www.librenms.org/">LibreNMS</a>. A process that I setup in a <a href="https://git.arcanium.tech/tristan/myscripts/src/branch/master/install-librenms.sh">script</a> for ease-of-use for anyone else wanting to try it. It is an amazing project and I highly praise it for all of the functionality it brings.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
However, there are still some pain points with the project in terms of the network map. When viewing a network map, unless you've grouped up your devices in small enough network groups (doesn't help sometimes) your network map will be presented in a spider-web without any ability to resize or manipulate the map in any way (that makes it easier to read). Although this is where any gripes over LibreNMS starts and ends, as otherwise this is an amazing project that makes monitoring your network much more manageable.
|
||||
</p>
|
||||
|
||||
<div id="Auvik Trial-Auvik"><h2 id="Auvik" class="header"><a href="#Auvik Trial-Auvik">Auvik</a></h2></div>
|
||||
<div id="Auvik Trial-Auvik-Deployment & Setup"><h3 id="Deployment & Setup" class="header"><a href="#Auvik Trial-Auvik-Deployment & Setup">Deployment & Setup</a></h3></div>
|
||||
<hr />
|
||||
<p>
|
||||
Deploying their solution was insanely easy. I took the route of deploying their collector via a docker container (they generate you a docker compose file) on my VM Server, which only took a few minutes to download the necessary images and start it. Very soon after it connected back to their platform and began scanning my internal network.
|
||||
</p>
|
||||
|
||||
<div id="Auvik Trial-Auvik-Operation : Function"><h3 id="Operation : Function" class="header"><a href="#Auvik Trial-Auvik-Operation : Function">Operation : Function</a></h3></div>
|
||||
<hr />
|
||||
<p>
|
||||
Within 10 minutes their collector had mapped out (just about) every single VLAN and network I had running in my homelab (even the vnets running on my VM server). It really suprised me how invasive it was.
|
||||
</p>
|
||||
|
||||
<div id="Auvik Trial-Auvik-Operation : UX"><h3 id="Operation : UX" class="header"><a href="#Auvik Trial-Auvik-Operation : UX">Operation : UX</a></h3></div>
|
||||
<hr />
|
||||
<p>
|
||||
With my experience with Solarwinds, Zabbix and LibreNMS I didn't expect much in the way of UX from Auvik. However, I was plesantly suprised. The UI & UX for their platform was outstanding. Everything is laid out well and everything is formatted in a way that makes everything easy to read.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
For someone that despises Front-End work, I can appreciate the effort they've put into their product.
|
||||
</p>
|
||||
|
||||
<div id="Auvik Trial-Auvik-Operation : Features"><h3 id="Operation : Features" class="header"><a href="#Auvik Trial-Auvik-Operation : Features">Operation : Features</a></h3></div>
|
||||
<div id="Auvik Trial-Auvik-Operation : Features-Remote Management"><h4 id="Remote Management" class="header"><a href="#Auvik Trial-Auvik-Operation : Features-Remote Management">Remote Management</a></h4></div>
|
||||
<hr />
|
||||
<p>
|
||||
One of the features that I really like about this prouct is the "remote management" feature. While it does allow you to monitor your devices from the cloud, it also allows you to run commands and even get a shell on the device itself. It looks like it supports both telnet and ssh to get a shell on the device (provided you have configured the credentials).
|
||||
</p>
|
||||
|
||||
<p>
|
||||
LibreNMS lets you take a shortcut by pressing the "Telnet to <hostname>"/"SSH to <hostname>" that simply opens up a link in a new window in the format <code>ssh://<hostname></code> or <code>telnet://<hostname></code> and it's up to your desktop enviroment to interpret it and try to launch it in the default application to handle those connections. However, with Auvik they have a web-based terminal that allows you to access your devices from anywhere (provided the collector has access to the port needed to ssh or telnet to the device.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
This allows you to gain access to your devices and make changes without having to deal with VPN's or actually being on the network to do it locally. This is a very useful tool and one of the few features that I appreciate from the platform.
|
||||
</p>
|
||||
|
||||
<div id="Auvik Trial-Auvik-Operation : Features-Others"><h4 id="Others" class="header"><a href="#Auvik Trial-Auvik-Operation : Features-Others">Others</a></h4></div>
|
||||
<hr />
|
||||
<p>
|
||||
Unfortunately with the little time I was on the platform I wasn't able to delve into the depts of what it offers. However, from what I was able to see the offered the full stack of applications and services for your needs:
|
||||
</p>
|
||||
<ul>
|
||||
<li>
|
||||
SNMP monitoring
|
||||
|
||||
<li>
|
||||
Syslog
|
||||
|
||||
<li>
|
||||
Remote Management
|
||||
|
||||
<li>
|
||||
Network Map (best I've used so far on a NMS platform)
|
||||
|
||||
<li>
|
||||
Traffic Analysis
|
||||
|
||||
</ul>
|
||||
<p>
|
||||
There were probably much more that I just haven't seen, but this is the what I was able to see on the surface.
|
||||
</p>
|
||||
|
||||
<div id="Auvik Trial-Overall"><h2 id="Overall" class="header"><a href="#Auvik Trial-Overall">Overall</a></h2></div>
|
||||
<hr />
|
||||
<p>
|
||||
This is a really high-quality product I would like to use in my own lab, but due to it's black-box nature I wouldn't be ok with using it for my home network.
|
||||
</p>
|
||||
|
||||
</body>
|
||||
</html>
|
126
posts/personal/1702849369-zfs-upgrade-issue.html
Normal file
126
posts/personal/1702849369-zfs-upgrade-issue.html
Normal file
@@ -0,0 +1,126 @@
|
||||
<!DOCTYPE html>
|
||||
<html>
|
||||
<head>
|
||||
<link rel="Stylesheet" type="text/css" href="../../style.css">
|
||||
<link rel="alternate" type="application/rss+xml" title="RSS" href="../../rss.xml">
|
||||
<title>ZFS Upgrade Issue</title>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1">
|
||||
</head>
|
||||
<body>
|
||||
|
||||
|
||||
|
||||
<hr />
|
||||
<p>
|
||||
<a href="index.html">Index</a>
|
||||
<hr />
|
||||
</p>
|
||||
|
||||
<p>
|
||||
last 5 posts
|
||||
<hr />
|
||||
</p>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
<a href="1701545547-no-tickets.html">No Tickets</a>
|
||||
|
||||
<li>
|
||||
<a href="1700863814-auvik-trial.html">Auvik Trial</a>
|
||||
|
||||
<li>
|
||||
<a href="1700345096-busy-week.html">Busy Week</a>
|
||||
|
||||
<li>
|
||||
<a href="1700104768-new-job-offer.html">New Job Offer</a>
|
||||
|
||||
<li>
|
||||
<a href="1699564352-webhooks.html">Webhooks</a>
|
||||
|
||||
</ul>
|
||||
<p>
|
||||
<span id="-Date:"></span><strong id="Date:">Date:</strong> 2023/12/17
|
||||
</p>
|
||||
|
||||
<p>
|
||||
<span id="-Author:"></span><strong id="Author:">Author:</strong> Tristan Ancelet
|
||||
</p>
|
||||
|
||||
<div id="ZFS Upgrade Issue"><h1 id="ZFS Upgrade Issue" class="header"><a href="#ZFS Upgrade Issue">ZFS Upgrade Issue</a></h1></div>
|
||||
<div id="ZFS Upgrade Issue-Background"><h2 id="Background" class="header"><a href="#ZFS Upgrade Issue-Background">Background</a></h2></div>
|
||||
<hr />
|
||||
<p>
|
||||
I have an DIY Ubuntu NAS (one of the first few linux installs), and I was having aggravations with the zfs-dkms package that I had setup a couple of years ago to host raided pools for my NAS setup. However, recently during an update I noticed the kernel was updated on the machine to 6.2.0-39-generic which now caused the zfs-dkms to throw errors when apt would run mkinitcpio as the zfs-dkms-2.1.5 module only supported up to kernel 5.19.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
While it didn't exactly cause any issues with the zfs installation there was currently (it still functioned fine even with the new kernel). I got tired of it so I decided to compile openzfs from source and install it on my system.
|
||||
</p>
|
||||
|
||||
<pre bash>
|
||||
## Run as root
|
||||
# sudo -i
|
||||
|
||||
git clone https://github.com/openzfs/zfs
|
||||
|
||||
## I was missing a few dependencies but installed them like so
|
||||
apt install uuid-dev libblkid-dev
|
||||
|
||||
cd zfs
|
||||
## Run the autoconf autogen script
|
||||
./autogen.sh
|
||||
## Run the configure script to build the Makefile
|
||||
./configure
|
||||
|
||||
## Build the module to make sure everything goes ok
|
||||
make
|
||||
|
||||
## Had to add the extra modules to the depmod search ath
|
||||
depmod_cont="$(</etc/depmod.d/ubuntu.conf)"
|
||||
## Replace "search" with "search extra" to put the extra modules into the depmod path
|
||||
depmod_cont="${depmod_cont/search/search extra}"
|
||||
echo "$depmod_cont" > /etc/depmod.d/ubuntu.conf
|
||||
|
||||
## Build and intall
|
||||
make install
|
||||
|
||||
## Run ldconfig
|
||||
ldconfig
|
||||
|
||||
## Run depmod
|
||||
depmod
|
||||
</pre>
|
||||
|
||||
|
||||
<div id="ZFS Upgrade Issue-Other issues"><h2 id="Other issues" class="header"><a href="#ZFS Upgrade Issue-Other issues">Other issues</a></h2></div>
|
||||
<div id="ZFS Upgrade Issue-Other issues-Zpools not importing"><h3 id="Zpools not importing" class="header"><a href="#ZFS Upgrade Issue-Other issues-Zpools not importing">Zpools not importing</a></h3></div>
|
||||
<hr />
|
||||
<p>
|
||||
Upon finishing installation and reboot I noticed that when the server rebooted it didn't mount the pools on boot. I always had to import them manually <code>zpool import data && zpool import media</code>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
I was confused because the configs setup by my dkms installation were still valid <code>/etc/defaults/zfs</code>.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
While it took me an hour to figure it out, I eventually figured out what was wrong and why zfs wasn't importing my pools.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
the services configured in /usr/lib/systemd/system were setup with the path that bsd/unix would use for the zpool.cache file (<code>/usr/local/etc/zfs/zpool.cache</code>) instead of what zfs was configured with on my zfs-dkms installation (<code>/etc/zfs/zpool.cache</code>).
|
||||
</p>
|
||||
|
||||
<div id="ZFS Upgrade Issue-Other issues-Resolution"><h3 id="Resolution" class="header"><a href="#ZFS Upgrade Issue-Other issues-Resolution">Resolution</a></h3></div>
|
||||
<hr />
|
||||
<p>
|
||||
All I ended up needing to do was change the path's that the service files from <code>/usr/local/etc/zfs/zpool.cache</code> to <code>/etc/zfs/zpool.cache</code> (wherever applicable).
|
||||
</p>
|
||||
|
||||
<p>
|
||||
After doing that and rebooting the pools were imported and mounted as they previously had.
|
||||
</p>
|
||||
|
||||
</body>
|
||||
</html>
|
Reference in New Issue
Block a user