Date: Sun, 20 Dec 2020 00:30:42 +0100 From: Hans Petter Selasky <hps@selasky.org> To: mike tancsa <mike@sentex.net>, Mateusz Guzik <mjguzik@gmail.com> Cc: George Neville-Neil <gnn@neville-neil.com>, "netperf-admin@FreeBSD.org" <netperf-admin@freebsd.org>, netperf-users@freebsd.org, Paul Holes <pholes@sentex.ca> Subject: Re: zoo back online (was Re: zoo hang) Message-ID: <51c4dfed-a42a-a820-816c-f89691e853e7@selasky.org> In-Reply-To: <7c508e03-7575-b06a-3b14-f8b6e1ed10db@sentex.net> References: <5483e76e-4a2f-3153-c10b-7902839c1b68@sentex.net> <CAGudoHF-3XhWQq-x8vROdUJ0sTweha2YEK_LXVwv44E4k=TtmQ@mail.gmail.com> <a55a69da-c9c6-eb18-9975-3572457ae5ef@sentex.net> <8c26a0d3-3bd0-7535-0abc-3d1e9e5ac7c4@sentex.net> <64923d33-4bf2-0fd5-1b17-d6bd73e9fd32@sentex.net> <13a9ab42-1df8-c054-0c83-5708ab9d9e2b@sentex.net> <C94AED22-A984-49ED-8D18-FD4856D70E01@neville-neil.com> <6cef40cd-de57-aa84-bc70-ceea71add397@sentex.net> <F0FA8C48-1DB1-4D63-ACD4-3ADD78AFA568@neville-neil.com> <837ce2bc-9731-85b0-c6a5-1b3c7bcadb72@sentex.net> <CAGudoHFDLu_MDT1H7xgcX5cXAEi8g_a1Kq8DumO6fJKQq6zBbg@mail.gmail.com> <7c508e03-7575-b06a-3b14-f8b6e1ed10db@sentex.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/19/20 10:57 PM, mike tancsa wrote: > I was able to do a zpool clear zoobackup; zpool export zoobackup even > though it threw a few more errors > > (da2:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 b4 00 20 28 00 00 18 00 > (da2:umass-sim0:0:0:0): CAM status: CCB request completed with an error > (da2:umass-sim0:0:0:0): Retrying command, 2 more tries remain > (da2:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 b4 00 20 28 00 00 18 00 > (da2:umass-sim0:0:0:0): CAM status: CCB request completed with an error > (da2:umass-sim0:0:0:0): Retrying command, 1 more tries remain > Solaris: WARNING: Pool 'zoobackup' has encountered an uncorrectable I/O > failure and has been suspended. > > (da2:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 02 38 00 00 10 00 > (da2:umass-sim0:0:0:0): CAM status: SCSI Status Error > (da2:umass-sim0:0:0:0): SCSI status: Check Condition > (da2:umass-sim0:0:0:0): SCSI sense: NOT READY asc:4,1 (Logical unit is > in process of becoming ready) > > (da2:umass-sim0:0:0:0): Polling device for readiness > > I wonder if Monday we should try upgrading the BIOS first > > > BIOS Information > Vendor: American Megatrends Inc. > Version: 1.0b > Release Date: 01/29/2015 > Address: 0xF0000 > Runtime Size: 64 kB > ROM Size: 16 MB > Characteristics: > > System Information > Manufacturer: Supermicro > Product Name: SYS-7048R-C1RT4+ > Version: 0123456789 > Serial Number: S16909225402569 > UUID: 00000000-0000-0000-0000-0cc47a1f2fa0 > Wake-up Type: Power Switch > SKU Number: To be filled by O.E.M. > Family: To be filled by O.E.M. > > Handle 0x0002, DMI type 2, 15 bytes > Base Board Information > Manufacturer: Supermicro > Product Name: X10DRC-T4+ > Version: 1.01 > > > https://www.supermicro.com/Bios/softfiles/10079/P-X10DRC(-I-LN4-T4_)_BIOS_3_2_release_notes.pdf > > is from 2019 > > On 12/19/2020 3:16 PM, Mateusz Guzik wrote: >> I'm adding hps for USB stack comments. >> >> On 12/19/20, mike tancsa <mike@sentex.net> wrote: >>> Hmm, This has happened again. Not sure if its a bug with the driver, the >>> firmware or both, but after a period of time the usb drive starts to >>> throw errors. This unit was working fine on RELENG12 and we swapped it >>> with another drive too, but same results. The drive is clean >>> >>> smartctl -a /dev/da2 -T permissive >>> You might want to do a usbdump of the traffic for a short while to figure out exactly what kind of USB error this is. --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?51c4dfed-a42a-a820-816c-f89691e853e7>