extend docs/misc_tips_troubleshooting.md with zfs disk error tip

docs/misc_tips_troubleshooting.md

@@ -72,3 +72,11 @@ You update Caddy Server with a new Go Binary, try to restart caddy.service, and
 Maybe you get an error message such as the following `listen tcp :80: bind: permission denied` and/or
 `listen tcp :443: bind: permission denied`.  
 Fix this error with the following command `sudo setcap CAP_NET_BIND_SERVICE=+eip /path/to/caddy`
+
+## ZFS Disc Error Disc Identification
+
+You created a zpool using /dev/disk-by-id to specify the devices, and now you want to figure out
+which disks are causing you trouble.  For instance, your system log, `journalctl | grep -i fail`
+shows read error on /dev/sdc.  
+
+You can use `lsblk -o MODEL,SERIAL` to match the information generated by `zpool status`.

site/index.html

@@ -234,5 +234,5 @@
 
 <!--
 MkDocs version : 0.16.3
-Build Date UTC : 2017-08-22 10:01:29
+Build Date UTC : 2017-09-07 16:50:29
 -->

site/misc_tips_troubleshooting/index.html

@@ -131,6 +131,8 @@
         
             <li><a class="toctree-l3" href="#updating-caddy-server">Updating Caddy Server</a></li>
         
+            <li><a class="toctree-l3" href="#zfs-disc-error-disc-identification">ZFS Disc Error Disc Identification</a></li>
+        
         </ul>
     
 
@@ -231,6 +233,11 @@ Also, WTF?</p>
 Maybe you get an error message such as the following <code>listen tcp :80: bind: permission denied</code> and/or
 <code>listen tcp :443: bind: permission denied</code>.<br />
 Fix this error with the following command <code>sudo setcap CAP_NET_BIND_SERVICE=+eip /path/to/caddy</code></p>
+<h2 id="zfs-disc-error-disc-identification">ZFS Disc Error Disc Identification</h2>
+<p>You created a zpool using /dev/disk-by-id to specify the devices, and now you want to figure out
+which disks are causing you trouble.  For instance, your system log, <code>journalctl | grep -i fail</code>
+shows read error on /dev/sdc.  </p>
+<p>You can use <code>lsblk -o MODEL,SERIAL</code> to match the information generated by <code>zpool status</code>.</p>
               
             </div>
           </div>

site/mkdocs/search_index.json

