Over-writing a boot partition fails obscurely

Bug #38168 reported by Jack Wasey
8
Affects Status Importance Assigned to Milestone
base-installer (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

I attempted to install Dapper over a Breezy install, but not with dist-upgrade. I was moving from amd64 to i386. I had a new root partition, but wanted the same boot partition. I chose NOT to format the boot partition (I wanted to be able to boot into the previous install). This led to the "install base system" step failing half-way through with no explanation. It turned out that it couldn't work out what to do with the old amd64 kernels in /boot. I'm afraid I can't remember the exit messages or problems, and I don't care to repeat the experience.

Revision history for this message
Connor Imes (ckimes) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release?

It makes sense that the system wouldn't know what to do with kernels for a different architecture. I'm not sure that's actually a bug. The proper way to allow booting into both systems is to setup a dual boot.

Thanks in advance.

Changed in base-installer:
status: New → Incomplete
Revision history for this message
Colin Watson (cjwatson) wrote :

The bug is "fails obscurely", not "fails". I doubt that this has been fixed yet, so setting to Triaged in the hope that people will stop poking this bug.

Changed in base-installer:
status: Incomplete → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.