The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Nico Schottelius <nico-kernel@schottelius.org>
To: linux-kernel@vger.kernel.org
Cc: nico-kernel@schottelius.org
Subject: usb issue in 2.6 or notebook defect?
Date: Tue, 17 Feb 2004 12:08:40 +0100	[thread overview]
Message-ID: <20040217110840.GR1881@schottelius.org> (raw)

Hello again!

Now I am trying to recover what is possible to a usb hard disk.
I tried to dd or tar the data, but after some time it stops.
(dmesg attached).

On another host the usb hard disk can be read without any problems.
Both hosts are running Linux 2.6.2. 

Now my question is: Is it possible that not even the first harddisk is
broken, but something from the notebook? Although I remember that
reading usb disks (either adapted 2.5" notebook hard disks or usb
sticks) never went very well (even on my old Acer or the Test-Toshiba
reading and writing much data failed).

So is this a kernel USB issue or a hardware issue?
In any case, can you give me some hints howto find the source of errors?

Greetings.

Nico Schottelius

             reply	other threads:[~2004-02-17 11:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-17 11:08 Nico Schottelius [this message]
2004-02-17 11:09 ` usb issue in 2.6 or notebook defect? Nico Schottelius
2004-02-17 13:24   ` Nico Schottelius

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040217110840.GR1881@schottelius.org \
    --to=nico-kernel@schottelius.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox