Custom Query (1359 matches)

I've bought a brand new 1T Seagate drive yesterday.

kotik tmp # dmesg | grep ST31
[    0.834822] ata1.00: ATA-8: ST31000528AS, CC35, max UDMA/133
[    0.847168] scsi 0:0:0:0: Direct-Access     ATA      ST31000528AS     CC35 PQ: 0 ANSI: 5

I was quite surprised to see its Head_Flying_Hours to be some n-teen digit number when I first run smartctl on it, however, Power_On_Hours value was sane. To be sure that everything is ok with my eyes I ran smrtctl again. This time the value was completely different although of the same order of magnitude. After quick investigation it became quite obvious that there is something wrong with the byte order of the raw value

kotik tmp # smartctl -d ata  -A  /dev/sda  | grep ^240
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       102838696935451
kotik tmp # printf "%x\n" 102838696935451
5d880000001b

When I read the values with my programme (see attachment) I found that one of the bytes of the value is stored in the reserv field of the ata_smart_attribute structure. The right order to read the value seems to be

raw[3], raw[2], raw[1], raw[0], reserv, raw[5], raw[4]

However, I am not sure about more significant bytes (raw[1-3]).

The value itself is almost for sure number of milliseconds.

I have sata & sas drives attached to areca 1680ix controllers and am not able to pull any data from the drives. I used to have sata drives attached to areca 1280ml's when on those I was able to. Seems the program 1) does not recognize the newer 1.47 firmware and 2) can't pull data from the controller. This is being run under ubuntu 8.04.3 64bit.

I would be willing to test any non destructive patches if you do not have access to an areca 1680ix controller.

stcost@loki:/var/log/arecadiskstat/2009$ sudo /var/ftp/pub/incoming/src/sm5/smartctl --all --device=areca,1 /dev/sg11 smartctl 5.39 2009-01-21 22:33 [x86_64-unknown-linux-gnu] (local build) Copyright (C) 2002-8 by Bruce Allen, ​http://smartmontools.sourceforge.net

The firmware of your Areca RAID controller appears to be outdated! Please update your controller to firmware version 1.46 or later. You may download it here: ​ftp://ftp.areca.com.tw/RaidCards/BIOS_Firmware

Smartctl: Device Read Identity Failed (not an ATA/ATAPI device)

Some sample data from Areca's CLI program from within linux. --- The System Information =========================================== Main Processor : 1200MHz CPU ICache Size : 32KB CPU DCache Size : 32KB CPU SCache Size : 512KB System Memory : 2048MB/533MHz/ECC Firmware Version : V1.47 2009-07-16 BOOT ROM Version : V1.47 2009-06-25 Serial Number : Y820CABWAR800096 Controller Name : ARC-1680 Current IP Address : 172.18.9.17 =========================================== GuiErrMsg<0x00>: Success. The Hardware Monitor Information ===================================================== [Controller H/W Monitor]

CPU Temperature : 69 C Controller Temp. : 63 C CPU Fan : 2518 RPM 12V : 11.856 V 5V : 5.026 V 3.3V : 3.264 V DDR-II +1.8V : 1.792 V PCI-E +1.8V : 1.808 V CPU +1.8V : 1.824 V CPU +1.2V : 1.200 V DDR-II +0.9V : 0.896 V Battery Status : 100%

