Re: external hdd problem

2007-05-13 Thread Kushal Kumaran
On 5/14/07, tom arnall <[EMAIL PROTECTED]> wrote: I'm trying to get an external hdd working. (The maker is Magnetic Data Technologies.) When I try to mount it I get the 'tell me about the format' message. Last time I dealt with one of these I just hooked it up and it worked. Any ideas? Are you

Re: external hdd problem APOLOGIES

2007-05-13 Thread Greg Folkert
On Sun, 2007-05-13 at 14:21 -0700, tom arnall wrote: > I sent the following mail this a.m. after looking via google for help on the > issue. but i forgot to look on this user list and just now stumbled onto a > lot of posts on the topic. i need of course to read these before posting new > quest

external hdd problem APOLOGIES

2007-05-13 Thread tom arnall
I sent the following mail this a.m. after looking via google for help on the issue. but i forgot to look on this user list and just now stumbled onto a lot of posts on the topic. i need of course to read these before posting new questions. = I'm trying to

external hdd problem

2007-05-13 Thread tom arnall
I'm trying to get an external hdd working. (The maker is Magnetic Data Technologies.) When I try to mount it I get the 'tell me about the format' message. Last time I dealt with one of these I just hooked it up and it worked. Any ideas? tom arnall arcata, ca -- To UNSUBSCRIBE, email to [E

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 wee

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 tu

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

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): ext3_jour

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_abor

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_

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 commit

[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 ext3_

Re: [hdd problem] Strange errors

2005-11-10 Thread Hugo Vanwoerkom
belbo wrote: Hi, I've got a big problem concerning my second hard drive. Sometimes, let's say once a week, my Linux unmount an hdb partition with this message: EXT3-fs error (device hdb5): ext3_journal_start_sb: Detected aborted journal R

[hdd problem] Strange errors

2005-11-09 Thread belbo
Hi, I've got a big problem concerning my second hard drive. Sometimes, let's say once a week, my Linux unmount an hdb partition with this message: >> EXT3-fs error (device hdb5): ext3_journal_start_sb: Detected aborted journal Remounting filesys

Re: hdd problem

2004-07-26 Thread Alvin Oga
On Mon, 26 Jul 2004, Justinas wrote: > Hi there! > > My dmesg output: hdd: command error: status=0x51 { DriveReady SeekComplete > Error } hdd: command error: error=0x54; /dev/hdd is my sony cd-rom. > Does anybody faced such a problem? it means your cdrom is talking at ata-33 speed

Re: hdd problem

2004-07-26 Thread Justinas
On Mon, 26 Jul 2004 14:00:12 +0300 David Baron <[EMAIL PROTECTED]> wrote: > On Monday 26 July 2004 13:47, [EMAIL PROTECTED] > wrote: > > My dmesg output: hdd: command error: status=0x51 { DriveReady > > SeekComplete Error } hdd: command error: error=0x54; /dev/hdd is my sony > > cd-rom. D

Re: hdd problem

2004-07-26 Thread Klaus Imgrund
On Monday 26 July 2004 04:52 am, Justinas wrote: > Hi there! > > My dmesg output: hdd: command error: status=0x51 { > DriveReady SeekComplete Error } hdd: command error: > error=0x54; /dev/hdd is my sony cd-rom. Does anybody > faced such a problem? Various times but not with a cd-rom only wi

Re: hdd problem

2004-07-26 Thread David Baron
On Monday 26 July 2004 13:47, [EMAIL PROTECTED] wrote: > My dmesg output: hdd: command error: status=0x51 { DriveReady > SeekComplete Error } hdd: command error: error=0x54; /dev/hdd is my sony > cd-rom. Does anybody faced such a problem? I have seen this for a normal HD. Apparently no il

Re: hdd problem

2004-07-26 Thread Justinas
On Mon, 26 Jul 2004 12:18:55 +0200 Rainer Bendig <[EMAIL PROTECTED]> wrote: > Hi Justinas, *, > > Justinas wrote on Mon Jul 26, 2004 at 11:52:49AM +0300: > > My dmesg output: hdd: command error: status=0x51 { DriveReady SeekComplete > > Error } hdd: command error: error=0x54; /dev/hdd is my

Re: hdd problem

2004-07-26 Thread Rainer Bendig
Hi Justinas, *, Justinas wrote on Mon Jul 26, 2004 at 11:52:49AM +0300: > My dmesg output: hdd: command error: status=0x51 { DriveReady SeekComplete > Error } hdd: command error: error=0x54; /dev/hdd is my sony cd-rom. > Does anybody faced such a problem? That's a common message in 2.

hdd problem

2004-07-26 Thread Justinas
Hi there! My dmesg output: hdd: command error: status=0x51 { DriveReady SeekComplete Error } hdd: command error: error=0x54; /dev/hdd is my sony cd-rom. Does anybody faced such a problem? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? C