blackf0rk Posted February 22, 2020 Share Posted February 22, 2020 (edited) 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 February 22, 2020 by blackf0rk clarity & diagnostics Quote Link to comment
trurl Posted February 23, 2020 Share Posted February 23, 2020 Run extended SMART test on cache Quote Link to comment
blackf0rk Posted February 23, 2020 Author Share Posted February 23, 2020 The SMART extended self-test completed without error tower-smart-20200223-1440.zip Quote Link to comment
trurl Posted February 24, 2020 Share Posted February 24, 2020 Here is another thread about this. I don't know if it applies in your case or not. Quote Link to comment
blackf0rk Posted February 25, 2020 Author Share Posted February 25, 2020 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 Quote Link to comment
JorgeB Posted February 26, 2020 Share Posted February 26, 2020 7 hours ago, blackf0rk said: FITRIM ioctl failed: Remote I/O error It's not trimming the SSD, only the loop images, if you want trim to work connect the SSD to an onboard SATA port. 1 Quote Link to comment
blade316 Posted January 11, 2021 Share Posted January 11, 2021 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? Quote Link to comment
JorgeB Posted January 11, 2021 Share Posted January 11, 2021 5 hours ago, blade316 said: do you know why TRIM doesn't work when the SSD drives are connected to a SAS controller? Depends on the SAS controller. Quote Link to comment
Recommended Posts
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.