From: Franc Z. <fz...@in...> - 2009-10-22 22:30:04
|
Gabriele, I have more WD SMART info. The following attributes were extracted from WD's wdidle3.exe utility, after unpacking it with UPX. http://www.synology.com/support/faq_images/enu/wdidle3.zip Raw Read Error Rate Throughput Performance Spin Up Time Start/Stop Count Re-allocated Sector Count Read Channel Margin Seek Error Rate Seek Time Performance Power-On Hours Count Spin Retry Count Drive Calibration Retry Count Drive Power Cycle Count Soft Read Error Rate SATA Downshift Error Count End to End Error Det/Corr Count Head Stability Induced Op-Vibration Detection Reported Uncorrectable Errors Command Time Out High Fly Writes Airflow Temperature Shock Sense Emergency Retract Cycle Count Load/Unload Cycle Count HDA Temperature ECC on the Fly Count Re-allocated Sector Event Current Pending Sector Count Offline Uncorrectable Sector Count UltraDMA CRC Error Rate Multi Zone Error Rate Soft Read Error Rate Data Address Mark Errors Run Out Cancel Soft ECC Correction Thermal Asperity Rate Flying Height Spin High Current Spin Buzz Offline Seek Performance Disk Shift G-Sense Error Rate Loaded hours Load/Unload Retry Count Load Friction Load/Unload Cycle Count Load-in Time Torque Amplification Count Power-Off Retract Count GMR Head Amp Temperature Head Flying Hours Total LBAs written Total LBAs read Read Error Retry Rate Free Fall Sensor -Franc |
From: Dan L. <da...@ob...> - 2009-10-23 01:28:05
|
On 23.10.2009 0:29, Franc Zabkar: > The following attributes were extracted from WD's wdidle3.exe > utility, after unpacking it with UPX. > > http://www.synology.com/support/faq_images/enu/wdidle3.zip With ID's of the attribute (extracted from the same source): 1 Raw Read Error Rate 2 Throughput Performance 3 Spin Up Time 4 Start/Stop Count 5 Re-allocated Sector Count 6 Read Channel Margin 7 Seek Error Rate 8 Seek Time Performance 9 Power-On Hours Count 10 Spin Retry Count 11 Drive Calibration Retry Count 12 Drive Power Cycle Count 13 Soft Read Error Rate 183 SATA Downshift Error Count 184 End to End Error Det/Corr Count 185 Head Stability 186 Induced Op-Vibration Detection 187 Reported Uncorrectable Errors 188 Command Time Out 189 High Fly Writes 190 Airflow Temperature 191 Shock Sense 192 Emergency Retract Cycle Count 193 Load/Unload Cycle Count 194 HDA Temperature 195 ECC on the Fly Count 196 Re-allocated Sector Event 197 Current Pending Sector Count 198 Offline Uncorrectable Sector Count 199 UltraDMA CRC Error Rate 200 Multi Zone Error Rate 201 Soft Read Error Rate 202 Data Address Mark Errors 203 Run Out Cancel 204 Soft ECC Correction 205 Thermal Asperity Rate 206 Flying Height 207 Spin High Current 208 Spin Buzz 209 Offline Seek Performance 220 Disk Shift 221 G-Sense Error Rate 222 Loaded hours 223 Load/Unload Retry Count 224 Load Friction 225 Load/Unload Cycle Count 226 Load-in Time 227 Torque Amplification Count 228 Power-Off Retract Count 230 GMR Head Amp 231 Temperature 240 Head Flying Hours 241 Total LBAs written 242 Total LBAs read 250 Read Error Retry Rate 254 Free Fall Sensor Dan |
From: Manfred S. <man...@gm...> - 2009-10-23 19:56:59
|
> On 23.10.2009 0:29, Franc Zabkar: > > The following attributes were extracted from WD's wdidle3.exe > > utility, after unpacking it with UPX. > > > > http://www.synology.com/support/faq_images/enu/wdidle3.zip > > With ID's of the attribute (extracted from the same source): > Thanks a lot to you both, Franc and Dan. I will try look into things right now. Cheers, Manfred > 1 Raw Read Error Rate > 2 Throughput Performance > 3 Spin Up Time > 4 Start/Stop Count > 5 Re-allocated Sector Count > 6 Read Channel Margin > 7 Seek Error Rate > 8 Seek Time Performance > 9 Power-On Hours Count > 10 Spin Retry Count > 11 Drive Calibration Retry Count > 12 Drive Power Cycle Count > 13 Soft Read Error Rate > > 183 SATA Downshift Error Count > 184 End to End Error Det/Corr Count > 185 Head Stability > 186 Induced Op-Vibration Detection > 187 Reported Uncorrectable Errors > 188 Command Time Out > 189 High Fly Writes > 190 Airflow Temperature > 191 Shock Sense > 192 Emergency Retract Cycle Count > 193 Load/Unload Cycle Count > 194 HDA Temperature > 195 ECC on the Fly Count > 196 Re-allocated Sector Event > 197 Current Pending Sector Count > 198 Offline Uncorrectable Sector Count > 199 UltraDMA CRC Error Rate > 200 Multi Zone Error Rate > 201 Soft Read Error Rate > 202 Data Address Mark Errors > 203 Run Out Cancel > 204 Soft ECC Correction > 205 Thermal Asperity Rate > 206 Flying Height > 207 Spin High Current > 208 Spin Buzz > 209 Offline Seek Performance > > 220 Disk Shift > 221 G-Sense Error Rate > 222 Loaded hours > 223 Load/Unload Retry Count > 224 Load Friction > 225 Load/Unload Cycle Count > 226 Load-in Time > 227 Torque Amplification Count > 228 Power-Off Retract Count > > 230 GMR Head Amp > 231 Temperature > > 240 Head Flying Hours > 241 Total LBAs written > 242 Total LBAs read > > 250 Read Error Retry Rate > > 254 Free Fall Sensor > > Dan > -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 |
From: Tim S. <ti...@bu...> - 2009-10-23 10:01:53
|
Franc Zabkar wrote: > I have more WD SMART info. > > The following attributes were extracted from WD's wdidle3.exe > utility, after unpacking it with UPX. > Whilst we're on this subject, I briefly looked at disassembling and/or running wdidle3.exe in a debugger to work out what it's actually doing (since it'd be nice to have that sort of functionality in a Linux util rather than having to fart about with DOS!). It seems to be built with free software (watcom and the DOS extender have both been opensourced), but ran out of time to investigate further - any x86 reverse engineering gurus fancy collaborating on it further? An alternative might be to use some sort of x86 emulator with PCI passthrough to snoop on what it's transactions with the IDE controller, but I didn't investigate this route... For those of you who aren't familiar with the issue that wdidle3 addresses: http://ata.wiki.kernel.org/index.php/Known_issues#Drives_which_perform_frequent_head_unloads_under_Linux ... and it also crossed my mind that smartctl could warn users about this condition (i.e. drives with high head unload count for the number of power-on-hours - e.g. 200000 unloads in 2000 power-on-hours for one of my drives) - I've had a couple of Seagate 2.5" drives die, and I suspect this was the reason. Cheers, Tim. |
From: Dan L. <da...@ob...> - 2009-10-26 01:23:19
|
> Whilst we're on this subject, I briefly looked at disassembling and/or > running wdidle3.exe in a debugger to work out what it's actually doing > (since it'd be nice to have that sort of functionality in a Linux util > rather than having to fart about with DOS!). There are are VSCDataIn, VSCDataOut, VSCSendKey routines within WDIDLE3 that seems to implement some sort of remote procedure call (e.g. call of internal firmware function identified by action code with parameters) There is http://www.google.com/patents?vid=USPAT7062398 which seems to describe the method. It may be very dangerous to play with such interface unless we have depth knowledge of firmware internals ... Dan |
From: Franc Z. <fz...@in...> - 2009-10-23 11:39:57
|
I was recently involved in a discussion about APM (Automatic Power Management) at the Seagate forums. http://forums.seagate.com/stx/board/message?board.id=ata_drives&message.id=14976#M14976 The Start/Stop Count increased by 1 every 2 minutes while the drive (Barracuda LP 1TB) was idle with the motor not spinning. I noticed that the Raw_Read_Error_Rate value did not change, and that the Seek_Error_Rate increased by only 5 counts. These 5 seeks would have been incurred when the drive retrieved SMART data from the platters. Otherwise there did not appear to be any sign of software induced activity. I'm wondering if the Load/Unload counts are not similarly affected. In the above case, I suspect that there may have been some background activity, eg SMART offline testing (temperature?), which was responsible for the strange counts. Speaking of temperature, and at the risk of steering this discussion off on another tangent, the Smart Control Transport spec provides a way to retrieve a complete temperature history from the drive. Could this feature be incorporated into smartctl? More info here: http://forums.seagate.com/stx/board/message?board.id=ata_drives&message.id=15966#M15966 -Franc At 09:03 PM 23/10/09, you wrote: >Franc Zabkar wrote: >>I have more WD SMART info. >> >>The following attributes were extracted from WD's wdidle3.exe >>utility, after unpacking it with UPX. >> > >Whilst we're on this subject, I briefly looked at disassembling >and/or running wdidle3.exe in a debugger to work out what it's >actually doing (since it'd be nice to have that sort of >functionality in a Linux util rather than having to fart about with DOS!). > >It seems to be built with free software (watcom and the DOS extender >have both been opensourced), but ran out of time to investigate >further - any x86 reverse engineering gurus fancy collaborating on it further? > >An alternative might be to use some sort of x86 emulator with PCI >passthrough to snoop on what it's transactions with the IDE >controller, but I didn't investigate this route... > > >For those of you who aren't familiar with the issue that wdidle3 addresses: > >http://ata.wiki.kernel.org/index.php/Known_issues#Drives_which_perform_frequent_head_unloads_under_Linux > > >... and it also crossed my mind that smartctl could warn users about >this condition (i.e. drives with high head unload count for the >number of power-on-hours - e.g. 200000 unloads in 2000 >power-on-hours for one of my drives) - I've had a couple of Seagate >2.5" drives die, and I suspect this was the reason. > >Cheers, > >Tim. |
From: Tim S. <ti...@bu...> - 2009-10-23 14:44:42
|
Franc Zabkar wrote: > I'm wondering if the Load/Unload counts are not similarly affected. In > the above case, I suspect that there may have been some background > activity, eg SMART offline testing (temperature?), which was > responsible for the strange counts. The high unload counts under Linux are present without any SMART activity, and are definitely genuine - you can hear the drive doing it. They are an interaction between the Linux kernel's write patterns and internal timers on the drives. i.e. Just after the drive decides that the system is idle, and unloads the heads, the Linux kernel flushes data to disk and causes them to be unloaded. Repeat until broken. Ta, Tim. |
From: Manfred S. <man...@gm...> - 2009-10-23 19:39:07
|
> I was recently involved in a discussion about APM (Automatic Power > Management) at the Seagate forums. > > http://forums.seagate.com/stx/board/message?board.id=ata_drives&message.id=14976#M14976 > > The Start/Stop Count increased by 1 every 2 minutes while the drive > (Barracuda LP 1TB) was idle with the motor not spinning. > > I noticed that the Raw_Read_Error_Rate value did not change, and that > the Seek_Error_Rate increased by only 5 counts. These 5 seeks would > have been incurred when the drive retrieved SMART data from the > platters. Otherwise there did not appear to be any sign of software > induced activity. > > I'm wondering if the Load/Unload counts are not similarly affected. > In the above case, I suspect that there may have been some background > activity, eg SMART offline testing (temperature?), which was > responsible for the strange counts. > > Speaking of temperature, and at the risk of steering this discussion > off on another tangent, the Smart Control Transport spec provides a > way to retrieve a complete temperature history from the drive. Could > this feature be incorporated into smartctl? > > More info here: > > http://forums.seagate.com/stx/board/message?board.id=ata_drives&message.id=15966#M15966 > You mean something different than #> smartctl -l scttemp /dev/sda ? With "-l scttempsts" and "-l scttemphist" you get the upper resp. lower part of the above command. As usual, RTFM ;-) Cheers, Manfred > -Franc > > > At 09:03 PM 23/10/09, you wrote: > >Franc Zabkar wrote: > >>I have more WD SMART info. > >> > >>The following attributes were extracted from WD's wdidle3.exe > >>utility, after unpacking it with UPX. > >> > > > >Whilst we're on this subject, I briefly looked at disassembling > >and/or running wdidle3.exe in a debugger to work out what it's > >actually doing (since it'd be nice to have that sort of > >functionality in a Linux util rather than having to fart about with > DOS!). > > > >It seems to be built with free software (watcom and the DOS extender > >have both been opensourced), but ran out of time to investigate > >further - any x86 reverse engineering gurus fancy collaborating on it > further? > > > >An alternative might be to use some sort of x86 emulator with PCI > >passthrough to snoop on what it's transactions with the IDE > >controller, but I didn't investigate this route... > > > > > >For those of you who aren't familiar with the issue that wdidle3 > addresses: > > > >http://ata.wiki.kernel.org/index.php/Known_issues#Drives_which_perform_frequent_head_unloads_under_Linux > > > > > >... and it also crossed my mind that smartctl could warn users about > >this condition (i.e. drives with high head unload count for the > >number of power-on-hours - e.g. 200000 unloads in 2000 > >power-on-hours for one of my drives) - I've had a couple of Seagate > >2.5" drives die, and I suspect this was the reason. > > > >Cheers, > > > >Tim. > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > Smartmontools-support mailing list > Sma...@li... > https://lists.sourceforge.net/lists/listinfo/smartmontools-support -- Neu: GMX DSL bis 50.000 kBit/s und 200,- Euro Startguthaben! http://portal.gmx.net/de/go/dsl02 |
From: Franc Z. <fz...@in...> - 2009-10-25 02:30:44
|
At 06:38 AM 24/10/09, you wrote: >You mean something different than >#> smartctl -l scttemp /dev/sda >? > >With "-l scttempsts" and "-l scttemphist" you get the >upper resp. lower part of the above command. >As usual, RTFM ;-) > >Cheers, >Manfred My apologies. I have smacked my head. <ouch> BTW, there is another list of WD SMART attributes in Data Lifeguard for DOS, near the end of the EXE. Unfortunately I'm not SMART enough to determine the compression algorithm used. See http://www.users.on.net/~fzabkar/DLGDIAG5.EXE Would it be worthwhile investigating *all* WD disc utilities? -Franc |
From: Franc Z. <fz...@in...> - 2009-10-25 23:24:50
|
I've had a look inside the Windows version of DataLifeGuard. Unfortunately its list of SMART attributes is unexciting and contains no additional information. -Franc At 10:03 AM 26/10/09, you wrote: >On 25.10.2009 3:30, Franc Zabkar: >>BTW, there is another list of WD SMART attributes in Data Lifeguard >>for DOS, near the end of the EXE. Unfortunately I'm not SMART enough >>to determine the compression algorithm used. >> >>See http://www.users.on.net/~fzabkar/DLGDIAG5.EXE > >It's CauseWay DOS Extender compressor. Unfortunately, I have no decompressor. > >This: >http://www.exetools.com/files/unpackers/dos/unpcwc.zip >doesn't work here because it work for raw compressed image, not for >the one bundled with DOS extender code (e.g. .EXE file) |