From nobody Sun Dec 19 19:28:54 2021 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 9E92118FC54A for ; Sun, 19 Dec 2021 19:28:50 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "www.zefox.com", Issuer "www.zefox.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4JHCSf2pDnz4ZXh for ; Sun, 19 Dec 2021 19:28:50 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.16.1/8.15.2) with ESMTPS id 1BJJStVg015322 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sun, 19 Dec 2021 11:28:55 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.16.1/8.15.2/Submit) id 1BJJSs47015321; Sun, 19 Dec 2021 11:28:54 -0800 (PST) (envelope-from fbsd) Date: Sun, 19 Dec 2021 11:28:54 -0800 From: bob prohaska To: Mark Millard Cc: Free BSD Subject: Re: Dealing with slow USB disks, was: Re: Saving environment variables in u-boot Message-ID: <20211219192854.GB14873@www.zefox.net> References: <20211217013613.GA4452@www.zefox.net> <20211218005946.GA7670@www.zefox.net> <5C44D0E6-2FF1-4EEB-B21A-83333D6FCF46@yahoo.com> <9D416106-660F-40BB-98D2-1354B53D2FEF@yahoo.com> <20211218223543.GA9484@www.zefox.net> <772E3794-B762-429F-B2A5-F504EA293C59@yahoo.com> <20211219043422.GA12811@www.zefox.net> <288258B0-40B0-44EC-B449-7A8FB81575F8@yahoo.com> List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <288258B0-40B0-44EC-B449-7A8FB81575F8@yahoo.com> X-Rspamd-Queue-Id: 4JHCSf2pDnz4ZXh X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N On Sun, Dec 19, 2021 at 12:55:12AM -0800, Mark Millard wrote: > > http://www.zefox.net/~fbsd/slow_usb_notes shows: > > umass0 on uhub1 > umass0: on usbus1 > umass0: SCSI over Bulk-Only; quirks = 0x8100 > umass0:0:0: Attached to scbus0 > . . . > a0 at umass-sim0 bus 0 scbus0 target 0 lun 0 > da0: Fixed Direct Access SPC-4 SCSI device > da0: Serial Number 000000000000A > da0: 40.000MB/s transfers > da0: 953869MB (1953525168 512 byte sectors) > da0: quirks=0x2 > > https://jamesachambers.com/fixing-storage-adapters-for-raspberry-pi-via-firmware-updates/ > > has material about SABRENT adapters: > > QUOTE > Sabrent and Orico both have the worst track records for working storage adapters for the Pi. I don???t recommend them at all but they can sometimes be fixed. > END QUOTE > > (Not that all models are bad.) > > I've not found anything to identify the specific product > that you are using. He lists some specific ones as > problematical but possibly fixable: > > ??? EC-SSHD* > ??? EC-UASP* > ??? EC-UK30* > ??? EC-UM3W* > ??? EC-DFLT* > ??? EC-NVME* > ??? EC-TFNE* > ??? EC-TFNB* > > (The above are JMicro based.) Can you identify your adapter > type? > The enclosure is simply marked SABRENT EC_UASP, The usb-sata bridge is marked JMS576 2026 QH8A3A A E76H20013 The "product brief" is at https://www.jmicron.com/file/download/1015/JMS576_Product+Brief.pdf but it's more advertising than technical. It claims Windows and Mac support, the omission of linux/bsd isn't surprising. I've tried power-cycling the disk, it doesn't seem to have any effect on discovery using usb reset. There is one slightly odd thing: Once the disk is found, it does not stay found. Left sitting at the u-boot prompt after discovery a subsequent usb reset frequently fails to find the disk and it's durably lost. A total system reset seems required to find it. One other observation... I tried smartctl on both Pi3 and P4. On the Pi3 it failed: root@pelorus:/usr/ports/sysutils/smartmontools # smartctl -a /dev/da0 smartctl 7.2 2021-09-14 r5236 [FreeBSD 13.0-STABLE arm64] (local build) Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org Read NVMe Identify Controller failed: scsi error unsupported field in scsi command On the Pi4 it worked: root@nemesis:/usr/local/poudriere # smartctl -a /dev/da0 smartctl 7.2 2021-09-14 r5236 [FreeBSD 14.0-CURRENT arm64] (local build) Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Seagate Barracuda 2.5 5400 Device Model: ST1000LM048-2E7172 Serial Number: ZDEM543B ....[voluminous output snipped] Might the difference in behavior be significant? Thanks for reading! bob prohaska