Re: [HDD problem] Strange remount read-only

2005-11-27 Thread Colin
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.

Re: [HDD problem] Strange remount read-only

2005-11-27 Thread Gregory Soyez
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

Re: [HDD problem] Strange remount read-only

2005-11-27 Thread Bruno Buys
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

[HDD problem] Strange remount read-only

2005-11-26 Thread belbo
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

Re: [HDD problem] Strange remount read-only

2005-11-26 Thread Bruno Buys
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

Re: [HDD problem] Strange remount read-only

2005-11-26 Thread belbo
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:

Re: [HDD problem] Strange remount read-only

2005-11-26 Thread Gene Heskett
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

Re: [HDD problem] Strange remount read-only

2005-11-26 Thread Bruno Buys
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):