Custom Query (1405 matches)

I would like to report that this Unknown USB bridge [0x0471:0x2021 (0x103)] works with:

-d sat

It's a external usb box for HDD, Philips model:SDE3273VC/97

Example output:

# smartctl -d sat -x /dev/sdb

smartctl 5.42 2011-10-20 r3458 [i686-linux-2.6.39-gentoo-r3] (local build) Copyright (C) 2002-11 by Bruce Allen, ​http://smartmontools.sourceforge.net

START OF INFORMATION SECTION

Model Family: Western Digital Scorpio Blue Serial ATA Device Model: WDC WD5000BEVT-22A0RT0 Serial Number: WD-WXG1A10C5467 LU WWN Device Id: 5 0014ee 0021371d0 Firmware Version: 01.01A01 User Capacity: 500 107 862 016 bytes [500 GB] Sector Size: 512 bytes logical/physical Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Thu Jan 12 22:22:58 2012 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: (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: (13200) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate.

Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. 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: ( 154) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x7037) SCT Status 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 POSR-K 200 200 051 - 0 3 Spin_Up_Time POS--K 184 152 021 - 1800 4 Start_Stop_Count -O--CK 090 090 000 - 10009 5 Reallocated_Sector_Ct PO--CK 200 200 140 - 0 7 Seek_Error_Rate -OSR-K 200 200 000 - 0 9 Power_On_Hours -O--CK 096 096 000 - 3418

10 Spin_Retry_Count -O--CK 100 100 051 - 0 11 Calibration_Retry_Count -O--CK 100 100 000 - 0 12 Power_Cycle_Count -O--CK 099 099 000 - 1267

