| 1 |
On Mon, Dec 12, 2011 at 2:33 PM, James Broadhead |
| 2 |
<jamesbroadhead@×××××.com> wrote: |
| 3 |
> On 12 December 2011 14:14, James Broadhead <jamesbroadhead@×××××.com> wrote: |
| 4 |
>> ext4: "fill_buffer on unknown block <BLOCKID> out of range" |
| 5 |
> |
| 6 |
> Apologies; the correct message is: |
| 7 |
> grow_buffers: requested out-of-range block 18446744072382021139 for device sdb1 |
| 8 |
> |
| 9 |
> This appears 42 times immediately following mount. |
| 10 |
> |
| 11 |
> Running picasa today, it informed me that one of the files I was |
| 12 |
> working with was corrupted (but put the message in a box too small to |
| 13 |
> read the full path). |
| 14 |
> |
| 15 |
> This makes me think that perhaps the disk is bad. Any advice, aside |
| 16 |
> from the usual "get your data off asap"? |
| 17 |
|
| 18 |
Does it happen to be a >2TB USB drive? I remember reading about |
| 19 |
problems with some of those. It works in Windows with the factory |
| 20 |
partition/FAT tables because of tricks they do to the addressing that |
| 21 |
works in Windows, but once you reformat it you can't access the >2TB |
| 22 |
areas. Something like that... As far as I recall, you could |
| 23 |
repartition to create a 2TB or smaller partition and that would work, |
| 24 |
but then the rest of the drive was inaccessible. |
Archives