[smartmontools-support] smartctl short test taking too long on Toshiba AL13SEB300
Gilson Urbano Ferreira Dias
gilsonurban at gmail.com
Fri Jul 22 16:54:11 CEST 2022
Nathan,
The Toshiba AL13SEB300 is SCSI and unfortunately there's no information
when I run "smartctl -c /dev/sdX".
I added the output of two commands, "smartctl -a /dev/sda", and "sg_logs
-a /dev/sda".
$ smartctl -a /dev/sda
smartctl 7.0 2018-12-30 r4883 [x86_64-linux-4.15.0-58-generic] (local build)
Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Vendor: TOSHIBA
Product: AL13SEB300
Revision: 0101
Compliance: SPC-3
User Capacity: 300,000,000,000 bytes [300 GB]
Logical block size: 512 bytes
Rotation Rate: 10500 rpm
Form Factor: 2.5 inches
Logical Unit id: 0x5000039568423224
Device type: disk
Transport protocol: SAS (SPL-3)
Local Time is: Fri Jul 22 16:46:28 2022 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
Temperature Warning: Enabled
=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK
Current Drive Temperature: 31 C
Drive Trip Temperature: 65 C
Manufactured in week 13 of year 2014
Specified cycle count over device lifetime: 50000
Accumulated start-stop cycles: 37
Specified load-unload count over device lifetime: 200000
Accumulated load-unload cycles: 599
Elements in grown defect list: 0
Error counter log:
Errors Corrected by Total Correction Gigabytes
Total
ECC rereads/ errors algorithm processed
uncorrected
fast | delayed rewrites corrected invocations [10^9 bytes]
errors
read: 0 28 1 0 0 495483.627
1
write: 0 5 1 0 0 145691.134
1
Non-medium error count: 15
Self-test execution status: 100% of test remaining
SMART Self-test log
Num Test Status segment LifeTime
LBA_first_err [SK ASC ASQ]
Description number (hours)
# 1 Background short Self test in progress ... - NOW
- [- - -]
# 2 Background long Aborted (by user command) - 44225
- [- - -]
Long (extended) Self-test duration: 2561 seconds [42.7 minutes]
$ sg_logs -a /dev/sda
TOSHIBA AL13SEB300 0101
Supported log pages [0x0]:
0x00 Supported log pages [sp]
0x01 Buffer over-run/under-run [bou]
0x02 Write error [we]
0x03 Read error [re]
0x05 Verify error [ve]
0x06 Non medium [nm]
0x0d Temperature [temp]
0x0e Start-stop cycle counter [sscc]
0x0f Application client [ac]
0x10 Self test results [str]
0x15 Background scan results [bsr]
0x18 Protocol specific port [psp]
0x1a Power condition transitions [pct]
0x2f Informational exceptions [ie]
0x38
Buffer over-run/under-run page [0x1]
under-run = 0
over-run = 0
Write error counter page [0x2]
Errors corrected without substantial delay = 0
Errors corrected with possible delays = 5
Total rewrites or rereads = 1
Total errors corrected = 0
Total bytes processed = 0
Total uncorrected errors = 1
Read error counter page [0x3]
Errors corrected without substantial delay = 0
Errors corrected with possible delays = 28
Total rewrites or rereads = 1
Total errors corrected = 0
Total bytes processed = 0
Total uncorrected errors = 1
Verify error counter page [0x5]
Errors corrected without substantial delay = 0
Errors corrected with possible delays = 0
Total rewrites or rereads = 0
Total errors corrected = 0
Total bytes processed = 0
Total uncorrected errors = 0
Non-medium error page [0x6]
Non-medium error count = 15
Temperature page [0xd]
Current temperature = 31 C
Reference temperature = 65 C
Start-stop cycle counter page [0xe]
Date of manufacture, year: 2014, week: 13
Accounting date, year: , week:
Specified cycle count over device lifetime = 50000
Accumulated start-stop cycles = 37
Specified load-unload count over device lifetime = 200000
Accumulated load-unload cycles = 599
Application client page [0xf]
00 0f 00 40 00 00 00 83 fc 00 00 00 00 00 00 00 00
10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
..... [truncated after 64 of 16388 bytes (use '-H' to see the rest)]
Self-test results page [0x10]
Parameter code = 1, accumulated power-on hours = 0
self-test code: background short [1]
self-test result: self test in progress [15]
Parameter code = 2, accumulated power-on hours = 44225
self-test code: background extended [2]
self-test result: aborted by SEND DIAGNOSTIC [1]
Background scan results page [0x15]
Status parameters:
Accumulated power on minutes: 2653719 [h:m 44228:39]
Status: background scan enabled, none active (waiting for BMS interval
timer to expire)
Number of background scans performed: 566
Background medium scan progress: 0.00 %
Number of background medium scans performed: 0 [not reported]
Protocol Specific port page for SAS SSP (sas-2) [0x18]
relative target port id = 1
generation code = 2
number of phys = 1
phy identifier = 0
attached SAS device type: SAS or SATA device
attached reason: unknown
reason: loss of dword synchronization
negotiated logical link rate: 3 Gbps
attached initiator port: ssp=1 stp=1 smp=1
attached target port: ssp=0 stp=0 smp=0
SAS address = 0x5000039568423226
attached SAS address = 0x5001e679b3cc1000
attached phy identifier = 0
Invalid DWORD count = 59812
Running disparity error count = 59671
Loss of DWORD synchronization = 14953
Phy reset problem = 0
Phy event descriptors:
Invalid word count: 59812
Running disparity error count: 59671
Loss of dword synchronization count: 14953
Phy reset problem count: 0
Elasticity buffer overflow count: 0
Received abandon-class OPEN_REJECT count: 0
Transmitted BREAK count: 2
Received BREAK count: 0
Transmitted SSP frame error count: 0
Received SSP frame error count: 0
relative target port id = 2
generation code = 2
number of phys = 1
phy identifier = 1
attached SAS device type: no device attached
attached reason: unknown
reason: unknown
negotiated logical link rate: phy enabled; unknown rate
attached initiator port: ssp=0 stp=0 smp=0
attached target port: ssp=0 stp=0 smp=0
SAS address = 0x5000039568423227
attached SAS address = 0x0
attached phy identifier = 0
Invalid DWORD count = 0
Running disparity error count = 0
Loss of DWORD synchronization = 0
Phy reset problem = 0
Phy event descriptors:
Invalid word count: 0
Running disparity error count: 0
Loss of dword synchronization count: 0
Phy reset problem count: 0
Elasticity buffer overflow count: 0
Received abandon-class OPEN_REJECT count: 0
Transmitted BREAK count: 0
Received BREAK count: 0
Transmitted SSP frame error count: 0
Received SSP frame error count: 0
Power condition transitions page [0x1a]
Accumulated transitions to idle_a = 3405628
Accumulated transitions to idle_b = 3405592
Accumulated transitions to idle_c = 599
Reserved [0x4] = 0
Accumulated transitions to standby_z = 0
Accumulated transitions to standby_y = 0
Informational Exceptions page [0x2f]
IE asc = 0x0, ascq = 0x0
Current temperature = 31 C
Threshold temperature = 0 C [IBM extension]
Regards,
Gilson Urbano
On Thu, Jul 21, 2022 at 8:23 PM Nathan Stratton Treadway <nathanst at ontko.com>
wrote:
>
> On Wed, Jul 20, 2022 at 10:49:15 +0200, Gilson Urbano Ferreira Dias wrote:
> > Two days have passed and the short test on Toshiba is still running
> > (53% remaining). I don't think the difference from 6Gbps to 12Gbps
> > makes that huge difference.
>
> Correct -- the SMART self-tests are internal to the drive and do not
> involve sending data across the SATA interface.
>
> What does the "Short self-test routine recommended polling time:" field
> in the output of "smartctl -c /dev/sdX" say for that drive?
>
> (In any case, having a short self-test take days does sound like a bug
> in the drive's firmware.... but I myself don't have any specific
> information about or experience with that particular drive model.)
>
> Nathan
>
>
>
----------------------------------------------------------------------------
> Nathan Stratton Treadway - nathanst at ontko.com - Mid-Atlantic region
> Ray Ontko & Co. - Software consulting services -
http://www.ontko.com/
> GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: 1023D/ECFB6239
> Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239
> _______________________________________________
> Smartmontools-support mailing list
> Smartmontools-support at listi.jpberlin.de
> https://listi.jpberlin.de/mailman/listinfo/smartmontools-support
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://listi.jpberlin.de/pipermail/smartmontools-support/attachments/20220722/858650a2/attachment.htm>
More information about the Smartmontools-support
mailing list