Ubuntu
ubiquity package

feisty life cd does not create bootrecord

Bug #137343 reported by Andrew Frank
2
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

i installed feisty (7.04) today on a brand new disk. used the manual option (did a partition with / and /home before) and assigned the partitions.
feisty completed installation, but did not write the boot record, the system did not boot correctly afterwards.
only when i used the automatic version (used part of the largest partition) then it installed correctly (with a boot menu that included the previously created installation, which later could be booted!). in this case the boot record was written and the system booted correctly into the grub menu and then in either of the two feisty installations.

i have done installations before, but all on machines where window was instaleld and a boot record already written. there the manual assignment of partitions worked well.

please check if for manual partions and no previous boot record on the disk, the boot record is written. this was very confusing (and destroyed the effect of showing a window geek how quickly and easily ubuntu installs)

thank you!
andrew

Revision history for this message
cut (cut) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this bug as a bug in ubiquity.

Revision history for this message
Miguel Ruiz (mruiz) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't start working on it yet, because your description didn't include enough information.

Please include the information requested at https://wiki.ubuntu.com/DebuggingUbiquity/AttachingLogs as separate attachments by visiting your bug's web page. Thanks in advance.

Changed in ubiquity:
status: New → Incomplete
Revision history for this message
Evan (ev) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in ubiquity:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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