From: Frieder F. <Fri...@we...> - 2010-02-25 08:37:12
|
Hi, I'm appending the output of smartctl -a after running smartctl -t short /dev/sda An earlier report about a similar drive (OCZ Vertex) is here: http://sourceforge.net/mailarchive/message.php?msg_id=4A6E091D.20008%40isg.de Similar to the report there, the drive here has non-zero values for 198, 199, 200, 201 The drive has less than 20 Power_On_Hours (although reporting 0). Strangely the drive reports a Power_Cycle_Count of zero although the firmware release notes for 1916 claim this has been fixed. http://supertalent.com/support/download/UltraDrive_Firmware_Release_Notes_v1916.pdf The release notes also say an additional smart info "Remaining life" (which I'd be interested in:) has been fixed. Thanks for Smartmontools! Greetings, Frieder ___________________________________________________________ GRATIS für alle WEB.DE-Nutzer: Die maxdome Movie-FLAT! Jetzt freischalten unter http://movieflat.web.de |
From: Frieder F. <fri...@we...> - 2010-02-25 09:08:45
Attachments:
smartctl_ssd_3.out
|
Hi, Frieder Ferlemann schrieb: > I'm appending the output of smartctl -a after running smartctl -t short /dev/sda Sorry, the attachment didn't stick. Greetings, Frieder ./smartctl -a /dev/sdb smartctl 5.40 2010-02-18 r3069 [x86_64-suse-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: STT_FTM64GX25H Serial Number: P612102-MIBY-208A052 Firmware Version: 1916 User Capacity: 64.023.257.088 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: Thu Feb 25 10:03:39 2010 CET 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: (0x1d) SMART execute Offline immediate. No Auto Offline data collection support. Abort Offline collection upon new command. Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. No Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x00) Error logging NOT supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 0) minutes. Extended self-test routine recommended polling time: ( 0) minutes. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x0000 006 000 000 Old_age Offline - 0 9 Power_On_Hours 0x0000 014 000 000 Old_age Offline - 0 12 Power_Cycle_Count 0x0000 005 000 000 Old_age Offline - 0 184 End-to-End_Error 0x0000 093 000 000 Old_age Offline - 0 195 Hardware_ECC_Recovered 0x0000 000 000 000 Old_age Offline - 0 196 Reallocated_Event_Count 0x0000 000 000 000 Old_age Offline - 0 197 Current_Pending_Sector 0x0000 000 000 000 Old_age Offline - 0 198 Offline_Uncorrectable 0x0000 118 097 000 Old_age Offline - 424 199 UDMA_CRC_Error_Count 0x0000 179 236 000 Old_age Offline - 1066 200 Multi_Zone_Error_Rate 0x0000 227 139 000 Old_age Offline - 10 201 Soft_Read_Error_Rate 0x0000 165 193 000 Old_age Offline - 18 202 Data_Address_Mark_Errs 0x0000 126 217 000 Old_age Offline - 0 203 Run_Out_Cancel 0x0000 106 161 000 Old_age Offline - 0 204 Soft_ECC_Correction 0x0000 000 000 000 Old_age Offline - 0 205 Thermal_Asperity_Rate 0x0000 016 039 000 Old_age Offline - 0 206 Flying_Height 0x0000 001 000 000 Old_age Offline - 0 207 Spin_High_Current 0x0000 011 001 000 Old_age Offline - 0 208 Spin_Buzz 0x0000 011 000 000 Old_age Offline - 0 209 Offline_Seek_Performnce 0x0000 100 000 000 Old_age Offline - 0 211 Unknown_Attribute 0x0000 000 000 000 Old_age Offline - 0 212 Unknown_Attribute 0x0000 000 000 000 Old_age Offline - 0 213 Unknown_Attribute 0x0000 000 000 000 Old_age Offline - 0 Warning: device does not support Error Logging Warning! SMART ATA Error Log Structure error: invalid SMART checksum. SMART Error Log Version: 1 No Errors Logged Warning! SMART Self-Test Log Structure error: invalid SMART checksum. SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] Device does not support Selective Self Tests/Logging |
From: Manfred S. <man...@gm...> - 2010-03-04 00:15:54
|
Frieder, thanks for your report. could you run the following: cat > drivedb.h.add <<EOF { "SuperTalent UltraDrive GX SSD", "STT_FT[MD](28|32|56|64)GX25H", "", "", " -v 9,raw64" " -v 12,raw64" " -v 184,raw64,Initial_Bad_Block_Count" " -v 195,raw64,Program_Failure_Blk_Ct" " -v 196,raw64,Erase_Failure_Blk_Ct" " -v 197,raw64,Read_Failure_Blk_Ct" " -v 198,raw64,Read_Sectors_Tot_Ct" " -v 199,raw64,Write_Sectors_Tot_Ct" " -v 200,raw64,Read_Commands_Tot_Ct" " -v 201,raw64,Write_Commands_Tot_Ct" " -v 202,raw64,Error_Bits_Flash_Tot_Ct" " -v 203,raw64,Corr_Read_Errors_Tot_Ct" " -v 204,raw64,Bad_Block_Full_Flag" " -v 205,raw64,Max_PE_Count_Spec" " -v 206,raw64,Min_Erase_Count" " -v 207,raw64,Max_Erase_Count" " -v 208,raw64,Average_Erase_Count" " -v 209,raw64,Remaining_Lifetime_Perc" }, EOF smartctl -B drivedb.h.add -a /dev/sd? and report back the results? Thanks! Manfred |
From: Frieder F. <fri...@we...> - 2010-03-04 05:57:28
|
Hi Manfred, thanks! Am 04.03.2010 01:15, schrieb Manfred Schwarb: > could you run the following: > > cat > drivedb.h.add <<EOF > { "SuperTalent UltraDrive GX SSD", > "STT_FT[MD](28|32|56|64)GX25H", > "", "", > " -v 9,raw64" > " -v 12,raw64" > " -v 184,raw64,Initial_Bad_Block_Count" > " -v 195,raw64,Program_Failure_Blk_Ct" > " -v 196,raw64,Erase_Failure_Blk_Ct" > " -v 197,raw64,Read_Failure_Blk_Ct" > " -v 198,raw64,Read_Sectors_Tot_Ct" > " -v 199,raw64,Write_Sectors_Tot_Ct" > " -v 200,raw64,Read_Commands_Tot_Ct" > " -v 201,raw64,Write_Commands_Tot_Ct" > " -v 202,raw64,Error_Bits_Flash_Tot_Ct" > " -v 203,raw64,Corr_Read_Errors_Tot_Ct" > " -v 204,raw64,Bad_Block_Full_Flag" > " -v 205,raw64,Max_PE_Count_Spec" > " -v 206,raw64,Min_Erase_Count" > " -v 207,raw64,Max_Erase_Count" > " -v 208,raw64,Average_Erase_Count" > " -v 209,raw64,Remaining_Lifetime_Perc" > }, > EOF > > smartctl -B drivedb.h.add -a /dev/sd? > > > and report back the results? It's: Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x0000 006 000 000 Old_age Offline - 0 9 Power_On_Hours 0x0000 --- --- --- Old_age Offline - 73 12 Power_Cycle_Count 0x0000 --- --- --- Old_age Offline - 17 184 Initial_Bad_Block_Count 0x0000 --- --- --- Old_age Offline - 93 195 Program_Failure_Blk_Ct 0x0000 --- --- --- Old_age Offline - 0 196 Erase_Failure_Blk_Ct 0x0000 --- --- --- Old_age Offline - 0 197 Read_Failure_Blk_Ct 0x0000 --- --- --- Old_age Offline - 0 198 Read_Sectors_Tot_Ct 0x0000 --- --- --- Old_age Offline - 63412716 199 Write_Sectors_Tot_Ct 0x0000 --- --- --- Old_age Offline - 93996899 200 Read_Commands_Tot_Ct 0x0000 --- --- --- Old_age Offline - 1352556 201 Write_Commands_Tot_Ct 0x0000 --- --- --- Old_age Offline - 1953112 202 Error_Bits_Flash_Tot_Ct 0x0000 --- --- --- Old_age Offline - 147757 203 Corr_Read_Errors_Tot_Ct 0x0000 --- --- --- Old_age Offline - 111351 204 Bad_Block_Full_Flag 0x0000 --- --- --- Old_age Offline - 0 205 Max_PE_Count_Spec 0x0000 --- --- --- Old_age Offline - 10000 206 Min_Erase_Count 0x0000 --- --- --- Old_age Offline - 1 207 Max_Erase_Count 0x0000 --- --- --- Old_age Offline - 306 208 Average_Erase_Count 0x0000 --- --- --- Old_age Offline - 50 209 Remaining_Lifetime_Perc 0x0000 --- --- --- Old_age Offline - 100 211 Unknown_Attribute 0x0000 000 000 000 Old_age Offline - 0 212 Unknown_Attribute 0x0000 000 000 000 Old_age Offline - 0 213 Unknown_Attribute 0x0000 000 000 000 Old_age Offline - 0 now:) Greetings, Frieder |
From: Manfred S. <man...@gm...> - 2010-03-04 09:21:00
|
> Hi Manfred, > > thanks! > > > Am 04.03.2010 01:15, schrieb Manfred Schwarb: > > could you run the following: > > > > cat > drivedb.h.add <<EOF > > { "SuperTalent UltraDrive GX SSD", > > "STT_FT[MD](28|32|56|64)GX25H", > > "", "", > > " -v 9,raw64" > > " -v 12,raw64" > > " -v 184,raw64,Initial_Bad_Block_Count" > > " -v 195,raw64,Program_Failure_Blk_Ct" > > " -v 196,raw64,Erase_Failure_Blk_Ct" > > " -v 197,raw64,Read_Failure_Blk_Ct" > > " -v 198,raw64,Read_Sectors_Tot_Ct" > > " -v 199,raw64,Write_Sectors_Tot_Ct" > > " -v 200,raw64,Read_Commands_Tot_Ct" > > " -v 201,raw64,Write_Commands_Tot_Ct" > > " -v 202,raw64,Error_Bits_Flash_Tot_Ct" > > " -v 203,raw64,Corr_Read_Errors_Tot_Ct" > > " -v 204,raw64,Bad_Block_Full_Flag" > > " -v 205,raw64,Max_PE_Count_Spec" > > " -v 206,raw64,Min_Erase_Count" > > " -v 207,raw64,Max_Erase_Count" > > " -v 208,raw64,Average_Erase_Count" > > " -v 209,raw64,Remaining_Lifetime_Perc" > > }, > > EOF > > > > smartctl -B drivedb.h.add -a /dev/sd? > > > > > > and report back the results? > > It's: > Thanks. Power_On_Hours and Remaining_Lifetime_Perc look promising now, so I think we got it right. I will add it to the drive database. Cheers, Manfred > Vendor Specific SMART Attributes with Thresholds: > ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED > WHEN_FAILED RAW_VALUE > 1 Raw_Read_Error_Rate 0x0000 006 000 000 Old_age Offline > - 0 > 9 Power_On_Hours 0x0000 --- --- --- Old_age Offline > - 73 > 12 Power_Cycle_Count 0x0000 --- --- --- Old_age Offline > - 17 > 184 Initial_Bad_Block_Count 0x0000 --- --- --- Old_age Offline > - 93 > 195 Program_Failure_Blk_Ct 0x0000 --- --- --- Old_age Offline > - 0 > 196 Erase_Failure_Blk_Ct 0x0000 --- --- --- Old_age Offline > - 0 > 197 Read_Failure_Blk_Ct 0x0000 --- --- --- Old_age Offline > - 0 > 198 Read_Sectors_Tot_Ct 0x0000 --- --- --- Old_age Offline > - 63412716 > 199 Write_Sectors_Tot_Ct 0x0000 --- --- --- Old_age Offline > - 93996899 > 200 Read_Commands_Tot_Ct 0x0000 --- --- --- Old_age Offline > - 1352556 > 201 Write_Commands_Tot_Ct 0x0000 --- --- --- Old_age Offline > - 1953112 > 202 Error_Bits_Flash_Tot_Ct 0x0000 --- --- --- Old_age Offline > - 147757 > 203 Corr_Read_Errors_Tot_Ct 0x0000 --- --- --- Old_age Offline > - 111351 > 204 Bad_Block_Full_Flag 0x0000 --- --- --- Old_age Offline > - 0 > 205 Max_PE_Count_Spec 0x0000 --- --- --- Old_age Offline > - 10000 > 206 Min_Erase_Count 0x0000 --- --- --- Old_age Offline > - 1 > 207 Max_Erase_Count 0x0000 --- --- --- Old_age Offline > - 306 > 208 Average_Erase_Count 0x0000 --- --- --- Old_age Offline > - 50 > 209 Remaining_Lifetime_Perc 0x0000 --- --- --- Old_age Offline > - 100 > 211 Unknown_Attribute 0x0000 000 000 000 Old_age Offline > - 0 > 212 Unknown_Attribute 0x0000 000 000 000 Old_age Offline > - 0 > 213 Unknown_Attribute 0x0000 000 000 000 Old_age Offline > - 0 > > now:) > > Greetings, > Frieder -- Sicherer, schneller und einfacher. Die aktuellen Internet-Browser - jetzt kostenlos herunterladen! http://portal.gmx.net/de/go/chbrowser |
From: Frieder F. <fri...@we...> - 2010-03-04 17:39:09
|
Hi Manfred, Am 04.03.2010 10:20, schrieb Manfred Schwarb: > Thanks. > Power_On_Hours and Remaining_Lifetime_Perc look promising now, > so I think we got it right. I will add it to the > drive database. Thanks! 198 Read_Sectors_Tot_Ct 0x0000 --- --- --- Old_age Offline - 63412716 199 Write_Sectors_Tot_Ct 0x0000 --- --- --- Old_age Offline - 93996899 200 Read_Commands_Tot_Ct 0x0000 --- --- --- Old_age Offline - 1352556 201 Write_Commands_Tot_Ct 0x0000 --- --- --- Old_age Offline - 1953112 I'm surprised about this one: 208 Average_Erase_Count 0x0000 --- --- --- Old_age Offline - 50 because to my reading (on the wrong assumption of only linear writes) this would translate to 50 * 64GByte drive capacity = 3 TByte having been written. (the ratio of about 60 between 3 TByte and 93996899 sectors * 512 bytes/sector = 48 GByte would seem very high to me) (write sectors being higher than read sectors could be plausible because I did two installs of linux. First one was just for fun a milestone version of openSUSE 11.3 which I a few hours later exchanged for 11.2) I bought the drive as a new device and I did no firmware update as it already had the latest firmware 1916. The first say 10 hours the disk was used with a 2.6.31 kernel since then a kernel of 2.6.33 series was installed. I intend to do a follow up posting if the drive has some more power on hours. Greetings, Frieder |
From: Frieder F. <fri...@we...> - 2010-03-09 20:10:25
Attachments:
smartctl_ssd_5.out
|
Hi again, Am 04.03.2010 18:38, schrieb Frieder Ferlemann: > Thanks! > > 198 Read_Sectors_Tot_Ct 0x0000 --- --- --- Old_age Offline - 63412716 > 199 Write_Sectors_Tot_Ct 0x0000 --- --- --- Old_age Offline - 93996899 > 200 Read_Commands_Tot_Ct 0x0000 --- --- --- Old_age Offline - 1352556 > 201 Write_Commands_Tot_Ct 0x0000 --- --- --- Old_age Offline - 1953112 > > I'm surprised about this one: > > 208 Average_Erase_Count 0x0000 --- --- --- Old_age Offline - 50 > > because to my reading (on the wrong assumption of only linear writes) > this would translate to 50 * 64GByte drive capacity = 3 TByte > having been written. > (the ratio of about 60 between 3 TByte and 93996899 sectors * > 512 bytes/sector = 48 GByte would seem very high to me) > > (write sectors being higher than read sectors could be plausible > because I did two installs of linux. First one was just for > fun a milestone version of openSUSE 11.3 which I a few hours > later exchanged for 11.2) > > I bought the drive as a new device and I did no firmware update > as it already had the latest firmware 1916. > The first say 10 hours the disk was used with a 2.6.31 kernel > since then a kernel of 2.6.33 series was installed. > > I intend to do a follow up posting if the drive has some more > power on hours. actually I did never expect to report back this early, but I'm quite upset about the Average Erase Count of 72 of the drive. 198 Read_Sectors_Tot_Ct 0x0000 --- --- --- Old_age Offline - 82208608 199 Write_Sectors_Tot_Ct 0x0000 --- --- --- Old_age Offline - 106676155 200 Read_Commands_Tot_Ct 0x0000 --- --- --- Old_age Offline - 1781513 201 Write_Commands_Tot_Ct 0x0000 --- --- --- Old_age Offline - 2275882 208 Average_Erase_Count 0x0000 --- --- --- Old_age Offline - 72 Meanwhile 6492 MByte have been written (106676155 - 93996899) Sectors * 512 Bytes /Sector while 1408511 MByte have been erased! (72 - 50) * 64.023.257.088 Bytes This would mean that wear leaveling (or garbage collection/whatever) causes an overhead of more than 200 in flash erase cycles!!! Intolerable. I hope there is a mistake in my calculations or somewhere else. My configuration: - The system has been in what I'd call "light desktop use" - The SSD was shipped with the latest firmware 1916 - I did never mount swap on it (4GB Ram and Swap on a conventional disk, so no need to) - The root partition was mounted noatime - Using a kernel of 2.6.33 series More detail: /dev/sda2 on / type ext4 (rw,noatime,acl,user_xattr) /dev/sda1 on /home type ext4 (rw,acl,user_xattr) Linux version 2.6.33-29-desktop (geeko@buildhost) (gcc version 4.4.1 [gcc-4_4-branch revision 150839] (SUSE Linux) ) #1 SMP PREEMPT 2010-03-05 10:49:02 +0100 Output of smartctl -a /dev/sda is attached If my observations can be independently confirmed this should probably escalate (LKML / LWN / Slashdot) Can someone else have a look? Greetings and thanks, Frieder |
From: Frieder F. <fri...@we...> - 2010-03-15 22:43:40
Attachments:
smartctl_ssd_8.out
|
Hi, just had a look into the output of smartd in /var/log/messages. Seems like the log mistakenly contains 198 Read_Sectors_Tot_Ct as Offline uncorrectable sectors? Mar 15 17:43:51 lake smartd[2821]: smartd 5.40 2010-03-05 r3074 [x86_64-suse-linux-gnu] (local build)#012Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net#012 Mar 15 17:43:51 lake smartd[2821]: No configuration file /usr/local/etc/smartd.conf found, scanning devices ... Mar 15 17:43:51 lake smartd[3116]: smartd has fork()ed into background mode. New PID=3116. ... Mar 15 18:03:50 lake rsyslogd: -- MARK -- Mar 15 18:13:51 lake smartd[3116]: Device: /dev/sda [SAT], 95840173 Offline uncorrectable sectors (changed +703184) ... Mar 15 18:43:50 lake rsyslogd: -- MARK -- Mar 15 18:43:51 lake smartd[3116]: Device: /dev/sda [SAT], 96170325 Offline uncorrectable sectors (changed +330152) ... Mar 15 19:13:51 lake smartd[3116]: Device: /dev/sda [SAT], 96449717 Offline uncorrectable sectors (changed +279392) ... Mar 15 19:43:51 lake smartd[3116]: Device: /dev/sda [SAT], 96457509 Offline uncorrectable sectors (changed +7792) ... It would be really nice if: 208 Average_Erase_Count 209 Remaining_Lifetime_Perc would instead be reported in the log:) Am 09.03.2010 21:09, schrieb Frieder Ferlemann: > actually I did never expect to report back this early, > but I'm quite upset about the Average Erase Count > of 72 of the drive. > > 198 Read_Sectors_Tot_Ct 0x0000 --- --- --- Old_age Offline - 82208608 > 199 Write_Sectors_Tot_Ct 0x0000 --- --- --- Old_age Offline - 106676155 > 200 Read_Commands_Tot_Ct 0x0000 --- --- --- Old_age Offline - 1781513 > 201 Write_Commands_Tot_Ct 0x0000 --- --- --- Old_age Offline - 2275882 > > 208 Average_Erase_Count 0x0000 --- --- --- Old_age Offline - 72 > > Meanwhile 6492 MByte have been written (106676155 - 93996899) Sectors * 512 Bytes /Sector > while 1408511 MByte have been erased! (72 - 50) * 64.023.257.088 Bytes > > This would mean that wear leaveling (or garbage collection/whatever) > causes an overhead of more than 200 in flash erase cycles!!! > > Intolerable. > > I hope there is a mistake in my calculations or somewhere else. meanwhile the drive seems to continue self destruction: 9 Power_On_Hours 0x0000 --- --- --- Old_age Offline - 126 12 Power_Cycle_Count 0x0000 --- --- --- Old_age Offline - 36 198 Read_Sectors_Tot_Ct 0x0000 --- --- --- Old_age Offline - 96638645 199 Write_Sectors_Tot_Ct 0x0000 --- --- --- Old_age Offline - 115111795 200 Read_Commands_Tot_Ct 0x0000 --- --- --- Old_age Offline - 2073793 201 Write_Commands_Tot_Ct 0x0000 --- --- --- Old_age Offline - 2531426 208 Average_Erase_Count 0x0000 --- --- --- Old_age Offline - 88 209 Remaining_Lifetime_Perc 0x0000 --- --- --- Old_age Offline - 100 Since the last post 4319 MByte have been written (115111795 - 106676155) Sectors * 512 Bytes /Sector while 1024372 MByte have been erased! (88 - 72) * 64.023.257.088 Bytes So again more than 200 times more have been erased than have been written!!! (output of smartctl -a is appended). To put this factor into perspective: For some other SSD drives "write amplification multipliers" of as low as 1.1 have been reported/claimed! (I'd be happy with a factor of say 4 to 8 ) And I'm trying to treat the drive like a raw egg: - More than 5% of the total drive capacity were never assigned to a partition. - And were never written to. - And the root partition was mounted noatime (output of "mount" was shown in an earlier post). - And a 2.6.33 kernel is used. - And I have aligned the partitions to 2 MBytes: > fdisk -l /dev/sda Disk /dev/sda: 64.0 GB, 64023257088 bytes 128 heads, 32 sectors/track, 30528 cylinders Units = cylinders of 4096 * 512 = 2097152 bytes Disk identifier: 0x3d2797a4 Device Boot Start End Blocks Id System /dev/sda1 2 16386 33556480 83 Linux /dev/sda2 * 16387 28675 25167872 83 Linux Greetings, Frieder |
From: Christian F. <Chr...@t-...> - 2010-03-16 17:19:39
|
Frieder Ferlemann wrote: > Hi, > > just had a look into the output of smartd in /var/log/messages. > > Seems like the log mistakenly contains 198 Read_Sectors_Tot_Ct > as Offline uncorrectable sectors? > > Yes. The defaults 197/198 of -C/-U directives do not make sense here. > ... > > > It would be really nice if: > > 208 Average_Erase_Count > 209 Remaining_Lifetime_Perc > > would instead be reported in the log:) > > Try smartd.conf: /dev/sda -a -C 0 -U 0 -R 208 -R 209 BTW: > SMART Attributes Data Structure revision number: 16 > Vendor Specific SMART Attributes with Thresholds: > ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE > 1 Raw_Read_Error_Rate 0x0000 006 000 000 Old_age Offline - 0 > 9 Power_On_Hours 0x0000 --- --- --- Old_age Offline - 126 > ... > 209 Remaining_Lifetime_Perc 0x0000 --- --- --- Old_age Offline - 100 > 211 Unknown_Attribute 0x0000 000 000 000 Old_age Offline - 0 > 212 Unknown_Attribute 0x0000 000 000 000 Old_age Offline - 0 > 213 Unknown_Attribute 0x0000 000 000 000 Old_age Offline - 0 > Likely all attributes use the raw64 format. I would suggest to add -v 1,raw64 -v 211,raw64 -v 212,raw64 -v 213,raw64 to drivedb.h entry. Cheers, Christian |
From: Frieder F. <fri...@we...> - 2010-03-18 20:52:12
|
Hi Christian, Am 16.03.2010 18:19, schrieb Christian Franke: > Try smartd.conf: > > /dev/sda -a -C 0 -U 0 -R 208 -R 209 thanks! /var/log/messages looks like: Mar 17 23:20:45 lake smartd[2923]: Device: /dev/sda [SAT], SMART Usage Attribute: 208 Average_Erase_Count changed from 97 (Raw) to 98 (Raw) ... Mar 18 02:50:45 lake smartd[2923]: Device: /dev/sda [SAT], SMART Usage Attribute: 208 Average_Erase_Count changed from 98 (Raw) to 99 (Raw) ... Mar 18 13:20:45 lake smartd[2923]: Device: /dev/sda [SAT], SMART Usage Attribute: 208 Average_Erase_Count changed from 99 (Raw) to 100 (Raw) Mar 18 13:20:45 lake smartd[2923]: Device: /dev/sda [SAT], SMART Usage Attribute: 209 Remaining_Lifetime_Perc changed from 100 (Raw) to 99 (Raw) ... Mar 18 18:50:45 lake smartd[2923]: Device: /dev/sda [SAT], SMART Usage Attribute: 208 Average_Erase_Count changed from 100 (Raw) to 101 (Raw) ... Mar 18 20:50:45 lake smartd[2923]: Device: /dev/sda [SAT], SMART Usage Attribute: 208 Average_Erase_Count changed from 101 (Raw) to 102 (Raw) now. This would be a useful default setting for me:) >> SMART Attributes Data Structure revision number: 16 >> Vendor Specific SMART Attributes with Thresholds: >> ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE >> 1 Raw_Read_Error_Rate 0x0000 006 000 000 Old_age Offline - 0 >> 9 Power_On_Hours 0x0000 --- --- --- Old_age Offline - 126 >> ... >> 209 Remaining_Lifetime_Perc 0x0000 --- --- --- Old_age Offline - 100 >> 211 Unknown_Attribute 0x0000 000 000 000 Old_age Offline - 0 >> 212 Unknown_Attribute 0x0000 000 000 000 Old_age Offline - 0 >> 213 Unknown_Attribute 0x0000 000 000 000 Old_age Offline - 0 >> > > Likely all attributes use the raw64 format. I would suggest to add > > -v 1,raw64 -v 211,raw64 -v 212,raw64 -v 213,raw64 > > to drivedb.h entry. Yes, added, this gives: 1 Raw_Read_Error_Rate 0x0000 --- --- --- Old_age Offline - 6 9 Power_On_Hours 0x0000 --- --- --- Old_age Offline - 163 ... 209 Remaining_Lifetime_Perc 0x0000 --- --- --- Old_age Offline - 99 211 Unknown_Attribute 0x0000 --- --- --- Old_age Offline - 0 212 Unknown_Attribute 0x0000 --- --- --- Old_age Offline - 0 213 Unknown_Attribute 0x0000 --- --- --- Old_age Offline - 0 Another note from the "trying to treat the drive like a raw egg" section, I edited /etc/init.d/boot.local to contain: echo 0 > /sys/block/sdb/queue/rotational echo deadline > /sys/block/sda/queue/scheduler Greetings, Frieder |
From: Frieder F. <fri...@we...> - 2010-04-30 23:31:07
Attachments:
smartctl_20100426_1530.txt
|
Hi, here goes a report. And a call to action. After 325 hours of desktop use overall 105 times more bytes have been erased than have been written. Which is excessive. I'd be happy if someone would either confirm or disprove this finding. To help tracking this down I added a script which hourly records the status of the disk: smartctl -a /dev/sda | gzip >/tmp/smartctl_`date -u +%Y%m%d_%H%M`.txt.gz If you care (and have a disk with indilinx controller), please consider adding this as /etc/cron.hourly/smartctl And report back. (hourly data collected here is happily available on request) I would like to keep discussion here, because a) the expertise is here, b) the adequate tool is here (no screenshots from one or the other Windows application), c) the perceived problem would likely affect SSDs from different vendors and d) I trust mail much more than vendor forums(*) Please help track this down. Greetings, Frieder (*) To me the Super Talent forum seems to show indicators of censorship: Lookup the topics "1916 CG firmware an Linux" (bart3005 Wed Mar 03, 2010 7:25 am) or "AS SSD Benchmark" (i3m Sat Jan 23, 2010 12:28 am) at: http://supertalent.com/home/forum/viewforum.php?f=40 For the first topic no posts are shown at all. For the second topic only 2 posts are shown while the forum software indicates that there have been more than 10 postings. |
From: Frieder F. <fri...@we...> - 2010-07-29 13:47:32
|
Hi, Am 16.03.2010 18:19, schrieb Christian Franke: >> 211 Unknown_Attribute 0x0000 000 000 000 Old_age >> Offline - 0 >> 212 Unknown_Attribute 0x0000 000 000 000 Old_age >> Offline - 0 >> 213 Unknown_Attribute 0x0000 000 000 000 Old_age >> Offline - 0 >> > > Likely all attributes use the raw64 format. I would suggest to add > > -v 1,raw64 -v 211,raw64 -v 212,raw64 -v 213,raw64 > > to drivedb.h entry. Hi, as of yesterday the meaning of 211 and 212 for indilinx based drives is published here: http://www.ocztechnologyforum.com/forum/showthread.php?75788-SMART-Attributes-for-Indilinx-based-drives-%28Agility-Vertex-Solid2%29 211 SATA Error Count CRC 212 SATA Error Count Handshake :) Greetings, Frieder |