Crunch qutting one me. (error code 2)

[Nazagul]

here's what i run...
./crunch 1 5 -f charset.lst mixalpha-numeric-all-space -b 2gib -o START
Crunch will now generate the following amount of data: 46837566140 bytes 44667 MB 43 GB
Crunch will now generate the following number of lines: 7820126495
5%
10%
14%
19%
23%
28%
32%
37%
42%
46%
51%
Error renaming file. Status2 = -1 Code = 2
The problem is = No such file or directory

tried different drives, repeating it, etc. Always stops at 51%. There is plenty of room on the drive, (400GB's plus) but for some reason it just stops.
What am I doing wrong?

[TAPE]

Hey there, the syntax you are using is correct if you want to place the 21/22 2gib files on the
drive that you are running BT from.

Just out of inteterest, you are not trying to save on an external drive are you and mistakenly using
-o START instead of -o /media/mydrive/START for instance are you ?

I have to admit that I have never attempted to create a 43gig wordlist.. so can really help you with
what may be causing the problem.

Hopefully bofh28 will see this post (he will) and hppe he may be able to advise what the possible cause may be.

[thorin]

When it stops do you have 9 or 10 2gib files in the output directory?

[Nazagul]

When it stops do you have 9 or 10 2gib files in the output directory?

It has 9 files in the output directory.
@TAPE, no I copy crunch over to where I want the output to be.

[TAPE]

Interesting, so as long as you are writing to the disk using the -o START in the right location,
I cannot think of much..

I was thinking however, the error message is referring to file / directory ...
when using the -b option crunch writes out files of the given size which are named following the
1st entry and the last entry.
Is it possible that the first or last entry is containing a character that actually is messing up the
file name and how the file is (able to be) read ?

Have you tried with slightly different sizes ?
so

./crunch 1 5 -f charset.lst mixalpha-numeric-all-space -b 1999mib -o START
or
./crunch 1 5 -f charset.lst mixalpha-numeric-all-space -b 1999mb -o START

to see whether that change in resulting filenames may give different results ?

Can you advise what was the last entry in the last file created ?

[Nazagul]

@Tape,
yes I've tried different sizes, and they get to different percents, but (ie, 47% instead of 51%) but always end in the same error. I have been able to generate one, with no division of the wordlist.

[TAPE]

Then it sounds very likely that characters in the output filename are containing special characters which
may be messing up with the way how the files are (able to be) read..

Can you provide an example of the last words in the last file before it quits ?

This is rather an interesting bug if it is the filename that is causing it, I talk to bofh28 occasionally
on crunch to pass on things I find (fingers crossed for crunch v3.0 soon ) and would like to make sure that
if this is a bug he can look at it before v3.0 is released.

So if you can give as much detail on the last words created in files prior to crunch quitting and wihich syntax you
had used, that would be great.

[Nazagul]

I can't open the file, (its 2gb) but I checked the directory and it said that this file was modified last.
N0hUX-R>YZ#.txt. So I'm assuming this is the generated line before it went kaput. Not sure what else I can give you, both crunch 2.8 and 2.9 give the same error.

[thorin]

Is "N0hUX-R>YZ#.txt" the file name, the last line in the file, or the output on the screen?

If it's a filename I'm 99% sure the greater than character is what's causing the problem (maybe the number sign too), but since greater than is used for output redirection on the command line it's my guess.

[TAPE]

That sounds likely, waiting for bofh28 to view and advise on the issue, but when I am able to might do a few tests
to confirm the error myself.

Edit
----
OK, so at the airport and doing a few tests (no, not airbase and goatse..)

I have done a quick test based on using R>YZ# as starting point for a crunch wordlist ;

./crunch 1 5 -f charset.lst mixalpha-numeric-all-space -s R>YZ#

and it seems to pass on the R> part.. I will have to do a few more tests when back behind my main machine, however it really seems that the filename is causing the problem.
I am 99.9% sure its that. (Probably will live to regret saying that )

Thanks for the advice on this bug as it is something that not many would have found, who the hell goes for creating a 43gib 1-5 character file .. nice catch.

bofh28 will maybe not be so happy as he was close (I think) to being ready for the release of v3.0 ..

Ah well..

Please post any further info known pertaining to the aforementioned problem, so that it
can be properly sorted.

Thanks