整个文件系统变成只读

wizardzq

急救。我的debian文件系统整个变成只读的了。以root身份执行vim test.txt保存，报
错："test.txt" E212: Can't open file for writing

# mount
/dev/sda1 on / type ext3 (rw,errors=remount-ro)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
procbususb on /proc/bus/usb type usbfs (rw)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)

重新mount硬盘结果：
# mount /dev/sda1 -o remount,rw
mount: block device /dev/sda1 is write-protected, mounting read-only


执行fdisk 结果：
# fdisk
bash: /sbin/fdisk: 输入/输出错误

这是怎么回事啊？郁闷死了，之前也没做什么操作，就是一些cp，mv，rm。基本上是在
自己帐号home目录和/var/www两个目录下操作的。


# fsck -t ext3 -r /dev/sda1
fsck 1.41.3 (12-Oct-2008)
e2fsck 1.41.3 (12-Oct-2008)
/dev/sda1: recovering journal
fsck.ext3: Bad magic number in super-block while trying to re-open /dev/sda1
Warning... fsck.ext3 for device /dev/sda1 exited with signal 11.


# fsck  -r /dev/sda1
fsck 1.41.3 (12-Oct-2008)
e2fsck 1.41.3 (12-Oct-2008)
fsck.ext3: Superblock invalid, trying backup blocks...
Resize inode not valid.  Recreate<y>? yes

/dev/sda1 was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Error reading block 1028 (Attempt to read block from filesystem resulted in
short read) while getting next inode from scan.  Ignore error<y>? yes

Force rewrite<y>? yes

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

fstab 文件内容：


# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    defaults        0       0
/dev/sda1       /               ext3    errors=remount-ro 0       1
/dev/sda5       none            swap    sw              0       0
/dev/scd0       /media/cdrom0   udf,iso9660 user,noauto     0       0
~

急求帮助。

Maxshine

/dev/sda1 / ext3 errors=remount-ro 0 1

注意这里，我猜可能启动的时候挂载出问题，然后就会以ro方式挂载，可以用dmesg查一下。

仅仅是猜测

waq

那就fsck一下呗