Re: [HDD problem] Strange remount read-only

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 wee

Re: [HDD problem] Strange remount read-only

> > 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 tu

Re: [HDD problem] Strange remount read-only

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

Bruno Buys wrote: > belbo wrote: > >> Bruno Buys wrote: >> >> >>> belbo wrote: >>> >> >> [...] >> >> [...] >> I did "fsck.ext3 -c /dev/hdb5". It finds many badblock, but it is >> useless. How >> can I avoid badblocks? >> >> Bye >> >> >> >> > You can have good practices, to avoid exposing

Re: [HDD problem] Strange remount read-only

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_jour

Re: [HDD problem] Strange remount read-only

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_abor

Re: [HDD problem] Strange remount read-only

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_

Re: [HDD problem] Strange remount read-only

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 commit