1 |
On Sunday 28 Aug 2016 11:49:44 Grant wrote: |
2 |
> I have a USB stick with a crucial file on it (and only an old backup |
3 |
> elsewhere). It's formatted NTFS because I wanted to be able to open |
4 |
> the file on various Gentoo systems and my research indicated that NTFS |
5 |
> was the best solution. |
6 |
> |
7 |
> I decided to copy a 10GB file from a USB hard disk directly to the USB |
8 |
> stick this morning and I ran into errors so I canceled the operation |
9 |
> and now the file manager (thunar) has been stuck for well over an hour |
10 |
> and I'm getting errors like these over and over: |
11 |
> |
12 |
> [ 2794.535814] Buffer I/O error on dev sdc1, logical block 2134893, |
13 |
> lost async page write |
14 |
> [ 2794.535819] Buffer I/O error on dev sdc1, logical block 2134894, |
15 |
> lost async page write |
16 |
> [ 2794.535822] Buffer I/O error on dev sdc1, logical block 2134895, |
17 |
> lost async page write |
18 |
> [ 2794.535824] Buffer I/O error on dev sdc1, logical block 2134896, |
19 |
> lost async page write |
20 |
> [ 2794.535826] Buffer I/O error on dev sdc1, logical block 2134897, |
21 |
> lost async page write |
22 |
> [ 2794.535828] Buffer I/O error on dev sdc1, logical block 2134898, |
23 |
> lost async page write |
24 |
> [ 2794.535830] Buffer I/O error on dev sdc1, logical block 2134899, |
25 |
> lost async page write |
26 |
> [ 2794.535832] Buffer I/O error on dev sdc1, logical block 2134900, |
27 |
> lost async page write |
28 |
> [ 2794.535835] Buffer I/O error on dev sdc1, logical block 2134901, |
29 |
> lost async page write |
30 |
> [ 2794.535837] Buffer I/O error on dev sdc1, logical block 2134902, |
31 |
> lost async page write |
32 |
> [ 2842.568843] sd 9:0:0:0: [sdc] tag#0 FAILED Result: |
33 |
> hostbyte=DID_ERROR driverbyte=DRIVER_SENSE |
34 |
> [ 2842.568849] sd 9:0:0:0: [sdc] tag#0 Sense Key : Hardware Error [current] |
35 |
> [ 2842.568852] sd 9:0:0:0: [sdc] tag#0 Add. Sense: No additional sense |
36 |
> information |
37 |
> [ 2842.568857] sd 9:0:0:0: [sdc] tag#0 CDB: Write(10) 2a 00 01 04 a4 |
38 |
> 58 00 00 f0 00 |
39 |
> [ 2842.568859] blk_update_request: I/O error, dev sdc, sector 17081432 |
40 |
> [ 2842.568862] buffer_io_error: 20 callbacks suppressed |
41 |
> |
42 |
> nmon says sdc is 100% busy but doesn't show any reading or writing. I |
43 |
> once pulled the USB stick in a situation like this and I ended up |
44 |
> having to reformat it which I need to avoid this time since the file |
45 |
> is crucial. What should I do? |
46 |
> |
47 |
> - Grant |
48 |
|
49 |
Whatever you do, do NOT try to unplug the USB you were writing to unless you |
50 |
first manage to successfully unmount it. If you do pull the USB stick |
51 |
regardless of its current I/O state you will likely corrupt whatever file you |
52 |
were writing onto, or potentially more. |
53 |
|
54 |
You could well have a hardware failure here, which manifested itself during |
55 |
your copying operation. Things you could try: |
56 |
|
57 |
Run lsof to find out which process is trying to access the USB fs and kill it. |
58 |
Then see if you can remount it read-only. |
59 |
|
60 |
Run dd, dcfldd, ddrescue to make an image of the complete USB stick on your |
61 |
hard drive and then try to recover any lost files with testdisk. |
62 |
|
63 |
Use any low level recovery tools the manufacturer may offer - they will likely |
64 |
require MSWindows. |
65 |
|
66 |
Shut down your OS and disconnect the USB stick, then reboot and try again to |
67 |
access it, although I would first create an image of the device using any of |
68 |
the above tools. |
69 |
|
70 |
Good luck. |
71 |
-- |
72 |
Regards, |
73 |
Mick |