Avoiding corrupted uploads to Mega, using md5 checksum files?

[remol]

(SOLVED) Avoiding corrupted uploads to Mega, using md5 checksum files?

My Internet connection breaks up very often.
I want to upload many folders and files to the cloud service Mega.
I created a checksum .md5 file and I would like to use it to verify that none of the files is corrupt.
Is it possible to do anything to verify the files in Mega are OK and not corrupt? I'm concerned about these things mainly because my connection is so unstable. The only solution I know everything is ok, is to download the files, from Mega, and then check these files with the checksum file in my Windows 7. But I'd prefer not to do this since it takes too much time.
Any ideas? Thanks in advance.

 

[Alejandro85]

As far as I know no, you can't verify them online without downloading them again as you suggest (and suffering from the double transfer). The real problem is that once you upload files there, you have effectively no access to them in any way, other than download or delete them, hence you can verify them "online". Maybe the server itself provides hashes on their website, but don't know if that really exist.

A workaround could be to split the files in smaller parts and upload those instead. So you end up uploading 10 100MB files instead of a single 1GB file, for example. In the event of a broken part, reupload that single piece is easier, and chances of disconnections are less for shorter uploads.
Also, remember to upload the checksums themselves too, so that they can be verified afterwards when you actually need to use the files.

 

[remol]

Thanks, I've finally downloaded and checked the copy against the local .md5 file
Yes, I had the big files divided into small parts by using winrar (without compression, since it was used for mp3 files), which helped me uploading, since my bandwidth is smaller for uploads...
I've had some issues when downloading the files, because from my Desktop (the destination for the files I've chosen) the files were disappearing after a while, but not the folders. It was strange to me, this happened twice... but it was solved changing the destination directory.
The problem is gone now. Cheers!