belbo wrote:
If there are BadBlocks in my hard drive, the driver normally can manage them,
simply not using them. I wanted to ask if there is some sort of hdparm (or sth
like that) option to tell the driver hey, avoid the badblocks.
I don't think you're getting the severity of the messages.
If there are BadBlocks in my hard drive, the driver normally can manage
them,
simply not using them. I wanted to ask if there is some sort of hdparm (or
sth
like that) option to tell the driver hey, avoid the badblocks.
I had basically the same problem last week and It turned into a
Gregory Soyez wrote:
If there are BadBlocks in my hard drive, the driver normally can manage
them,
simply not using them. I wanted to ask if there is some sort of hdparm (or
sth
like that) option to tell the driver hey, avoid the badblocks.
I had basically the same problem last week
Hi guys,
I've got this problem 4-5 times a day. My kernel 2.6 sends this message about an
ext3 partition (of 60GB):
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
belbo wrote:
Hi guys,
I've got this problem 4-5 times a day. My kernel 2.6 sends this message about an
ext3 partition (of 60GB):
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
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:
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
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):
8 matches
Mail list logo