From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id BF290C55189 for ; Wed, 22 Apr 2020 08:41:36 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 9057C206B9 for ; Wed, 22 Apr 2020 08:41:36 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="QCpu1Dll" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 9057C206B9 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=infradead.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-nvme-bounces+linux-nvme=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=/IzBGQiLZa2NWptW5Ix+WsYaNrYxfIPuLCctyRJABso=; b=QCpu1Dll2yXEj6 Z77joENdjhT0bk/MEOuxCpqkgzQXMQI0VALcv5ZRZoA4uuI55eKYzvkP5UEJvXC8MI7htdwDCyxk7 7SwhHyGx37KzUEDkQNHo6CDygfe+zxpL7b/vYmZ61vyYaUJiawy540p8eUtMwhZfM7vB8pAueGs7R pAP2wQxmHea3CFf4auvdoDFWkiT2ZUq9qeGCReO9oa6Hr9UfHuCT6Vbgk/PQwh2shjwSX7rG7bB1r cygZoqwg9n54dYAZDvdAt2UMx3Gafx7b5LBB4LHcVwNNCL3mXOnGYvJZ7VSqYkVuz6KjH1t2AfGx0 V+ar8uoD+1iPYZ+dNlvg==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1jRAwo-0005bX-7e; Wed, 22 Apr 2020 08:41:34 +0000 Received: from hch by bombadil.infradead.org with local (Exim 4.92.3 #3 (Red Hat Linux)) id 1jRAwl-0005aw-Bt; Wed, 22 Apr 2020 08:41:31 +0000 Date: Wed, 22 Apr 2020 01:41:31 -0700 From: Christoph Hellwig To: Christian Kastner Subject: Re: NVME drive warns on power-off; smartd reports error log entry increase Message-ID: <20200422084131.GA9192@infradead.org> References: <671cdd44-dfa1-730f-634f-0946f5b6beeb@kvr.at> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <671cdd44-dfa1-730f-634f-0946f5b6beeb@kvr.at> X-BeenThere: linux-nvme@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: linux-nvme@lists.infradead.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-nvme" Errors-To: linux-nvme-bounces+linux-nvme=archiver.kernel.org@lists.infradead.org On Fri, Apr 17, 2020 at 02:49:52PM +0200, Christian Kastner wrote: > I installed a Samsung 970 EVO Plus NVME drive last year. > > After having installed smartd, I now receive a notification after each > reboot, containing the following information: > > > The following warning/error was logged by the smartd daemon: > > > > Device: /dev/nvme0, number of Error Log entries increased from 195 to 196 > > > > Device info: > > Samsung SSD 970 EVO Plus 500GB, S/N:S4EVNF0M860395T, FW:2B2QEXM7, 500 GB > > Furthermore, just a moment before actual power-off, a kernel warning is > printed. (This is something recent, resulting from updates to either the > kernel or systemd on my end). Can you check with the latest Linux 5.6 upstream kernel if that still shows up? I have a hard time figuring out what weird mix of patches any given distro kernel has. Alternatively report it to the debian bug tracking system (bugs.debian.org). For the error log: Please run nvme error-log /dev/nvme0 after the reboot (make sure nvme-cli is installed) which will tell us what entry showed up in the error log. _______________________________________________ linux-nvme mailing list linux-nvme@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-nvme