This is the same file. Both files start with:
ffpstick started at Sat Mar 12 16:21:05 GMT 2011
When you rebooted again ffpboot.log became ffpboot.log.1.gz, ffpboot.log.1.gz became ffpboot.log.2.gz, ...
So I need the file with the higest number, which is the initial boot (unless it shifted out after beeing ffpboot.log.9.gz).
But you interrupted the initial install? In that case it is possible that the logfile doesn't exist. The initial install does:
1-Copy the content of the stick to RAM
2-Restart the script in RAM
3-Repartition the stick in two partitions
4-Format the first partition FAT
5-Put the files for partition 1 back
6-Format the second partition EXT3
7-Put the files for partition 2 back
8-Wait for the partitions to be mounted by the firmware
9-Move the logfile from RAM to partition 1
10-Download and install FFP on partition 2
According to the logfile you uploaded, the stick has two partitions, the first partition at least contains a few files, the second partition cannot be mounted (Will try to mount ffproot myself; mount: you must specify the filesystem type
), so it's probably not formatted. So the process can have been interrupted during step 5 or step 6. In that case there is no logfile.
Another possibility is that the stick already had two partitions when you started. In that case the script assumed that the initial boot was already done (Check /dev/sdb for number of partitions... /dev/sdb has 2 partitions
), and it would not try to apply the initial boot. (In that case the files for partition 2 (after_booting.sh and rootfs.tgz) are still on partition 1)
The only way to get the initial boot running again, is to remove the second partition, and start over with the initial files. I hope Windows 7 diskmanager can remove that partition.