Ubuntu
ubiquity package

install problems wiped hard drive and install shell

Asked by dave jordan

Hiya, I'm not really a noob but to be honest I've forgotten alot and things have changed......

I used the install cd downloaded last week for ubuntu 10 10, in virtual box pretty good.

Needed direct access to hardware...com ports etc so tried to install on sda3, I went "Ubuntu Try" and then install. The option for install mbr in the parttion wizard toggled back from what we set it to, aghhh /dev/sda1 is a bit of history, but recovered most of it......, Just about finished that. My own fault I should have known better.....but the wizard may need a look at.
==========================================================================.

After fixing up the other hard drive, I went back to installing ubuntu onto a single hard drive set up as the first /dev/sda1, boot flag is set, and initially I was able to reboot into ubuntu, but I think I may have had the install disk in the cd/dvd drive.

Now if I boot from the hard drive I get into a text based install screen (select language etc ). Sometimes, if I boot from the cd and take boot from 1st hard drive I get a proper installed boot, sometimes not. Tried option F4 normal....not sure if that makes a difference.

I had a look through the /boot area but, things have changed with grub since the last time I used Linux properly. In fact not even sure it's grub, wheres, the *.lst files gone ? LOL

Soemtimes if I get the timing right and press esc on the boot, I get the boot messages up saying unknow user can't start "gtxterm". So I guess it's a script somewhere left over from install.

Dave

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu ubiquity Edit question
Assignee:
No assignee Edit question
Solved by:
dave jordan
Solved:
Last query:
Last reply:
Revision history for this message
Tim (samacaster) said : 		#1

Ubuntu 10.10 uses the the Grub2 bootloader. You should install it on /dev/sda. The install is pretty strait forward. Install alongside another OS, erase and use whole disc, or manually partition. If you have no other OS your using, I'd erase and use the whole disc and let the Live CD do its work.

Revision history for this message
dave jordan (davo-ozzy) said : 		#2

Thanks,

I'll give that a go, been off the Linux pills for a while but it's coming
back. The Grub looks a bit different thoough!

Thanks

Dave

On Thu, Nov 18, 2010 at 5:19 PM, Tim
<email address hidden>wrote:

> Your question #134491 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/134491
>
> Status: Open => Answered
>
> Tim proposed the following answer:
> Ubuntu 10.10 uses the the Grub2 bootloader. You should install it on
> /dev/sda. The install is pretty strait forward. Install alongside
> another OS, erase and use whole disc, or manually partition. If you have
> no other OS your using, I'd erase and use the whole disc and let the
> Live CD do its work.
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
> https://answers.launchpad.net/ubuntu/+question/134491/+confirm?answer_id=0
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.launchpad.net/ubuntu/+question/134491
>
> You received this question notification because you are a direct
> subscriber of the question.
>

Revision history for this message
dave jordan (davo-ozzy) said : 		#3

Tim,

thanks, I tried grub2-install man.db error, tried to find what might be locking it, probably the install script...failed so I blew sda1 away and did a fresh install. Better to start off right I think.

Thanks for your help!!

Dave

Revision history for this message
dave jordan (davo-ozzy) said : 		#4

This returned to haunt me after a reboot with the install liveCD in, after updating repos...

so I removed grub2 and installed legacy grub. Seems to be ok now.

It was a pain as the instlaller locks up some aspects of the software package managers and some things will not install,

I tired killing the processes for the installer, in the end had to settle for the tty....then things could happen

Dave