Custom Query (1564 matches)
Results (451 - 453 of 1564)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #204 | wontfix | Illegal request CDBs submit to some models of Fujitsu SCSI disks | ||
| Description |
Since smartmontools 5.41, on our Solaris 9/10 systems when using "smartctl -a" against a Fujitsu SCSI disk, it appears smartctl is submitting invalid CDBs to the underlying drive (which rejects the command, citing ILLEGAL REQUEST). "smartctl -x" induces two rejections. smartmontools 5.40 does not cause this behaviour. The problem with the rejection is that the Solaris kernel logs this in such a way that it appears as a disk failure to our NOC, which results tickets opened to have disks replaced when in fact there's nothing wrong with the disk at all. Relevant details: # iostat -E -n
c0t0d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: FUJITSU Product: MAW3147NC Revision: 0104 Serial No:
Size: 147.09GB <147086327296 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 0 Predictive Failure Analysis: 0
# smartctl -x /dev/rdsk/c0t0d0s0
smartctl 5.42 2011-10-20 r3458 [i386-pc-solaris2.10] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net
Vendor: FUJITSU
Product: MAW3147NC
Revision: 0104
User Capacity: 147,086,327,808 bytes [147 GB]
Logical block size: 512 bytes
Serial number: DAA0P7B05H9C
Device type: disk
Transport protocol: Parallel SCSI (SPI-4)
Local Time is: Wed Nov 9 01:49:21 2011 PST
Device supports SMART and is Enabled
Temperature Warning Enabled
SMART Health Status: OK
Current Drive Temperature: 26 C
Drive Trip Temperature: 65 C
Manufactured in week 46 of year 2007
Specified cycle count over device lifetime: 10000
Accumulated start-stop cycles: 19
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 0 0 0 0 6208.306 0
write: 0 9 0 0 0 24562.295 0
Non-medium error count: 53
SMART Self-test log
Num Test Status segment LifeTime LBA_first_err [SK ASC ASQ]
Description number (hours)
# 1 Background long Self test in progress ... - NOW - [- - -]
# 2 Background long Self test in progress ... - NOW - [- - -]
Long (extended) Self Test duration: 3432 seconds [57.2 minutes]
Device does not support Background scan results logging
scsiPrintSasPhy Log Sense Failed [unsupported field in scsi command]
# iostat -E -n
c0t0d0 Soft Errors: 2 Hard Errors: 0 Transport Errors: 0
Vendor: FUJITSU Product: MAW3147NC Revision: 0104 Serial No:
Size: 147.09GB <147086327296 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 2 Predictive Failure Analysis: 0
Errors on console, which I imagine will greatly help since they include the request CDB: Nov 9 09:49:21 scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci1022,7450@a/pci9005,ffff@a/sd@0,0 (sd0): Error for Command: inquiry Error Level: Informational Nov 9 09:49:21 scsi: [ID 107833 kern.notice] Requested Block: 0 Error Block: 0 Nov 9 09:49:21 scsi: [ID 107833 kern.notice] Vendor: FUJITSU Serial Number: DAA0P7B05H9C Nov 9 09:49:21 scsi: [ID 107833 kern.notice] Sense Key: Illegal Request Nov 9 09:49:21 scsi: [ID 107833 kern.notice] ASC: 0x24 (invalid field in cdb), ASCQ: 0x0, FRU: 0x0 Nov 9 09:49:22 scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci1022,7450@a/pci9005,ffff@a/sd@0,0 (sd0): Error for Command: log sense(10) Error Level: Informational Nov 9 09:49:22 scsi: [ID 107833 kern.notice] Requested Block: 0 Error Block: 0 Nov 9 09:49:22 scsi: [ID 107833 kern.notice] Vendor: FUJITSU Serial Number: DAA0P7B05H9C Nov 9 09:49:22 scsi: [ID 107833 kern.notice] Sense Key: Illegal Request Nov 9 09:49:22 scsi: [ID 107833 kern.notice] ASC: 0x24 (invalid field in cdb), ASCQ: 0x0, FRU: 0x0 I believe the "scsiPrintSasPhy Log Sense Failed" error can explain one of the illegal requests, but I'm not sure where the other is. Pretty much all our Fujitsu disks behave like this -- more than just the model shown above (smaller models, etc.). If you need me to make a list of them all (for drivedb exclusions/quirks) I can do so. Let me know how to proceed, I have lots of systems to test with. :-) |
|||
| #231 | fixed | Imation Odyssey external USB dock | ||
| Description |
Hi, I have an Imation Odyssey external USB dock. Similar in concept to RDX and Quantum GoVault, the Odyssey dock is a removable drive. Cartridges contain a 2.5" SATA hard disk. smartctl seems to work fine using -d sat to talk directly to the drive in the cartridge. The dock USB VID:PID is 0718:1000. On connecting the dock I get dmesg output like: scsi 10:0:0:0: Direct-Access Imation Odyssey RHDD PQ: 0 ANSI: 4 lsusb output begins (serial number redacted): # lsusb -v -d 0718:1000 Bus 002 Device 009: ID 0718:1000 Imation Corp. Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x0718 Imation Corp. idProduct 0x1000 bcdDevice 51.04 iManufacturer 1 Imation iProduct 2 Odyssey RHDD iSerial 3 0Axxxxxxxxxx There are also internal USB and "mobile USB" Odyssey docks but I don't know the USB IDs for those. The make and model of hard disk in Odyssey cartridges will vary; the example below is for the Fujitsu drive inside a 120GB cartridge. (Notice that the drive accessed via the dock shows as having 4 fewer user sectors than the actual/native number of sectors. That's changed using DCO, either at the factory or by the dock firmware; I'm not sure which.) Example from "smartctl -d sat --xall" with a 120GB cartridge that contains a Fujitsu drive: smartctl 5.41 2011-06-09 r3365 [x86_64-linux-3.0.0-23-generic] (local build) Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: Fujitsu MHW BH Device Model: FUJITSU MHW2120BH Serial Number: NZxxxxxxxxxx LU WWN Device Id: 5 00000e xxxxxxxxx Firmware Version: 00000012 User Capacity: 120,034,121,728 bytes [120 GB] Sector Size: 512 bytes logical/physical Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 3b Local Time is: Tue Jul 24 19:18:33 2012 BST 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: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. 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: ( 578) 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: ( 82) minutes. Conveyance self-test routine recommended polling time: ( 2) 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 FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-- 100 100 046 - 175929 2 Throughput_Performance P-S--- 100 100 030 - 32047104 3 Spin_Up_Time PO---- 100 100 025 - 1 4 Start_Stop_Count -O--CK 100 100 000 - 12 5 Reallocated_Sector_Ct PO--CK 100 100 024 - 0 (2000, 0) 7 Seek_Error_Rate POSR-- 100 100 047 - 3894 8 Seek_Time_Performance P-S--- 100 100 019 - 0 9 Power_On_Hours -O--CK 100 100 000 - 2 10 Spin_Retry_Count PO--C- 100 100 020 - 0 12 Power_Cycle_Count -O--CK 100 100 000 - 12 192 Power-Off_Retract_Count -O--CK 100 100 000 - 7 193 Load_Cycle_Count -O--CK 100 100 000 - 25 194 Temperature_Celsius -O---K 100 100 000 - 35 (Min/Max 25/54) 195 Hardware_ECC_Recovered -O-RC- 100 100 000 - 656 196 Reallocated_Event_Count -O--CK 100 100 000 - 0 (0, 6800) 197 Current_Pending_Sector -O--C- 100 100 000 - 0 198 Offline_Uncorrectable ----C- 100 100 000 - 0 199 UDMA_CRC_Error_Count -OSRCK 200 200 000 - 0 200 Multi_Zone_Error_Rate POSR-- 100 100 060 - 4 203 Run_Out_Cancel -O---- 100 100 000 - 2628552360442 240 Head_Flying_Hours -OSRCK 200 200 000 - 0 |
|||
| #346 | fixed | Implement "-l devstat" using smartlog if gplog failed | ||
| Description |
On Darwin (OSX) ATA_LOG_EXT command is not implemented, as well as on some other outdated ATA interfaces. However i found that device statistic is readable using smartlog 0x04 page. This is sample output with my dirty hack for darwin: Device Statistics (SMART Log 0x04)
Page Offset Size Value Description
1 ===== = = == General Statistics (rev 2) ==
1 0x008 4 544 Lifetime Power-On Resets
1 0x010 4 413 Power-on Hours
1 0x018 6 4466199876 Logical Sectors Written
1 0x020 6 23335260 Number of Write Commands
1 0x028 6 4027657571 Logical Sectors Read
1 0x030 6 16200567 Number of Read Commands
4 ===== = = == General Errors Statistics (rev 1) ==
4 0x008 4 0 Number of Reported Uncorrectable Errors
4 0x010 4 0 Resets Between Cmd Acceptance and Completion
6 ===== = = == Transport Statistics (rev 1) ==
6 0x008 4 0 Number of Hardware Resets
6 0x010 4 0 Number of ASR Events
6 0x018 4 0 Number of Interface CRC Errors
7 ===== = = == Solid State Device Statistics (rev 1) ==
7 0x008 1 0~ Percentage Used Endurance Indicator
|_ ~ normalized value
Correct logic on -ldevstat should be:
Also os_darwin.cpp needs to be converted to the new interface (#103) to support multi-sector requests. |
|||
