我的服務(wù)器有某種驅(qū)動(dòng)器故障導(dǎo)致操作系統(tǒng)(CentOS 5)崩潰并停止工作(它拒絕啟動(dòng)).

所以我們把另一個(gè)帶有工作OS的驅(qū)動(dòng)器放在那里,然后我們嘗試在舊驅(qū)動(dòng)器中安裝分區(qū).

大多數(shù)分區(qū)都安裝正常,除了一個(gè)：/ var分區(qū),我的MySQL表所在的分區(qū).

當(dāng)我嘗試安裝那個(gè)時(shí),我用dmesg看到這些錯(cuò)誤：

sd 0:0:1:0: Unhandled sense code

sd 0:0:1:0: SCSI error: return code = 0x08100002

Result: hostbyte=invalid driverbyte=DRIVER_SENSE,SUGGEST_OK

sdb: Current: sense key: Medium Error

Add. Sense: Unrecovered read error

Info fld=0x4a47e

JBD: Failed to read block at offset 9863

JBD: recovery failed

EXT3-fs: error loading journal.

有沒(méi)有辦法可以恢復(fù)該分區(qū)中的數(shù)據(jù)？

編輯：

根據(jù)要求,tune2fs -l / dev / sdb2的輸出為：

tune2fs 1.39 (29-May-2006)

Filesystem volume name: /var1

Last mounted on:

Filesystem UUID: d84f5181-24f3-40ce-9eaa-601ae5ae33bd

Filesystem magic number: 0xEF53

Filesystem revision #: 1 (dynamic)

Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super large_file

Default mount options: user_xattr acl

Filesystem state: clean

Errors behavior: Continue

Filesystem OS type: Linux

Inode count: 26214400

Block count: 26214063

Reserved block count: 1310703

Free blocks: 25127226

Free inodes: 26213665

First block: 0

Block size: 4096

Fragment size: 4096

Reserved GDT blocks: 1017

Blocks per group: 32768

Fragments per group: 32768

Inodes per group: 32768

Inode blocks per group: 1024

Filesystem created: Thu May 13 18:14:28 2010

Last mount time: Thu Nov 29 12:52:00 2012

Last write time: Wed Mar 27 20:29:28 2013

Mount count: 15

Maximum mount count: -1

Last checked: Thu May 13 18:14:28 2010

Check interval: 0 ()

Reserved blocks uid: 0 (user root)

Reserved blocks gid: 0 (group root)

First inode: 11

Inode size: 128

Journal inode: 8

Default directory hash: tea

Directory Hash Seed: 35f38c48-3933-4c99-bde2-63b0eccf200d

Journal backup: inode blocks

編輯2：

正如@Hartmut所建議的那樣,我使用以下結(jié)果運(yùn)行fsck.ext3 / dev / sdb2：

e2fsck 1.39 (29-May-2006)

/var1: recovering journal

/var1: Attempt to read block from filesystem resulted in short read while reading block 11931

JBD: Failed to read block at offset 9863

fsck.ext3: No such device or address while trying to re-open /var1

e2fsck: io manager magic bad!

總結(jié)

以上是生活随笔為你收集整理的ext3分区修复linux,linux – 如何从损坏的ext3分区恢复数据？的全部?jī)?nèi)容，希望文章能夠幫你解決所遇到的問(wèn)題。

如果覺(jué)得生活随笔網(wǎng)站內(nèi)容還不錯(cuò)，歡迎將生活随笔推薦給好友。