GRUB failed to install on 'dummy'.

[Sam]

Note: This is a Ubuntu Secure Remix 12.10 Live USB. I will attempt again with a normal Ubuntu Live USB.

Second attempt to dual-boot install Ubuntu on a brand new Lenovo Z580 after the first install's GRUB was mysteriously overwritten by the preloaded Windows 8.

I chose to format the / and /home mountpoints. I assumed the UEFI system partition was automatically selected.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: ubiquity 2.12.16
ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
Uname: Linux 3.5.0-17-generic x86_64
ApportVersion: 2.6.1-0ubuntu3
Architecture: amd64
CasperVersion: 1.328
Date: Tue Nov 13 17:00:10 2012
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi.signed file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash --
LiveMediaBuild: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Sam (krazi-bazil)]

This may be too little too late, but I managed to work around the issue a few days after posting this report. It had something to do with a dirty filesystem; possibly the UEFI system partition or either of the Windows-related partition. I ran a few fscks/chkdsks and attempted the install again, and it worked.

I'll leave this bug open for someone else to consider. I feel that the installer should have provided a slightly more insightful error rather than freezing, which is, IIRC, what happened.

[Phillip Susi (psusi)]

I don't suppose you have the log of what chkdsk found and repaired do you?

[Sam (krazi-bazil)]

Hang fire, I'll if I can find it in the Event Log when my Dad gets home. Although we're a bit wary of trying to boot Windows because last time, the newly installed GRUB boot entry was overwritten. I don't know whether that was my Dad's fault, however.

[Sam (krazi-bazil)]

Unfortunately, I couldn't find any logs, nor boot into Windows. I think that there's also a chance that I ran fsck on a live USB environment, so the logs would have been lost immediately afterwards.