Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #265863 > unrolled thread
| Started by | gene heskett <gheskett@shentel.net> |
|---|---|
| First post | 2024-01-13 03:50 +0100 |
| Last post | 2024-01-19 21:10 +0100 |
| Articles | 20 on this page of 167 — 25 participants |
Back to article view | Back to linux.debian.user
smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-13 03:50 +0100
Re: smartctl cannot access my storage, need syntax help "Gareth Evans" <donotspam@fastmail.fm> - 2024-01-13 04:00 +0100
Re: smartctl cannot access my storage, need syntax help Andy Smith <andy@strugglers.net> - 2024-01-13 04:00 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-13 06:00 +0100
Re: smartctl cannot access my storage, need syntax help Andy Smith <andy@strugglers.net> - 2024-01-13 16:50 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-13 18:10 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-13 18:30 +0100
Re: smartctl cannot access my storage, need syntax help Andy Smith <andy@strugglers.net> - 2024-01-13 19:50 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-14 00:30 +0100
Re: smartctl cannot access my storage, need syntax help Steve McIntyre <steve@einval.com> - 2024-01-14 14:40 +0100
Re: smartctl cannot access my storage, need syntax help Nicolas George <george@nsup.org> - 2024-01-14 11:40 +0100
Re: smartctl cannot access my storage, need syntax help Andy Smith <andy@strugglers.net> - 2024-01-14 17:30 +0100
Re: smartctl cannot access my storage, need syntax help Charles Curley <charlescurley@charlescurley.com> - 2024-01-13 06:40 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-14 13:50 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-14 20:50 +0100
Re: smartctl cannot access my storage, need syntax help David Wright <deblis@lionunicorn.co.uk> - 2024-01-15 01:50 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-15 02:20 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-15 14:50 +0100
Re: smartctl cannot access my storage, need syntax help Felix Miata <mrmazda@earthlink.net> - 2024-01-15 19:50 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-15 23:00 +0100
Re: smartctl cannot access my storage, need syntax help David Wright <deblis@lionunicorn.co.uk> - 2024-01-15 21:00 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-16 00:20 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-16 01:00 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-16 01:10 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-16 00:50 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-16 01:10 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-16 01:20 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-16 02:40 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-16 03:20 +0100
Re: smartctl cannot access my storage, need syntax help David Wright <deblis@lionunicorn.co.uk> - 2024-01-16 04:00 +0100
Re: smartctl cannot access my storage, need syntax help Felix Miata <mrmazda@earthlink.net> - 2024-01-16 07:00 +0100
Re: smartctl cannot access my storage, need syntax help Tom Furie <tom@furie.org.uk> - 2024-01-16 09:20 +0100
Re: smartctl cannot access my storage, need syntax help Felix Miata <mrmazda@earthlink.net> - 2024-01-16 12:10 +0100
Re: smartctl cannot access my storage, need syntax help Valerio Vanni <valerio.vanni@inwind.it> - 2024-01-16 13:40 +0100
Re: smartctl cannot access my storage, need syntax help David Wright <deblis@lionunicorn.co.uk> - 2024-01-17 01:20 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-17 03:00 +0100
Re: smartctl cannot access my storage, need syntax help Max Nikulin <manikulin@gmail.com> - 2024-01-16 16:00 +0100
Re: smartctl cannot access my storage, need syntax help David Wright <deblis@lionunicorn.co.uk> - 2024-01-16 15:10 +0100
Re: smartctl cannot access my storage, need syntax help Felix Miata <mrmazda@earthlink.net> - 2024-01-16 15:40 +0100
Re: smartctl cannot access my storage, need syntax help Greg Wooledge <greg@wooledge.org> - 2024-01-16 15:50 +0100
Re: smartctl cannot access my storage, need syntax help David Wright <deblis@lionunicorn.co.uk> - 2024-01-17 01:20 +0100
Re: smartctl cannot access my storage, need syntax help "Thomas Schmitt" <scdbackup@gmx.net> - 2024-01-16 17:10 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-17 03:20 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-17 07:00 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-17 15:30 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-17 18:10 +0100
Re: smartctl cannot access my storage, need syntax help "Thomas Schmitt" <scdbackup@gmx.net> - 2024-01-17 18:30 +0100
Re: smartctl cannot access my storage, need syntax help "Thomas Schmitt" <scdbackup@gmx.net> - 2024-01-17 20:40 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-17 21:40 +0100
Re: smartctl cannot access my storage, need syntax help "Thomas Schmitt" <scdbackup@gmx.net> - 2024-01-17 22:20 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-17 22:40 +0100
normally start new xterms [was: Re: smartctl cannot access my storage, need syntax help] Max Nikulin <manikulin@gmail.com> - 2024-01-18 17:40 +0100
Re: normally start new xterms "Thomas Schmitt" <scdbackup@gmx.net> - 2024-01-18 20:10 +0100
Re: normally start new xterms conover@panix.com (John Conover) - 2024-01-18 20:20 +0100
Re: normally start new xterms "Thomas Schmitt" <scdbackup@gmx.net> - 2024-01-18 21:20 +0100
Re: normally start new xterms conover@panix.com (John Conover) - 2024-01-18 21:40 +0100
Re: normally start new xterms <tomas@tuxteam.de> - 2024-01-19 06:50 +0100
Re: normally start new xterms <tomas@tuxteam.de> - 2024-01-19 09:10 +0100
Re: normally start new xterms "Thomas Schmitt" <scdbackup@gmx.net> - 2024-01-19 10:20 +0100
Re: normally start new xterms <tomas@tuxteam.de> - 2024-01-19 10:40 +0100
Re: normally start new xterms "Thomas Schmitt" <scdbackup@gmx.net> - 2024-01-19 09:10 +0100
Re: normally start new xterms David Wright <deblis@lionunicorn.co.uk> - 2024-01-19 18:10 +0100
Re: normally start new xterms Henning Follmann <hfollmann@itcfollmann.com> - 2024-01-19 15:20 +0100
Re: normally start new xterms <tomas@tuxteam.de> - 2024-01-19 16:10 +0100
Re: smartctl cannot access my storage, need syntax help David Wright <deblis@lionunicorn.co.uk> - 2024-01-18 04:50 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-17 22:20 +0100
Re: smartctl cannot access my storage, need syntax help "Thomas Schmitt" <scdbackup@gmx.net> - 2024-01-17 08:50 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-17 16:40 +0100
Re: smartctl cannot access my storage, need syntax help "Thomas Schmitt" <scdbackup@gmx.net> - 2024-01-17 17:40 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-17 21:20 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-17 22:10 +0100
Re: smartctl cannot access my storage, need syntax help Curt <curty@free.fr> - 2024-01-17 17:40 +0100
Re: smartctl cannot access my storage, need syntax help "Thomas Schmitt" <scdbackup@gmx.net> - 2024-01-17 18:20 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-17 21:40 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-17 22:50 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-18 01:00 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-18 02:00 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-18 05:30 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-18 07:00 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-18 07:50 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-18 10:00 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-18 12:50 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-18 22:10 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-19 07:00 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-19 08:30 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-19 22:00 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-20 01:20 +0100
Re: smartctl cannot access my storage, need syntax help Felix Miata <mrmazda@earthlink.net> - 2024-01-20 02:30 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-20 06:40 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-20 08:00 +0100
Re: smartctl cannot access my storage, need syntax help Max Nikulin <manikulin@gmail.com> - 2024-01-20 16:30 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-20 21:30 +0100
Re: smartctl cannot access my storage, need syntax help Max Nikulin <manikulin@gmail.com> - 2024-01-21 06:40 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-21 07:40 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-21 12:50 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-21 22:20 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-21 23:50 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-22 00:30 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-22 06:50 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-22 10:50 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-22 12:30 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-22 19:00 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-22 20:40 +0100
Re: smartctl cannot access my storage, need syntax help Stefan Monnier <monnier@iro.umontreal.ca> - 2024-01-22 22:10 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-23 00:50 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-23 03:50 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-23 04:00 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-23 05:00 +0100
Powered USB hub [was: Re: smartctl cannot access my storage, need syntax help] Max Nikulin <manikulin@gmail.com> - 2024-01-23 05:20 +0100
Re: Powered USB hub [was: Re: smartctl cannot access my storage, needsyntax help] gene heskett <gheskett@shentel.net> - 2024-01-23 06:10 +0100
Re: Powered USB hub [was: Re: smartctl cannot access my storage, need syntax help] Anssi Saari <anssi.saari@debian-user.mail.kapsi.fi> - 2024-01-25 11:00 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-23 08:40 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-23 12:10 +0100
Re: smartctl cannot access my storage, need syntax help Stefan Monnier <monnier@iro.umontreal.ca> - 2024-01-23 04:50 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-23 12:50 +0100
Re: smartctl cannot access my storage, need syntax help Karl Vogel <vogelke@pobox.com> - 2024-01-23 06:40 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-23 12:10 +0100
Re: smartctl cannot access my storage, need syntax help Gremlin <scott-andrews@columbus.rr.com> - 2024-01-23 12:20 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-23 12:40 +0100
Re: smartctl cannot access my storage, need syntax help Anssi Saari <anssi.saari@debian-user.mail.kapsi.fi> - 2024-01-25 15:10 +0100
Re: smartctl cannot access my storage, need syntax help "Roy J. Tellason, Sr." <roy@rtellason.com> - 2024-01-25 18:20 +0100
Re: smartctl cannot access my storage, need syntax help Anssi Saari <anssi.saari@debian-user.mail.kapsi.fi> - 2024-01-26 12:50 +0100
Re: smartctl cannot access my storage, need syntax help David Wright <deblis@lionunicorn.co.uk> - 2024-01-29 06:20 +0100
Re: smartctl cannot access my storage, need syntax help Karl Vogel <vogelke@pobox.com> - 2024-01-24 09:30 +0100
Re: smartctl cannot access my storage, need syntax help Max Nikulin <manikulin@gmail.com> - 2024-01-21 10:40 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-21 18:40 +0100
Re: smartctl cannot access my storage, need syntax help David Wright <deblis@lionunicorn.co.uk> - 2024-01-19 05:10 +0100
Re: smartctl cannot access my storage, need syntax help "Thomas Schmitt" <scdbackup@gmx.net> - 2024-01-18 08:40 +0100
Re: smartctl cannot access my storage, need syntax help Anssi Saari <anssi.saari@debian-user.mail.kapsi.fi> - 2024-01-19 09:20 +0100
Re: smartctl cannot access my storage, need syntax help "Thomas Schmitt" <scdbackup@gmx.net> - 2024-01-19 11:00 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-19 13:10 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-19 13:00 +0100
Re: smartctl cannot access my storage, need syntax help Curt <curty@free.fr> - 2024-01-18 17:40 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-17 21:20 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-17 18:10 +0100
Re: smartctl cannot access my storage, need syntax help Charles Curley <charlescurley@charlescurley.com> - 2024-01-18 08:20 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-17 02:10 +0100
Re: smartctl cannot access my storage, need syntax help David Wright <deblis@lionunicorn.co.uk> - 2024-01-17 03:00 +0100
Re: smartctl cannot access my storage, need syntax help Felix Miata <mrmazda@earthlink.net> - 2024-01-17 05:10 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-15 08:50 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-15 15:50 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-15 23:00 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-16 00:40 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-16 00:50 +0100
Re: smartctl cannot access my storage, need syntax help Felix Miata <mrmazda@earthlink.net> - 2024-01-16 07:10 +0100
Re: smartctl cannot access my storage, need syntax help Felix Miata <mrmazda@earthlink.net> - 2024-01-16 07:20 +0100
Re: smartctl cannot access my storage, need syntax help Andy Smith <andy@strugglers.net> - 2024-01-16 17:40 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-17 02:50 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-17 02:30 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-15 17:10 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-16 00:10 +0100
Re: smartctl cannot access my storage, need syntax help Franco Martelli <martellif67@gmail.com> - 2024-01-16 21:00 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-16 22:10 +0100
To partition or not to partition MD arrays (Was Re: smartctl cannot access my storage, need syntax help) Andy Smith <andy@strugglers.net> - 2024-01-16 22:40 +0100
Re: To partition or not to partition MD arrays (Was Re: smartctl cannot access my storage, need syntax help) Steve McIntyre <steve@einval.com> - 2024-01-18 02:00 +0100
Re: To partition or not to partition MD arrays (Was Re: smartctl cannotaccess my storage, need syntax help) gene heskett <gheskett@shentel.net> - 2024-01-18 04:40 +0100
Re: To partition or not to partition MD arrays (Was Re: smartctl cannotaccess my storage, need syntax help) Nicholas Geovanis <nickgeovanis@gmail.com> - 2024-01-18 17:30 +0100
Re: To partition or not to partition MD arrays (Was Re: smartctl cannotaccess my storage, need syntax help) Andy Smith <andy@strugglers.net> - 2024-01-18 18:10 +0100
Re: To partition or not to partition MD arrays (Was Re: smartctl cannot access my storage, need syntax help) Andy Smith <andy@strugglers.net> - 2024-01-18 15:20 +0100
Re: To partition or not to partition MD arrays (Was Re: smartctl cannot access my storage, need syntax help) Steve McIntyre <steve@einval.com> - 2024-01-18 17:10 +0100
Re: mdraid construction and testing (was: smartctl cannot access my stor...) Felix Miata <mrmazda@earthlink.net> - 2024-01-16 23:00 +0100
Testing storage performance (Was Re: mdraid construction and testing (was: smartctl cannot access my stor...)) Andy Smith <andy@strugglers.net> - 2024-01-17 04:40 +0100
Re: smartctl cannot access my storage, need syntax help Anssi Saari <anssi.saari@debian-user.mail.kapsi.fi> - 2024-01-19 09:10 +0100
Re: To partition or not to partition MD arrays (Was Re: smartctl cannotaccess my storage, need syntax help) Franco Martelli <martellif67@gmail.com> - 2024-01-19 20:10 +0100
Re: To partition or not to partition MD arrays (Was Re: smartctl cannotaccess my storage, need syntax help) Nicolas George <george@nsup.org> - 2024-01-19 20:20 +0100
Re: To partition or not to partition MD arrays (Was Re: smartctl cannotaccess my storage, need syntax help) Franco Martelli <martellif67@gmail.com> - 2024-01-19 20:50 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-19 21:10 +0100
Page 5 of 9 — ← Prev page 1 2 3 4 [5] 6 7 8 9 Next page →
| From | David Christensen <dpchrist@holgerdanske.com> |
|---|---|
| Date | 2024-01-18 10:00 +0100 |
| Message-ID | <HXwpH-3SNk-1@gated-at.bofh.it> |
| In reply to | #266175 |
On 1/17/24 22:44, gene heskett wrote:>> On 1/18/24 00:50, David Christensen wrote: > The migration took two passes because udev can't make up its alleged > mind so I was finally forced to use the rescue mode to edit fstab to > mount it by UUID and that worked, I've got /home on the copy right now. Congratulations! :-) > and I took the 60 G's of swap out too since I've never used more the 20G > with any gfx program, so I figure 47G's on /dev/sda is enough. 1 GB swap works for me. When a memory leak gets out of control, I do not have to wait long for the lock up. > So now > none of the raid is mounted, but the 30+ second lag when opening a write > path is still there, so I was erroneously blaming the raid. So I've > narrowed the problem Good to know. > but w/o a good clue what to do next. Find the needle in the haystack or do a fresh install. I prefer the latter, because I can estimate the effort and I am reasonably confident of the outcome. > One thing that > bothers me is there is no way the installers parted shows partition > names for non-raid disks. To me that is a serious bug. It appears from > the help that it can LABEL a partition but can't read that LABEL. When installing to UEFI/GPT, I am able to label partitions in the Debian Installer, the labels are visible in the installer, and the labels persist on disk after installation is complete. > parted > when asked to print all does that just fine, but the | doesn't put it to > less, so it scrolls off screen the top 60% of a parted's print all > output at some fraction of C speed. Not exactly helpful. I have other > things to do while I cogitate on what to do next. The following works as expected on my machine: 2024-01-18 00:34:41 root@laalaa ~ # parted -l | less > Many thanks to all that helped. YW. :-) >> If you use rsync(1), I suggest using some kind of integrity checking >> tool to verify that the source and destination file systems are >> identical. I prefer BSD mtree(8): > > I assume I'd have to remount the raid like to /raid? > Whew! That's got more arguments than rsync... The old /home RAID10 still has its metadata on disk. I would install the "mdadm" package, edit /etc/fstab, copy and rework the old /home line (new mount point, add option "ro"), create the mount point, and mount. David
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2024-01-18 12:50 +0100 |
| Message-ID | <HXz4d-3Uox-5@gated-at.bofh.it> |
| In reply to | #266181 |
On 1/18/24 03:57, David Christensen wrote: > On 1/17/24 22:44, gene heskett wrote:>> On 1/18/24 00:50, David > Christensen wrote: >> The migration took two passes because udev can't make up its alleged >> mind so I was finally forced to use the rescue mode to edit fstab to >> mount it by UUID and that worked, I've got /home on the copy right now. > > > Congratulations! :-) > > >> and I took the 60 G's of swap out too since I've never used more the >> 20G with any gfx program, so I figure 47G's on /dev/sda is enough. > > > 1 GB swap works for me. When a memory leak gets out of control, I do > not have to wait long for the lock up. > > >> So now none of the raid is mounted, but the 30+ second lag when >> opening a write path is still there, so I was erroneously blaming the >> raid. So I've narrowed the problem > > > Good to know. > > >> but w/o a good clue what to do next. > > > Find the needle in the haystack or do a fresh install. I prefer the > latter, because I can estimate the effort and I am reasonably confident > of the outcome. > > >> One thing that bothers me is there is no way the installers parted >> shows partition names for non-raid disks. To me that is a serious bug. >> It appears from the help that it can LABEL a partition but can't read >> that LABEL. > > > When installing to UEFI/GPT, I am able to label partitions in the Debian > Installer, the labels are visible in the installer, and the labels > persist on disk after installation is complete. > > >> parted when asked to print all does that just fine, but the | doesn't >> put it to less, so it scrolls off screen the top 60% of a parted's >> print all output at some fraction of C speed. Not exactly helpful. I >> have other things to do while I cogitate on what to do next. > > > The following works as expected on my machine: > > 2024-01-18 00:34:41 root@laalaa ~ > # parted -l | less > > >> Many thanks to all that helped. > > > YW. :-) > > >>> If you use rsync(1), I suggest using some kind of integrity checking >>> tool to verify that the source and destination file systems are >>> identical. I prefer BSD mtree(8): >> >> I assume I'd have to remount the raid like to /raid? >> Whew! That's got more arguments than rsync... > > > The old /home RAID10 still has its metadata on disk. I would install > the "mdadm" package, edit /etc/fstab, copy and rework the old /home line > (new mount point, add option "ro"), create the mount point, and mount. I believe mdadm is already installed. At least enough to collect and mount this raid10 and use it for /home for the last nearly 2 years. Now after all this folderall, all 4 of the SSD's are reporting read errors at very high lba's. all 4 drives are reporting the same poh, 21027 hours for the occurence of the error, that sounds like it could be just one crash or dirty power down. In which case it s/b repairable Do we have a repair utility that will force the drive to reallocate a spare sector and fix those? I have issued a smartctl -tlong on all 4 drives, results in about 3 hours. > David > > . Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | David Christensen <dpchrist@holgerdanske.com> |
|---|---|
| Date | 2024-01-18 22:10 +0100 |
| Message-ID | <HXHO9-3ZQb-5@gated-at.bofh.it> |
| In reply to | #266186 |
On 1/18/24 03:47, gene heskett wrote: > On 1/18/24 03:57, David Christensen wrote: >> The old /home RAID10 still has its metadata on disk. I would install >> the "mdadm" package, edit /etc/fstab, copy and rework the old /home >> line (new mount point, add option "ro"), create the mount point, and >> mount. > > I believe mdadm is already installed. At least enough to collect and > mount this raid10 and use it for /home for the last nearly 2 years. I made the suggestion to install the "mdadm" package because I thought you were going to do a fresh install of Debian. > Now after all this folderall, all 4 of the SSD's are reporting read > errors at very high lba's. > > all 4 drives are reporting the same poh, 21027 hours for the occurence > of the error, that sounds like it could be just one crash or dirty power > down. In which case it s/b repairable > > Do we have a repair utility that will force the drive to reallocate a > spare sector and fix those? > I have issued a smartctl -tlong on all 4 drives, results in about 3 hours. A SMART long test should find and fix any read errors. When deploying an SSD into a new role, I like to do a "secure erase" followed by a SMART long test. David
[toc] | [prev] | [next] | [standalone]
| From | David Christensen <dpchrist@holgerdanske.com> |
|---|---|
| Date | 2024-01-19 07:00 +0100 |
| Message-ID | <HXQ53-44Gg-1@gated-at.bofh.it> |
| In reply to | #266234 |
On 1/18/24 15:10, gene heskett wrote:
> On 1/18/24 16:08, David Christensen wrote:
>> On 1/18/24 03:47, gene heskett wrote:
>>> I have issued a smartctl -tlong on all 4 drives, results in about 3
>>> hours.
>>
>>
>> A SMART long test should find and fix any read errors.
>>
> Which has now been done on all 4 SSD. but the log is still a mess. 4th
> one in particular, smartctl -a /dev/sdg attached.
179 Used_Rsvd_Blk_Cnt_Tot 0x0013 085 085 010 Pre-fail Always
- 168
183 Runtime_Bad_Block 0x0013 085 085 010 Pre-fail Always
- 168
187 Uncorrectable_Error_Cnt 0x0032 099 099 000 Old_age Always
- 3275
195 ECC_Error_Rate 0x001a 199 199 000 Old_age Always
- 3275
Error 3332 occurred at disk power-on lifetime: 21027 hours (876 days + 3
hours)
When the command that caused the error occurred, the device was
active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 38 e8 ea 67 40 Error: WP at LBA = 0x0067eae8 = 6810344
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
61 18 38 e8 ea 67 40 07 15:17:03.046 WRITE FPDMA QUEUED
60 00 30 00 5e a9 40 06 15:17:03.046 READ FPDMA QUEUED
60 28 28 00 f4 87 40 05 15:17:03.046 READ FPDMA QUEUED
60 00 20 00 7c a9 40 04 15:17:03.046 READ FPDMA QUEUED
60 00 18 00 4a a9 40 03 15:17:03.046 READ FPDMA QUEUED
Error 3331 occurred at disk power-on lifetime: 21027 hours (876 days + 3
hours)
Error 3330 occurred at disk power-on lifetime: 21027 hours (876 days + 3
hours)
Error 3329 occurred at disk power-on lifetime: 21027 hours (876 days + 3
hours)
Error 3328 occurred at disk power-on lifetime: 21027 hours (876 days + 3
hours)
I am unclear if those errors are inside the SSD or if they are the SATA
communications link between the SSD and the motherbaord or HBA port
and/or main memory (?). Does dmesg(1) show anything?
In any case, make sure that you are using SATA III 6 Gbps cables with
locking connectors for your drives and that all the connections are good.
>> When deploying an SSD into a new role, I like to do a "secure erase"
>> followed by a SMART long test.
>
> not fam with that, I usually just reformat. But I'll not do that until
> I have amanda running again.
Secure erase will erase all of the blocks in the drive, including those
that are held in reserve. This both verifies that each block can be
erased, and provides maximum performance what you put the disk into
service and start writing to it.
> Thanks David, take care & stay well
Likewise. :-)
David
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2024-01-19 08:30 +0100 |
| Message-ID | <HXRu9-45Cd-3@gated-at.bofh.it> |
| In reply to | #266247 |
On 1/19/24 00:55, David Christensen wrote: > On 1/18/24 15:10, gene heskett wrote: >> On 1/18/24 16:08, David Christensen wrote: >>> On 1/18/24 03:47, gene heskett wrote: >>>> I have issued a smartctl -tlong on all 4 drives, results in about 3 >>>> hours. >>> >>> >>> A SMART long test should find and fix any read errors. >>> >> Which has now been done on all 4 SSD. but the log is still a mess. 4th >> one in particular, smartctl -a /dev/sdg attached. > > > 179 Used_Rsvd_Blk_Cnt_Tot 0x0013 085 085 010 Pre-fail Always > - 168 > > 183 Runtime_Bad_Block 0x0013 085 085 010 Pre-fail Always > - 168 > 187 Uncorrectable_Error_Cnt 0x0032 099 099 000 Old_age Always > - 3275 > > 195 ECC_Error_Rate 0x001a 199 199 000 Old_age Always > - 3275 > > Error 3332 occurred at disk power-on lifetime: 21027 hours (876 days + 3 > hours) > When the command that caused the error occurred, the device was > active or idle. > > After command completion occurred, registers were: > ER ST SC SN CL CH DH > -- -- -- -- -- -- -- > 40 51 38 e8 ea 67 40 Error: WP at LBA = 0x0067eae8 = 6810344 > > Commands leading to the command that caused the error were: > CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name > -- -- -- -- -- -- -- -- ---------------- -------------------- > 61 18 38 e8 ea 67 40 07 15:17:03.046 WRITE FPDMA QUEUED > 60 00 30 00 5e a9 40 06 15:17:03.046 READ FPDMA QUEUED > 60 28 28 00 f4 87 40 05 15:17:03.046 READ FPDMA QUEUED > 60 00 20 00 7c a9 40 04 15:17:03.046 READ FPDMA QUEUED > 60 00 18 00 4a a9 40 03 15:17:03.046 READ FPDMA QUEUED > > Error 3331 occurred at disk power-on lifetime: 21027 hours (876 days + 3 > hours) > > Error 3330 occurred at disk power-on lifetime: 21027 hours (876 days + 3 > hours) > > Error 3329 occurred at disk power-on lifetime: 21027 hours (876 days + 3 > hours) > > Error 3328 occurred at disk power-on lifetime: 21027 hours (876 days + 3 > hours) > > > I am unclear if those errors are inside the SSD or if they are the SATA > communications link between the SSD and the motherbaord or HBA port > and/or main memory (?). Does dmesg(1) show anything? I'm not sure what I should be looking for, and I don't see anything that is looping to correct an error. Suggested grep targets? > > In any case, make sure that you are using SATA III 6 Gbps cables with > locking connectors for your drives and that all the connections are good. That's hard to verify once the cables are removed from the packing. all are black, with locking clips There is a cable maker under every tree in china so I'n not swearing any are up to specs, I've had cable problem in the past but usually a magenta colored on that is over 2 years old, If you have a known good src on straight on cables, please share. You would be doing everyone a favor. No hot red need apply. People think its pretty, but the die that gives the color, eats the copper in the cable. I am the src of the internet legend about that, first observed in the early 1970's when all the cb radio mic cables switched from dull red to this bright red/magemta as the tx wire in multiconductor cables. And that wire literally dissolved the copper in the hot red conductor to a dull rusty powder in 2 years. And its been doing that same failure in sata cables of that color for a decade now. Test what you have by taking a wooden stick and moving each one a centimeter or so, if the log blows up with sata resets, bingo, bad cable. replace it asap. > > >>> When deploying an SSD into a new role, I like to do a "secure erase" >>> followed by a SMART long test. >> >> not fam with that, I usually just reformat. But I'll not do that >> until I have amanda running again. > > > Secure erase will erase all of the blocks in the drive, including those > that are held in reserve. This both verifies that each block can be > erased, and provides maximum performance what you put the disk into > service and start writing to it. > > >> Thanks David, take care & stay well > > Likewise. :-) > > > David > > > . Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | David Christensen <dpchrist@holgerdanske.com> |
|---|---|
| Date | 2024-01-19 22:00 +0100 |
| Message-ID | <HY481-4d2I-1@gated-at.bofh.it> |
| In reply to | #266252 |
On 1/18/24 23:23, gene heskett wrote:
> On 1/19/24 00:55, David Christensen wrote:
>> I am unclear if those errors are inside the SSD or if they are the
>> SATA communications link between the SSD and the motherbaord or HBA
>> port and/or main memory (?). Does dmesg(1) show anything?
>
> I'm not sure what I should be looking for, and I don't see anything that
> is looping to correct an error. Suggested grep targets?
Here is a dmesg(1) excerpt from 2014 -- Debian 7, good SSD, bad SATA cable:
[ 2.086360] ata3.00: ATA-9: INTEL SSDSC2CW060A3, 400i, max UDMA/133
[ 2.086365] ata3.00: 117231408 sectors, multi 16: LBA48 NCQ (depth
31/32), AA
[ 2.096265] ata3.00: configured for UDMA/133
[ 14.718054] EXT4-fs (dm-0): mounted filesystem with ordered data
mode. Opts: (null)
[ 18.449227] EXT4-fs (sda1): mounted filesystem with ordered data
mode. Opts: (null)
[ 20.157693] ata3.00: exception Emask 0x10 SAct 0x400000 SErr 0xc00001
action 0x6 frozen
[ 20.157699] ata3.00: irq_stat 0x08000000, interface fatal error
[ 20.157703] ata3: SError: { RecovData Handshk LinkSeq }
[ 20.157709] ata3.00: failed command: WRITE FPDMA QUEUED
[ 20.157716] ata3.00: cmd 61/08:b0:a0:e0:61/00:00:00:00:00/40 tag 22
ncq 4096 out
[ 20.157721] ata3.00: status: { DRDY }
[ 20.157727] ata3: hard resetting link
[ 20.473489] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 20.484835] ata3.00: configured for UDMA/133
[ 20.484847] ata3: EH complete
[ 21.059825] ata3.00: exception Emask 0x10 SAct 0x4000 SErr 0x400100
action 0x6 frozen
[ 21.059831] ata3.00: irq_stat 0x08000000, interface fatal error
[ 21.059835] ata3: SError: { UnrecovData Handshk }
[ 21.059840] ata3.00: failed command: WRITE FPDMA QUEUED
[ 21.059848] ata3.00: cmd 61/08:70:50:e2:61/00:00:00:00:00/40 tag 14
ncq 4096 out
[ 21.059853] ata3.00: status: { DRDY }
[ 21.059859] ata3: hard resetting link
[ 21.376135] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 21.397234] ata3.00: configured for UDMA/133
[ 21.397246] ata3: EH complete
[ 22.590805] ata3.00: exception Emask 0x10 SAct 0x600 SErr 0x400100
action 0x6 frozen
[ 22.590811] ata3.00: irq_stat 0x08000000, interface fatal error
[ 22.590815] ata3: SError: { UnrecovData Handshk }
[ 22.590819] ata3.00: failed command: WRITE FPDMA QUEUED
[ 22.590826] ata3.00: cmd 61/08:48:f0:ee:1d/00:00:00:00:00/40 tag 9
ncq 4096 out
[ 22.590831] ata3.00: status: { DRDY }
[ 22.590834] ata3.00: failed command: WRITE FPDMA QUEUED
[ 22.590840] ata3.00: cmd 61/08:50:70:ef:1d/00:00:00:00:00/40 tag 10
ncq 4096 out
[ 22.590844] ata3.00: status: { DRDY }
[ 22.590851] ata3: hard resetting link
[ 22.909955] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 22.921525] ata3.00: configured for UDMA/133
[ 22.937878] ata3: EH complete
[ 22.938635] ata3: limiting SATA link speed to 3.0 Gbps
[ 22.938638] ata3.00: exception Emask 0x10 SAct 0x400000 SErr 0x400100
action 0x6 frozen
[ 22.938640] ata3.00: irq_stat 0x08000000, interface fatal error
[ 22.938642] ata3: SError: { UnrecovData Handshk }
[ 22.938645] ata3.00: failed command: WRITE FPDMA QUEUED
[ 22.938648] ata3.00: cmd 61/60:b0:20:28:66/00:00:00:00:00/40 tag 22
ncq 49152 out
[ 22.938650] ata3.00: status: { DRDY }
[ 22.938652] ata3: hard resetting link
[ 23.257418] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 23.269251] ata3.00: configured for UDMA/133
[ 23.285387] ata3: EH complete
>> In any case, make sure that you are using SATA III 6 Gbps cables with
>> locking connectors for your drives and that all the connections are good.
>
> That's hard to verify once the cables are removed from the packing. all
> are black, with locking clips There is a cable maker under every tree
> in china so I'n not swearing any are up to specs, I've had cable problem
> in the past but usually a magenta colored on that is over 2 years old,
> If you have a known good src on straight on cables, please share. You
> would be doing everyone a favor.
https://www.cablematters.com/pc-187-156-3-pack-straight-60-gbps-sata-iii-cable.aspx
https://www.cablematters.com/pc-188-156-cable-matters-3-pack-90-degree-right-angle-60-gbps-sata-iii-cable-18-inches.aspx
> Test what you have by taking a wooden stick and moving each one a
> centimeter or so, if the log blows up with sata resets, bingo, bad
> cable. replace it asap.
I call that the "wiggle" test.
David
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2024-01-20 01:20 +0100 |
| Message-ID | <HY7fA-4fd4-9@gated-at.bofh.it> |
| In reply to | #266291 |
On 1/19/24 15:56, David Christensen wrote: No sign of that snipped stuff. > https://www.cablematters.com/pc-187-156-3-pack-straight-60-gbps-sata-iii-cable.aspx Cheap enough at 18", ordered 4 packs of 3 for service & build stock, thanks David. > I call that the "wiggle" test. So do I but I've had to explain it. Several times. Now they'll have to dig me out, got around 16" of white stuff in the last 36 hrs. I believe winter has arrived. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | Felix Miata <mrmazda@earthlink.net> |
|---|---|
| Date | 2024-01-20 02:30 +0100 |
| Message-ID | <HY8lj-4fMQ-7@gated-at.bofh.it> |
| In reply to | #266300 |
gene heskett composed on 2024-01-19 19:09 (UTC-0500): > On 1/19/24 15:56, David Christensen wrote: > No sign of that snipped stuff. > >> https://www.cablematters.com/pc-187-156-3-pack-straight-60-gbps-sata-iii-cable.aspx > Cheap enough at 18", ordered 4 packs of 3 for service & build stock, > thanks David. Among the elements of that page, opened in web browser lacking JS support, was absence of a price, and also were the following "features": Serial ATA/150 and Fast data transfer rate of up to 150 Mbps Those describe SATA revision 1.0 (1.5 Gbit/s), not SATA revision 2.0 (300MB/s, 3.0 Gbit/s), not SATA revision 3.0 (600MB/s, 6.0 Gbit/s). https://en.wikipedia.org/wiki/SATA With JS enabled, the page radically changed to show $8.49 for a 3-pack of 6.0 Gbit/s cables. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2024-01-20 06:40 +0100 |
| Message-ID | <HYcff-4iaI-1@gated-at.bofh.it> |
| In reply to | #266301 |
On 1/19/24 20:29, Felix Miata wrote: > gene heskett composed on 2024-01-19 19:09 (UTC-0500): > >> On 1/19/24 15:56, David Christensen wrote: > >> No sign of that snipped stuff. >> >>> https://www.cablematters.com/pc-187-156-3-pack-straight-60-gbps-sata-iii-cable.aspx > >> Cheap enough at 18", ordered 4 packs of 3 for service & build stock, >> thanks David. > > Among the elements of that page, opened in web browser lacking JS support, was > absence of a price, and also were the following "features": > > Serial ATA/150 > and > Fast data transfer rate of up to 150 Mbps > > Those describe SATA revision 1.0 (1.5 Gbit/s), not SATA revision 2.0 (300MB/s, 3.0 > Gbit/s), not SATA revision 3.0 (600MB/s, 6.0 Gbit/s). > https://en.wikipedia.org/wiki/SATA > > With JS enabled, the page radically changed to show $8.49 for a 3-pack of 6.0 > Gbit/s cables. They had 2 lengths, 24" will if everything isn't good, sign on as sata-II but the 18" I bought claim sata-III. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | David Christensen <dpchrist@holgerdanske.com> |
|---|---|
| Date | 2024-01-20 08:00 +0100 |
| Message-ID | <HYduF-4iOG-1@gated-at.bofh.it> |
| In reply to | #266305 |
On 1/19/24 21:34, gene heskett wrote: > On 1/19/24 20:29, Felix Miata wrote: >> gene heskett composed on 2024-01-19 19:09 (UTC-0500): >>> On 1/19/24 15:56, David Christensen wrote: >>>> https://www.cablematters.com/pc-187-156-3-pack-straight-60-gbps-sata-iii-cable.aspx >> >>> Cheap enough at 18", ordered 4 packs of 3 for service & build stock, >>> thanks David. >> >> Among the elements of that page, opened in web browser lacking JS >> support, was >> absence of a price, and also were the following "features": >> >> Serial ATA/150 >> and >> Fast data transfer rate of up to 150 Mbps >> >> Those describe SATA revision 1.0 (1.5 Gbit/s), not SATA revision 2.0 >> (300MB/s, 3.0 >> Gbit/s), not SATA revision 3.0 (600MB/s, 6.0 Gbit/s). >> https://en.wikipedia.org/wiki/SATA >> >> With JS enabled, the page radically changed to show $8.49 for a 3-pack >> of 6.0 >> Gbit/s cables. > > They had 2 lengths, 24" will if everything isn't good, sign on as > sata-II but the 18" I bought claim sata-III. I bought black cables, 18" and 24", straight-straight and straight-90. The older ones are labeled "Serial ATA 6G". The newer ones are labeled "Serial ATA3.2". David
[toc] | [prev] | [next] | [standalone]
| From | Max Nikulin <manikulin@gmail.com> |
|---|---|
| Date | 2024-01-20 16:30 +0100 |
| Message-ID | <HYlse-4nDn-5@gated-at.bofh.it> |
| In reply to | #266234 |
On 19/01/2024 06:10, gene heskett wrote: > SMART Attributes Data Structure revision number: 1 > Vendor Specific SMART Attributes with Thresholds: > ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE > 179 Used_Rsvd_Blk_Cnt_Tot 0x0013 085 085 010 Pre-fail Always - 168 > 183 Runtime_Bad_Block 0x0013 085 085 010 Pre-fail Always - 168 85 is still far enough from 10, however the change is noticeable. > 190 Airflow_Temperature_Cel 0x0032 071 049 000 Old_age Always - 29 Initial 100 decreased to 49 means that sometimes the drive is hot enough. On the other hand the raw value of 29 is likely centigrade degrees and it is not really hot for the normalized value of 71. > SMART Self-test log structure revision number 1 > Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error > # 1 Extended offline Completed: read failure 50% 21128 1847474744 > # 2 Extended offline Completed: read failure 50% 10917 1847474376 > # 3 Extended offline Completed: read failure 50% 10586 1847474376 May it happen that disk firmware does not remap failed sectors to allow the user to identify what file is damaged?
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2024-01-20 21:30 +0100 |
| Message-ID | <HYq8x-4qqo-3@gated-at.bofh.it> |
| In reply to | #266319 |
On 1/20/24 10:24, Max Nikulin wrote: > On 19/01/2024 06:10, gene heskett wrote: >> SMART Attributes Data Structure revision number: 1 >> Vendor Specific SMART Attributes with Thresholds: >> ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE >> UPDATED WHEN_FAILED RAW_VALUE >> 179 Used_Rsvd_Blk_Cnt_Tot 0x0013 085 085 010 Pre-fail >> Always - 168 >> 183 Runtime_Bad_Block 0x0013 085 085 010 Pre-fail >> Always - 168 > > 85 is still far enough from 10, however the change is noticeable. > >> 190 Airflow_Temperature_Cel 0x0032 071 049 000 Old_age >> Always - 29 > > Initial 100 decreased to 49 means that sometimes the drive is hot > enough. I've been under the impression that 100C was the absolute temp limit, and it not been over 36C that I know of according to gkrellm which s set to monitor that stuff in real time. Right now nothing in the system is north of 32C, might get to 36C at the end of a 9 minute build of something in OpenSCAD. On the other hand the raw value of 29 is likely centigrade > degrees and it is not really hot for the normalized value of 71. > this is true, all reported temps are in C. >> SMART Self-test log structure revision number 1 >> Num Test_Description Status Remaining >> LifeTime(hours) LBA_of_first_error >> # 1 Extended offline Completed: read failure 50% >> 21128 1847474744 >> # 2 Extended offline Completed: read failure 50% >> 10917 1847474376 >> # 3 Extended offline Completed: read failure 50% >> 10586 1847474376 > > May it happen that disk firmware does not remap failed sectors to allow > the user to identify what file is damaged? IDK Max. I know the microware os9 file system well enough to connect the dots, but have little knowledge for how one might do this with ext4. Thanks Max, take care & stay well. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | Max Nikulin <manikulin@gmail.com> |
|---|---|
| Date | 2024-01-21 06:40 +0100 |
| Message-ID | <HYyIN-4vM5-1@gated-at.bofh.it> |
| In reply to | #266330 |
On 21/01/2024 03:23, gene heskett wrote: > On 1/20/24 10:24, Max Nikulin wrote: >> On 19/01/2024 06:10, gene heskett wrote: >>> ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED >>> WHEN_FAILED RAW_VALUE >> >>> 190 Airflow_Temperature_Cel 0x0032 071 049 000 Old_age >>> Always - 29 >> >> Initial 100 decreased to 49 means that sometimes the drive is hot enough. > > I've been under the impression that 100C was the absolute temp limit Do not confuse normalized values (100 means shiny new, 0 means really old or damaged) and RAW_VALUE. For some drives smartctl -x may report history of temperature measurements, but I think summer values are already unavailable. > and it not been over 36C that I know of according to gkrellm which s set > to monitor that stuff in real time. Right now nothing in the system is > north of 32C, might get to 36C 71 <-> 29 °C and 49 <-> 36 °C mapping might be possible, but I would expect higher temperature for 49. >>> # 2 Extended offline Completed: read failure 50% >>> 10917 1847474376 >>> # 3 Extended offline Completed: read failure 50% >>> 10586 1847474376 >> >> May it happen that disk firmware does not remap failed sectors to >> allow the user to identify what file is damaged? > > IDK Max. I know the microware os9 file system well enough to connect the > dots, but have little knowledge for how one might do this with ext4. If you are motivated enough then docs either for badblocks or for some data recovery software may give you a recipe. A search engine should help to find it.
[toc] | [prev] | [next] | [standalone]
| From | David Christensen <dpchrist@holgerdanske.com> |
|---|---|
| Date | 2024-01-21 07:40 +0100 |
| Message-ID | <HYzER-4wmm-3@gated-at.bofh.it> |
| In reply to | #266349 |
On 1/20/24 21:48, gene heskett wrote: > New -x version for this SSD attached > SMART Attributes Data Structure revision number: 1 > Vendor Specific SMART Attributes with Thresholds: > ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE > 5 Reallocated_Sector_Ct PO--CK 094 094 010 - 64 > 183 Runtime_Bad_Block PO--C- 094 094 010 - 64 > 187 Uncorrectable_Error_Cnt -O--CK 099 099 000 - 392 > 195 ECC_Error_Rate -O-RC- 199 199 000 - 392 > 199 CRC_Error_Count -OSRCK 099 099 000 - 2 Those attributes are worrisome. Especially Reallocated_Sector_Ct and Runtime_Bad_Block -- I am confident those are inside the SSD. > 9 Power_On_Hours -O--CK 095 095 000 - 21194 That is equivalent to 10.2 years at 40 hours/week. > 241 Total_LBAs_Written -O--CK 099 099 000 - 38429262625 TBW specification for 1 TB drive is 600TB. You are at 19.7. > Error 466 [1] occurred at disk power-on lifetime: 21078 hours (878 days + 6 hours) > When the command that caused the error occurred, the device was active or idle. > > After command completion occurred, registers were: > ER -- ST COUNT LBA_48 LH LM LL DV DC > -- -- -- == -- == == == -- -- -- -- -- > 40 -- 51 00 40 00 00 1b a4 0d 18 40 00 Error: WP at LBA = 0x1ba40d18 = 463736088 > > Commands leading to the command that caused the error were: > CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name > -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- > 61 00 08 00 40 00 00 1b a4 0d 18 40 08 1d+03:35:20.430 WRITE FPDMA QUEUED > 60 0a 00 00 38 00 00 70 f1 a4 00 40 07 1d+03:35:20.430 READ FPDMA QUEUED > 60 07 80 00 30 00 00 70 f1 3c 80 40 06 1d+03:35:20.430 READ FPDMA QUEUED > 61 00 28 00 28 00 00 1b a4 0d 38 40 05 1d+03:35:20.430 WRITE FPDMA QUEUED > 47 00 00 00 01 00 00 00 00 00 00 40 02 1d+03:35:20.430 READ LOG DMA EXT > > Error 465 [0] occurred at disk power-on lifetime: 21078 hours (878 days + 6 hours) > ... > Error 464 [3] occurred at disk power-on lifetime: 21078 hours (878 days + 6 hours) > ... > Error 463 [2] occurred at disk power-on lifetime: 21078 hours (878 days + 6 hours) I am still uncertain if those are internal SSD errors or SATA errors. Please check if you see matching errors in dmesg(1). David
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2024-01-21 12:50 +0100 |
| Message-ID | <HYEuS-4zfE-9@gated-at.bofh.it> |
| In reply to | #266351 |
On 1/21/24 01:33, David Christensen wrote: > On 1/20/24 21:48, gene heskett wrote: >> New -x version for this SSD attached > > > SMART Attributes Data Structure revision number: 1 > > Vendor Specific SMART Attributes with Thresholds: > > ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE > > 5 Reallocated_Sector_Ct PO--CK 094 094 010 - 64 > > 183 Runtime_Bad_Block PO--C- 094 094 010 - 64 > > 187 Uncorrectable_Error_Cnt -O--CK 099 099 000 - 392 > > 195 ECC_Error_Rate -O-RC- 199 199 000 - 392 > > 199 CRC_Error_Count -OSRCK 099 099 000 - 2 > > Those attributes are worrisome. Especially Reallocated_Sector_Ct and > Runtime_Bad_Block -- I am confident those are inside the SSD. > > > > 9 Power_On_Hours -O--CK 095 095 000 - 21194 > > That is equivalent to 10.2 years at 40 hours/week. Machine runs 24/7/365.25 > > > > 241 Total_LBAs_Written -O--CK 099 099 000 - 38429262625 > > TBW specification for 1 TB drive is 600TB. You are at 19.7. relatively low IOW. > > > > Error 466 [1] occurred at disk power-on lifetime: 21078 hours (878 > days + 6 hours) > > When the command that caused the error occurred, the device was > active or idle. > > > > After command completion occurred, registers were: > > ER -- ST COUNT LBA_48 LH LM LL DV DC > > -- -- -- == -- == == == -- -- -- -- -- > > 40 -- 51 00 40 00 00 1b a4 0d 18 40 00 Error: WP at LBA = > 0x1ba40d18 = 463736088 > > > > Commands leading to the command that caused the error were: > > CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time > Command/Feature_Name > > -- == -- == -- == == == -- -- -- -- -- --------------- > -------------------- > > 61 00 08 00 40 00 00 1b a4 0d 18 40 08 1d+03:35:20.430 WRITE > FPDMA QUEUED > > 60 0a 00 00 38 00 00 70 f1 a4 00 40 07 1d+03:35:20.430 READ FPDMA > QUEUED > > 60 07 80 00 30 00 00 70 f1 3c 80 40 06 1d+03:35:20.430 READ FPDMA > QUEUED > > 61 00 28 00 28 00 00 1b a4 0d 38 40 05 1d+03:35:20.430 WRITE > FPDMA QUEUED > > 47 00 00 00 01 00 00 00 00 00 00 40 02 1d+03:35:20.430 READ LOG > DMA EXT > > > > Error 465 [0] occurred at disk power-on lifetime: 21078 hours (878 > days + 6 hours) > > ... > > Error 464 [3] occurred at disk power-on lifetime: 21078 hours (878 > days + 6 hours) > > ... > > Error 463 [2] occurred at disk power-on lifetime: 21078 hours (878 > days + 6 hours) > > I am still uncertain if those are internal SSD errors or SATA errors. > Please check if you see matching errors in dmesg(1). > > There aren't any. Those hours would very closely correspond to my attempts to rsync and the OOM deamon killed the machine, which it did around 10 times. So logging by then had been killed. That to me is the smoking gun. 2T is enough /home for the nonce. so I'll do the rsync thing going the other direction, using it for a backup of /home until I'm ready for trixie. However I am tempted to zero the drives an recreate the raid w/o formatting since the mdadm seems capable to installing itw own filesystems to use the whole drive unpartitioned, giving me a backup that sizewise is about the same as the single 2T drive has now. And although my single experience with lvm over a decade ago was a total disaster, made out of used spinning rust I may now see how the other 4 2T's assembled as a lvm for amandas vtapes as an 8T lvm to backup the whole system, which in addition to the 4 cnc'd machines, has over the last 5 years seen a train of 3d printers go by. If all 3, currently a WIP, get rebuilt, the smallest is 305 by, the largest is 400 by. And all I hope will lay plastic at 200+ mm a second. Normal consumer stuff is 40 to 60. Obviously I have an eclectic choice of too many hobbies. ;o)> Now if curiosity doesn't kill this cat, I need to find some breakfast and git to it. Thank you David, take care, stay warm dry and well. > David > > . Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | David Christensen <dpchrist@holgerdanske.com> |
|---|---|
| Date | 2024-01-21 22:20 +0100 |
| Message-ID | <HYNot-4ELo-7@gated-at.bofh.it> |
| In reply to | #266364 |
On 1/21/24 03:47, gene heskett wrote: > On 1/21/24 01:33, David Christensen wrote: >> I am still uncertain if those are internal SSD errors or SATA errors. >> Please check if you see matching errors in dmesg(1). >> > There aren't any. Those hours would very closely correspond to my > attempts to rsync and the OOM deamon killed the machine, which it did > around 10 times. So logging by then had been killed. That to me is the > smoking gun. Kernel ring buffer is renewed with each boot and newer messages overwrite older messages. So, you will want to save or clear the ring buffer with demsg(1), save a SMART full report, exercise the disk with dd(1) and/or a SMART test, save the ring buffer, save a SMART full report, and analyze everything to see if you have disk problems, SATA problems, and/or system problems. Once everything passes without error, the disk is ready to be put into service. > 2T is enough /home for the nonce. so I'll do the rsync > thing going the other direction, using it for a backup of /home > until I'm ready for trixie. > > However I am tempted to zero the drives an recreate the raid w/o > formatting since the mdadm seems capable to installing itw own > filesystems to use the whole drive unpartitioned, giving me a backup > that sizewise is about the same as the single 2T drive has now. > > And although my single experience with lvm over a decade ago was a total > disaster, made out of used spinning rust I may now see how the other 4 > 2T's assembled as a lvm for amandas vtapes as an 8T lvm to backup the > whole system, which in addition to the 4 cnc'd machines, has over the > last 5 years seen a train of 3d printers go by. If all 3, currently a > WIP, get rebuilt, the smallest is 305 by, the largest is 400 by. And > all I hope will lay plastic at 200+ mm a second. Normal consumer stuff > is 40 to 60. > > Obviously I have an eclectic choice of too many hobbies. ;o)> > Now if curiosity doesn't kill this cat, I need to find some breakfast > and git to it. This and other threads have led me to the conclusion that consumer SSD's are meant for devices that are off most of the time -- e.g. notepad, laptop, desktop, and workstation computers. If you put them into a NAS/ file server and run them 24x7, they will die sometime after 2 years. So, I suggest: 1. Build a storage server using NAS or enterprise HDD's. Use an enterprise SSD or DOM for the OS. Run it 24x7 or shut it down as you like. 2. Use your Asus PRIME Z370-A II as a workstation. Install the WD Black M.2 NVMe PCIe SSD. Connect the optical drive to the first motherboard SATA port. Install Debian onto the WD Black. Then, connect the five Samsung EVO 870's to the remaining motherboard SATA ports. Set them up as a 5-way mirror (RAID1). Use the Samsung RAID as a scratch disk for your 3-D work. As the Samsung's die off, replace them with the Gigastones. Shut it down when you are not using it. 3. For Amanda, either add more HDD's to the storage server or build another server. If another server, shut it down when you are not using it. David
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2024-01-21 23:50 +0100 |
| Message-ID | <HYONz-4FtI-7@gated-at.bofh.it> |
| In reply to | #266425 |
On 1/21/24 16:13, David Christensen wrote: > On 1/21/24 03:47, gene heskett wrote: >> On 1/21/24 01:33, David Christensen wrote: >>> I am still uncertain if those are internal SSD errors or SATA errors. >>> Please check if you see matching errors in dmesg(1). >>> >> There aren't any. Those hours would very closely correspond to my >> attempts to rsync and the OOM deamon killed the machine, which it did >> around 10 times. So logging by then had been killed. That to me is >> the smoking gun. > > > Kernel ring buffer is renewed with each boot and newer messages > overwrite older messages. So, you will want to save or clear the ring > buffer with demsg(1), save a SMART full report, exercise the disk with > dd(1) and/or a SMART test, save the ring buffer, save a SMART full > report, and analyze everything to see if you have disk problems, SATA > problems, and/or system problems. Once everything passes without error, > the disk is ready to be put into service. > > >> 2T is enough /home for the nonce. so I'll do the rsync thing going the >> other direction, using it for a backup of /home until I'm ready for >> trixie. >> >> However I am tempted to zero the drives an recreate the raid w/o >> formatting since the mdadm seems capable to installing itw own >> filesystems to use the whole drive unpartitioned, giving me a backup >> that sizewise is about the same as the single 2T drive has now. >> >> And although my single experience with lvm over a decade ago was a >> total disaster, made out of used spinning rust I may now see how the >> other 4 2T's assembled as a lvm for amandas vtapes as an 8T lvm to >> backup the whole system, which in addition to the 4 cnc'd machines, >> has over the last 5 years seen a train of 3d printers go by. If all 3, >> currently a WIP, get rebuilt, the smallest is 305 by, the largest is >> 400 by. And all I hope will lay plastic at 200+ mm a second. Normal >> consumer stuff is 40 to 60. >> >> Obviously I have an eclectic choice of too many hobbies. ;o)> >> Now if curiosity doesn't kill this cat, I need to find some breakfast >> and git to it. > > > This and other threads have led me to the conclusion that consumer SSD's > are meant for devices that are off most of the time -- e.g. notepad, > laptop, desktop, and workstation computers. If you put them into a NAS/ > file server and run them 24x7, they will die sometime after 2 years. > That has not been my experience at all David, I bought a 4 pack of 120G ssd's when they were the biggest available and replaced 3 spinning rust drives that had 50-70k hours on them with these. My cnc machines are all wired so power for the mill/lathe/what have you is totally controlled by the enable key, f2, so if f2 is off only the computer is running. That was at least 6 years ago. Then I installed a 240G as an extra drive on the rpi4 that runs my biggest lathe and made a buildbot out of it to pull linuxcnc-master from github and build it, also armhf kernels for linuxcnc's realtime needs. The 120G disappeared in about a year, replaced the adapter with a startech, drive was and is just fine. There is now at least 5 years on everyone of those original 120's, zero SSD problems in the whole lot. > > So, I suggest: > > 1. Build a storage server using NAS or enterprise HDD's. Use an > enterprise SSD or DOM for the OS. Run it 24x7 or shut it down as you like. > > 2. Use your Asus PRIME Z370-A II as a workstation. Install the WD > Black M.2 NVMe PCIe SSD. Connect the optical drive to the first > motherboard SATA port. Install Debian onto the WD Black. Then, connect > the five Samsung EVO 870's to the remaining motherboard SATA ports. Set > them up as a 5-way mirror (RAID1). Use the Samsung RAID as a scratch > disk for your 3-D work. As the Samsung's die off, replace them with the > Gigastones. Shut it down when you are not using it. > > 3. For Amanda, either add more HDD's to the storage server or build > another server. If another server, shut it down when you are not using it. > Speaking as someone who has used amanda for about 25 years: People don't always understand that one of Amanda prime directives is to balance the size of an individual back up run by advancing the level 3 scheduled for tonight, by advancing it to level 0 if this run is only going to be small. The only guarantee is that if you have a 10 day schedule, all machines/dle's, will get that level 0 backup not more than 10 days after the last one. You choose how many days long that cycle is. I adjust it so the storage is around 75 to 80% used after the schedule has stabilized. This may take quite a few such cycles. Designed to run every night when things are relatively quiet, how this works well depends on the other machines it is backing up be available. Machines missing at backup time can and will muck things up for this efficient scheduling. Corporate users of Amanda, used to doing it their way, backing the weeks business on friday nights just don't understand that the Amanda way gets them a 100% coverage backup by backing up only the differences from the previous run of that dle every night is far superior to their fridey night when most of the offices machines are turned off for the weekend. For those cases we recommend composing two or more dle files and rigging cron to run them at more appropriate scheduling. This can be fairly easily done but MBA's watching every watt on the power bill just don't see it that way. They will get burnt when their place burns. Thanks David. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | David Christensen <dpchrist@holgerdanske.com> |
|---|---|
| Date | 2024-01-22 00:30 +0100 |
| Message-ID | <HYPqh-4FYG-1@gated-at.bofh.it> |
| In reply to | #266432 |
On 1/21/24 14:48, gene heskett wrote: > On 1/21/24 16:13, David Christensen wrote: >> On 1/21/24 03:47, gene heskett wrote: >>> On 1/21/24 01:33, David Christensen wrote: >>>> I am still uncertain if those are internal SSD errors or SATA >>>> errors. Please check if you see matching errors in dmesg(1). >>>> >>> There aren't any. Those hours would very closely correspond to my >>> attempts to rsync and the OOM deamon killed the machine, which it did >>> around 10 times. So logging by then had been killed. That to me is >>> the smoking gun. >> >> >> Kernel ring buffer is renewed with each boot and newer messages >> overwrite older messages. So, you will want to save or clear the ring >> buffer with demsg(1), save a SMART full report, exercise the disk with >> dd(1) and/or a SMART test, save the ring buffer, save a SMART full >> report, and analyze everything to see if you have disk problems, SATA >> problems, and/or system problems. Once everything passes without >> error, the disk is ready to be put into service. >> >> >>> 2T is enough /home for the nonce. so I'll do the rsync thing going >>> the other direction, using it for a backup of /home until I'm ready >>> for trixie. >>> >>> However I am tempted to zero the drives an recreate the raid w/o >>> formatting since the mdadm seems capable to installing itw own >>> filesystems to use the whole drive unpartitioned, giving me a backup >>> that sizewise is about the same as the single 2T drive has now. >>> >>> And although my single experience with lvm over a decade ago was a >>> total disaster, made out of used spinning rust I may now see how the >>> other 4 2T's assembled as a lvm for amandas vtapes as an 8T lvm to >>> backup the whole system, which in addition to the 4 cnc'd machines, >>> has over the last 5 years seen a train of 3d printers go by. If all >>> 3, currently a WIP, get rebuilt, the smallest is 305 by, the largest >>> is 400 by. And all I hope will lay plastic at 200+ mm a second. >>> Normal consumer stuff is 40 to 60. >>> >>> Obviously I have an eclectic choice of too many hobbies. ;o)> >>> Now if curiosity doesn't kill this cat, I need to find some breakfast >>> and git to it. >> >> >> This and other threads have led me to the conclusion that consumer >> SSD's are meant for devices that are off most of the time -- e.g. >> notepad, laptop, desktop, and workstation computers. If you put them >> into a NAS/ file server and run them 24x7, they will die sometime >> after 2 years. >> > That has not been my experience at all David, I bought a 4 pack of 120G > ssd's when they were the biggest available and replaced 3 spinning rust > drives that had 50-70k hours on them with these. My cnc machines are all > wired so power for the mill/lathe/what have you is totally controlled by > the enable key, f2, so if f2 is off only the computer is running. That > was at least 6 years ago. Then I installed a 240G as an extra drive on > the rpi4 that runs my biggest lathe and made a buildbot out of it to > pull linuxcnc-master from github and build it, also armhf kernels for > linuxcnc's realtime needs. The 120G disappeared in about a year, > replaced the adapter with a startech, drive was and is just fine. There > is now at least 5 years on everyone of those original 120's, zero SSD > problems in the whole lot. I also have small SSD's that have lasted far longer than 2 years on mixed duty, including 24x7 (Intel SSD 520 Series 60 GB). The relevant recent threads on this list seem to be 1+ TB Samsung's. It is interesting to note that BackBlaze does not seem to use Samsung SSD's: https://www.backblaze.com/blog/ssd-edition-2023-mid-year-drive-stats-review/ >> 3. For Amanda, either add more HDD's to the storage server or build >> another server. If another server, shut it down when you are not >> using it. >> > Speaking as someone who has used amanda for about 25 years: > > People don't always understand that one of Amanda prime directives is to > balance the size of an individual back up run by advancing the level 3 > scheduled for tonight, by advancing it to level 0 if this run is only > going to be small. The only guarantee is that if you have a 10 day > schedule, all machines/dle's, will get that level 0 backup not more than > 10 days after the last one. You choose how many days long that cycle > is. I adjust it so the storage is around 75 to 80% used after the > schedule has stabilized. This may take quite a few such cycles. > Designed to run every night when things are relatively quiet, how this > works well depends on the other machines it is backing up be available. > > Machines missing at backup time can and will muck things up for this > efficient scheduling. Corporate users of Amanda, used to doing it their > way, backing the weeks business on friday nights just don't understand > that the Amanda way gets them a 100% coverage backup by backing up only > the differences from the previous run of that dle every night is far > superior to their fridey night when most of the offices machines are > turned off for the weekend. For those cases we recommend composing two > or more dle files and rigging cron to run them at more appropriate > scheduling. This can be fairly easily done but MBA's watching every watt > on the power bill just don't see it that way. They will get burnt when > their place burns. I believe all of my computers have one or both of the following BIOS/UEFI features: 1. Wake on LAN. 2. Wake at preset day/time. Perhaps your client computers also have such and you could configure it to coordinate with Amanda. David
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2024-01-22 06:50 +0100 |
| Message-ID | <HYVm1-4Jyv-1@gated-at.bofh.it> |
| In reply to | #266434 |
On 1/21/24 18:29, David Christensen wrote: > On 1/21/24 14:48, gene heskett wrote: >> On 1/21/24 16:13, David Christensen wrote: >>> On 1/21/24 03:47, gene heskett wrote: >>>> On 1/21/24 01:33, David Christensen wrote: >>>>> I am still uncertain if those are internal SSD errors or SATA >>>>> errors. Please check if you see matching errors in dmesg(1). >>>>> >>>> There aren't any. Those hours would very closely correspond to my >>>> attempts to rsync and the OOM deamon killed the machine, which it >>>> did around 10 times. So logging by then had been killed. That to me >>>> is the smoking gun. >>> >>> >>> Kernel ring buffer is renewed with each boot and newer messages >>> overwrite older messages. So, you will want to save or clear the >>> ring buffer with demsg(1), save a SMART full report, exercise the >>> disk with dd(1) and/or a SMART test, save the ring buffer, save a >>> SMART full report, and analyze everything to see if you have disk >>> problems, SATA problems, and/or system problems. Once everything >>> passes without error, the disk is ready to be put into service. >>> >>> >>>> 2T is enough /home for the nonce. so I'll do the rsync thing going >>>> the other direction, using it for a backup of /home until I'm ready >>>> for trixie. >>>> >>>> However I am tempted to zero the drives an recreate the raid w/o >>>> formatting since the mdadm seems capable to installing itw own >>>> filesystems to use the whole drive unpartitioned, giving me a backup >>>> that sizewise is about the same as the single 2T drive has now. >>>> >>>> And although my single experience with lvm over a decade ago was a >>>> total disaster, made out of used spinning rust I may now see how the >>>> other 4 2T's assembled as a lvm for amandas vtapes as an 8T lvm to >>>> backup the whole system, which in addition to the 4 cnc'd machines, >>>> has over the last 5 years seen a train of 3d printers go by. If all >>>> 3, currently a WIP, get rebuilt, the smallest is 305 by, the largest >>>> is 400 by. And all I hope will lay plastic at 200+ mm a second. >>>> Normal consumer stuff is 40 to 60. >>>> >>>> Obviously I have an eclectic choice of too many hobbies. ;o)> >>>> Now if curiosity doesn't kill this cat, I need to find some >>>> breakfast and git to it. >>> >>> >>> This and other threads have led me to the conclusion that consumer >>> SSD's are meant for devices that are off most of the time -- e.g. >>> notepad, laptop, desktop, and workstation computers. If you put them >>> into a NAS/ file server and run them 24x7, they will die sometime >>> after 2 years. >>> >> That has not been my experience at all David, I bought a 4 pack of >> 120G ssd's when they were the biggest available and replaced 3 >> spinning rust drives that had 50-70k hours on them with these. My cnc >> machines are all wired so power for the mill/lathe/what have you is >> totally controlled by the enable key, f2, so if f2 is off only the >> computer is running. That was at least 6 years ago. Then I installed a >> 240G as an extra drive on the rpi4 that runs my biggest lathe and made >> a buildbot out of it to pull linuxcnc-master from github and build it, >> also armhf kernels for linuxcnc's realtime needs. The 120G >> disappeared in about a year, replaced the adapter with a startech, >> drive was and is just fine. There is now at least 5 years on everyone >> of those original 120's, zero SSD problems in the whole lot. > > > I also have small SSD's that have lasted far longer than 2 years on > mixed duty, including 24x7 (Intel SSD 520 Series 60 GB). The relevant > recent threads on this list seem to be 1+ TB Samsung's. > > > It is interesting to note that BackBlaze does not seem to use Samsung > SSD's: > > https://www.backblaze.com/blog/ssd-edition-2023-mid-year-drive-stats-review/ > > >>> 3. For Amanda, either add more HDD's to the storage server or build >>> another server. If another server, shut it down when you are not >>> using it. >>> >> Speaking as someone who has used amanda for about 25 years: >> >> People don't always understand that one of Amanda prime directives is >> to balance the size of an individual back up run by advancing the >> level 3 scheduled for tonight, by advancing it to level 0 if this run >> is only going to be small. The only guarantee is that if you have a 10 >> day schedule, all machines/dle's, will get that level 0 backup not >> more than 10 days after the last one. You choose how many days long >> that cycle is. I adjust it so the storage is around 75 to 80% used >> after the schedule has stabilized. This may take quite a few such >> cycles. Designed to run every night when things are relatively quiet, >> how this works well depends on the other machines it is backing up be >> available. >> >> Machines missing at backup time can and will muck things up for this >> efficient scheduling. Corporate users of Amanda, used to doing it >> their way, backing the weeks business on friday nights just don't >> understand that the Amanda way gets them a 100% coverage backup by >> backing up only the differences from the previous run of that dle >> every night is far superior to their fridey night when most of the >> offices machines are turned off for the weekend. For those cases we >> recommend composing two or more dle files and rigging cron to run them >> at more appropriate scheduling. This can be fairly easily done but >> MBA's watching every watt on the power bill just don't see it that >> way. They will get burnt when their place burns. > > > I believe all of my computers have one or both of the following > BIOS/UEFI features: > > 1. Wake on LAN. > > 2. Wake at preset day/time. > > > Perhaps your client computers also have such and you could configure it > to coordinate with Amanda. > > > David > Unfortunately, amanda is truely ancient, for some reason the originator who first wrote it in the later 70's IIRC sold it nearly 20 years ago to a commercial outfit called zmanda, who took it more or less commercial, throwing the amanda named version under the buss. They must have ran out of money and resold it to another outfit, who has redoubled their effort to get rid of the free version. One of the things it has not been fixed to do, is issue a wakeup call, and wait for the clients to get their stuff in one sock, say 30 seconds to get everything spun up and ready to take orders, so I'm pretty sure a client that doesn't respond in milliseconds will be skipped. So basically, amanda needs to be officially forked since the current owner, Betsol has not made any contribution to amanda that amounts to an actual update but once in 6 or 7 years now, There's several things it now needs, such as the wake-on-lan support done right. Python is part of it but python 2 is still needed. Or a whole new start for something to replace and put it back squarely in the gplv2 or 3 camp. If there is actually another capable of diddling the level schedule like amanda does, I'm sure I could name some of the major users that would jump ship in a week or so once they became aware of a workalike. Take care, David. I'm going to turn on a blanket, its 5F out. And the wind is creeping up. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | David Christensen <dpchrist@holgerdanske.com> |
|---|---|
| Date | 2024-01-22 10:50 +0100 |
| Message-ID | <HYZ6i-4LJN-9@gated-at.bofh.it> |
| In reply to | #266440 |
On 1/21/24 21:42, gene heskett wrote: > On 1/21/24 18:29, David Christensen wrote: >> On 1/21/24 14:48, gene heskett wrote: >>> On 1/21/24 16:13, David Christensen wrote: >>>> On 1/21/24 03:47, gene heskett wrote: >>>>> On 1/21/24 01:33, David Christensen wrote: >>>> 3. For Amanda, either add more HDD's to the storage server or build >>>> another server. If another server, shut it down when you are not >>>> using it. >>> ... >>> Designed to run every night when things are relatively quiet, >>> how this works well depends on the other machines it is backing up be >>> available. >> ... >> 1. Wake on LAN. >> >> 2. Wake at preset day/time. > ... > Unfortunately, amanda is truely ancient, for some reason the originator > who first wrote it in the later 70's IIRC sold it nearly 20 years ago to > a commercial outfit called zmanda, who took it more or less commercial, > throwing the amanda named version under the buss. They must have ran out > of money and resold it to another outfit, who has redoubled their effort > to get rid of the free version. One of the things it has not been fixed > to do, is issue a wakeup call, and wait for the clients to get their > stuff in one sock, say 30 seconds to get everything spun up and ready to > take orders, so I'm pretty sure a client that doesn't respond in > milliseconds will be skipped. So basically, amanda needs to be > officially forked since the current owner, Betsol has not made any > contribution to amanda that amounts to an actual update but once in 6 or > 7 years now, There's several things it now needs, such as the > wake-on-lan support done right. Python is part of it but python 2 is > still needed. Or a whole new start for something to replace and put it > back squarely in the gplv2 or 3 camp. If there is actually another > capable of diddling the level schedule like amanda does, I'm sure I > could name some of the major users that would jump ship in a week or so > once they became aware of a workalike. It appears Amanda has a script API for both the client and the server: https://manpages.debian.org/buster/amanda-common/amanda-scripts.7.en.html The zmanda wiki has a Script API page, but it is empty (?): https://wiki.zmanda.com/index.php/Script_API. For BIOS/UEFI wake-on-lan, it might be possible to write a script that wakes the clients, to write a script that shuts down the clients, to configure the Amanda server to run the wake script before backups, and to configure the Amanda server to run the shutdown script after backups. For BIOS/UEFI wake at preset day/time, it might be possible to set the clients to wake before the scheduled backup time, to write a script that shuts down the clients, and to configure the Amanda server to run the shutdown script after backups. David
[toc] | [prev] | [next] | [standalone]
Page 5 of 9 — ← Prev page 1 2 3 4 [5] 6 7 8 9 Next page →
Back to top | Article view | linux.debian.user
csiph-web