Page 1 of 1

Buffer I/O error on device sdb1 - Problem

Posted: 02. Mar 2009 22:22
by [_ch_]
Hallo

Ich bin neu in diesem Board allerding kein absoluter Linux neuling. Ich habe einen Linux Server mit Debian Etch (c't VDR 6.2). Darauf läuft hauptsächllich VDR mit 2 DVB-S Karten.

Code: Select all

Meine Hardware:
* Intel Pentium 3 866Mhz
* Elitegroup P6VAP-A+
* 384 MB SD-RAM
* GeForce TNT2
* Terratec Cintergy 1200 DVB-S
* WinTV Nova-s Plus
* Promise Fasttrek TX2300 SATA Controller (2 SATA Ports)
* 1,5 TB Seagate Barracuda 7200.11 (Firmware SD1B, angeblich nun Bugfree) SATA
* 60 GB Seagate SATA
* 250 GB Samstung IDE
* 160 GB WD IDE

Die Beiden SATA Festplatten hängen am Fasttrek!

Softwaremäßig  hab ich
Debian Etch mit so weit ich weiß allen Updates
VDR 1.6.0.2 mit einigen Plugins
zusätzlich ein apache Server
installiert

Wenn ich nun boote habe ich vollgendes Problem:
Öfters bekomme ich im dmesg

Code: Select all

Buffer I/O error on device sdb1, logical block xxx 
sdb ist meine Barracuda 1,5TB wo eine 1,37TB Ext3 Partition hat.
davon sind etwa 800GB belegt.

dmesg | grep 'sdb'

Code: Select all

SCSI device sdb: 2930277168 512-byte hdwr sectors (1500302 MB)
sdb: Write Protect is off
sdb: Mode Sense: 00 3a 00 00
SCSI device sdb: drive cache: write back
SCSI device sdb: 2930277168 512-byte hdwr sectors (1500302 MB)
sdb: Write Protect is off
sdb: Mode Sense: 00 3a 00 00
SCSI device sdb: drive cache: write back
 sdb: sdb1
sd 1:0:0:0: Attached scsi disk sdb
sdb: Current: sense key: Aborted Command
end_request: I/O error, dev sdb, sector 270639
Buffer I/O error on device sdb1, logical block 135288
Buffer I/O error on device sdb1, logical block 135289
Buffer I/O error on device sdb1, logical block 135290
Buffer I/O error on device sdb1, logical block 135291
Buffer I/O error on device sdb1, logical block 135292
Buffer I/O error on device sdb1, logical block 135293
Buffer I/O error on device sdb1, logical block 135294
Buffer I/O error on device sdb1, logical block 135295
Buffer I/O error on device sdb1, logical block 135296
Buffer I/O error on device sdb1, logical block 135297
EXT3 FS on sdb1, internal journal
Wenn ich boote bleibt er fast immer hängen und sagt, um den Start fortzusetzen muss ich STRG+D drücken; auf sdb konnte das Filesystem nicht überprüft werden, ich solle es manuell nachholen.

Wenn ich jetzt ein

Code: Select all

fsck /dev/sdb1
mache bekomme ich folgende Meldung:

Code: Select all

vdr:~# fsck /dev/sdb1
fsck 1.40-WIP (14-Nov-2006)
e2fsck 1.40-WIP (14-Nov-2006)
/dev/sdb1 enthält ein fehlerhaftes Dateisystem, Prüfung erzwungen.
Durchgang 1: Prüfe Inodes, Blocks, und Größen
Lesefehler - Block 820291 &#40;Attempt to read block from filesystem resulted in short read&#41; während Inode-Scan  Ignoriere Fehler<j>?
bzw. wenn ich mit Y bestätige:

Code: Select all

vdr&#58;~# fsck /dev/sdb1
fsck 1.40-WIP &#40;14-Nov-2006&#41;
e2fsck 1.40-WIP &#40;14-Nov-2006&#41;
/dev/sdb1 enthält ein fehlerhaftes Dateisystem, Prüfung erzwungen.
Durchgang 1&#58; Prüfe Inodes, Blocks, und Größen
Lesefehler - Block 1212449 &#40;Attempt to read block from filesystem resulted in short read&#41; während Inode-Scan  Ignoriere Fehler<j>? ja

Rückschreiben erzwingen<j>? ja

Lesefehler - Block 1212450 &#40;Attempt to read block from filesystem resulted in short read&#41; während Inode-Scan  Ignoriere Fehler<j>? ja

Rückschreiben erzwingen<j>?
Was mich sehr wundert ist, dass ich immer bei unterschiedlichen Blöcken das Problem habe.
So wie ich das sehe dürfte es kein Hardware-Defekt sein, doch ich bin mir nich sicher.
Würde eher darauf tippen dass die Partitionstabelle defekt ist (oder Inode Table?)
Doch hier möchte ich nicht herumprobieren, da wie oben beschrieben etwa 800GB TV Aufnahmen liegen, die ich ungern verliehren würde

Wenn ihr irgendwelche Logs braucht, meldet euch bitte.
Das relevante aus dem dmesg hab ich raus.

Habt ihr einen Tipp was ich da machen könnte?

Schon mal Danke

Gruß
[_ch_]

Posted: 02. Mar 2009 22:54
by Janka
Gib mal den kompletten Log zwischen mehreren "Buffer I/O error"-Meldungen aus. Da steht auch noch interessantes aus dem SCSI (SATA)-Subsystem drin...

Janka

Posted: 03. Mar 2009 11:32
by hjb
Hi!

Das ist ganz klar eine sterbende Festplatte. Ich würde die Daten auf eine neue Platte kopieren, bevor es zu spät ist.

Das Problem kann aber auch wieder verschwinden. Da jede Platte intern Reserve-Sektoren hat, die automatisch genutzt werden, wenn ein Sektor als fehlerhaft erkannt wird, sind irgendwann alle fehlerhaften Sektoren ersetzt und es tritt kein Fehler mehr auf. Freilich weiß man nie, wie lange...

Grüße,
hjb

Posted: 04. Mar 2009 22:01
by [_ch_]
Hallo

Danke für euere Antworten. Die Platte ist fast neu (seit Weihnachten). Die dmesg oder syslog sagen nur das selbe:

Code: Select all

Mar  2 20&#58;42&#58;19 vdr kernel&#58; EXT3 FS on sda1, internal journal
Mar  2 20&#58;42&#58;19 vdr kernel&#58; loop&#58; loaded &#40;max 8 devices&#41;
Mar  2 20&#58;42&#58;19 vdr kernel&#58; Non-volatile memory driver v1.2
Mar  2 20&#58;42&#58;19 vdr kernel&#58; device-mapper&#58; ioctl&#58; 4.7.0-ioctl &#40;2006-06-24&#41; initialised&#58; dm-devel@redhat.com
Mar  2 20&#58;42&#58;19 vdr kernel&#58; ata2&#58; no sense translation for status&#58; 0x50
Mar  2 20&#58;42&#58;19 vdr kernel&#58; ata2&#58; translated ATA stat/err 0x50/00 to SCSI SK/ASC/ASCQ 0xb/00/00
Mar  2 20&#58;42&#58;19 vdr kernel&#58; ata2&#58; status=0x50 &#123; DriveReady SeekComplete &#125;
Mar  2 20&#58;42&#58;19 vdr kernel&#58; ata2&#58; no sense translation for status&#58; 0x50
Mar  2 20&#58;42&#58;19 vdr kernel&#58; ata2&#58; translated ATA stat/err 0x50/00 to SCSI SK/ASC/ASCQ 0xb/00/00
Mar  2 20&#58;42&#58;19 vdr kernel&#58; ata2&#58; status=0x50 &#123; DriveReady SeekComplete &#125;
Mar  2 20&#58;42&#58;19 vdr kernel&#58; ata2&#58; no sense translation for status&#58; 0x50
Mar  2 20&#58;42&#58;19 vdr kernel&#58; ata2&#58; translated ATA stat/err 0x50/00 to SCSI SK/ASC/ASCQ 0xb/00/00
Mar  2 20&#58;42&#58;19 vdr kernel&#58; ata2&#58; status=0x50 &#123; DriveReady SeekComplete &#125;
Mar  2 20&#58;42&#58;19 vdr kernel&#58; ata2&#58; no sense translation for status&#58; 0x50
Mar  2 20&#58;42&#58;19 vdr kernel&#58; ata2&#58; translated ATA stat/err 0x50/00 to SCSI SK/ASC/ASCQ 0xb/00/00
Mar  2 20&#58;42&#58;19 vdr kernel&#58; ata2&#58; status=0x50 &#123; DriveReady SeekComplete &#125;
Mar  2 20&#58;42&#58;19 vdr kernel&#58; ata2&#58; no sense translation for status&#58; 0x50
Mar  2 20&#58;42&#58;19 vdr kernel&#58; ata2&#58; translated ATA stat/err 0x50/00 to SCSI SK/ASC/ASCQ 0xb/00/00
Mar  2 20&#58;42&#58;19 vdr kernel&#58; ata2&#58; status=0x50 &#123; DriveReady SeekComplete &#125;
Mar  2 20&#58;42&#58;19 vdr kernel&#58; ata2&#58; no sense translation for status&#58; 0x50
Mar  2 20&#58;42&#58;19 vdr kernel&#58; ata2&#58; translated ATA stat/err 0x50/00 to SCSI SK/ASC/ASCQ 0xb/00/00
Mar  2 20&#58;42&#58;19 vdr kernel&#58; ata2&#58; status=0x50 &#123; DriveReady SeekComplete &#125;
Mar  2 20&#58;42&#58;19 vdr kernel&#58; sd 1&#58;0&#58;0&#58;0&#58; SCSI error&#58; return code = 0x08000002
Mar  2 20&#58;42&#58;19 vdr kernel&#58; sdb&#58; Current&#58; sense key&#58; Aborted Command
Mar  2 20&#58;42&#58;19 vdr kernel&#58;     Additional sense&#58; No additional sense information
Mar  2 20&#58;42&#58;19 vdr kernel&#58; end_request&#58; I/O error, dev sdb, sector 270639
Mar  2 20&#58;42&#58;19 vdr kernel&#58; Buffer I/O error on device sdb1, logical block 135288
Mar  2 20&#58;42&#58;19 vdr kernel&#58; Buffer I/O error on device sdb1, logical block 135289
Mar  2 20&#58;42&#58;19 vdr kernel&#58; end_request&#58; I/O error, dev sdb, sector 270639
Mar  2 20&#58;42&#58;19 vdr kernel&#58; Buffer I/O error on device sdb1, logical block 135288
Mar  2 20&#58;42&#58;19 vdr kernel&#58; Buffer I/O error on device sdb1, logical block 135289
Mar  2 20&#58;42&#58;19 vdr kernel&#58; Buffer I/O error on device sdb1, logical block 135290
Mar  2 20&#58;42&#58;19 vdr kernel&#58; Buffer I/O error on device sdb1, logical block 135291
Mar  2 20&#58;42&#58;19 vdr kernel&#58; Buffer I/O error on device sdb1, logical block 135292
Mar  2 20&#58;42&#58;19 vdr kernel&#58; Buffer I/O error on device sdb1, logical block 135293
Mar  2 20&#58;42&#58;19 vdr kernel&#58; Buffer I/O error on device sdb1, logical block 135294
Mar  2 20&#58;42&#58;19 vdr kernel&#58; Buffer I/O error on device sdb1, logical block 135295
Mar  2 20&#58;42&#58;19 vdr kernel&#58; Buffer I/O error on device sdb1, logical block 135296
Mar  2 20&#58;42&#58;19 vdr kernel&#58; Buffer I/O error on device sdb1, logical block 135297
Mar  2 20&#58;42&#58;19 vdr kernel&#58; kjournald starting.  Commit interval 5 seconds
Mar  2 20&#58;42&#58;19 vdr kernel&#58; EXT3 FS on sda4, internal journal
Mar  2 20&#58;42&#58;19 vdr kernel&#58; EXT3-fs&#58; mounted filesystem with ordered data mode.
Mar  2 20&#58;42&#58;19 vdr kernel&#58; kjournald starting.  Commit interval 5 seconds
Mar  2 20&#58;42&#58;19 vdr kernel&#58; EXT3 FS on hdc1, internal journal
Mar  2 20&#58;42&#58;19 vdr kernel&#58; EXT3-fs&#58; mounted filesystem with ordered data mode.
Mar  2 20&#58;42&#58;19 vdr kernel&#58; kjournald starting.  Commit interval 5 seconds
Mar  2 20&#58;42&#58;19 vdr kernel&#58; EXT3 FS on hdd1, internal journal
Mar  2 20&#58;42&#58;19 vdr kernel&#58; EXT3-fs&#58; mounted filesystem with ordered data mode.
Mar  2 20&#58;42&#58;19 vdr kernel&#58; kjournald starting.  Commit interval 5 seconds
Mar  2 20&#58;42&#58;19 vdr kernel&#58; EXT3-fs warning&#58; mounting fs with errors, running e2fsck is recommended
Mar  2 20&#58;42&#58;19 vdr kernel&#58; EXT3 FS on sdb1, internal journal
Mar  2 20&#58;42&#58;19 vdr kernel&#58; EXT3-fs&#58; mounted filesystem with ordered data mode.
Mar  2 20&#58;42&#58;19 vdr kernel&#58; kjournald starting.  Commit interval 5 seconds
Mar  2 20&#58;42&#58;19 vdr kernel&#58; EXT3 FS on sda2, internal journal
Mar  2 20&#58;42&#58;19 vdr kernel&#58; EXT3-fs&#58; mounted filesystem with ordered data mode.
Mar  2 20&#58;42&#58;19 vdr kernel&#58; e1000&#58; eth0&#58; e1000_watchdog&#58; NIC Link is Up 100 Mbps Full Duplex
smartctl funktioniert nicht, er meldet die Platte unterstüzt kein SMART.
Vermutlich hängt es aus der Kombination sehr alte Hardware mit einen SATA Controller zusammen. Vorerst lasse ich den Server aus und werde bei gelegenheit die Platte in meinen Desktop mit Ubuntu 8.10 einbauen und sehen was smartctl da meint bzw. ob er dort auch nicht booten kann.

Ein Kollege meinte, es könne auch am alten Kernel (2.6.18-5) liegen. Mal schauen was mein Ubuntu zur Platte meint.
Gab mir auch den Vorschlag ein "dd if=/dev/zero of=/dev/sdb" machen. Wann er nicht die Meldung "1370GB Written in xxxx Seconds" gibt, dann ist wirklich was faul.
davor natürlich backupen =)

