Shouldn't smartctl -t long /dev/sdx make the drive make noise?
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
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.
Yes. No, it didn't make sounds, nor did the LED light up.
Oh wow that's hugely useful, thanks. I have no idea why it would take so much time without even consulting the drive at all, but whatever, if you say that's been your experience than I believe you, thanks jsbjsb001.
Is there any way to see how far along it's gone while it's running? Or is there very act of checking on its progress going to stop the test. (Like the Heisenberg principle.)
Distribution: Currently: OpenMandriva. Previously: openSUSE, PCLinuxOS, CentOS, among others over the years.
Posts: 3,881
Rep:
Quote:
Originally Posted by Rotwang2
Oh wow that's hugely useful, thanks. I have no idea why it would take so much time without even consulting the drive at all, but whatever, if you say that's been your experience than I believe you, thanks jsbjsb001.
But it DOES do something - just because you can't hear it or see it, it doesn't mean it's "doing nothing".
Quote:
Is there any way to see how far along it's gone while it's running? Or is there very act of checking on its progress going to stop the test. (Like the Heisenberg principle.)
If there is - I'm not sure how you would see that.
For the test, smartctl doesn't do anything beyond telling the drive, "Run your long test." Since there is no further external activity, the LED remains dark. Internally, the surface is typically tested sequentially from beginning to end. There are no long seeks to make any noise.
After starting the test, you should wait the suggested time and then run "smartctl -l selftest" or "smartctl -a" to see the result.
Ok I ran it last night, that was 6 hours ago (it said it would take 87 minutes so I figure 6 hours is enough haha). Here are the results:
Code:
$ sudo smartctl -a /dev/sdb
smartctl 6.5 2016-05-07 r4318 [i686-linux-4.14.5-300.fc27.i686+PAE] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Hitachi/HGST Travelstar Z7K500
Device Model: HGST HTS725050A7E630
Serial Number: RCE55ACE3U5ADM
LU WWN Device Id: 5 000cca 85ef5b7d1
Firmware Version: GS2OA3E0
User Capacity: 500,107,862,016 bytes [500 GB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 7200 rpm
Form Factor: 2.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS T13/1699-D revision 6
SATA Version is: SATA 2.6, 6.0 Gb/s (current: 1.5 Gb/s)
Local Time is: Mon Dec 17 12:11:15 2018 EST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x02) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 45) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 87) minutes.
SCT capabilities: (0x003d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b 100 100 062 Pre-fail Always - 0
2 Throughput_Performance 0x0005 198 198 040 Pre-fail Offline - 98
3 Spin_Up_Time 0x0007 235 235 033 Pre-fail Always - 1
4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 63
5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0
7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 154 154 040 Pre-fail Offline - 32
9 Power_On_Hours 0x0012 087 087 000 Old_age Always - 5714
10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 54
191 G-Sense_Error_Rate 0x000a 100 100 000 Old_age Always - 0
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 12
193 Load_Cycle_Count 0x0012 097 097 000 Old_age Always - 37760
194 Temperature_Celsius 0x0002 230 230 000 Old_age Always - 26 (Min/Max 21/47)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0
197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 0
223 Load_Retry_Count 0x000a 100 100 000 Old_age Always - 0
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed without error 00% 5714 -
# 2 Extended offline Aborted by host 80% 5712 -
# 3 Extended offline Aborted by host 90% 5712 -
# 4 Extended offline Aborted by host 60% 5712 -
# 5 Extended offline Completed without error 00% 5321 -
# 6 Extended offline Aborted by host 90% 5319 -
# 7 Extended offline Aborted by host 90% 5319 -
# 8 Extended offline Aborted by host 90% 5319 -
# 9 Extended offline Aborted by host 80% 5319 -
#10 Extended offline Completed without error 00% 5056 -
#11 Extended offline Completed without error 00% 5054 -
#12 Extended offline Completed without error 00% 51 -
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
Why is everything stuck at 90% and/or "Not_testing"? The last thing I did before going to sleep was:
Code:
$ sudo smartctl -t long /dev/sdb
smartctl 6.5 2016-05-07 r4318 [i686-linux-4.14.5-300.fc27.i686+PAE] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION ===
Sending command: "Execute SMART Extended self-test routine immediately in off-line mode".
Drive command "Execute SMART Extended self-test routine immediately in off-line mode" successful.
Testing has begun.
Please wait 87 minutes for test to complete.
Test will complete after Mon Dec 17 06:12:28 2018
All those "Aborted by host" with 90% remaining lines are the times when you did something to abort the test without waiting for it to complete. The most recent run, line 1, completed with no error.
All those "Aborted by host" with 90% remaining lines are the times when you did something to abort the test without waiting for it to complete. The most recent run, line 1, completed with no error.
using & understanding smartctl requires more than a little reading of documentation.
preferably also some tutorials from the wild web.
if OP had done ANY of that 90% of their questions would not have been asked.
it saddens me.
using & understanding smartctl requires more than a little reading of documentation.
preferably also some tutorials from the wild web.
if OP had done ANY of that 90% of their questions would not have been asked.
it saddens me.
Oh you gotta be kidding me. I totally did. These two I found to be the most useful:
At no time in anything I could find did it say that the drive would remain silent.
Go find me a tutorial that mentioned that, ondoho. Good luck.
Your myopicy "saddens me" too, ondoho
if you'd even read the smartctl man page, or even clicked on the link i provided and read that, you wouldn't have asked some of the questions you asked subsequently.
that's proof enough for me.
Distribution: Currently: OpenMandriva. Previously: openSUSE, PCLinuxOS, CentOS, among others over the years.
Posts: 3,881
Rep:
Rotwang2, I would have to concur with the other guys that have replied to this thread - your own output is clearly telling you that the drive has PASSED the test. Just run "sudo smartctl -a /dev/sdX" (replace "sdX" with the actual node) from time to time, and you should be fine.
Just a quick note: SMART is built into the drive, therefore explains why you are not seeing any activity - because there is NO data being read or written to or from the drive to begin with. I was going to say that before, but you seemed confused enough and rknichols is our "resident expert" when it comes to drive related matters. So if he says your drive is good, then it's good - so stop worrying about it. And saying things like "Your myopicy "saddens me" too, ondoho" doesn't help your cause - just say'n.
if you'd even read the smartctl man page, or even clicked on the link i provided and read that, you wouldn't have asked some of the questions you asked subsequently.
that's proof enough for me.
Obviously I read the man page that's how I even knew the the CLI commands.
Yea I clicked your link- where does it say that there isn't going to be noise?
Besides that, you're backpedaling from your statement here:
Quote:
Originally Posted by ondoho
preferably also some tutorials from the wild web.
if OP had done ANY of that 90% of their questions would not have been asked.
Now your categorizing it down to just your link instead of the entire web and all of its tutorials and docs, to try and save face.
Rotwang2, I would have to concur with the other guys that have replied to this thread - your own output is clearly telling you that the drive has PASSED the test. Just run "sudo smartctl -a /dev/sdX" (replace "sdX" with the actual node) from time to time, and you should be fine.
Just a quick note: SMART is built into the drive, therefore explains why you are not seeing any activity - because there is NO data being read or written to or from the drive to begin with. I was going to say that before, but you seemed confused enough and rknichols is our "resident expert" when it comes to drive related matters. So if he says your drive is good, then it's good - so stop worrying about it. And saying things like "Your myopicy "saddens me" too, ondoho" doesn't help your cause - just say'n.
Um I was quoting him, re-using his "it saddens me" line (see above).
As for the "PASSED"- well, but- here's the thing though- when I was still in the process of understanding- I had noticed that when I check it too early with smartctl -a (as in like 2 minutes), it still says "passed" even though it didn't do the entire test. So that's what was confusing me, and thanks to (most of) the responders, I get it now.
I'm not worried about it all, I'm way past that, thanks. As I had said above, I get it now.
Distribution: Currently: OpenMandriva. Previously: openSUSE, PCLinuxOS, CentOS, among others over the years.
Posts: 3,881
Rep:
Well, can we leave it there then? Your questions have been answered, there's no need to continue insulting other members. I don't mean to be a smartass or rude to you, but let's stop being silly.
Well, can we leave it there then? Your questions have been answered, there's no need to continue insulting other members. I don't mean to be a smartass or rude to you, but let's stop being silly.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