191 G-Sense_Error_Rate -O--CK 076 076 000 - 24 192 Power-Off_Retract_Count -O--CK 199 199 000 - 985 193 Load_Cycle_Count -O--CK 193 193 000 - 23082 194 Temperature_Celsius -O---K 119 099 000 - 28 196 Reallocated_Event_Count -O--CK 200 200 000 - 0 197 Current_Pending_Sector -O--CK 200 200 000 - 0 198 Offline_Uncorrectable ----CK 200 200 000 - 0 199 UDMA_CRC_Error_Count -O--CK 200 200 000 - 0 200 Multi_Zone_Error_Rate ---R-- 200 200 051 - 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] GP/S Log at address 0x00 has 1 sectors [Log Directory] SMART Log at address 0x01 has 1 sectors [Summary SMART error log] SMART Log at address 0x02 has 5 sectors [Comprehensive SMART error log] GP Log at address 0x03 has 6 sectors [Ext. Comprehensive SMART error log] SMART Log at address 0x06 has 1 sectors [SMART self-test log] GP Log at address 0x07 has 1 sectors [Extended self-test log] SMART Log at address 0x09 has 1 sectors [Selective self-test log] GP Log at address 0x10 has 1 sectors [NCQ Command Error log] GP Log at address 0x11 has 1 sectors [SATA Phy Event Counters] GP/S Log at address 0x80 has 16 sectors [Host vendor specific log] GP/S Log at address 0x81 has 16 sectors [Host vendor specific log] GP/S Log at address 0x82 has 16 sectors [Host vendor specific log] GP/S Log at address 0x83 has 16 sectors [Host vendor specific log] GP/S Log at address 0x84 has 16 sectors [Host vendor specific log] GP/S Log at address 0x85 has 16 sectors [Host vendor specific log] GP/S Log at address 0x86 has 16 sectors [Host vendor specific log] GP/S Log at address 0x87 has 16 sectors [Host vendor specific log] GP/S Log at address 0x88 has 16 sectors [Host vendor specific log] GP/S Log at address 0x89 has 16 sectors [Host vendor specific log] GP/S Log at address 0x8a has 16 sectors [Host vendor specific log] GP/S Log at address 0x8b has 16 sectors [Host vendor specific log] GP/S Log at address 0x8c has 16 sectors [Host vendor specific log] GP/S Log at address 0x8d has 16 sectors [Host vendor specific log] GP/S Log at address 0x8e has 16 sectors [Host vendor specific log] GP/S Log at address 0x8f has 16 sectors [Host vendor specific log] GP/S Log at address 0x90 has 16 sectors [Host vendor specific log] GP/S Log at address 0x91 has 16 sectors [Host vendor specific log] GP/S Log at address 0x92 has 16 sectors [Host vendor specific log] GP/S Log at address 0x93 has 16 sectors [Host vendor specific log] GP/S Log at address 0x94 has 16 sectors [Host vendor specific log] GP/S Log at address 0x95 has 16 sectors [Host vendor specific log] GP/S Log at address 0x96 has 16 sectors [Host vendor specific log] GP/S Log at address 0x97 has 16 sectors [Host vendor specific log] GP/S Log at address 0x98 has 16 sectors [Host vendor specific log] GP/S Log at address 0x99 has 16 sectors [Host vendor specific log] GP/S Log at address 0x9a has 16 sectors [Host vendor specific log] GP/S Log at address 0x9b has 16 sectors [Host vendor specific log] GP/S Log at address 0x9c has 16 sectors [Host vendor specific log] GP/S Log at address 0x9d has 16 sectors [Host vendor specific log] GP/S Log at address 0x9e has 16 sectors [Host vendor specific log] GP/S Log at address 0x9f has 16 sectors [Host vendor specific log] GP/S Log at address 0xa0 has 16 sectors [Device vendor specific log] GP/S Log at address 0xa1 has 16 sectors [Device vendor specific log] GP/S Log at address 0xa2 has 16 sectors [Device vendor specific log] GP/S Log at address 0xa3 has 16 sectors [Device vendor specific log] GP/S Log at address 0xa4 has 16 sectors [Device vendor specific log] GP/S Log at address 0xa5 has 16 sectors [Device vendor specific log] GP/S Log at address 0xa6 has 16 sectors [Device vendor specific log] GP/S Log at address 0xa7 has 16 sectors [Device vendor specific log] GP/S Log at address 0xa8 has 1 sectors [Device vendor specific log] GP/S Log at address 0xa9 has 1 sectors [Device vendor specific log] GP/S Log at address 0xaa has 1 sectors [Device vendor specific log] GP/S Log at address 0xab has 1 sectors [Device vendor specific log] GP/S Log at address 0xac has 1 sectors [Device vendor specific log] GP/S Log at address 0xad has 1 sectors [Device vendor specific log] GP/S Log at address 0xae has 1 sectors [Device vendor specific log] GP/S Log at address 0xaf has 1 sectors [Device vendor specific log] GP/S Log at address 0xb0 has 1 sectors [Device vendor specific log] GP/S Log at address 0xb1 has 1 sectors [Device vendor specific log] GP/S Log at address 0xb2 has 1 sectors [Device vendor specific log] GP/S Log at address 0xb3 has 1 sectors [Device vendor specific log] GP/S Log at address 0xb4 has 1 sectors [Device vendor specific log] GP/S Log at address 0xb5 has 1 sectors [Device vendor specific log] GP/S Log at address 0xb6 has 1 sectors [Device vendor specific log] GP/S Log at address 0xb7 has 1 sectors [Device vendor specific log] GP/S Log at address 0xc0 has 1 sectors [Device vendor specific log] GP Log at address 0xc1 has 24 sectors [Device vendor specific log] GP/S Log at address 0xe0 has 1 sectors [SCT Command/Status] GP/S Log at address 0xe1 has 1 sectors [SCT Data Transfer]

SMART Extended Comprehensive Error Log Version: 1 (6 sectors) Device Error Count: 186 (device log contains only the most recent 24 errors)

