/dev/mmcblk0p1 does not have any corresponding BIOS drive

[robinfxdl]

Binary package hint: ubiquity

 I was in the process of installing Ubuntu 9.04 to a 16GB SDHC card. The install was to put the Grub boot loader on a 4GB USB thumb drive that has Ubuntu 9.10. The grub install failed, I do not know why. I have tried installing Ubuntu 9.10 on the SDHC card but that fails with portions of the file system missing (eg nothing in the proc folder or incomplete dev folder).

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
InterpreterPath: /usr/bin/python2.6
MediaBuild: Ubuntu 9.04 "Jaunty Jackalope" - Release amd64 (20090420.1)
Package: ubiquity 1.12.12
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/python /usr/lib/ubiquity/bin/ubiquity --only
ProcEnviron:
 LANGUAGE=
 PATH=(custom, no user)
 LANG=en_US.UTF-8
PythonArgs: ['/usr/lib/ubiquity/bin/ubiquity', '--only']
SourcePackage: ubiquity
Title: ubiquity crashed with InstallStepError in configure_bootloader()
Uname: Linux 2.6.28-11-generic x86_64
UserGroups:

[Colin Watson (cjwatson)]

Jan 10 00:23:30 ubuntu grub-installer: info: Installing grub on '/dev/sdb'
Jan 10 00:23:30 ubuntu grub-installer: info: grub-install supports --no-floppy
Jan 10 00:23:30 ubuntu grub-installer: info: Running chroot /target grub-install --no-floppy "/dev/sdb"
Jan 10 00:23:30 ubuntu grub-installer: You shouldn't call /sbin/grub-install. Please call /usr/sbin/grub-install instead!
Jan 10 00:23:30 ubuntu grub-installer:
Jan 10 00:23:39 ubuntu grub-installer: Probing devices to guess BIOS drives. This may take a long time.
Jan 10 00:23:40 ubuntu grub-installer: /dev/mmcblk0p1 does not have any corresponding BIOS drive.
Jan 10 00:23:40 ubuntu grub-installer: error: Running 'grub-install --no-floppy "/dev/sdb"' failed.

This looks quite likely to be fixed by 9.10 with GRUB 2. Would you mind retesting?

[robinfxdl (robinfxdl)]

Colin,
    Thanks for the response. I had tried Ubuntu 9.04 because my previous attempts to install Ubuntu 9.10 had failed. There were no traps but I did receive install errors. However I retried Ubuntu 9.10 as you suggested again and this time the install completed without any indications of a trap or errors. The difference between this attempt and the prior attempts is that on the prior attempts I had selected either to do the install Ubuntu 9.10 without activating the network after starting Ubuntu 9.10 from CD or tried the install without first loading Ubuntu 9.10 from CD.
     This time I did the following:
Started Ubuntu 9.10 from CD.Started the network support.Launched the Install from the Desktop Icon.

The only difference between the successful install and failed attempts is that network was activated. Not sure why this would matter. Booting from a SDHC however does not work because the Grub loader is unable to find the drive.

Thanks.
Regards,
   Robert.

