On Saturday 26 November 2005 13:38, belbo wrote: >Bruno Buys wrote: >> belbo wrote: > >[...] > >>> journal_bmap: journal block not found at offset 5132 on hdb5 >>> Aborting journal on device hdb5. >>> __journal_remove_journal_head: freeing b_committed_data >>> journal commit I/O error >>> ext3_abort called. >>> EXT3-fs error (device hdb5): ext3_journal_start_sb: Detected aborted >>> journal >>> Remounting filesystem read-only >>> >>> >>> If I umount the partition, do e2fsck -y /dev/hdb5 and remount, >>> partition works >>> fine for 2-3 hours, and then it happens again. >>> I think it is only a software problem, what can I do to fix the >>> problem? >>> >>> Thanks and bye >> >> Looks like hw failure to me (badblocks?). > >I did "fsck.ext3 -c /dev/hdb5". It finds many badblock, but it is > useless. How can I avoid badblocks? > >Bye
Your drive is wheezing its last, run, do not walk, to someplace where you can get another and do not waste any time in copying your data off else it WILL be gone shortly. -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) 99.36% setiathome rank, not too shabby for a WV hillbilly Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
