Festplatte überprüfen

[chipy]

Mit welchen Programm kann ich meine Festplatte auf Fehler überprüfen?
Wenn möglich ein Programm mit GUI.

[taylor]

Steht in den FAQ dieses Forums.

[atomical]

das tool heißt badblocks und ist bei den e2fsprogs enthalten - die sind bei jeder gängigen Distri dabei

[chipy]

Danke für die schnellen Antworten.
Ich habe meine Festplatte jetzt überprüft und das ist dabei rausgekommen.

linux:~ # badblocks -vs /dev/hda2
Checking blocks 0 to 116423055
Checking for bad blocks (read-only test): 237350404/116423055
237350505/116423055
2373506
2373507
237350808/116423055
237350909/116423055
237351010/116423055
237351111/116423055
891718322/116423055
891718333/116423055
891718344/116423055
89171835
905839200/116423055
905855122/116423055
905855133/116423055
90585514
90585515
90585516
90585517
90585518
90585519
90585520
90585521
90585522
90585523
90585524
90585525
90585526
90585527
90585528
90585529
90585530
90585531
90585532
90585533
90585534
90585535
90585536
90585537
90585538
90585539
90585540
90585541
90585542
90585543
90585544
90585545
90585546
90585547
90585548
90585549
90585550
90585551
90585552
90585553
90585554
90585555
90585556
90585557
90585558
90585559
905855600/116423055
905855611/116423055
905855622/116423055
905855633/116423055
905877922/116423055
905877933/116423055
90587794
90587795
90587796
90587797
90587798
90587799
90587800
90587801
90587802
90587803
90587804
90587805
90587806
90587807
90587808
90587809
90587810
90587811
90587812
90587813
90587814
90587815
90587816
90587817
90587818
90587819
90587820
90587821
90587822
90587823
90587824
90587825
90587826
90587827
90587828
90587829
90587830
90587831
90587832
90587833
90587834
90587835
905878366/116423055
905878377/116423055
905878388/116423055
905878399/116423055
933826400/116423055
933826411/116423055
93382642
93382643
93382644
93382645
93382646
93382647
105166696/116423055
105166697/116423055
105166698
105166699
105166700
105166701
105166702
105166703
105166704
105166705
105166706
105166707
105166708
105166709
105166710
105166711
105166712
105166713
105166714
105166715
105166716
105166717
105166718
105166719
105166720
105166721
105166722
105166723
105166724
105166725
105166726
105166727
105166728
105166729
105166730
105166731
105166732
105166733
105166734
105166735
105166736
105166737
105166738
105166739
105166740
105166741
105166742
105166743
105166744
105166745
105166746
105166747
105166748/116423055
105166749/116423055
105166750/116423055
105166751/116423055
106195664/116423055
106195665/116423055
106195666
106195667
106195668
106195669
106195670
106195671
106195672
106195673
106195674
106195675
106195676
106195677
106195678
106195679
106195680
106195681
106195682
106195683
106195684
106195685
106195686
106195687
106195688
106195689
106195690
106195691
106195692
106195693
106195694
106195695
106195696
106195697
106195698
106195699
106195700/116423055
106195701/116423055
106195702/116423055
106195703/116423055
113246312/116423055
113246313/116423055
113246314
113246315
113246316
113246317
113246318
113246319
113246320
113246321
113246322
113246323
113246324
113246325
113246326
113246327
113246328
113246329
113246330
113246331
113246332
113246333
113246334
113246335
113246336
113246337
113246338
113246339
113246340
113246341
113246342
113246343
113246344
113246345
113246346
113246347
113246348
113246349
113246350
113246351
113246352
113246353
113246354
113246355
113246356
113246357
113246358
113246359
113246360
113246361
113246362
113246363
113246364
113246365
113246366
113246367
113246368
113246369
113246370
113246371
113246372/116423055
113246373/116423055
113246374/116423055
113246375/116423055
done
Pass completed, 281 bad blocks found.


Wie kann ich Linux jetzt sagen das es keine Daten in die Badblocks schreiben soll?

