I'm a novice--attempted to run true ubiquity to fix a boot/ubuntu can't see win 7 problem-true ubiquity was unable to load grub to any device

Bug #1211178 reported by pat ricks
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
grub-installer (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Have no idea if this is a bug or not. Before running true ubiquity, I ran os-prober and got this:
(short form) sda1: win 7(loader) windows:chain
                        sda2: win 7(loader) windows 1: chain
                       sdd5: ubuntu 13.04(13.04) ubuntu: linux
then ran WINOSDATA=true os-prober and got this:
                        sda2: win 7(loader) windows 1: chain
                        sdd5--same as above

13.04 is actually installed on my external drive but when I attempt to boot to ubuntu I get what appears to be a dos prompt with some wording about grubfordos. When I installed 13.04 to the external disc there was no partition(s) seen(only sda) at the point where I set up my partitions on the external hdd(I used the "something else" option).

When running true ubiquity first error was "unable to install in sda" I then chose sdd, then sdd1--neither worked. i then chose "continue without a bootloader" and THAT caused the installer to crash.
My most recent "paste info" BEFORE I tried true ubiquity was //paste.ubuntu.com/5974385.

thanks,
Pat Ricks

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: ubiquity 2.14.6
ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
Uname: Linux 3.8.0-19-generic i686
ApportVersion: 2.9.2-0ubuntu8
Architecture: i386
CasperVersion: 1.331
Date: Mon Aug 12 09:23:46 2013
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- nomodeset
LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
pat ricks (rickypat7) wrote :
Revision history for this message
Phillip Susi (psusi) wrote :

I don't know what you mean by "true ubiquity" but you seem to be trying to install grub to a drive with no partition table. You must partition the drive.

Changed in grub-installer (Ubuntu):
status: New → Invalid
Revision history for this message
pat ricks (rickypat7) wrote : Re: [Bug 1211178] Re: I'm a novice--attempted to run true ubiquity to fix a boot/ubuntu can't see win 7 problem-true ubiquity was unable to load grub to any device

I was told the "wizard name" of the ubuntu installer was ubiquity.
Yes, it seems that way, but unfortunately neither the Ubuntu installer(nor the included partition mgr) see/recognize the partitions on my c drive. More unfortunately, in trying to fix this "problem", I deleted one of my partitions and now THAT problem has priority. Thanks, though.

________________________________
 From: Phillip Susi <email address hidden>
To: <email address hidden>
Sent: Tuesday, August 13, 2013 8:45 PM
Subject: [Bug 1211178] Re: I'm a novice--attempted to run true ubiquity to fix a boot/ubuntu can't see win 7 problem-true ubiquity was unable to load grub to any device

I don't know what you mean by "true ubiquity" but you seem to be trying
to install grub to a drive with no partition table.  You must partition
the drive.

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1211178

Title:
  I'm a novice--attempted to run true ubiquity to fix a boot/ubuntu
  can't see win 7 problem-true ubiquity was unable to load grub to any
  device

Status in “grub-installer” package in Ubuntu:
  Invalid

Bug description:
  Have no idea if this is a bug or not. Before running true ubiquity,  I ran os-prober and got this:
  (short form) sda1: win 7(loader) windows:chain
                          sda2: win 7(loader) windows 1: chain
                         sdd5: ubuntu 13.04(13.04) ubuntu: linux
  then ran WINOSDATA=true os-prober and got this:
                          sda2: win 7(loader) windows 1: chain
                          sdd5--same as above

  13.04 is actually installed on my external drive but when I attempt to
  boot to ubuntu I get what appears to be a dos prompt with some wording
  about grubfordos. When I installed 13.04 to the external disc there
  was no partition(s) seen(only sda) at the point where I set up my
  partitions on the external hdd(I used the "something else" option).

  When running true ubiquity first error was "unable to install in sda" I then chose sdd, then sdd1--neither worked. i then chose "continue without a bootloader" and THAT caused the installer to crash.
  My most recent "paste info" BEFORE I tried true ubiquity was //paste.ubuntu.com/5974385.

  thanks,
  Pat Ricks

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: ubiquity 2.14.6
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic i686
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: i386
  CasperVersion: 1.331
  Date: Mon Aug 12 09:23:46 2013
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash --  nomodeset
  LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: grub-installer
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1211178/+subscriptions

Revision history for this message
pat ricks (rickypat7) wrote : Got this.........🙏✝️❤️

Hi,
How are you doing, I want to ask you for an assistanceDo you normally order from amazon?
Thanks........pat

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.