Opened 14 years ago
Closed 13 years ago
#83 closed enhancement (fixed)
iomega LDHD-UP
Reported by: | bikepunk2 | Owned by: | Christian Franke |
---|---|---|---|
Priority: | minor | Milestone: | Release 5.40 |
Component: | all | Version: | 5.39.1 |
Keywords: | Cc: | gnargl |
Description
I just added the Iomega LDHD-UP in the USB supported device list on my own and then I saw that I'm supposed to write to you. Sorry. Hoping I was right
If you're interested here is my
smartctl -a -d usbsunplus /dev/sdb :
smartctl 5.39.1 2010-01-28 r3054 [i686-pc-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net
START OF INFORMATION SECTION
Model Family: Seagate Barracuda 7200.12 family
Device Model: ST3500418AS
Serial Number: 6VMAG6CM
Firmware Version: CC38
User Capacity: 500,107,862,016 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 8
ATA Standard is: ATA-8-ACS revision 4
Local Time is: Wed Jul 7 01:53:05 2010 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: ( 609) 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: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 91) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x103f) SCT Status supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 080 080 006 Pre-fail Always - 192598735
3 Spin_Up_Time 0x0003 097 097 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 134
5 Reallocated_Sector_Ct 0x0033 062 062 036 Pre-fail Always - 1565
7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 389014
9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 355
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 57
183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0
184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0
187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 115
188 Command_Timeout 0x0032 100 091 000 Old_age Always - 120260919324
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 061 050 045 Old_age Always - 39 (Lifetime Min/Max 39/43)
194 Temperature_Celsius 0x0022 039 050 000 Old_age Always - 39 (0 16 0 0)
195 Hardware_ECC_Recovered 0x001a 038 030 000 Old_age Always - 192598735
197 Current_Pending_Sector 0x0012 040 040 000 Old_age Always - 2470
198 Offline_Uncorrectable 0x0010 040 040 000 Old_age Offline - 2470
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 83163451752791
241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 3915841531
242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 857597085
SMART Error Log Version: 1
ATA Error Count: 64239 (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 64239 occurred at disk power-on lifetime: 349 hours (14 days + 13 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
-- -- -- -- -- -- --
04 71 04 9d 00 32 40 Device Fault; Error: ABRT 4 sectors at LBA = 0x0032009d = 3276957
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 03 08 20 45 69 40 00 03:21:55.134 READ DMA EXT
25 03 08 20 45 69 40 00 03:21:55.104 READ DMA EXT
25 03 80 20 45 69 40 00 03:21:55.073 READ DMA EXT
25 03 08 18 45 69 40 00 03:21:55.042 READ DMA EXT
25 03 08 18 45 69 40 00 03:21:55.011 READ DMA EXT
Error 64238 occurred at disk power-on lifetime: 349 hours (14 days + 13 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
-- -- -- -- -- -- --
04 71 04 9d 00 32 40 Device Fault; Error: ABRT 4 sectors at LBA = 0x0032009d = 3276957
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 03 08 20 45 69 40 00 03:21:55.104 READ DMA EXT
25 03 80 20 45 69 40 00 03:21:55.073 READ DMA EXT
25 03 08 18 45 69 40 00 03:21:55.042 READ DMA EXT
25 03 08 18 45 69 40 00 03:21:55.011 READ DMA EXT
25 03 08 18 45 69 40 00 03:21:54.981 READ DMA EXT
Error 64237 occurred at disk power-on lifetime: 349 hours (14 days + 13 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
-- -- -- -- -- -- --
04 71 04 9d 00 32 40 Device Fault; Error: ABRT 4 sectors at LBA = 0x0032009d = 3276957
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 03 80 20 45 69 40 00 03:21:55.073 READ DMA EXT
25 03 08 18 45 69 40 00 03:21:55.042 READ DMA EXT
25 03 08 18 45 69 40 00 03:21:55.011 READ DMA EXT
25 03 08 18 45 69 40 00 03:21:54.981 READ DMA EXT
25 03 08 18 45 69 40 00 03:21:54.951 READ DMA EXT
Error 64236 occurred at disk power-on lifetime: 349 hours (14 days + 13 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
-- -- -- -- -- -- --
04 71 04 9d 00 32 40 Device Fault; Error: ABRT 4 sectors at LBA = 0x0032009d = 3276957
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 03 08 18 45 69 40 00 03:21:55.042 READ DMA EXT
25 03 08 18 45 69 40 00 03:21:55.011 READ DMA EXT
25 03 08 18 45 69 40 00 03:21:54.981 READ DMA EXT
25 03 08 18 45 69 40 00 03:21:54.951 READ DMA EXT
25 03 08 10 45 69 40 00 03:21:54.921 READ DMA EXT
Error 64235 occurred at disk power-on lifetime: 349 hours (14 days + 13 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
-- -- -- -- -- -- --
04 71 04 9d 00 32 40 Device Fault; Error: ABRT 4 sectors at LBA = 0x0032009d = 3276957
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 03 08 18 45 69 40 00 03:21:55.011 READ DMA EXT
25 03 08 18 45 69 40 00 03:21:54.981 READ DMA EXT
25 03 08 18 45 69 40 00 03:21:54.951 READ DMA EXT
25 03 08 10 45 69 40 00 03:21:54.921 READ DMA EXT
25 03 08 10 45 69 40 00 03:21:54.890 READ DMA EXT
SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]
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.
Change History (6)
comment:1 by , 14 years ago
Component: | smartctl → all |
---|---|
Milestone: | → Release 5.40 |
Owner: | changed from | to
Status: | new → accepted |
comment:2 by , 14 years ago
Resolution: | → fixed |
---|---|
Status: | accepted → closed |
follow-up: 4 comment:3 by , 13 years ago
Cc: | added |
---|---|
Resolution: | fixed |
Status: | closed → reopened |
Version: | 5.39.1 → 5.41 |
I reopened this because apparently they're selling different controllers with the same USB vendor:product combination, my "iomega Desktop Hard Drive" doesn't work with "-d usbsunplus", but only with "-d usbjmicron". Can the smartmontools work around this?
Output of "smartctl -i /dev/sdc" or "smartctl -i -d usbsunplus /dev/sdc":
smartctl 5.41 2011-06-09 r3365 [x86_64-linux-2.6.35-30-generic] (local build) Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net Smartctl: Device Read Identity Failed: scsi error unsupported scsi opcode A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
Output of "smartctl -i -d usbjmicron /dev/sdc":
smartctl 5.41 2011-06-09 r3365 [x86_64-linux-2.6.35-30-generic] (local build) Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: Seagate Barracuda 7200.10 Device Model: ST3500830AS Serial Number: 6QG2G1W0 Firmware Version: 3.AAD 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: 7 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Sun Sep 11 19:04:48 2011 CEST SMART support is: Available - device has SMART capability. SMART support is: Enabled
Output of "lsusb -d 059b:0370 -v":
Bus 002 Device 003: ID 059b:0370 Iomega Corp. Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x059b Iomega Corp. idProduct 0x0370 bcdDevice 0.00 iManufacturer 10 Iomega iProduct 11 External HD iSerial 5 6210FFFFFFFF bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 4 USB Mass Storage bmAttributes 0xc0 Self Powered MaxPower 2mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk (Zip) iInterface 6 MSC Bulk-Only Transfer Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Device Qualifier (for other device speed): bLength 10 bDescriptorType 6 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 bNumConfigurations 1 Device Status: 0x5301 Self Powered
comment:4 by , 13 years ago
Status: | reopened → accepted |
---|
Replying to gnargl:
... my "iomega Desktop Hard Drive" doesn't work with "-d usbsunplus", but only with "-d usbjmicron". Can the smartmontools work around this?
Yes, if and only if the devices return different bcdDevice values.
The "usbjmicron" device returns:
idVendor 0x059b Iomega Corp.
idProduct 0x0370
bcdDevice 0.00
What is the bcdDevice value of the "usbsunplus" device ?
comment:5 by , 13 years ago
Keywords: | needinfo added |
---|
comment:6 by , 13 years ago
Keywords: | needinfo removed |
---|---|
Resolution: | → fixed |
Status: | accepted → closed |
Version: | 5.41 → 5.39.1 |
Missing feedback. Please create new ticket if bcdDevice Info for the "usbsunplus" device is available. Don't reopen this ticket, it is related to 5.40 milestone.
r3124.