On Fri, Apr 4, 2025, 11:47 PM Steve Kargl <kar...@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 > >