Ich werde euch auf dem laufenden halten

Gruß
[_ch_]

Posted: 05. Mar 2009 12:10
by hjb
Hi!

Die Platte muss SMART unterstützen. Die könnte allerdings abgeschaltet sein, lässt sich aber mit smartctl aktivieren. Evtl. musst du die richtige Option für smatrtctl angeben, meist ist das "-d ata".

Ich habe zwar keine Erfahrungswerte, ob Kabeldefekte bei SATA auftreten können, aber hast du mal das Kabel getauscht?

Grüße,
hjb

Posted: 07. Mar 2009 23:28
by [_ch_]
Hallo!

habe hier mal ein paar neue Infos:

die Option "-d ata" hat ncihts gebracht.
Habe die Platte in meinem Desktop gebaut und unter ubuntu smartctl gestartet. Vorerst nur der SHORT-Test weil um diese Zeit ich keine Lust habe den Long (255min) fertig laufen zu lassen :D werde ich aber morgen nachholen:

also der Shorttest:

Code: Select all

christoph@christoph-desktop&#58;~$ sudo smartctl --test=short /dev/sda --all
smartctl version 5.38 &#91;i686-pc-linux-gnu&#93; Copyright &#40;C&#41; 2002-8 Bruce Allen
Home page is http&#58;//smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Device Model&#58;     ST31500341AS
Serial Number&#58;    9VS0C2PD
Firmware Version&#58; SD1B
User Capacity&#58;    1.500.301.910.016 bytes
Device is&#58;        Not in smartctl database &#91;for details use&#58; -P showall&#93;
ATA Version is&#58;   8
ATA Standard is&#58;  ATA-8-ACS revision 4
Local Time is&#58;    Sat Mar  7 23&#58;02&#58;37 2009 CET
SMART support is&#58; Available - device has SMART capability.
SMART support is&#58; Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result&#58; PASSED

