From 6a0434a998a9a6457bf266a8658a45f6c39cd012 Mon Sep 17 00:00:00 2001 From: Trent Palmer Date: Thu, 7 Sep 2017 09:50:46 -0700 Subject: [PATCH] extend docs/misc_tips_troubleshooting.md with zfs disk error tip --- docs/misc_tips_troubleshooting.md | 8 ++++++ site/index.html | 2 +- site/misc_tips_troubleshooting/index.html | 7 ++++++ site/mkdocs/search_index.json | 7 +++++- site/sitemap.xml | 30 +++++++++++------------ 5 files changed, 37 insertions(+), 17 deletions(-) diff --git a/docs/misc_tips_troubleshooting.md b/docs/misc_tips_troubleshooting.md index 2b98ab8..45d8e96 100644 --- a/docs/misc_tips_troubleshooting.md +++ b/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`. diff --git a/site/index.html b/site/index.html index 6d4a58e..c860502 100644 --- a/site/index.html +++ b/site/index.html @@ -234,5 +234,5 @@ diff --git a/site/misc_tips_troubleshooting/index.html b/site/misc_tips_troubleshooting/index.html index 8021001..df142f2 100644 --- a/site/misc_tips_troubleshooting/index.html +++ b/site/misc_tips_troubleshooting/index.html @@ -131,6 +131,8 @@
  • Updating Caddy Server
    • +
  • ZFS Disc Error Disc Identification
    • + @@ -231,6 +233,11 @@ Also, WTF?

    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.

    diff --git a/site/mkdocs/search_index.json b/site/mkdocs/search_index.json index e516b2a..47bef30 100644 --- a/site/mkdocs/search_index.json +++ b/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 \"\"\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 \n# publish image of container to local *storage*\nlxc publish --alias \n# export the new image to tarball\nlxc image export \n# scp tarball to other box\nscp a4762b114fecee2e2bc227b9032405642c5286c02009babef7953e011e597bfe.tar.gz server:\n# on other box import the image\nlxc image import --alias \n# launch container\nlxc launch \n# assign profile to container\nlxc profile assign \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 \"\"\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 \n# publish image of container to local *storage*\nlxc publish --alias \n# export the new image to tarball\nlxc image export \n# scp tarball to other box\nscp a4762b114fecee2e2bc227b9032405642c5286c02009babef7953e011e597bfe.tar.gz server:\n# on other box import the image\nlxc image import --alias \n# launch container\nlxc launch \n# assign profile to container\nlxc profile assign \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.", diff --git a/site/sitemap.xml b/site/sitemap.xml index 1d3773b..4c7b094 100644 --- a/site/sitemap.xml +++ b/site/sitemap.xml @@ -4,7 +4,7 @@ / - 2017-08-22 + 2017-09-07 daily @@ -12,7 +12,7 @@ /apt_pinning_artful_aardvark_packages_in_xenial_xerus/ - 2017-08-22 + 2017-09-07 daily @@ -20,7 +20,7 @@ /lxd_container_home_server_networking_for_dummies/ - 2017-08-22 + 2017-09-07 daily @@ -28,7 +28,7 @@ /how_to_reassign_a_static_ip_address_with_dnsmasq/ - 2017-08-22 + 2017-09-07 daily @@ -36,7 +36,7 @@ /serve_and_share_apps_from_your_phone_with_fdroid/ - 2017-08-22 + 2017-09-07 daily @@ -44,7 +44,7 @@ /nspawn/ - 2017-08-22 + 2017-09-07 daily @@ -52,7 +52,7 @@ /gentoo_lxd_container/ - 2017-08-22 + 2017-09-07 daily @@ -60,7 +60,7 @@ /mastodon_on_arch/ - 2017-08-22 + 2017-09-07 daily @@ -68,7 +68,7 @@ /debian_nspawn_container_on_arch_for_testing_apache_configurations/ - 2017-08-22 + 2017-09-07 daily @@ -76,7 +76,7 @@ /dynamic_cacheing_nginx_reverse_proxy_for_pacman/ - 2017-08-22 + 2017-09-07 daily @@ -84,7 +84,7 @@ /freebsd_jails_on_freenas/ - 2017-08-22 + 2017-09-07 daily @@ -92,7 +92,7 @@ /arch_redis_nspawn/ - 2017-08-22 + 2017-09-07 daily @@ -100,7 +100,7 @@ /arch_postgresql_nspawn/ - 2017-08-22 + 2017-09-07 daily @@ -108,7 +108,7 @@ /misc_tips_troubleshooting/ - 2017-08-22 + 2017-09-07 daily @@ -116,7 +116,7 @@ /self_signed_certs/ - 2017-08-22 + 2017-09-07 daily