root@Remus:~ # smartctl -a /dev/ada6 smartctl 6.5 2016-05-07 r4318 [FreeBSD 11.0-STABLE amd64] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Toshiba 3.5" DT01ACA... Desktop HDD Device Model: TOSHIBA DT01ACA300 Serial Number: 37T9H31AS LU WWN Device Id: 5 000039 fe6d26785 Firmware Version: MX6OABB0 User Capacity: 3,000,592,982,016 bytes [3.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 7200 rpm Form Factor: 3.5 inches Device is: In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS T13/1699-D revision 4 SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Tue Sep 19 20:45:18 2017 AEST 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: (0x84) Offline data collection activity was suspended by an interrupting command from host. Auto Offline Data Collection: Enabled. 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: (21648) 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: ( 1) minutes. Extended self-test routine recommended polling time: ( 361) 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 016 Pre-fail Always - 0 2 Throughput_Performance 0x0005 140 140 054 Pre-fail Offline - 68 3 Spin_Up_Time 0x0007 100 100 024 Pre-fail Always - 0 4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 1 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 124 124 020 Pre-fail Offline - 33 9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 76 10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 1 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 2 193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 2 194 Temperature_Celsius 0x0002 171 171 000 Old_age Always - 35 (Min/Max 25/53) 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 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% 61 - # 2 Extended offline Completed without error 00% 5 - # 3 Short offline Completed without error 00% 0 - 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.
Around 24 hours mate
I'm surprised by an an average (not maximum!) sequential transfer rate of over 250 MB/s from an 7200 rpm HDD. But if this is the only issue with this shiny new HDD ...
Yeah strange but no other indicators of any issues. Ill just set up smart testing periodically and keep an eye on it.
Performance seems to be (at least to me and at least somewhat) suspiciously good.
Total badblocks data volume transferred:
<disk capacity> * <# of badblocks patterns> * <read/write factor> =
3.00 TB * 4 * 2 =
24 TB
Average (read or write) badblocks sequential data rate, based on rough 24 h run time estimate:
24 TB / 24 h =
24 * 10^6 MB / (24 * 3600 s) =
278 MB/s
I'm surprised by an an average (not maximum!) sequential transfer rate of over 250 MB/s from an 7200 rpm HDD. But if this is the only issue with this shiny new HDD ...
Excepted it didn't scan 24 TB but only what is used at that time + some metadata so the speed is far less than 250 MB/s.
badblocks -ws /dev/ada6
reads and writes the whole device four times regardless of which sectors are used at that time and even regardless if there is/was a file system on that device prior to the badblocks run.Ah, sorry, didn't saw you were talking about badblocks.
But I guess your drive isn't 24 TB so where this number come from?
badblocks -ws <device>
does 4 complete device writes (for 4 different patterns 0xaa, 0x55, 0xff and 0x00) and 4 complete device reads as explained in the man page, so my calculation isOk, so from that it seems that the speed is correct but it seems to be very high. Well, I guess you can be happy about that :D
While that might be true, for an average home user, the differences in those values tend to be so close that it shouldn't matter too much for home use. Also, if you do way too much research in buying them, you might just end up doing research and not have any time left to buy the damn hardware
Question from a curious individual: Could you please take a Reporting -> Disk -> Disk I/O screenshot of this disk from the date in question and show it here? A 24h period should show at least half of the badblocks run.
I'm not sure how (if its even possible) to magnify all the data onto one legible screen... anyway...
View attachment 20715 View attachment 20716