From owner-freebsd-hackers@freebsd.org Thu Jul 5 16:11:36 2018 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0B0F41038698 for ; Thu, 5 Jul 2018 16:11:36 +0000 (UTC) (envelope-from sblachmann@gmail.com) Received: from mail-oi0-x22a.google.com (mail-oi0-x22a.google.com [IPv6:2607:f8b0:4003:c06::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8E08D84EAF; Thu, 5 Jul 2018 16:11:35 +0000 (UTC) (envelope-from sblachmann@gmail.com) Received: by mail-oi0-x22a.google.com with SMTP id d189-v6so17911224oib.6; Thu, 05 Jul 2018 09:11:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=WZ2wsYhtVL1hUyIJVsXmwuAuAxJzsn7T6bie5dJ4sik=; b=DRx7sWqByay0DqmEkR2CtFBxvIY/gWiQ8HmeElTNz9ZyxhT9de+NC5+CmPaM7FCz2n kISBp2LGR2KOnZMpF7EPOIOMhSFlvPfDsfptrj11gUqlb9Yq1LOOMY3mBHNf8reg/huA Q9w4wFPFkn6+X9Dof3rDytUmApX5AjE0kUD9Hr1jD7DN3k9rM7oB4bASub7Cl0lbqRla njgIev3z5w57jeXZ+xw5gLHo/CHUl6LS4jNnTUtqBTDtnlNre3WKaMinV0gnzjrLu9zz M92ac3HR2kbl4M/lTVW2tFc6Z4xwPWJDPj9H/vp9ITPUGH7Eh8EJlkU1/71uIP6KwMb2 VkiQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=WZ2wsYhtVL1hUyIJVsXmwuAuAxJzsn7T6bie5dJ4sik=; b=Qs5d1yPf640BmUsj/K/MMB/tJX8lRQsnH3YmH0DPX46W3U8YqXXiybN1e/XpViGRjB h7nVY1aGcim+V9PXJ2pN5u8J1XJmHy9YTo2TeWIKmPgj5Y9uNAmSz7Wi2y3cXOVJoAgh W6NqRLq96mNrH3WpnhngRKKoBA/QOR9mgUlgQnNTeDMMzp9ZqgcHo9n1fWD/Akupq3mV AhVBkO25HAh6f7wPBZVjFmsDDP+uexeL+YE9Dc2poag443/E1hM4yq/dsDEx2hxa2CZj UvIIb6O5phdoz7Y5BBtJY7TY21wJPYttE88RI2EqAa+/+Gsc28d/JqFyvEQpqv3wynnO 0s+A== X-Gm-Message-State: APt69E1wuuvj5DAWO+jPk+Tm0vkVDP3P/1ZWcK/TEhcyKCydApL8NkLH UDKQGxDVzCQmVuGaFKE2F/RDkKl5v/vNUTDH34Q9aw== X-Google-Smtp-Source: AAOMgpfvl7eO+l/yCJgIig1N8LjIfDwqan9C4bf3Fa5Jg24wOFIh2AGx437Z+DighkVlj6/56bawJx/D72sQJmqTqGo= X-Received: by 2002:aca:3d43:: with SMTP id k64-v6mr6988533oia.166.1530807094956; Thu, 05 Jul 2018 09:11:34 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:ac9:2b9c:0:0:0:0:0 with HTTP; Thu, 5 Jul 2018 09:11:34 -0700 (PDT) In-Reply-To: References: <51eb8232-49a7-0b3a-2d0f-9882ebfbfa1d@FreeBSD.org> From: Stefan Blachmann Date: Thu, 5 Jul 2018 18:11:34 +0200 Message-ID: Subject: Re: Confusing smartd messages To: Wojciech Puchar Cc: Lev Serebryakov , FreeBSD Hackers , George Mitchell Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jul 2018 16:11:36 -0000 Another problem issue is that flash memories also exhibit the charge drain problem. They cannot be read indefinitely without occasional rewrite, as every read drains a minuscule amount of the charge. I often wished I knew of some OS/driver function/mechanism which can rewrite respective refresh media on a mounted+running system and could be, for example, run via cron. Such would not only be very useful to fix pending sectors without stopping a running machine, but also for keeping embedded machines' flash memories reliably charged over the years. On 7/5/18, Wojciech Puchar wrote: >>> okay. What's the recommended action at this point? -- George >> >> In my experience it is begin of disk death, even if overall status is >> PASSED. It could work for month or may be half a year after first >> Offline_Uncorrectable is detected (it depends on load), but you best bet >> to replace it ASAP and throw away. > well my disk had this and live happily for 3 years. > > It JUST means that some sectors are unreadable which may be a reason that > at some some write got wrong because of hardware problem. But this problem > may be - and possibly were - powerdown while writing, or power spike. > > the media itself could be fine. the best action in such case is to force > rewrite whole drive with some data. > > with gmirror it is as easy as first checking second drive for no errors, > then forcing remirror. > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" >