CODE
Feb 13 21:04:34 myhostname kernel: scsi0: ERROR on channel 0, id 0, lun 0, CDB: Read (10) 00 03 30 9c 31 00 00 08 00
Feb 13 21:04:34 myhostname kernel: Info fld=0x3309c31, Current sd08:03: sense key Medium Error
Feb 13 21:04:34 myhostname kernel: scsi0: ERROR on channel 0, id 0, lun 0, CDB: Read (10) 00 03 30 9c 31 00 00 08 00
Feb 13 21:04:34 myhostname kernel: Info fld=0x3309c31, Current sd08:03: sense key Medium Error
Feb 13 21:04:34 myhostname kernel: Additional sense indicates Read retries exhausted
Feb 13 21:04:34 myhostname kernel: I/O error: dev 08:03, sector 36976
Feb 13 21:04:34 myhostname kernel: journal_bmap_Rsmp_6199acb1: journal block not found at offset 4108 on sd(8,3)
Feb 13 21:04:34 myhostname kernel: Aborting journal on device sd(8,3).
Feb 13 21:04:34 myhostname kernel: Error (-5) on journal on device 08:03
Feb 13 21:04:34 myhostname kernel: ext3_abort called.
Feb 13 21:04:34 myhostname kernel: EXT3-fs abort (device sd(8,3)): ext3_journal_start: Detected aborted journal
Feb 13 21:04:34 myhostname kernel: Remounting filesystem read-only
Feb 13 21:04:34 myhostname kernel: Info fld=0x3309c31, Current sd08:03: sense key Medium Error
Feb 13 21:04:34 myhostname kernel: scsi0: ERROR on channel 0, id 0, lun 0, CDB: Read (10) 00 03 30 9c 31 00 00 08 00
Feb 13 21:04:34 myhostname kernel: Info fld=0x3309c31, Current sd08:03: sense key Medium Error
Feb 13 21:04:34 myhostname kernel: Additional sense indicates Read retries exhausted
Feb 13 21:04:34 myhostname kernel: I/O error: dev 08:03, sector 36976
Feb 13 21:04:34 myhostname kernel: journal_bmap_Rsmp_6199acb1: journal block not found at offset 4108 on sd(8,3)
Feb 13 21:04:34 myhostname kernel: Aborting journal on device sd(8,3).
Feb 13 21:04:34 myhostname kernel: Error (-5) on journal on device 08:03
Feb 13 21:04:34 myhostname kernel: ext3_abort called.
Feb 13 21:04:34 myhostname kernel: EXT3-fs abort (device sd(8,3)): ext3_journal_start: Detected aborted journal
Feb 13 21:04:34 myhostname kernel: Remounting filesystem read-only
About two weeks ago server rebooted on its own. Then last night this was in the log at 21:04 and ever since I have been unable to keep my / partition (sda3) from becoming read-only a few minutes after reboot. I'm wondering if it's a software error causing the hardware error or a hardware error causing the software error as it appears.