FreeBSD, Gentoo, openSUSE, CentOS, Ubuntu, Debian
ohgott
Posts: 28Joined: 2006-03-21 16:21
Post by ohgott 2006-07-25 21:47
Einige Dateien waren bei mir beschädigt, fsck tat dann dieses:
Code: Select all
(IPX)rescue:~# fsck /dev/hda3
fsck 1.37 (21-Mar-2005)
e2fsck 1.37 (21-Mar-2005)
/dev/hda3: recovering journal
Error reading block 3538945 (Attempt to read block from filesystem resulted in s
hort read) while reading inode and block bitmaps. Ignore error<y>? yes
Force rewrite<y>? yes
Error reading block 4390912 (Attempt to read block from filesystem resulted in short read) while reading inode and block bitmaps. Ignore error<y>? yes
Force rewrite<y>? yes
Clearing orphaned inode 3195126 (uid=0, gid=0, mode=0100600, size=0)
Clearing orphaned inode 3571720 (uid=30, gid=0, mode=0100600, size=0)
Backing up journal inode block information.
/dev/hda3: clean, 96663/4882432 files, 1150833/9747438 blocks
(IPX)rescue:~# fsck /dev/hda3
fsck 1.37 (21-Mar-2005)
e2fsck 1.37 (21-Mar-2005)
/dev/hda3: clean, 96663/4882432 files, 1150833/9747438 blocks
Was bedeutet das nun genau und was ist zu tun? Platte defekt?
oxygen
Posts: 2138Joined: 2002-12-15 00:10Location: Bergheim
Post by oxygen 2006-07-25 21:59
Wäre möglich. Aber ein Fehler im Dateiesystem kann viele Ursachen haben (Stromausfall, Absturz, Überhitzung, Softwarefehler etc)
ohgott
Posts: 28Joined: 2006-03-21 16:21
Post by ohgott 2006-07-25 22:33
Code: Select all
smartctl -a /dev/hda
smartctl version 5.36 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
=== START OF INFORMATION SECTION ===
Model Family: Maxtor DiamondMax Plus 8 family
Device Model: Maxtor 6E040L0
Serial Number: E1AMPCJE
Firmware Version: NAR61590
User Capacity: 41,110,142,976 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 7
ATA Standard is: ATA/ATAPI-7 T13 1532D revision 0
Local Time is: Tue Jul 25 22:28:30 2006 CEST
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: (0x80) Offline data collection activity
was never started.
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: (1021) 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: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 17) 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_VALU
E
3 Spin_Up_Time 0x0027 252 252 063 Pre-fail Always - 2524
4 Start_Stop_Count 0x0032 253 253 000 Old_age Always - 20
5 Reallocated_Sector_Ct 0x0033 252 252 063 Pre-fail Always - 9
6 Read_Channel_Margin 0x0001 253 253 100 Pre-fail Offline - 0
7 Seek_Error_Rate 0x000a 253 252 000 Old_age Always - 0
8 Seek_Time_Performance 0x0027 252 239 187 Pre-fail Always - 45630
9 Power_On_Minutes 0x0032 212 212 000 Old_age Always - 59h+27m
10 Spin_Retry_Count 0x002b 252 252 157 Pre-fail Always - 0
11 Calibration_Retry_Count 0x002b 253 252 223 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 253 253 000 Old_age Always - 24
192 Power-Off_Retract_Count 0x0032 253 253 000 Old_age Always - 6
193 Load_Cycle_Count 0x0032 253 253 000 Old_age Always - 174
194 Temperature_Celsius 0x0032 253 253 000 Old_age Always - 40
195 Hardware_ECC_Recovered 0x000a 253 252 000 Old_age Always - 5592
196 Reallocated_Event_Count 0x0008 253 253 000 Old_age Offline - 0
197 Current_Pending_Sector 0x0008 253 253 000 Old_age Offline - 3
198 Offline_Uncorrectable 0x0008 253 253 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0008 199 199 000 Old_age Offline - 0
200 Multi_Zone_Error_Rate 0x000a 253 252 000 Old_age Always - 0
201 Soft_Read_Error_Rate 0x000a 253 252 000 Old_age Always - 0
202 TA_Increase_Count 0x000a 253 199 000 Old_age Always - 0
203 Run_Out_Cancel 0x000b 253 252 180 Pre-fail Always - 8
204 Shock_Count_Write_Opern 0x000a 253 252 000 Old_age Always - 0
205 Shock_Rate_Write_Opern 0x000a 253 252 000 Old_age Always - 0
207 Spin_High_Current 0x002a 252 252 000 Old_age Always - 0
208 Spin_Buzz 0x002a 252 252 000 Old_age Always - 0
209 Offline_Seek_Performnce 0x0024 185 185 000 Old_age Offline - 0
99 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0
100 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0
101 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0
SMART Error Log Version: 1
ATA Error Count: 115 (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 115 occurred at disk power-on lifetime: 13366 hours (556 days + 22 hours)
When the command that caused the error occurred, the device was in an unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 07 10 00 00 e0 Error: UNC 7 sectors at LBA = 0x00000010 = 16
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 10 00 00 e0 08 46d+07:26:41.328 READ DMA
c8 00 30 48 00 00 e0 08 46d+07:26:41.328 READ DMA
c8 00 40 88 00 00 e0 08 46d+07:26:41.328 READ DMA
c8 00 08 78 00 00 e0 08 46d+07:26:41.328 READ DMA
c8 00 08 08 00 00 e0 08 46d+07:26:41.312 READ DMA
Error 114 occurred at disk power-on lifetime: 13366 hours (556 days + 22 hours)
When the command that caused the error occurred, the device was in an unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 07 10 00 00 e0 Error: UNC 7 sectors at LBA = 0x00000010 = 16
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 10 00 00 e0 08 46d+07:26:40.032 READ DMA
c8 00 08 10 00 00 e0 08 46d+07:26:38.736 READ DMA
c8 00 08 40 00 00 e0 08 46d+07:26:38.736 READ DMA
c8 00 08 10 00 00 e0 08 46d+07:26:37.440 READ DMA
c8 00 08 80 00 00 e0 08 46d+07:26:37.440 READ DMA
Error 113 occurred at disk power-on lifetime: 13366 hours (556 days + 22 hours)
When the command that caused the error occurred, the device was in an unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 07 10 00 00 e0 Error: UNC 7 sectors at LBA = 0x00000010 = 16
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 10 00 00 e0 08 46d+07:26:38.736 READ DMA
c8 00 08 40 00 00 e0 08 46d+07:26:38.736 READ DMA
c8 00 08 10 00 00 e0 08 46d+07:26:37.440 READ DMA
c8 00 08 80 00 00 e0 08 46d+07:26:37.440 READ DMA
c8 00 08 10 00 00 e0 08 46d+07:26:36.160 READ DMA
Error 112 occurred at disk power-on lifetime: 13366 hours (556 days + 22 hours)
When the command that caused the error occurred, the device was in an unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 07 10 00 00 e0 Error: UNC 7 sectors at LBA = 0x00000010 = 16
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 10 00 00 e0 08 46d+07:26:37.440 READ DMA
c8 00 08 80 00 00 e0 08 46d+07:26:37.440 READ DMA
c8 00 08 10 00 00 e0 08 46d+07:26:36.160 READ DMA
c8 00 08 10 00 00 e0 08 46d+07:26:34.880 READ DMA
c8 00 08 00 00 00 e0 08 46d+07:26:34.864 READ DMA
Error 111 occurred at disk power-on lifetime: 13366 hours (556 days + 22 hours)
When the command that caused the error occurred, the device was in an unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 07 10 00 00 e0 Error: UNC 7 sectors at LBA = 0x00000010 = 16
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 10 00 00 e0 08 46d+07:26:36.160 READ DMA
c8 00 08 10 00 00 e0 08 46d+07:26:34.880 READ DMA
c8 00 08 00 00 00 e0 08 46d+07:26:34.864 READ DMA
c8 00 08 00 2d c9 e4 08 46d+07:26:34.848 READ DMA
e7 00 00 00 00 00 e0 08 46d+07:26:24.864 FLUSH CACHE
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% 2646 -
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.
Da steht was von Fehlern, oder?
ohgott
Posts: 28Joined: 2006-03-21 16:21
Post by ohgott 2006-07-25 23:06
"solange die Werte nicht die bei "smartctl -A /dev/hda"
angezeigten Threshold-Wert erreichen, ist das unbedenklich"
Code: Select all
195 Hardware_ECC_Recovered 0x000a 253 252 000 Old_age Always - 5592
Threshold-Wert -A
Code: Select all
195 Hardware_ECC_Recovered 0x000a 253 252 000 Old_age Always - 3461
Verstehe ich das richtig? 5592 ist größer als 3461..
[/code]
isotopp
Posts: 471Joined: 2003-08-21 10:21Location: Berlin
Post by isotopp 2006-07-26 06:30
OhGott wrote: Error reading block 3538945 (Attempt to read block from filesystem resulted in short read) while reading inode and block bitmaps. Ignore error<y>? yes
Dieser Block war unlesbar. fsck hat ihn markiert und substituiert.
Error reading block 4390912 (Attempt to read block from filesystem resulted in short read) while reading inode and block bitmaps. Ignore error<y>? yes
Nochmal.
Clearing orphaned inode 3195126 (uid=0, gid=0, mode=0100600, size=0)
Möglicherweise zwei Files verloren.
/dev/hda3: clean, 96663/4882432 files, 1150833/9747438 blocks
Dateisystem wurde repariert.
(IPX)rescue:~# fsck /dev/hda3
Filesystem ist heil.
Was bedeutet das nun genau und was ist zu tun? Platte defekt?
smartmontools meint "internal self-assessment PASSED". Alles ist gut.
ohgott
Posts: 28Joined: 2006-03-21 16:21
Post by ohgott 2006-07-26 07:14
Code: Select all
=== START OF READ SMART DATA SECTION ===
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 60% 13369 17
# 2 Extended offline Completed: read failure 40% 13369 17
# 3 Extended offline Completed: read failure 40% 13369 17
# 4 Short offline Completed without error 00% 2646 -
Ist das auch noch ok?
r. u. serious
Posts: 88Joined: 2006-06-10 14:17
Post by r. u. serious 2006-07-26 09:19
Wenn ein einzelner Fehler auftaucht, ist das meistens zu ignorieren, wenn mehrere Fehler in kürzer werdenden Intervallen auftauchen, _kann_ das heißen, dass die Platte langsam ihren Geist aufgibt.
Auf jeden Fall die Backupstrategie prüfen, und Restores testen ob auch alles funktioniert (wenn nicht sowieso schon geschehen). Fall möglich würde ich auch schonmal versuchen einen Platenaustuasch in die Wege zu leiten.
http://scottstuff.net/blog/articles/200 ... ve-failure
isotopp
Posts: 471Joined: 2003-08-21 10:21Location: Berlin
Post by isotopp 2006-07-26 09:20
OhGott wrote: Code: Select all
=== START OF READ SMART DATA SECTION ===
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 60% 13369 17
# 2 Extended offline Completed: read failure 40% 13369 17
# 3 Extended offline Completed: read failure 40% 13369 17
# 4 Short offline Completed without error 00% 2646 -
Ist das auch noch ok?
Noch ja. Du hast Lesefehler von der Platte, und zwar alle zur selben Zeit (13369 Betriebsstunden). Ich würde die Daten sichern und das Ding dann weiter beobachten.
Lesefehler, die nicht sowieso ab Werk auf der Platte sind, entwickeln sich meistens am Stück. Das kann den totalen Verfall der Platte einleiten oder sich relativ schnell wieder beruhigen. Das ist vorab kaum zu sagen.
Kris
ohgott
Posts: 28Joined: 2006-03-21 16:21
Post by ohgott 2006-07-26 14:05
Danke für die Hilfe,
adjustman
Posts: 1132Joined: 2003-03-26 23:29Location: SA
Post by adjustman 2006-08-21 00:12
Ich häng mich hier mal dran.
Es geht um diesen Thread
http://www.rootforum.org/forum/viewtopic.php?t=41921
Heute war "richtig" was los!
In messages hab ich dann folgendes entdeckt
Aug 20 05:30:55 server kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
und hab dann smartctl laufen lassen:
SMART Self-test log structure revision number 1
Was sagt mir das alles? Filesystem kaputt? Platte am sterben? :(
Roger Wilco
Posts: 5923Joined: 2004-05-23 12:53
Post by Roger Wilco 2006-08-21 01:22
Die Meldungen sind völlig unabhängig vom Dateisystem. Deine Festplatte ist am Sterben, also nochmal ein letztes Backup machen und dann austauschen.
adjustman
Posts: 1132Joined: 2003-03-26 23:29Location: SA
Post by adjustman 2006-08-21 01:36
ja, ok. Lass ich morgen machen.
Aber ok sind die Meldungen auch nicht. ;)
UND hat das was damit zu tun? Das war genau die Zeit
ab der nix mehr ging.
http://www.rootforum.org/forum/viewtopic.php?t=41921
thorsten
Posts: 561Joined: 2003-02-01 13:14Location: Fuldatal
Post by thorsten 2006-08-21 12:15
Ich kann mir gut vorstellen, dass das zusammenpaßt.
Outlaw
Posts: 1500Joined: 2002-12-04 10:22Location: 4. Server von rechts, 2. Reihe von oben
Post by Outlaw 2006-08-22 19:09
Backup machen, Provider informieren und über neue Platte freuen .... ;):D
flo
Posts: 2223Joined: 2002-07-28 13:02Location: Berlin
Post by flo 2006-08-22 19:18
Outlaw wrote: Ok, ist oft vielleicht nicht notwendig aber bisher war es bei mir immer so, daß die Techniker lieber sicher gehen wollten, als nachher händeringend nach Ausreden auf den Vorwurf "Ich habs Ihnen ja gesagt" zu suchen ....
Ist wohl ne Haftungsfrage - kann mich noch gut an die Zeit erinnern können, als wohl eine ganze Serie bei einem Provider mit instabilen Platten bestückt worden ist.
flo.
nyxus
Posts: 626Joined: 2002-09-13 08:41Location: Lübeck
Post by nyxus 2006-08-22 20:43
flo wrote: Ist wohl ne Haftungsfrage - kann mich noch gut an die Zeit erinnern können, als wohl eine ganze Serie bei einem Provider mit instabilen Platten bestückt worden ist.
Och komm, die IC25 ist ein uneingeschränktes Qualitätsprodukt ... :twisted: Also, in meinem Rootserver läuft sie seint ca. vier Jahren (was mich aber auch nicht wirklich beruhigt).
flo
Posts: 2223Joined: 2002-07-28 13:02Location: Berlin
Post by flo 2006-08-22 21:45
Schön für Dich ... :-D ... ich war mal um sechs im Büro, hab ein manuelles Backup gezogen und dem Rechner bei seinen letzten Zuckungen zugesehen, ist IMHO auch ca. vier Jahre her ;-)
adjustman
Posts: 1132Joined: 2003-03-26 23:29Location: SA
Post by adjustman 2006-08-22 21:46
adjustMan wrote: ja, ok. Lass ich morgen machen.
Ist jetzt getauscht. In ne WD800BB-22DKA0
