Hey! I just found this error in the log today.

Nov 24 05:01:10 NAS kernel: blk_update_request: critical target error, dev sdc, sector 230727725

I am not sure what it means, but seems related to the "Dynamix SSD TRIM" pkugin?
All drives (data, parity, cache) have been pre-cleared before they were added to the array.

 

I also don't know why sending the alert email failed because when I test the email notification then it works

Full log attached.

log.txt

 

diagnostics file a bit further down below in this thread.

Edited November 25, 20178 yr by cholzer

Not sure about the error itself (also always post the complete diagnostics), but your system share is still on the array and can't be moved while in use, since you have a cache device do this:

 

-stop docker service

-stop VM service

-run the mover

-when done restart docker and VM services.

My concern isn't with the Mover entries, but the bad sector after the mover finished.

I have just checked my Schedules and noticed that the Mover and SSD Trim are executed at the same time.
I have now changed the SSD trim Schedule to a later point so that these 2 should not collide anymore (even though it seems that they were not executed at the same time).

 

But when I read the log correctly then it seems to say that there is a bad sector on the cache SSD? :-/

 

1 hour ago, johnnie.black said:

Not sure about the error itself (also always post the complete diagnostics), but your system share is still on the array and can't be moved while in use, since you have a cache device do this:

 

-stop docker service

-stop VM service

-run the mover

-when done restart docker and VM services.

 

Guess I need to enable VT-x in the bios as I can't access the "VM Manager" in the settings to turn of the service. Only get a warning that VT-x is not enabled/present.

Edited November 24, 20178 yr by cholzer

I've seen before some ATA errors during trim on some SSDs, but not like those, it may be related to the controller where it's connected not supporting trim, but without the diagnostics I'm just speculating.

This issue is definitely caused/related to the SSD Trim plugin as it happened again today right after the plugin was executed.

 

Nov 25 05:45:42 NAS kernel: sd 1:0:1:0: [sdc] tag#23 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Nov 25 05:45:42 NAS kernel: sd 1:0:1:0: [sdc] tag#23 Sense Key : 0x5 [current]
Nov 25 05:45:42 NAS kernel: sd 1:0:1:0: [sdc] tag#23 ASC=0x21 ASCQ=0x0
Nov 25 05:45:42 NAS kernel: sd 1:0:1:0: [sdc] tag#23 CDB: opcode=0x42 42 00 00 00 00 00 00 00 18 00
Nov 25 05:45:42 NAS kernel: blk_update_request: critical target error, dev sdc, sector 230727725
Nov 25 05:45:43 NAS sSMTP[1006]: Creating SSL connection to host
Nov 25 05:45:43 NAS sSMTP[1006]: SSL connection using ECDHE-RSA-AES256-GCM-SHA384
Nov 25 05:45:47 NAS sSMTP[1006]: 554 5.2.0 STOREDRV.Submission.Exception:InvalidRecipientsException; Failed to process message due to a permanent exception with message Recipient "root" isn't resolved. All recipients must be resolved before a message can be submitted. InvalidRecipientsException: Recipient "root" isn't resolved. All recipients must be resolved before a message can be submitted. <80203e93-af65-4a59-bc51-da6368e9c5b7@CWLP265MB0323.GBRP265.PROD.OUTLOOK.COM> [Hostname=CWLP265MB0323.GBRP265.PROD.OUTLOOK.COM]

Also the e-mail notification failed again as the plugin wants to notify 'root' ? Instead of sending an e-mail to the address that is in the notification configuration. I doubt that I could even add an e-mail address to the root user? At least I don't see such a field. :-/

nas-diagnostics-20171125-0845.zip

Edited November 25, 20178 yr by cholzer

LSI2008 based controllers don't support trim on most SSDs, you should connect it to the onboard SATA ports, though it's currently set to IDE, enter bios and change it to AHCI.

 

 

2 hours ago, johnnie.black said:

LSI2008 based controllers don't support trim on most SSDs, you should connect it to the onboard SATA ports, though it's currently set to IDE, enter bios and change it to AHCI.

 

 

Thanks!

 

I have change the SATA config on the mainboard to AHCI and connected the SSD Cache to one of the Sata 6G connectors.
Cache drive shows up and is working inside of unRAID too.

 

Trimming seems to work now too!

Nov 25 11:40:42 NAS root: /mnt/cache: 105.6 GiB (113398353920 bytes) trimmed

Thanks a lot!!!!

 

But the log is flooded with this now:

Nov 25 11:37:23 NAS root: error: plugins/preclear.disk/Preclear.php: wrong csrf_token

Already tried to uninstall and reinstall the plugin, but still throws that error now.

 

*edit*
"wrong csrf_token" was caused by having a browser tab open from before I restarted the server. refreshed that and now the error is gone.

Edited November 25, 20178 yr by cholzer