Date: Sat, 5 Apr 2025 01:11:13 -0600 From: Warner Losh <imp@bsdimp.com> To: Steve Kargl <kargls@comcast.net> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Samsung T7 external SSD support? Message-ID: <CANCZdfpvDW-b2kPoXnzqYBU-iwgcpWAUJ7V3ZWQRruqaKXhd-Q@mail.gmail.com> In-Reply-To: <b223ff24-c9ff-4c87-8881-1b47b63bc076@comcast.net> References: <39bd6092-4bd9-4086-b202-08b83b425fb5@comcast.net> <35d2361d-80e8-489a-bd9d-6c5ada5736b8@FreeBSD.org> <591a0d84-a74a-4d8e-bd40-04475eb5b457@comcast.net> <b223ff24-c9ff-4c87-8881-1b47b63bc076@comcast.net>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Fri, Apr 4, 2025, 11:47 PM Steve Kargl <kargls@comcast.net> wrote: > On 4/4/25 19:44, Steve Kargl wrote: > > On 4/4/25 19:28, Alexander Motin wrote: > >> On 04.04.2025 21:45, Steve Kargl wrote: > >>> Anyone using a Samsung T7 external SSD with FreeBSD current? > >>> > >>> If I plug the drive into a USB 2.0 port, I see > >>> > >>> usb_msc_auto_quirk: UQ_MSC_NO_GETMAXLUN set for USB mass storage > >>> device Samsung PSSD T7 Shield (0x04e8:0x61fb) > >>> ugen0.2: <Samsung PSSD T7 Shield> at usbus0 > >>> umass0 on uhub1 > >>> umass0: <Samsung PSSD T7 Shield, class 0/0, rev 2.10/1.00, addr 47> > >>> on usbus0 > >>> umass0: SCSI over Bulk-Only; quirks = 0x0100 > >>> umass0:5:0: Attached to scbus5 > >>> da0 at umass-sim0 bus 0 scbus5 target 0 lun 0 > >>> da0: <Samsung PSSD T7 Shield 0> Fixed Direct Access SPC-4 SCSI device > >>> da0: Serial Number S6NPNS0Y201077Y > >>> da0: 40.000MB/s transfers > >>> da0: 1907729MB (3907029168 512 byte sectors) > >>> da0: quirks=0x2<NO_6_BYTE> > >>> > >>> However, the SSD is supposedly a USB 3.2 gen 2 device with a ~1000 MBps > >>> read/write speed. > >>> > >>> When plugged into a USB 3.x port, I typically see > >>> > >>> ugen0.2: <vendor 0x0507 product 0x0204> at usbus0 > >>> > >>> and the device is not listed with usbconfig. Repeatedly, unplugging > the > >>> ssd and re-plugging it into the USB 3.x port, I eventually get the > >>> above dmesg output. Do I need a quirk for this SSD to get > >>> recognized? Also, > >>> shouldn't it connect with faster transfer rate than 'da0: 40.0MB/s'? > >> > >> 40MB/s exactly means the device connected to USB2 controller or at > >> least at USB2 speed. Considering that other times it does not connect > >> at all, I wonder if some signal quality issue or something else > >> prevents it from going proper USB3. IIRC USB3 uses completely > >> different wires in the connector. Also USB2 and USB3 can be handled > >> by different controllers with different drivers, so not detecting it > >> still might be a software issue, but I can't say much about that area. > > > > Thanks for confirming my suspension. > > > > I've tried two different cables. I have few more I can test. > > Unfortunately, I have to use a short USB 3.x extension cable > > as the port is on the motherboard under a table. > > > > Climbing under the table and plugging directly into the motherboard > gives > usb_msc_auto_quirk: UQ_MSC_NO_GETMAXLUN set for USB mass storage device > Samsung PSSD T7 Shield (0x04e8:0x61fb) > ugen2.2: <Samsung PSSD T7 Shield> at usbus2 > umass0 on uhub0 > umass0: <Samsung PSSD T7 Shield, class 0/0, rev 3.20/1.00, addr 1> on > usbus2 > umass0: SCSI over Bulk-Only; quirks = 0x0100 > umass0:5:0: Attached to scbus5 > da0 at umass-sim0 bus 0 scbus5 target 0 lun 0 > da0: <Samsung PSSD T7 Shield 0> Fixed Direct Access SPC-4 SCSI device > da0: Serial Number S6NPNS0Y201077Y > da0: 400.000MB/s transfers > da0: 1907729MB (3907029168 512 byte sectors) > da0: quirks=0x2<NO_6_BYTE> > > which is what I expected. So, the extension cable seems to be > an issue. > What is the dd performance? Warner > > -- > steve > > [-- Attachment #2 --] <div dir="auto"><div><br><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Fri, Apr 4, 2025, 11:47 PM Steve Kargl <<a href="mailto:kargls@comcast.net">kargls@comcast.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 4/4/25 19:44, Steve Kargl wrote:<br> > On 4/4/25 19:28, Alexander Motin wrote:<br> >> On 04.04.2025 21:45, Steve Kargl wrote:<br> >>> Anyone using a Samsung T7 external SSD with FreeBSD current?<br> >>><br> >>> If I plug the drive into a USB 2.0 port, I see<br> >>><br> >>> usb_msc_auto_quirk: UQ_MSC_NO_GETMAXLUN set for USB mass storage <br> >>> device Samsung PSSD T7 Shield (0x04e8:0x61fb)<br> >>> ugen0.2: <Samsung PSSD T7 Shield> at usbus0<br> >>> umass0 on uhub1<br> >>> umass0: <Samsung PSSD T7 Shield, class 0/0, rev 2.10/1.00, addr 47> <br> >>> on usbus0<br> >>> umass0: SCSI over Bulk-Only; quirks = 0x0100<br> >>> umass0:5:0: Attached to scbus5<br> >>> da0 at umass-sim0 bus 0 scbus5 target 0 lun 0<br> >>> da0: <Samsung PSSD T7 Shield 0> Fixed Direct Access SPC-4 SCSI device<br> >>> da0: Serial Number S6NPNS0Y201077Y<br> >>> da0: 40.000MB/s transfers<br> >>> da0: 1907729MB (3907029168 512 byte sectors)<br> >>> da0: quirks=0x2<NO_6_BYTE><br> >>><br> >>> However, the SSD is supposedly a USB 3.2 gen 2 device with a ~1000 MBps<br> >>> read/write speed.<br> >>><br> >>> When plugged into a USB 3.x port, I typically see<br> >>><br> >>> ugen0.2: <vendor 0x0507 product 0x0204> at usbus0<br> >>><br> >>> and the device is not listed with usbconfig. Repeatedly, unplugging the<br> >>> ssd and re-plugging it into the USB 3.x port, I eventually get the <br> >>> above dmesg output. Do I need a quirk for this SSD to get <br> >>> recognized? Also,<br> >>> shouldn't it connect with faster transfer rate than 'da0: 40.0MB/s'?<br> >><br> >> 40MB/s exactly means the device connected to USB2 controller or at <br> >> least at USB2 speed. Considering that other times it does not connect <br> >> at all, I wonder if some signal quality issue or something else <br> >> prevents it from going proper USB3. IIRC USB3 uses completely <br> >> different wires in the connector. Also USB2 and USB3 can be handled <br> >> by different controllers with different drivers, so not detecting it <br> >> still might be a software issue, but I can't say much about that area.<br> > <br> > Thanks for confirming my suspension.<br> > <br> > I've tried two different cables. I have few more I can test.<br> > Unfortunately, I have to use a short USB 3.x extension cable<br> > as the port is on the motherboard under a table.<br> > <br> <br> Climbing under the table and plugging directly into the motherboard<br> gives<br> usb_msc_auto_quirk: UQ_MSC_NO_GETMAXLUN set for USB mass storage device <br> Samsung PSSD T7 Shield (0x04e8:0x61fb)<br> ugen2.2: <Samsung PSSD T7 Shield> at usbus2<br> umass0 on uhub0<br> umass0: <Samsung PSSD T7 Shield, class 0/0, rev 3.20/1.00, addr 1> on usbus2<br> umass0: SCSI over Bulk-Only; quirks = 0x0100<br> umass0:5:0: Attached to scbus5<br> da0 at umass-sim0 bus 0 scbus5 target 0 lun 0<br> da0: <Samsung PSSD T7 Shield 0> Fixed Direct Access SPC-4 SCSI device<br> da0: Serial Number S6NPNS0Y201077Y<br> da0: 400.000MB/s transfers<br> da0: 1907729MB (3907029168 512 byte sectors)<br> da0: quirks=0x2<NO_6_BYTE><br> <br> which is what I expected. So, the extension cable seems to be<br> an issue.<br></blockquote></div></div><div dir="auto"><br></div><div dir="auto">What is the dd performance?</div><div dir="auto"><br></div><div dir="auto">Warner </div><div dir="auto"><div class="gmail_quote gmail_quote_container"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <br> -- <br> steve<br> <br> </blockquote></div></div></div>home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfpvDW-b2kPoXnzqYBU-iwgcpWAUJ7V3ZWQRruqaKXhd-Q>