@@ -467,7 +467,7 @@
         },
         {
             "location": "/misc_tips_troubleshooting/",
-            "text": "Misc Tips, TroubleShooting\n\n\nSending commands to LXD containers\n\n\nUse \nbash -c \"<command>\"\n for commands with wildcards. i.e.\n\n\nfor machine in $(lxc list | grep RUNNING | awk '{print $2}') ;\\\n    do lxc exec \"${machine}\" -- bash -c \"cat /etc/apt/apt.conf.d/02*\" ; done\n\n\n\n\nfish shell is actually a little bit cleaner\n\n\nfor machine in (lxc list | grep RUNNING | awk '{print $2}') ; \\\n    lxc exec $machine -- bash -c \"cat /etc/apt/apt.conf.d/02*\" ; end\n\n\n\n\n# change all their time zones\nfor machine in (lxc list | grep RUNNING | awk '{print $2}') ; \\\n    lxc exec $machine -- bash -c \"timedatectl set-timezone America/Los_Angeles\" ; end\n# check to see if anyone is logged in before rebooting\nfor machine in (lxc list | grep RUNNING | awk '{print $2}') ; echo ; \\\n    echo $machine ; lxc exec $machine -- bash -c \"who\" ; end \n\n\n\n\nMove LXD container to another Server\n\n\n# stop the container\nlxc stop <container name>\n# publish image of container to local *storage*\nlxc publish <container name> --alias <image name>\n# export the new image to tarball\nlxc image export <image name>\n# scp tarball to other box\nscp a4762b114fecee2e2bc227b9032405642c5286c02009babef7953e011e597bfe.tar.gz server:\n# on other box import the image\nlxc image import <tarball file name> --alias <image name>\n# launch container\nlxc launch <image name> <container name>\n# assign profile to container\nlxc profile assign <container name> <profile name>\n\n\n\n\nShell into the new running container, update any network interface\nconfigurations that you need to, and then restart the container.\n\n\nSee also\n\nLXD Container Home Server Networking For Dummies\n\n\nUbuntu-Mate-Welcome-Center doesn't work some for some repos\n\n\nPerhaps your apt-cacher-ng proxy server isn't configured to allow \ntraffic through from https sources. Make sure the following is\nuncommented. This applies for all PPA's that use https.\n\n\n# /etc/apt-cacher-ng/acng.conf\nPassThroughPattern: .*\n\n\n\n\nQuitting Mosh\n\n\nThe key combination to quit mosh it \nctrl+6+.\n\nAlso, WTF?\n\n\nUpdating Caddy Server\n\n\nYou update Caddy Server with a new Go Binary, try to restart caddy.service, and it fails.\nMaybe you get an error message such as the following \nlisten tcp :80: bind: permission denied\n and/or\n\nlisten tcp :443: bind: permission denied\n.\n\nFix this error with the following command \nsudo setcap CAP_NET_BIND_SERVICE=+eip /path/to/caddy",
+            "text": "Misc Tips, TroubleShooting\n\n\nSending commands to LXD containers\n\n\nUse \nbash -c \"<command>\"\n for commands with wildcards. i.e.\n\n\nfor machine in $(lxc list | grep RUNNING | awk '{print $2}') ;\\\n    do lxc exec \"${machine}\" -- bash -c \"cat /etc/apt/apt.conf.d/02*\" ; done\n\n\n\n\nfish shell is actually a little bit cleaner\n\n\nfor machine in (lxc list | grep RUNNING | awk '{print $2}') ; \\\n    lxc exec $machine -- bash -c \"cat /etc/apt/apt.conf.d/02*\" ; end\n\n\n\n\n# change all their time zones\nfor machine in (lxc list | grep RUNNING | awk '{print $2}') ; \\\n    lxc exec $machine -- bash -c \"timedatectl set-timezone America/Los_Angeles\" ; end\n# check to see if anyone is logged in before rebooting\nfor machine in (lxc list | grep RUNNING | awk '{print $2}') ; echo ; \\\n    echo $machine ; lxc exec $machine -- bash -c \"who\" ; end \n\n\n\n\nMove LXD container to another Server\n\n\n# stop the container\nlxc stop <container name>\n# publish image of container to local *storage*\nlxc publish <container name> --alias <image name>\n# export the new image to tarball\nlxc image export <image name>\n# scp tarball to other box\nscp a4762b114fecee2e2bc227b9032405642c5286c02009babef7953e011e597bfe.tar.gz server:\n# on other box import the image\nlxc image import <tarball file name> --alias <image name>\n# launch container\nlxc launch <image name> <container name>\n# assign profile to container\nlxc profile assign <container name> <profile name>\n\n\n\n\nShell into the new running container, update any network interface\nconfigurations that you need to, and then restart the container.\n\n\nSee also\n\nLXD Container Home Server Networking For Dummies\n\n\nUbuntu-Mate-Welcome-Center doesn't work some for some repos\n\n\nPerhaps your apt-cacher-ng proxy server isn't configured to allow \ntraffic through from https sources. Make sure the following is\nuncommented. This applies for all PPA's that use https.\n\n\n# /etc/apt-cacher-ng/acng.conf\nPassThroughPattern: .*\n\n\n\n\nQuitting Mosh\n\n\nThe key combination to quit mosh it \nctrl+6+.\n\nAlso, WTF?\n\n\nUpdating Caddy Server\n\n\nYou update Caddy Server with a new Go Binary, try to restart caddy.service, and it fails.\nMaybe you get an error message such as the following \nlisten tcp :80: bind: permission denied\n and/or\n\nlisten tcp :443: bind: permission denied\n.\n\nFix this error with the following command \nsudo setcap CAP_NET_BIND_SERVICE=+eip /path/to/caddy\n\n\nZFS Disc Error Disc Identification\n\n\nYou created a zpool using /dev/disk-by-id to specify the devices, and now you want to figure out\nwhich disks are causing you trouble.  For instance, your system log, \njournalctl | grep -i fail\n\nshows read error on /dev/sdc.  \n\n\nYou can use \nlsblk -o MODEL,SERIAL\n to match the information generated by \nzpool status\n.",
             "title": "Misc Tips, Trouble Shooting"
         },
         {
@@ -500,6 +500,11 @@
             "text": "You update Caddy Server with a new Go Binary, try to restart caddy.service, and it fails.\nMaybe you get an error message such as the following  listen tcp :80: bind: permission denied  and/or listen tcp :443: bind: permission denied . \nFix this error with the following command  sudo setcap CAP_NET_BIND_SERVICE=+eip /path/to/caddy",
             "title": "Updating Caddy Server"
         },
