You can subscribe to this list. Hi all after some hassle getting 5.38 compiled, I'm trying to access a disk on a Sun x4500 Thumper, but don't get really far. 2009, at 09:24, Dan Lukes wrote: Patrick Proniewski napsal/wrote, On 11/27/09 08:54: I've added a brand new WDC WD10EADS hard drive why does ad6 gets hot twice a daywhen smartctl config is supposed to trigger only one selftest per day? Probably: Auto Offline Data Collection: Enabled. Thank you for this lightning-fast reply. # smartctl -offlineauto=off /dev/ad6 smartctl version 5.38 i386-portbld-freebsd6.4 Copyright (C) 2002-8 Bruce Allen Home page is START OF ENABLE/DISABLE COMMANDS SECTION SMART Automatic Offline Testing Disabled.
Now lets wait. But I'm still surprised by the rise of the temperature:( It's my only HD that behaves like this. Thanks, patpro. Hi all, I'm facing a strange behaviour in my FreeBSD server. I've added a brand new WDC WD10EADS hard drive in the server. It's supposed to be eco-friendly (cooler).
But during selftest, its temperature rises from 39°C to 44-45°C for few hours. You can take a look here: /dev/ad4 -H -m root -a -o on -S on -s (S/./././02 L/././6/03) /dev/ad6 -H -m root -a -o on -S on -s (S/./././02 L/././6/03) It yields to a second question: why does ad6 gets hot twice a day, when smartctl config is supposed to trigger only one selftest per day? Info output for this drive: # smartctl -info /dev/ad6 smartctl version 5.38 i386-portbld-freebsd6.4 Copyright (C) 2002-8 Bruce Allen Home page is START OF INFORMATION SECTION Device Model: WDC WD10EADS-00M2B0 Serial Number: WD-WCAV51538624 Firmware Version: 01.00A01 User Capacity: 1,000,204,886,016 bytes Device is: Not in smartctl database for details use: -P showall ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Fri Nov 27 08: CET SMART support is: Available - device has SMART capability. SMART support is: Enabled patpro. Hdparm was considered. There is a case for being part of hdparm/blktool, as it is yet another drive parameter and it would presumably be handy. However, these particular parameters relate to drive reliabity and how the drive deals with error conditions.
So, like SMART tries to predict failure, ERC gives some control when failure occurs. Consequently, I do think it is related to SMART and should be part of the same tool even though it isn't traditional SMART. Also, technically, ERC is defined as a sub command of SMART Command Transport. Although I've not implemented it, this includes another failure recovery/detection option - long blocks, ie, sectors with an appended CRC. Obviously this.really. needs kernel support to be useful, but I do think it is another example of where the smart in SMART is going. Richard +- -+ Biological Sciences, Room 231 +- -+ Mario 'BitKoenig' Holbe wrote: Richard Gregory wrote: Attached is a patch against CVS to get and set the Error Recovery Control parameters in recentish ATA drives.
Hmmm, don't you think this would better fit to hdparm, blktool or the like? I'd say ERC has nothing to do with S.M.A.R.T. At all but with drive configuration - which, in turn, is the domain of the tools named above. just my 2 cents Mario.
Dear smartmontools developers! Until the very recent version of smartmontools (5.39), SMART through USB was not possible on Mac OS X, because the Mac OS X kernel does not support SCSI pass through. That was the reasoning of Christian Franke. Meanwhile I googled for: And found a person, who wrote a SCSI pass through driver for Mac OS X: In the site's comment section I asked as Stefan Nowak whether this code could be used for passing through SMART: And the developer answered within the site's comment section as wagerlabs, that it should work: I don't know low-level coding, otherwise I would offer my help. Please, dear Darwin related smartmontools developers: Could you built SMART through USB support into the Mac version of smartmontools? Regards, Stefan Nowak.
Wdc Wd10eads-00m2b0 Drivers For Mac Free
MIDGARD Internet wrote: Hellomy machine environment is Debian Linux 5.0.3, Linux 2.6.24-7-pve on x8664 and I get an INQUIRY failed message when I exec the command: # smartctl -a -d megaraid,0 -T permissive /dev/sda I believe that chip doens't use the megaraid driver - it uses the mptsas driver - so the -d megaraid is no use to you. Try just running: smartctl -a /dev/sg0 (sg1 etc.) Unfortunately, I've found the smart passthrough on MPT chips buggy (probably an LSI firmware bug), so you may want to tread carefully when using this. See my recent post to this list, and the thread on linux-scsi etc. Hello, my machine environment is Debian Linux 5.0.3, Linux 2.6.24-7-pve on x8664 and I get an INQUIRY failed message when I exec the command: # smartctl -a -d megaraid,0 -T permissive /dev/sda smartctl 5.39 2009-10-10 r2955 x8664-unknown-linux-gnu (local build) Copyright (C) 2002-9 by Bruce Allen, Smartctl open device: /dev/sda megaraiddisk00 failed: INQUIRY failed I'm disorientated about this error, unless smartctl with megaraid only supports SAS o SCSI disks and not SATA disk attached (this is my case).
In that case, is there any prevision or work around it? I'm sure the device can return smart data (at least raw data), because with lsiutil I can obtain them. I leave a partial transcription to clarify: # lsiutil. Port Name Chip Vendor/Type/Rev MPT Rev Firmware Rev IOC 1. /proc/mpt/ioc0 LSI Logic SAS1064E B3 105 011a0000 0.
Wdc Wd10eads-00m2b0 Drivers For Mac Office
Current active firmware version is 011a0000 (1.26.00) Firmware image's version is MPTFW-01.26.00.00-IE LSI Logic x86 BIOS image's version is MPTBIOS-6.24.00.00 (2008.07.01) FCode image's version is MPT SAS FCode Version 1.00.49 (2007.09.21). Devices SAS1064E's links are 3.0 G, 3.0 G, down, down BTL Type Vendor Product Rev SASAddress PhyNum 0 8 0 Disk LSILOGIC Logical Volume 3000 Hidden RAID Devices: BT Device Vendor Product Rev SASAddress PhyNum 0 10 PhysDisk 0 ATA WDC WD7500AADS-0 0A4a39d8b8a 0 0 9 PhysDisk 1 ATA WDC WD7501AALS-0 0K05 8a7f3b25a09e918a 1.
SATA SMART Read Test (RAW, target 10, similar results with target 9) 256 words of SMART Read Data returned 0: 0010 2f01 c800 00c8 0000 0000 0000 2703 e600 2be3 / ' + 10: 0021 0000 0000 3204 6400 1a64 0000 0000 0000 3305! 2 d d 3 20: c800 00c8 0000 0000 0000 2e07 c800 00c8 0000 0000.
Attachments: Hi, Attached is a patch against CVS to get and set the Error Recovery Control parameters in recentish ATA drives. This is the standardised equivalent of Western Digital's TLER, as used in their enterprise SATA drives for RAID configurations, and editable by their WDTLER.EXE utility, mainly for use with non-enterprise SATA drives. Although ERC is now part of the ATA spec, there are no Linux programs to change it, hence this patch. The meat of this patch extends the WRITELOG command to return the ATA registers back to the higher level code. With this the ERC value, which is returned in SectorCount and LBALow, can be queried. To support this, have also extended the man page, the command line options and the SCT capabilities reporting.
This has been tested on Hitachi HDP725050GLA360 (500GB), Western Digital WD20EADS (2TB GP) and Western Digital WD2002FYPS (2TB RE4-GP). It has also been tested to not break existing functionality.
Ata, sat and hpt devices are supported. Unlike WDTLER, changes to the ERC options are lost after a reset or power-loss. To work with High Point controllers (I tested the RR2320), the driver must be patched to pass back the results of a TASKFILE ioctl. This small patch is also attached. Richard +- -+ Biological Sciences, Room 231 +- -+. Assuming there are 255 heads (aka tracks per cylinder) and 63 sectors/track, one can convert CHS geometries to LBA numbers as follows: LBA = (C x 255 x 63) + (H x 63) + (S - 1) Partition size (in sectors) = End LBA - Start LBA + 1 = (Ce - Cs) x 255 x 63 + (He - Hs) x 63 + (Se - Ss) + 1 where e/s are the end/start values of CHS.
BTW, I notice that there appears to be a hidden area between partitions 1 and 2. It starts at 7/0/1 (LBA 112455) and ends at 7/2/59 (LBA 112639). Its size is 185 sectors. I wonder what Dell hides in there.
I've only ever used the Windows version of dd, but I expect you could extract the hidden area as follows: dd if=ddrescue.bin of=hidden.bin bs=512 count=185 skip=112455 -Franc Al Grant wrote: The following is taken from testdisk on a ddrescue.bin file and shows the partition structure. Current partition structure: Partition Start End Size in sectors 1 P FAT16 32M 0 1 1 6 292 DellUtility 2 P HPFS - NTFS 7 2 60 1312 11520 RECOVERY 3. HPFS - NTFS 1312 13 55552 Family.
Al Grant wrote: Current partition structure: Partition Start End Size in sectors 1 P FAT16 32M 0 1 1 6 292 DellUtility 2 P HPFS - NTFS 7 2 60 1312 11520 RECOVERY 3. HPFS - NTFS 1312 13 55552 Family (a) I assume the Start/End values are CHS values? Looks like it. (b) If so, isnt C.H.S = block size (ie should be same as size in sectors?
Close - you need to know what the pretend geometry is (lets guess at something like 38913/255/63 - since most things use 255/63 these days), and also that cylinders and heads are numbered from zero, but sectors are numbered from 1 (just to make things a bit more difficult), so: The first sector on the disk is 0 0 1, and start of partition 1 is 63 sectors-in (0 0 1 to 0 0 63 contains the mbr). The end of partition 1 is at track 6, head 254, sector 63. At the end of the 63rd sector of the 7th track on the 255th head. So the size of partition 1 = (7. 255. 63) - (1.
63) = 112392 Ta, Tim. Well, my first observation appears to be spectacularly wrong. The ATA error count of 7941 (= 0x1F05) appears to be a genuine 16-bit count. Your second drive has a count of 893 which has an uninteresting hex value of 0x037d. Furthermore, the example at the following URL has a count of 65535 (0xFFFF) which appears to confirm that it is a 16-bit count: As for the raw attribute values, your second drive also seems to have large numbers, but not quite as large. Attribute / raw decimal / normalised / raw hexadecimal / bits 16 - 31 - PowerOnHours 558 100 0x2e 558 ReallocatedEventCount 555 100 0x2b 555 CurrentPendingSector 81750614 70 0x000004df6a56 1247 OfflineUncorrectable 16751596 94 0x000000ff9bec 255 UDMACRCErrorCount 5634748 98 0x00000055fabc 85 MultiZoneErrorRate 8040082 98 0x0000007aae92 122 Here are the data for the drive at the abovementioned URL and at.
Hi All Apologies for this being slightly OT, but smartctl and drive geometry seem to go hand in hand. The following is taken from testdisk on a ddrescue.bin file and shows the partition structure.
Current partition structure: Partition Start End Size in sectors 1 P FAT16 32M 0 1 1 6 292 DellUtility 2 P HPFS - NTFS 7 2 60 1312 11520 RECOVERY 3. HPFS - NTFS 1312 13 55552 Family (a) I assume the Start/End values are CHS values?
(b) If so, isnt C.H.S = block size (ie should be same as size in sectors? Still struggling to come to terms with drive geometry numbers!!!! All help appreciated. On 11/16/09, Martin Bene wrote: HiKernel modules: aacraid As I know adaptec raid card is not supported by smartmontool, I read somewhere I can monitor every SATA disk accesing directly using scsi driver from the kernel, this way Since the aacraid driver exposes the /dev/sg.
devices just to allow programs like smartmontool to work, I'd say the combination is quite well supported. Hi Martin, Thanks for your answer, I see you can do some self-test to disks using smartctl, but I want to ask you if this self-test are necesary to get the health status of all disks. When do I have to run this self-test to disks? From time to time? Or only when problems are detected on disks? Thanks again.
Regards, Israel. #smartctl -a -d sat /dev/sg1 #smartctl -a -d sat /dev/sg2 #smartctl -a -d sat /dev/sg3 #smartctl -a -d sat /dev/sg4 This way I get all SMART info from 4 hdds. Questions: Is any chance or possibility to harm the RAID or any data on any disk I'm accessing the way I show above? Is there any other way to get SMART health of the 4 disk of my server?
The (r/o) access to the /dev/sg. devices by smartmontool should be save. Franc Zabkar wrote: Attribute / raw decimal / normalised / raw hexadecimal - CurrentPendingSector 234006505 14 0x0000 0df2 a7e9 OfflineUncorrectable 23407161 92 0x0000 0165 2a39 Just for info: Current SVN version of smartctl allows to print the raw values in hex format. It is also possible to change the attribute name. Example: $ smartctl -v 197,hex48 -v 198,hex48,OfflUncORUnknown -A /dev/ice. 197 CurrentPendingSector 0x0032 070 070 000.
0x00000df2a7e9 198 OfflUncORUnknown 0x0032 094 094 000. 0x000001652a39. It would be easy to add new print formats for such drives if desired. Cheers, Christian. Attachments: Dear Franc, Thanks you very much for you thorough analysis of my logs. As far as I understand from your words ('the errors are soft') my disk is not in excellent condition but it is in an acceptable state and I should not throw it away.
This laptop has been heavily used since one year and had travelled a lot. But except for issues in the suspend-to-ram process (which occurred few times), the hard disk was always switched off during transportation, i.e., during strong/dangerous vibrations. Attached you can find the logs for the second hard drive: same vendor and model but mounted inside another laptop. This second laptop was used much less than mine (it is the 'spare' laptop of our group). The attached output is generated by 'smartctl -a /dev/sda'. Best, Emanuele Franc Zabkar wrote: The values do appear to be byte-swapped. However, if you examine the 'ATA Error Count', its value of 7941 equates to 0x1F05, which, AFAICSwould suggest otherwise.
Attribute / raw decimal / normalised / raw hexadecimal - CurrentPendingSector 234006505 14 0x0000 0df2 a7e9 OfflineUncorrectable 23407161 92 0x0000 0165 2a39 UDMACRCErrorCount 9500054 97 0x0000 0090 f596 MultiZoneErrorRate 23555200 92 0x0000 0167 6c80 If you examine the raw value for CurrentPendingSector, it is about 10 times the value of OfflineUncorrectable and MultiZoneErrorRate. The drops in the normalised values also differ by a factor of 10, ie by 86, 8, and 8, respectively. This suggests that the higher bytes are the ones that store the error counts. I'm guessing that the actual error counts are as follows: CurrentPendingSector 0x0df2 = 3570 OfflineUncorrectable 0x0165 = 357 UDMACRCErrorCount 0x0090 = 144 MultiZoneErrorRate 0x0167 = 359 The fact that your drive has no reallocated sectors would suggest that all the errors are 'soft'. The UDMA CRC errors suggest a communication problem of some kind, perhaps due to an intermittent data cable?
MultiZoneErrorRate is sometimes interpreted as Write Error Rate. Perhaps your drive has difficulty writing, possibly as a consequence of power supply issues, or vibration? Such soft errors would be corrected when the sector is retested prior to reallocation. Can you post the SMART numbers for your second drive? As long as the raw values of the above attributes are less than 0xFFFF (65535), then this would suggest 0 errors. HiKernel modules: aacraid As I know adaptec raid card is not supported by smartmontool, I read somewhere I can monitor every SATA disk accesing directly using scsi driver from the kernel, this way Since the aacraid driver exposes the /dev/sg.
devices just to allow programs like smartmontool to work, I'd say the combination is quite well supported. #smartctl -a -d sat /dev/sg1 #smartctl -a -d sat /dev/sg2 #smartctl -a -d sat /dev/sg3 #smartctl -a -d sat /dev/sg4 This way I get all SMART info from 4 hdds.
Questions: Is any chance or possibility to harm the RAID or any data on any disk I'm accessing the way I show above? Is there any other way to get SMART health of the 4 disk of my server?
The (r/o) access to the /dev/sg. devices by smartmontool should be save. The values do appear to be byte-swapped. However, if you examine the 'ATA Error Count', its value of 7941 equates to 0x1F05, which, AFAICS, would suggest otherwise. Attribute / raw decimal / normalised / raw hexadecimal - CurrentPendingSector 234006505 14 0x0000 0df2 a7e9 OfflineUncorrectable 23407161 92 0x0000 0165 2a39 UDMACRCErrorCount 9500054 97 0x0000 0090 f596 MultiZoneErrorRate 23555200 92 0x0000 0167 6c80 If you examine the raw value for CurrentPendingSector, it is about 10 times the value of OfflineUncorrectable and MultiZoneErrorRate.
The drops in the normalised values also differ by a factor of 10, ie by 86, 8, and 8, respectively. This suggests that the higher bytes are the ones that store the error counts. I'm guessing that the actual error counts are as follows: CurrentPendingSector 0x0df2 = 3570 OfflineUncorrectable 0x0165 = 357 UDMACRCErrorCount 0x0090 = 144 MultiZoneErrorRate 0x0167 = 359 The fact that your drive has no reallocated sectors would suggest that all the errors are 'soft'. The UDMA CRC errors suggest a communication problem of some kind, perhaps due to an intermittent data cable? MultiZoneErrorRate is sometimes interpreted as Write Error Rate. Perhaps your drive has difficulty writing, possibly as a consequence of power supply issues, or vibration?
Such soft errors would be corrected when the sector is retested prior to reallocation. Can you post the SMART numbers for your second drive? As long as the raw values of the above attributes are less than 0xFFFF (65535), then this would suggest 0 errors.Franc These values are reported by smart-notifier as serious problems. I guess that such oddly high values can be explained only by some byte swap issue that seems not unusual for Samsung firmware, according to smartctl man page. An extra concern is that, when the hard disk was running (now it is fully backed up and switched off), the figures (234006505, 23407161) kept INCREASING in time. I've just downloaded UBCD v411 and ran SHDIAG.
It reports no errors at all. Moreover, I've tested smartmontools on an identical hard disk (same vendor, same model) and I got again odd values for those two smart attributes. Shall I throw away the disk or what? Dear All, I've just installed smartmontools on a Samsun hs122jc and I get strange CurrentPendingSector and OfflineUncorrectable values: - (for full log see at the end of this email) - # smartctl -a /dev/sda.(cut).
Khmer english dictionary online. 197 CurrentPendingSector 0x0032 014 014 000 Oldage Always - 234006505 198 OfflineUncorrectable 0x0032 092 092 000 Oldage Always - 23407161.(cut). These values are reported by smart-notifier as serious problems. I guess that such oddly high values can be explained only by some byte swap issue that seems not unusual for Samsung firmware, according to smartctl man page. An extra concern is that, when the hard disk was running (now it is fully backed up and switched off), the figures (234006505, 23407161) kept INCREASING in time.
I've just downloaded UBCD v411 and ran SHDIAG. It reports no errors at all. Moreover, I've tested smartmontools on an identical hard disk (same vendor, same model) and I got again odd values for those two smart attributes. Shall I throw away the disk or what? Thanks in advance to every answer, Emanuele - full 'smartctl -a /dev/sda' log - START OF INFORMATION SECTION Device Model: SAMSUNG HS122JC Serial Number: S18GJ16Q218038 Firmware Version: GQ100-01 User Capacity: 120,034,123,776 bytes Device is: In smartctl database for details use: -P show ATA Version is: 6 ATA Standard is: ATA/ATAPI-6 T13 1410D revision 1 Local Time is: Sun Nov 15 00: CET WARNING: May need -F samsung or -F samsung2 enabled; see manual for details. 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: ( 0) seconds.
Offline data collection capabilities: (0x59) SMART execute Offline immediate. No Auto Offline data collection support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No 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: ( 62) minutes.
WDC WD10EADS-00M2B0 driver manufacturer is (محركات الأقراص القياسية) and developed by Microsoft in the database contains 1 versions of the WDC WD10EADS-00M2B0 matches the hardware GenDisk.WDC WD10EADS-00M2B0 compatible with 1 hardwares driver contains 1 binary files, You can Download the latest drivers for your WDC WD10EADS-00M2B0. Driver name: WDC WD10EADS-00M2B0 Version: 6.1.7600.16385 Date added: 6-21-2006 Manufacturer: (محركات الأقراص القياسية) Provider: Microsoft Update date: 6-21-2006 Device class: DiskDrive Device GUID: 4D36E967-E325-11CE-BFC1-08002BE10318 Hardware Id: Install Id: IDE DISKWDCWD10EADS-00M2B001.00A01 4&96B8844&0&0.1.0 Inf file name: disk.inf Section name: diskinstall Capabilitys.