Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #266094
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: smartctl cannot access my storage, need syntax help |
| Date | 2024-01-17 02:10 +0100 |
| Message-ID | <HX2Bj-3ASX-1@gated-at.bofh.it> (permalink) |
| References | (4 earlier) <HWjNT-39gy-5@gated-at.bofh.it> <HWvvH-3ggh-1@gated-at.bofh.it> <HWBhL-3jQw-15@gated-at.bofh.it> <HWE5X-3lCQ-1@gated-at.bofh.it> <HWKEq-3pFQ-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 1/16/24 00:56, Felix Miata wrote: > gene heskett composed on 2024-01-15 17:56 (UTC-0500): > >> Thanks for that composition: but it will be word wrapped: >> root@coyote:~# for j in /dev/disk/by-id/* ; do printf '%s\t%s\n' >> "$(realpath "$j")" "$j" ; done >> /dev/sr0 /dev/disk/by-id/ata-ATAPI_iHAS424_B_3524253_327133504865 >> /dev/sdi /dev/disk/by-id/ata-Gigastone_SSD_GST02TBG221146 >> /dev/sdj1 /dev/disk/by-id/ata-Gigastone_SSD_GST02TBG221146-part1 >> /dev/sdh /dev/disk/by-id/ata-Gigastone_SSD_GSTD02TB230102 >> /dev/sdh1 /dev/disk/by-id/ata-Gigastone_SSD_GSTD02TB230102-part1 >> /dev/sdk /dev/disk/by-id/ata-Gigastone_SSD_GSTG02TB230206 >> /dev/sdk1 /dev/disk/by-id/ata-Gigastone_SSD_GSTG02TB230206-part1 >> /dev/sdf /dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302498T >> /dev/sdf1 >> /dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302498T-part1 >> /dev/sdf2 >> /dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302498T-part2 >> /dev/sdf3 >> /dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302498T-part3 >> /dev/sde /dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302502E >> /dev/sde1 >> /dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302502E-part1 >> /dev/sde2 >> /dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302502E-part2 >> /dev/sde3 >> /dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302502E-part3 >> /dev/sdd /dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302507V >> /dev/sdd1 >> /dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302507V-part1 >> /dev/sdd2 >> /dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302507V-part2 >> /dev/sdd3 >> /dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302507V-part3 >> /dev/sdg /dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302509W >> /dev/sdg1 >> /dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302509W-part1 >> /dev/sdg2 >> /dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302509W-part2 >> /dev/sdg3 >> /dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302509W-part3 >> /dev/sda /dev/disk/by-id/ata-Samsung_SSD_870_QVO_1TB_S5RRNF0T201730V >> /dev/sda1 >> /dev/disk/by-id/ata-Samsung_SSD_870_QVO_1TB_S5RRNF0T201730V-part1 >> /dev/sda2 >> /dev/disk/by-id/ata-Samsung_SSD_870_QVO_1TB_S5RRNF0T201730V-part2 >> /dev/sda3 >> /dev/disk/by-id/ata-Samsung_SSD_870_QVO_1TB_S5RRNF0T201730V-part3 >> /dev/md0 /dev/disk/by-id/md-name-coyote:0 >> /dev/md0p1 /dev/disk/by-id/md-name-coyote:0-part1 >> /dev/md2 /dev/disk/by-id/md-name-coyote:2 >> /dev/md1 /dev/disk/by-id/md-name-_none_:1 >> /dev/md0 /dev/disk/by-id/md-uuid-3d5a3621:c0e32c8a:e3f7ebb3:318edbfb >> /dev/md0p1 >> /dev/disk/by-id/md-uuid-3d5a3621:c0e32c8a:e3f7ebb3:318edbfb-part1 >> /dev/md1 /dev/disk/by-id/md-uuid-57a88605:27f5a773:5be347c1:7c5e7342 >> /dev/md2 /dev/disk/by-id/md-uuid-bb6e03ce:19d290c8:5171004f:0127a392 >> /dev/sdc /dev/disk/by-id/usb-Brother_MFC-J6920DW_BROG5F229909-0:0 >> /dev/sdb /dev/disk/by-id/usb-USB_Mass_Storage_Device_816820130806-0:0 >> /dev/sdf /dev/disk/by-id/wwn-0x5002538f413394a5 >> /dev/sdf1 /dev/disk/by-id/wwn-0x5002538f413394a5-part1 >> /dev/sdf2 /dev/disk/by-id/wwn-0x5002538f413394a5-part2 >> /dev/sdf3 /dev/disk/by-id/wwn-0x5002538f413394a5-part3 >> /dev/sde /dev/disk/by-id/wwn-0x5002538f413394a9 >> /dev/sde1 /dev/disk/by-id/wwn-0x5002538f413394a9-part1 >> /dev/sde2 /dev/disk/by-id/wwn-0x5002538f413394a9-part2 >> /dev/sde3 /dev/disk/by-id/wwn-0x5002538f413394a9-part3 >> /dev/sdd /dev/disk/by-id/wwn-0x5002538f413394ae >> /dev/sdd1 /dev/disk/by-id/wwn-0x5002538f413394ae-part1 >> /dev/sdd2 /dev/disk/by-id/wwn-0x5002538f413394ae-part2 >> /dev/sdd3 /dev/disk/by-id/wwn-0x5002538f413394ae-part3 >> /dev/sdg /dev/disk/by-id/wwn-0x5002538f413394b0 >> /dev/sdg1 /dev/disk/by-id/wwn-0x5002538f413394b0-part1 >> /dev/sdg2 /dev/disk/by-id/wwn-0x5002538f413394b0-part2 >> /dev/sdg3 /dev/disk/by-id/wwn-0x5002538f413394b0-part3 >> /dev/sda /dev/disk/by-id/wwn-0x5002538f42205e8e >> /dev/sda1 /dev/disk/by-id/wwn-0x5002538f42205e8e-part1 >> /dev/sda2 /dev/disk/by-id/wwn-0x5002538f42205e8e-part2 >> /dev/sda3 /dev/disk/by-id/wwn-0x5002538f42205e8e-part3 >> root@coyote:~# >> but like I wrote, 2 pairs with identical "serial numbers", so the >> assunption is that the last one overwrites the first on by udev, when >> IMO it should be yelling about the duplicats. > > I straightened out the wrapping mess, and gave each entry a line number. I see > nothing I recognize as representing serial number duplication among /dev/sdX > (physical device) names: > > /dev/md0 1 /dev/disk/by-id/md-name-coyote:0 > /dev/md0 2 /dev/disk/by-id/md-uuid-3d5a3621:c0e32c8a:e3f7ebb3:318edbfb > /dev/md0p1 3 /dev/disk/by-id/md-name-coyote:0-part1 > /dev/md0p1 4 /dev/disk/by-id/md-uuid-3d5a3621:c0e32c8a:e3f7ebb3:318edbfb-part1 > /dev/md1 5 /dev/disk/by-id/md-name-_none_:1 > /dev/md1 6 /dev/disk/by-id/md-uuid-57a88605:27f5a773:5be347c1:7c5e7342 > /dev/md2 7 /dev/disk/by-id/md-name-coyote:2 > /dev/md2 8 /dev/disk/by-id/md-uuid-bb6e03ce:19d290c8:5171004f:0127a392 > /dev/sda 9 /dev/disk/by-id/ata-Samsung_SSD_870_QVO_1TB_S5RRNF0T201730V > /dev/sda 10 /dev/disk/by-id/wwn-0x5002538f42205e8e > /dev/sda1 11 /dev/disk/by-id/ata-Samsung_SSD_870_QVO_1TB_S5RRNF0T201730V-part1 > /dev/sda1 12 /dev/disk/by-id/wwn-0x5002538f42205e8e-part1 > /dev/sda2 13 /dev/disk/by-id/ata-Samsung_SSD_870_QVO_1TB_S5RRNF0T201730V-part2 > /dev/sda2 14 /dev/disk/by-id/wwn-0x5002538f42205e8e-part2 > /dev/sda3 15 /dev/disk/by-id/ata-Samsung_SSD_870_QVO_1TB_S5RRNF0T201730V-part3 > /dev/sda3 16 /dev/disk/by-id/wwn-0x5002538f42205e8e-part3 > /dev/sdb 17 /dev/disk/by-id/usb-USB_Mass_Storage_Device_816820130806-0:0 > /dev/sdc 18 /dev/disk/by-id/usb-Brother_MFC-J6920DW_BROG5F229909-0:0 # How does a printer get a storage device assignment??? > /dev/sdd 19 /dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302507V > /dev/sdd 20 /dev/disk/by-id/wwn-0x5002538f413394ae > /dev/sdd1 21 /dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302507V-part1 > /dev/sdd1 22 /dev/disk/by-id/wwn-0x5002538f413394ae-part1 > /dev/sdd2 23 /dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302507V-part2 > /dev/sdd2 24 /dev/disk/by-id/wwn-0x5002538f413394ae-part2 > /dev/sdd3 25 /dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302507V-part3 > /dev/sdd3 26 /dev/disk/by-id/wwn-0x5002538f413394ae-part3 > /dev/sde 27 /dev/disk/by-id/wwn-0x5002538f413394a9 > /dev/sde 28 /dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302502E > /dev/sde1 29 /dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302502E-part1 > /dev/sde1 30 /dev/disk/by-id/wwn-0x5002538f413394a9-part1 > /dev/sde2 31 /dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302502E-part2 > /dev/sde2 32 /dev/disk/by-id/wwn-0x5002538f413394a9-part2 > /dev/sde3 33 /dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302502E-part3 > /dev/sde3 34 /dev/disk/by-id/wwn-0x5002538f413394a9-part3 > /dev/sdf 35 /dev/disk/by-id/wwn-0x5002538f413394a5 > /dev/sdf 36 /dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302498T > /dev/sdf1 37 /dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302498T-part1 > /dev/sdf1 38 /dev/disk/by-id/wwn-0x5002538f413394a5-part1 > /dev/sdf2 39 /dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302498T-part2 > /dev/sdf2 40 /dev/disk/by-id/wwn-0x5002538f413394a5-part2 > /dev/sdf3 41 /dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302498T-part3 > /dev/sdf3 42 /dev/disk/by-id/wwn-0x5002538f413394a5-part3 > /dev/sdg 43 /dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302509W > /dev/sdg 44 /dev/disk/by-id/wwn-0x5002538f413394b0 > /dev/sdg1 45 /dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302509W-part1 > /dev/sdg1 46 /dev/disk/by-id/wwn-0x5002538f413394b0-part1 > /dev/sdg2 47 /dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302509W-part2 > /dev/sdg2 48 /dev/disk/by-id/wwn-0x5002538f413394b0-part2 > /dev/sdg3 49 /dev/disk/by-id/ata-Samsung_SSD_870_EVO_1TB_S626NF0R302509W-part3 > /dev/sdg3 50 /dev/disk/by-id/wwn-0x5002538f413394b0-part3 > /dev/sdh 51 /dev/disk/by-id/ata-Gigastone_SSD_GSTD02TB230102 > /dev/sdh1 52 /dev/disk/by-id/ata-Gigastone_SSD_GSTD02TB230102-part1 > /dev/sdi 53 /dev/disk/by-id/ata-Gigastone_SSD_GST02TBG221146 > /dev/sdj1 54 /dev/disk/by-id/ata-Gigastone_SSD_GST02TBG221146-part1 > /dev/sdk 55 /dev/disk/by-id/ata-Gigastone_SSD_GSTG02TB230206 > /dev/sdk1 56 /dev/disk/by-id/ata-Gigastone_SSD_GSTG02TB230206-part1 > /dev/sr0 57 /dev/disk/by-id/ata-ATAPI_iHAS424_B_3524253_327133504865 > > Exactly which line numbers represent duplication among the physical drives? lsblk, which I've published several times, shows 5 drives. by-id listing only shows 3. The drive I've been trying to use bounces from /dev/sdd to sde to sdh dependin on which controller it is curently plugged into. And I've since tried cp in addition to rsync, does the same thing, killing the sysytem with the OOM but much quicker. cp using all system memory (32Gb) in 1 minute, another 500K into swap adds another 15 secs, and the OOM kills the system. So both cp and rsync act broken. rsync, with a --bwlimit=3m set, takes much longer to kill the system but the amount of data moved is very similar, 13.5G from clean disk to system freeze for rsync, 13.4G for cp. 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
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
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
csiph-web