Trim Plugin returning error


Robot

Recommended Posts

Hi! I built my new unRAID server like a week ago, and after the parity sync and all I finally started using it on September the 7th.

Since I have a Raid1 cache pool of two M.2 1TB drives, I installed the Trim Plugin as suggested by "Fix Common Problems".

 

I got it scheduled to run every night at 5:30, but I get these errors in one of the M.2 drives everytime the trim plugin starts.

 

Sep 8 05:30:01 unRAID kernel: print_req_error: I/O error, dev nvme0n1, sector 2144
Sep 8 05:30:01 unRAID kernel: print_req_error: I/O error, dev nvme0n1, sector 10304
Sep 8 05:30:01 unRAID kernel: print_req_error: I/O error, dev nvme0n1, sector 43072
Sep 8 05:30:01 unRAID kernel: print_req_error: I/O error, dev nvme0n1, sector 2162240
Sep 8 05:30:01 unRAID kernel: print_req_error: I/O error, dev nvme0n1, sector 46704704
Sep 8 05:30:01 unRAID kernel: print_req_error: I/O error, dev nvme0n1, sector 48277568
Sep 8 05:30:01 unRAID kernel: print_req_error: I/O error, dev nvme0n1, sector 50374720
Sep 8 05:30:01 unRAID kernel: print_req_error: I/O error, dev nvme0n1, sector 52471872
Sep 8 05:30:01 unRAID kernel: print_req_error: I/O error, dev nvme0n1, sector 54569024
Sep 8 05:30:01 unRAID kernel: print_req_error: I/O error, dev nvme0n1, sector 56666176
Sep 8 05:30:01 unRAID kernel: BTRFS warning (device nvme0n1p1): failed to trim 25 block group(s), last error -5
Sep 8 05:30:01 unRAID kernel: BTRFS warning (device nvme0n1p1): failed to trim 1 device(s), last error -5
Sep 8 23:18:51 unRAID emhttpd: shcmd (3681): /usr/sbin/hdparm -y /dev/nvme0n1
Sep 8 23:18:51 unRAID root: /dev/nvme0n1:
Sep 9 05:30:01 unRAID kernel: print_req_error: I/O error, dev nvme0n1, sector 2112
Sep 9 05:30:01 unRAID kernel: print_req_error: I/O error, dev nvme0n1, sector 10304
Sep 9 05:30:01 unRAID kernel: print_req_error: I/O error, dev nvme0n1, sector 43072
Sep 9 05:30:01 unRAID kernel: print_req_error: I/O error, dev nvme0n1, sector 2141400
Sep 9 05:30:01 unRAID kernel: print_req_error: I/O error, dev nvme0n1, sector 60157808
Sep 9 05:30:01 unRAID kernel: print_req_error: I/O error, dev nvme0n1, sector 60860480
Sep 9 05:30:01 unRAID kernel: print_req_error: I/O error, dev nvme0n1, sector 62957632
Sep 9 05:30:01 unRAID kernel: print_req_error: I/O error, dev nvme0n1, sector 65475464
Sep 9 05:30:01 unRAID kernel: print_req_error: I/O error, dev nvme0n1, sector 67247928
Sep 9 05:30:01 unRAID kernel: print_req_error: I/O error, dev nvme0n1, sector 70005864
Sep 9 05:30:01 unRAID kernel: BTRFS warning (device nvme0n1p1): failed to trim 281 block group(s), last error -5
Sep 9 05:30:01 unRAID kernel: BTRFS warning (device nvme0n1p1): failed to trim 1 device(s), last error -5
Sep 10 05:30:01 unRAID kernel: print_req_error: I/O error, dev nvme0n1, sector 2144
Sep 10 05:30:01 unRAID kernel: print_req_error: I/O error, dev nvme0n1, sector 10304
Sep 10 05:30:01 unRAID kernel: print_req_error: I/O error, dev nvme0n1, sector 43072
Sep 10 05:30:01 unRAID kernel: print_req_error: I/O error, dev nvme0n1, sector 2180088
Sep 10 05:30:01 unRAID kernel: print_req_error: I/O error, dev nvme0n1, sector 28342784
Sep 10 05:30:01 unRAID kernel: print_req_error: I/O error, dev nvme0n1, sector 57390288
Sep 10 05:30:01 unRAID kernel: print_req_error: I/O error, dev nvme0n1, sector 60157808
Sep 10 05:30:01 unRAID kernel: print_req_error: I/O error, dev nvme0n1, sector 60860480
Sep 10 05:30:01 unRAID kernel: print_req_error: I/O error, dev nvme0n1, sector 62957632
Sep 10 05:30:01 unRAID kernel: print_req_error: I/O error, dev nvme0n1, sector 65475464
Sep 10 05:30:01 unRAID kernel: BTRFS warning (device nvme0n1p1): failed to trim 233 block group(s), last error -5
Sep 10 05:30:01 unRAID kernel: BTRFS warning (device nvme0n1p1): failed to trim 1 device(s), last error -5
Sep 11 05:30:01 unRAID kernel: print_req_error: I/O error, dev nvme0n1, sector 2144
Sep 11 05:30:01 unRAID kernel: print_req_error: I/O error, dev nvme0n1, sector 10304
Sep 11 05:30:01 unRAID kernel: print_req_error: I/O error, dev nvme0n1, sector 43072
Sep 11 05:30:01 unRAID kernel: print_req_error: I/O error, dev nvme0n1, sector 28342208
Sep 11 05:30:01 unRAID kernel: print_req_error: I/O error, dev nvme0n1, sector 57390288
Sep 11 05:30:01 unRAID kernel: print_req_error: I/O error, dev nvme0n1, sector 60157808
Sep 11 05:30:01 unRAID kernel: print_req_error: I/O error, dev nvme0n1, sector 60969520
Sep 11 05:30:01 unRAID kernel: print_req_error: I/O error, dev nvme0n1, sector 62957632
Sep 11 05:30:01 unRAID kernel: print_req_error: I/O error, dev nvme0n1, sector 65475464
Sep 11 05:30:01 unRAID kernel: print_req_error: I/O error, dev nvme0n1, sector 67247416
Sep 11 05:30:01 unRAID kernel: BTRFS warning (device nvme0n1p1): failed to trim 169 block group(s), last error -5
Sep 11 05:30:01 unRAID kernel: BTRFS warning (device nvme0n1p1): failed to trim 1 device(s), last error -5

 