General SMART Values&#58;
Offline data collection status&#58;  &#40;0x82&#41;	Offline data collection activity
					was completed without error.
					Auto Offline Data Collection&#58; Enabled.
Self-test execution status&#58;      &#40;  25&#41;	The self-test routine was aborted by
					the host.
Total time to complete Offline 
data collection&#58; 		 &#40; 609&#41; seconds.
Offline data collection
capabilities&#58; 			 &#40;0x7b&#41; 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&#58;            &#40;0x0003&#41;	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability&#58;        &#40;0x01&#41;	Error logging supported.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time&#58; 	 &#40;   1&#41; minutes.
Extended self-test routine
recommended polling time&#58; 	 &#40; 255&#41; minutes.
Conveyance self-test routine
recommended polling time&#58; 	 &#40;   2&#41; minutes.
SCT capabilities&#58; 	       &#40;0x103b&#41;	SCT Status supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number&#58; 10
Vendor Specific SMART Attributes with Thresholds&#58;
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   109   100   006    Pre-fail  Always       -       21345405
  3 Spin_Up_Time            0x0003   095   093   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       99
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       3
  7 Seek_Error_Rate         0x000f   058   052   030    Pre-fail  Always       -       25774674157
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       754
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       98
184 Unknown_Attribute       0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Unknown_Attribute       0x0032   100   099   000    Old_age   Always       -       12885098500
189 High_Fly_Writes         0x003a   074   074   000    Old_age   Always       -       26
190 Airflow_Temperature_Cel 0x0022   067   065   045    Old_age   Always       -       33 &#40;Lifetime Min/Max 24/33&#41;
194 Temperature_Celsius     0x0022   033   040   000    Old_age   Always       -       33 &#40;0 13 0 0&#41;
195 Hardware_ECC_Recovered  0x001a   034   032   000    Old_age   Always       -       21345405
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0