> Date: Tue, 19 Jan 2010 19:03:37 +0000
> From: <email address hidden>
> To: <email address hidden>
> Subject: [Bug 505396] Re: ubiquity crashed with InstallStepError in configure_bootloader()
>
> Jan 10 00:23:30 ubuntu grub-installer: info: Installing grub on '/dev/sdb'
> Jan 10 00:23:30 ubuntu grub-installer: info: grub-install supports --no-floppy
> Jan 10 00:23:30 ubuntu grub-installer: info: Running chroot /target grub-install --no-floppy "/dev/sdb"
> Jan 10 00:23:30 ubuntu grub-installer: You shouldn't call /sbin/grub-install. Please call /usr/sbin/grub-install instead!
> Jan 10 00:23:30 ubuntu grub-installer:
> Jan 10 00:23:39 ubuntu grub-installer: Probing devices to guess BIOS drives. This may take a long time.
> Jan 10 00:23:40 ubuntu grub-installer: /dev/mmcblk0p1 does not have any corresponding BIOS drive.
> Jan 10 00:23:40 ubuntu grub-installer: error: Running 'grub-install --no-floppy "/dev/sdb"' failed.
>
> This looks quite likely to be fixed by 9.10 with GRUB 2. Would you mind
> retesting?
>
> ** Package changed: ubiquity (Ubuntu) => grub-installer (Ubuntu)
>
> ** Summary changed:
>
> - ubiquity crashed with InstallStepError in configure_bootloader()
> + /dev/mmcblk0p1 does not have any corresponding BIOS drive
>
> ** Visibility changed to: Public
>
> --
> /dev/mmcblk0p1 does not have any corresponding BIOS drive
> https://bugs.launchpad.net/bugs/505396
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “grub-installer” package in Ubuntu: New
>
> Bug description:
> Binary package hint: ubiquity
>
> I was in the process of installing Ubuntu 9.04 to a 16GB SDHC card. The install was to put the Grub boot loader on a 4GB USB thumb drive that has Ubuntu 9.10. The grub install failed, I do not know why. I have tried installing Ubuntu 9.10 on the SDHC card but that fails with portions of the file system missing (eg nothing in the proc folder or incomplete dev folder).
>
> ProblemType: Crash
> Architecture: amd64
> DistroRelease: Ubuntu 9.04
> ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
> InterpreterPath: /usr/bin/python2.6
> MediaBuild: Ubuntu 9.04 "Jaunty Jackalope" - Release amd64 (200...

[Phillip Susi (psusi)]

Have you been able to try this with 10.04 or 10.10?

[robinfxdl (robinfxdl)]

I have tried it with 10.10 and it did not work. I get a "error: no such device" error.

Sent from my iPod

On Nov 1, 2010, at 2:15 PM, Phillip Susi <email address hidden> wrote:

> Have you been able to try this with 10.04 or 10.10?
>
>
> ** Changed in: grub-installer (Ubuntu)
> Status: New => Incomplete
>
> --
> /dev/mmcblk0p1 does not have any corresponding BIOS drive
> https://bugs.launchpad.net/bugs/505396
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “grub-installer” package in Ubuntu: Incomplete
>
> Bug description:
> Binary package hint: ubiquity
>
> I was in the process of installing Ubuntu 9.04 to a 16GB SDHC card. The install was to put the Grub boot loader on a 4GB USB thumb drive that has Ubuntu 9.10. The grub install failed, I do not know why. I have tried installing Ubuntu 9.10 on the SDHC card but that fails with portions of the file system missing (eg nothing in the proc folder or incomplete dev folder).
>
> ProblemType: Crash
> Architecture: amd64
> DistroRelease: Ubuntu 9.04
> ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
> InterpreterPath: /usr/bin/python2.6
> MediaBuild: Ubuntu 9.04 "Jaunty Jackalope" - Release amd64 (20090420.1)
> Package: ubiquity 1.12.12
> ProcAttrCurrent: unconfined
> ProcCmdline: /usr/bin/python /usr/lib/ubiquity/bin/ubiquity --only
> ProcEnviron:
> LANGUAGE=
> PATH=(custom, no user)
> LANG=en_US.UTF-8
> PythonArgs: ['/usr/lib/ubiquity/bin/ubiquity', '--only']
> SourcePackage: ubiquity
> Title: ubiquity crashed with InstallStepError in configure_bootloader()
> Uname: Linux 2.6.28-11-generic x86_64
> UserGroups:
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/505396/+subscribe
>

[robinfxdl (robinfxdl)]

Phillip,
   After my last response I was able to get it to boot from /dev/mmcblk0p1 using Ubuntu 10.10. I am not sure why it did not work at first, but maybe my explaining what I did may help you determine why.
The following is what I did.

1. I installed Ubuntu 10.10 on a USB thumb drive, and placed the Grub loader on the MBR. The boot menu did
     display OK and I was able to boot Ubuntu 10.10 from the drive OK. The menu did show the previous version
     of Ubuntu on /dev/mmcblk0p1 but I was never able to get it to boot.

2. After I received your note requesting a test of using Ubuntu 10.10, I installed Ubuntu 10.10 on
     /dev/mmcblk0p1 and placed the grub loader on the /dev/sdb which is the MBR of my thumb drive from step 1.
     This was to ensure that the Grub menu would be updated for this version of Ubuntu.

3. I tried booting from the thumb drive in step 1 but the Grub menu never displayed. Instead I got the message
     I reported in my previous note and was place in the Grub rescue screen.

4. After not being able to restore the MBR, I reinstalled Ubuntu 10.10 to the USB thumb drive and placed the
     grub loader on the MBR as I had done in step 1.

5. When I booted from the thumb drive, the Grub menu displayed included both the system installed in step 4 and step 2. I am now able to select either system and they boot OK.

I hope the above sequence better explains what I did and what went wrong. I am not sure why what happened in step 4 did not happen in step 2 as far as setting up the Grub menu.

Regards,
       Robert.

> Date: Sun, 7 Nov 2010 00:25:48 +0000
> From: <email address hidden>
> To: <email address hidden>
> Subject: [Bug 505396] Re: /dev/mmcblk0p1 does not have any corresponding BIOS drive
>
> ** Changed in: grub-installer (Ubuntu)
> Status: Incomplete => New
>
> --
> /dev/mmcblk0p1 does not have any corresponding BIOS drive
> https://bugs.launchpad.net/bugs/505396
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “grub-installer” package in Ubuntu: New
>
> Bug description:
> Binary package hint: ubiquity
>
> I was in the process of installing Ubuntu 9.04 to a 16GB SDHC card. The install was to put the Grub boot loader on a 4GB USB thumb drive that has Ubuntu 9.10. The grub install failed, I do not know why. I have tried installing Ubuntu 9.10 on the SDHC card but that fails with portions of the file system missing (eg nothing in the proc folder or incomplete dev folder).
>
> ProblemType: Crash
> Architecture: amd64
> DistroRelease: Ubuntu 9.04
> ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
> InterpreterPath: /usr/bin/python2.6
> MediaBuild: Ubuntu 9.04 "Jaunty Jackalope" - Release amd64 (20090420.1)
> Package: ubiquity 1.12.12
> ProcAttrCurrent: unconfined
> ProcCmdline: /usr/bin/python /usr/lib/ubiquity/bin/ubiquity --only
> ProcEnviron:
> LANGUAGE=
> PATH=(custom, no user)
> LANG=en_US.UTF-8
> PythonArgs: ['/usr/lib/ubiquity/bin/ubiquity', '--only']
> SourcePackage: ubiquity
> Title: ubiquity crashed with InstallStepError in configure_bootloader()
> Uname: Linux 2.6.28-11-generic x86_64
> UserGroups:
>
> To unsubscribe from...

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.