From: davidc502 <davidc502@tds.net>
To: linux-block@vger.kernel.org
Subject: Re: fstrim error - AORUS NVMe Gen4 SSD
Date: Mon, 22 Jul 2019 19:06:30 -0500 [thread overview]
Message-ID: <bdb8e486-bcda-1b11-0fd7-f25bc48eeb2c@tds.net> (raw)
In-Reply-To: <4b76413b-1af4-a406-5b16-6789b2b7012a@tds.net>
Hello,
I'm not sure my email from yesterday went through due to .txt
requirements. However, I've added some additional logs at the end of
this email.
If this email group does not deal with these type of issues, please
let me know.
Best Regards,
David
On 7/20/19 9:41 PM, davidc502 wrote:
Hello,
I've assembled a X570 board with a 1TB AORUS NVMe Gen4 SSD.
When attempting to fstrim the NVMe, I receive the following error.
davidc502@Ryzen-3900x:~$ sudo fstrim -a -v
fstrim: /boot/efi: FITRIM ioctl failed: Input/output error
fstrim: /: FITRIM ioctl failed: Input/output error
Anyhow, I have put some details below which might be helpful. Note
that this NVMe is supposed to be TRIM and SMART compliant. The SMART
outputs are available using the utility “nvme-cli”.
I am willing to provide whatever command outputs that are needed to
help solve this issue.
OS= Ubuntu 18.4.2 LTS
Different Kernels I’ve tried = 5.1.16, 5.2 rc7, and 4.18
fstrim version = fstrim from util-linux 2.31.1
Firmware version for Aorus NVMe = EGFM11.0
mount output
/dev/nvme0n1p2 on / type ext4 (rw,relatime,errors=remount-ro)
/dev/nvme0n1p1 on /boot/efi type vfat
(rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
NVMe firmware version using utility ‘nvme’
$ sudo nvme list /dev/nvme0n1
Node SN Model Namespace Usage
Format FW Rev
---------------- --------------------
---------------------------------------- ---------
-------------------------- ---------------- --------
/dev/nvme0n1 SNX GIGABYTE GP-ASM2NE6100TTTD
1 1.00 TB / 1.00 TB 512 B + 0 B EGFM11.0
More Log information
[Fri Jul 19 17:05:08 2019] nvme 0000:01:00.0: AMD-Vi: Event logged
[IO_PAGE_FAULT domain=0x0000 address=0x0 flags=0x0000]
[Fri Jul 19 17:05:08 2019] nvme 0000:01:00.0: AMD-Vi: Event logged
[IO_PAGE_FAULT domain=0x0000 address=0x0 flags=0x0000]
[Fri Jul 19 17:05:08 2019] nvme 0000:01:00.0: AMD-Vi: Event logged
[IO_PAGE_FAULT domain=0x0000 address=0x0 flags=0x0000]
[Fri Jul 19 17:05:08 2019] nvme 0000:01:00.0: AMD-Vi: Event logged
[IO_PAGE_FAULT domain=0x0000 address=0x0 flags=0x0000]
[Fri Jul 19 17:05:08 2019] nvme 0000:01:00.0: AMD-Vi: Event logged
[IO_PAGE_FAULT domain=0x0000 address=0x0 flags=0x0000]
[Fri Jul 19 17:05:08 2019] nvme 0000:01:00.0: AMD-Vi: Event logged
[IO_PAGE_FAULT domain=0x0000 address=0x0 flags=0x0000]
[Fri Jul 19 17:05:08 2019] print_req_error: I/O error, dev nvme0n1,
sector 4160 flags 803
[Fri Jul 19 17:05:08 2019] nvme 0000:01:00.0: AMD-Vi: Event logged
[IO_PAGE_FAULT domain=0x0000 address=0x0 flags=0x0000]
[Fri Jul 19 17:05:08 2019] nvme 0000:01:00.0: AMD-Vi: Event logged
[IO_PAGE_FAULT domain=0x0000 address=0x0 flags=0x0000]
[Fri Jul 19 17:05:08 2019] nvme 0000:01:00.0: AMD-Vi: Event logged
[IO_PAGE_FAULT domain=0x0000 address=0x0 flags=0x0000]
[Fri Jul 19 17:05:08 2019] nvme 0000:01:00.0: AMD-Vi: Event logged
[IO_PAGE_FAULT domain=0x0000 address=0x0 flags=0x0000]
[Fri Jul 19 17:05:08 2019] amd_iommu_report_page_fault: 28 callbacks
suppressed
[Fri Jul 19 17:05:08 2019] AMD-Vi: Event logged [IO_PAGE_FAULT
device=01:00.0 domain=0x0000 address=0x0 flags=0x0000]
[Fri Jul 19 17:05:08 2019] AMD-Vi: Event logged [IO_PAGE_FAULT
device=01:00.0 domain=0x0000 address=0x0 flags=0x0000]
[Fri Jul 19 17:05:08 2019] print_req_error: I/O error, dev nvme0n1,
sector 1141976 flags 803
[Fri Jul 19 17:05:59 2019] amd_iommu_report_page_fault: 2 callbacks
suppressed
[Fri Jul 19 17:05:59 2019] nvme 0000:01:00.0: AMD-Vi: Event logged
[IO_PAGE_FAULT domain=0x0000 address=0x0 flags=0x0000]
[Fri Jul 19 17:05:59 2019] nvme 0000:01:00.0: AMD-Vi: Event logged
[IO_PAGE_FAULT domain=0x0000 address=0x0 flags=0x0000]
[Fri Jul 19 17:05:59 2019] nvme 0000:01:00.0: AMD-Vi: Event logged
[IO_PAGE_FAULT domain=0x0000 address=0x0 flags=0x0000]
[Fri Jul 19 17:05:59 2019] nvme 0000:01:00.0: AMD-Vi: Event logged
[IO_PAGE_FAULT domain=0x0000 address=0x0 flags=0x0000]
[Fri Jul 19 17:05:59 2019] nvme 0000:01:00.0: AMD-Vi: Event logged
[IO_PAGE_FAULT domain=0x0000 address=0x0 flags=0x0000]
[Fri Jul 19 17:05:59 2019] nvme 0000:01:00.0: AMD-Vi: Event logged
[IO_PAGE_FAULT domain=0x0000 address=0x0 flags=0x0000]
[Fri Jul 19 17:05:59 2019] print_req_error: I/O error, dev nvme0n1,
sector 4160 flags 803
[Fri Jul 19 17:05:59 2019] nvme 0000:01:00.0: AMD-Vi: Event logged
[IO_PAGE_FAULT domain=0x0000 address=0x0 flags=0x0000]
[Fri Jul 19 17:05:59 2019] nvme 0000:01:00.0: AMD-Vi: Event logged
[IO_PAGE_FAULT domain=0x0000 address=0x0 flags=0x0000]
[Fri Jul 19 17:05:59 2019] nvme 0000:01:00.0: AMD-Vi: Event logged
[IO_PAGE_FAULT domain=0x0000 address=0x0 flags=0x0000]
[Fri Jul 19 17:05:59 2019] nvme 0000:01:00.0: AMD-Vi: Event logged
[IO_PAGE_FAULT domain=0x0000 address=0x0 flags=0x0000]
[Fri Jul 19 17:05:59 2019] AMD-Vi: Event logged [IO_PAGE_FAULT
device=01:00.0 domain=0x0000 address=0x0 flags=0x0000]
[Fri Jul 19 17:05:59 2019] AMD-Vi: Event logged [IO_PAGE_FAULT
device=01:00.0 domain=0x0000 address=0x0 flags=0x0000]
[Fri Jul 19 17:05:59 2019] print_req_error: I/O error, dev nvme0n1,
sector 1141976 flags 803
If there is any other additional information I can provide please let
me know.
Best Regards,
David
next prev parent reply other threads:[~2019-07-23 0:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-21 2:41 fstrim error - AORUS NVMe Gen4 SSD davidc502
[not found] ` <4b76413b-1af4-a406-5b16-6789b2b7012a@tds.net>
2019-07-23 0:06 ` davidc502 [this message]
2019-07-23 2:19 ` Ming Lei
[not found] ` <4a7ec7aa-f6ee-f9dc-4a17-38f2b169c721@tds.net>
2019-07-23 4:38 ` Ming Lei
2019-07-23 21:38 ` davidc502
2019-07-23 21:56 ` davidc502
2019-07-24 1:45 ` Ming Lei
2019-07-24 1:45 ` Ming Lei
2019-07-24 21:30 ` Keith Busch
2019-07-26 13:26 ` davidc502
2019-07-26 13:30 ` davidc502
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=bdb8e486-bcda-1b11-0fd7-f25bc48eeb2c@tds.net \
--to=davidc502@tds.net \
--cc=linux-block@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.