hello everyone.

 

I am no linux specialist and I can't seem to find an easy way to do something that I am pretty sure sound simple to some of you.

 

I have connected an NTFS drive to my unraid.

mounted it as read only using ntfs-3g

and copied the content of the whole disk to one of my unraid disk.

 

before clearing the disk I would like to do a file/folder compare of all the copied files to make sure the copy was successful

anyone has an idea or a tool that could help ?

 

the source folder being /mnt/user/ntfs

the destination folder /mnt/disk3/tempo

it contains a bunch of files/folders

I am not sure it would make a real difference but i am running 4.7

 

Cheers,

R

Quick and dirty would be

diff -r /mnt/user/ntfs /mnt/disk3/tempo

If you get no output from the diff command, everything is the same.  Of course if you have written other data to the /mnt/disk3/tempo directory then this won't work quite as cleanly

@spectrum

 

that's what I ran.

but the no output worried me.. I was expecting at least an "ok"... lol

so this mean that I am ready to run ! thanks a lot.

too bad there is no other "more obvious" tool to use for this type of purpose as a lot of people are doing that to start their array...

 

Cheers,

R

@spectrum

 

that's what I ran.

but the no output worried me.. I was expecting at least an "ok"... lol

so this mean that I am ready to run ! thanks a lot.

too bad there is no other "more obvious" tool to use for this type of purpose as a lot of people are doing that to start their array...

 

Cheers,

R

 

The more obvious tool to use would be md5deep to generate a list of md5 sums from the source, then use the list to check the destination.  The list can also be saved for verifying integrity later if you want to hang on to it.  I just didn't take the time to look for a Slackware package or to build one.  I might build a Slack package an unMenu package for it some time but don't hold your breath

@spectrum

 

that's what I ran.

but the no output worried me.. I was expecting at least an "ok"... lol

so this mean that I am ready to run ! thanks a lot.

too bad there is no other "more obvious" tool to use for this type of purpose as a lot of people are doing that to start their array...

 

Cheers,

R

 

The more obvious tool to use would be md5deep to generate a list of md5 sums from the source, then use the list to check the destination.  The list can also be saved for verifying integrity later if you want to hang on to it.  I just didn't take the time to look for a Slackware package or to build one.  I might build a Slack package an unMenu package for it some time but don't hold your breath

unMenu has md5deep ready to install now.

Ahh I missed that.  Thanks for the heads up so I don't go redoing something that has already been done!

Ahh I missed that.  Thanks for the heads up so I don't go redoing something that has already been done!

It is even more interesting than that.  The package manager in unMENU downloads the md5sum source code from sourceforge and compiles it on the unRAID server.  All with a few clicks of a button.

 

It takes three clicks to install the gcc compiler. One to select the package, one to download it and all the libraries needed, and one more to install it.  Then three more clicks to select the md5sum package, download it, and one last to compile and install it.

 

Joe L.

everyone,

 

thank you so much for the info.

I will give it a shot and revert on how easy/hard it is to use

 

Cheers,

R

ok,

 

md5deep works like a charm even though I would love to see a better ETA/PROCESSING

 

I did not feel like making my life a living hell so when I mounted the ntfs drive I did it as read only to avoid any mistake

 

source : /mnt/user/ntfs/*

destination : /mnt/diskX/OLDDISK/*

 

here is what I have been doing :

 

first create the MD5 for all the files

 

cd /mnt/user/ntfs/
md5deep -e -l -r * >/boot/hashes.txt

cd /mnt/user/ntfs/ you have to go to the source folder to allow the use of relative folders

-e gives me an ETA per file.. not very useful information as per say but it was the only way I could think of that gives some kind of progress + it felt good to see the process is still running.

-l keeps relative filenames so you don't have to edit the resulting file at the end

-r * is recursive for all

>/boot/hashes.txt because as i mentioned I used a read only mounted disk so I wanted to store the file in an easy location.

 

then compare the copied file

 

cd /mnt/diskX/OLDDISK/
md5deep -e -x /boot/hashes.txt -r *
md5deep -e -x hashes.txt -r *

cd /mnt/diskX/OLDDISK/ once again this is to make it easier by using relative path

-e same reason as above, otherwise you might think that the process is not running

-x /boot/hashes.txt

-r * recursive call for all files

 

I hope it can help someone.

 

Cheers,

R