|
|
昨天在Gentoo启动时两次强制按电源关机，导致Gentoo无法启动。最后显示：
No filesystem could mount root.tried:ext2 。。。
kernel panic -not syncing:VFS:Unable to mount root fs on unknown-block(8,6) Dumping ftrace buffer ftrace buffer empty)
我/boot 在/dev/sda5 根目录/ 在/dev/sda6上
曾经用ubuntu启动盘尝试fsck -p /dev/sda6 e2fsck -fy /dev/sda6
ubuntu@ubuntu:~$ sudo fsck -p /dev/sda6
fsck 1.40.8 (13-Mar-2008)
The problem has occurred looks like a hardware problem. If you have
bad blocks, we advise you to get a new hard drive, because once you
get one bad block that the disk drive internals cannot hide from
your sight,the chances of getting more are generally said to become
much higher (precise statistics are unknown to us), and this disk
drive is probably not expensive enough for you to you to risk your
time and data on it. If you don't want to follow that follow that
advice then if you have just a few bad blocks, try writing to the
bad blocks and see if the drive remaps the bad blocks (that means
it takes a block it has in reserve and allocates it for use for
of that block number). If it cannot remap the block, use badblock
option (-B) with reiserfs utils to handle this block correctly.
bread: Cannot read the block (8210): (Input/output error).
Warning... fsck.reiserfs for device /dev/sda6 exited with signal 6.
ubuntu@ubuntu:~$ sudo e2fsck -fy /dev/sda6
e2fsck 1.40.8 (13-Mar-2008)
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block 当试图打开/dev/sda6时
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
哪位大侠知道怎修复不，难道要重装Gentoo? |
|
IP卡
狗仔卡
发表于 2009-2-4 00:12:45
提升卡
置顶卡
沉默卡
喧嚣卡
变色卡
显身卡
楼主