1 |
On Dec 13, 2011 12:25 a.m., "Paul Hartman" <paul.hartman+gentoo@×××××.com> |
2 |
wrote: |
3 |
> |
4 |
> On Mon, Dec 12, 2011 at 6:03 PM, James Broadhead |
5 |
> <jamesbroadhead@×××××.com> wrote: |
6 |
> >> Does it happen to be a >2TB USB drive? I remember reading about |
7 |
> >> problems with some of those. It works in Windows with the factory |
8 |
> >> partition/FAT tables because of tricks they do to the addressing that |
9 |
> >> works in Windows, but once you reformat it you can't access the >2TB |
10 |
> >> areas. Something like that... As far as I recall, you could |
11 |
> >> repartition to create a 2TB or smaller partition and that would work, |
12 |
> >> but then the rest of the drive was inaccessible. |
13 |
> > |
14 |
> > So on returning to this machine, I see that another USB disk that I |
15 |
> > have connected to it is also having those messages printed about it. |
16 |
> > This leads me to suspect that it's either an ext4 bug or the situation |
17 |
> > that you mentioned above. |
18 |
> > |
19 |
> > Both are Western Digital 2TB disks; |
20 |
> > 1058:1130 Western Digital Technologies, Inc. |
21 |
> > 1058:1021 Western Digital Technologies, Inc. Elements 2TB |
22 |
> > |
23 |
> > There are 42 messages in quick succession for each disk, appearing to |
24 |
> > cycle through the same list of blocks twice. I'll attach the messages. |
25 |
> > |
26 |
> > I'm inclined towards the bad-usb-firmware idea - do you have a link to |
27 |
> > where you read about the 2TB partition problem ? |
28 |
> > |
29 |
> > I don't have much time to deal with this at the moment, so I think |
30 |
> > that I'll just power them down and wait until I do. |
31 |
> |
32 |
> The problem I was referring to was for drives LARGER than 2TB (I think |
33 |
> the real limit hits somewhere around 2.1 or 2.2TB). So if your drives |
34 |
> are 2TB then I don't think it's that problem. |
35 |
> |
36 |
> I use a 2TB external USB drive myself (LaCie brand, with a pair of |
37 |
> spanned 1TB Samsung disks inside), formatted as ext4, and it works |
38 |
> fine. However, that was not always the case. I had to replace the USB |
39 |
> cable after I suffered a lot of corruption and random USB disconnects. |
40 |
> Later on, the drive started going offline and making the click of |
41 |
> death, and eventually failed to start up. It turned out to be a faulty |
42 |
> power supply. They sent me a replacement free of charge, despite the |
43 |
> drive being out of warranty, and it worked perfectly fine with the new |
44 |
> power supply. And it has worked fine ever since. |
45 |
> |
46 |
|
47 |
Actually, a bit more triage shows that these errors are triggered on mount, |
48 |
and only when using pmount. Mounting manually as root doesn't trigger them. |
49 |
|
50 |
I'll have another look through my logs to see if they've happened at other |
51 |
times, but for the moment I'll stop using pmount and see if it reoccurs. |