CR = Command Register FEATR = Features Register COUNT = Count (was: Sector Count) Register LBA_48 = Upper bytes of LBA High/Mid/Low Registers ] ATA-8 LH = LBA High (was: Cylinder High) Register ] LBA LM = LBA Mid (was: Cylinder Low) Register ] Register LL = LBA Low (was: Sector Number) Register ] DV = Device (was: Device/Head) Register DC = Device Control Register ER = Error register ST = Status register

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 186 [17] occurred at disk power-on lifetime: 3382 hours (140 days + 22 hours)

When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 08 00 00 07 47 54 2f 40 00 Error: UNC 8 sectors at LBA = 0x0747542f = 122115119

Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 25 ff da 00 08 00 07 54 00 47 2f 40 00 00:01:04.974 READ DMA EXT 25 ff da 00 08 00 07 54 00 47 2f 40 00 00:01:02.520 READ DMA EXT 25 ff da 00 08 00 07 54 00 47 2f 40 00 00:01:00.068 READ DMA EXT 25 ff da 00 08 00 07 54 00 47 2f 40 00 00:00:57.571 READ DMA EXT 25 ff da 00 08 00 07 54 00 47 2f 40 00 00:00:55.073 READ DMA EXT

Error 185 [16] occurred at disk power-on lifetime: 3382 hours (140 days + 22 hours)

When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 08 00 00 07 47 54 2f 40 00 Error: UNC 8 sectors at LBA = 0x0747542f = 122115119

Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 25 ff da 00 08 00 07 54 00 47 2f 40 00 00:01:02.520 READ DMA EXT 25 ff da 00 08 00 07 54 00 47 2f 40 00 00:01:00.068 READ DMA EXT 25 ff da 00 08 00 07 54 00 47 2f 40 00 00:00:57.571 READ DMA EXT 25 ff da 00 08 00 07 54 00 47 2f 40 00 00:00:55.073 READ DMA EXT 25 ff da 00 08 00 07 54 00 47 2f 40 00 00:00:52.620 READ DMA EXT

Error 184 [15] occurred at disk power-on lifetime: 3382 hours (140 days + 22 hours)

When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 08 00 00 07 47 54 2f 40 00 Error: UNC 8 sectors at LBA = 0x0747542f = 122115119

Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 25 ff da 00 08 00 07 54 00 47 2f 40 00 00:01:00.068 READ DMA EXT 25 ff da 00 08 00 07 54 00 47 2f 40 00 00:00:57.571 READ DMA EXT 25 ff da 00 08 00 07 54 00 47 2f 40 00 00:00:55.073 READ DMA EXT 25 ff da 00 08 00 07 54 00 47 2f 40 00 00:00:52.620 READ DMA EXT 25 ff da 00 08 00 07 54 00 47 2f 40 00 00:00:50.167 READ DMA EXT

Error 183 [14] occurred at disk power-on lifetime: 3382 hours (140 days + 22 hours)

When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 08 00 00 07 47 54 2f 40 00 Error: UNC 8 sectors at LBA = 0x0747542f = 122115119

Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 25 ff da 00 08 00 07 54 00 47 2f 40 00 00:00:57.571 READ DMA EXT 25 ff da 00 08 00 07 54 00 47 2f 40 00 00:00:55.073 READ DMA EXT 25 ff da 00 08 00 07 54 00 47 2f 40 00 00:00:52.620 READ DMA EXT 25 ff da 00 08 00 07 54 00 47 2f 40 00 00:00:50.167 READ DMA EXT 25 ff da 00 08 00 07 54 00 47 2f 40 00 00:00:47.714 READ DMA EXT

Error 182 [13] occurred at disk power-on lifetime: 3382 hours (140 days + 22 hours)

When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 08 00 00 07 47 54 2f 40 00 Error: UNC 8 sectors at LBA = 0x0747542f = 122115119

Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 25 ff da 00 08 00 07 54 00 47 2f 40 00 00:00:55.073 READ DMA EXT 25 ff da 00 08 00 07 54 00 47 2f 40 00 00:00:52.620 READ DMA EXT 25 ff da 00 08 00 07 54 00 47 2f 40 00 00:00:50.167 READ DMA EXT 25 ff da 00 08 00 07 54 00 47 2f 40 00 00:00:47.714 READ DMA EXT 25 ff da 00 08 00 07 54 00 47 2f 40 00 00:00:45.260 READ DMA EXT

