From owner-freebsd-questions@freebsd.org Sat Nov 21 21:13:44 2020 Return-Path: Delivered-To: freebsd-questions@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 86789470DCF for ; Sat, 21 Nov 2020 21:13:44 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.131]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CdmP33dpmz3Q87 for ; Sat, 21 Nov 2020 21:13:43 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([94.222.30.201]) by mrelayeu.kundenserver.de (mreue009 [212.227.15.167]) with ESMTPA (Nemesis) id 1MNss4-1krfza1b3I-00OKk6; Sat, 21 Nov 2020 22:13:34 +0100 Date: Sat, 21 Nov 2020 22:13:33 +0100 From: Polytropon To: Ralf Mardorf Cc: freebsd-questions@freebsd.org, Polytropon Subject: Re: usb harddisk not working Message-Id: <20201121221333.19973dbd.freebsd@edvax.de> In-Reply-To: <20201121212613.153cfbda@archlinux> References: <20201121204425.86d9c6b1.freebsd@edvax.de> <20201121212613.153cfbda@archlinux> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K1:lLFifxjqWRK6pKzMDKfBKo9K2je2hurubDp6HXotBGEd5X+xY1N c62UdUnr3iIYyRIdsfa8Nx2SjDT3WaYNSV1hhmbgbq5jN+nY/+5gfQ1hH3IT5dTvVW9qNK2 PqxOuxe2Vok05NdtKhyUkIKvCUqYXu+9aAS6f8EzuQZgXfKxhebXLKV1z4ZYN+f2RPTX72A PZkz0Jo/qrpJiA9v0DoLw== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:cPOzzN7Y1LI=:3HyzaCbOGjJaU8bd1bgCB/ M4UaLwB9L2tc3zDolII465NM1avstVJaTD9vjgTaFagzZMs5AQM6ewU+BedcIzKjR3vbk320u nRhpohlNoVCpCMEePTyVj0nhwkkXEV6FAL53p1252+ZFQH0NnlHLAmzvaeFbkw1sTIShJvVyg JBv7OCYnNhmxZ/sCXPha5xNhvsOtyqYiFUtmw8Zj4GggJMm7IzbVOBAponBySFRTI5Jt9JvId m9zd53j+V5bpecN53C/8ikqFn0ZBM1jfEO41aV6PF/YYhoiPzoYjN9h6+CeIw2g2cEXVl/6KS DX33eRgHVigad/W27H10ZmraTprfOz/CprfoYGtShKdWs9HEg4TA9j1kxwkEyymQ0QRe9VuQX 22S0flwTeytQuWxfC0nbBPJYEJGFtZx1tYe27/ifiiiqUFLrXxisVhy4n6Hls X-Rspamd-Queue-Id: 4CdmP33dpmz3Q87 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of freebsd@edvax.de has no SPF policy when checking 212.227.126.131) smtp.mailfrom=freebsd@edvax.de X-Spamd-Result: default: False [-0.60 / 15.00]; HAS_REPLYTO(0.00)[freebsd@edvax.de]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; HAS_ORG_HEADER(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RECEIVED_SPAMHAUS_PBL(0.00)[94.222.30.201:received]; RCVD_TLS_LAST(0.00)[]; R_DKIM_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[212.227.126.131:from]; ASN(0.00)[asn:8560, ipnet:212.227.0.0/16, country:DE]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[edvax.de]; AUTH_NA(1.00)[]; SPAMHAUS_ZRD(0.00)[212.227.126.131:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MID_CONTAINS_FROM(1.00)[]; RCVD_IN_DNSWL_NONE(0.00)[212.227.126.131:from]; R_SPF_NA(0.00)[no SPF record]; RWL_MAILSPIKE_POSSIBLE(0.00)[212.227.126.131:from]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-questions] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Nov 2020 21:13:44 -0000 On Sat, 21 Nov 2020 21:26:13 +0100, Ralf Mardorf wrote: > On Sat, 21 Nov 2020 20:44:25 +0100, Polytropon wrote: > >This could be a wiring thing, but in my experience with cheap USB disk > >enclosings, it's probably a version of the firmware (the part that > >does "USB plug <---> SATA disk") that is not working properly and > >according to the standard. This can also explain the "works here, but > >not there" and "works sometimes, but not always". > > Hahaha, > > IIRC we already agreed off-list regarding USB enclosures and the > firmware a while ago. > > I can not remember that we discussed wiring issues. > > IMO it's super-very-most-unlikely a wiring issue. I can't imagine a > reasonable wiring issue. I wanteed to mention this because I experienced that once: It was a USB enclosure with the came it came with - worked sometimes, on some systems, but was hard to predict _where_ it would work _when_. Turned out, after removing the original USB cable and using a different one, the disk worked everywhere every time. :-) I called this "wiring issue" because the only thing involved is the wires in the USB cable. There _might_ be wiring problems within the enclosure (PCB to disk), but that doesn't seem to happen that often. Still a possibility. > In the beginning I disassembled the drives and connected them to my PC > to test, if the drives are broken. Nowadays I don't even test the > drives, I directly return such USB enclosures. I even don't waste time > to test another USB port ;), let alone another computer. In the past, I also solved "broken disk" issues by removing them from the enclosure and attaching them to my trusted JMicron universal adapter (for SATA, PATA, mini-PATA), using the original power supply. So far, that worked on _every_ computer's _every_ USB port. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...