It seems like some sectors are bad? It's not always the same ones... Also it doesn't seem to be increasing day by day?

Should I be worried? This M.2 drive is brand new.

 

By the way, this particular M.2 is NVME; the other one on the pool is M.2 SATA, since my mobo didn't support two NVME disks.

 

Thanks!

Link to comment
On 9/12/2019 at 3:28 PM, Taddeusz said:

Do you have IOMMU enabled in your BIOS? I was getting similar issues with my NVME cache drive. I added "iommu=pt" to the append statement in my syslinux configuration and it fixed that. Basically what this statement does is enables IOMMU only for the devices you want to pass through to a VM.

 

I have it enabled, yes. Although I didn't enable it, it seems it is enabled by default when loading BIOS defaults.

What is the "syslinux configuration",  and what is the "append statement"? Only thing I manually edited so far is the go file in the flashdrive share, in order to disable c-states of my Ryzen.

 

Thanks!

Link to comment
7 hours ago, Robot said:

 

I have it enabled, yes. Although I didn't enable it, it seems it is enabled by default when loading BIOS defaults.

What is the "syslinux configuration",  and what is the "append statement"? Only thing I manually edited so far is the go file in the flashdrive share, in order to disable c-states of my Ryzen.

 

Thanks!

Open the web interface to the Main tab. Under Boot Device click on Flash. Scroll down to the Syslinux Configuration section. I would add that to both the "unRAID OS" and "unRAID OS GUI Mode" sections. Add it on the same line after "append initrd=/bzroot" separated with a space.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.