That's what I told the client:

The initial release of 8.2.13.219 platform. The current release of 8.2.16.352 platform. Updated without problems and restructuring is successful. Original Release configuration PSU 2.0.32.1. Updated on release 2.0.41.3. In the most crucial moment suddenly run out of space on the disk.

chdbfl.exe says:

Damaged header of the database file is damaged contents of the internal faylaBaza completely destroyed can not be restored.

Tool_1CD.exe does not help ...

To begin, I used the project http://code.google.com/p/restoration-base-1c8/

I used the 0.2.2 configuration. (At time of publication version is not laid because small improvements which will tell below, lined with version 0.1.7 for the actual restoration is not appropriate, there are too many errors, it is more exploratory in nature)

To start the renamed file and uploaded it, loading was 2 hours (file size is about 1.8 gig, loading is long including by the fact that the root object is not used). During the boot process I obmaterili

1. a dozen messages like "Error table describe the flow" _REFERENCE54 ", Block 00 00 0F 6C E0 00" it really is a bug restore configuration, but I quickly realized what was happening, a table where the description covers more than one unit loaded only one manually reload (search index and a button "Upload data block"), well, and by this to the instructions after the table "Load structure of branches." (This is one error that prevents lay version 0.2.2)

2. A more serious problem that was the message such as "In the description of the root block table 00 00 67 97 00 A0 contains invalid characters."

Locate the power shake "Edit table", getting rice "n-1", it is clear that the description of the table intact just after it comes the "tail" of garbage, I go into the box and scoring zeroes this garbage. (Second revision required - necessary procedure oblosti clogged with zeros, I'm just worn out one figachit).

After the error was gone, I press the "Download the structure of branches."

Unfortunately one table was not subject how to reset, but on reflection, I realized that this is a table of the new configuration, and it is just an empty, so I decided to score it.

At this stage, everything seems to look nice, but it still does not work.

Then climb to the root object "edit table" and I see clearly that the length of the curve (in the picture already Revised), well, I climb into the description of the root and correct length.

then Tool_1CD.exe produces only 1 error and chdbfl.exe two and says that can help.

Launch chdbfl.exe to correct base and started up in the enterprise mode, and like all the data intact.

go on (the last picture)

Given that some of the blocks incorrectly distributed (pictured gray) and the root object has links to FREE blocks, run on the basis of any fraud in the configuration is not necessary, is through XML upload all moved to a new clean database and have to work with it.