Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have tried to Google and research, but trying to understand the meaning of this error. I believe this is disk related, but what can you tell from the "sd 2:0:17:0". Does this tell you what drive is having issues?
Distribution: Currently: OpenMandriva. Previously: openSUSE, PCLinuxOS, CentOS, among others over the years.
Posts: 3,881
Rep:
Quote:
Originally Posted by NewbODA
I have tried to Google and research, but trying to understand the meaning of this error. I believe this is disk related, but what can you tell from the "sd 2:0:17:0". Does this tell you what drive is having issues?
From the output you have provided, no, it does not mean you are necessarily having any drive issues. You have to remember that the Linux kernel is very, very verbose and not just with drives either.
If your output looks similar to the following, this is quite normal:
badblocks -v /dev/sdap
Checking blocks 0 to 390711384
Checking for bad blocks (read-only test): done
Pass completed, 0 bad blocks found.
smartctl 5.42 2011-10-20 r3458 [x86_64-linux-2.6.39-400.245.1.el5uek] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net
Vendor: HGST
Product: HSCAC2DA4SUN400G
Revision: A122
User Capacity: 400,088,457,216 bytes [400 GB]
Logical block size: 512 bytes
Logical Unit id: 0x5000cca04e0dfb84
Serial number: 001507JQPBZA 0QV7PBZA
Device type: disk
Transport protocol: SAS
Local Time is: Wed Oct 25 09:42:33 2017 EDT
Device supports SMART and is Enabled
Temperature Warning Enabled
SMART Health Status: OK
SS Media used endurance indicator: 0%
Current Drive Temperature: 28 C
Drive Trip Temperature: 70 C
Manufactured in week 07 of year 2015
Specified cycle count over device lifetime: 0
Accumulated start-stop cycles: 0
Specified load-unload count over device lifetime: 0
Accumulated load-unload cycles: 0
defect list format 6 unknown
Elements in grown defect list: 0
Vendor (Seagate) cache information
Blocks sent to initiator = 9977776182394880
i don't know what this message means, but as i said, it's not an error, not even a warning.
every 6 minutes seems fine, your logs shouldn't fill up faster than your log rotation software can handle, but of course you can check filesizes in /var/log yourself.
my complete /var/log is just 66M.
a single file can grow to a few megabyte in size.
these are of course very rough estimates and not meant to be taken literally or even seriously.
apart from that, logrotate or systemd should take care of deleting old logs.
You could scan the kernel for what generates that message. There's probably a flag somewhere to turn down the logging level / verbosity if they annoy you that much. /proc/sys/dev/scsi/logging_level ???
so scsi_debug and scsi_mod kernel modules. Further inspection of the sources could help you understand what is being reported. Although 6-ish minutes seems like the spindown time for spinning rust that is inactive. Just a guess though, you might be able to umount whatever part of them are mounted to avoid it spinning back up. Or just unplug them if you're not actively using them to avoid the messages (and save power).
I second ondoho on this. The file is "messages" not "errors" for good reason. It is full of kernel, application, listener, shell, and process messages that might be very handy IF something goes wrong. Unless they contain the ERR string or WARNING they are just messages and do not indicate (by themselves) a problem.
I would ignore them unless you get them in association with an error or warning.
Do smartctl and smartd run on a virtual machine guest OS?
Yes and no. Smartctl and smartd run on a virtual machine guest OS without problems. But this isn't very useful because the virtual disks do not support SMART. If a guest OS disk is configured as a raw disk, this only means that its sectors are mapped transparently to the underlying physical disk. This does not imply the ATA or SCSI pass-through access required to access the SMART info of the physical disk. Even the disk's identity is typically not exposed to the guest OS.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.