This looks like a repeat of bug #539027, which is still open. Are there any other messages shown on the console at this point? Has this only started happening with the latest candidate image? Is it consistently reproducible across multiple install tests in the hardware in question?
This looks like a repeat of bug #539027, which is still open. Are there any other messages shown on the console at this point? Has this only started happening with the latest candidate image? Is it consistently reproducible across multiple install tests in the hardware in question?