[Enclosure#1 : ARECA SAS RAID AdapterV1.0] [Enclosure#2 : ARC-8011x28-01.00.05.08 000 ] [Enclosure#3 : AIC EI16-53C-01A1 114j]

1.9V : 1.880 V PSU_0 : OK PSU_1 : OK Tmprature_0 : 39 C

[Enclosure#4 : AIC EI16-53C-01A1 114j]

1.9V : 1.890 V PSU_0 : OK PSU_1 : OK Tmprature_0 : 39 C

[Enclosure#5 : AIC EI16-53C-01A1 114j]

1.9V : 1.880 V PSU_0 : OK PSU_1 : OK Tmprature_0 : 40 C

[Enclosure#6 : AIC EI16-53C-01A1 114j]

1.9V : 1.880 V PSU_0 : OK PSU_1 : OK Tmprature_0 : 39 C

===================================================== GuiErrMsg<0x00>: Success. Drive Information =============================================================== Device Type : SAS(5000C5000B0E7C3E) Device Location : Enclosure#2 SLOT 21 Model Name : HP DH072BB978 Serial Number : 3PD1V46M0000990 Firmware Rev. : HPD9 Disk Capacity : 73.4GB Device State : NORMAL Timeout Count : 0 Media Error Count : 0 Rotation Speed : 15015(RPM) Device Temperature : 52 C Read Errors Receovered W/O Delay : 0x0000000000000000 Read Errors Receovered W Delay : 0x0000000000000000 Read Errors Receovered W Retry : 0x0000000000000000 Read Errors Receovered : 0x0000000000000000 Read Total Bytes : 0x0000000000000000 Read Errors Unrecovered : 0x0000000000000000 Write Errors Receovered W/O Delay : 0xFFFFFFFFFFFFFFFF Write Errors Receovered W Delay : 0x0000000000000000 Write Errors Receovered W Retry : 0x0000000000000000 Write Errors Receovered : 0x0000000000000000 Write Total Bytes : 0x0000000000000000 Write Errors Unrecovered : 0x0000000000000000 Verify Errors Receovered W/O Delay : 0x0000000000000000 Verify Errors Receovered W Delay : 0x0000000000000000 Verify Errors Receovered W Retry : 0x0000000000000000 Verify Errors Receovered : 0x0000000000000000 Verify Errors Unrecovered : 0x0000000000000000 Non-Medium Errors : 0x0000000000000000 =============================================================== GuiErrMsg<0x00>: Success. Drive Information =============================================================== Device Type : SATA(50015B2080005565) Device Location : Enclosure#3 Disk_01 Model Name : ST31000340NS Serial Number : 9QJ37BDL Firmware Rev. : SN06 Disk Capacity : 1000.2GB Device State : NORMAL Timeout Count : 0 Media Error Count : 0 SMART Read Error Rate : 84(44) SMART Spinup Time : 99(0) SMART Reallocation Count : 100(36) SMART Seek Error Rate : 76(30) SMART Spinup Retries : 100(97) SMART Calibration Retries : N.A.(N.A.) =============================================================== GuiErrMsg<0x00>: Success.

I'm running smartctl from SVN head (revision 2985) on an AMD64 system with Linux kernel 2.6.30-2 (Debian unstable)

Calling smartctl -d 3ware,0 -a /dev/sda results in a Segmentation fault.

Backtrace: #0 0x000000000042e2de in os_linux::linux_escalade_device::ata_pass_through (this=0x674010, in=..., out=...) at os_linux.cpp:1610 #1 0x000000000040cb99 in smartcommandhandler (device=0x674010, command=IDENTIFY, select=0, data=0x662d40 "\036") at atacmds.cpp:569 #2 0x000000000040e82d in ataReadHDIdentity (device=0x674010, buf=0x662d40) at atacmds.cpp:774 #3 0x0000000000413891 in ataPrintMain (device=0x674010, options=...) at ataprint.cpp:1758 #4 0x000000000040600d in main_worker (argc=5, argv=0x7fffffffe4e8) at smartctl.cpp:949 #5 0x000000000040614c in main (argc=5, argv=0x7fffffffe4e8) at smartctl.cpp:967

Debugging reveals:

passthru is initialized in os_linux.cpp:1471 in the (m_escalade_type==AMCC_3WARE_678K) section. It is then reset to NULL at os_linux.cpp:1576 The subsequent access at os_linux.cpp:1610 dereferences the NULL-Pointer, which segfaults.