Date: Tue, 27 Dec 2022 07:05:47 +0100 From: Polytropon <freebsd@edvax.de> To: Robert Huff <roberthuff@rcn.com> Cc: questions@FreeBSD.org Subject: Re: unknown USR mass storage device Message-ID: <20221227070547.a3d38f76.freebsd@edvax.de> In-Reply-To: <25513.50264.824359.772717@jerusalem.litteratus.org> References: <25513.50264.824359.772717@jerusalem.litteratus.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 26 Dec 2022 10:57:12 -0500, Robert Huff wrote: >=20 > Hello: > On a system running: >=20 > FreeBSD 14.0-CURRENT #0 main-f0a15aafcb > Mon Oct 31 08:19:54 EDT 2022 > amd64 >=20 > I plugged a mystery thumb drive into a USB port, and went through > the usual steps of trying to mount it. > Except the drive isn't recognized by gpart. Or camcontrol. > /var/log/messages shows: >=20 > Dec 26 10:48:38 jerusalem kernel: usb_msc_auto_quirk: UQ_MSC_NO_GETMAXLUN= set for USB mass storage device Generic Mass Storage Device (0x14cd:0x1212) > Dec 26 10:48:38 jerusalem kernel: usb_msc_auto_quirk: UQ_MSC_NO_TEST_UNIT= _READY set for USB mass storage device Generic Mass Storage Device (0x14cd:= 0x1212) > Dec 26 10:48:38 jerusalem kernel: usb_msc_auto_quirk: UQ_MSC_NO_PREVENT_A= LLOW set for USB mass storage device Generic Mass Storage Device (0x14cd:0x= 1212) > Dec 26 10:48:38 jerusalem kernel: usb_msc_auto_quirk: UQ_MSC_NO_SYNC_CACH= E set for USB mass storage device Generic Mass Storage Device (0x14cd:0x121= 2) > Dec 26 10:48:38 jerusalem kernel: ugen2.4: <Generic Mass Storage Device> = at usbus2 > Dec 26 10:48:38 jerusalem kernel: umass0 on uhub7 > Dec 26 10:48:38 jerusalem kernel: umass0: <Generic Mass Storage Device, c= lass 0/0, rev 2.00/1.00, addr 4> on usbus2 > Dec 26 10:48:38 jerusalem kernel: umass0: SCSI over Bulk-Only; quirks = =3D 0xc101 > Dec 26 10:48:38 jerusalem kernel: umass0:6:0: Attached to scbus6 > Dec 26 10:48:39 jerusalem kernel: da0 at umass-sim0 bus 0 scbus6 target 0= lun 0 > Dec 26 10:48:39 jerusalem kernel: da0: <Mass Storage Device 1.00> Removab= le Direct Access SCSI device > Dec 26 10:48:39 jerusalem kernel: da0: Serial Number 121220160204 > Dec 26 10:48:39 jerusalem kernel: da0: 40.000MB/s transfers > Dec 26 10:48:39 jerusalem kernel: da0: Attempt to query device size faile= d: NOT READY, Medium not present > Dec 26 10:48:39 jerusalem kernel: da0: quirks=3D0x2<NO_6_BYTE> > Dec 26 10:48:39 jerusalem kernel: da0: Write Protected >=20 > <insert slack-jawed expression> > Anyone know what I'm looking at here? What capabilities does usbconfig list f=FCr this particular device? Without knowing what it is, I'm just guessing: It could be a device that contains drivers for "Windows", presented on an imaginary file system (USB mass storage, write protected). Some older UMTS sticks did this, but they presented themselves both as USB CD drive and as USB communications device. Maybe you're looking at something comparable? If you cannot use gpart, can you inspect the raw file (/dev/da0, maybe /dev/da0s1), "file -s /dev/da0" or using a hex viewer, if you can access data on the device at all, without mounting? Also check the USB vendor and device ID, maybe you can find out what it is? If you're sure it is a regular USB stick / thumb drive, try "newfs /dev/da0". Before you do, replace the write ring. ;-) --=20 Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20221227070547.a3d38f76.freebsd>