aMule Forum
English => en_Bugs => Topic started by: falcon7 on January 07, 2010, 07:14:08 PM
-
I run Ubuntu 8.10 with aMule 2.2.2
Hi everyone and thanks in advance for any possible help/idea :D
I was downloading fine when my hdd space ended, after i freed some space on it moving some folders (that have nothing to do with amule) on another hdd, i found the following situation:
I tried to RESUME the STOPPED downloads and some turned ERRONEOUS, checked permissions of the folder and they're fine (some other files are still being downloaded indeed), tried a suggested procedure (quitting, removing PREFERENCES + KNOWN.MET and restarting) but nothing changed, i even checked in the TEMP folder for the correspondent .PART files and strangely some of em are missing, some others are still there instead (always talking about the ERRONEOUS marked files of course), in fact if i right click on an ERRONEOUS file and try to watch its preview, VLC does open it and shows it to me, not for all of em of course, the ones with the .PART file missing are not being shown...
This is what the aMule log shows "PartFiles: Error while saving part-file: SafeIO::IOFailure: Error writing to file: Input/output error"
What happened? Could someone suggest a solution? I feel like i tried everything and I really don't want to CANCEL them all and re-start downloading em all over.
THANKS
-
Have you run a file system check on the drive with your temp files? If not please do it.
-
A file system check with my temp files? could you be more specific please, thank you
-
A filesystem check of the filesystem where your part files are. Also, a hard drive scan for errors. And RAM scan for errors. One of them is the culprit.
-
... or the fact that it's 2.2.2 and the hdd physically ran out of space.
I'd suggest upgrading to 2.2.6 and set a reasonable amount in Preferences->Files->Minimum free disk space.
About recovering the files marked 'Erroneous':
- if the .part file is missing (or its size is zero), you can do nothing but re-download that file.
- if the .part.met file is missing but there's a non-zero sized .part.met.bak, you can rename the backup (although it might not help in some cases).
- otherwise, you can do the following, for each erroneous file:
1) stop aMule, and move the .part file out of the incoming directory, delete the other files corresponding to that download.
2) restart aMule and restart downloading that file, and wait until at least one part is finished
3) stop aMule
4) move the old .part file (the one you moved away) back to the incoming folder, and make sure you overwrite .part file of the newly started download.
5) restart aMule. It will rehash the file, giving you back all the finished parts.
6) repeat this for all the files you want to recover.
-
set a reasonable amount in Preferences->Files->Minimum free disk space.
And also make sure 'Check free space' is enabled.
-
Or that.
-
6) repeat this for all the files you want to recover.
You can also go through these steps for all of your files together.
-
ok, thank you all for the advices. I tried to do as suggested but unfortunately most of the .part(s) were missing, so i just deleted all the erroneous ones and start them back all over... now, i just would like to know what caused what happened, i haven't found a clue about the reason so far, neither on ubuntu's logs nor on amule's logs... any idea?
id like to understand what happened in order to prevent it in the future
thanks very much for your support
-
A filesystem check of the filesystem where your part files are. Also, a hard drive scan for errors. And RAM scan for errors. One of them is the culprit.
Did you do that?
-
Performed the first 2 and everything seems to be fine. I don't know how to perform the RAM scan for errors...
Anyway now it works pretty well, but it crashes now and then. I remember I already had this problem in the past and I solved it by incrementing (in Ubuntu) the max number of files possibly opened by an application, and it never crashed anymore... Now it's back to it... Any other possible reason? thanks
P.S.
And if you could also suggest how to run a RAM scan for errors, thanks
-
memtest86