SMART Error Log Version&#58; 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime&#40;hours&#41;  LBA_of_first_error
# 1  Extended offline    Aborted by host               90%       754         -
# 2  Short offline       Completed without error       00%       754         -
# 3  Short offline       Aborted by host               40%       754         -
# 4  Short offline       Completed without error       00%       754         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags &#40;0x0&#41;&#58;
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

=== START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION ===
Sending command&#58; "Execute SMART Short self-test routine immediately in off-line mode".
Drive command "Execute SMART Short self-test routine immediately in off-line mode" successful.
Testing has begun.
Please wait 1 minutes for test to complete.
Test will complete after Sat Mar  7 23&#58;03&#58;37 2009

Use smartctl -X to abort test.
christoph@christoph-desktop&#58;~$ 
Kann mir jemand sagen was die werte bedeuten?
Ich kenne mich mit Smart nicht aus...

Werde morgen den Long-Test nachreichen

Schönes Wochenende

Gruß
[_ch_][/list]

Posted: 08. Mar 2009 12:57
by Janka
Die wichtigste Zeile:
[_ch_] wrote:

Code: Select all

  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       3
Der Raw Value von "Reallocated_Sector_Ct" sollte immer bei "0" sein, ansonsten hat die Platte schon Stellen, bei der sie selbst annimmt, dass diese Stellen der Oberfläche sich niemals mehr benutzen lassen. 3 mag sich zwar wenig anhören, aber nach dem "long test" werden das sicher mehr. Heile Platten haben hier immer "0".

