print_req_error: critical target error, dev sdg


Recommended Posts

I'm getting the following errors and warnings when the trim service runs. I'm using the SSD as my cache device.

 

Feb 22 08:46:08 Tower kernel: sd 7:0:5:0: [sdg] tag#2572 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Feb 22 08:46:08 Tower kernel: sd 7:0:5:0: [sdg] tag#2572 Sense Key : 0x5 [current]
Feb 22 08:46:08 Tower kernel: sd 7:0:5:0: [sdg] tag#2572 ASC=0x21 ASCQ=0x0
Feb 22 08:46:08 Tower kernel: sd 7:0:5:0: [sdg] tag#2572 CDB: opcode=0x42 42 00 00 00 00 00 00 00 18 00
Feb 22 08:46:08 Tower kernel: print_req_error: critical target error, dev sdg, sector 1950394402
Feb 22 08:46:08 Tower kernel: BTRFS warning (device sdg1): failed to trim 1 device(s), last error -121
Feb 22 08:46:08 Tower root: /etc/libvirt: 920.7 MiB (965431296 bytes) trimmed on /dev/loop3
Feb 22 08:46:08 Tower root: /var/lib/docker: 18.1 GiB (19436044288 bytes) trimmed on /dev/loop2
Feb 22 08:46:13 Tower sSMTP[24153]: Creating SSL connection to host
Feb 22 08:46:13 Tower sSMTP[24153]: SSL connection using TLS_AES_256_GCM_SHA384
Feb 22 08:46:14 Tower sSMTP[24153]: Authorization failed (535 5.7.8 https://support.google.com/mail/?p=BadCredentials v202sm2148007oie.10 - gsmtp)

Motherboard:

Supermicro X9DR3-F, Version 0123456789

 

Processor:

Intel® Xeon® CPU E5-2630 v2 @ 2.60GHz

 

 

tower-diagnostics-20200222-1310.zip

Edited by blackf0rk
clarity & diagnostics
Link to comment

To be clear, it seems like TRIM is working - just not all the way (I think). When I run a fstrim -a -v, I get this...

 

root@Tower:~# fstrim -a -v
/etc/libvirt: 920.6 MiB (965332992 bytes) trimmed on /dev/loop3
/var/lib/docker: 17.9 GiB (19178844160 bytes) trimmed on /dev/loop2
fstrim: /mnt/cache: FITRIM ioctl failed: Remote I/O error

 

Link to comment
  • 10 months later...
On 2/26/2020 at 5:28 PM, JorgeB said:

It's not trimming the SSD, only the loop images, if you want trim to work connect the SSD to an onboard SATA port.

hey mate, do you know why TRIM doesn't work when the SSD drives are connected to a SAS controller? Whats the reason they have to be connected to the onboard SATA ports? 

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.