← Back to team overview

mythbuntu-bugs team mailing list archive

Re: [Bug 485083] Re: 9.10 system left unbootbale with enire disk install method.

 

Sure! Anything I can do to help.
I am not 100% sure that was the disk layout at the time of install; I
might have removed some disks during install just to be safe. But 90%
certain that was.

Let me know anything else you need.



On Tue, Jan 26, 2010 at 03:26:06PM -0000, MarcRandolph wrote:
> Thank you for helping to improve Ubuntu by opening this ticket.   I am
> marking this ticket as confirmed because it appears to have enough
> information to help the developers understand the problem.  It is
> possible I am wrong and another more experienced triager or developer
> may adjust the status of the ticket to "incomplete" and request
> additional information.
> 
> ** Changed in: ubiquity (Ubuntu)
>    Importance: Undecided => High
> 
> ** Changed in: ubiquity (Ubuntu)
>        Status: Incomplete => Confirmed
> 
> ** Changed in: mythbuntu
>        Status: Incomplete => Invalid
> 
> ** Summary changed:
> 
> - 9.10 system left unbootbale with enire disk install method.
> + 9.10 system left unbootable with entire disk install method
> 
> -- 
> 9.10 system left unbootable with entire disk install method
> https://bugs.launchpad.net/bugs/485083
> You received this bug notification because you are a direct subscriber
> of the bug.

--


--------------
Regards
David

-- 
9.10 system left unbootable with entire disk install method
https://bugs.launchpad.net/bugs/485083
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to Mythbuntu.

Status in Mythbuntu, Ubuntu derivative focused upon MythTV: Invalid
Status in “ubiquity” package in Ubuntu: Confirmed

Bug description:
I tried with the same system, a system previously running Ubuntu 7.10 w/ MythTV on it, and 2 different disks to install Mythbuntu 9.10 choosing the "Use entire disk" method and the system is unable to boot.

Further points:

1. The disk doesn't have the bootable flag set
2. The disk is not in the first SATA port and has other disks on the system to be later used with the system, but not setup during the install.
3. Choosing to manually partition on a subsequent install, at the end I click Advanced and found the bootloader was to be installed on hd(0,0) but I am not sure which disk grub was mapping that too, so I choose the disk manually and that install worked.
4. When it fails to load, it's a case of hanging, it seems to find something to boot off the disk, but one is left with a flashing underscore cursor with no text on the screen.





References