[Jesaja]

schmeiß die Platte lieber weg, wenn einmal defekte Sektoren dabei sind, geht die recht schnell ganz kaputt.

[chipy]

von den tausenden blocks sind 281 defekt und ich kann dann direkt die ganze Festplatte wegschmeißen?

[nobody0]

Ja, denn die Platten habe eine interne Reseve von ca. 1 %, mit der die defekten Blöcke von der Platten-Logik intern verwaltet werden.
Wenn badblocks etwas findet, ist die Platte deshalb deutlich defekt; wenn noch mehr Defekte auftreten bedeutet das garantierten Datenverlust!

Du solltest mal mit

smartctl -a /dev/<platte>

nachsehen, was der Selbsttest der Platte ausgibt.

[nobody0]

Nachtrag: Was mein Vorredner sagte stimmt; wenn Defekte nachweisbar sind, ist die Platte meist bald (Tage ... Wochen) komplett gestorben und wird meist nicht einmal vom BIOS gefunden.

[Phoenix33]

R ead M ail - R eally F ast / is meine empfehlung und dann nimmste die platte wirfst sie in eine microwelle stellst die auf höchste stufe ca 20 min .. und schreibst dann hier mit bild wie des ding aussieht (wollte ich schon immer mal wissen *g*)

[chipy]

Mit smartctl -a /dev/<platte> kommt bei mir imer nur command not found.

[carnil]

Hi

Mit smartctl -a /dev/<platte> kommt bei mir imer nur command not found.

Entsprechendes Paket dass dies zur Verfügung stellt ist installiert? (Bei debian wäre es z.B. smartmontools).
Führst Du das als root aus?

MfG carnil

[chipy]

Ok hab das Paket installiert. Das wird mir angezeigt.

linux:~ # smartctl -a /dev/hda2
smartctl version 5.32 Copyright (C) 2002-4 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Device Model: ST3120023A
Serial Number: 3KA02YBK
Firmware Version: 3.30
Device is: In smartctl database [for details use: -P show]
ATA Version is: 6
ATA Standard is: ATA/ATAPI-6 T13 1410D revision 2
Local Time is: Sat Nov 13 11:09:13 2004 CET
SMART support is: Available - device has SMART capability.
SMART support is: Disabled

SMART Disabled. Use option -s with argument 'on' to enable it.

[nobody0]

Dann mach mal was da empfohlen wird, also

smartctl -s on /dev/hda
smartctl -a /dev/hda

Und wenn das nicht funtioniert, ist wohl schon diese Funktionalität gestorben.
Festplatten sterben zu ca. 50 % langsam, Stück für Stück.

[chipy]

Ok das hier hat mir das Programm ausgespuckt. Was sagt mir das jetzt alles. Ich Blick da nicht ganz durch.

linux:~ # smartctl -s on /dev/hda2 -d ata
smartctl version 5.32 Copyright (C) 2002-4 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF ENABLE/DISABLE COMMANDS SECTION ===
SMART Enabled.

linux:~ # smartctl -a /dev/hda2
smartctl version 5.32 Copyright (C) 2002-4 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Device Model: ST3120023A
Serial Number: 3KA02YBK
Firmware Version: 3.30
Device is: In smartctl database [for details use: -P show]
ATA Version is: 6
ATA Standard is: ATA/ATAPI-6 T13 1410D revision 2
Local Time is: Sat Nov 13 14:26:18 2004 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: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
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: ( 426) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off 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.
No General Purpose Logging support.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 84) minutes.

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 053 043 006 Pre-fail Always - 51899231
3 Spin_Up_Time 0x0003 100 100 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 705
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 13
7 Seek_Error_Rate 0x000f 078 060 030 Pre-fail Always - 74295966
9 Power_On_Hours 0x0032 094 094 000 Old_age Always - 5281
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 098 098 020 Old_age Always - 2090
194 Temperature_Celsius 0x0022 023 058 000 Old_age Always - 23
195 Hardware_ECC_Recovered 0x001a 053 043 000 Old_age Always - 51899231
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 6
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 6
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x0000 100 253 000 Old_age Offline - 0
202 TA_Increase_Count 0x0032 098 251 000 Old_age Always - 2

