Du bist nicht angemeldet.

#1 17.02.2017 12:17:48

mumpf
Mitglied

smartctl: read failure, mit badblocks noch 'was zu reissen?

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     0x002f   199   199   051    Pre-fail  Always       -       21207
  3 Spin_Up_Time            0x0027   177   174   021    Pre-fail  Always       -       2150
  4 Start_Stop_Count        0x0032   092   092   000    Old_age   Always       -       8382
  5 Reallocated_Sector_Ct   0x0033   188   188   140    Pre-fail  Always       -       106
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   089   089   000    Old_age   Always       -       8096
10 Spin_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
11 Calibration_Retry_Count 0x0032   100   100   000    Old_age   Always       -       0
12 Power_Cycle_Count       0x0032   094   094   000    Old_age   Always       -       6032
191 G-Sense_Error_Rate      0x0032   001   001   000    Old_age   Always       -       2657
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       209
193 Load_Cycle_Count        0x0032   154   154   000    Old_age   Always       -       138959
194 Temperature_Celsius     0x0022   119   101   000    Old_age   Always       -       28
196 Reallocated_Event_Count 0x0032   199   118   000    Old_age   Always       -       1
197 Current_Pending_Sector  0x0032   197   001   000    Old_age   Always       -       467
198 Offline_Uncorrectable   0x0030   100   253   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   100   253   000    Old_age   Offline      -       0

