A few errors in my log...

opentoe · February 23, 2020

Hi- I was sifting through my logs which I try to do every now and then to make sure things are working smooth and came upon a few errors which I don't think should be there. I've attached my diags, but in a nutshell these are the entries:

SUN kernel: EDAC sbridge: Failed to register device with error -19.

this comes up a lot.

SUN kernel: print_req_error: critical target error, dev sdi, sector 975849578

SDI is an UNASSINGED drive.

sSMTP[10629]: Authorization failed (535 5.7.8 https://support.google.com/mail/?p=BadCredentials z13sm2720944qtu.53 - gsmtp)

I do not have any email notifications setup at all. Have no idea why it is trying to connect to Google.

sun-diagnostics-20200223-0234.zip

Squid · February 23, 2020

5 hours ago, opentoe said:

sSMTP[10629]: Authorization failed (535 5.7.8 https://support.google.com/mail/?p=BadCredentials z13sm2720944qtu.53 - gsmtp)

I do not have any email notifications setup at all. Have no idea why it is trying to connect to Google.

You sure about that?

5 hours ago, opentoe said:

SUN kernel: print_req_error: critical target error, dev sdi, sector 975849578

SDI is an UNASSINGED drive.

Run an extended smart test on it

5 hours ago, opentoe said:

SUN kernel: EDAC sbridge: Failed to register device with error -19.

this comes up a lot.

Happens during initialization and not a worry.

opentoe · February 24, 2020

On 2/23/2020 at 8:37 AM, Squid said:

You sure about that?

Run an extended smart test on it

Happens during initialization and not a worry.

I unchecked ALL email notifications. I only like to get my notifications on the browser. Where it says SMTP settings in the notifications area it defaults to GMAIL. I look through the list and there is no selection DISABLE or anything like that. If I hit RESET, it goes right back to GMAIL.

I will run an extended test on that drive spitting out that error on that unassigned SDI drive. It is an older drive but good for misc stuff.

Thanks for the info...

Forgot one question. After running the extended, where does the output go?

Edited February 24, 2020 by opentoe

Squid · February 24, 2020

That's happening then because the trim command running on a cron job is returning an error when it tries to trim your cache drive because of the critical target errors. What it's trying to do is email "root". Is there anything listed within the email addresses / etc on the scheduler?

opentoe · February 25, 2020

The SDI drive that is spiting out the errors is an unassigned SSD drive. I ran the extended test and when I checked out the webgui all it says is COMPLETED WITHOUT ERROR. There is no button that says VIEW RESULTS or anything.

I don't use the cache drive as a "cache" drive. I've set all my drives NOT to use it. Unfortunately there is no DISABLED option in the mover settings. I attached my scheduler page and my notification page.

And here is the log info for that SDI drive spitting out those errors:

Feb 21 17:04:27 SUN kernel: sd 8:0:0:0: [sdi] 976773168 512-byte logical blocks: (500 GB/466 GiB)
Feb 21 17:04:27 SUN kernel: sd 8:0:0:0: [sdi] Write Protect is off
Feb 21 17:04:27 SUN kernel: sd 8:0:0:0: [sdi] Mode Sense: 7f 00 10 08
Feb 21 17:04:27 SUN kernel: sd 8:0:0:0: [sdi] Write cache: enabled, read cache: enabled, supports DPO and FUA
Feb 21 17:04:27 SUN kernel: sdi: sdi1
Feb 21 17:04:27 SUN kernel: sd 8:0:0:0: [sdi] Attached SCSI disk
Feb 21 17:04:38 SUN emhttpd: Samsung_SSD_860_EVO_500GB_S3YZNB0K206049P (sdi) 512 976773168
Feb 21 17:04:51 SUN unassigned.devices: Adding disk '/dev/sdi1'...
Feb 21 17:04:51 SUN unassigned.devices: Mount drive command: /sbin/mount -t xfs -o rw,noatime,nodiratime,discard '/dev/sdi1' '/mnt/disks/unassigned'
Feb 21 17:04:51 SUN kernel: XFS (sdi1): Mounting V5 Filesystem
Feb 21 17:04:51 SUN kernel: XFS (sdi1): Ending clean mount
Feb 21 17:04:51 SUN unassigned.devices: Successfully mounted '/dev/sdi1' on '/mnt/disks/unassigned'.
Feb 22 00:00:11 SUN kernel: sd 8:0:0:0: [sdi] tag#3152 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Feb 22 00:00:11 SUN kernel: sd 8:0:0:0: [sdi] tag#3152 Sense Key : 0x5 [current]
Feb 22 00:00:11 SUN kernel: sd 8:0:0:0: [sdi] tag#3152 ASC=0x21 ASCQ=0x0
Feb 22 00:00:11 SUN kernel: sd 8:0:0:0: [sdi] tag#3152 CDB: opcode=0x42 42 00 00 00 00 00 00 00 18 00
Feb 22 00:00:11 SUN kernel: print_req_error: critical target error, dev sdi, sector 975849578
Feb 23 00:00:09 SUN kernel: sd 8:0:0:0: [sdi] tag#2134 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Feb 23 00:00:09 SUN kernel: sd 8:0:0:0: [sdi] tag#2134 Sense Key : 0x5 [current]
Feb 23 00:00:09 SUN kernel: sd 8:0:0:0: [sdi] tag#2134 ASC=0x21 ASCQ=0x0
Feb 23 00:00:09 SUN kernel: sd 8:0:0:0: [sdi] tag#2134 CDB: opcode=0x42 42 00 00 00 00 00 00 00 18 00
Feb 23 00:00:09 SUN kernel: print_req_error: critical target error, dev sdi, sector 975849578
Feb 24 00:00:09 SUN kernel: sd 8:0:0:0: [sdi] tag#1663 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Feb 24 00:00:09 SUN kernel: sd 8:0:0:0: [sdi] tag#1663 Sense Key : 0x5 [current]
Feb 24 00:00:09 SUN kernel: sd 8:0:0:0: [sdi] tag#1663 ASC=0x21 ASCQ=0x0
Feb 24 00:00:09 SUN kernel: sd 8:0:0:0: [sdi] tag#1663 CDB: opcode=0x42 42 00 00 00 00 00 00 00 18 00
Feb 24 00:00:09 SUN kernel: print_req_error: critical target error, dev sdi, sector 975849578
Feb 25 00:00:11 SUN kernel: sd 8:0:0:0: [sdi] tag#3277 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Feb 25 00:00:11 SUN kernel: sd 8:0:0:0: [sdi] tag#3277 Sense Key : 0x5 [current]
Feb 25 00:00:11 SUN kernel: sd 8:0:0:0: [sdi] tag#3277 ASC=0x21 ASCQ=0x0
Feb 25 00:00:11 SUN kernel: sd 8:0:0:0: [sdi] tag#3277 CDB: opcode=0x42 42 00 00 00 00 00 00 00 18 00
Feb 25 00:00:11 SUN kernel: print_req_error: critical target error, dev sdi, sector 975849578

Squid · February 25, 2020

9 minutes ago, opentoe said:

I don't use the cache drive as a "cache" drive. I've set all my drives NOT to use it. Unfortunately there is no DISABLED option in the mover settings. I attached my scheduler page and my notification page.

If no shares are set to be able to move to or from the cache drive, then effectively it is disabled. But, the mover tuning plugin does have an option to be able to explicitly disable mover from ever running, regardless of the share settings.

opentoe · February 25, 2020

Then my mover should be disabled since I don't use it to move anything.

I think I should be more concerned with that target error on that unassigned SSD. I thought running an extended test would present the button to view the results, but it does not.

Squid · February 25, 2020

display the smart report. Dont use UD for disks, so not sure if there's a button for that or not.

opentoe · February 25, 2020

22 minutes ago, Squid said:

display the smart report. Dont use UD for disks, so not sure if there's a button for that or not.

How do I display the extended test results if there is no button to view them?

Squid · February 26, 2020

Is there a button to display the smart report / attributes somewhere maybe click on the disk?

trurl · February 26, 2020

49 minutes ago, Squid said:

Is there a button to display the smart report / attributes somewhere maybe click on the disk?

Yes, click on the disk to get to its page and the button to Show the test history is right there, same page with the Start test buttons.

opentoe · February 26, 2020

Ok, here is my whole drive page for the drive SDI. Which button would I click on to see the results?

trurl · February 26, 2020

15 hours ago, trurl said:

the button to Show the test history is right there

12 hours ago, opentoe said:

Which button would I click on

The SHOW button next to the text "SMART self-test history"

opentoe · February 26, 2020

I clicked on all the buttons that had SHOW in it and every line and log stated

COMPLETED WITHOUT ERROR

I'm just a little confused, since I kept getting that error from my first post on this same drive. If nothing is wrong with this SSD drive, why the errors in the log? I guess that's what is confusing to me. I think I'm expecting to see errors but I do not.

This is the error I get all the time on this SDI drive that has no errors with the extended test.

Feb 26 00:00:09 SUN kernel: sd 8:0:0:0: [sdi] tag#146 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Feb 26 00:00:09 SUN kernel: sd 8:0:0:0: [sdi] tag#146 Sense Key : 0x5 [current] 
Feb 26 00:00:09 SUN kernel: sd 8:0:0:0: [sdi] tag#146 ASC=0x21 ASCQ=0x0 
Feb 26 00:00:09 SUN kernel: sd 8:0:0:0: [sdi] tag#146 CDB: opcode=0x42 42 00 00 00 00 00 00 00 18 00
Feb 26 00:00:09 SUN kernel: print_req_error: critical target error, dev sdi, sector 975849578
Feb 26 00:00:09 SUN root: /etc/libvirt: 921 MiB (965677056 bytes) trimmed on /dev/loop3
Feb 26 00:00:09 SUN root: /var/lib/docker: 14.4 GiB (15433830400 bytes) trimmed on /dev/loop2

Then this also comes up, trying to connect to Google's SMTP even when I have no email address or anything setup for notifications.

Feb 26 00:00:09 SUN sSMTP[26838]: Authorization failed (535 5.7.8  https://support.google.com/mail/?p=BadCredentials o10sm480577qtp.38 - gsmtp)
Feb 26 03:40:16 SUN crond[2002]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null

My mover should be disabled, since I setup ALL my drives not to use a cache drive. It should not be trying to reach out to anywhere. I've posted all the screen shots on what my mover page looks like and notifications page. Nothing in there indicates that the mover is active or disabled. I wish there was a drop down for the mover to be disabled.

Edited February 26, 2020 by opentoe

JorgeB · February 26, 2020

Is the SSD being trimmed at midnight? Trim won't work on that LSI and can cause those errors, which in that case are not a problem, besides the SSD not being trimmed.

opentoe · February 26, 2020

TRIM was configured at defaults which was DAILY, so I disabled it since if it isn't going to work anyway. I'll do a reboot and see if those errors still come around. I know I'll still see unraid try to connect to Gmails SMTP server. Can't seem to stop that.

opentoe · February 26, 2020

Ok, I just disabled TRIM and rebooted. Server been up only 15 minutes but no SDI messages yet. I'll need to wait a little bit when some notifications comes through to see if the system tries to connect to Gmails SMTP server. I have selected ALL notifications for browser and unchecked everything else, so I'm not sure how those Gmail connections are even in the log.

Edited February 26, 2020 by opentoe

trurl · February 26, 2020

11 minutes ago, opentoe said:

I have selected ALL notifications for browser and unchecked everything else, so I'm not sure how those Gmail connections are even in the log.

Other things besides those on the Notifications page can send emails, such as scripts or plugins.

opentoe · February 26, 2020

5 minutes ago, trurl said:

Other things besides those on the Notifications page can send emails, such as scripts or plugins.

This is why I would like to get to the bottom of what the heck is trying to connect to Gmails servers. I guess the only way to find out is to configure it properly and send whatever it is trying to send to my email address and see what the content is.

trurl · February 26, 2020

Most plugins I assume would be sending a notice, warning, or alert notification, so those should be covered by your settings. And any scripts that call notify would have to choose one of those types also.

Do you have any scripts that call ssmtp directly?

opentoe · February 26, 2020

9 minutes ago, trurl said:

Most plugins I assume would be sending a notice, warning, or alert notification, so those should be covered by your settings. And any scripts that call notify would have to choose one of those types also.

Do you have any scripts that call ssmtp directly?

Not that I know of. I just have a few plugins installed, one docker going all the time and that's about it. I tried configuring the Gmail SMTP setup and cannot get it to authorize. It is a very easy setup.

Server Address: smtp.gmail.com

Username: Your Gmail Address (e.g. [email protected])

Password: Your Gmail Password

Port Number: 587 (With TLS)

Alternative Port Number: 465 (With SSL)

trurl · February 26, 2020

2 minutes ago, opentoe said:

I tried configuring the Gmail SMTP

You probably need to setup an app password in gmail for your server to use.

Squid · February 26, 2020

Now that there's more info, this is cron attempting to email because the cronjob failed (mover returned error 1)

Mover even if all shares are disabled to move always runs (but, there has to be some share that is eligible to move, otherwise it wouldn't be attempting and failing). Either way, have you remove all email addresses in the smpt settings if you don't want to use it.

Otherwise, you need to set up gmail to accept connections from less secure clients (or whatever it's called in gmail settings)

opentoe · February 26, 2020

12 minutes ago, Squid said:

Now that there's more info, this is cron attempting to email because the cronjob failed (mover returned error 1)

Mover even if all shares are disabled to move always runs (but, there has to be some share that is eligible to move, otherwise it wouldn't be attempting and failing). Either way, have you remove all email addresses in the smpt settings if you don't want to use it.

Otherwise, you need to set up gmail to accept connections from less secure clients (or whatever it's called in gmail settings)

Only shares APPDATA and DOMAINS are selected to ONLY use cache drive but right next to the setting where it says NO there is a comment, MOVER TAKES NO ACTION.

But since I changed that TRIM setting to disabled I don't think I have seen any attempts just yet. I'll come back to it in a couple hours to check.

Alrighty, did get the Gmail SMTP going...so I will leave that on and find out what this Gmail mystery is.

Edited February 26, 2020 by opentoe

Dissones4U · February 26, 2020

1 hour ago, Squid said:

Either way, have you remove all email addresses in the smpt settings if you don't want to use it

This may not be possible, I've tried for the same reason and unRaid insists that you have a sending address in there...

A few errors in my log...

Recommended Posts

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Join the conversation