[Solved] kernel: print_req_error: I/O error

[Titus]

So here is the issue. I have replaced my cache with 2x1TB NVME and use other 2 I had for plex metadata and vm storage. Whenever the Dynamix SSD TRIM is ran I get these errors but all the ssd/nvme ssd are not in the array. I have searched and really am stumped for the damn of me cannot figure out what dev loop2/3 are and whats causing the errors.

 

 

 

Quote

Apr 19 03:05:01 SERVERHOSTNAME kernel: print_req_error: 15 callbacks suppressed
Apr 19 03:05:01 SERVERHOSTNAME kernel: print_req_error: I/O error, dev loop3, sector 26968
Apr 19 03:05:01 SERVERHOSTNAME kernel: print_req_error: I/O error, dev loop3, sector 75776
Apr 19 03:05:01 SERVERHOSTNAME kernel: print_req_error: I/O error, dev loop3, sector 285440
Apr 19 03:05:01 SERVERHOSTNAME kernel: print_req_error: I/O error, dev loop3, sector 416512
Apr 19 03:05:01 SERVERHOSTNAME kernel: BTRFS warning (device loop3): failed to trim 4 block group(s), last error -5
Apr 19 03:05:01 SERVERHOSTNAME kernel: print_req_error: I/O error, dev loop3, sector 2048
Apr 19 03:05:01 SERVERHOSTNAME kernel: BTRFS warning (device loop3): failed to trim 1 device(s), last error -5
Apr 19 03:05:01 SERVERHOSTNAME kernel: print_req_error: I/O error, dev loop2, sector 26872
Apr 19 03:05:01 SERVERHOSTNAME kernel: print_req_error: I/O error, dev loop2, sector 78048
Apr 19 03:05:01 SERVERHOSTNAME kernel: print_req_error: I/O error, dev loop2, sector 1127272
Apr 19 03:05:01 SERVERHOSTNAME kernel: print_req_error: I/O error, dev loop2, sector 3756488
Apr 19 03:05:01 SERVERHOSTNAME kernel: print_req_error: I/O error, dev loop2, sector 5352640
Apr 19 03:05:01 SERVERHOSTNAME kernel: BTRFS warning (device loop2): failed to trim 17 block group(s), last error -5
Apr 19 03:05:01 SERVERHOSTNAME kernel: BTRFS warning (device loop2): failed to trim 1 device(s), last error -5
Apr 19 03:05:37 SERVERHOSTNAME root: /mnt/disks/vmssd: 374.7 GiB (402313396224 bytes) trimmed on /dev/sdo1
Apr 19 03:05:37 SERVERHOSTNAME root: /mnt/disks/plexssd: 457.9 GiB (491640537088 bytes) trimmed on /dev/sdn1
Apr 19 03:05:37 SERVERHOSTNAME root: /mnt/cache: 898.3 GiB (964490092544 bytes) trimmed on /dev/nvme0n1p1

 

Edited April 21, 2020 by Titus
changed Server name

[Titus]

I have scrubbed both nothing is showing bad. I do have them on vmssd and not on cache im going to try and move them to cache and off vmssd if i get the same warning in the morning. I am puzzled that does smart check on ssd's nothing scrub nothing but still get this error

[itimpi]

How are the SSDs connected?  The error messages suggest that the ones contains the docker.img and libvirt.img files are connected to a controller that does not support the trim operation, but that is just a guess.

 

if you provide your system diagnostics zip file (obtained via Tools >> Diagnostics) attached to your NEXT post then we should be able to provide a more definitive answer.

[Titus]

that is weird because the controller does support ssd trim. I am just wondering it is not liking the fact that is pasted through to vmssd on unassigned devices and rather be in cache but id rather have my 62gb docker image off the cache and on the ssd but who knows

titties-diagnostics-20200420-0347.zip

[JonathanM]

2 hours ago, Titus said:

my 62gb docker image

Why in the world is it that big? How many containers do you have? I have 32 containers, and my image is using 16GB. I have a 30GB image because some of my containers temporarily take a bunch of space during upgrades, but I'm typically under 20GB total usage.

 

Unless you installed every container in the app tab, I suspect you have something misconfigured.

[Titus]

1 hour ago, jonathanm said:

Why in the world is it that big? How many containers do you have? I have 32 containers, and my image is using 16GB. I have a 30GB image because some of my containers temporarily take a bunch of space during upgrades, but I'm typically under 20GB total usage.

 

Unless you installed every container in the app tab, I suspect you have something misconfigured.

honestly that has been the docker size since I started unraid server last year. I just haven't shrunk it but last time I checked it was running 12gb. Probably should shrink it I might if today when I get off work and move the containers back to cache delete it and remake it if this continues to give errors. HBA is update and supports TRIM so only thing I can think of is from moving drives it somewhere lost some bytes and giving me nothing but headaches. 

[Titus]

Well I went and just rebuilt the docker and libvirt we will see once nightly trim comes if I still get error

[Titus]

Well rebuilding them fixed the issue

 

 

Apr 21 03:05:39 TittieS root: /etc/libvirt: 1.8 GiB (1933770752 bytes) trimmed on /dev/loop3
Apr 21 03:05:39 TittieS root: /var/lib/docker: 20.2 GiB (21677744128 bytes) trimmed on /dev/loop2
Apr 21 03:05:39 TittieS root: /mnt/disks/vmssd: 435.7 GiB (467811647488 bytes) trimmed on /dev/sdo1
Apr 21 03:05:39 TittieS root: /mnt/disks/plexssd: 457.8 GiB (491516846080 bytes) trimmed on /dev/sdn1
Apr 21 03:05:39 TittieS root: /mnt/cache: 880.3 GiB (945247129600 bytes) trimmed on /dev/nvme0n1p1