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.
Shouldn't smartctl -t long /dev/sdx make the drive make noise?
I run:
smartctl -t long /dev/sda
Shouldn't the drive start making noise? I've tried this on two drives and in both cases I've tried waiting as long as 20 minutes and they don't make any noise (as they would if copying a file) and there's no activity on the led.
Both drives are fairly new and hand have SMART capability. For the 500g drive I ran:
Code:
$ sudo smartctl -i /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 00:54:07 2018 EST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
The other drive is newer- from about 2014.
I swear there's something I'm missing here.
I'm doing:
sudo smartctl -t long /dev/sdb
Is that wrong? (oh and no, this not the boot drive).
The same thing happens on a different PC with a 1TB drive.
I really must be getting the line commands wrong right?
Distribution: Currently: OpenMandriva. Previously: openSUSE, PCLinuxOS, CentOS, among others over the years.
Posts: 3,881
Rep:
In answer to what I think is your question; no, not necessarily. If you did hear a "clicking sound", then that could actually mean drive failure (and in that case likely would mean that). But that said, I'm not seeing anything that would indicate drive failure.
I had a drive fail on me - smartctl still reported the drive as PASSED. Because it hadn't actually breached any of the thresholds, but files did disappear from it, followed by filesystem, and then partition collapse, as well as a "clicking sound" right when it did actually fail.
If both drives are new; I would not expect they would be failing yet. I would say the chances of that would be quite small at this stage.
So no, I don't see any reason why you are "missing anything" IMHO.
Yes, both drives. As for the sound- well when I would copy files from they, they'd be making the usual crunching noises that drives make; and perhaps most importantly the activity light would be flickering. smartctl isn't causing either. So what is it doing, exactly? If it's the short test I can see why it would just be a question with an immediate answer. But the long test? It says it'll take like 90 minutes, so isn't it supposed to be, well.... doing something?
Btw- the way I'm testing the other drive; the 1TB drive- it's on a different PC (the one I'm on right now actually), and the way I'm checking is that a few hours ago I burned an ALT Linux Rescue iso and booted into that. (Because I wanted to make everything as clean as possible; occam's razor.)
Distribution: Currently: OpenMandriva. Previously: openSUSE, PCLinuxOS, CentOS, among others over the years.
Posts: 3,881
Rep:
I think you might be worrying for nothing. Other than the "Seek_Time_Performance" SMART attribute, I don't see anything of concern in your output. And even in terms of that, it hasn't breached the threshold yet. But I would keep an eye on it though.
I think you might be worrying for nothing. Other than the "Seek_Time_Performance" SMART attribute, I don't see anything of concern in your output. And even in terms of that, it hasn't breached the threshold yet. But I would keep an eye on it though.
Right but it's never run a long test. That's not the output from a long test.
You can run the following command to get a little more detail on the SMART "attributes";
Code:
sudo smartctl -a /dev/sdb
(run the long test before you run that command, and wait for it to finish - it should tell you how long it will take.)
Wait I don't get it- I should run the -a command after the long test finishes? I don't follow you. Do you mean I should run the long test and then run the -a while the long test is going on so that I can see how long it'll take to finish?
Distribution: Currently: OpenMandriva. Previously: openSUSE, PCLinuxOS, CentOS, among others over the years.
Posts: 3,881
Rep:
Quote:
Originally Posted by Rotwang2
Wait I don't get it- I should run the -a command after the long test finishes?
Yes.
Quote:
I don't follow you. Do you mean I should run the long test and then run the -a while the long test is going on so that I can see how long it'll take to finish?
No. When you tell it to run a long test, it should tell you how long the test will take. It vary's depending on the drive.
No. When you tell it to run a long test, it should tell you how long the test will take. It vary's depending on the drive.
Oh ok I think I see what you mean. I don't understand why I should bother running the long test when it doesn't make the drive do anything.
Well here's a question for all of you on this thread (and thanks for your help btw)- Have any of you run a long test on a PC sitting next to you? (As opposed to a server somewhere). Did the drive do anything? Did the activity led light up?
Wait I don't get it- I should run the -a command after the long test finishes? I don't follow you. Do you mean I should run the long test and then run the -a while the long test is going on so that I can see how long it'll take to finish?
IME smartctl -a is multiply broken, unless you wait as long as smartctl -t long directs before using smartctl -a.
Distribution: Currently: OpenMandriva. Previously: openSUSE, PCLinuxOS, CentOS, among others over the years.
Posts: 3,881
Rep:
Quote:
Originally Posted by Rotwang2
...
Well here's a question for all of you on this thread (and thanks for your help btw)- Have any of you run a long test on a PC sitting next to you? (As opposed to a server somewhere). Did the drive do anything? Did the activity led light up?
Yes. No, it didn't make sounds, nor did the LED light up.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.