Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 16 Jun 2015 11:15:58 +0200
From:      Fabian Keil <freebsd-listen@fabiankeil.de>
To:        freebsd-questions@freebsd.org
Subject:   Re: ZFS passdevgonecb
Message-ID:  <7869b17a.63033ffe@fabiankeil.de>
In-Reply-To: <557F90DB.80601@herveybayaustralia.com.au>
References:  <557F90DB.80601@herveybayaustralia.com.au>

next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/UmZKK_kwtf7r5bOE71wBcZb
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Da Rock <freebsd-questions@herveybayaustralia.com.au> wrote:

> I hate jumping in like this out of the blue, but time is not on my side=20
> atm with a lot going on.
>=20
> I have a problem with some devices disappearing on various versions of=20
> FreeBSD and machines (laptops, workstations/servers). Umass are the=20
> norm, with the message occurring most on usb sticks and sd cards.
>=20
> Big problem atm is that my file server has a failed disk in the raid,=20
> and I've tried replacing it with a new drive (twice now), and both times=
=20
> it begins to resilver and then it is "REMOVED". If I online it again, it=
=20
> goes for about 10mins then REMOVED again.

For similar occasions I wrote a ggatel patch as a workaround:
https://www.fabiankeil.de/sourcecode/electrobsd/ggatel-Optionally-retry-req=
uests.diff

Later on I stumbled over gmountver which you may want to try
first. At least on my system it doesn't work unless I disable
kern.geom.mountver.check_ident (which obviously is dangerous),
but I didn't have time to investigate this yet.

> Dmesg shows that the device is removed from the devfs with a=20
> passdevgonecb/lost device message. This apparently occurs right at boot=20
> too, as it shows amongst the usual scrolling during boot.
>=20
> I had a chat with someone and they mentioned the cable and/or controller=
=20
> could be the issue. Could anyone add any insight or tests I could do?=20

Scrubbing the pool with one of the workarounds mentioned above might
be a good start.

Fabian

--Sig_/UmZKK_kwtf7r5bOE71wBcZb
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlV/6TsACgkQBYqIVf93VJ1TQQCgxrOiIXBBJXXKFA4sQiTbPW/+
rW4AoLkjftQptdFYBDc0ZW6ZR1K63ds/
=wlFl
-----END PGP SIGNATURE-----

--Sig_/UmZKK_kwtf7r5bOE71wBcZb--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7869b17a.63033ffe>