Hello,
Here is the result of smartctl with Hitachi HUS724040ALE640, not in
http://sourceforge.net/apps/trac/smartmontools/browser/trunk/smartmontools/drivedb.h
It seems to be a Hitachi Ultrastar 7K4000 SATA III 4To.
Is it "normal" that I need to pass "-d sat" to get correct results ?
Will the add to the database will fix this ?
And what are the lines :
ff 00 00 00 00 00 00 00 00:16:33.988 [VENDOR SPECIFIC]
The test has been running from a Solaris system (but does it count ?).
Thank you for your effort for maintaining smartctl !
Regards
--
Théophile Helleboid
# smartctl -a /dev/rdsk/c8t5000CCA22BC24BC3d0
smartctl 5.42 2011-10-20 r3458 [i386-pc-solaris2.10] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net
/dev/rdsk/c8t5000CCA22BC24BC3d0: Unable to detect device type
Smartctl: please specify device type with the -d option.
Use smartctl -h to get a usage summary
# smartctl -a /dev/rdsk/c8t5000CCA22BC24BC3d0 -d scsi
smartctl 5.42 2011-10-20 r3458 [i386-pc-solaris2.10] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net
User Capacity: 4,000,787,030,016 bytes [4.00 TB]
Logical block size: 512 bytes
Logical Unit id: 0x5000cca22bc24bc3
Serial number: PK2331PAG51KTT
Device type: disk
Local Time is: Mon Oct 1 16:59:57 2012 CEST
Device supports SMART and is Enabled
Temperature Warning Disabled or Not Supported
Log Sense failed, IE page [scsi response fails sanity test]
Error Counter logging not supported
SMART Self-test log
Num Test Status segment LifeTime LBA_first_err
[SK ASC ASQ]
Description number (hours)
# 1 Background short Completed - 188 -
[- - -]
# 2 Background short Completed - 62 -
[- - -]
# 3 Background short Completed - 22 -
[- - -]
# 4 Background short Completed - 22 -
[- - -]
# 5 Background short Completed - 22 -
[- - -]
# 6 Background short Completed - 18 -
[- - -]
Long (extended) Self Test duration: 34080 seconds [568.0 minutes]
# smartctl -a /dev/rdsk/c8t5000CCA22BC24BC3d0 -d sat
smartctl 5.42 2011-10-20 r3458 [i386-pc-solaris2.10] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net
=== START OF INFORMATION SECTION ===
Device Model: Hitachi HUS724040ALE640
Serial Number: PK2331PAG51KTT
LU WWN Device Id: 5 000cca 22bc24bc3
Firmware Version: MJAOA3B0
User Capacity: 4,000,787,030,016 bytes [4.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 8
ATA Standard is: ATA-8-ACS revision 4
Local Time is: Mon Oct 1 17:00:01 2012 CEST
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: (0x82) Offline data collection activity
was completed without error.
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: ( 24) 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: ( 255) 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 137 137 054 Pre-fail Offline
- 78
3 Spin_Up_Time 0x0007 144 144 024 Pre-fail Always
- 592 (Average 480)
4 Start_Stop_Count 0x0012 100 100 000 Old_age Always
- 13
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 117 117 020 Pre-fail Offline
- 36
9 Power_On_Hours 0x0012 100 100 000 Old_age Always
- 188
10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always
- 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always
- 13
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always
- 20
193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always
- 20
194 Temperature_Celsius 0x0002 206 206 000 Old_age Always
- 29 (Min/Max 17/34)
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
ATA Error Count: 137 (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 137 occurred at disk power-on lifetime: 0 hours (0 days + 0 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
-- -- -- -- -- -- --
00 51 00 00 00 08 00
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
ff 00 00 00 00 00 00 00 00:16:33.988 [VENDOR SPECIFIC]
c1 00 00 00 00 00 00 00 00:16:33.987 [VENDOR SPECIFIC]
ff 00 00 00 00 00 00 00 00:16:33.980 [VENDOR SPECIFIC]
c1 00 00 00 00 00 00 00 00:16:33.979 [VENDOR SPECIFIC]
ff 00 00 00 00 00 00 00 00:16:33.971 [VENDOR SPECIFIC]
Error 136 occurred at disk power-on lifetime: 0 hours (0 days + 0 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
-- -- -- -- -- -- --
00 51 00 00 00 08 00
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
ff 00 00 00 00 00 00 00 00:16:33.971 [VENDOR SPECIFIC]
c1 00 00 00 00 00 00 00 00:16:33.971 [VENDOR SPECIFIC]
ff 00 00 00 00 00 00 00 00:16:33.963 [VENDOR SPECIFIC]
c1 00 00 00 00 00 00 00 00:16:33.962 [VENDOR SPECIFIC]
ff 00 00 00 00 00 00 00 00:16:33.955 [VENDOR SPECIFIC]
Error 135 occurred at disk power-on lifetime: 0 hours (0 days + 0 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
-- -- -- -- -- -- --
00 51 00 00 00 08 00
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
ff 00 00 00 00 00 00 00 00:16:33.938 [VENDOR SPECIFIC]
c1 00 00 00 00 00 00 00 00:16:33.938 [VENDOR SPECIFIC]
ff 00 00 00 00 00 00 00 00:16:33.930 [VENDOR SPECIFIC]
c1 00 00 00 00 00 00 00 00:16:33.929 [VENDOR SPECIFIC]
ff 00 00 00 00 00 00 00 00:16:33.921 [VENDOR SPECIFIC]
Error 134 occurred at disk power-on lifetime: 0 hours (0 days + 0 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
-- -- -- -- -- -- --
00 51 00 00 00 08 00
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
ff 00 00 00 00 00 00 00 00:16:33.930 [VENDOR SPECIFIC]
c1 00 00 00 00 00 00 00 00:16:33.929 [VENDOR SPECIFIC]
ff 00 00 00 00 00 00 00 00:16:33.921 [VENDOR SPECIFIC]
c1 00 00 00 00 00 00 00 00:16:33.921 [VENDOR SPECIFIC]
ff 00 00 00 00 00 00 00 00:16:33.914 [VENDOR SPECIFIC]
Error 133 occurred at disk power-on lifetime: 0 hours (0 days + 0 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
-- -- -- -- -- -- --
00 51 00 00 00 08 00
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
ff 00 00 00 00 00 00 00 00:16:33.905 [VENDOR SPECIFIC]
c1 00 00 00 00 00 00 00 00:16:33.904 [VENDOR SPECIFIC]
ff 00 00 00 00 00 00 00 00:16:33.896 [VENDOR SPECIFIC]
c1 00 00 00 00 00 00 00 00:16:33.896 [VENDOR SPECIFIC]
ff 00 00 00 00 00 00 00 00:16:33.888 [VENDOR SPECIFIC]
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours)
LBA_of_first_error
# 1 Short offline Completed without error 00% 188 -
# 2 Short offline Completed without error 00% 62 -
# 3 Short offline Completed without error 00% 22 -
# 4 Short offline Completed without error 00% 22 -
# 5 Short offline Completed without error 00% 22 -
# 6 Short offline Completed without error 00% 18 -
# 7 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.
------------------------------------------------------------------------------
Got visibility?
Most devs has no idea what their production app looks like.
Find out how fast your code is with AppDynamics Lite.
http://ad.doubleclick.net/clk;262219671;13503038;y?
http://info.appdynamics.com/FreeJavaPerformanceDownload.html
_______________________________________________
Smartmontools-database mailing list
Smartmontools-database@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/smartmontools-database