Janka

Posted: 08. Mar 2009 20:31
by [_ch_]
Sodala der LONG-Test ist da:

hat sich aber nicht viel geändert:

Code: Select all

christoph@christoph-desktop&#58;~$ sudo smartctl /dev/sda --all
&#91;sudo&#93; password for christoph&#58; 
smartctl version 5.38 &#91;i686-pc-linux-gnu&#93; Copyright &#40;C&#41; 2002-8 Bruce Allen
Home page is http&#58;//smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Device Model&#58;     ST31500341AS
Serial Number&#58;    9VS0C2PD
Firmware Version&#58; SD1B
User Capacity&#58;    1.500.301.910.016 bytes
Device is&#58;        Not in smartctl database &#91;for details use&#58; -P showall&#93;
ATA Version is&#58;   8
ATA Standard is&#58;  ATA-8-ACS revision 4
Local Time is&#58;    Sun Mar  8 20&#58;28&#58;42 2009 CET
SMART support is&#58; Available - device has SMART capability.
SMART support is&#58; Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result&#58; PASSED

General SMART Values&#58;
Offline data collection status&#58;  &#40;0x82&#41;	Offline data collection activity
					was completed without error.
					Auto Offline Data Collection&#58; Enabled.
Self-test execution status&#58;      &#40;   0&#41;	The previous self-test routine completed
					without error or no self-test has ever 
					been run.