SMART Error Log Version: 1
ATA Error Count: 4249 (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 4249 occurred at disk power-on lifetime: 5281 hours (220 days + 1 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 08 f3 74 7c ed Error: UNC 8 sectors at LBA = 0x0d7c74f3 = 226260211

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 f3 74 7c ed 00 00:13:13.199 READ DMA
ca 00 08 bb 9d a8 ed 00 00:13:13.198 WRITE DMA
c8 00 08 f3 74 7c ed 00 00:13:09.586 READ DMA
e7 00 00 00 00 00 00 00 00:13:09.577 FLUSH CACHE
ca 00 08 c3 ca 18 e0 00 00:13:09.577 WRITE DMA

Error 4248 occurred at disk power-on lifetime: 5281 hours (220 days + 1 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 08 f3 74 7c ed Error: UNC 8 sectors at LBA = 0x0d7c74f3 = 226260211

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 f3 74 7c ed 00 00:13:09.586 READ DMA
e7 00 00 00 00 00 00 00 00:13:09.577 FLUSH CACHE
ca 00 08 c3 ca 18 e0 00 00:13:09.577 WRITE DMA
e7 00 00 00 00 00 00 00 00:13:09.285 FLUSH CACHE
ca 00 30 93 ca 18 e0 00 00:13:09.285 WRITE DMA

Error 4247 occurred at disk power-on lifetime: 5281 hours (220 days + 1 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 08 f3 74 7c ed Error: UNC 8 sectors at LBA = 0x0d7c74f3 = 226260211

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 f3 74 7c ed 00 00:13:04.947 READ DMA
ca 00 10 e3 45 a8 e7 00 00:13:04.935 WRITE DMA
ca 00 10 cb 45 a8 e7 00 00:13:04.932 WRITE DMA
ca 00 18 a3 45 a8 e7 00 00:13:04.929 WRITE DMA
ca 00 10 23 45 a8 e7 00 00:13:04.926 WRITE DMA

Error 4246 occurred at disk power-on lifetime: 5281 hours (220 days + 1 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 08 f3 74 7c ed Error: UNC 8 sectors at LBA = 0x0d7c74f3 = 226260211

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 f3 74 7c ed 00 00:13:00.770 READ DMA
e7 00 00 00 00 00 00 00 00:13:00.761 FLUSH CACHE
ca 00 08 8b ca 18 e0 00 00:13:00.761 WRITE DMA
e7 00 00 00 00 00 00 00 00:13:00.739 FLUSH CACHE
ca 00 48 43 ca 18 e0 00 00:13:00.739 WRITE DMA

Error 4245 occurred at disk power-on lifetime: 5281 hours (220 days + 1 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 08 f3 74 7c ed Error: UNC 8 sectors at LBA = 0x0d7c74f3 = 226260211

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 f3 74 7c ed 00 00:12:57.109 READ DMA
e7 00 00 00 00 00 00 00 00:12:56.901 FLUSH CACHE
ca 00 08 3b c9 18 e0 00 00:12:56.901 WRITE DMA
e7 00 00 00 00 00 00 00 00:12:56.870 FLUSH CACHE
ca 00 e0 5b c8 18 e0 00 00:12:56.849 WRITE DMA

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 0 -

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.

[derguteweka]

Moin,

Ok das hier hat mir das Programm ausgespuckt. Was sagt mir das jetzt alles. Ich Blick da nicht ganz durch.

Da steht (in 72pt, rot und blinkend): "Ich bin eine kaputte Festplatte. Mach sofort ein Backup auf ein anderes Medium, wenn dir irgendwas an den Daten auf mir liegt. Dann bau mich aus und kauf mich neu."

Bei ner durchgebrannten Gluehbirne fragt doch auch keiner, an welcher Stelle getzt genau und wie oft der Draht durchgeschmolzen ist - oder?

Gruss
WK