LinuxQuestions.org - Shouldn't smartctl -t long /dev/sdx make the drive make noise?

- Linux - Hardware (https://www.linuxquestions.org/questions/linux-hardware-18/)

- - Shouldn't smartctl -t long /dev/sdx make the drive make noise? (https://www.linuxquestions.org/questions/linux-hardware-18/shouldnt-smartctl-t-long-dev-sdx-make-the-drive-make-noise-4175644421/)

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?

are you saying this happens on both drives?

how close did you put your ears? hands, to feel the vibrations?

the long tests require a bit of reading to understand.
they can be queried while running.

some tests probably only read info from some internal SMART chip.

http://dt.iki.fi/hard-drive-and-fs-health-checks

and we would evtl. need to see more output.

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.

Quote:

Originally Posted by ondoho (Post 5938034)

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?

Why don't you post the results of the following command in CODE tags;

Code:

sudo smartctl -x /dev/sda

Oh yea it's actually sdb (my mistake that the first time at the top of my post I said sda): Here's the results for sdb, the one I was checking:

Code:

$ sudo smartctl -x /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 03:52:10 2018 EST

SMART support is: Available - device has SMART capability.

SMART support is: Enabled

AAM feature is:  Unavailable

APM level is:    128 (minimum power consumption without standby)

Rd look-ahead is: Enabled

Write cache is:  Enabled

ATA Security is:  Disabled, NOT FROZEN [SEC1]

Wt Cache Reorder: 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:      ( 249) Self-test routine in progress...

                                        90% of test remaining.

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          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE

  1 Raw_Read_Error_Rate    PO-R--  100  100  062    -    0

  2 Throughput_Performance  P-S---  198  198  040    -    98

  3 Spin_Up_Time            POS---  235  235  033    -    1

  4 Start_Stop_Count        -O--C-  100  100  000    -    63

  5 Reallocated_Sector_Ct  PO--CK  100  100  005    -    0

  7 Seek_Error_Rate        PO-R--  100  100  067    -    0

  8 Seek_Time_Performance  P-S---  154  154  040    -    32

  9 Power_On_Hours          -O--C-  087  087  000    -    5712

 10 Spin_Retry_Count        PO--C-  100  100  060    -    0

 12 Power_Cycle_Count      -O--CK  100  100  000    -    54

191 G-Sense_Error_Rate      -O-R--  100  100  000    -    0

192 Power-Off_Retract_Count -O--CK  100  100  000    -    12

193 Load_Cycle_Count        -O--C-  097  097  000    -    37759

194 Temperature_Celsius    -O----  193  193  000    -    31 (Min/Max 21/47)

196 Reallocated_Event_Count -O--CK  100  100  000    -    0

197 Current_Pending_Sector  -O---K  100  100  000    -    0

198 Offline_Uncorrectable  ---R--  100  100  000    -    0

199 UDMA_CRC_Error_Count    -O-R--  200  200  000    -    0

223 Load_Retry_Count        -O-R--  100  100  000    -    0

                            ||||||_ K auto-keep

                            |||||__ C event count

                            ||||___ R error rate

                            |||____ S speed/performance

                            ||_____ O updated online

                            |______ P prefailure warning



General Purpose Log Directory Version 1

SMART          Log Directory Version 1 [multi-sector log support]

Address    Access  R/W  Size  Description

0x00      GPL,SL  R/O      1  Log Directory

0x01          SL  R/O      1  Summary SMART error log

0x02          SL  R/O      1  Comprehensive SMART error log

0x03      GPL    R/O      1  Ext. Comprehensive SMART error log

0x06          SL  R/O      1  SMART self-test log

0x07      GPL    R/O      1  Extended self-test log

0x09          SL  R/W      1  Selective self-test log

0x10      GPL    R/O      1  SATA NCQ Queued Error log

0x11      GPL    R/O      1  SATA Phy Event Counters log

0x80-0x9f  GPL,SL  R/W    16  Host vendor specific log

0xe0      GPL,SL  R/W      1  SCT Command/Status

0xe1      GPL,SL  R/W      1  SCT Data Transfer



SMART Extended Comprehensive Error Log Version: 1 (1 sectors)

No Errors Logged



SMART Extended Self-test Log Version: 1 (1 sectors)

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.)

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.

Quote:

Originally Posted by jsbjsb001 (Post 5938058)

Right but it's never run a long test. That's not the output from a long test.

Quote:

Originally Posted by Rotwang2 (Post 5938060)

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.)

Quote:

Originally Posted by jsbjsb001 (Post 5938061)

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?

Quote:

Originally Posted by Rotwang2 (Post 5938066)

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.

Quote:

Originally Posted by jsbjsb001 (Post 5938069)

Yes.

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?

Quote:

Originally Posted by Rotwang2 (Post 5938066)

IME smartctl -a is multiply broken, unless you wait as long as smartctl -t long directs before using smartctl -a.

Quote:

Originally Posted by Rotwang2 (Post 5938072)

...
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.