Total time to complete Offline 
data collection&#58; 		 &#40; 609&#41; seconds.
Offline data collection
capabilities&#58; 			 &#40;0x7b&#41; 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&#58;            &#40;0x0003&#41;	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability&#58;        &#40;0x01&#41;	Error logging supported.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time&#58; 	 &#40;   1&#41; minutes.
Extended self-test routine
recommended polling time&#58; 	 &#40; 255&#41; minutes.
Conveyance self-test routine
recommended polling time&#58; 	 &#40;   2&#41; minutes.
SCT capabilities&#58; 	       &#40;0x103b&#41;	SCT Status supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number&#58; 10
Vendor Specific SMART Attributes with Thresholds&#58;
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   115   100   006    Pre-fail  Always       -       97967819
  3 Spin_Up_Time            0x0003   094   093   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       100
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       3
  7 Seek_Error_Rate         0x000f   058   052   030    Pre-fail  Always       -       25774710645
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       766
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       99
184 Unknown_Attribute       0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Unknown_Attribute       0x0032   100   099   000    Old_age   Always       -       12885098500
189 High_Fly_Writes         0x003a   074   074   000    Old_age   Always       -       26
190 Airflow_Temperature_Cel 0x0022   063   060   045    Old_age   Always       -       37 &#40;Lifetime Min/Max 13/40&#41;
194 Temperature_Celsius     0x0022   037   040   000    Old_age   Always       -       37 &#40;0 13 0 0&#41;
195 Hardware_ECC_Recovered  0x001a   034   032   000    Old_age   Always       -       97967819
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0

SMART Error Log Version&#58; 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime&#40;hours&#41;  LBA_of_first_error
# 1  Extended offline    Completed without error       00%       765         -
# 2  Extended offline    Completed without error       00%       761         -
# 3  Short offline       Completed without error       00%       754         -
# 4  Extended offline    Aborted by host               90%       754         -
# 5  Short offline       Completed without error       00%       754         -
# 6  Short offline       Aborted by host               40%       754         -
# 7  Short offline       Completed without error       00%       754         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags &#40;0x0&#41;&#58;
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

christoph@christoph-desktop&#58;~$ 
Sind immer noch bei 3 Fehlerhaften stellen.
Ist dies ein Grund zur Reklamation? oder innerhalb der Toleranz wie z.B. Pixelfehler gemäß der Pixelfehlerklasse?

Gruß
[_ch_][/code]

Posted: 08. Mar 2009 22:44
by Janka
Ja, etwas anderes als Null Fehler bei Auslieferung ist ein Reklamationsgrund. Pixelfehler bei Displays streng genommen übrigens auch, aber da nimmt man, was man kriegt. Der Platte, die du das hast, würde ich keine wichtigen Daten anvertrauen.

