PDA

Archiv verlassen und diese Seite im Standarddesign anzeigen : Platte defekt ???



weally
15.02.05, 19:07
Hallo,

nachdem mein Server nicht mehr booten wollte hab ich das System mit "fsck" überprüft folgende Fehler sind aufgetreten (und das nicht grad wenig):



Inode 98978 was part of the orphaned inode list. FIXED.
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=3241621, high=0, low=3241621, sector=2100904
end_request: I/O error, dev 03:03 (hda), sector 2100904
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=3241621, high=0, low=3241621, sector=2100912
end_request: I/O error, dev 03:03 (hda), sector 2100912
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=3241621, high=0, low=3241621, sector=2100920
end_request: I/O error, dev 03:03 (hda), sector 2100920
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=3241619, high=0, low=3241619, sector=2100928
end_request: I/O error, dev 03:03 (hda), sector 2100928
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=3241621, high=0, low=3241621, sector=2100936
end_request: I/O error, dev 03:03 (hda), sector 2100936
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=3241621, high=0, low=3241621, sector=2100944
end_request: I/O error, dev 03:03 (hda), sector 2100944
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=3241621, high=0, low=3241621, sector=2100952
end_request: I/O error, dev 03:03 (hda), sector 2100952
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=3241623, high=0, low=3241623, sector=2100960
end_request: I/O error, dev 03:03 (hda), sector 2100960
Error reading block 262613 (Attempt to read block from filesystem resulted in short read) while doing inode scan. Ignore error<y>? yes

Force rewrite<y>? yes

Error reading block 262614 (Attempt to read block from filesystem resulted in short read) while doing inode scan. Ignore error<y>? yes

Force rewrite<y>? yes

Error reading block 262615 (Attempt to read block from filesystem resulted in short read) while doing inode scan. Ignore error<y>? yes

Force rewrite<y>? yes

Error reading block 262616 (Attempt to read block from filesystem resulted in short read) while doing inode scan. Ignore error<y>?



hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=44396338, high=2, low=10841906, sector=43255720
end_request: I/O error, dev 03:03 (hda), sector 43255720
Error reading block 5406965 (Attempt to read block from filesystem resulted in short read) while doing inode scan. Ignore error<y>? yes




Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: +11208982 -11208984 -13664962 -13994155
Fix<y>? yes

Free blocks count wrong for group #417 (22146, counted=22147).
Fix<y>? yes

Free blocks count wrong for group #427 (23092, counted=23093).
Fix<y>? yes

Free blocks count wrong (8477473, counted=8477475).
Fix<y>? yes

Inode bitmap differences: -98416 -98419 -98923 -98930 -98978 -6832292
Fix<y>? yes

Free inodes count wrong for group #6 (15560, counted=15565).
Fix<y>? yes

Free inodes count wrong for group #417 (15254, counted=15255).
Fix<y>? yes

Free inodes count wrong (6940068, counted=6940074).
Fix<y>? yes


/dev/hda3: ***** FILE SYSTEM WAS MODIFIED *****
/dev/hda3: ***** REBOOT LINUX *****
/dev/hda3: 498262/7438336 files (4.0% non-contiguous), 6392690/14870165 blocks
fsck.ext3 /dev/hda3 failed (status 0x3). Run manually!



Ist die Festplatte defekt?

Hatte das Problem vor paar Wochen schon einmal, nach dem fsck-Check geht aber alles wieder.

Danke

geronet
15.02.05, 19:16
Lies die S.M.A.R.T. Informationen der Platte aus und entscheide weise.

IT-Low
15.02.05, 19:21
Lies die S.M.A.R.T. Informationen der Platte aus und entscheide weise.

Vorausgesetzt das (alte) Teil gibt sowas schon her?

Ich würde auf jeden Fall sofort ein Backup machen, wenn es sich um ein Produktivsystem handelt und die Platte in die Tonne werfen.