1 |
>> I have a USB stick with a crucial file on it (and only an old backup |
2 |
>> elsewhere). It's formatted NTFS because I wanted to be able to open |
3 |
>> the file on various Gentoo systems and my research indicated that NTFS |
4 |
>> was the best solution. |
5 |
>> |
6 |
>> I decided to copy a 10GB file from a USB hard disk directly to the USB |
7 |
>> stick this morning and I ran into errors so I canceled the operation |
8 |
>> and now the file manager (thunar) has been stuck for well over an hour |
9 |
>> and I'm getting errors like these over and over: |
10 |
>> |
11 |
>> [ 2794.535814] Buffer I/O error on dev sdc1, logical block 2134893, |
12 |
>> lost async page write |
13 |
>> [ 2794.535819] Buffer I/O error on dev sdc1, logical block 2134894, |
14 |
>> lost async page write |
15 |
>> [ 2794.535822] Buffer I/O error on dev sdc1, logical block 2134895, |
16 |
>> lost async page write |
17 |
>> [ 2794.535824] Buffer I/O error on dev sdc1, logical block 2134896, |
18 |
>> lost async page write |
19 |
>> [ 2794.535826] Buffer I/O error on dev sdc1, logical block 2134897, |
20 |
>> lost async page write |
21 |
>> [ 2794.535828] Buffer I/O error on dev sdc1, logical block 2134898, |
22 |
>> lost async page write |
23 |
>> [ 2794.535830] Buffer I/O error on dev sdc1, logical block 2134899, |
24 |
>> lost async page write |
25 |
>> [ 2794.535832] Buffer I/O error on dev sdc1, logical block 2134900, |
26 |
>> lost async page write |
27 |
>> [ 2794.535835] Buffer I/O error on dev sdc1, logical block 2134901, |
28 |
>> lost async page write |
29 |
>> [ 2794.535837] Buffer I/O error on dev sdc1, logical block 2134902, |
30 |
>> lost async page write |
31 |
>> [ 2842.568843] sd 9:0:0:0: [sdc] tag#0 FAILED Result: |
32 |
>> hostbyte=DID_ERROR driverbyte=DRIVER_SENSE |
33 |
>> [ 2842.568849] sd 9:0:0:0: [sdc] tag#0 Sense Key : Hardware Error [current] |
34 |
>> [ 2842.568852] sd 9:0:0:0: [sdc] tag#0 Add. Sense: No additional sense |
35 |
>> information |
36 |
>> [ 2842.568857] sd 9:0:0:0: [sdc] tag#0 CDB: Write(10) 2a 00 01 04 a4 |
37 |
>> 58 00 00 f0 00 |
38 |
>> [ 2842.568859] blk_update_request: I/O error, dev sdc, sector 17081432 |
39 |
>> [ 2842.568862] buffer_io_error: 20 callbacks suppressed |
40 |
>> |
41 |
>> nmon says sdc is 100% busy but doesn't show any reading or writing. I |
42 |
>> once pulled the USB stick in a situation like this and I ended up |
43 |
>> having to reformat it which I need to avoid this time since the file |
44 |
>> is crucial. What should I do? |
45 |
>> |
46 |
>> - Grant |
47 |
> |
48 |
> Whatever you do, do NOT try to unplug the USB you were writing to unless you |
49 |
> first manage to successfully unmount it. If you do pull the USB stick |
50 |
> regardless of its current I/O state you will likely corrupt whatever file you |
51 |
> were writing onto, or potentially more. |
52 |
> |
53 |
> You could well have a hardware failure here, which manifested itself during |
54 |
> your copying operation. Things you could try: |
55 |
> |
56 |
> Run lsof to find out which process is trying to access the USB fs and kill it. |
57 |
> Then see if you can remount it read-only. |
58 |
> |
59 |
> Run dd, dcfldd, ddrescue to make an image of the complete USB stick on your |
60 |
> hard drive and then try to recover any lost files with testdisk. |
61 |
> |
62 |
> Use any low level recovery tools the manufacturer may offer - they will likely |
63 |
> require MSWindows. |
64 |
> |
65 |
> Shut down your OS and disconnect the USB stick, then reboot and try again to |
66 |
> access it, although I would first create an image of the device using any of |
67 |
> the above tools. |
68 |
|
69 |
|
70 |
dd errored and lsof returned no output at all so I tried to reboot but |
71 |
even that hung after the first 2 lines of output so I did a hard reset |
72 |
after waiting an hour or so. Once it came back up I tried to do 'dd |
73 |
if=/dev/sdb1 of=usbstick' but I got this after awhile: |
74 |
|
75 |
dd: error reading ‘/dev/sdb1’: Input/output error |
76 |
16937216+0 records in |
77 |
16937216+0 records out |
78 |
8671854592 bytes (8.7 GB) copied, 230.107 s, 37.7 MB/s |
79 |
|
80 |
It's a 64GB USB stick. dmesg says: |
81 |
|
82 |
[ 744.729873] sd 8:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK |
83 |
driverbyte=DRIVER_SENSE |
84 |
[ 744.729879] sd 8:0:0:0: [sdb] tag#0 Sense Key : Medium Error [current] |
85 |
[ 744.729883] sd 8:0:0:0: [sdb] tag#0 Add. Sense: Unrecovered read error |
86 |
[ 744.729886] sd 8:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 01 02 78 e0 |
87 |
00 00 f0 00 |
88 |
[ 744.729889] blk_update_request: critical medium error, dev sdb, |
89 |
sector 16939232 |
90 |
[ 744.763468] sd 8:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK |
91 |
driverbyte=DRIVER_SENSE |
92 |
[ 744.763472] sd 8:0:0:0: [sdb] tag#0 Sense Key : Medium Error [current] |
93 |
[ 744.763474] sd 8:0:0:0: [sdb] tag#0 Add. Sense: Unrecovered read error |
94 |
[ 744.763478] sd 8:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 01 02 79 00 |
95 |
00 00 04 00 |
96 |
[ 744.763480] blk_update_request: critical medium error, dev sdb, |
97 |
sector 16939264 |
98 |
[ 744.763482] Buffer I/O error on dev sdb1, logical block 4234304, |
99 |
async page read |
100 |
[ 744.786743] sd 8:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK |
101 |
driverbyte=DRIVER_SENSE |
102 |
[ 744.786747] sd 8:0:0:0: [sdb] tag#0 Sense Key : Medium Error [current] |
103 |
[ 744.786750] sd 8:0:0:0: [sdb] tag#0 Add. Sense: Unrecovered read error |
104 |
[ 744.786753] sd 8:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 01 02 79 04 |
105 |
00 00 04 00 |
106 |
[ 744.786755] blk_update_request: critical medium error, dev sdb, |
107 |
sector 16939268 |
108 |
[ 744.786758] Buffer I/O error on dev sdb1, logical block 4234305, |
109 |
async page read |
110 |
|
111 |
I haven't tried to mount it yet. Any suggestions? |
112 |
|
113 |
- Grant |