I ran two installations of today's precise image in a row under a current precise host with precise kernel, then two more under precise host running a lucid kernel, and all four succeeded. In the VM (under the live system) I also tried to copy /bin/ to /target 10.000 times in all four cases which also did not trigger the bug. But I guess I've just been lucky here, or something else in my environment is different. In all cases I was using virtio for the VM hard disk.
Does this also happen when not using virtio? If not, this might provide a workaround for the time being.
I ran two installations of today's precise image in a row under a current precise host with precise kernel, then two more under precise host running a lucid kernel, and all four succeeded. In the VM (under the live system) I also tried to copy /bin/ to /target 10.000 times in all four cases which also did not trigger the bug. But I guess I've just been lucky here, or something else in my environment is different. In all cases I was using virtio for the VM hard disk.
Does this also happen when not using virtio? If not, this might provide a workaround for the time being.