Bei einer ca. 6 Jahre alten Festplatte habe ich massive Leseprobleme, Zu Beginn konnte ich kein backup mehr erstellen (Windows 7), Nach chkdsk /r /f liess sich die Platte, auch eingebaut in einen anderen Rechner, überhaupt nicht mehr starten, Die Erkennung als sata-Platte misslang. Hier

 
badblocks -f -t 0 -v -e 1000000 -b 4096 -s -w /dev/sdb
Nach defekten Blöcken wird gesucht (Lesen+Schreiben-Modus)
Von Block 0 bis 183143645
Mit Muster 0x wird getestet00:   0.00% erledigt, 0:00 verstrichen. (0/0/0 Fehler^C  1.07% erledigt, 1:26:02 verstrichen. (0/0/0 Fehler)

Interrupted at block 1952192
root@miyolinux:/home/userxy# mke2fs  -b 4096 -v /dev/sdb
mke2fs 1.42.12 (29-Aug-2014)
Dateisystemtypen für das Aufschlüsseln von mke2fs.conf: 'ext2'
Dateisystembezeichnung=
OS-Typ: Linux
Blockgröße=4096 (log=2)
Fragmentgröße=4096 (log=2)
Stride=0 Blöcke, Stripebreite=0 Blöcke
45793280 Inodes, 183143646 Blöcke
9157182 Blöcke (5.00%) reserviert für den Superuser
Erster Datenblock=0
Maximale Dateisystem-Blöcke=4294967296
5590 Blockgruppen
32768 Blöcke pro Gruppe, 32768 Fragmente pro Gruppe
8192 Inodes pro Gruppe
UUID des Dateisystems: 3c30cbc7-c34c-48cf-a510-744b419cd677
Superblock-Sicherungskopien gespeichert in den Blöcken: 
	32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 
	4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968, 
	102400000

beim Anfordern von Speicher für die Gruppentabellen: erledigt                        
Inode-Tabellen werden geschrieben: erledigt                        
ext2fs_mkdir: Der Versuch, einen Block vom Dateisystem zu lesen, endete in kurzem Lesen beim Erstellen des Wurzelverzeichnisses
root@miyolinux:/home/userxy# cfdisk /dev/sdb
cfdisk: cannot open /dev/sdb: Eingabe-/Ausgabefehler
root@miyolinux:/home/userxy# smartctl -t short /dev/sdb
smartctl 6.4 2014-10-07 r4002 [x86_64-linux-3.16.0-4-amd64] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION ===
Sending command: "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 2 minutes for test to complete.
Test will complete after Fri Feb 17 08:02:38 2017

Use smartctl -X to abort test.

root@miyolinux:/home/userxy# smartctl -a /dev/sdb
smartctl 6.4 2014-10-07 r4002 [x86_64-linux-3.16.0-4-amd64] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Scorpio Blue Serial ATA (AF)
Device Model:     WDC WD7500BPVT-22HXZT3
Serial Number:    WD-WXL1E61NDFF3
LU WWN Device Id: 5 0014ee 656ccbe3a
Firmware Version: 01.01A01
User Capacity:    750'156'374'016 bytes [750 GB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS (minor revision not indicated)
SATA Version is:  SATA 2.6, 3.0 Gb/s
Local Time is:    Fri Feb 17 08:07:48 2017 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:      ( 248)	Self-test routine in progress...
					80% of test remaining.
Total time to complete Offline 
data collection: 		(17160) seconds.
Offline data collection
capabilities: 			 (0x7b) 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:            (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: 	 ( 169) minutes.
Conveyance self-test routine
recommended polling time: 	 (   5) minutes.
SCT capabilities: 	       (0x7035)	SCT Status supported.
					SCT Feature Control supported.
					SCT Data Table supported.

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     0x002f   199   199   051    Pre-fail  Always       -       21207
  3 Spin_Up_Time            0x0027   177   174   021    Pre-fail  Always       -       2150
  4 Start_Stop_Count        0x0032   092   092   000    Old_age   Always       -       8382
  5 Reallocated_Sector_Ct   0x0033   188   188   140    Pre-fail  Always       -       106
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   089   089   000    Old_age   Always       -       8096
 10 Spin_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   100   100   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   094   094   000    Old_age   Always       -       6032
191 G-Sense_Error_Rate      0x0032   001   001   000    Old_age   Always       -       2657
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       209
193 Load_Cycle_Count        0x0032   154   154   000    Old_age   Always       -       138959
194 Temperature_Celsius     0x0022   119   101   000    Old_age   Always       -       28
196 Reallocated_Event_Count 0x0032   199   118   000    Old_age   Always       -       1
197 Current_Pending_Sector  0x0032   197   001   000    Old_age   Always       -       467
198 Offline_Uncorrectable   0x0030   100   253   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   100   253   000    Old_age   Offline      -       0

SMART Error Log Version: 1
ATA Error Count: 161 (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 161 occurred at disk power-on lifetime: 8086 hours (336 days + 22 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
  -- -- -- -- -- -- --
  01 51 08 00 00 00 e0  Error: AMNF 8 sectors at LBA = 0x00000000 = 0

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 00 00 00 e0 08      00:04:20.619  READ DMA
  ec 00 00 00 00 00 a0 08      00:04:20.610  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 08      00:04:20.602  SET FEATURES [Set transfer mode]

Error 160 occurred at disk power-on lifetime: 8086 hours (336 days + 22 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
  -- -- -- -- -- -- --
  01 51 08 00 00 00 e0  Error: AMNF 8 sectors at LBA = 0x00000000 = 0

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 00 00 00 e0 08      00:04:04.964  READ DMA
  ec 00 01 00 00 00 00 08      00:03:54.057  IDENTIFY DEVICE

Error 159 occurred at disk power-on lifetime: 8086 hours (336 days + 22 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
  -- -- -- -- -- -- --
  01 51 08 00 00 00 e0  Error: AMNF 8 sectors at LBA = 0x00000000 = 0

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 00 00 00 e0 08      00:03:44.370  READ DMA
  ec 00 00 00 00 00 a0 08      00:03:44.361  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 08      00:03:44.354  SET FEATURES [Set transfer mode]

Error 158 occurred at disk power-on lifetime: 8086 hours (336 days + 22 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
  -- -- -- -- -- -- --
  01 51 08 00 00 00 e0  Error: AMNF 8 sectors at LBA = 0x00000000 = 0

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 00 00 00 e0 08      00:03:40.465  READ DMA
  ec 00 01 00 00 00 00 08      00:03:38.984  IDENTIFY DEVICE

Error 157 occurred at disk power-on lifetime: 8086 hours (336 days + 22 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
  -- -- -- -- -- -- --
  01 51 08 00 00 00 e0  Error: AMNF 8 sectors at LBA = 0x00000000 = 0

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 00 00 00 e0 08      00:03:34.459  READ DMA
  ec 00 00 00 00 00 a0 08      00:03:34.450  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 08      00:03:34.443  SET FEATURES [Set transfer mode]

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed: read failure       90%      8085         57353089
# 2  Short offline       Completed: read failure       90%      8085         57353089
# 3  Short offline       Completed: read failure       90%      8084         57353088

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 (0x0):
  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.

nun die Schritte, die ich unternommen habe, damit die bad sectors wieder  werden können. Denke aber, die Platte ist hinüber, aufgrund der hohen raw-value Werte bei 1, 5, 191 und 197. Den badblocks Befehl habe ich abgebrochen, da ich mich nicht tagelang (1.07%  in 1:26:02) auf das Resultat warten konnte und weil es sich - wahrscheinlich (?) nicht rentiert. Das WD Programm ist beim Kurztest abgestürzt. Das HP Bios HD checkprogramm hat gemeldet, die Platte müsse ersetzt werden, aber so schnell möchte ich nicht aufgeben. Falls die Wahrscheinlichkeit > 50% ist, dass die Platte noch ein paar Jährchen laufen kann, würde ich einen laptop auch ein paar Tage lang sich damit befassen lassen (die Platte war über usb-sata Adapter angeschlossen, daher sdb).

Beitrag geändert von mumpf (17.02.2017 12:40:22)

Offline

#2 17.02.2017 12:35:54

frostschutz
Mitglied

Re: smartctl: read failure, mit badblocks noch 'was zu reissen?

Defekte Blöcke kann man nicht reparieren, die Platte ist einfach hinüber.

Online

#3 17.02.2017 12:46:38

mumpf
Mitglied

Re: smartctl: read failure, mit badblocks noch 'was zu reissen?

ok, dachte, so etwas wie ein low-level Formatieren ist evtl. möglich (obwohl das Auslagern von Daten auf defekten Sektoren ja immer die Platte selber macht)

Offline

#4 17.02.2017 18:33:48

TBone
Mitglied

Re: smartctl: read failure, mit badblocks noch 'was zu reissen?

man hdparm | grep repair-sector

Ja, ist möglich, je nachdem, wie du das definierst. Du kannst dafür sorgen, dass Current_Pending_Sectors neu beschrieben werden, je nach Erfolg werden sie wieder benutzt oder wandern zu den Reallocated_Sector_Ct.
Ich rate dir: Werf die Platte weg, du hast damit keine Freude mehr.

Offline

#5 Gestern 19:35:44

mumpf
Mitglied

Re: smartctl: read failure, mit badblocks noch 'was zu reissen?

Hallo TBone
Danke für den Befehl. Habe die Platte nun trotzdem entsorgt, denke, wenn die Mechanik hinüber ist, dann ist das so. Wie Du richtig schreibst: ich werde keine Freude d'ran haben.

Offline

Schnellantwort auf dieses Thema

Schreibe deinen Beitrag und versende ihn
Deine Antwort

Fußzeile des Forums