Error 181 [12] occurred at disk power-on lifetime: 3382 hours (140 days + 22 hours)

When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 08 00 00 07 47 54 2f 40 00 Error: UNC 8 sectors at LBA = 0x0747542f = 122115119

Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 25 ff da 00 08 00 07 54 00 47 2f 40 00 00:00:52.620 READ DMA EXT 25 ff da 00 08 00 07 54 00 47 2f 40 00 00:00:50.167 READ DMA EXT 25 ff da 00 08 00 07 54 00 47 2f 40 00 00:00:47.714 READ DMA EXT 25 ff da 00 08 00 07 54 00 47 2f 40 00 00:00:45.260 READ DMA EXT 25 ff da 00 08 00 07 54 00 47 2f 40 00 00:00:42.808 READ DMA EXT

Error 180 [11] occurred at disk power-on lifetime: 3382 hours (140 days + 22 hours)

When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 08 00 00 07 47 54 2f 40 00 Error: UNC 8 sectors at LBA = 0x0747542f = 122115119

Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 25 ff da 00 08 00 07 54 00 47 2f 40 00 00:00:50.167 READ DMA EXT 25 ff da 00 08 00 07 54 00 47 2f 40 00 00:00:47.714 READ DMA EXT 25 ff da 00 08 00 07 54 00 47 2f 40 00 00:00:45.260 READ DMA EXT 25 ff da 00 08 00 07 54 00 47 2f 40 00 00:00:42.808 READ DMA EXT 25 ff da 00 08 00 07 54 00 47 2f 40 00 00:00:40.355 READ DMA EXT

Error 179 [10] occurred at disk power-on lifetime: 3382 hours (140 days + 22 hours)

When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 08 00 00 07 47 54 2f 40 00 Error: UNC 8 sectors at LBA = 0x0747542f = 122115119

Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 25 ff da 00 08 00 07 54 00 47 2f 40 00 00:00:47.714 READ DMA EXT 25 ff da 00 08 00 07 54 00 47 2f 40 00 00:00:45.260 READ DMA EXT 25 ff da 00 08 00 07 54 00 47 2f 40 00 00:00:42.808 READ DMA EXT 25 ff da 00 08 00 07 54 00 47 2f 40 00 00:00:40.355 READ DMA EXT 25 ff da 00 08 00 07 54 00 47 2f 40 00 00:00:37.902 READ DMA EXT

SMART Extended Self-test Log Version: 1 (1 sectors) Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 3416 - # 2 Selective offline Completed without error 00% 3408 - # 3 Extended offline Aborted by host 90% 3408 - # 4 Extended offline Aborted by host 70% 3408 - # 5 Short offline Completed without error 00% 3406 - # 6 Short offline Completed without error 00% 3389 - # 7 Short offline Completed without error 00% 3389 - # 8 Short offline Completed without error 00% 3388 - # 9 Short offline Completed without error 00% 3388 - #10 Short offline Completed: read failure 90% 3367 122115120 #11 Extended offline Completed: read failure 90% 3364 122115120 #12 Selective offline Completed: read failure 90% 3364 122115120 #13 Short offline Completed: read failure 90% 3364 122115120 #14 Short offline Completed: read failure 90% 3363 122115120

SMART Selective self-test log data structure revision number 1

SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS

1 122115121 122115130 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.

SCT Status Version: 2 SCT Version (vendor specific): 258 (0x0102) SCT Support Level: 1 Device State: Stand-by (1) Current Temperature: 28 Celsius Power Cycle Min/Max Temperature: 27/42 Celsius Lifetime Min/Max Temperature: 27/48 Celsius Under/Over Temperature Limit Count: 0/0 SCT Temperature History Version: 2 Temperature Sampling Period: 1 minute Temperature Logging Interval: 1 minute Min/Max recommended Temperature: 0/60 Celsius Min/Max Temperature Limit: -41/85 Celsius Temperature History Size (Index): 128 (92)

