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 1 of 9 [1] 2 3 4 5 6 7 8 9 Next page →
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2024-01-13 03:50 +0100 |
| Subject | smartctl cannot access my storage, need syntax help |
| Message-ID | <HVCfT-2HSR-7@gated-at.bofh.it> |
I just found an mbox file in my home directory, containing about 90 days worth of undelivered msgs from smartctl running as root. smartctl says my raid10 is dying, but will not access the drives for detail. The -d /dev/sde1 for instance generates a help msg saying it needs a devicename as final argument, being run as "sudo smartctl -i -d /dev/sde1". or as -i -d /dev/md0p1??? Typical: sudo smartctl -i -d /dev/md0p1: gene@coyote:~$ sudo smartctl -i -d /dev/md0p1 smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.0-17-rt-amd64] (local build) Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org ERROR: smartctl requires a device name as the final command-line argument. Use smartctl -h to get a usage summary Instructions please... Thank you. 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] | [next] | [standalone]
| From | "Gareth Evans" <donotspam@fastmail.fm> |
|---|---|
| Date | 2024-01-13 04:00 +0100 |
| Message-ID | <HVCpz-2HW8-3@gated-at.bofh.it> |
| In reply to | #265863 |
On Sat 13/01/2024 at 02:42, gene heskett <gheskett@shentel.net> wrote: > I just found an mbox file in my home directory, containing about 90 days > worth of undelivered msgs from smartctl running as root. > > smartctl says my raid10 is dying, but will not access the drives for > detail. The -d /dev/sde1 for instance generates a help msg saying it > needs a devicename as final argument, being run as "sudo smartctl -i -d > /dev/sde1". or as -i -d /dev/md0p1??? > Typical: sudo smartctl -i -d /dev/md0p1: > gene@coyote:~$ sudo smartctl -i -d /dev/md0p1 > smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.0-17-rt-amd64] (local build) > Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org > > ERROR: smartctl requires a device name as the final command-line argument. > > > Use smartctl -h to get a usage summary > > > Instructions please... Hi Gene, You seem to be asking it to operate on partitions. smartctl -options /dev/sdX is the form, I believe, in which sdX must be a device, not a virtual thing such as MD, LVM etc.
[toc] | [prev] | [next] | [standalone]
| From | Andy Smith <andy@strugglers.net> |
|---|---|
| Date | 2024-01-13 04:00 +0100 |
| Message-ID | <HVCpz-2HW8-1@gated-at.bofh.it> |
| In reply to | #265863 |
Hi Gene, There are some indicators of a fundamental lack of understanding here I'm afraid. On Fri, Jan 12, 2024 at 09:42:54PM -0500, gene heskett wrote: > smartctl says my raid10 is dying, No it doesn't; smartctl works on drives, not mdadm arrays. mdadm arrays are composed of block devices. Therefore any output you get from smartd refers to a storage drive, not an mdadm array. As usual you have not bothered to show us what you are talking about (the email from smartd), so we are left to guess. We should not assume that it even says what you think it says. > The -d /dev/sde1 for instance generates a help msg saying it needs a > devicename as final argument, being run as "sudo smartctl -i -d /dev/sde1". > or as -i -d /dev/md0p1??? Neither. /dev/sde1 is a partition on a block device. /dev/md0p1 is a partition on an mdadm array. Neither one is something that smartd works with. You probably wanted /dev/sde. Also, the -d option of smartctl specifies the device type. You almost certainly don't need it. If you don't absolutely know why you are using -d, don't use it. So: # smartctl -i /dev/sde or, heck, get all the info at once: # smartctl -a /dev/sde ********************************************************************** If there is anything in that output that you have questions about, please make sure to quote the full and unedited output back here to the list, so we aren't left guessing what the subject of discussion is. ********************************************************************** Thanks, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2024-01-13 06:00 +0100 |
| Message-ID | <HVEhH-2J79-3@gated-at.bofh.it> |
| In reply to | #265866 |
On 1/12/24 21:56, Andy Smith wrote: > Hi Gene, > > There are some indicators of a fundamental lack of understanding > here I'm afraid. > > On Fri, Jan 12, 2024 at 09:42:54PM -0500, gene heskett wrote: >> smartctl says my raid10 is dying, > > No it doesn't; smartctl works on drives, not mdadm arrays. mdadm > arrays are composed of block devices. Therefore any output you get > from smartd refers to a storage drive, not an mdadm array. > This appears to be true, there are 4 1t drives as a raid10, and the various messages in that mbox file name 3 of the individual drives. But those individual drives cannot now be found by smartctl. So I must be doing something wrong. individually it names /dev/sde1, /dev/sdg1, and /dev/sdd1. but -h offers no syntax help that works > As usual you have not bothered to show us what you are talking about > (the email from smartd), so we are left to guess. We should not > assume that it even says what you think it says. copy paste from another shell: gene@coyote:~$ sudo smartctl -i -d /dev/sde1 [sudo] password for gene: smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.0-17-rt-amd64] (local build) Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org ERROR: smartctl requires a device name as the final command-line argument. Ok, got that figure out, the -d specs the interface sat ot whatever. Then I find the linux has played 52 pickup with the device names. There are in actual fact 3 sata controller is this machine, the motherboards 6 ports, 6 more on an inexpensive sata contrller that are actually the 4 raid10 amsung 870 1T drives, and 4 more on a more sxpensive 16 port card which has a quartet of 2T gigastone SSD's on it, but the drives are not found in the order of the controllers. That raid10 was composed w/o the third controller. blkid does not sort them in order either. And of coarse does not list whats unmounted, forcing me to ident the drive by gparted in order to get its device name. From that I might be able to construct another raid from the 8T of 4 2T drives but its confusing as hell when the first of those 2T drives is assigned /dev/sde and the next 4 on the new controller are /dev/sdi, j, k, & l. So it appears I have 5 of those gigastones, and sde is the odd one So that one could be formatted ext4 and serve as a backup of the raid10. But since I can't copy a locked file, how do I make an image of that raid10 to /dev/sde and get every byte? That seems like the first step to me. > Neither. /dev/sde1 is a partition on a block device. > /dev/md0p1 is a partition on an mdadm array. Neither one is > something that smartd works with. I've got that now. > > You probably wanted /dev/sde. > > Also, the -d option of smartctl specifies the device type. You > almost certainly don't need it. If you don't absolutely know why > you are using -d, don't use it. So: > > # smartctl -i /dev/sde > > or, heck, get all the info at once: > > # smartctl -a /dev/sde > > ********************************************************************** > If there is anything in that output that you have questions about, > please make sure to quote the full and unedited output back here to > the list, so we aren't left guessing what the subject of > discussion is. > ********************************************************************** > > Thanks, > Andy > /dev/sde1 has been formatted and mounted, what cmd line will copy every byte including locked files in that that raid10 to it? Thank you 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 | Andy Smith <andy@strugglers.net> |
|---|---|
| Date | 2024-01-13 16:50 +0100 |
| Message-ID | <HVOqJ-2PK9-5@gated-at.bofh.it> |
| In reply to | #265867 |
Hi Gene, On Fri, Jan 12, 2024 at 11:57:23PM -0500, gene heskett wrote: > On 1/12/24 21:56, Andy Smith wrote: > > No it doesn't; smartctl works on drives, not mdadm arrays. mdadm > > arrays are composed of block devices. Therefore any output you get > > from smartd refers to a storage drive, not an mdadm array. > > > This appears to be true, there are 4 1t drives as a raid10, and the various > messages in that mbox file name 3 of the individual drives. Messages you do not show us, meanwhile the rest of your report is littered with errors, so I'm afraid I can't take you at your word until you show me. I repeat, smartd only works with whole drives. Those emails will show device paths for whole drives. > But those individual drives cannot now be found by smartctl. You have not yet demonstrated use of a single correct smartctl command even though I literally told you what to type. > individually it names /dev/sde1, /dev/sdg1, and > /dev/sdd1. I don't believe that you have an email from smartctl saying any of that. So please show us. Again, it would be plausible for these emails to mention /dev/sde etc. > > As usual you have not bothered to show us what you are talking about > > (the email from smartd), so we are left to guess. We should not > > assume that it even says what you think it says. > > copy paste from another shell: > gene@coyote:~$ sudo smartctl -i -d /dev/sde1 Here is what I said, which is quoted above, but I'll repeat it here for emphasis: > As usual you have not bothered to show us what you are talking > about (THE EMAIL FROM SMARTD) You then proceed to show us something that is not the email from smartd — that is the very topic of your email — but just repeat the output of a command that I already advised you was erroneously formed. > blkid does not sort them in order either. And of coarse does not list whats > unmounted, forcing me to ident the drive by gparted in order to get its > device name. From that I might be able to construct another raid from the 8T > of 4 2T drives but its confusing as hell when the first of those 2T drives > is assigned /dev/sde and the next 4 on the new controller are /dev/sdi, j, > k, & l. WHAT ON EARTH are you talking about. You start off by complaining about an email that you don't show us, by email two you are on about tearing your RAID apart and making a new one, all without a shred of relevant information or the first idea of how to show the status of anything. You are working blind here, DO NOT DO ANYTHING until you fully understand what is going on. Start with your first concern which was these emails from smartd. SHOW THEM TO US. > > or, heck, get all the info at once: > > > > # smartctl -a /dev/sde > > > > ********************************************************************** > > If there is anything in that output that you have questions about, > > please make sure to quote the full and unedited output back here to > > the list, so we aren't left guessing what the subject of > > discussion is. > > ********************************************************************** > > > > Thanks, > > Andy > > > /dev/sde1 has been formatted and mounted, what cmd line will copy every byte > including locked files in that that raid10 to it? !? For the love of God can someone, anyone, any intelligent entity out there, explain to me how I could have been ANY MORE EXPLICIT about the need for you to run a single command that I specified and show us the output of it? And did you do that? No, apparently you have nuked a drive that we don't know the status of. Incredible. Let's just assume for a second that we can just ignore everything you have said previously and focus on your last question about copying data, why would anyone even both responding given that as demonstrated here you are prepared to ignore even the most basic explicit advice and do something insane like nuke a whole drive? Just what is the point? Lost for words. -- https://bitfolk.com/ -- No-nonsense VPS hosting
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2024-01-13 18:10 +0100 |
| Message-ID | <HVPG9-2QG5-5@gated-at.bofh.it> |
| In reply to | #265886 |
On 1/13/24 10:49, Andy Smith wrote:
> Hi Gene,
>
> On Fri, Jan 12, 2024 at 11:57:23PM -0500, gene heskett wrote:
>> On 1/12/24 21:56, Andy Smith wrote:
>>> No it doesn't; smartctl works on drives, not mdadm arrays. mdadm
>>> arrays are composed of block devices. Therefore any output you get
>>> from smartd refers to a storage drive, not an mdadm array.
>>>
>> This appears to be true, there are 4 1t drives as a raid10, and the various
>> messages in that mbox file name 3 of the individual drives.
>
> Messages you do not show us, meanwhile the rest of your report is
> littered with errors, so I'm afraid I can't take you at your word
> until you show me.
>
> I repeat, smartd only works with whole drives. Those emails will
> show device paths for whole drives.
>
>> But those individual drives cannot now be found by smartctl.
>
> You have not yet demonstrated use of a single correct smartctl
> command even though I literally told you what to type.
>
>> individually it names /dev/sde1, /dev/sdg1, and
>> /dev/sdd1.
>
> I don't believe that you have an email from smartctl saying any of
> that. So please show us. Again, it would be plausible for
> these emails to mention /dev/sde etc.
>
>>> As usual you have not bothered to show us what you are talking about
>>> (the email from smartd), so we are left to guess. We should not
>>> assume that it even says what you think it says.
>>
>> copy paste from another shell:
>> gene@coyote:~$ sudo smartctl -i -d /dev/sde1
>
> Here is what I said, which is quoted above, but I'll repeat it here
> for emphasis:
>
>> As usual you have not bothered to show us what you are talking
>> about (THE EMAIL FROM SMARTD)
>
> You then proceed to show us something that is not the email from
> smartd — that is the very topic of your email — but just repeat the
> output of a command that I already advised you was erroneously
> formed.
>
>> blkid does not sort them in order either. And of coarse does not list whats
>> unmounted, forcing me to ident the drive by gparted in order to get its
>> device name. From that I might be able to construct another raid from the 8T
>> of 4 2T drives but its confusing as hell when the first of those 2T drives
>> is assigned /dev/sde and the next 4 on the new controller are /dev/sdi, j,
>> k, & l.
>
> WHAT ON EARTH are you talking about. You start off by complaining
> about an email that you don't show us, by email two you are on about
> tearing your RAID apart and making a new one, all without a shred of
> relevant information or the first idea of how to show the status of
> anything.
>
> You are working blind here, DO NOT DO ANYTHING until you fully
> understand what is going on.
>
> Start with your first concern which was these emails from smartd.
> SHOW THEM TO US.
>
>>> or, heck, get all the info at once:
>>>
>>> # smartctl -a /dev/sde
>>>
>>> **********************************************************************
>>> If there is anything in that output that you have questions about,
>>> please make sure to quote the full and unedited output back here to
>>> the list, so we aren't left guessing what the subject of
>>> discussion is.
>>> **********************************************************************
>>>
>>> Thanks,
>>> Andy
>>>
>> /dev/sde1 has been formatted and mounted, what cmd line will copy every byte
>> including locked files in that that raid10 to it?
>
> !?
>
> For the love of God can someone, anyone, any intelligent entity
> out there, explain to me how I could have been ANY MORE EXPLICIT
> about the need for you to run a single command that I specified and
> show us the output of it?
>
> And did you do that?
>
> No, apparently you have nuked a drive that we don't know the status
> of.
>
> Incredible.
>
> Let's just assume for a second that we can just ignore everything
> you have said previously and focus on your last question about
> copying data, why would anyone even both responding given that as
> demonstrated here you are prepared to ignore even the most basic
> explicit advice and do something insane like nuke a whole drive?
>
> Just what is the point?
>
> Lost for words.
>
So am I Andy. Since writing that, and my urge to get rid of a 30+ second
delay on opening ANYTHING that wants write perms to this raid, I've done
this this morning:
used gparted to format to ext4 a single gpt partition on that /dev/sde
with a LABEL=homesde1 but forgot the 1 when editing /etc/fstab to
remount it on a reboot to /mnt/homesde1, which resulted in a failed
boot, look up the root pw and finally get in to fix /etc/fstab for the
missing 1 in the labelname.
but first mounted a 2t gigastone ssd to /mnt/homesde1 which is where it
showed up in an lsblk -f report.
Spent 2+ hours rsync'ing with:
sudo rsync -av /home/ /mnt/homesde1
which worked entirely within the same 6 port controller as this raid10
is running on.
reboot failed, moved the data cable to the motherboard port 5 or 6 (or
maybe 1 or 2, 6 ports, nfi which is 0 and which is 5) but its on the
mobo ports now, should be easily found at boot time.
Finally look up root pw, get in to fix /etc/fstab and get booted.
Talk about portable devicenames, that drive is now /dev/sdk1 !!! And
empty of a LABELname but now has the 360gigs of data I just rsync'd to it.
but on reboot, its now /dev/sdb1 and empty.
from a df:
gene@coyote:~$ df
Filesystem 1K-blocks Used Available Use% Mounted on
udev 16327704 0 16327704 0% /dev
tmpfs 3272684 1888 3270796 1% /run
/dev/sda1 863983352 376505108 443516596 46% /
tmpfs 16363420 1244 16362176 1% /dev/shm
tmpfs 5120 8 5112 1% /run/lock
/dev/sda3 47749868 132 45291728 1% /tmp
/dev/md0p1 1796382580 334985304 1370072300 20% /home
/dev/sdb1 1967892164 28 1867855888 1% /mnt/homesde1
tmpfs 3272684 2544 3270140 1% /run/user/1000
gene@coyote:~$
and gparted now says that indeed, /dev/sdb is the drive with the label
"homesde1" on it. And showing 31GiB used. What for unless thats ext4
overhead. All I can see on /mnt/homesde1 is lost+found, which is empty.
So at this point I still have a home raid10, and have NDI where the he!!
the rsync line actually copied 360 Gb of stuff from home to.
smartctl -a /dev/sdb shows:
gene@coyote:~$ sudo smartctl -a /dev/sdb
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.0-17-rt-amd64] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Device Model: Gigastone SSD <- the devices name
Serial Number: GST02TBG221146
Firmware Version: T0917A0
User Capacity: 2,048,408,248,320 bytes [2.04 TB]
Sector Size: 512 bytes logical/physical
Rotation Rate: Solid State Device
Form Factor: 2.5 inches
TRIM Command: Available
Device is: Not in smartctl database 7.3/5319
ATA Version is: ACS-3 T13/2161-D revision 4
SATA Version is: SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Sat Jan 13 11:28:50 2024 EST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection:
Disabled.
Self-test execution status: ( 0) The previous self-test routine
completed
without error or no self-test
has ever
been run.
Total time to complete Offline
data collection: ( 120) seconds.
Offline data collection
capabilities: (0x11) SMART execute Offline immediate.
No Auto Offline data collection
support.
Suspend Offline collection upon new
command.
No Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
No Selective Self-test supported.
SMART capabilities: (0x0002) Does not save SMART data before
entering power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 10) minutes.
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
1 Raw_Read_Error_Rate 0x0032 100 100 050 Old_age
Always - 0
5 Reallocated_Sector_Ct 0x0032 100 100 050 Old_age
Always - 0
9 Power_On_Hours 0x0032 100 100 050 Old_age
Always - 884
12 Power_Cycle_Count 0x0032 100 100 050 Old_age
Always - 5
160 Unknown_Attribute 0x0032 100 100 050 Old_age Always
- 0
161 Unknown_Attribute 0x0033 100 100 050 Pre-fail Always
- 100
163 Unknown_Attribute 0x0032 100 100 050 Old_age Always
- 10
164 Unknown_Attribute 0x0032 100 100 050 Old_age Always
- 46
165 Unknown_Attribute 0x0032 100 100 050 Old_age Always
- 2
166 Unknown_Attribute 0x0032 100 100 050 Old_age Always
- 0
167 Unknown_Attribute 0x0032 100 100 050 Old_age Always
- 0
168 Unknown_Attribute 0x0032 100 100 050 Old_age Always
- 1500
169 Unknown_Attribute 0x0032 100 100 050 Old_age Always
- 100
175 Program_Fail_Count_Chip 0x0032 100 100 050 Old_age Always
- 0
176 Erase_Fail_Count_Chip 0x0032 100 100 050 Old_age Always
- 0
177 Wear_Leveling_Count 0x0032 100 100 050 Old_age Always
- 0
178 Used_Rsvd_Blk_Cnt_Chip 0x0032 100 100 050 Old_age Always
- 0
181 Program_Fail_Cnt_Total 0x0032 100 100 050 Old_age Always
- 0
182 Erase_Fail_Count_Total 0x0032 100 100 050 Old_age Always
- 0
192 Power-Off_Retract_Count 0x0032 100 100 050 Old_age Always
- 4
194 Temperature_Celsius 0x0022 100 100 050 Old_age Always
- 40
195 Hardware_ECC_Recovered 0x0032 100 100 050 Old_age Always
- 0
196 Reallocated_Event_Count 0x0032 100 100 050 Old_age Always
- 0
197 Current_Pending_Sector 0x0032 100 100 050 Old_age Always
- 0
198 Offline_Uncorrectable 0x0032 100 100 050 Old_age Always
- 0
199 UDMA_CRC_Error_Count 0x0032 100 100 050 Old_age Always
- 0
232 Available_Reservd_Space 0x0032 100 100 050 Old_age Always
- 100
241 Total_LBAs_Written 0x0030 100 100 050 Old_age
Offline - 986
242 Total_LBAs_Read 0x0030 100 100 050 Old_age
Offline - 7
245 Unknown_Attribute 0x0032 100 100 050 Old_age Always
- 0
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]
Selective Self-tests/Logging not supported
*********
please $diety, deliver me from linux's vaporous disk naming scheme that
changes faster than the weather. Even device LABEL= does not work. I
mounted that drive by its label to /mnt/homesde1 and rsync'd /home/ to
it but that 360Gb of data went someplace else. Since the data, according
to what I see in gparted, actually went to /dev/sdk1, which is another
of the 2T gigastones, I intend to make a raid6 out of, no harm to my
data is done. My raid10 was not destroyed. But I'm burned out and
frustrated. This is hardware, not a roll of the dice per boot.
I can easily erase and restart that drive for a raid with gparted, But
howinhell do I get a stable drive detection system so I know what I am
doing??????????????????????????????????????????
Besides that, I'm running low on hair too.
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 | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2024-01-13 18:30 +0100 |
| Message-ID | <HVPZv-2QMd-7@gated-at.bofh.it> |
| In reply to | #265886 |
On 1/13/24 10:49, Andy Smith wrote: > Hi Gene, > > On Fri, Jan 12, 2024 at 11:57:23PM -0500, gene heskett wrote: >> On 1/12/24 21:56, Andy Smith wrote: >>> No it doesn't; smartctl works on drives, not mdadm arrays. mdadm >>> arrays are composed of block devices. Therefore any output you get >>> from smartd refers to a storage drive, not an mdadm array. >>> >> This appears to be true, there are 4 1t drives as a raid10, and the various >> messages in that mbox file name 3 of the individual drives. > > Messages you do not show us, meanwhile the rest of your report is > littered with errors, so I'm afraid I can't take you at your word > until you show me. > > I repeat, smartd only works with whole drives. Those emails will > show device paths for whole drives. > >> But those individual drives cannot now be found by smartctl. > > You have not yet demonstrated use of a single correct smartctl > command even though I literally told you what to type. > >> individually it names /dev/sde1, /dev/sdg1, and >> /dev/sdd1. > > I don't believe that you have an email from smartctl saying any of > that. So please show us. Again, it would be plausible for > these emails to mention /dev/sde etc. > >>> As usual you have not bothered to show us what you are talking about >>> (the email from smartd), so we are left to guess. We should not >>> assume that it even says what you think it says. >> >> copy paste from another shell: >> gene@coyote:~$ sudo smartctl -i -d /dev/sde1 > > Here is what I said, which is quoted above, but I'll repeat it here > for emphasis: > >> As usual you have not bothered to show us what you are talking >> about (THE EMAIL FROM SMARTD) > > You then proceed to show us something that is not the email from > smartd — that is the very topic of your email — but just repeat the > output of a command that I already advised you was erroneously > formed. > >> blkid does not sort them in order either. And of coarse does not list whats >> unmounted, forcing me to ident the drive by gparted in order to get its >> device name. From that I might be able to construct another raid from the 8T >> of 4 2T drives but its confusing as hell when the first of those 2T drives >> is assigned /dev/sde and the next 4 on the new controller are /dev/sdi, j, >> k, & l. > > WHAT ON EARTH are you talking about. You start off by complaining > about an email that you don't show us, by email two you are on about > tearing your RAID apart and making a new one, all without a shred of > relevant information or the first idea of how to show the status of > anything. > > You are working blind here, DO NOT DO ANYTHING until you fully > understand what is going on. > > Start with your first concern which was these emails from smartd. > SHOW THEM TO US. > >>> or, heck, get all the info at once: >>> >>> # smartctl -a /dev/sde >>> >>> ********************************************************************** >>> If there is anything in that output that you have questions about, >>> please make sure to quote the full and unedited output back here to >>> the list, so we aren't left guessing what the subject of >>> discussion is. >>> ********************************************************************** >>> >>> Thanks, >>> Andy >>> >> /dev/sde1 has been formatted and mounted, what cmd line will copy every byte >> including locked files in that that raid10 to it? > > !? > > For the love of God can someone, anyone, any intelligent entity > out there, explain to me how I could have been ANY MORE EXPLICIT > about the need for you to run a single command that I specified and > show us the output of it? > > And did you do that? > > No, apparently you have nuked a drive that we don't know the status > of. > > Incredible. > > Let's just assume for a second that we can just ignore everything > you have said previously and focus on your last question about > copying data, why would anyone even both responding given that as > demonstrated here you are prepared to ignore even the most basic > explicit advice and do something insane like nuke a whole drive? > > Just what is the point? > > Lost for words. > One last question before I embark on a replay of what I just did, and failed at. This time by using device labels. Does making a raid erase the drives label field in a gpt partition scheme? That question ought to have a simple yes or no answer. Thanks. 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 | Andy Smith <andy@strugglers.net> |
|---|---|
| Date | 2024-01-13 19:50 +0100 |
| Message-ID | <HVReW-2Rro-19@gated-at.bofh.it> |
| In reply to | #265898 |
Gene, On Sat, Jan 13, 2024 at 12:23:28PM -0500, gene heskett wrote: > Does making a raid erase the drives label field in a gpt partition scheme? > > That question ought to have a simple yes or no answer. I'm forced to conclude that it's a waste of anyone's time to try to help you since you don't listen to advice, won't even type commands you are asked to, and don't provide relevant information. On top of that between any two emails you embark on misguided epic restructuring of your entire computing environment rendering anything that was said in between utterly pointless. At this point you are just howling into the wind and we're hearing the noise from far away. Please get a blog or something, instead of directing it here, where well-meaning people can mistake it for something they could engage with. I assume this thread can now close since you are never going to provide the email from smartd that prompted it, for a system that no longer exists. Otherwise it's destined to become another Gene megathread with a shifting stream of consciousness topic of the hour. Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2024-01-14 00:30 +0100 |
| Message-ID | <HVVBT-2UcH-1@gated-at.bofh.it> |
| In reply to | #265903 |
On 1/13/24 13:41, Andy Smith wrote: > Gene, > > On Sat, Jan 13, 2024 at 12:23:28PM -0500, gene heskett wrote: >> Does making a raid erase the drives label field in a gpt partition scheme? >> >> That question ought to have a simple yes or no answer. > > I'm forced to conclude that it's a waste of anyone's time to try to > help you since you don't listen to advice, won't even type commands > you are asked to, and don't provide relevant information. I've furnished exactly what you asked for in previous msgs, until you ask for something that is NOT installed by bookworm and cannot be found by synaptic. It must take an extra long ladder to get up on the horse you are riding. On top of > that between any two emails you embark on misguided epic > restructuring of your entire computing environment rendering > anything that was said in between utterly pointless. I'm looking for a solution to a broken install, all caused by the installer finding a plugged in FDTI usb-serial adapter so it automatically assumed I was blind and automatically installed brltty and orca, which are not removable once installed without ripping the system apart rendering it unbootable. If orca is disabled, the system will _NOT_ reboot. And I catch hell for discriminating against the blind when I complained at the time. That took me 20+ installs to get this far because if I removed the exec bits on orca, disabling it=no reboot=yet another re-install go thru the same thing with orca yelling at me for every keystroke entered, till someone took pity on me and wrote to unplug the usb stuff which looks like a weeping willow tree here, nothing more or less. And I'm forced to conclude that a simple yes or no answer to what looks like a single, simple question to me, included above, is beyond you. Surely there is someone who /can/ answer that question. Do take care, stay warm, dry and well Andy. And unvaxed, so you might live to be my age. I am not. You are helpful, just not to me. That, I do not understand. It comes across to me that you have no time for anyone north of 50 years old, we are too dumb to be help when something goes south. The only part of the advanced age category I fit into is the poor short term memory of someone 89 years old, which I am. 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 | Steve McIntyre <steve@einval.com> |
|---|---|
| Date | 2024-01-14 14:40 +0100 |
| Message-ID | <HW8St-32FO-3@gated-at.bofh.it> |
| In reply to | #265908 |
Gene Heskett wrote: > >I'm looking for a solution to a broken install, all caused by the >installer finding a plugged in FDTI usb-serial adapter so it >automatically assumed I was blind and automatically installed brltty and >orca, which are not removable once installed without ripping the system >apart rendering it unbootable. If orca is disabled, the system will >_NOT_ reboot. And I catch hell for discriminating against the blind when >I complained at the time. > >That took me 20+ installs to get this far because if I removed the exec >bits on orca, disabling it=no reboot=yet another re-install go thru the >same thing with orca yelling at me for every keystroke entered, till >someone took pity on me and wrote to unplug the usb stuff which looks >like a weeping willow tree here, nothing more or less. Gene, *stop* doing this. When you ask for help with *one* issue (in this case, smartctl), looping around other issues you've had in the last few years *does not help*. It's unrelated, it obfuscates what you're saying, and it's *intensely* frustrating to the people here who might actually be trying to help you. You do this *a lot*. Please focus on one thing at a time, and we might be able to help you better. The usual advice applies: * Give a clear description of the problem you're seeing. Include command lines and command output, log entries or similar. Make it possible for people to actually identify the problem - vague descriptions make it much harder. * When people reply to you asking for more information, they're not doing that to annoy you. They're trying to understand the problem you've reported more, so they can help you fix it. If they ask you to run extra commands and report the output, *please do that*. * Stay on topic. If you have another issue you'd like help with, send a separate mail about that and have a separate thread of conversation about that issue. Don't mix things up. Please think about this, and help people to help you. >And I'm forced to conclude that a simple yes or no answer to what looks >like a single, simple question to me, included above, is beyond you. >Surely there is someone who /can/ answer that question. > >Do take care, stay warm, dry and well Andy. And unvaxed, so you might >live to be my age. > >I am not. You are helpful, just not to me. That, I do not understand. It >comes across to me that you have no time for anyone north of 50 years >old, we are too dumb to be help when something goes south. The only >part of the advanced age category I fit into is the poor short term >memory of someone 89 years old, which I am. It's nothing to do with your age. You keep on bringing this up. People are volunteering their time to help you. When you don't pay attention and go wandering off-topic it makes it much harder for people to help. I hope you can understand that. -- Steve McIntyre, Cambridge, UK. steve@einval.com Can't keep my eyes from the circling sky, Tongue-tied & twisted, Just an earth-bound misfit, I...
[toc] | [prev] | [next] | [standalone]
| From | Nicolas George <george@nsup.org> |
|---|---|
| Date | 2024-01-14 11:40 +0100 |
| Message-ID | <HW64h-311r-3@gated-at.bofh.it> |
| In reply to | #265866 |
Hi. Andy Smith (12024-01-13): > As usual you have not bothered to show us what you are talking about > (the email from smartd) And that leads you to write a patient and detailed answer, so surely it was the best way to proceed. Regards, -- Nicolas George
[toc] | [prev] | [next] | [standalone]
| From | Andy Smith <andy@strugglers.net> |
|---|---|
| Date | 2024-01-14 17:30 +0100 |
| Message-ID | <HWbwZ-34iv-3@gated-at.bofh.it> |
| In reply to | #265921 |
Hello, On Sun, Jan 14, 2024 at 11:37:08AM +0100, Nicolas George wrote: > Andy Smith (12024-01-13): > > As usual you have not bothered to show us what you are talking about > > (the email from smartd) > > And that leads you to write a patient and detailed answer, so surely it > was the best way to proceed. If only Gene had signalled that no matter what I had written, he was going to nuke it all and start again anyway. Then I could have given a detailed answer piped from /dev/urandom and nothing would have changed for anyone involved. Thanks, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
[toc] | [prev] | [next] | [standalone]
| From | Charles Curley <charlescurley@charlescurley.com> |
|---|---|
| Date | 2024-01-13 06:40 +0100 |
| Message-ID | <HVEUp-2JDX-1@gated-at.bofh.it> |
| In reply to | #265863 |
On Fri, 12 Jan 2024 21:42:54 -0500 gene heskett <gheskett@shentel.net> wrote: > gene@coyote:~$ sudo smartctl -i -d /dev/md0p1 Gene, you could try reading the fine man page. The -d option takes an argument, which eats the /dev/md0p1, leaving no device for smartctl to look at. I have no idea what md0p1 is, but I doubt it's a physical drive, like sda. So that's two problems. And you probably don't need the -d option. Try "ls /dev/sd?" and go from there. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
[toc] | [prev] | [next] | [standalone]
| From | David Christensen <dpchrist@holgerdanske.com> |
|---|---|
| Date | 2024-01-14 13:50 +0100 |
| Message-ID | <HW865-32as-1@gated-at.bofh.it> |
| In reply to | #265863 |
Re-ordered for clarity -- David. On 1/12/24 18:42, gene heskett wrote: > I just found an mbox file in my home directory, containing about 90 days > worth of undelivered msgs from smartctl running as root. Do you know how the mbox file got there? > smartctl says my raid10 is dying, ... Please post a console session with a command that displays the message. On 1/12/24 20:57, gene heskett wrote: > ... there are 4 1t drives as a raid10, and the > various messages in that mbox file name 3 of the individual drives. Please post a representative sample of the messages. > Then I find the linux has played 52 pickup with the device names. /dev/sd* device node names are unpredictable. The traditional solution is UUID's. Linux added /dev/disk/by-id/* a while ago and I am starting to use them as much as possible. Make sure you look very carefully at the serial numbers when you have several drives of the same make and model. > There are in actual fact 3 sata controller is this machine, the > motherboards 6 ports, 6 more on an inexpensive sata contrller that are > actually the 4 raid10 amsung 870 1T drives, and 4 more on a more > sxpensive 16 port card which has a quartet of 2T gigastone SSD's on it, > but the drives are not found in the order of the controllers. That > raid10 was composed w/o the third controller. So: * /home is on a RAID 10 with 2 @ mirror of 2 @ 1 TB Samsung 870 SSD? * 4 @ 2 TB Gigastone SSD for a new RAID 10? What drives are connected to which ports? What is on the other 20 ports? > blkid does not sort them in order either. And of coarse does not list > whats unmounted, forcing me to ident the drive by gparted in order to > get its device name. From that I might be able to construct another raid > from the 8T of 4 2T drives but its confusing as hell when the first of > those 2T drives is assigned /dev/sde and the next 4 on the new > controller are /dev/sdi, j, k, & l. > So it appears I have 5 of those gigastones, and sde is the odd one I am confused -- do you have 4 or 5 Gigastone 2 TB SSD? > So that one could be formatted ext4 and serve as a backup of the raid10. > how do I make an image of that > raid10 to /dev/sde and get every byte? That seems like the first step > to me. Please get a USB 3.x HDD, do a full backup of your entire computer, put it off-site, get another USB 3.x HDD, do another full backup, and keep it nearby. > But since I can't copy a locked file, What file is lock? Please post a console session that demonstrates. > /dev/sde1 has been formatted and mounted, what cmd line will copy every > byte including locked files in that that raid10 to it? See above for locked. Otherwise, I suggest rsync(1). On 1/13/24 09:02, gene heskett wrote: > ... I've done this this morning: > used gparted to format to ext4 a single gpt partition on that /dev/sde > with a LABEL=homesde1 but forgot the 1 when editing /etc/fstab to > remount it on a reboot to /mnt/homesde1, which resulted in a failed > boot, look up the root pw and finally get in to fix /etc/fstab for the > missing 1 in the labelname. > > but first mounted a 2t gigastone ssd to /mnt/homesde1 which is where it > showed up in an lsblk -f report. > Spent 2+ hours rsync'ing with: > sudo rsync -av /home/ /mnt/homesde1 > which worked entirely within the same 6 port controller as this raid10 > is running on. > > reboot failed, moved the data cable to the motherboard port 5 or 6 (or > maybe 1 or 2, 6 ports, nfi which is 0 and which is 5) but its on the > mobo ports now, should be easily found at boot time. > > Finally look up root pw, get in to fix /etc/fstab and get booted. > Talk about portable devicenames, that drive is now /dev/sdk1 !!! And > empty of a LABELname but now has the 360gigs of data I just rsync'd to it. > but on reboot, its now /dev/sdb1 and empty. > > from a df: > gene@coyote:~$ df > Filesystem 1K-blocks Used Available Use% Mounted on > udev 16327704 0 16327704 0% /dev > tmpfs 3272684 1888 3270796 1% /run > /dev/sda1 863983352 376505108 443516596 46% / > tmpfs 16363420 1244 16362176 1% /dev/shm > tmpfs 5120 8 5112 1% /run/lock > /dev/sda3 47749868 132 45291728 1% /tmp > /dev/md0p1 1796382580 334985304 1370072300 20% /home > /dev/sdb1 1967892164 28 1867855888 1% /mnt/homesde1 > tmpfs 3272684 2544 3270140 1% /run/user/1000 > gene@coyote:~$ > and gparted now says that indeed, /dev/sdb is the drive with the label > "homesde1" on it. > And showing 31GiB used. What for unless thats ext4 > overhead. All I can see on /mnt/homesde1 is lost+found, which is empty. > So at this point I still have a home raid10, and have NDI What does "NDI" mean? > where the he!! > the rsync line actually copied 360 Gb of stuff from home to. Please post: # ls -a /mnt # ls -a /mnt/homesde1 > gene@coyote:~$ sudo smartctl -a /dev/sdb Please use /dev/disk/by-id/* paths. > ... > Device Model: Gigastone SSD <- the devices name > Serial Number: GST02TBG221146 > ... > User Capacity: 2,048,408,248,320 bytes [2.04 TB] > Sector Size: 512 bytes logical/physical > ... > Form Factor: 2.5 inches > TRIM Command: Available > ... > SMART overall-health self-assessment test result: PASSED Okay. > 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 > 1 Raw_Read_Error_Rate 0x0032 100 100 050 Old_age > Always - 0 > 5 Reallocated_Sector_Ct 0x0032 100 100 050 Old_age > Always - 0 > 9 Power_On_Hours 0x0032 100 100 050 Old_age > Always - 884 > ... Attribute values of 100 for all VALUE and WORST makes sense for a brand new drive, which contradicts "Old_age" and "Pre-fail" (?). How long has that drive been in your computer? How many hours per week has it been on? > SMART Error Log Version: 1 > No Errors Logged Okay. > SMART Self-test log structure revision number 1 > No self-tests have been logged. [To run self-tests, use: smartctl -t] /sd Please run: # smartctl -t short /dev/disk/by-id/*GST02TBG221146* Wait a few minutes. Then run: # smartctl -x short /dev/disk/by-id/*GST02TBG221146* We do not need to see the whole output, but please post the "SMART Self-test log structure revision number 1" section. It should show the short test. > please $diety, deliver me from linux's vaporous disk naming scheme that > changes faster than the weather. Even device LABEL= does not work. I > mounted that drive by its label to /mnt/homesde1 and rsync'd /home/ to > it but that 360Gb of data went someplace else. Use script(1) to capture your console sessions. Save the files it generates. Use cat(1) to display their contents. > Since the data, according > to what I see in gparted, actually went to /dev/sdk1, > which is another > of the 2T gigastones, I intend to make a raid6 out of, no harm to my > data is done. My raid10 was not destroyed. But I'm burned out and > frustrated. This is hardware, not a roll of the dice per boot. > > I can easily erase and restart that drive for a raid with gparted, But > howinhell do I get a stable drive detection system so I know what I am > doing?????????????????????????????????????????? > > Besides that, I'm running low on hair too. Please use /dev/disk/by-id/* paths. On 1/13/24 09:23, gene heskett wrote: > One last question before I embark on a replay of what I just did, and > failed at. This time by using device labels. > > Does making a raid erase the drives label field in a gpt partition scheme? It has been several years since I used mdadm(8), but I suspect the answer depends upon whether you give whole disks as arguments or give disk partitions as arguments. If you give whole disks, it would not surprise me if mdadm(8) overwrote any and all sectors as it pleased, including MBR and/or GPT partition tables. If you give partitions, I would expect mdadm(8) to not write outside those partitions, so GPT labels should be untouched. Please also see mdadm(8) "CREATE MODE" and the discussion about partition type and version-1.x metadata. On 1/13/24 15:21, gene heskett wrote: > I'm looking for a solution to a broken install, all caused by the > installer finding a plugged in FDTI usb-serial adapter so it > automatically assumed I was blind and automatically installed brltty and > orca, which are not removable once installed without ripping the system > apart rendering it unbootable. If orca is disabled, the system will > _NOT_ reboot. And I catch hell for discriminating against the blind when > I complained at the time. > > That took me 20+ installs to get this far because if I removed the exec > bits on orca, disabling it=no reboot=yet another re-install go thru the > same thing with orca yelling at me for every keystroke entered, till > someone took pity on me and wrote to unplug the usb stuff which looks > like a weeping willow tree here, nothing more or less. Do you have a USB drive with an installation of Debian? If not, build one. I used SanDisk Ultra Fit USB 3.0 16 GB drives for many years. Now I use Samsung UM410 16 GB SSD's and a StarTech USB to SATA adapter cable. Then disconnect all the drives except the 4 @ 1 TB SSD's for the RAID10 /home, boot your USB Debian drive, assemble the RAID10, mount the file system read-only, and test for the 30 second delay. David
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2024-01-14 20:50 +0100 |
| Message-ID | <HWeEx-363k-11@gated-at.bofh.it> |
| In reply to | #265926 |
On 1/14/24 07:42, David Christensen wrote:
> Re-ordered for clarity -- David.
And snipped by Gene as I updated
>
> On 1/12/24 18:42, gene heskett wrote:
>> I just found an mbox file in my home directory, containing about 90
>> days worth of undelivered msgs from smartctl running as root.
>
>
> Do you know how the mbox file got there?
No, it just appeared.
>
>
>> smartctl says my raid10 is dying, ...
>
>
> Please post a console session with a command that displays the message.
This is a copy/paste of the second message in that file, the first from
smartctl, followed by the last message in that file:
From root@coyote.coyote.den Wed Nov 02 00:29:05 2022
Return-path: <root@coyote.coyote.den>
Envelope-to: root@coyote.coyote.den
Delivery-date: Wed, 02 Nov 2022 00:29:05 -0400
Received: from root by coyote.coyote.den with local (Exim 4.94.2)
(envelope-from <root@coyote.coyote.den>)
id 1oq5NB-000DBx-15
for root@coyote.coyote.den; Wed, 02 Nov 2022 00:29:05 -0400
To: root@coyote.coyote.den
Subject: SMART error (SelfTest) detected on host: coyote
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Message-Id: <E1oq5NB-000DBx-15@coyote.coyote.den>
From: root <root@coyote.coyote.den>
Date: Wed, 02 Nov 2022 00:29:05 -0400
Content-Length: 513
Lines: 16
Status: RO
X-Status:
X-Keywords:
X-UID: 2
This message was generated by the smartd daemon running on:
host name: coyote
DNS domain: coyote.den
The following warning/error was logged by the smartd daemon:
Device: /dev/sde [SAT], Self-Test Log error count increased from 0 to 1
Device info:
Samsung SSD 870 EVO 1TB, S/N:S626NF0R302507V, WWN:5-002538-f413394ae,
FW:SVT01B6Q, 1.00 TB
For details see host's SYSLOG.
You can also use the smartctl utility for further investigation.
Another message will be sent in 24 hours if the problem persists.
======= 3 more identical msgs refering to the other 3 drives in the
raid.=====
From root@coyote.coyote.den Wed Nov 16 06:22:02 2022
Return-path: <root@coyote.coyote.den>
Envelope-to: root@coyote.coyote.den
Delivery-date: Wed, 16 Nov 2022 06:22:02 -0500
Received: from root by coyote.coyote.den with local (Exim 4.94.2)
(envelope-from <root@coyote.coyote.den>)
id 1ovGUR-0000De-Bc
for root@coyote.coyote.den; Wed, 16 Nov 2022 06:21:59 -0500
To: root@coyote.coyote.den
Subject: SMART error (SelfTest) detected on host: coyote
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Message-Id: <E1ovGUR-0000De-Bc@coyote.coyote.den>
From: root <root@coyote.coyote.den>
Date: Wed, 16 Nov 2022 06:21:59 -0500
Content-Length: 592
Lines: 17
Status: RO
X-Status:
X-Keywords:
X-UID: 9
This message was generated by the smartd daemon running on:
host name: coyote
DNS domain: coyote.den
The following warning/error was logged by the smartd daemon:
Device: /dev/sdd [SAT], Self-Test Log error count increased from 1 to 2
Device info:
Samsung SSD 870 EVO 1TB, S/N:S626NF0R302502E, WWN:5-002538-f413394a9,
FW:SVT01B6Q, 1.00 TB
For details see host's SYSLOG.
You can also use the smartctl utility for further investigation.
The original message about this issue was sent at Wed Nov 2 06:59:04
2022 EDT
Another message will be sent in 24 hours if the problem persists.
I also note they are now very old messages but the file itself is dated
Jan 7nth. And syslog has been rotated several times since.
I'm not expert at interpreting smartctl reports, but I do not see such
in the smarttcl output now. going backwads thru the list, the 4th drive
in the raid has had 3334 errors, as had the third drive with 3332
ettors, the 1st and 2nd are clean.
One stanza of the error report:
Error 3328 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 28 00 54 a9 40 Error: UNC at LBA = 0x00a95400 = 11097088
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 28 00 54 a9 40 05 15:16:34.891 READ FPDMA QUEUED
61 18 18 e8 ea 67 40 03 15:16:34.891 WRITE FPDMA QUEUED
60 00 10 00 5e a9 40 02 15:16:34.891 READ FPDMA QUEUED
60 28 08 00 f4 87 40 01 15:16:34.891 READ FPDMA QUEUED
60 00 00 00 7c a9 40 00 15:16:34.891 READ FPDMA QUEUED
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% 10917
1847474376
# 2 Extended offline Completed: read failure 50% 10586
1847474376
So half the samsung 870's are on their way out. But nothing recent...
So I am now trying to get a good rsync copy on another drive.
>
> On 1/12/24 20:57, gene heskett wrote:
> > ... there are 4 1t drives as a raid10, and the
> > various messages in that mbox file name all of the individual drives.
>
>
> Please post a representative sample of the messages.
See above, most of it is swahili to me.
>
> > Then I find the linux has played 52 pickup with the device names.
>
>
> /dev/sd* device node names are unpredictable. The traditional solution
> is UUID's. Linux added /dev/disk/by-id/* a while ago and I am starting
> to use them as much as possible. Make sure you look very carefully at
> the serial numbers when you have several drives of the same make and model.
>
>
> > There are in actual fact 3 sata controller is this machine, the
> > motherboards 6 ports, 6 more on an inexpensive sata controller that are
> > actually the 4 raid10 Samsung 870 1T drives, and 4 more on a more
> > sxpensive 16 port card which has a quartet of 2T gigastone SSD's on it,
> > but the drives are not found in the order of the controllers. That
> > raid10 was composed w/o the third controller.
>
>
> So:
>
> * /home is on a RAID 10 with 2 @ mirror of 2 @ 1 TB Samsung 870 SSD?
I think thasts what you call a raid10
> * 4 @ 2 TB Gigastone SSD for a new RAID 10?
just installed, not mounted or made into a raid yet. WIP?
>
> What drives are connected to which ports?
4 Samsung 870 1T's are on the 1st added controller.
ATM 5, 2T gigastone's are on the 2nd, 16 port added controller
smarttcl says all 5 of those are fine.
>
>
> What is on the other 20 ports?
On the mobo? A big dvd writer and 2 other half T or 1T samsung drives
from earlier 860 runs, not currently mounted. No spinning rust anyplace
now. I don't appreciate being a lab rat for seagate to experiment on.
A current lsblk:
gene@coyote:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 931.5G 0 disk
├─sda1 8:1 0 838.2G 0 part /
├─sda2 8:2 0 46.8G 0 part [SWAP]
└─sda3 8:3 0 46.6G 0 part /tmp
sdb 8:16 1 0B 0 disk is probably my camera, currently
plugged in
sdc 8:32 1 0B 0 disk is probably my brother
MFP-J6920DW printer, always plugged in
first controller, 6 port
sdd 8:48 0 931.5G 0 disk
├─sdd1 8:49 0 900G 0 part
│ └─md0 9:0 0 1.7T 0 raid10
│ └─md0p1 259:0 0 1.7T 0 part /home
├─sdd2 8:50 0 30G 0 part
│ └─md1 9:1 0 60G 0 raid10 [SWAP]
└─sdd3 8:51 0 1.5G 0 part
└─md2 9:2 0 3G 0 raid10
sde 8:64 0 931.5G 0 disk
├─sde1 8:65 0 900G 0 part
│ └─md0 9:0 0 1.7T 0 raid10
│ └─md0p1 259:0 0 1.7T 0 part /home
├─sde2 8:66 0 30G 0 part
│ └─md1 9:1 0 60G 0 raid10 [SWAP]
└─sde3 8:67 0 1.5G 0 part
└─md2 9:2 0 3G 0 raid10
sdf 8:80 0 931.5G 0 disk
├─sdf1 8:81 0 900G 0 part
│ └─md0 9:0 0 1.7T 0 raid10
│ └─md0p1 259:0 0 1.7T 0 part /home
├─sdf2 8:82 0 30G 0 part
│ └─md1 9:1 0 60G 0 raid10 [SWAP]
└─sdf3 8:83 0 1.5G 0 part
└─md2 9:2 0 3G 0 raid10
sdg 8:96 0 931.5G 0 disk
├─sdg1 8:97 0 900G 0 part
│ └─md0 9:0 0 1.7T 0 raid10
│ └─md0p1 259:0 0 1.7T 0 part /home
├─sdg2 8:98 0 30G 0 part
│ └─md1 9:1 0 60G 0 raid10 [SWAP]
└─sdg3 8:99 0 1.5G 0 part
└─md2 9:2 0 3G 0 raid10
2nd controller, 16 ports, all 5 2T gigastone's
sdh 8:112 0 1.9T 0 disk
└─sdh1 8:113 0 1.9T 0 part
sdi 8:128 0 1.9T 0 disk
└─sdi1 8:129 0 1.9T 0 part
sdj 8:144 0 1.9T 0 disk
└─sdj1 8:145 0 1.9T 0 part
sdk 8:160 0 1.9T 0 disk
└─sdk1 8:161 0 1.9T 0 part
sdl 8:176 0 1.9T 0 disk
└─sdl1 8:177 0 1.9T 0 part
sr0 11:0 1 1024M 0 rom The internal dvd writer
gene@coyote:~$
>
>
> > blkid does not sort them in order either. And of coarse does not list
> > whats unmounted, forcing me to ident the drive by gparted in order to
> > get its device name. From that I might be able to construct another raid
> > from the 8T of 4 2T drives but its confusing as hell when the first of
> > those 2T drives is assigned /dev/sde and the next 4 on the new
> > controller are /dev/sdi, j, k, & l.
> > So it appears I have 5 of those gigastones, and sde is the odd one
Which when it was /dev/sde1, was plugged into the 1st extra controller
When the data cable was plugged into a motherboard port, it became
/dev/sdb1. So I've relabeled it, and about to test it on the second 16
port controller.
>
>
> I am confused -- do you have 4 or 5 Gigastone 2 TB SSD?
5, ordered in 2 separate orders.
>
> > So that one could be formatted ext4 and serve as a backup of the raid10.
What I am trying to do now, but cannot if it is plugged into a
motherboard port, hence the repeat of this exercise on the 2nd sata card.
>
> > how do I make an image of that
> > raid10 to /dev/sde and get every byte? That seems like the first step
> > to me.
This I am still trying to do, the first pass copied all 350G of /home
but went to the wrong drive, and I had mounted the drive by its label.
It is now /dev/sdh and all labels above it are now wrong. Crazy.
These SSD's all have an OTP serial number. I am tempted to use that
serial number as a label _I_ can control. And according to gparted,
labels do not survive being incorporated into a raid as the raid is all
labeled with hostname : partition number. So there really is no way in
linux to define a drive that is that drive forever. Unreal...
> Please get a USB 3.x HDD, do a full backup of your entire computer, put
> it off-site, get another USB 3.x HDD, do another full backup, and keep
> it nearby
That, using amanda is the end target of this. But I have bought 3 such
spinning rust drives over the years and not had any survive being hot
plugged into a usb port more than twice.
With that track record, I'll not waste any more money down that rabbit hole.
>
> > But since I can't copy a locked file,
>
>
> What file is lock? Please post a console session that demonstrates.
A file that is opened but not closed is exclusive to that app and its
lock, and cannot be copied except by rsync, or so I have been told. And
there are quite a few such open locks on this system right now. This
killed my full housed amiga when the boot drive with all its custom
scripts died, and I found the backups I had were totally devoid of any
of those scripts. I still have about 20 QIC tapes from that machine, but
now no drives to read them. I need to cull the midden heap.
>
> > /dev/sde1 has been formatted and mounted, what cmd line will copy every
> > byte including locked files in that that raid10 to it?
>
>
> See above for locked. Otherwise, I suggest rsync(1).
>
[...]
Thank you 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 Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2024-01-15 01:50 +0100 |
| Message-ID | <HWjkR-38RW-3@gated-at.bofh.it> |
| In reply to | #265949 |
On Sun 14 Jan 2024 at 14:48:49 (-0500), gene heskett wrote:
> On 1/14/24 07:42, David Christensen wrote:
> > I am confused -- do you have 4 or 5 Gigastone 2 TB SSD?
>
> 5, ordered in 2 separate orders.
> >
> > > So that one could be formatted ext4 and serve as a backup of the raid10.
> What I am trying to do now, but cannot if it is plugged into a
> motherboard port, hence the repeat of this exercise on the 2nd sata
> card.
> >
> > > how do I make an image of that
> > > raid10 to /dev/sde and get every byte? That seems like the first step
> > > to me.
> This I am still trying to do, the first pass copied all 350G of /home
> but went to the wrong drive, and I had mounted the drive by its label.
> It is now /dev/sdh and all labels above it are now wrong. Crazy.
> These SSD's all have an OTP serial number. I am tempted to use that
> serial number as a label _I_ can control. And according to gparted,
> labels do not survive being incorporated into a raid as the raid is
> all labeled with hostname : partition number. So there really is no
> way in linux to define a drive that is that drive forever. Unreal...
Interesting to see in how many differents ways you can use the
term "label". BTW I have no idea what an "OTP serial number" is.
On Sun 14 Jan 2024 at 16:47:41 (-0500), gene heskett wrote:
> ene@coyote:~/src/klipper-docs$ sudo smartctl -a /dev/sde
> [sudo] password for gene:
> smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.0-17-rt-amd64] (local build)
> Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org
>
> === START OF INFORMATION SECTION ===
> Device Model: Gigastone SSD
> Serial Number: GST02TBG221146
↑↑↑↑↑↑↑↑↑↑↑↑↑↑
You see that there? You should find this symlink on your system:
/dev/disk/by-id/… …GST02TBG221146
pointing at some random /dev/sdX. Where you put /dev/sdX,
put /dev/disk/by-id/… …GST02TBG221146 instead. Then you'll
know you're referring to that disk. Likewise the others.
(As already suggested by David C, Sun, 14 Jan 2024 04:41:51 -0800)
Cheers,
David.
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2024-01-15 02:20 +0100 |
| Message-ID | <HWjNT-39gy-5@gated-at.bofh.it> |
| In reply to | #265965 |
On 1/14/24 19:48, David Wright wrote: > On Sun 14 Jan 2024 at 14:48:49 (-0500), gene heskett wrote: >> On 1/14/24 07:42, David Christensen wrote: > >>> I am confused -- do you have 4 or 5 Gigastone 2 TB SSD? >> >> 5, ordered in 2 separate orders. >>> >>> > So that one could be formatted ext4 and serve as a backup of the raid10. >> What I am trying to do now, but cannot if it is plugged into a >> motherboard port, hence the repeat of this exercise on the 2nd sata >> card. >>> >>> > how do I make an image of that >>> > raid10 to /dev/sde and get every byte? That seems like the first step >>> > to me. >> This I am still trying to do, the first pass copied all 350G of /home >> but went to the wrong drive, and I had mounted the drive by its label. >> It is now /dev/sdh and all labels above it are now wrong. Crazy. >> These SSD's all have an OTP serial number. I am tempted to use that >> serial number as a label _I_ can control. And according to gparted, >> labels do not survive being incorporated into a raid as the raid is >> all labeled with hostname : partition number. So there really is no >> way in linux to define a drive that is that drive forever. Unreal... > > Interesting to see in how many differents ways you can use the > term "label". BTW I have no idea what an "OTP serial number" is. > OTP=One Time Pad, never to be used again. > On Sun 14 Jan 2024 at 16:47:41 (-0500), gene heskett wrote: >> ene@coyote:~/src/klipper-docs$ sudo smartctl -a /dev/sde >> [sudo] password for gene: >> smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.0-17-rt-amd64] (local build) >> Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org >> >> === START OF INFORMATION SECTION === >> Device Model: Gigastone SSD >> Serial Number: GST02TBG221146 > > ↑↑↑↑↑↑↑↑↑↑↑↑↑↑ > > You see that there? You should find this symlink on your system: > > /dev/disk/by-id/… …GST02TBG221146 > > pointing at some random /dev/sdX. Where you put /dev/sdX, > put /dev/disk/by-id/… …GST02TBG221146 instead. Then you'll > know you're referring to that disk. Likewise the others. > (As already suggested by David C, Sun, 14 Jan 2024 04:41:51 -0800) > > Cheers, > 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 | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2024-01-15 14:50 +0100 |
| Message-ID | <HWvvH-3ggh-1@gated-at.bofh.it> |
| In reply to | #265972 |
On 1/14/24 20:19, gene heskett wrote: > On 1/14/24 19:48, David Wright wrote: >> On Sun 14 Jan 2024 at 14:48:49 (-0500), gene heskett wrote: >>> On 1/14/24 07:42, David Christensen wrote: >> >>>> I am confused -- do you have 4 or 5 Gigastone 2 TB SSD? >>> >>> 5, ordered in 2 separate orders. >>>> >>>> > So that one could be formatted ext4 and serve as a backup of the >>>> raid10. >>> What I am trying to do now, but cannot if it is plugged into a >>> motherboard port, hence the repeat of this exercise on the 2nd sata >>> card. >>>> >>>> > how do I make an image of that >>>> > raid10 to /dev/sde and get every byte? That seems like the >>>> first step >>>> > to me. >>> This I am still trying to do, the first pass copied all 350G of /home >>> but went to the wrong drive, and I had mounted the drive by its label. >>> It is now /dev/sdh and all labels above it are now wrong. Crazy. >>> These SSD's all have an OTP serial number. I am tempted to use that >>> serial number as a label _I_ can control. And according to gparted, >>> labels do not survive being incorporated into a raid as the raid is >>> all labeled with hostname : partition number. So there really is no >>> way in linux to define a drive that is that drive forever. Unreal... >> >> Interesting to see in how many differents ways you can use the >> term "label". BTW I have no idea what an "OTP serial number" is. >> > OTP=One Time Pad, never to be used again. > >> On Sun 14 Jan 2024 at 16:47:41 (-0500), gene heskett wrote: >>> ene@coyote:~/src/klipper-docs$ sudo smartctl -a /dev/sde >>> [sudo] password for gene: >>> smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.0-17-rt-amd64] (local >>> build) >>> Copyright (C) 2002-22, Bruce Allen, Christian Franke, >>> www.smartmontools.org >>> >>> === START OF INFORMATION SECTION === >>> Device Model: Gigastone SSD >>> Serial Number: GST02TBG221146 >> >> ↑↑↑↑↑↑↑↑↑↑↑↑↑↑ >> >> You see that there? You should find this symlink on your system: >> >> /dev/disk/by-id/… …GST02TBG221146 >> >> pointing at some random /dev/sdX. Where you put /dev/sdX, >> put /dev/disk/by-id/… …GST02TBG221146 instead. Then you'll >> know you're referring to that disk. Likewise the others. >> (As already suggested by David C, Sun, 14 Jan 2024 04:41:51 -0800) >> >> Cheers, >> David. There is a big horse-fly in that soup !!! I moved the data cable to where I knew I could find it again, as one of 5 drives attached to the 16 port card, and on reboot it shows up in an lsblk list as: root@coyote:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 0 931.5G 0 disk ├─sda1 8:1 0 838.2G 0 part / ├─sda2 8:2 0 46.8G 0 part [SWAP] └─sda3 8:3 0 46.6G 0 part /tmp sdb 8:16 1 0B 0 disk sdc 8:32 1 0B 0 disk sdd 8:48 0 931.5G 0 disk ├─sdd1 8:49 0 900G 0 part │ └─md0 9:0 0 1.7T 0 raid10 │ └─md0p1 259:0 0 1.7T 0 part /home ├─sdd2 8:50 0 30G 0 part │ └─md1 9:1 0 60G 0 raid10 [SWAP] └─sdd3 8:51 0 1.5G 0 part └─md2 9:2 0 3G 0 raid10 sde 8:64 0 931.5G 0 disk ├─sde1 8:65 0 900G 0 part │ └─md0 9:0 0 1.7T 0 raid10 │ └─md0p1 259:0 0 1.7T 0 part /home ├─sde2 8:66 0 30G 0 part │ └─md1 9:1 0 60G 0 raid10 [SWAP] └─sde3 8:67 0 1.5G 0 part └─md2 9:2 0 3G 0 raid10 sdf 8:80 0 931.5G 0 disk ├─sdf1 8:81 0 900G 0 part │ └─md0 9:0 0 1.7T 0 raid10 │ └─md0p1 259:0 0 1.7T 0 part /home ├─sdf2 8:82 0 30G 0 part │ └─md1 9:1 0 60G 0 raid10 [SWAP] └─sdf3 8:83 0 1.5G 0 part └─md2 9:2 0 3G 0 raid10 sdg 8:96 0 931.5G 0 disk ├─sdg1 8:97 0 900G 0 part │ └─md0 9:0 0 1.7T 0 raid10 │ └─md0p1 259:0 0 1.7T 0 part /home ├─sdg2 8:98 0 30G 0 part │ └─md1 9:1 0 60G 0 raid10 [SWAP] └─sdg3 8:99 0 1.5G 0 part └─md2 9:2 0 3G 0 raid10 sdh 8:112 0 1.9T 0 disk └─sdh1 8:113 0 1.9T 0 part <<< sdi 8:128 0 1.9T 0 disk └─sdi1 8:129 0 1.9T 0 part <<< sdj 8:144 0 1.9T 0 disk └─sdj1 8:145 0 1.9T 0 part <<< sdk 8:160 0 1.9T 0 disk └─sdk1 8:161 0 1.9T 0 part <<< sdl 8:176 0 1.9T 0 disk └─sdl1 8:177 0 1.9T 0 part <<< sr0 11:0 1 1024M 0 rom root@coyote:~# Now confirmed by looking at all 5 with gparted, there are only 3 unique serial numbers: root@coyote:~# ls /dev/disk/by-id ata-ATAPI_iHAS424_B_3524253_327133504865 ata-Samsung_SSD_870_EVO_1TB_S626NF0R302509W wwn-0x5002538f413394a5-part1 ata-Gigastone_SSD_GST02TBG221146 ata-Samsung_SSD_870_EVO_1TB_S626NF0R302509W-part1 wwn-0x5002538f413394a5-part2 ata-Gigastone_SSD_GST02TBG221146-part1 =========== ata-Samsung_SSD_870_EVO_1TB_S626NF0R302509W-part2 wwn-0x5002538f413394a5-part3 ata-Gigastone_SSD_GSTD02TB230102 ata-Samsung_SSD_870_EVO_1TB_S626NF0R302509W-part3 wwn-0x5002538f413394a9 ata-Gigastone_SSD_GSTD02TB230102-part1 =========== ata-Samsung_SSD_870_QVO_1TB_S5RRNF0T201730V wwn-0x5002538f413394a9-part1 ata-Gigastone_SSD_GSTG02TB230206 ata-Samsung_SSD_870_QVO_1TB_S5RRNF0T201730V-part1 wwn-0x5002538f413394a9-part2 ata-Gigastone_SSD_GSTG02TB230206-part1 =========== ata-Samsung_SSD_870_QVO_1TB_S5RRNF0T201730V-part2 wwn-0x5002538f413394a9-part3 ata-Samsung_SSD_870_EVO_1TB_S626NF0R302498T ata-Samsung_SSD_870_QVO_1TB_S5RRNF0T201730V-part3 wwn-0x5002538f413394ae ata-Samsung_SSD_870_EVO_1TB_S626NF0R302498T-part1 md-name-coyote:0 wwn-0x5002538f413394ae-part1 ata-Samsung_SSD_870_EVO_1TB_S626NF0R302498T-part2 md-name-coyote:0-part1 wwn-0x5002538f413394ae-part2 ata-Samsung_SSD_870_EVO_1TB_S626NF0R302498T-part3 md-name-coyote:2 wwn-0x5002538f413394ae-part3 ata-Samsung_SSD_870_EVO_1TB_S626NF0R302502E md-name-_none_:1 wwn-0x5002538f413394b0 ata-Samsung_SSD_870_EVO_1TB_S626NF0R302502E-part1 md-uuid-3d5a3621:c0e32c8a:e3f7ebb3:318edbfb wwn-0x5002538f413394b0-part1 ata-Samsung_SSD_870_EVO_1TB_S626NF0R302502E-part2 md-uuid-3d5a3621:c0e32c8a:e3f7ebb3:318edbfb-part1 wwn-0x5002538f413394b0-part2 ata-Samsung_SSD_870_EVO_1TB_S626NF0R302502E-part3 md-uuid-57a88605:27f5a773:5be347c1:7c5e7342 wwn-0x5002538f413394b0-part3 ata-Samsung_SSD_870_EVO_1TB_S626NF0R302507V md-uuid-bb6e03ce:19d290c8:5171004f:0127a392 wwn-0x5002538f42205e8e ata-Samsung_SSD_870_EVO_1TB_S626NF0R302507V-part1 usb-Brother_MFC-J6920DW_BROG5F229909-0:0 wwn-0x5002538f42205e8e-part1 ata-Samsung_SSD_870_EVO_1TB_S626NF0R302507V-part2 usb-USB_Mass_Storage_Device_816820130806-0:0 wwn-0x5002538f42205e8e-part2 ata-Samsung_SSD_870_EVO_1TB_S626NF0R302507V-part3 wwn-0x5002538f413394a5 wwn-0x5002538f42205e8e-part3 root@coyote:~# only 3 unique serial numbers!!!!!! udev when finding that situation should scream from the rooftops!! not silently overwrite an entry in the by-id that its already made. HTH do I fix that? can tune2fs edit a serial number? no. can the UUID be rendered read-only, no. gparted and similar can change the UUID by a click of the mouse. I'm officially screwed and I have had them too long to return them now. That could even explain why my first run of rsync worked fine but went to a drive that was NOT mounted. And it was mounted by LABEL= The only one of those 5 SSD's I had labeled at that time. Thanks everybody. 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-15 19:50 +0100 |
| Message-ID | <HWAc1-3jdA-3@gated-at.bofh.it> |
| In reply to | #265987 |
gene heskett composed on 2024-01-15 08:39 (UTC-0500): > └─md2 9:2 0 3G 0 raid10 > sdh 8:112 0 1.9T 0 disk > └─sdh1 8:113 0 1.9T 0 part <<< > sdi 8:128 0 1.9T 0 disk > └─sdi1 8:129 0 1.9T 0 part <<< > sdj 8:144 0 1.9T 0 disk > └─sdj1 8:145 0 1.9T 0 part <<< > sdk 8:160 0 1.9T 0 disk > └─sdk1 8:161 0 1.9T 0 part <<< > sdl 8:176 0 1.9T 0 disk > └─sdl1 8:177 0 1.9T 0 part <<< > sr0 11:0 1 1024M 0 rom Is there a smart card reader in coyote? They can cause what looks like phantom drives. If not, I have no idea what those 5 <<< devices might be assigned to, other than their sizes. :( I suspect it could be some kind of bug, possibly in SATA expansion card firmware. There was a buggy Bookworm kernel recently causing I/O problems. What kernel are you running? 6.1.0-17 is current. Bug was sometime after 6.1.0-13. I have a card reader that produces sd[cdef]: # lsscsi [2:0:0:0] disk ATA ST1000NM0011 SN02 /dev/sda [3:0:0:0] disk ATA ST1000DM003-1CH1 CC49 /dev/sdb [4:0:0:0] cd/dvd ASUS DRW-24B1ST j 1.11 /dev/sr0 [6:0:0:0] disk Generic USB SD Reader 1.00 /dev/sdc [6:0:0:1] disk Generic USB CF Reader 1.01 /dev/sdd [6:0:0:2] disk Generic USB SM Reader 1.02 /dev/sde [6:0:0:3] disk Generic USB MS Reader 1.03 /dev/sdf # So, when I insert a generic USB stick, it gets /dev/sdg. :p -- 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-15 23:00 +0100 |
| Message-ID | <HWD9T-3l1K-5@gated-at.bofh.it> |
| In reply to | #265995 |
On 1/15/24 13:44, Felix Miata wrote: > gene heskett composed on 2024-01-15 08:39 (UTC-0500): > >> └─md2 9:2 0 3G 0 raid10 >> sdh 8:112 0 1.9T 0 disk >> └─sdh1 8:113 0 1.9T 0 part <<< the one I'm fooling with >> sdi 8:128 0 1.9T 0 disk >> └─sdi1 8:129 0 1.9T 0 part <<< >> sdj 8:144 0 1.9T 0 disk >> └─sdj1 8:145 0 1.9T 0 part <<< >> sdk 8:160 0 1.9T 0 disk >> └─sdk1 8:161 0 1.9T 0 part <<< >> sdl 8:176 0 1.9T 0 disk >> └─sdl1 8:177 0 1.9T 0 part <<< >> sr0 11:0 1 1024M 0 rom > > Is there a smart card reader in coyote? They can cause what looks like phantom > drives. If not, I have no idea what those 5 <<< devices might be assigned to, > other than their sizes. :( I suspect it could be some kind of bug, possibly in > SATA expansion card firmware. There was a buggy Bookworm kernel recently causing > I/O problems. What kernel are you running? 6.1.0-17 is current. Bug was sometime > after 6.1.0-13. > > I have a card reader that produces sd[cdef]: > # lsscsi > [2:0:0:0] disk ATA ST1000NM0011 SN02 /dev/sda > [3:0:0:0] disk ATA ST1000DM003-1CH1 CC49 /dev/sdb > [4:0:0:0] cd/dvd ASUS DRW-24B1ST j 1.11 /dev/sr0 > [6:0:0:0] disk Generic USB SD Reader 1.00 /dev/sdc > [6:0:0:1] disk Generic USB CF Reader 1.01 /dev/sdd > [6:0:0:2] disk Generic USB SM Reader 1.02 /dev/sde > [6:0:0:3] disk Generic USB MS Reader 1.03 /dev/sdf > # > So, when I insert a generic USB stick, it gets /dev/sdg. :p I have one, plugged into usb, but nothing is plugged into it ATM, an ONN from wallies. no problems here but it can mess with armbian booting on a bannapi-m5. Got a bunch of those. Nothing that ob this box that looks like the last 4 above. I look at dmesg tp see what it is before I mount it. Thank you Felix. 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]
Page 1 of 9 [1] 2 3 4 5 6 7 8 9 Next page →
Back to top | Article view | linux.debian.user
csiph-web