- 论坛徽章:
- 0
|
前几天我的fc4系统出现了一个问题,某个分区不能写入了,重启了操作系统后恢复了,检查message信息发现了下面的内容,不知道是分区系统的问题还是硬盘的问题。
我查了一下有的网友说可以用fsck进入到单用户模式进行修复,我想问一下如果在多用户模式下使用fsck进行修复是否可行?
Jan 6 08:27:06 localhost kernel: mmap sys buffer<4>ata1: status=0x51 { DriveReady SeekComplete Error }
Jan 6 08:27:06 localhost kernel: ata1: error=0x10 { SectorIdNotFound }
Jan 6 08:27:14 localhost kernel: ata1: status=0x51 { DriveReady SeekComplete Error }
Jan 6 08:27:14 localhost kernel: ata1: error=0x10 { SectorIdNotFound }
Jan 6 08:27:19 localhost kernel: ata1: status=0x51 { DriveReady SeekComplete Error }
Jan 6 08:27:19 localhost kernel: ata1: error=0x10 { SectorIdNotFound }
Jan 6 08:27:24 localhost kernel: ata1: status=0x51 { DriveReady SeekComplete Error }
Jan 6 08:27:24 localhost kernel: ata1: error=0x10 { SectorIdNotFound }
Jan 6 08:27:28 localhost kernel: ata1: status=0x51 { DriveReady SeekComplete Error }
Jan 6 08:27:28 localhost kernel: ata1: error=0x10 { SectorIdNotFound }
Jan 6 08:27:28 localhost kernel: SCSI error : <0 0 0 0> return code = 0x8000002
Jan 6 08:27:28 localhost kernel: sda: Current: sense key: Aborted Command
Jan 6 08:27:28 localhost kernel: Additional sense: Recorded entity not found
Jan 6 08:27:29 localhost kernel: end_request: I/O error, dev sda, sector 160002733
Jan 6 08:27:29 localhost kernel: Buffer I/O error on device sda6, logical block 15233045
Jan 6 08:27:29 localhost kernel: lost page write due to I/O error on sda6
Jan 6 08:27:29 localhost kernel: Aborting journal on device sda6.
Jan 6 08:27:29 localhost kernel: __journal_remove_journal_head: freeing b_committed_data
Jan 6 08:27:29 localhost kernel: __journal_remove_journal_head: freeing b_frozen_data
Jan 6 08:27:29 localhost kernel: __journal_remove_journal_head: freeing b_committed_data
Jan 6 08:27:29 localhost kernel: __journal_remove_journal_head: freeing b_frozen_data
Jan 6 08:27:29 localhost kernel: __journal_remove_journal_head: freeing b_frozen_data
Jan 6 08:27:29 localhost kernel: ext3_abort called.
Jan 6 08:27:29 localhost kernel: EXT3-fs error (device sda6): ext3_journal_start_sb: Detected aborted journal
Jan 6 08:27:30 localhost kernel: Remounting filesystem read-only
Jan 6 08:28:01 localhost crond(pam_unix)[2252]: session opened for user |
|