fsck命令是否可以在正常的系统上运行进行修复？

前段时间发现系统出现了问题，某个分区无法写入文件了，重启系统后恢复了，查询当时的message文件发现了一下的报错，不知道是否是分区文件系统的问题还是硬件的问题。
我在网上查了一下可以用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