Linux - Hardware This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
 |
|
11-20-2020, 05:48 AM
|
#1
|
|
LQ Newbie
Registered: Nov 2020
Posts: 27
Rep: 
|
test SATA hard disk for errors
I tried test my SATA 2.5" hard disk for errors. Disk is in an external enclosure, attached to laptop via USB.
Debian 9 on my laptop and smartmontools installed. I did short test first:
Code:
Disk /dev/sdb: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xb45e11b8
Device Boot Start End Sectors Size Id Type
/dev/sdb1 2048 718847 716800 350M de Dell Utility
/dev/sdb2 718848 7010303 6291456 3G c W95 FAT32 (LBA)
/dev/sdb3 * 7010304 960389119 953378816 454.6G 83 Linux
/dev/sdb4 960391166 976771071 16379906 7.8G 5 Extended
/dev/sdb5 960391168 976771071 16379904 7.8G 82 Linux swap / Solaris
$ sudo smartctl -H /dev/sdb3
smartctl 6.6 2016-05-31 r4324 [i686-linux-4.9.0-14-686-pae] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK
$ sudo smartctl --info /dev/sdb
smartctl 6.6 2016-05-31 r4324 [i686-linux-4.9.0-14-686-pae] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Toshiba 2.5" HDD MQ01ABF...
Device Model: TOSHIBA MQ01ABF050
Serial Number: Y5MTTNZWT
LU WWN Device Id: 5 000039 6a1e08598
Firmware Version: AM0P1D
User Capacity: 500,107,862,016 bytes [500 GB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5400 rpm
Form Factor: 2.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS (minor revision not indicated)
SATA Version is: SATA 3.0, 6.0 Gb/s (current: 1.5 Gb/s)
Local Time is: Fri Nov 20 02:41:41 2020 EET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
$ sudo smartctl --capabilities /dev/sdb
smartctl 6.6 2016-05-31 r4324 [i686-linux-4.9.0-14-686-pae] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF READ SMART DATA SECTION ===
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
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: ( 120) 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: ( 123) minutes.
SCT capabilities: (0x003d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
$ sudo smartctl --test=short /dev/sdb
smartctl 6.6 2016-05-31 r4324 [i686-linux-4.9.0-14-686-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 Short self-test routine immediately in off-line mode".
Drive command "Execute SMART Short self-test routine immediately in off-line mode" successful.
Testing has begun.
Please wait 2 minutes for test to complete.
Test will complete after Fri Nov 20 02:50:00 2020
Use smartctl -X to abort test.
$ sudo smartctl --capabilities /dev/sdb
smartctl 6.6 2016-05-31 r4324 [i686-linux-4.9.0-14-686-pae] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF READ SMART DATA SECTION ===
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
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: ( 120) 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: ( 123) minutes.
SCT capabilities: (0x003d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
Last edited by kosmo333; 11-20-2020 at 05:49 AM.
|
|
|
|
|
11-20-2020, 06:51 AM
|
#2
|
|
LQ Guru
Registered: Jan 2006
Location: Ireland
Distribution: Slackware, Slarm64 & Android
Posts: 17,422
|
And your question is??…
|
|
|
1 members found this post helpful.
|
|
11-20-2020, 07:43 AM
|
#3
|
|
Moderator
Registered: Aug 2002
Posts: 26,640
|
Quote:
=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK
|
This shows the overall health of the drive as OK. If you want to see the all of the details look at the output of the command:
Last edited by michaelk; 11-20-2020 at 07:45 AM.
|
|
|
|
|
11-20-2020, 10:27 AM
|
#4
|
|
Member
Registered: Jun 2007
Distribution: Knoppix, antiX
Posts: 252
Rep: 
|
Did you detect anything that makes you sceptic about drive's health or just as a routine check-up?
|
|
|
|
|
11-20-2020, 12:06 PM
|
#5
|
|
LQ Newbie
Registered: Nov 2020
Posts: 27
Original Poster
Rep:
|
Quote:
Originally Posted by masterclassic
Did you detect anything that makes you sceptic about drive's health or just as a routine check-up?
|
I pulled it out because there were I/O errors, and later there is no output on display at all (after I run the fsck manually). So I think the disk is already damaged or close to failure.
Output after I did long test:
Code:
$ sudo smartctl -a /dev/sdb
[sudo] password for alexander:
smartctl 6.6 2016-05-31 r4324 [i686-linux-4.9.0-14-686-pae] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Toshiba 2.5" HDD MQ01ABF...
Device Model: TOSHIBA MQ01ABF050
Serial Number: Y5MTTNZWT
LU WWN Device Id: 5 000039 6a1e08598
Firmware Version: AM0P1D
User Capacity: 500,107,862,016 bytes [500 GB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5400 rpm
Form Factor: 2.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS (minor revision not indicated)
SATA Version is: SATA 3.0, 6.0 Gb/s (current: 1.5 Gb/s)
Local Time is: Fri Nov 20 06:14:29 2020 EET
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: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 112) The previous self-test completed having
the read element of the test failed.
Total time to complete Offline
data collection: ( 120) 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: ( 123) 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: 128
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 050 Pre-fail Always - 0
3 Spin_Up_Time 0x0027 100 100 001 Pre-fail Always - 1352
5 Reallocated_Sector_Ct 0x0033 100 100 050 Pre-fail Always - 0
9 Power_On_Hours 0x0032 078 078 000 Old_age Always - 8931
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 3716
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 966
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 1
193 Load_Cycle_Count 0x0032 098 098 000 Old_age Always - 23475
194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 28 (Min/Max 10/43)
199 UDMA_CRC_Error_Count 0x0032 100 100 000 Old_age Always - 57415753
200 Multi_Zone_Error_Rate 0x0032 100 100 000 Old_age Always - 218838054
240 Head_Flying_Hours 0x0032 079 079 000 Old_age Always - 8678
241 Total_LBAs_Written 0x0032 100 100 000 Old_age Always - 11510038086
242 Total_LBAs_Read 0x0032 100 100 000 Old_age Always - 9973049304
254 Free_Fall_Sensor 0x0032 100 100 000 Old_age Always - 0
SMART Error Log Version: 1
ATA Error Count: 243 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 243 occurred at disk power-on lifetime: 8927 hours (371 days + 23 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 48 c0 fe 2a ed Error: UNC 72 sectors at LBA = 0x0d2afec0 = 220921536
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 78 90 fe 2a e0 00 02:41:56.760 READ DMA EXT
25 00 80 88 fe 2a e0 00 02:41:52.974 READ DMA EXT
25 00 08 80 fe 2a e0 00 02:41:52.973 READ DMA EXT
25 00 08 78 fe 2a e0 00 02:41:52.949 READ DMA EXT
e1 00 00 00 00 00 a0 00 02:41:52.949 IDLE IMMEDIATE
Error 242 occurred at disk power-on lifetime: 8927 hours (371 days + 23 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 48 c0 fe 2a ed Error: UNC 72 sectors at LBA = 0x0d2afec0 = 220921536
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 80 88 fe 2a e0 00 02:41:52.974 READ DMA EXT
25 00 08 80 fe 2a e0 00 02:41:52.973 READ DMA EXT
25 00 08 78 fe 2a e0 00 02:41:52.949 READ DMA EXT
e1 00 00 00 00 00 a0 00 02:41:52.949 IDLE IMMEDIATE
35 00 08 00 f8 6a e0 00 02:41:44.260 WRITE DMA EXT
Error 241 occurred at disk power-on lifetime: 8927 hours (371 days + 23 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 48 c0 fe 2a ed Error: UNC 72 sectors at LBA = 0x0d2afec0 = 220921536
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 88 80 fe 2a e0 00 02:41:40.449 READ DMA EXT
25 00 90 78 fe 2a e0 00 02:41:36.662 READ DMA EXT
25 00 08 70 fe 2a e0 00 02:41:36.661 READ DMA EXT
25 00 08 68 fe 2a e0 00 02:41:36.345 READ DMA EXT
35 00 08 00 f8 6a e0 00 02:41:36.344 WRITE DMA EXT
Error 240 occurred at disk power-on lifetime: 8927 hours (371 days + 23 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 48 c0 fe 2a ed Error: UNC 72 sectors at LBA = 0x0d2afec0 = 220921536
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 90 78 fe 2a e0 00 02:41:36.662 READ DMA EXT
25 00 08 70 fe 2a e0 00 02:41:36.661 READ DMA EXT
25 00 08 68 fe 2a e0 00 02:41:36.345 READ DMA EXT
35 00 08 00 f8 6a e0 00 02:41:36.344 WRITE DMA EXT
e1 00 00 00 00 00 a0 00 02:41:36.111 IDLE IMMEDIATE
Error 239 occurred at disk power-on lifetime: 8927 hours (371 days + 23 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 48 c0 fe 2a ed Error: UNC 72 sectors at LBA = 0x0d2afec0 = 220921536
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 98 70 fe 2a e0 00 02:41:16.959 READ DMA EXT
25 00 a0 68 fe 2a e0 00 02:41:13.172 READ DMA EXT
25 00 08 60 fe 2a e0 00 02:41:13.171 READ DMA EXT
25 00 08 58 fe 2a e0 00 02:41:12.884 READ DMA EXT
e1 00 00 00 00 00 a0 00 02:41:12.882 IDLE IMMEDIATE
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed: read failure 00% 8929 588461808
# 2 Short offline Completed without error 00% 8928 -
# 3 Short offline Completed without error 00% 8926 -
# 4 Short offline Completed without error 00% 8924 -
# 5 Short offline Completed without error 00% 6030 -
# 6 Short offline Completed without error 00% 549 -
# 7 Short offline Completed without error 00% 1 -
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.
|
|
|
|
|
11-20-2020, 08:47 PM
|
#6
|
|
Senior Member
Registered: Aug 2016
Posts: 3,345
|
With that output from smartctl I would certainly be skeptical of that disk. Repeated identical errors with the same sector count at the same LBA address shows a bad disk.
|
|
|
|
|
11-21-2020, 02:48 AM
|
#7
|
|
Member
Registered: Jun 2007
Distribution: Knoppix, antiX
Posts: 252
Rep:
|
Quote:
Originally Posted by computersavvy
With that output from smartctl I would certainly be skeptical of that disk. Repeated identical errors with the same sector count at the same LBA address shows a bad disk.
|
I think so, too. "I/O error" is usually associated with hardware problems. In case of random block numbers it could be from a bad cable or connector, or from a momentary power issue. Always at the same block, means that it is a problem at the specific drive position (a bad block or a group of bad blocks).
The "verdict" of the check is PASSED, however I'm sceptic about this persisting I/O error. Normally, hard drives contain a number of spare blocks where their firmware can remap bad blocks in a transparent manner. Bad blocks become more apparent when spare blocks are already used, and then the problem is perhaps already severe.
I would suggest to backup any important data from the drive, before going further with longer and more stressing tests. Anyway a backup is always a good idea, before any problem arises  After that, you could look for the extended SMART tests and/or manufacturer's test software. |
|
|
|
|
11-21-2020, 08:09 AM
|
#8
|
|
LQ Newbie
Registered: Nov 2020
Posts: 27
Original Poster
Rep:
|
I have no dedicated media storage to backup a full disk copy 500gb, just important data.
When I tried to backup one of the folders, there was an error, the part of the data was copied, but no all. I just repeated a few times, all the same. I checked the folder and found that it no longer shows any files at all.
I tried ls -al: the files are present there, but one docs marked as '??? ?? ????' as it doesn't recognized.
What's command to copy content of folder to media? Also, is there way to recover such broken data?
Last edited by kosmo333; 11-21-2020 at 08:11 AM.
|
|
|
|
|
11-21-2020, 09:00 AM
|
#9
|
|
Senior Member
Registered: Aug 2009
Distribution: Rocky Linux
Posts: 4,812
|
Strange that the drive does not report attribute 197, Current_Pending_Sector count. Those are the sectors that will cause an I/O error when read and will be reallocated to spare sectors the next time they are written. It's hard to know what shape the drive is in without that information. To date, no sectors have been reallocated (attribute 5, Reallocated_Sector_Ct).
To evaluate the drive's condition and recover as much data as possible, I suggest using ddrescue to make a copy of the drive. You could also use dd with "conv=noerror,sync", but it will be less aggressive about isolating errors. You will need another drive at least as large or space for a 500GB file. The output from ddrescue and its log file will show where the problem areas of the drive are. If it's just a few bad sectors (it happens, especially on external drives), simply rewriting those sectors will either repair them or cause them to be reallocated to spare sectors.
|
|
|
|
|
11-21-2020, 09:18 AM
|
#10
|
|
LQ Newbie
Registered: Nov 2020
Posts: 27
Original Poster
Rep:
|
Can we fully rely on smartctl utility to correctly evaluate the disk health when the disk is connected via USB as an external drive?
|
|
|
|
|
11-21-2020, 09:38 AM
|
#11
|
|
Senior Member
Registered: Aug 2009
Distribution: Rocky Linux
Posts: 4,812
|
Quote:
Originally Posted by kosmo333
Can we fully rely on smartctl utility to correctly evaluate the disk health when the disk is connected via USB as an external drive?
|
All of the "smarts" of SMART are in the disk drive itself. The commands needed to retrieve that report are either supported by the USB bridge chip or they are not. It's pretty hard for it to go "halfway". |
|
|
|
|
11-21-2020, 09:57 AM
|
#12
|
|
Senior Member
Registered: Jan 2007
Location: Wild West Wales, UK
Distribution: Linux Mint 22 MATE, Peppermint OS-Devuan, EndeavourOS
Posts: 4,316
|
kosmo333,
Install gsmartcontrol:
Code:
sudo apt install gsmartcontrol
Right click on drive > Perform test > Extended self-test (30 minutes).
If the output from #197 is not zero, your drive may have a problem |
|
|
|
|
11-22-2020, 11:27 AM
|
#13
|
|
LQ Newbie
Registered: Nov 2020
Posts: 27
Original Poster
Rep:
|
Quote:
Originally Posted by beachboy2
kosmo333,
Install gsmartcontrol:
Code:
sudo apt install gsmartcontrol
Right click on drive > Perform test > Extended self-test (30 minutes).
If the output from #197 is not zero, your drive may have a problem |
well, its not 30min, it show extended test 2h 3min. Same as I did from command line? |
|
|
|
|
11-22-2020, 02:29 PM
|
#14
|
|
LQ Newbie
Registered: Nov 2020
Posts: 27
Original Poster
Rep:
|
error log:
Code:
Complete error log:
SMART Error Log Version: 1
ATA Error Count: 272 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 272 occurred at disk power-on lifetime: 8932 hours (372 days + 4 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 08 c8 0c 6b ee Error: UNC 8 sectors at LBA = 0x0e6b0cc8 = 241896648
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 08 c8 0c 6b e0 00 01:30:25.296 READ DMA EXT
25 00 08 c8 0c 6b e0 00 01:30:21.530 READ DMA EXT
25 00 08 c8 0c 6b e0 00 01:30:17.763 READ DMA EXT
25 00 08 c8 0c 6b e0 00 01:30:14.067 READ DMA EXT
25 00 08 c0 0c 6b e0 00 01:30:14.067 READ DMA EXT
Error 271 occurred at disk power-on lifetime: 8932 hours (372 days + 4 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 08 c8 0c 6b ee Error: UNC 8 sectors at LBA = 0x0e6b0cc8 = 241896648
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 08 c8 0c 6b e0 00 01:30:21.530 READ DMA EXT
25 00 08 c8 0c 6b e0 00 01:30:17.763 READ DMA EXT
25 00 08 c8 0c 6b e0 00 01:30:14.067 READ DMA EXT
25 00 08 c0 0c 6b e0 00 01:30:14.067 READ DMA EXT
25 00 08 b8 0c 6b e0 00 01:30:14.066 READ DMA EXT
Error 270 occurred at disk power-on lifetime: 8932 hours (372 days + 4 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 08 c8 0c 6b ee Error: UNC 8 sectors at LBA = 0x0e6b0cc8 = 241896648
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 08 c8 0c 6b e0 00 01:30:17.763 READ DMA EXT
25 00 08 c8 0c 6b e0 00 01:30:14.067 READ DMA EXT
25 00 08 c0 0c 6b e0 00 01:30:14.067 READ DMA EXT
25 00 08 b8 0c 6b e0 00 01:30:14.066 READ DMA EXT
25 00 08 b0 0c 6b e0 00 01:30:14.065 READ DMA EXT
Error 269 occurred at disk power-on lifetime: 8932 hours (372 days + 4 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 08 c8 0c 6b ee Error: UNC 8 sectors at LBA = 0x0e6b0cc8 = 241896648
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 08 c8 0c 6b e0 00 01:30:14.067 READ DMA EXT
25 00 08 c0 0c 6b e0 00 01:30:14.067 READ DMA EXT
25 00 08 b8 0c 6b e0 00 01:30:14.066 READ DMA EXT
25 00 08 b0 0c 6b e0 00 01:30:14.065 READ DMA EXT
25 00 08 a8 0c 6b e0 00 01:30:14.065 READ DMA EXT
Error 268 occurred at disk power-on lifetime: 8932 hours (372 days + 4 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 08 98 fb 6a ee Error: UNC 8 sectors at LBA = 0x0e6afb98 = 241892248
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 08 98 fb 6a e0 00 01:30:06.407 READ DMA EXT
25 00 08 98 fb 6a e0 00 01:30:02.629 READ DMA EXT
25 00 08 98 fb 6a e0 00 01:29:58.851 READ DMA EXT
25 00 08 98 fb 6a e0 00 01:29:55.092 READ DMA EXT
25 00 08 90 fb 6a e0 00 01:29:55.092 READ DMA EXT
|
|
|
|
|
11-22-2020, 02:39 PM
|
#15
|
|
LQ Newbie
Registered: Nov 2020
Posts: 27
Original Poster
Rep:
|
error log:
Code:
smartctl 6.6 2016-05-31 r4324 [i686-linux-4.9.0-14-686-pae] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Toshiba 2.5" HDD MQ01ABF...
Device Model: TOSHIBA MQ01ABF050
Serial Number: Y5MTTNZWT
LU WWN Device Id: 5 000039 6a1e08598
Firmware Version: AM0P1D
User Capacity: 500,107,862,016 bytes [500 GB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5400 rpm
Form Factor: 2.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS (minor revision not indicated)
SATA Version is: SATA 3.0, 6.0 Gb/s (current: 1.5 Gb/s)
Local Time is: Sun Nov 22 22:35:26 2020 EET
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: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 112) The previous self-test completed having
the read element of the test failed.
Total time to complete Offline
data collection: ( 120) 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: ( 123) 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: 128
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 050 Pre-fail Always - 0
3 Spin_Up_Time 0x0027 100 100 001 Pre-fail Always - 1368
5 Reallocated_Sector_Ct 0x0033 100 100 050 Pre-fail Always - 0
9 Power_On_Hours 0x0032 078 078 000 Old_age Always - 8936
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 3720
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 966
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 1
193 Load_Cycle_Count 0x0032 098 098 000 Old_age Always - 23541
194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 28 (Min/Max 10/43)
199 UDMA_CRC_Error_Count 0x0032 100 100 000 Old_age Always - 57856308
200 Multi_Zone_Error_Rate 0x0032 100 100 000 Old_age Always - 218858163
240 Head_Flying_Hours 0x0032 079 079 000 Old_age Always - 8680
241 Total_LBAs_Written 0x0032 100 100 000 Old_age Always - 11510120217
242 Total_LBAs_Read 0x0032 100 100 000 Old_age Always - 9976919957
254 Free_Fall_Sensor 0x0032 100 100 000 Old_age Always - 0
SMART Error Log Version: 1
ATA Error Count: 272 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 272 occurred at disk power-on lifetime: 8932 hours (372 days + 4 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 08 c8 0c 6b ee Error: UNC 8 sectors at LBA = 0x0e6b0cc8 = 241896648
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 08 c8 0c 6b e0 00 01:30:25.296 READ DMA EXT
25 00 08 c8 0c 6b e0 00 01:30:21.530 READ DMA EXT
25 00 08 c8 0c 6b e0 00 01:30:17.763 READ DMA EXT
25 00 08 c8 0c 6b e0 00 01:30:14.067 READ DMA EXT
25 00 08 c0 0c 6b e0 00 01:30:14.067 READ DMA EXT
Error 271 occurred at disk power-on lifetime: 8932 hours (372 days + 4 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 08 c8 0c 6b ee Error: UNC 8 sectors at LBA = 0x0e6b0cc8 = 241896648
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 08 c8 0c 6b e0 00 01:30:21.530 READ DMA EXT
25 00 08 c8 0c 6b e0 00 01:30:17.763 READ DMA EXT
25 00 08 c8 0c 6b e0 00 01:30:14.067 READ DMA EXT
25 00 08 c0 0c 6b e0 00 01:30:14.067 READ DMA EXT
25 00 08 b8 0c 6b e0 00 01:30:14.066 READ DMA EXT
Error 270 occurred at disk power-on lifetime: 8932 hours (372 days + 4 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 08 c8 0c 6b ee Error: UNC 8 sectors at LBA = 0x0e6b0cc8 = 241896648
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 08 c8 0c 6b e0 00 01:30:17.763 READ DMA EXT
25 00 08 c8 0c 6b e0 00 01:30:14.067 READ DMA EXT
25 00 08 c0 0c 6b e0 00 01:30:14.067 READ DMA EXT
25 00 08 b8 0c 6b e0 00 01:30:14.066 READ DMA EXT
25 00 08 b0 0c 6b e0 00 01:30:14.065 READ DMA EXT
Error 269 occurred at disk power-on lifetime: 8932 hours (372 days + 4 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 08 c8 0c 6b ee Error: UNC 8 sectors at LBA = 0x0e6b0cc8 = 241896648
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 08 c8 0c 6b e0 00 01:30:14.067 READ DMA EXT
25 00 08 c0 0c 6b e0 00 01:30:14.067 READ DMA EXT
25 00 08 b8 0c 6b e0 00 01:30:14.066 READ DMA EXT
25 00 08 b0 0c 6b e0 00 01:30:14.065 READ DMA EXT
25 00 08 a8 0c 6b e0 00 01:30:14.065 READ DMA EXT
Error 268 occurred at disk power-on lifetime: 8932 hours (372 days + 4 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 08 98 fb 6a ee Error: UNC 8 sectors at LBA = 0x0e6afb98 = 241892248
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 08 98 fb 6a e0 00 01:30:06.407 READ DMA EXT
25 00 08 98 fb 6a e0 00 01:30:02.629 READ DMA EXT
25 00 08 98 fb 6a e0 00 01:29:58.851 READ DMA EXT
25 00 08 98 fb 6a e0 00 01:29:55.092 READ DMA EXT
25 00 08 90 fb 6a e0 00 01:29:55.092 READ DMA EXT
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed: read failure 00% 8935 588461808
# 2 Short offline Completed without error 00% 8934 -
# 3 Extended offline Completed: read failure 00% 8929 588461808
# 4 Short offline Completed without error 00% 8928 -
# 5 Short offline Completed without error 00% 8926 -
# 6 Short offline Completed without error 00% 8924 -
# 7 Short offline Completed without error 00% 6030 -
# 8 Short offline Completed without error 00% 549 -
# 9 Short offline Completed without error 00% 1 -
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.
|
|
|
|
All times are GMT -5. The time now is 09:18 PM.
|
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
|
 Latest Threads
LQ News
|
|
