Militantly FREE software support.
Militantly FREE software support.
NavigationUser loginSpam?See spam posts on this site? If so, please don't reply to the spam! Instead, just report the URL to the webmaster. |
Unable to use a new USB drive.This is on my Debian etch AMD-64 system. Just to be precise, hendrik@april:~$ uname -a When I plug in my new 500GB USB drive, it tells me: usb 2-7: new high speed USB drive using ehci_hcd and address 3 After that, noting happens. Pluggin it into another USB port (I My USB mouse works properly. What information would be useful to track down this problem and fix it? -- hendrik -- Bookmark/Search this post with: 
|
• Debian Weekly News - Essential reading for any Debian fan. • Documentation - Debian's own authoritative documentation, including installation docs. • FAQ - Got questions about Debian GNU/Linux? • From Windows to Debian - Tips for converting from Windows to Debian GNU/Linux • Package of the Day. • Security - Security information and alerts! • Bug System - Bug tracking and instructions on reporting bugs. • CD Images - Where/how to get Debian GNU/Linux CD images. • Mailing List Subscription - Dozens of Debian-specific support mailing lists! • Mailing List Archives - Searchable archives of Debian's mailing lists. • Free Software Guidelines - Learn Debian's idea of what "free" software really is. • Package Listings - A very valuable tool: searchable, integrated with bug reports. • Apt-Get Sources - Sources for *.debs which are not official Debian packages. • Backports - Unofficial new software packages that have been "back-ported" to work with the Debian stable/official release. • Developer's Corner - Info about the people behind Debian, policies, and how to package *.deb files.
Unable to use a new USB drive.
Hallo.
25-01-2007, hendrik:
> This is on my Debian etch AMD-64 system. Just to be precise,
>
> hendrik@april:~$ uname -a
> Linux april 2.6.17-2-amd64 #1 SMP Wed Sep 13 17:49:33 CEST 2006 x86_64
> GNU/Linuxhendrik@april:~$
return -EOLDKERNEL;
Please, try 2.6.18 from testing.
____
--
Unable to use a new USB drive.
On Thu, Jan 25, 2007 at 07:34:49PM +0000, Oleg Verych wrote:
> Hallo.
>
> 25-01-2007, hendrik:
> > This is on my Debian etch AMD-64 system. Just to be precise,
> >
> > hendrik@april:~$ uname -a
> > Linux april 2.6.17-2-amd64 #1 SMP Wed Sep 13 17:49:33 CEST 2006 x86_64
> > GNU/Linuxhendrik@april:~$
>
> return -EOLDKERNEL;
>
> Please, try 2.6.18 from testing.
Will try that tomorrow morning, when I have no users. Thanks.
-- hendrik
--
Unable to use a new USB drive.
hendrik@topoi.pooq.com wrote:
> This is on my Debian etch AMD-64 system. Just to be precise,
>
> hendrik@april:~$ uname -a
> Linux april 2.6.17-2-amd64 #1 SMP Wed Sep 13 17:49:33 CEST 2006 x86_64
> GNU/Linuxhendrik@april:~$
>
> When I plug in my new 500GB USB drive, it tells me:
>
> usb 2-7: new high speed USB drive using ehci_hcd and address 3
> ehci_hcd 0000:00:0b:1: Unlink after no-IRQ? Controller is probably
> using the wrong IRQ
> usb 2-7: device not accepting addr 3, error -110
> usb 2-7: new high speed USB drive using ehci_hcd and address 4
> usb 2-7: device not accepting addr 4, error -110
> usb 2-7: new high speed USB drive using ehci_hcd and address 5
> usb 2-7: device not accepting addr 5, error -110
> usb 2-7: new high speed USB drive using ehci_hcd and address 6
> usb 2-7: device not accepting addr 6, error -110
>
> After that, noting happens. Pluggin it into another USB port (I
> have 6) doesn't help.
>
> My USB mouse works properly.
>
> What information would be useful to track down this problem and fix it?
>
> -- hendrik
Only a guess, but is the USB_STORAGE module loaded?
--
Unable to use a new USB drive.
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?
:-)
-- hendrik
--
Unable to use a new USB drive.
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?
>
> :-)
>
> -- hendrik
>
>
That's your problem
Hugo
--
Unable to use a new USB drive.
On Thu, Jan 25, 2007 at 10:26:31PM -0500, 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
>
> :-)
>
> -- hendrik
>
>
> --
Unable to use a new USB drive.
hendrik@topoi.pooq.com wrote:
> On Thu, Jan 25, 2007 at 10:26:31PM -0500, 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 :)
--
Unable to use a new USB drive.
On Fri, Jan 26, 2007 at 05:30:08PM -0500, Roby wrote:
> wrote:
>
> > On Thu, Jan 25, 2007 at 10:26:31PM -0500, 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.
--
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:
> > wrote:
> >
> > > On Thu, Jan 25, 2007 at 10:26:31PM -0500, 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
--
Unable to use a new USB drive.
On Sun, Jan 28, 2007 at 09:12:07AM -0500, wrote:
>
> 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.
Yes, a long time. Took about 40 hours.
-- hendrik
--
Unable to use a new USB drive.
On Mon, 2007-01-29 at 16:15 -0500, wrote:
> On Sun, Jan 28, 2007 at 09:12:07AM -0500, wrote:
> >
> > 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.
>
> Yes, a long time. Took about 40 hours.
A USB stick of Flash... they only have a FINITE number of times they can
be written to. Yes it is quite high a number, but think in 40 hours how
many times does the format write to a location during verify? Too many
times for a device like flash.
In effect, you have tremendously reduced the useful life of your device.
--
Novell's Directory Services is a competitive product to Microsoft's
Active Directory in much the same way that the Saturn V is a competitive
product to those dinky little model rockets that kids light off down at
the playfield. -- Thane Walkup
Unable to use a new USB drive.
On Mon, Jan 29, 2007 at 05:27:29PM -0500, Greg Folkert wrote:
> On Mon, 2007-01-29 at 16:15 -0500, wrote:
> > On Sun, Jan 28, 2007 at 09:12:07AM -0500, wrote:
> > >
> > > 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.
> >
> > Yes, a long time. Took about 40 hours.
>
> A USB stick of Flash... they only have a FINITE number of times they can
> be written to. Yes it is quite high a number, but think in 40 hours how
> many times does the format write to a location during verify?
Four.
> Too many
> times for a device like flash.
>
> In effect, you have tremendously reduced the useful life of your device.
> --
>
Except that is really was a 500GB USB disk drive, not flash.
-- hendrik
--
Unable to use a new USB drive.
On Tue, 2007-01-30 at 06:35 -0500, wrote:
> On Mon, Jan 29, 2007 at 05:27:29PM -0500, Greg Folkert wrote:
> > On Mon, 2007-01-29 at 16:15 -0500, wrote:
> > > On Sun, Jan 28, 2007 at 09:12:07AM -0500, wrote:
> > > >
> > > > 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.
> > >
> > > Yes, a long time. Took about 40 hours.
> >
> > A USB stick of Flash... they only have a FINITE number of times they can
> > be written to. Yes it is quite high a number, but think in 40 hours how
> > many times does the format write to a location during verify?
>
> Four.
>
> > Too many
> > times for a device like flash.
> >
> > In effect, you have tremendously reduced the useful life of your device.
>
> Except that is really was a 500GB USB disk drive, not flash.
These days there are *FEW IF ANY* reasons to do a check and verify. Most
drives have on board error correction (both IDE and SCSI). So, in
essence, it is a waste of time.
The only time I'd use it is if the drive is suspect. Since it was a 500G
drive, it is fairly new... unless it was dropped and so on.
--
Novell's Directory Services is a competitive product to Microsoft's
Active Directory in much the same way that the Saturn V is a competitive
product to those dinky little model rockets that kids light off down at
the playfield. -- Thane Walkup
Unable to use a new USB drive.
On Tue, Jan 30, 2007 at 07:50:44AM -0500, Greg Folkert wrote:
>
> These days there are *FEW IF ANY* reasons to do a check and verify. Most
> drives have on board error correction (both IDE and SCSI). So, in
> essence, it is a waste of time.
And if the on-board error correction can't handle it, the drive is
probably on its last legs.
>
> The only time I'd use it is if the drive is suspect. Since it was a 500G
> drive, it is fairly new... unless it was dropped and so on.
I bought two drives at the same time. One of them failed the test, the
other passed. So I'd say, in retrospect, I probably did the right
thing.
-- hendrik
> --
>
>
> Novell's Directory Services is a competitive product to Microsoft's
> Active Directory in much the same way that the Saturn V is a competitive
> product to those dinky little model rockets that kids light off down at
> the playfield. -- Thane Walkup
--
Unable to use a new USB drive.
On Thu, Jan 25, 2007 at 12:28:07PM -0500, wrote:
> This is on my Debian etch AMD-64 system. Just to be precise,
>
> hendrik@april:~$ uname -a
> Linux april 2.6.17-2-amd64 #1 SMP Wed Sep 13 17:49:33 CEST 2006 x86_64
> GNU/Linuxhendrik@april:~$
>
> When I plug in my new 500GB USB drive, it tells me:
>
> usb 2-7: new high speed USB drive using ehci_hcd and address 3
> ehci_hcd 0000:00:0b:1: Unlink after no-IRQ? Controller is probably
> using the wrong IRQ
> usb 2-7: device not accepting addr 3, error -110
> usb 2-7: new high speed USB drive using ehci_hcd and address 4
> usb 2-7: device not accepting addr 4, error -110
> usb 2-7: new high speed USB drive using ehci_hcd and address 5
> usb 2-7: device not accepting addr 5, error -110
> usb 2-7: new high speed USB drive using ehci_hcd and address 6
> usb 2-7: device not accepting addr 6, error -110
>
> After that, noting happens. Pluggin it into another USB port (I
> have 6) doesn't help.
There is mention of this at the linux-usb website in the faq's
http://www.linux-usb.org/FAQ.html
good luck
A
Unable to use a new USB drive.
Andrew Sackville-West wrote:
> On Thu, Jan 25, 2007 at 12:28:07PM -0500, wrote:
>> This is on my Debian etch AMD-64 system. Just to be precise,
>>
>> hendrik@april:~$ uname -a
>> Linux april 2.6.17-2-amd64 #1 SMP Wed Sep 13 17:49:33 CEST 2006 x86_64
>> GNU/Linuxhendrik@april:~$
>>
>> When I plug in my new 500GB USB drive, it tells me:
>>
>> usb 2-7: new high speed USB drive using ehci_hcd and address 3
>> ehci_hcd 0000:00:0b:1: Unlink after no-IRQ? Controller is probably
>> using the wrong IRQ
>> usb 2-7: device not accepting addr 3, error -110
>> usb 2-7: new high speed USB drive using ehci_hcd and address 4
>> usb 2-7: device not accepting addr 4, error -110
>> usb 2-7: new high speed USB drive using ehci_hcd and address 5
>> usb 2-7: device not accepting addr 5, error -110
>> usb 2-7: new high speed USB drive using ehci_hcd and address 6
>> usb 2-7: device not accepting addr 6, error -110
>>
>> After that, noting happens. Pluggin it into another USB port (I
>> have 6) doesn't help.
>
> There is mention of this at the linux-usb website in the faq's
> http://www.linux-usb.org/FAQ.html
>
> good luck
>
> A
Except some of those things are outdated. E.g. that patch to delay using
the driver: seems to be already present in 2.6.17+ because I get
messages like "waiting x secs for ... to show up..."
What seems to be hard with using mkinitrd.yaird is generating an image
for something else than the current running kernel.
Hugo
--