Externe 2TB Festplatte mit 1.2TB voll? Daten fehlen!

Hast Du Probleme mit Hardware, die durch die anderen Foren nicht abgedeckt werden? Schau auch in den "Tipps und Tricks"-Bereich.
Antworten
pferdefreund
Beiträge: 3791
Registriert: 26.02.2009 14:35:56

Re: Externe 2TB Festplatte mit 1.2TB voll? Daten fehlen!

Beitrag von pferdefreund » 01.11.2018 08:22:44

probier mal smartctl -d sat -a /dein/device. Funktioniert bei mir mit einer USB-Platte. Da solltest du dann die Daten betreffs realloc, pending read-error usw bekommen. Das -d sat ist das Entscheidende.

kocj
Beiträge: 18
Registriert: 09.02.2018 05:10:52

Re: Externe 2TB Festplatte mit 1.2TB voll? Daten fehlen!

Beitrag von kocj » 01.11.2018 13:09:31

Danke, jetzt stehen ein paar mehr Informationen zu Verfügung. Hat die Festplatte einen Schaden erlitten?

Code: Alles auswählen

root@debian:/home/john# smartctl -d sat -a /dev/sdc
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.9.0-8-amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     ST2000LM015-2E8174
Serial Number:    WDZ2A41J
LU WWN Device Id: 5 000c50 0a831c223
Firmware Version: SDM1
User Capacity:    2,000,398,934,016 bytes [2.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Form Factor:      2.5 inches
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ACS-3 T13/2161-D revision 3b
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Thu Nov  1 19:00:14 2018 +07
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: 			 (0x71) SMART execute Offline immediate.
					No Auto Offline data collection support.
					Suspend Offline collection upon new
					command.
					No 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: 	 (   1) minutes.
Extended self-test routine
recommended polling time: 	 ( 330) minutes.
Conveyance self-test routine
recommended polling time: 	 (   2) minutes.
SCT capabilities: 	       (0x3035)	SCT Status supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   073   059   006    Pre-fail  Always       -       22318506
  3 Spin_Up_Time            0x0003   098   098   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       339
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   073   060   045    Pre-fail  Always       -       4316335157
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       872 (116 88 0)
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       301
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   001   001   000    Old_age   Always       -       260
188 Command_Timeout         0x0032   100   098   000    Old_age   Always       -       124556017696
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   066   042   040    Old_age   Always       -       34 (Min/Max 22/40)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       14
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       158
193 Load_Cycle_Count        0x0032   099   099   000    Old_age   Always       -       3945
194 Temperature_Celsius     0x0022   034   058   000    Old_age   Always       -       34 (0 20 0 0 0)
197 Current_Pending_Sector  0x0012   071   071   000    Old_age   Always       -       2416
198 Offline_Uncorrectable   0x0010   071   071   000    Old_age   Offline      -       2416
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       434 (24 152 0)
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       7259759827
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       8152380245
254 Free_Fall_Sensor        0x0032   100   100   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 260 (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 260 occurred at disk power-on lifetime: 831 hours (34 days + 15 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 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  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 08 ff ff ff 4f 00      06:02:21.229  READ DMA EXT
  ef 03 46 c8 80 f1 00 00      06:02:21.215  SET FEATURES [Set transfer mode]
  ef 03 0c c8 80 f1 00 00      06:02:21.204  SET FEATURES [Set transfer mode]
  ec 03 08 c8 80 f1 00 00      06:02:21.203  IDENTIFY DEVICE
  00 00 00 00 00 00 00 04      06:02:21.160  NOP [Abort queued commands]

Error 259 occurred at disk power-on lifetime: 831 hours (34 days + 15 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 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  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 08 ff ff ff 4f 00      06:02:18.520  READ DMA EXT
  ef 03 46 c8 7c f1 00 00      06:02:18.506  SET FEATURES [Set transfer mode]
  ef 03 0c c8 7c f1 00 00      06:02:18.495  SET FEATURES [Set transfer mode]
  ec 03 08 c8 7c f1 00 00      06:02:18.493  IDENTIFY DEVICE
  00 00 00 00 00 00 00 04      06:02:18.298  NOP [Abort queued commands]

Error 258 occurred at disk power-on lifetime: 831 hours (34 days + 15 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 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  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 08 ff ff ff 4f 00      06:02:15.649  READ DMA EXT
  ef 03 46 c0 7b f1 00 00      06:02:15.635  SET FEATURES [Set transfer mode]
  ef 03 0c c0 7b f1 00 00      06:02:15.624  SET FEATURES [Set transfer mode]
  ec 03 08 c0 7b f1 00 00      06:02:15.623  IDENTIFY DEVICE
  00 00 00 00 00 00 00 04      06:02:15.512  NOP [Abort queued commands]

Error 257 occurred at disk power-on lifetime: 831 hours (34 days + 15 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 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  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 08 ff ff ff 4f 00      06:02:06.017  READ DMA EXT
  ef 03 46 b8 7b f1 00 00      06:02:06.003  SET FEATURES [Set transfer mode]
  ef 03 0c b8 7b f1 00 00      06:02:05.992  SET FEATURES [Set transfer mode]
  ec 08 00 b8 7b f1 00 00      06:02:05.991  IDENTIFY DEVICE
  00 00 00 00 00 00 00 04      06:02:05.807  NOP [Abort queued commands]

Error 256 occurred at disk power-on lifetime: 831 hours (34 days + 15 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 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 08 ff ff ff 4f 00      06:01:55.329  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      06:01:55.324  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      06:01:55.018  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      06:01:55.018  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      06:01:55.018  READ FPDMA QUEUED

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

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.

DeletedUserReAsG

Re: Externe 2TB Festplatte mit 1.2TB voll? Daten fehlen!

Beitrag von DeletedUserReAsG » 01.11.2018 17:28:01

Lesen kannst ja selbst: die Platte hat ’nen Knacks weg. Ich würde sie ersezten, das Backup auf die neue Platte zurückschreiben und gut.

Benutzeravatar
weshalb
Beiträge: 1265
Registriert: 16.05.2012 14:19:49

Re: Externe 2TB Festplatte mit 1.2TB voll? Daten fehlen!

Beitrag von weshalb » 01.11.2018 17:41:37

niemand hat geschrieben: ↑ zum Beitrag ↑
01.11.2018 17:28:01
Ich würde sie ersezten, das Backup auf die neue Platte zurückschreiben und gut.
Den konntest du dir wohl nicht verkneifen? :P

@TE

Ich habe gelesen, dass Photorec die Dateien findet, was doch ein guter Anfang ist. Ich würde die in einem Windowsrechner mit Testdisk auslesen und wenn es dir zu heikel ist, kannst du ja erstmal eine Iso davon erstellen, mit der du arbeiten kannst.

pferdefreund
Beiträge: 3791
Registriert: 26.02.2009 14:35:56

Re: Externe 2TB Festplatte mit 1.2TB voll? Daten fehlen!

Beitrag von pferdefreund » 02.11.2018 07:48:47

Manchmal - hatte ich auch schon, ist es nur das USB-Kabel oder der HUB, falls vorhanden. Mal mit Markenkabel probieren und nicht mit Billig-Chinamüll. Ein angeblich defekter USB-Stick war nach Austausch des Verlängerungskabels auf einmal wieder 100 % in Ordnung.

Antworten