Date: Mon, 5 Mar 2018 13:10:48 +0100 From: Dimitry Andric <dim@FreeBSD.org> To: Bruce Evans <brde@optusnet.com.au> Cc: tech-lists <tech-lists@zyxst.net>, FreeBSD Filesystems <freebsd-fs@freebsd.org>, FreeBSD Stable <freebsd-stable@freebsd.org> Subject: Re: zfs problems after rebuilding system [SOLVED] Message-ID: <AADBAEE5-BD33-4DEC-94C2-99C0199351B3@FreeBSD.org> In-Reply-To: <20180303234236.M3811@besplex.bde.org> References: <21c64a2d-b9f9-24c8-88ec-ff1210891f60@zyxst.net> <CAOtMX2jfmh%2BAMccAMcPSRq-DcQgs6wioqSSUHncEfPruD=w_Ag@mail.gmail.com> <1dc2b8ef-2914-8182-e2b0-ac637e6b2095@zyxst.net> <CAOtMX2gHm_UdYzn5J6Lm76r8KakkYMzEcxddFYLqkmGYwkihuQ@mail.gmail.com> <65372449-53f1-8002-981a-e20f4a592e26@zyxst.net> <CAOtMX2g79aqkinu0meBzhLbui7n9H9yiEwxKm6cxpZSaxbWqbg@mail.gmail.com> <f0e9385c-4d62-a68d-ea93-f013bc456b5d@zyxst.net> <CAOjFWZ4Yq4cnWN_qucbN4W-6qtf4NYNzjNKe4QL17DU-Q=N%2B_g@mail.gmail.com> <CAOjFWZ53WaOtCvRtNpsL1OqgE7rDu8jWNEHRVPZ5Z3Q_n1bnqw@mail.gmail.com> <CAOjFWZ6gF3=N8=v3aXQaiG=pd8kmZ-xpvN2jHYj9%2Bh8fCm=rsw@mail.gmail.com> <CAOjFWZ7nPFdKr_G2qHihXdcHUBed7V0uLLHM9=p1PKzJMZNemw@mail.gmail.com> <CAOjFWZ6J7UV_xXxtASqnonS8qatqaSSEqJUKyi9nw%2Bms%2BUg1QQ@mail.gmail.com> <5CFC89E9-57BE-4CB7-9C55-0D3CCF1E8D3D@FreeBSD.org> <edfb5da8-3fad-168f-4dbc-6da9b0822c76@zyxst.net> <20180303234236.M3811@besplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail=_964AB4CF-CDC5-4A80-AA77-493179094E33 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii On 3 Mar 2018, at 13:56, Bruce Evans <brde@optusnet.com.au> wrote: > > On Sat, 3 Mar 2018, tech-lists wrote: >> On 03/03/2018 00:23, Dimitry Andric wrote: ... >>> Whether this is due to some sort of BIOS handover trouble, or due to >>> cheap and/or crappy USB-to-SATA bridges (even with brand WD and Seagate >>> disks!), I have no idea. I attempted to debug it at some point, but >>> a well-placed "sleep 10" was an acceptable workaround... :) >> >> That fixed it, thank you again :D > > That won't work for the boot drive. > > When no boot drive is detected early enough, the kernel goes to the > mountroot prompt. That seems to hold a Giant lock which inhibits > further progress being made. Sometimes progress can be made by trying > to mount unmountable partitions on other drives, but this usually goes > too fast, especially if the USB drive often times out. What I would like to know, is why our USB stack has such timeout issues at all. When I boot Linux on the same type of hardware, I never see USB timeouts. They must be doing something right, or maybe they just don't bother checking some status bits that we are very strict about? -Dimitry --Apple-Mail=_964AB4CF-CDC5-4A80-AA77-493179094E33 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.2 iF0EARECAB0WIQR6tGLSzjX8bUI5T82wXqMKLiCWowUCWp0zyAAKCRCwXqMKLiCW ox4PAKCWp0chtfvrf/plVG056kdey/h94wCgvFWof7JkHBclVqAdAWiqXqSCYz4= =aRJ0 -----END PGP SIGNATURE----- --Apple-Mail=_964AB4CF-CDC5-4A80-AA77-493179094E33--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AADBAEE5-BD33-4DEC-94C2-99C0199351B3>