On Wed, Jan 28, 2009 at 7:14 AM, g <geleem@xxxxxxxxxxxxx> wrote: > greetings, > > from start of installation of f10, 4 months ago, to present, f10 has been > having a problem of staying operational, in that after being up for a short > time, it would bomb and have just now found problem. > > last update update was last night and while at command line, system showed > error messages of what is happening. > > these are not all of messages, but should be enough for finding problem. > > previously; > > +++ > REISERFS: abort (device sdb8): Journal write error in flush_commit_list > REISERFS: Aborting journal for filesystem on sdb8. > ext3_abort called. > EXT3-fs error (device sdb6): ext3_journal_start_sb: Detected aborted journal > Remounting filesystem read-only > +++ > > last night; > > +++ > EXT3-fs error (device sdb6): in ext3_reserve_inode_write: Journal has aborted > EXT3-fs error (device sdb6): in ext3_reserve_dirty_inode: Journal has aborted > ext3_abort called. > EXT3-fs error (device sdb6): in ext3_reserve_inode_write: Journal has aborted > EXT3-fs error (device sdb6): ext3_journal_start_sb: Detected aborted journal > Remounting filesystem read-only > +++ > > google search shows hits on patches to previous kernels and other non relate > info, but none of help. > > > suggestions? pointers? links? How about running fsck on the drives? badblocks? ~af -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
