1 |
On Sun, 28 Aug 2016 11:49:44 -0700, Grant wrote: |
2 |
|
3 |
> I have a USB stick with a crucial file on it (and only an old backup |
4 |
> elsewhere). It's formatted NTFS because I wanted to be able to open |
5 |
> the file on various Gentoo systems and my research indicated that NTFS |
6 |
> was the best solution. |
7 |
|
8 |
If it's only to be used on Gentoo (or Linux) systems, why not ext2? |
9 |
|
10 |
> [ 2794.535837] Buffer I/O error on dev sdc1, logical block 2134902, |
11 |
> lost async page write |
12 |
> [ 2842.568843] sd 9:0:0:0: [sdc] tag#0 FAILED Result: |
13 |
> hostbyte=DID_ERROR driverbyte=DRIVER_SENSE |
14 |
> [ 2842.568849] sd 9:0:0:0: [sdc] tag#0 Sense Key : Hardware Error |
15 |
> [current] [ 2842.568852] sd 9:0:0:0: [sdc] tag#0 Add. Sense: No |
16 |
> additional sense information |
17 |
> [ 2842.568857] sd 9:0:0:0: [sdc] tag#0 CDB: Write(10) 2a 00 01 04 a4 |
18 |
> 58 00 00 f0 00 |
19 |
> [ 2842.568859] blk_update_request: I/O error, dev sdc, sector 17081432 |
20 |
> [ 2842.568862] buffer_io_error: 20 callbacks suppressed |
21 |
> |
22 |
> nmon says sdc is 100% busy but doesn't show any reading or writing. I |
23 |
> once pulled the USB stick in a situation like this and I ended up |
24 |
> having to reformat it which I need to avoid this time since the file |
25 |
> is crucial. What should I do? |
26 |
|
27 |
That looks horribly like a hardware failure. The first step should be to |
28 |
see if you can dd the stick to an image file (without mounting it). Then |
29 |
you can work on the image file, or a copy of it, and try things like |
30 |
testdisk. |
31 |
|
32 |
If dd also gives hardware errors, ddrecsue may be able to recover some of |
33 |
it, hopefully including the important bits, but I'm not holding my breath |
34 |
for you :( |
35 |
|
36 |
|
37 |
-- |
38 |
Neil Bothwick |
39 |
|
40 |
When there's a will, I want to be in it. |