From: Mark Knecht <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] USB drive dead? (Commands to check?)
Date: Tue, 22 Sep 2009 13:20:42 -0700 [thread overview]
Message-ID: <5bdc1c8b0909221320n76280378q9d472965e649c406@mail.gmail.com> (raw)
In-Reply-To: <5bdc1c8b0909211439i5bffeea8kefb5166c4e213a5e@mail.gmail.com>
On Mon, Sep 21, 2009 at 2:39 PM, Mark Knecht <markknecht@gmail.com> wrote:
> On Mon, Sep 21, 2009 at 12:07 PM, Paul Hartman
> <paul.hartman+gentoo@gmail.com> wrote:
>> On Sat, Sep 19, 2009 at 5:21 PM, Mark Knecht <markknecht@gmail.com> wrote:
>>> Hi,
>>> I seem to have lost an external USB drive I've been using on my
>>> MythTV backend server for video storage. What commands can I try to
>>> get it to wake up or at least show me what's working and what isn't?
>>> The drive shows under fdisk /dev/sda. I can see the large partition,
>>> and it seems to be the right size, according to fdisk anyway, but I
>>> cannot mount it using mount, and so far I cannot get e2fsck to do
>>> anything.
>>
>> I had similar errors with an external USB drive recently and it turned
>> out to be related to the USB port on the computer. (I suspect the USB
>> controller was overloaded). I plugged it into a port on a different
>> controller and it started working normally again. So some easy things
>> I would suggest trying before messing with data:
>>
>> A) diferent USB port on the same computer
>> B) plug it into a different computer entirely
>> C) try a different USB cable
>>
>>
>
> By definition this will be true when I move it from the PPC-based Myth
> backend to the AMD64-based MythTV frontend here in the office. If it
> 'magically' starts working then that sort of cause may well be the
> reason.
>
> I'll report back on this but won't likely touch it before the weekend.
So last night my replacement drive - 1394-bsed, not USB - went
off-line during recording time so sll the late evening recordings were
hosed.
What's with Linux support of external drives? Is it just not reliable
enough to depend on? This was not a drive failure but just a bunch of
sense code message problems and everything quit. I probably could have
spent time removing drivers, etc, and then restarting it but I just
rebooted and everything came back.
I used to use this drive for weeks at a time on one of my Windows
boxes. No problems at that time so I have no strong reason to suspect
the drive when this is the second drive issue in a few days wit this
system.
I wonder how I determine if it's a drive problem or a kernel/driver problem?
- Mark
next prev parent reply other threads:[~2009-09-22 20:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-19 22:21 [gentoo-user] USB drive dead? (Commands to check?) Mark Knecht
2009-09-19 22:38 ` [gentoo-user] " Mark Knecht
2009-09-19 22:59 ` Volker Armin Hemmann
2009-09-19 23:05 ` Mark Knecht
2009-09-19 23:12 ` walt
2009-09-19 23:32 ` Volker Armin Hemmann
2009-09-19 23:40 ` Mark Knecht
2009-09-19 23:48 ` Volker Armin Hemmann
2009-09-20 0:01 ` Mark Knecht
2009-09-20 10:24 ` Stroller
2009-09-20 18:41 ` Mark Knecht
2009-09-21 8:21 ` Neil Bothwick
2009-09-21 21:38 ` Mark Knecht
2009-09-21 19:07 ` [gentoo-user] " Paul Hartman
2009-09-21 21:39 ` Mark Knecht
2009-09-22 20:20 ` Mark Knecht [this message]
2009-09-24 19:02 ` Mick
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=5bdc1c8b0909221320n76280378q9d472965e649c406@mail.gmail.com \
--to=markknecht@gmail.com \
--cc=gentoo-user@lists.gentoo.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