Index Estimated Time Temperature Celsius

93 2012-01-12 20:15 27

... ..( 5 skipped). ..

99 2012-01-12 20:21 27

100 2012-01-12 20:22 ? - 101 2012-01-12 20:23 27 102 2012-01-12 20:24 27 103 2012-01-12 20:25 27 104 2012-01-12 20:26 ? - 105 2012-01-12 20:27 27 ... ..( 15 skipped). .. 121 2012-01-12 20:43 27 122 2012-01-12 20:44 28 * 123 2012-01-12 20:45 ? - 124 2012-01-12 20:46 27 125 2012-01-12 20:47 28 * 126 2012-01-12 20:48 28 * 127 2012-01-12 20:49 29

0 2012-01-12 20:50 29 1 2012-01-12 20:51 28 *

... ..( 83 skipped). .. *

85 2012-01-12 22:15 28 * 86 2012-01-12 22:16 27 87 2012-01-12 22:17 28 *

... ..( 4 skipped). .. *

92 2012-01-12 22:22 28 *

Warning: device does not support SCT Error Recovery Control command SATA Phy Event Counters (GP Log 0x11) ID Size Value Description 0x0001 2 0 Command failed due to ICRC error 0x0002 2 0 R_ERR response for data FIS 0x0003 2 0 R_ERR response for device-to-host data FIS 0x0004 2 0 R_ERR response for host-to-device data FIS 0x0005 2 0 R_ERR response for non-data FIS 0x0006 2 0 R_ERR response for device-to-host non-data FIS 0x0007 2 0 R_ERR response for host-to-device non-data FIS 0x000a 2 1 Device-to-host register FISes sent due to a COMRESET 0x000b 2 0 CRC errors within host-to-device FIS 0x8000 4 35733 Vendor specific

# dmesg usb 1-2: new high speed USB device number 5 using ehci_hcd usb 1-2: New USB device found, idVendor=0471, idProduct=2021 usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 1-2: Product: disk by philips usb 1-2: Manufacturer: Mobile usb 1-2: SerialNumber: 57442D575847314131304335 scsi3 : usb-storage 1-2:1.0 scsi 3:0:0:0: Direct-Access Mobile disk by philips 1.03 PQ: 0 ANSI: 4 sd 3:0:0:0: Attached scsi generic sg3 type 0 sd 3:0:0:0: [sdc] 976773168 512-byte logical blocks: (500 GB/465 GiB) sd 3:0:0:0: [sdc] Write Protect is off sd 3:0:0:0: [sdc] Mode Sense: 21 00 00 00 sd 3:0:0:0: [sdc] Assuming drive cache: write through sd 3:0:0:0: [sdc] Assuming drive cache: write through sdc: unknown partition table sd 3:0:0:0: [sdc] Assuming drive cache: write through sd 3:0:0:0: [sdc] Attached SCSI disk

Please add phpBB to Hosted Apps!

I believe this is the best project around which to discuss S.M.A.R.T. related issues.

I have several questions I want to discuss in your forum. For example

How does the firmware, drivers and operating system avoid writing to pending sectors? How does software force writing to pending sectors?

Why is there a mismatch between the S.M.A.R.T. pending sector count and the sector error count from ddrescue?

Thanks!

Hi,

As I have seen some broken USB-Harddisks now, I would like to submit a WISH:

smartd, when started with options for devicescan and being told, they could be removable, and seeing that smart-notifier connects to smartd via dbus: couldn't smartd check usb-disks when they're connected after starting smartd? (using udisks dbus interface or somesuch) And if it does so already, please document it (then I woulnd't have asked).

Thank you VERY much for great work, which repeatedly saved me from data-loss.

mo