1 |
On Mon, Sep 21, 2009 at 2:39 PM, Mark Knecht <markknecht@×××××.com> wrote: |
2 |
> On Mon, Sep 21, 2009 at 12:07 PM, Paul Hartman |
3 |
> <paul.hartman+gentoo@×××××.com> wrote: |
4 |
>> On Sat, Sep 19, 2009 at 5:21 PM, Mark Knecht <markknecht@×××××.com> wrote: |
5 |
>>> Hi, |
6 |
>>> I seem to have lost an external USB drive I've been using on my |
7 |
>>> MythTV backend server for video storage. What commands can I try to |
8 |
>>> get it to wake up or at least show me what's working and what isn't? |
9 |
>>> The drive shows under fdisk /dev/sda. I can see the large partition, |
10 |
>>> and it seems to be the right size, according to fdisk anyway, but I |
11 |
>>> cannot mount it using mount, and so far I cannot get e2fsck to do |
12 |
>>> anything. |
13 |
>> |
14 |
>> I had similar errors with an external USB drive recently and it turned |
15 |
>> out to be related to the USB port on the computer. (I suspect the USB |
16 |
>> controller was overloaded). I plugged it into a port on a different |
17 |
>> controller and it started working normally again. So some easy things |
18 |
>> I would suggest trying before messing with data: |
19 |
>> |
20 |
>> A) diferent USB port on the same computer |
21 |
>> B) plug it into a different computer entirely |
22 |
>> C) try a different USB cable |
23 |
>> |
24 |
>> |
25 |
> |
26 |
> By definition this will be true when I move it from the PPC-based Myth |
27 |
> backend to the AMD64-based MythTV frontend here in the office. If it |
28 |
> 'magically' starts working then that sort of cause may well be the |
29 |
> reason. |
30 |
> |
31 |
> I'll report back on this but won't likely touch it before the weekend. |
32 |
|
33 |
So last night my replacement drive - 1394-bsed, not USB - went |
34 |
off-line during recording time so sll the late evening recordings were |
35 |
hosed. |
36 |
|
37 |
What's with Linux support of external drives? Is it just not reliable |
38 |
enough to depend on? This was not a drive failure but just a bunch of |
39 |
sense code message problems and everything quit. I probably could have |
40 |
spent time removing drivers, etc, and then restarting it but I just |
41 |
rebooted and everything came back. |
42 |
|
43 |
I used to use this drive for weeks at a time on one of my Windows |
44 |
boxes. No problems at that time so I have no strong reason to suspect |
45 |
the drive when this is the second drive issue in a few days wit this |
46 |
system. |
47 |
|
48 |
I wonder how I determine if it's a drive problem or a kernel/driver problem? |
49 |
|
50 |
- Mark |