[README] Unable to reconstruct
There's a chance you are not doing something wrong.
Reconstruction just doesn't work yet for all archives that use compressed RARs.
[README] Unable to reconstruct
Forum
» General discussion / ReScene
» [README] Unable to reconstruct
Summary:
No guarantees for compressed RARs.
"ValueError: Still not fine :("
Try playing with the new --mt-set option!
e.g. --mt-set 4,6,8 when it failed on rar.exe -mt2
[11:28:40] <@YopoM> Gfy, you asked yesterday about rar locking; On this one that fails, it is not locked, which is surprising, because I thought all rared files were locked, turns out they are not (all of the rar files I create are both locked and solid).
[11:29:05] <@YopoM> I ran into another one that cannot be re-created (and it's only 300mb, so easier to test).
[11:31:46] <@YopoM> "Solid archive is an archive packed with a special compression method, which treats several or all files within the archive as one continuous data stream. WinRAR supports solid mode only in RAR archiving format, ZIP archives are always non-solid. Use Create solid archive option in archiving dialog or -s command line switch to enable solid archiving."
[11:32:09] <@YopoM> do we use -s switch in trying to re-create?
[11:36:28] <@YopoM> http://pastebin.com/3XgU4Dpf
[11:37:15] <@YopoM> it says bin is solid, cue is not
[12:00:14] <linear> lots of bin/cue releases fail on the cue after successfully compressing the bin, probably for this reason
[12:00:47] <linear> it would be very useful if that could be resolved
[12:01:11] <linear> its kind of weird that they should be packed like that at all, as solid is only really beneficial when dealing with a large number of small files
[12:01:37] <linear> and treating a single file as solid archive is meaningless
[12:28:01] <@Gfy> we check solid, but not sure if done correctly in all cases
[12:28:09] <@Gfy> I think the first file can never be solid
[12:28:29] <@Gfy> the second file is solid, which means it continues on the compression used on the first file
[12:28:59] <@Gfy> locking is just a flag in the srr header afaikTo investigate.
RAR 3.80 Copyright (c) 1993-2008 Alexander Roshal 16 Sep 2008
Shareware version Type RAR -? for help
Solid volume fas-song.rar
Name Size Packed Ratio Date Time Attr CRC Meth Ver
Host OS Solid Old
-------------------------------------------------------------------------------
fas-song.cue 71 72 101% 31-08-13 16:18 .....A. EB7A69AC m5g 2.9
Win95/NT No No
fas-song.bin 307434624 14999790 --> 31-08-13 16:26 .....A. B987D355 m5g 2.9
Win95/NT Yes No
-------------------------------------------------------------------------------
2 307434695 14999862 4% volume 1
If No guarantees for compressed RARs, what's the point of creating the srr file?? They cannot be used to restore the original release RAR.
After all, many releases' original RAR have compression method used. I have tried 5 releases with compression used and they all failed to reconstruct.
Hopefully the issue should be resolved soon.
A lot of releases do work especially releases with only a single file, usually iso images.
I have successfully reconstructed a few hundred releases but I also have a lot which do not work.
Sometimes you need to take special steps to succeed e.g. only have one specific rar version in your rar directory or force a specific mt switch and always verify the crc of the reconstructed rar files as there can be bad parts.
Maybe a list of releases which do not work could be made on the wiki.
guys why is this happening??
srrGUI: srr.exe Z:\MMM100.E004.Kristina.Hard.Sofa.XXX.WMV-ER0S.srr -ypri \\MACBOOK\Downloads\ -o \\MACBOOK\Downloads\MMM100.E004.Kristina.Hard.Sofa.XXX.WMV-ER0SsrrGUI: Process running, please wait…
SRR file created with pyReScene Usenet 1.6.
Re-creating stored file: mmm100e004khs-er0s.nfo
Re-creating stored file: mmm100e004khs-er0s.sfv
Re-creating RAR file: mmm100e004khs-er0s.rar
The file does not exist: \\MACBOOK\Downloads\mmm100e004khs-er0s.wmv.
srrGUI: Process completed. srr.exe exit code = 1
it creates rar file 64kB big and thats it… any idea why this is happening?
/forum/t-747014/readme-unable-to-reconstruct#post-