[ale] hard drive won't mount

[cfowler]

hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }

This is what I get.  Can I badblock this disk with data on it?


On Thu, 2002-06-20 at 14:19, Geoffrey wrote:
> keith frost wrote:
> 
> > i would have to aggree, but was not going to argue
> > with anyone over it.
> > 
> > the maxtors may have problems that only show up with
> > the 2.4 kernel, but (and i mean no disrespect to the
> > kernel people) isn't this where opensource is supposed
> > to prevail.  you would think that somewhere there
> > would be a module option that would allow the drive to
> > think it was talking to a 2.2 kernel?
> 
> My current machine 2.4.17, Maxtor 40 gig, been on 2.4 since May I 
> believe, no problems yet.
> 
> -- 
> Until later: Geoffrey		esoteric at 3times25.net
> 
> I didn't have to buy my radio from a specific company to listen
> to FM, why doesn't that apply to the Internet (anymore...)?
> 
> 
> ---
> This message has been sent through the ALE general discussion list.
> See http://www.ale.org/mailing-lists.shtml for more info. Problems should be 
> sent to listmaster at ale dot org.
> 
> 
> 



---
This message has been sent through the ALE general discussion list.
See http://www.ale.org/mailing-lists.shtml for more info. Problems should be 
sent to listmaster at ale dot org.