Janka

sie ist gestorben!!!!!!

Posted: 19. Mar 2009 21:50
by gast
hy wer kann mir da weiter helfen???????

pc bootet win xp nicht mehr ganz hoch .......so wie ich dessehe ist meine festplatte gestorben ..... oder??????

Complete error log:

SMART Error Log Version: 1
ATA Error Count: 183 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 183 occurred at disk power-on lifetime: 344 hours (14 days + 8 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 27 e4 21 4a e0 Error: UNC 39 sectors at LBA = 0x004a21e4 = 4858340

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 03 40 cb 21 4a e0 00 00:12:17.114 READ DMA EXT
25 03 01 00 00 00 e0 00 00:12:06.548 READ DMA EXT
25 03 01 00 00 00 e0 00 00:12:05.934 READ DMA EXT
25 03 01 00 00 00 e0 00 00:12:05.933 READ DMA EXT
ef 03 22 e4 21 4a e0 00 00:12:05.920 SET FEATURES [Set transfer mode]

Error 182 occurred at disk power-on lifetime: 344 hours (14 days + 8 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 27 e4 21 4a e0 Error: UNC 39 sectors at LBA = 0x004a21e4 = 4858340

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 03 40 cb 21 4a e0 00 00:12:17.114 READ DMA EXT
25 03 01 00 00 00 e0 00 00:12:06.548 READ DMA EXT
25 03 01 00 00 00 e0 00 00:12:05.934 READ DMA EXT
25 03 01 00 00 00 e0 00 00:12:05.933 READ DMA EXT
ef 03 22 e4 21 4a e0 00 00:12:05.920 SET FEATURES [Set transfer mode]

Error 181 occurred at disk power-on lifetime: 344 hours (14 days + 8 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 27 e4 21 4a e0 Error: UNC 39 sectors at LBA = 0x004a21e4 = 4858340

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 03 40 cb 21 4a e0 00 00:11:44.282 READ DMA EXT
25 03 01 00 00 00 e0 00 00:12:06.548 READ DMA EXT
25 03 01 00 00 00 e0 00 00:12:05.934 READ DMA EXT
25 03 01 00 00 00 e0 00 00:12:05.933 READ DMA EXT
35 03 08 3f 00 5e e0 00 00:12:05.920 WRITE DMA EXT

Error 180 occurred at disk power-on lifetime: 344 hours (14 days + 8 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 27 e4 21 4a e0 Error: UNC 39 sectors at LBA = 0x004a21e4 = 4858340

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 03 40 cb 21 4a e0 00 00:11:44.282 READ DMA EXT
25 03 01 00 00 00 e0 00 00:11:44.280 READ DMA EXT
25 03 01 00 00 00 e0 00 00:11:44.277 READ DMA EXT
25 03 01 00 00 00 e0 00 00:11:44.275 READ DMA EXT
ef 03 22 e6 21 4a e0 00 00:11:44.273 SET FEATURES [Set transfer mode]

Error 179 occurred at disk power-on lifetime: 344 hours (14 days + 8 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 25 e6 21 4a e0 Error: UNC 37 sectors at LBA = 0x004a21e6 = 4858342

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 03 40 cb 21 4a e0 00 00:11:44.282 READ DMA EXT
25 03 40 8b 21 4a e0 00 00:11:44.280 READ DMA EXT
25 03 0c 7f 21 4a e0 00 00:11:44.277 READ DMA EXT
25 03 34 4b 5e 93 e0 00 00:11:44.275 READ DMA EXT
25 03 40 0b 5e 93 e0 00 00:11:44.273 READ DMA EXT

Posted: 20. Mar 2009 10:41
by Janka
Ja, die Festplatte ist hin. Bester Hinweis:
40 51 25 e6 21 4a e0 Error: UNC 37 sectors at LBA = 0x004a21e6 = 4858342
Unabhängig davon ist dies aber ein Forum, in dem es um Linux geht.

Janka