Date: Mon, 19 Apr 2021 17:10:56 +0200 From: Robert Clausecker <fuz@fuz.su> To: freebsd-arm@freebsd.org Subject: Re: RPi 4B USB 3 support appears to still be broken in 13.0-RELEASE Message-ID: <YH2dgI4Rttjr%2B0wv@fuz.su> In-Reply-To: <10b8cbd7-e426-4096-86ed-7f4629b37db2@stha.de> References: <YHoXAS%2B0/ptwL0IS@fuz.su> <CAOWUMWGvYBZmMo1OVfsHQ6OohBOpQy5_n%2B0T5BeKWvqowBQQiA@mail.gmail.com> <YHqqgmFRxNS7azeK@fuz.su> <6D2C75DF-796D-4CC9-9740-A8C15C6A6154@yahoo.com> <YHrWXkVhiPJFihdv@fuz.su> <C7C2B00E-772E-4EBE-AA0A-1EAB04F4F6A6@yahoo.com> <YHxvd16NypbTW0h2@fuz.su> <10b8cbd7-e426-4096-86ed-7f4629b37db2@stha.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Stefan, I've since managed to diagnose the issue and closed the PR. The problem is that the disk is a 4k disk but for some weird reason, FreeBSD thinks 512b sector accesses are ok. As you can see, all failing requests are in fact requests with odd numbers of sectors (in your case, 7 sectors of 512 byte). I managed to fix this problem for me by forcing ZFS into 4k sector mode (ashift=12). For GELI, there's the -s option to force a different sector size. Now the weird thing is why this problem doesn't occur on USB 2. Quite honestly, I have no idea. Yours, Robert Clausecker Am Mon, Apr 19, 2021 at 03:59:39PM +0200 schrieb Stefan Haller: > Hi, > > I just wanted to add one more data point I observed myself. > > On Sun, Apr 18, 2021 at 07:42:15PM +0200, Robert Clausecker wrote: > > This is getting super strange. The > > problem seems to occur only in this specific combination: > > > > * the specific drive I have > > * attached to a USB 3 port > > * on the Raspberry Pi 4 > > * trying to import a zpool from the drive > > I had a similar error on my RPi 4B as described in the initial post when > using ZFS _on GELI_ on an USB3 attached SATA-SSD. After switching to > plain ZFS on USB3 on the same device it magically started working. ZFS > on GELI was only working on the USB2 ports. Maybe the errors are > related? > > My dmesg dump from the time when it was not working: > > > ugen0.3: <ASMedia ASM1153E SATA 6Gbs Bridge> at usbus0 > > umass0 on uhub0 > > umass0: <ASMedia ASM1153E SATA 6Gbs Bridge, class 0/0, rev 3.00/1.00, addr 2> on usbus0 > > da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 > > da0: <SanDisk SSD PLUS 480GB 0> Fixed Direct Access SPC-4 SCSI device > > da0: Serial Number xxxxxxxxxxxx > > da0: 400.000MB/s transfers > > da0: 457862MB (937703088 512 byte sectors) > > da0: quirks=0x2<NO_6_BYTE> > > GEOM_ELI: Device da0.eli created. > > GEOM_ELI: Encryption: AES-CBC 128 > > GEOM_ELI: Crypto: software > > (da0:umass-sim0:0:0:0): READ(10). CDB: 28 00 13 2a 29 a6 00 00 07 00 > > (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error > > (da0:umass-sim0:0:0:0): Retrying command, 3 more tries remain > > (da0:umass-sim0:0:0:0): READ(10). CDB: 28 00 13 2a 29 a6 00 00 07 00 > > (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error > > (da0:umass-sim0:0:0:0): Retrying command, 2 more tries remain > > (da0:umass-sim0:0:0:0): READ(10). CDB: 28 00 08 80 20 36 00 00 07 00 > > (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error > > As I said, I switched to plain ZFS on the USB3 attached disk and > everything works. (I am using ZFS encryption available since FreeBSD 13 > without issues.) > > > Kind regards, > Stefan > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" -- () ascii ribbon campaign - for an 8-bit clean world /\ - against html email - against proprietary attachments
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YH2dgI4Rttjr%2B0wv>