+        {
+            "location": "/misc_tips_troubleshooting/#zfs-disc-error-disc-identification",
+            "text": "You created a zpool using /dev/disk-by-id to specify the devices, and now you want to figure out\nwhich disks are causing you trouble.  For instance, your system log,  journalctl | grep -i fail \nshows read error on /dev/sdc.    You can use  lsblk -o MODEL,SERIAL  to match the information generated by  zpool status .",
+            "title": "ZFS Disc Error Disc Identification"
+        },
         {
             "location": "/self_signed_certs/",
             "text": "Setting up Self-Signed Certs\n\n\nThis \njamielinux\n\nblog post looks promising.",

site/sitemap.xml

@@ -4,7 +4,7 @@
     
     <url>
      <loc>/</loc>
-     <lastmod>2017-08-22</lastmod>
+     <lastmod>2017-09-07</lastmod>
      <changefreq>daily</changefreq>
     </url>
     
@@ -12,7 +12,7 @@
     
     <url>
      <loc>/apt_pinning_artful_aardvark_packages_in_xenial_xerus/</loc>
-     <lastmod>2017-08-22</lastmod>
+     <lastmod>2017-09-07</lastmod>
      <changefreq>daily</changefreq>
     </url>
     
@@ -20,7 +20,7 @@
     
     <url>
      <loc>/lxd_container_home_server_networking_for_dummies/</loc>
-     <lastmod>2017-08-22</lastmod>
+     <lastmod>2017-09-07</lastmod>
      <changefreq>daily</changefreq>
     </url>
     
@@ -28,7 +28,7 @@
     
     <url>
      <loc>/how_to_reassign_a_static_ip_address_with_dnsmasq/</loc>
-     <lastmod>2017-08-22</lastmod>
+     <lastmod>2017-09-07</lastmod>
      <changefreq>daily</changefreq>
     </url>
     
@@ -36,7 +36,7 @@
     
     <url>
      <loc>/serve_and_share_apps_from_your_phone_with_fdroid/</loc>
-     <lastmod>2017-08-22</lastmod>
+     <lastmod>2017-09-07</lastmod>
      <changefreq>daily</changefreq>
     </url>
     
@@ -44,7 +44,7 @@
     
     <url>
      <loc>/nspawn/</loc>
-     <lastmod>2017-08-22</lastmod>
+     <lastmod>2017-09-07</lastmod>
      <changefreq>daily</changefreq>
     </url>
     
@@ -52,7 +52,7 @@
     
     <url>
      <loc>/gentoo_lxd_container/</loc>
-     <lastmod>2017-08-22</lastmod>
+     <lastmod>2017-09-07</lastmod>
      <changefreq>daily</changefreq>
     </url>
     
@@ -60,7 +60,7 @@
     
     <url>
      <loc>/mastodon_on_arch/</loc>
-     <lastmod>2017-08-22</lastmod>
+     <lastmod>2017-09-07</lastmod>
      <changefreq>daily</changefreq>
     </url>
     
@@ -68,7 +68,7 @@
     
     <url>
      <loc>/debian_nspawn_container_on_arch_for_testing_apache_configurations/</loc>
-     <lastmod>2017-08-22</lastmod>
+     <lastmod>2017-09-07</lastmod>
      <changefreq>daily</changefreq>
     </url>
     
@@ -76,7 +76,7 @@
     
     <url>
      <loc>/dynamic_cacheing_nginx_reverse_proxy_for_pacman/</loc>
-     <lastmod>2017-08-22</lastmod>
+     <lastmod>2017-09-07</lastmod>
      <changefreq>daily</changefreq>
     </url>
     
@@ -84,7 +84,7 @@
     
     <url>
      <loc>/freebsd_jails_on_freenas/</loc>
-     <lastmod>2017-08-22</lastmod>
+     <lastmod>2017-09-07</lastmod>
      <changefreq>daily</changefreq>
     </url>
     
@@ -92,7 +92,7 @@
     
     <url>
      <loc>/arch_redis_nspawn/</loc>
-     <lastmod>2017-08-22</lastmod>
+     <lastmod>2017-09-07</lastmod>
      <changefreq>daily</changefreq>
     </url>
     
@@ -100,7 +100,7 @@
     
     <url>
      <loc>/arch_postgresql_nspawn/</loc>
-     <lastmod>2017-08-22</lastmod>
+     <lastmod>2017-09-07</lastmod>
      <changefreq>daily</changefreq>
     </url>
     
@@ -108,7 +108,7 @@
     
     <url>
      <loc>/misc_tips_troubleshooting/</loc>
-     <lastmod>2017-08-22</lastmod>
+     <lastmod>2017-09-07</lastmod>
      <changefreq>daily</changefreq>
     </url>
     
@@ -116,7 +116,7 @@
     
     <url>
      <loc>/self_signed_certs/</loc>
-     <lastmod>2017-08-22</lastmod>
+     <lastmod>2017-09-07</lastmod>
      <changefreq>daily</changefreq>
     </url>