9.10 system left unbootable with entire disk install method

[DaveQB]

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.

[DaveQB (david-dward)]

I think I put everything in the description, was that wrong? :)

[KingOfKYA (tkneal2)]

Same problem on my system s it giving a grub Error 15 too. I notice on mine /boot/grub that there is no files in it. tested on 2 systems an amd seperon 3000+ and atholon64. Note it aperes to do the same thing on manual install. will report back if I figure it out.

[Mario Limonciello (superm1)]

Hi DaveQB:

When installing grub to the MBR, the bootable flag is irrelevant. That only matters if you are using a DOS MBR.

It might be a little late now since you were able to successfully install by choosing where to install the booloader on a subsequent installer, but would you mind elaborating on the exact configuration of your drives from the failed install?

Eg:
IDE port 0: drive I'm not doing anything with
Sata port 0: nothing connected
Sata port 1: drive I installed to

What order did you have them configured to boot from the BIOS as well?

Thanks,

[DaveQB (david-dward)]

The system is still going and has the sames disks in it it had then, I
believe.
I'll attach fdisk, /proc/mdstat and pvdisplay. I hope that helps.

On Mon, Jan 25, 2010 at 07:47:40AM -0000, Mario Limonciello wrote:
> Hi DaveQB:
>
> When installing grub to the MBR, the bootable flag is irrelevant. That
> only matters if you are using a DOS MBR.
>
> It might be a little late now since you were able to successfully
> install by choosing where to install the booloader on a subsequent
> installer, but would you mind elaborating on the exact configuration of
> your drives from the failed install?
>
> Eg:
> IDE port 0: drive I'm not doing anything with
> Sata port 0: nothing connected
> Sata port 1: drive I installed to
>
> What order did you have them configured to boot from the BIOS as well?
>
> Thanks,
>
> ** Also affects: ubiquity (Ubuntu)
> Importance: Undecided
> Status: New
>
> ** Changed in: ubiquity (Ubuntu)
> Status: New => Incomplete
>
> ** Changed in: mythbuntu
> Status: New => Incomplete
>
> --
> 9.10 system left unbootbale with enire 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

[MarcRandolph (mrand)]

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.

[DaveQB (david-dward)]

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

[skybon (skybon-deactivatedaccount-deactivatedaccount)]

This bug was last seen 3 years ago and belongs to unsupported distribution. If you notice this bug in 10.04, 12.04 or 12.10, feel free to reopen it.