Date: Sun, 12 Apr 2020 20:03:38 +0300 From: Slawa Olhovchenkov <slw@zxy.spb.ru> To: Stefan Bethke <stb@lassitu.de> Cc: freebsd-stable <freebsd-stable@freebsd.org> Subject: Re: make kernel ignore broken SATA disk Message-ID: <20200412170338.GJ8012@zxy.spb.ru> In-Reply-To: <D67DEF55-9E1B-4499-9455-E1474F5CFC26@lassitu.de> References: <A33629CA-63EC-45AA-AB06-09B003BBB0A6@lassitu.de> <20200412154319.GO8028@zxy.spb.ru> <9D60946A-6D81-444B-B6D0-36202B3BE5C6@lassitu.de> <20200412163104.GI8012@zxy.spb.ru> <D67DEF55-9E1B-4499-9455-E1474F5CFC26@lassitu.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Apr 12, 2020 at 06:38:10PM +0200, Stefan Bethke wrote: > > > > Am 12.04.2020 um 18:31 schrieb Slawa Olhovchenkov <slw@zxy.spb.ru>: > > > > On Sun, Apr 12, 2020 at 06:24:09PM +0200, Stefan Bethke wrote: > > > >> Am 12.04.2020 um 17:43 schrieb Slawa Olhovchenkov <slw@zxy.spb.ru>: > >>> > >>> On Sun, Apr 12, 2020 at 04:37:06PM +0200, Stefan Bethke wrote: > >>> > >>>> I have a server I don't have physical access to right now, which has a broken SATA disk that produces mostly errors (but not entirely). > >>>> > >>>> The disk has two partitions that are part of a zpool each. I can't bring the system up with this disk being online, because ZFS is trying its darndest to use it. > >>>> > >>>> I already renamed the GPT partitions in the hope that ZFS would not find them anymore, but it does. > >>>> > >>>> I can't gpart destroy -f ada1 because "device busy". > >>>> > >>>> Is there a way, ideally in the loader, to tell the kernel to ignore ada1 and/or ahcich5? Or can I force ZFS some other way to ignore the disk? I do have a spare disk I can use to replace the failed one, but I can't get the machine into a state where I could even issue the zpool replace command. > >>> > >>> `zpool offline pool device` if you have enoght redundancy? > >> > >> I do, but the command doesn't return. Instead, I'm getting loads of sata error message. > > > > What you zpool configuration? > > This is from the working system. The identifiers are slightly different, but the structure is identical. what about `zpool detach <pool> <device>` ? > # zpool status > pool: data > state: ONLINE > status: Some supported features are not enabled on the pool. The pool can > still be used, but some features are unavailable. > action: Enable all features using 'zpool upgrade'. Once this is done, > the pool may no longer be accessible by software that does not support > the features. See zpool-features(7) for details. > scan: resilvered 176K in 0 days 00:01:28 with 0 errors on Sun May 26 21:24:54 2019 > config: > > NAME STATE READ WRITE CKSUM > data ONLINE 0 0 0 > mirror-0 ONLINE 0 0 0 > gpt/ls0data ONLINE 0 0 0 > gpt/ls1data ONLINE 0 0 0 > logs > gpt/data0log ONLINE 0 0 0 > cache > gpt/data0cache ONLINE 0 0 0 > > errors: No known data errors > > pool: ls-host > state: ONLINE > status: Some supported features are not enabled on the pool. The pool can > still be used, but some features are unavailable. > action: Enable all features using 'zpool upgrade'. Once this is done, > the pool may no longer be accessible by software that does not support > the features. See zpool-features(7) for details. > scan: scrub repaired 0 in 0 days 00:06:33 with 0 errors on Sun Apr 12 11:46:25 2020 > config: > > NAME STATE READ WRITE CKSUM > ls-host ONLINE 0 0 0 > mirror-0 ONLINE 0 0 0 > gpt/ls0host ONLINE 0 0 0 > gpt/ls1host ONLINE 0 0 0 > logs > gpt/host0log ONLINE 0 0 0 > cache > gpt/host0cache ONLINE 0 0 0 > > errors: No known data errors > > > -- > Stefan Bethke <stb@lassitu.de> Fon +49 151 14070811 >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20200412170338.GJ8012>