From: Christoph Hellwig <hch@infradead.org>
To: Christian Kastner <ckk@kvr.at>
Cc: linux-nvme@lists.infradead.org
Subject: Re: NVME drive warns on power-off; smartd reports error log entry increase
Date: Wed, 22 Apr 2020 01:41:31 -0700 [thread overview]
Message-ID: <20200422084131.GA9192@infradead.org> (raw)
In-Reply-To: <671cdd44-dfa1-730f-634f-0946f5b6beeb@kvr.at>
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
next prev parent reply other threads:[~2020-04-22 8:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 12:49 NVME drive warns on power-off; smartd reports error log entry increase Christian Kastner
2020-04-22 8:41 ` Christoph Hellwig [this message]
2020-04-22 11:30 ` Christian Kastner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200422084131.GA9192@infradead.org \
--to=hch@infradead.org \
--cc=ckk@kvr.at \
--cc=linux-nvme@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox