[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Unable to use a new USB drive.



On Sat, Jan 27, 2007 at 06:09:30PM -0500, Douglas Allan Tutty wrote:
> On Fri, Jan 26, 2007 at 05:30:08PM -0500, Roby wrote:
> > hendrik@topoi.pooq.com wrote:
> > 
> > > On Thu, Jan 25, 2007 at 10:26:31PM -0500, hendrik@topoi.pooq.com wrote:
> > >> On Thu, Jan 25, 2007 at 01:37:11PM -0500, Roby wrote:
> > >> > 
> > >> > Only a guess, but is the USB_STORAGE module loaded?
> > >> 
> > >> No. it isn't.  I guess a modprobe usb-storage is in order?
> > > 
> > > Now it is, and I'm using the 2.6.18-3 kernel.  It now recognises the
> > > drive, but a bad blocks check reports it has trouble a bit past block
> > > 3000000 (counting 4K blocks) or 24000000 (counting 512-byte sectors.
> > > 
> > > Now it's time to test the *other* drive I bought.
> > > 
> > > -- hendrik
> > ... you can re-use the same usb-storage module for the second drive :)
> 
> Hi Hendrik,
> 
> If you're running Etch with udev this should happen automatically, at
> least it does for me when I plug in a USB stick.
> 
> Doug.

I *am* running etch with udev on the AMD-64 where I finally had some 
success.  I don't know why it didn't modprobe usb-storage for me 
automatically.

The second drive is testing out fine -- so fat.  I did a mke2fs -c -c on 
it, and it's been checking bad blocks ever sing Friday.  First writing 
blocks full of 0xaa, then reading them back, then repeating with -x55 
and 0xff ... that's as far as I saw when I went to bed Saturday night.  
I presume it went on to try 0x00 next.... It takes a long long time.
So far, no problems found.

-- hendrik



Reply to: