Installer Crashed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubiquity (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Wanted to install ubuntu, booted up the live CD and started an install with an unpartitioned, recently-reformated 300 GB SATA-150 HDD (Maxtor 6B300S0).
Had first 20GB unallocated (for future windows XP/x64 installs).
Then allocated 2GB as a linux-swap partition.
Then allocated 5GB as XFS partition for ubunto install.
Unallocated the rest (planned to use this as a FAT32 storage area in the future).
Set up the 2GB as swap and the 5GB as "/" for root...
It appears the setup has (mostly) completed before it crashed, and I can see the files when I dive into the 5GB partition. I do not know if, upon reboot, it will work correctly or not.
Traceback (most recent call last):
File "/usr/bin/
install(
File "/usr/bin/
ret = wizard.run()
File "/usr/lib/
self.
File "/usr/lib/
self.
File "/usr/lib/
self.
File "/usr/lib/
raise RuntimeError, ("Install failed with exit code %s; see "
RuntimeError: Install failed with exit code 1; see /var/log/
Thanks for your report. Due to some reliability problems with GRUB and XFS, you need to use a non-XFS root filesystem or create a non-XFS /boot filesystem. Bug 47848 is filed to note that the partitioner should warn you about this up-front.